Feature Requests -- Make a Github already



  • So 1.7 is now out.

    Do you really expect users to post the same feature requests yet again? For me, 1.8 will be the third one in a row. It's kinda ridiculous.

    THIS IS A SOLVED PROBLEM.

    Please consider setting up a normal issue tracker on Github, Google Code, Bugzilla, or even an external JIRA.

    This is a persistent easily searchable location where users can post bugs and feature requests. It includes voting functionality and the UIs are far superior, surfacing popular issues to the top, etc. Developers can easily reply with "This is under consideration" or even "wontfix", so users don't waste their time wondering if anyone read their request or if they're talking into an empty phone.

    Nobody reads through these 50+ page threads for the third time. I would bet Vivaldi developers don't do so either.

    Chrome issues tracker (google code platform):
    https://bugs.chromium.org/p/chromium/issues/list

    Firefox (bugzilla):
    https://bugzilla.mozilla.org/buglist.cgi?product=Firefox&component=Preferences&resolution=---

    Github:
    https://github.com/gorhill/uBlock/issues



  • Vivaldi has a bug tracker.
    And other external public trackers will not be introduced. Administration of such public service is much time consuming for testers and developers, the dev team is too small to handle.



  • OK. I won't be reposting my feature requests a third time, as I don't believe they're being seen and it's frankly a waste of my time.

    I hope Vivaldi becomes successful enough to afford to listen to their users in the future.



  • @jplanvers said in Feature Requests -- Make a Github already:

    Do you really expect users to post the same feature requests yet again?

    Probably... That's how things work here ATM. I mean, if it works out for them, I'm fine with reposting my requests after changing/improving them. Some users, like @Pesala have kept track of / kept reposting lists of the most common request since nearly the beginning of these forums. If the Vivaldi Team didn't change their approach on that radically, then it must be sufficient enough for them...

    @jplanvers said in Feature Requests -- Make a Github already:

    Please consider setting up a normal issue tracker on Github, Google Code, Bugzilla, or even an external JIRA.

    This is a persistent easily searchable location where users can post bugs and feature requests. It includes voting functionality and the UIs are far superior, surfacing popular issues to the top, etc. Developers can easily reply with "This is under consideration" or even "wontfix", so users don't waste their time wondering if anyone read their request or if they're talking into an empty phone.

    I've tried that already but nothing has changed so far. ๐Ÿ™„ But if you'd follow these forums more closely, then you'd certainly notice that it's definitely not an empty phone... ๐Ÿ˜‰

    @jplanvers said in Feature Requests -- Make a Github already:

    Nobody reads through these 50+ page threads for the third time. I would bet Vivaldi developers don't do so either.

    I think this user made the perfect response for your accusation:

    @jplanvers said in Feature requests for Vivaldi's new forum:

    you don't work for Vivaldi and can't speak for them

    I couldn't have said it better myself. ๐Ÿ˜

    PS. You can turn off pagination of topics in the forum's settings. (Click on your avatar in the upper right corner, go to Settings and uncheck "Paginate topics and posts instead of using infinite scroll" under Pagination menu). This will make each 50+ page thread a one-(very long)-page thread, which is much faster to look & read through. ๐Ÿ˜‰



  • Thanks for your measured response.

    Whether they read them or not, it's laborious for me to repost my suggestions every month or two, particularly as you need to wait 60 seconds between posts. I honestly just don't care enough to do it because I don't actually use Vivaldi as my primary browser.

    I would like to switch to Vivaldi, and that's why I was trying to improve it-- I would switch if they implemented customizable mouse chording in particular.

    I meant what I said; I hope Vivaldi eventually has enough staff to meaningfully engage with their customers.


  • Moderator

    @jplanvers said in Feature Requests -- Make a Github already:

    I meant what I said; I hope Vivaldi eventually has enough staff to meaningfully engage with their customers.

    Curious thing to say concerning the most engaged web-facing company I have ever dealt with. In my life.



  • Both Google and Mozilla have public bug trackers and respond to both bugs and feature requests.

    I wouldn't call them particularly responsive, and would like more engagement from both Google and Mozilla, but they do maintain modern issue trackers rather than forums resetting with each release and eventually respond to feature requests.

    They usually respond with a brusque "wontfix" or "waiting for your patch", but that's fine. If the Vivaldi devs said they wontfix my highly desired customizable mouse chording feature, for example, that would be infinitely better than no response at all.

    That's what you get with open-source, that commitment to communication is inherent to development. It is fairly rare with closed-source projects.


  • Moderator

    @jplanvers - a bugtracker does not define public engagement. And Vivaldi has one, which is pored over, discussed, verified, tested against, documented, updated, etc. by over 70 different minds from all over the world every day. The public is not in that one room. Oh, well.


Log in to reply
 

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