Async Reflection: Improving how we work
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
## Async Reflection
Use this issue to enumerate our challenges and suggest (and agree to try out) solutions.
- For a one week let's reflect on how we can improve the go-ipfs project. It can be challenges with or without proposed solutions, or things we currently do and want to do even more of. Consider starting comments with "I wish..." or "I like...."
- Then we'll vote for the challenges we think are most important to address first - maybe because they're the most acute, or maybe because they're the ones that don't seem intractable. Up to the voter. We may group similar ideas to avoid vote splitting. You get three votes.
- Then I'll create new issue/PR summarizing the most popular challenges and solutions. The team will have an opportunity to refine the solution part, I'll restate the solution and after a final call for dissenters we'll agree to try our solution out. Keep in mind these might be as un-momentous as say 'Make a PR template for go-ipfs with these fields ...'. We don't have to solve everything at once.
## Guidelines
- We don't have to be super ambitious. This project isn't going away, so we can feel free to defer tough questions if we don't have good answers.
- This is a public forum, and people with zero context can read this issue, so just frame things constructively. We don't want to scare away passers by.
- One 'I wish/like' per comment so we can easily vote on them afterwards.
## Notes
Our previous async reflection was #5781
Contributor guide
Assessment
This issue has not been assessed yet.