I hope to create an open community around documenting open-source software and practice what I preach: To eat my dog food, as they say. What better way than to create a repo and invite the contributions of other writers?
To be honest, its a bit tough to do this. I believe in “open source.” I promote it, even.
But here I am preparing to put my most ambitious project out there for others to join, and part of me is holding back. Inviting others to join challenges my sense of ownership. To put these feelings in words: Will this end up creating a mess of written-by-committee pablum that serves little purpose? As a writer, I like to revise and craft my work iteratively. How can I do that if I’m fending off the well-intentioned interference of other writers looking over my shoulder?
To overcome this hesitation, I have to re-envision my notions of ownership. Is this “my content?” Is this “my project?” Aside from contributing content, then, I hope to provide the system by which it gets created.
Systems are composed of people, processes, and technology.
This system I’m creating will consist of:
- People: Experienced technical writers and software teams who need to document open-source software.
- Processes: Open source contributions with an agile workflow following the open-source guide.