Yep, that's correct, me and Lukas talked about it briefly in the discord, but it'll definitely be much easier for people to help out if the expected tasks are more narrow focused.
So we were talking about breaking down responsibility into various groups, and give 'em a fancy name. Examples of what we were talking about would be something like:
- DEVGRU - primary development group. Would have repo access, and emphasize on new developmental code as well as validating/merging PRs
- WEBGRU - Work on web-facing stuff. The forums, wiki, landingpage
- MODGRU - Moderators for the forums
- TESTGRU - Just go over various PRs and test them, maybe also could be relied upon to do beatups on WIP builds for community members and act as a good starting point for feedback/issues.
Not a final list, but I think the basic idea holds merit in that it lets people better focus on what they're comfortable with if they want to directly contribute to the community without having to worry about all associated baggage. We have some obvious community leaders who have a heavy say in the ongoing direction of the engine, but outside that, I like to try and keep it more flexible and less rigid with a YOU MUST SUBMIT AN IDEA TO THE GRAND COUNCIL.
Obviously people like Az, Lukas, Mango, Timmy and others with our old, grizzled, knowledgable butts have the largest input on the future path of the engine because they make a lot of direct contributions to the progress of the engine(and would be the sort of people likely to end up on DEVGRU).
So I guess if you were talking SPECIFICALLY about "people to dictate the roadmap" that'd probably largely fall to the people that make direct contributions to the engine since, you know, they're contributing to the roadmap. In the suggested new setup, that'd be the DEVGRU.
I could see a handful of people having ultimate say beyond that like me, obviously and people like Az who have a good head about necessary features for getting games produced and the like. If that should get it's own separate group to better define the expectation of duty there, then we can look into that.
But as-is, being a "Steering Committe" member has a lot of weird baggage between the written expectations and then having to also specifically be a community face(which some people are uncomfortable with) and also having to be the ones that test and merge PRs, do a lot of core development, etc. It ultimately became pretty muddied overtime which is why I think reorganizing and better establishing who-do-what is better than just slapping a few people with the SC label and not changing anything else.
It's not like we have had a lack of people helping move things forward(steering, so to speak
) - far from it - but it's be weird and vague for people not in the know, and this is what will be corrected