Work in the Open
Before releasing your project, you may have worked on it in secret or just for your own purposes. Perhaps you enlisted the help of some folks, but in general you worked behind closed doors and outside of the potentially critical gaze of onlookers. That all changes the moment you release it; from there on out it will be free, open, and public. All of the development processes around it should similarly be free, open, and public; otherwise you will lose the trust of your users and contributors both.
These processes are not limited to the mechanical “create contribution-review contribution-merge contribution” development steps, though they’re certainly important to perform openly and in the public eye. The processes also include ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access