Thanks for starting this conversation way back when @Jake_Watson and for reviving it @adam.butler
At the risk of restating what has already been said, here are the most pressing needs that I currently see:
- Single landing place for developers (both existing users and newcomers from external sources)
- Which repo does what, what is the state of each, etc
- Unified policies and processes (code review, style, issue triage, contributing code from a fork, who are committers, who to go to for help, etc)
- Ongoing contexts for participating (contributor-friendly issues, Outreachy, GSoC...)
- Priorities (roadmap)
- Place for refined or approved user stories
- Forum "features" category is often raw; GitHub are more granular and include implementation strategies; where does the in-between "we know this is what need we want to satisfy but we don't know how yet" go?
- Where does the work to refine them go?
- Way to link related user stories
- e.g. there are currently several ideas in the features category that are related to accessing data outside the form (A dynamic form data lookup locally without server synchronization, Enable Case Management/Preloading) ideally these would be formalized a bit and considered together
- Way to track dependencies between issues (e.g. https://github.com/opendatakit/collect/issues/1763 and https://github.com/opendatakit/collect/issues/1764)
- Way to differentiate proposals by difficulty, importance, etc. so they can be triaged
- e.g. Disable choosing an image, video or audio should be really easy but there hasn't been consensus on appearance names; Auto-gps implementation on ODK Collect @Raghu_Mittal has code written for but it's stalled because the way the form specs handle this has fairly deep implications (Spec addition proposal: location preload)
Most of these needs could probably be addressed by process changes but even better if there are tools that will provide more support. I've seen Jira+Confluence used to good effect in other open source projects and haven't seen anything else I was blown away by so I'd be ready to try.
Thank you, @adam.butler, that is a really important point.