What do you guys think about a Trello Roadmap with Feature Voting?

Feedback Suggestions
1

Today there was this exchange:

I personally think that something like a Trello Roadmap with Feature Voting could potentially be very useful.

I know that some indie game developers are using these. One example would be this Trello from the game Barotrauma.

It seems that a while back OGS used UserVoice for feature requests and user suggestions. It seems that this effort has died down.

Key Advantages of using a Trello Roadmap

  1. Accessible to non-technical users
    • “Cards” and “Votes” are easy concepts
    • No need for labels or github issue etiquette knowledge
    • Anecdote: Even I feel reluctant to engage on GitHub even though I’m an engineer
  2. Prioritization via voting
    • Users can signal demand for what they want
  3. Clean Roadmap
    • Higher ups control what appears on the board
    • Avoids the clutter of low-quality input (not saying that is the case here but there are 111 open github issues)
    • Users get an overview of what is currently being worked on
  4. Strong community engagement
    • Users feel heard when voting
    • Encourages lightweight participation by simply clicking on an upvote button

Possible Downsides

  • Might not be used by enough people as the OGS community is rather small, see the deprecated UserVoice effort
  • Somebody has to do the curation of the board
  • Not developer-centric as it doesn’t integrate with commits
  • User votes could be misleading as popularity doesn’t always reflect importance
  • Might feel like double maintenance to have Trello cards and GitHub issues

Possible Flow

Idea (from the OGS forum or other channels if existing) → Trello vote → Selected → GitHub issue → Development

OGS has design issues
2

This. I liked the uservoice page, but I assume there was some cogent reason for retiring it

1 Like
3

I don’t know about trello (i’ve never used it) but uservoice was taken off because it wasn’t very useful; it didn’t allow users to properly discuss about the feature ideas, or properly explain and elaborate what they would want their features to actually do. Uservoice also had some limit on the votes people could cast (iirc it only allowed 10 votes per user), so most people just ran out of votes pretty quickly.

So it was deemed to be better to just use the forum, so that people could hone those ideas together and give some input on what they would prefer from any new feature suggestion.

There’s also github, where people can also actually work on the code together and build those features ^^

But like i said, i’m not familiar with trello at all… Is it better for discussing about feature ideas than the ogs forum?

4

I somewhat tried to elaborate that in the initial post but let me try to rephrase it.

The purpose is a different one:

  • Forum → exploration & discussion
  • Trello → (pre selection), prioritization & overview

The ideation process should happen in the OGS Forum (or other channels like Discord, Reddit or whereever else people are active).

But these ideas often end up being unfocused, repeated, fuzzy, lost in the ether, not clearly prioritized, and we lose track of them. They come up are discussed, then nothing happens, they disappear, and then 10 months later someone posts the same idea again.

A Trello Roadmap would show all ideas and their popularity at a glance. I encourage you to look at the Barotrauma example I linked above. That said the Barotrauma Trello was more active when the game was still being very actively developed. Now since the game is finally released and activity has died down somewhat so has the action on the Trello but I think it’s still a good example.

Trello is not good for in depth discussions but for transparency, community interaction and providing an overview. I think it would enable the community to get a deeper inside into what’s going on short and long term on OGS.

Few concrete examples and thoughts

  • I consider myself to be a relatively frequent OGS user (although I’m a little on and off with Go) but I have absolutely no idea what is currently being worked on or what is planned for the rest of the year or next year
  • Was the sound change intentional, is the community happy with it, will we ever talk about it again or is a thread with 10 users and 14 likes just not enough backlash? Did anything change about the sound of stones?
  • What about the chat issue, will we forget about it again, how many people actually want a fix? Private chat blocks game chat
  • What about the proposal to change the behavior of the First move timer for white in correspondence tournaments
  • What about the Feature Request: SGF Comments with four upvotes. Is that being considered? New people interested in that idea will have a hard time expressing their support because the last comment was over a month ago so the thread has gone to Valhalla by now
3 Likes
5

Ahh right! So trello is more like a site where developers can tell what they are working on, instead being open for all users to make their wishes for new features?

I can see how ogs would benefit for something like that! Now it feels like all those wonderful people coding new features just code the feature and push it to the main site, but theres no coherent system to let users know what is being worked at, or what has been done recently.

ps. ogs has a link to changelog in the “about” page, but that link seems to be to the wrong section of github? The current link is for Commits · online-go/online-go.com · GitHub, but i think it should go for Commits · online-go/online-go.com · GitHub?

1 Like
6

Without an increase in development resource, you might just end up with a beautifully prioritised list of hundreds of items and only the resources to do the top few. Also anoek is likely (and within his rights) to want to work on things he wants to work on, with some bias to what the community wants, but not controlled by it.

On my other screen:
Screenshot 2026-03-31 at 22.06.27
and we have 8 developers.

9 Likes
7

Hmm i think there’s a ton of things he wants to work on, but then theres constantly new bugfixes and other things popping up which become more urgent ://

But yeah, he def has a long to-do list he wants to work on, but i don’t think it’s written down anywhere…

Thank god he’s not the only developer working on ogs, but i guess everyone else has their own stuff they wanna focus on too, so it may feel kinda random sometimes

1 Like
8

Koba has largely nailed it:

I know for a fact that this is a major reason why anoek doesn’t commit to “roadmaps or timelines”, because experience shows that any such commitment will inevitably be “wrong” and later “used as evidence in a negative way”.

And of course we are also subject to this one:

BUT

this doesn’t mean “the developers who are contributing would not like to see a better roadmap with clear discussion and preferences from the user community”.

Personally, I’d love to see that.

There is one missing ingredient, and one wrong assumption, that prevents this from happening: assuming that anoek will “run with it and own it”.

What it would take for “A Trellow Roadmap”, or any other “organised effort to collect user input and curate it” is someone actually doing that over time.

A proposal that says “would it be nice if we have this” is largely worthless in a practical sense.

Doing it … consistently and in a sustained manner, directing conversations from here to it, summarizing and keeping it up to date: that is the hard work that is needed to make such a thing actually useful.

The tool (Trello or whatever) doesn’t matter too much, as long as the person driving it can use it in the way that’s needed.

If the proposal relies on “anoek needs be involved in operating this tool” then it’s not going to fly.

If the proposal is “I’m going to collect all our input, and curate it and summarize it back on an ongoing basis”: frickin go for it.

anoek listens to discussions here, curation of the discussion could totally add value.

But it’s not a “tool idea” its an activity someone would have to do ongoing to make it work.

12 Likes
9

I believe the closest we have to sonething like that which works today is GitHub thumbs up. The list is sortable by reacts it is possible to prioritize that way.

+1 to all the comments to the effect of this not being a tooling issue, but a question of resources. If devs were to divert some energy from development to planning (which isnt a bad thing) i think id be more interested in a lightweight “here’s what were working on” blog post rather than adoption of trello (or whatever sprint board tool)

4 Likes
10

I wonder if this ^^ is the role that What’s New is going to play?

Yet to be seen how that pans out :slight_smile:

3 Likes
11

Possibly. Seems like What’s new is more backwards looking (“here’s what we already built”) whereas “here’s what we’re working on” is more forward-looking. Both are good, but OGS devs are already pretty good at announcing what was made imo.

1 Like
12

I actually think that’s not true :stuck_out_tongue:

Like if you think about the amount of features that are just find out when you find out…

We got a feature to add other players games to the sgf library, we got a feature for supporters to analyse other players finished games without running a review, we got an ai analysis summary table, we temporarily had a way to choose if a player was a good sport, we even got the what’s new page, without any announcements that these features exist. One day I just spotted the sponsorship request page like the news page.

I’d say the majority of updates go unannounced, and typically I end up asking someone “is that new?”.

But… the big things do get announced.

If there’s a change of default of the automatch settings, if there’s a change in some sort of policy, or a change in the ratings and so on, those things can get a banner to draw people in for comments and feedback, and I think that’s a quite good thing.

Just if we have to be objective, if you don’t visit OGS everyday, and you don’t read the pull requests, and don’t randomly click every button, you won’t know a feature like personal chat channels (not malkovich or public) were added ages ago where you could store your variations in correspondence.

But I think the what’s new page is a great initiative, I think it’s worth telling people all the things that have changed or been added, and get them excited for the development and updates.

We should probably do videos even to show off the features as well.

5 Likes
13

If GitHub Issues is all OGS uses, it completely lacks triaging or prioritization. Tasks/issues need to be sorted by a compound value of effort and impact, such that low effort and high impact tasks/issues get resolved first (because they’re low effort, low-skill developers can handle them).

Issues like Why are some pages not reflected in the tab name? (low effort, medium impact) can be delegated to an intern or entry-level developer and dealt with immediately.

As for the thread topic, I don’t think it’s a good idea because the population who uses such features are always going to be a vocal minority and not guaranteed to represent the entire userbase.

1 Like
OGS has design issues
Why are some pages not reflected in the tab name?
14

curious what your understanding of the OGS dev team is :laughing:

(change “intern” to “claude” and you make a reasonable point)

3 Likes
15

I think you might be mistaking OGS for a big software company. It’s not quite a one man and his dog hobby project anymore, but it’s closer to that than what your comment suggests you think it is.

2 Likes
16

It was an example. Even in a one-man team, I could spend a few minutes to get low-effort tasks done half-asleep. I could train my dog or nephew (or Claude) to do them too. There’s no reason to let them sit on a backlog of 100s of issues and get to them weeks or months later.

17

You say it is easy, but the fact that you have not opened a pull request says otherwise.

18

Yes there is, for example the cost of context switching, or regression risk, or that they are a waste of the one-man expert developer’s time and skills so better left as an easy little intro ticket for a developer new to OGS. I remember I fixed some simple little annoyance like that as my first contribution to the OGS FE codebase some years ago.

2 Likes
19

There’s significant overhead to learning a codebase and tech stack and even more for me who hasn’t contributed to open-source ever, so I had to spend a day learning about forking, branches, Git submodules, etc.You assume this was ever something I wanted to do over my other hobbies, such as passing the 5 kyu time trial on goproblems.com which gave me more happiness and sense of accomplishment than contributing to a codebase with zero documented functions and 1000+ lines of code in each file would.

Anyways, I know how to contribute now and will be submitting a pull request for my re-design soon.

Context switching is not a concern if you understand the codebase like the back of your hand. For my previous example, in NextJS I know how to change webpage titles and git push it within seconds.

There is no regression risk for such a simple frontend task that doesn’t touch any part of the backend.

And waste of one man’s expert time you say? Washing dishes, watching TV, or playing Go at kyu level are also a waste of expert time yet we still do them.

I don’t understand the defensiveness when I pointed out a way OGS can improve without much effort. This is why I never had much motivation to contribute here, to a community that is so resistant to change. I’ll finish my play page re-design and move on from here.

20

What you are saying is true BUT what we currently have is feature decisions by forum which is an even more vocal, even smaller minority.

Also my idea was not just to use it for prioritization but also as an overview for non tech users to see what is currently being worked on. Plus you’d also see what has been worked on and what will be worked on.

I mean the dishes need to be washed though, right? Otherwise you would have to pay someone to wash the dishes for you which seems like a waste of money and is somewhat of an invasion of privacy. So that’s not a waste of time.

Watching TV is more of a leisure time activity to chill out. So again I wouldn’t think it’s a waste of time, and someone who would think it is would probably not watch TV.

How is playing Go at Kyu level a waste of time? Is it different from playing Go at a Dan level?