open-discussion
open-discussion > RE: Mark projects private during testing?
Jul 31, 2008 02:07 AM | Luis Ibanez
RE: Mark projects private during testing?
Hi Bennett,
My humble advice:
Although it may make sense to keep a project private during the initial stages of development, this is in general a bad way to start an Open Source project.
The right to make mistakes in public is a benefit
granted to developers in the context of Open Source development.
Projects that have a private birth, have also the
unfortunate tendency to remain private.
We have heard too many times of projects that are
"Open Source", but for which the code is not available because the authors are still "cleaning up" the code,...year after year...
A big README.txt file stating that the project is
in very active development should be enough warning for any visitor to know what to expect if they see that your project is changing from day to day.
Making a project private will deprive you from the
benefit of the collective intelligence from the
community that could help you make it better, in
particular at the very early stages, when the advice is needed the most.
Best Regards
Luis
Threaded View
| Title | Author | Date |
|---|---|---|
| Bennett Landman | Jul 30, 2008 | |
| NITRC Moderator | Aug 1, 2008 | |
| Luis Ibanez | Jul 31, 2008 | |
| Luis Ibanez | Jul 31, 2008 | |
