How to Organize Feature Requests & Projects?
Intro & Key problems for feature & project tracking
It's a gap right now how we propose, discuss, and organize around projects. The idea is not to gatekeep, but instead to organize our communication & ideas.
Keeping a Feature and Project List
I think a github project board might be the best way to track the different feature requests and projects. We can create cards to note the idea and give links to any discussion threads around it. The board could have 4 columns: "projects" "feature requests" "in progress" & "done". This could serve as a central repository for the master list of things that people could look at for what might strike their interest. If we go this route, I could use someones help to add cards for the existing feature requests.
Proposing Features & Projects
I think this should be done with forum threads. Once something reaches the point of, yes - that is a good idea, we create a card for it. The status of the card will be helpful to know what has been completed vs not. Project threads would probably be best discussed in the 'development' category and have a title that takes this format: "RFC: <project name>"
Working on Features & Projects
I think a dedicated thread for someone who wants to start work on a project would be a good thing. From that thread we can coordinate discussion, create a project board, identify the project owner, and have a place for others to mention thoughts, give feedback, or volunteer support.
Desired Outcome & Next steps
Any thoughts?? I think the overall next steps will be to document this process-process in the dev-setup documentation somewhere, eg: "this is how to start a project!" We will also need to create the project & features board, and perhaps do a few kick-off project threads to set the example.
@redrum given your background maintaining the TripleA feature request list, I'm particularly curious what you along with the rest of the community may think.
As an example, here is a (somewhat poorly written) RFC thread: https://forums.triplea-game.org/topic/3390/rfc-save-games-as-game-deltas
To further illustrate, under this proposal, the next step would be for that to be discussed and eventually entered into the project board as a card that would link back to the RFC thread. Then whenever anyone kicks off the effort and could begin work, they would create a new thread. That new thread would then centralize conversation about the active project & would signal for us to create a project board to track the individual tasks & efforts of the project.
For context, this is an example of an active project board: https://github.com/orgs/triplea-game/projects/2
We have a 'problem tracker' project board: https://github.com/orgs/triplea-game/projects/3
The board to track project ideas and feature requests would be somewhat similar to the 'problem tracker'