Proposal: add a "transparency" section to our philosophy doc?
Open
docs
- Dominant language
- Go
- Stars
- 4.8k
- Forks
- 542
- Avg merge
- 7d 21h
- Merged PRs (30d)
- 2
Description
I feel like we're very transparent with each other as-is, and it would be nice to write it down. Some ideas top of my head:
- We record all meetings and put them on youtube
- Agendas written down for dev meetings
- We have dev meetings!
- We vote on stuff in issues
- We file proposals in issues
- More?
What do folks think?
Contributor guide
Research direction
Start by locating and reading the philosophy document, then review this proposal and its discussion. The scope is not decided: agree which transparency practices belong in the document, and consider the work done when the team approves and adds the section.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100