At Common Fate, we decided to open source our software for one simple reason: users have the right to know what’s running on their machines and in their environments. We don’t believe that our software development processes can or should be insulated from our users, their experiences or their critiques.
So, the next obvious step was to create an RFD process. Broadly, our RFD process will follow the same philosophy as NWG’s RFC 3:
The content of a note may be any thought, suggestion, etc. related to the software or other aspect of the network. Notes are encouraged to be timely rather than polished. Philosophical positions without examples or other specifics, specific suggestions or implementation techniques without introductory or background explication, and explicit questions without any attempted answers are all acceptable. The minimum length for a note is one sentence.
These standards (or lack of them) are stated explicitly for two reasons. First, there is a tendency to view a written statement as ipso facto authoritative, and we hope to promote the exchange and discussion of considerably less than authoritative ideas. Second, there is a natural hesitancy to publish something unpolished, and we hope to ease this inhibition.
We want to emphasize that we welcome all discussion and feedback on our tools, our development process or any other aspect of how Common Fate functions as a company.
We’re also particularly keen to hear feedback from people in demographics that have been sidelined and discriminated against in tech, since we understand that such users are often wrongly lead to believe that their opinions are not as valuable as others.
Here are some examples of when we might open an RFD:
- Adding or changing a company process
- An architectural design decision impacting the existing software or a proposed new feature
- A change that affects the way people use our tools, especially if it could break integrations or impact their workflow
- Changes to our public-facing strategies, such as the way we write content, manage our social media or do developer advocacy
Of course, we also welcome our users to open RFDs for any ideas, suggestions, concerns they may have.
If you have an idea for a discussion but don’t know if it might be too trivial or silly — just post it! We want to hear from you. Our Developer Advocate isn’t afraid of looking dumb when he makes Twitter posts, so you shouldn’t worry either.
Check out the Discussions tab on this repo for how to open your own RFD.
When a discussion has reached a satisfactory conclusion, it'll be summarised in a Markdown file and added as a file in the repo.