Let’s just say, previous roadmap comments
and here
and further discussion of those or other ones in this thread make sense here
Let’s just say, previous roadmap comments
and here
and further discussion of those or other ones in this thread make sense here
Huh. I don’t really see how that can be true, since in this thread the top post points to the chess.go one!
But - whatever, at least this one has a more relevant heading ![]()
Should it be in “Meta”, rather than “General Go Discussion”? ![]()
Yeah we had the chess com one inspired by go magic’s pitch.
This thread was called “do we really need …” pointing to that thread. I’m calling this “original” because in the context of an OGS roadmap, I think this is the original one.
The one you linked was called “do we really need “do we really need…”” as a kind of a joke on the way it was titled. You can check where that thread points to (i.e. here).
I’ve renamed this thread because the focus, and at least the distinct discussion point I think that has come out of it, is whether there is or should be a roadmap for ogs, long or short term.
LOL OMG. OK now I kind of see the history. Glad that’s sorted. ![]()
And just to end with something more directly relevant … since this is “the thread on the topic” here is “the GaJ view of The Roadmap” (taken from the other thread)
GaJ view of OGS Roadmap:
Disclaimer: I do not speak for anoek or OGS, I’m just sharing what my impression is.
Now we have an actual attempt at an answer to this thread’s question … in this thread ![]()
Why don’t you guys just close one or the other duplicate thread?
Implying that they didn’t already…
Did we get a new button?
Might be one that that having a very visible roadmap or updates thread would help with.
Let’s say theres new features added, a thread or a page somewhere that lists the features added (simply). I don’t mean just check the GitHub commit history ![]()
I know sometimes we get big announcement threads of big features, but some small ones along the way could be dumped into a thread.
Idk, it feels like busy work to ask the devs to write about little updates like this. Like “Add to library” explains itself.
If we’re asking devs for increased communication, im more interested in the bigger ticket, forward looking discussions
I mean if we spread it out on who posts these things, or if we have a specific place where anyone who contributed something can post, or anyone that noticed a new feature can post it, I don’t see that as a bad thing.
I bet there’s a lot of little features people don’t know about because they don’t get announced
I like the idea, but among whom would the work be spread out? OGS has like 2 consistent devs
People that are trying to keep up to date with the development I suppose. I might make a thread for new (small) features and then when anyone spots a new feature crop up, or if the contributor of that feature wants a place to share it, it could go in there.
If it’s a good idea that is, to make such a thread, and there’s no better alternatives.
One could also imagine making a series of little videos like polgote did
maybe good for awarenes, but it is quite a bit of work.
Most of what has been discussed in this thread has been focussing on internal goals. Some nice points have been made (especially @GreenAsJade’s posts), but what I am curious of is are there also external goals OGS has in mind, as a roadmap to the future.
@anoek: what is your view on OGS’s long term goals?
Benjito was publishing such a thing himself for a while ![]()
I know that there are three or four forum dwellers who definitely do watch changes going in, so maybe you could get some support.
What’s an “external” goal?
Internal goals are goals to maintain, improve, etc. OGS (site, forum, etc.)
An external goal is any goal outside OGS, but definitely within or related to the go world.