Difference between revisions of "NCBO-OOR Source Control Practices and Processes"
Benjamindai (talk | contribs) |
Benjamindai (talk | contribs) |
||
| Line 1: | Line 1: | ||
=Stage 1 – Start Simple - Initial Development= | =Stage 1 – Start Simple - Initial Development= | ||
| − | + | The entire OOR community has access to the NCBO-OOR source code (essentially the BioPortal): | |
| + | |||
The BioPortal server side source can be perused at the following NCBO GForge link: | The BioPortal server side source can be perused at the following NCBO GForge link: | ||
Revision as of 16:37, 18 February 2009
Stage 1 – Start Simple - Initial Development
The entire OOR community has access to the NCBO-OOR source code (essentially the BioPortal):
The BioPortal server side source can be perused at the following NCBO GForge link:
https://bmir-gforge.stanford.edu/gf/project/bioportal_core/scmsvn/?action=browse&path=%2Ftrunk%2F
The BioPortal user interface source can be perused at the following NCBO GForge link:
https://bmir-gforge.stanford.edu/gf/project/bioportalui/scmsvn/?action=browse&path=%2Ftrunk%2F
In April 2009, a NCBO GForge branch will be created starting with an initial core pool of developers having commit access (including Michael Gruniger's graduate students).
Stage 2 – Ramp-Up Collaboration
As the developer community grows, there will quickly be a need for clear open source collaboration processes and practices. Mike Dean and Benjamin Dai will establish Open Source Collaboration policies (e.g., commit rights, trusted developers, external developers, etc). The NCBO GForge site will continue to be the primary source control mechanism for OOR.
As details of the NCBO-OOR open source collaboration policies are established, they will be updated on this wiki page.