-
General project info
of active contributors: _
Current workflow
- [ ] Benevolent dictator
- [ ] Multiple maintainers (#?)
- [ ] Rotating merge coordinator
Current platform / solution
- [ ] GitHub
- [ ] GitLab
- [ ] Mailing list
- [ ] Other (which?)
-
What are some issues that you have with existing web platform solutions like GitHub? (custom functionality, integrations, data ownership & migration, self-hosting, local-first, org ideology, other?)
-
What are your feature requirements? (things that a solution would need before you could consider it)
General UX requirements
- [ ] Happy with CLI-only tooling
- [ ] Need a web UI for parts of workflow
Patch / PR requirements (submitting/accepting patches)
- [ ] Need a web UI
- [ ] CLI-only is fine
- [ ] Patch files (e.g. mailing list workflow)
Patch review requirements
- [ ] Need a read-write web UI
- [ ] Need a read-only web UI
- [ ] CLI-only is fine
- [ ] Patch output for mailing-list style review
- [ ] Custom functionality / integration
CI/CD for
- [ ] Not used
- [ ] Tests
- [ ] Builds
- [ ] Deployments
- [ ] Releases
Issue tracking requirements
- [ ] Not required
- [ ] Need a read-write web UI
- [ ] Need a read-only web UI
- [ ] CLI-only is fine
- [ ] Custom functionality / integrations
Misc requirements
- [ ] Self-hosted solution
- [ ] Private repos
Any other requirements not covered?
-
Community and network importance and requirements?
- Do you use Github’s community features? If so how?
- Do you use the global search to discover and find projects?
- Do you benefit from more people discovering your project on Github?
- How could you do community building and management better if you had more control?
-
What feature(s) might make you think about moving away from your current solution?
-
What are your general views on Radicle as a project?
-
Are there any non-technical concerns that might prevent you from using Radicle? (philosophy, governance, crypto, etc)