The response to the request for developers on Sourceforge has been
encouraging. There are now five more people considering making
contributions to NCO than there were a month ago, a year ago,
and five years ago. NCO is already a big chunk of software to
digest so it will probably be some weeks or months before patches
start coming in. But remember that any contributions are welcome, code
patches, web page redesign, build improvements, documentation updates....
Each of you has so far expressed interest in a different aspect
of the operators, which is fine, but we want everyone to be aware
of what others are working on. Now is probably a good time to
ask everyone to begin to send messages related to NCO to the
appropriate Sourceforge discussion forum:
Of course we can still do offline emails when appropriate, but it is
best if technical discussions, ideas, and submission of (small)
patches takes place in the open. Using the fora will help avoid
duplication of effort and these will serve as a useful archive for new
users and developers and anyone who wants to create a FAQ. The way the
discussion forum is set up you will not receive email when someone
posts to it unless you go there and click on "Monitor Forum" in which
case you receive copies of everything in your email box.
If and when you decide to tackle something on the TODO list, please
post a message with to that effect (i.e., with the TODO item number)
to the Developer's Forum.
Those of you who have already identified tentative projects to work on
via offline correspondence with me should post what you are doing to
this forum once you begin to hack the source.
Finally, use CVS if you want to stay bleeding edge, but be warned that
only tagged releases (e.g., nco1_1_49) are expected to be stable:
cvs -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco login
cvs -z3 -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco co -kk nco
cvs -z3 -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco co -r nco1_1_49 -kk nco
Thanks,
Charlie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear potential NCO contributors,
The response to the request for developers on Sourceforge has been
encouraging. There are now five more people considering making
contributions to NCO than there were a month ago, a year ago,
and five years ago. NCO is already a big chunk of software to
digest so it will probably be some weeks or months before patches
start coming in. But remember that any contributions are welcome, code
patches, web page redesign, build improvements, documentation updates....
Each of you has so far expressed interest in a different aspect
of the operators, which is fine, but we want everyone to be aware
of what others are working on. Now is probably a good time to
ask everyone to begin to send messages related to NCO to the
appropriate Sourceforge discussion forum:
Open Discussion:
http://sourceforge.net/forum/forum.php?forum_id=9829
general discussion, inevitably some overlap with Developer's forum
Discussion of ambitious plans, future directions
Help:
http://sourceforge.net/forum/forum.php?forum_id=9830
Installation problems, user's questions (e.g., how do I average x and y....?)
Developers:
http://sourceforge.net/forum/forum.php?forum_id=9831
patches, technical questions related to modifying NCO,
discussion of specific items on TODO list and best how to address them
Of course we can still do offline emails when appropriate, but it is
best if technical discussions, ideas, and submission of (small)
patches takes place in the open. Using the fora will help avoid
duplication of effort and these will serve as a useful archive for new
users and developers and anyone who wants to create a FAQ. The way the
discussion forum is set up you will not receive email when someone
posts to it unless you go there and click on "Monitor Forum" in which
case you receive copies of everything in your email box.
If and when you decide to tackle something on the TODO list, please
post a message with to that effect (i.e., with the TODO item number)
to the Developer's Forum.
Those of you who have already identified tentative projects to work on
via offline correspondence with me should post what you are doing to
this forum once you begin to hack the source.
Finally, use CVS if you want to stay bleeding edge, but be warned that
only tagged releases (e.g., nco1_1_49) are expected to be stable:
cvs -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco login
cvs -z3 -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco co -kk nco
cvs -z3 -d:pserver:anonymous@cvs.nco.sourceforge.net:/cvsroot/nco co -r nco1_1_49 -kk nco
Thanks,
Charlie