welcome: please sign in

The following 126 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
accounts   Adam   add   added   admins   all   All   an   and   anyone   appropriate   are   as   at   be   both   by   Category   changes   check   checked   Chlipala   commit   contains   Coop   curious   custom   cvs   determine   developers   else   entries   etc   even   Every   existing   explanatory   feel   files   for   Forge   free   group   have   hcoop   hosted   how   However   http   https   id   implemented   in   init   instance   instructions   interest   into   is   it   It   keep   list   listinfo   lists   mail   mailing   make   misc   modification   modifying   module   modules   Most   most   necessary   need   net   new   non   of   on   open   others   our   Our   out   Outdated   owned   particular   probably   programs   project   public   Rely   repository   script   scripts   self   several   should   significant   so   some   Source   sourceforge   subdirectory   subscribe   support   sure   that   the   them   There   this   to   too   tools   triggers   trivial   use   We   Whenever   which   won   you  

Clear message
Edit

DeveloperGuidelines

We keep all of our non-trivial custom programs and scripts in CVS for our SourceForge project. All HCoop admins should have SourceForge accounts and be added as developers for project hcoop.

There are instructions on how to use our project CVS, both for admins and curious others.

Every commit to our repository triggers an e-mail to the hcoop-cvs mailing list hosted at SourceForge. All developers for the project should probably subscribe to this list. It's open to the public, so anyone else should feel free to subscribe, too.

Our CVS repository contains several modules. Most of them are custom tools implemented in ML and "owned" by AdamChlipala, so that most others won't even need to check them out for modification. However, the misc module is of particular interest to all admins. Whenever you make significant changes to some script (for instance, modifying an /etc/init.d script to add AFS support), it should be checked into the appropriate subdirectory of the misc module. Rely on the README files in that module to determine which subdirectory that is, and be sure to add new READMEs and new entries to existing files as necessary to keep the module self-explanatory.


CategoryOutdated

DeveloperGuidelines (last edited 2014-03-19 01:23:56 by sccinstr202144)