About closing feature requests and handling the issue



  • In the last topic I proposed few options that would allow you to break down bigger issues into smaller ones without stating untrue things (like marking not fully implemented request as done), yet you decided that it's better to keep things as is (so making people who barely look at the forum instead of thoroughly researching the truth believe that some things are different than in reality)
    There's one word that nicely names your practices, unfortunately it is considered to be too offensive to be used, even rightfully


  • Moderator

    @zakius I really don't know what you are hoping to accomplish here with comments like these. Vivaldi is a constant work-in-progress. Every new feature is just a starting point. Nothing is ever really done. You may have a bone to pick with the Vivaldi team and a personal battle that you may want to win, but I don't think that it's a battle that's worth trying to win. If anything, if you insist on trying to annoy the Vivaldi team and the Community, your personal feature requests may just end up on the bottom of their to-do lists, in perpetuity.



  • @xyzzy said in About closing feature requests and handling the issue:

    If anything, if you insist on trying to annoy the Vivaldi team and the Community, your personal feature requests may just end up on the bottom of their to-do lists, in perpetuity.

    I hope that someone behaving like a spoiled brat would not have the slightest effect on how the Vivaldi team prioritise feature requests. I, for one, definitely want more toolbar customisation, but menu customisation is more important in my opinion. What we have for toolbars is good enough for now.


  • Moderator

    @zakius said in About closing feature requests and handling the issue:

    In the last topic I proposed few options

    And in the end you say the working team does not tell the truth? Really? WUT!?

    I can understand you are angry about slow development of features, bug fixing and faulty tagging in forum.
    But then you yell in forum that the Vivaldi team is acting unprofessional. I proposed to contact the team by support link. Instead of using internal contact you start an other thread with provocative statements. 😱
    And now you think that someone wants to answer you?

    There's one word that nicely names your practices, unfortunately it is considered to be too offensive to be used, even rightfully

    Then stop this provocation. We were hearing your loud shouting.


    WikiMedia

    Please calm down.


    I whish you calm holi days with much happiness and luck, and a good New Year 2020.



  • To be honest, I'm bored of both sides in threads like this one (no matter who's correct) coz no one accepts the other opinion.


    Please don't reply to this part unless I'm completely incorrect and you want to clarify it to me.
    @zakius I ignored all prev threads on this topic, but as far as I understand, the request was marked done coz it was too confusing and new request for only still missing features was raised. This means nobody tells it's done, but some clever people decided to clear things up.


  • Moderator

    @zakius

    About closing feature requests

    Well, sometimes when i was asked in a polite way i would have moved and untagged some feature requests. But i was not contacted.
    And moderators are not allowed to override Community Managers decisions.


  • Moderator

    @potmeklecbohdan said in About closing feature requests and handling the issue:

    (…) but some clever people decided to clear things up

    And sometimes they make faults, humans often do this – me, too.

    I am very unhappy that @zakius did not contact me or Community Managers to reduce irritations, faults and anger on every side.


  • Moderator

    It's also worth noting that the Forum is a REALLY awkward way to handle feature requests. It does engage the Community to help improve Vivaldi, allows us to have constructive discussions, and is a conduit for getting feature requests into the developers' workflow. However, just because a feature is marked "Done" doesn't mean that it really is. Additional enhancements get made to fully-finished features. There can also be sub-tasks on a feature request that has been marked as Done (and is "done enough" for most people) that are still being tracked as open bugs in the Bug Tracker for developers to work on.



  • marking as done is misleadig
    it's fine to close one topic with adnotation that subtasks are observed in few other threads, that would be clever way of working around forum limitations
    marking as done while it is not done isn't clever, this only cause people on other forums to spread misinformation about Vivaldi development

    when the issue first appeared I tried talking to the moderarator that did this with no effect at all, issue was raised in public in another thread by another person and I just joined the talk, then thread was separated and left with no sign of good will to resolve the issue
    after long time with no visible progress towards properly marking the topic nor finishing the feature that was already marked as implemented I decided to remind you about the problem

    is there any way to see your roadmap orost of priorities or anything like that or we will never know anything until it lands in public snapshot?



  • @zakius So all you need is a separate PARTLY DONE tag (and maybe also FR category)?

    is there any way to see your roadmap orost of priorities or anything like that or we will never know anything until it lands in public snapshot?

    I think no. Maybe you could annoy the devs until they tell you, but that would be very dangerous & I don't recommend it.



  • @potmeklecbohdan said in About closing feature requests and handling the issue:

    So all you need is a separate PARTLY DONE tag (and maybe also FR category)?

    that would resolve this instance of issue, yes

    I'd like that to apply to all partly done features though, like middle-click-on-tab-bar-to-open-new-tab and mouse gestures and likely others I am not aware of

    I am not mad that it wasn't prioritized and stuff like that, quality requires time so it's just natural it will take time, but I'm tired of seeing "Vivaldi has this, this and that" everywhere around the web while I know it's not (completely) true because people mostly look at headlines if they don't care about some feature, headline says it's done? then it's done!

    it's more disappointing to see "yay! we are so happy to announce we did X!" and then realize it's on PoC level than to not hear about it at all for years


  • Moderator

    @zakius REALLY?!?

    it's more disappointing to see "yay! we are so happy to announce we did X!" and then realize it's on PoC level than to not hear about it at all for years

    When you start the Zakius browser company and hire an army of developers to help you make it a reality, then you can set your own priorities for feature development and define the completion criteria.

    When you release the fruits of your labour to the public, at no charge, how will you then handle it when you see posts from your users similar to the ones that you have posted here recently?

    I'll say it again: I really don't know what you are hoping to accomplish here with comments like these.



  • I hope to accomplish honest comunication, nothing more, nothing less

    I said many times: time is not issue, misleading headlines and tags are



  • do you even intent to ever sort out the issue of inappropriate flagging?


  • Moderator

    @zakius said in About closing feature requests and handling the issue:

    the issue of inappropriate flagging

    Please describe the issue.



  • feature requests and features that are not (fully) implemented or being bugged for years being flagged as done

    there's difference between "done" and "closed to split to subtasks"


  • Moderator

    @zakius if a requested feature is "done", but has bugs, these should be filed separately, as is the case for any feature with bugs.

    If the devs/admins have made the decision to mark a forum thread as done, but something is missing, then that's not to say it will never happen.

    If there's something missing you can open a new thread if none already exists, or vote for an existing one.

    The forum has a place for users to request features, but it's not a formal bug tracking system, so it's fine for it to not be perfectly accurate.



  • inappropriate flagging is misleading and causes misunderstandings while discussing featuresets of browsers and specifically Vivaldi's progress

    many people may not care about some feature but they seen request marked as done and then may spread misinfirmation further, and that happens way too often

    in caseof bugs: there's "middle click on tab bar" that doesn't work on default setup at all, but actually this one isn't closed, just a lot of people crying "but it's there, why request something that is implemented?"


  • Moderator

    @zakius said in About closing feature requests and handling the issue:

    many people may not care about some feature but they seen request marked as done and then may spread misinfirmation further, and that happens way too often

    But most interested users are able to ask if a feature is implemented.
    The forum is place for discussion and does not represent as complete list of closed bugs and implemented features.


  • Moderator

    Another thing to consider is that for many (or most?) people, a feature that has been marked as "done" really is done enough. Any additional work is either a nice-to-have enhancement or a bug fix, not a glaring omission. I personally find Vivaldi to be quite usable as is; it has everything that I need to be productive on Linux, Mac and Windows.

    The forum is place for discussion and does not represent as complete list of closed bugs and implemented features.

    Absolutely. The Forums are for us. It's not part of the developers' workflow. They may drop in from time to time if the QA team, Community Managers or Sopranos point them to a post but otherwise, they are purely focused on the next thing that needs to be done... and what that "next thing" may be (and its priority) is driven by the Vivaldi team's internal planning discussions and processes.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.