R Hackathon 1/Source Code Management
Requirements
All source code developed at the hackathon will be made available immediately under an OSI-approved license. This and the collaborative development that is at the heart of the event require all source code to be committed to an open (at least publicly and anonymously readable) source code repository under version control.
To make integration of the code into the existing package codebases as painless as possible, using the native code repositories of the participating packages may be preferable to using a repository that has been set up separately for the event. To qualify, an existing repository must fulfill the following requirements:
- uses a commonly and freely available version control software (e.g., cvs, svn; but not Perforce as it is commercial)
- permits public and anonymous checkout of the source code tree (i.e., anonymous read-access); the ability to browse the repository on the web is extremely useful but not required
- permits on-the-fly adding of commit-privileged developers (i.e., write-access) at (or before, or after) the hackathon event
Survey of participating packages
This survey means to get an overview of the source code repository, version control software, and development policies employed by the participating packages.
| Package | License | Source code release | Source code repository (server or URL) | Version control system | Anonymous checkout? | Can grant write-access? | New code on trunk or branch? |
|---|---|---|---|---|---|---|---|
| ade4 | GPL v2 | CRAN (v.1.4-5) |
browse CVS | cvs | No (1) | No (1) | New branch (1) |
| APE | GPL v2 | CRAN (v.2.0-2) |
https://svn.mpl.ird.fr/ape/ | svn | Yes | Yes | ? |
| apTreeshape | GPL v2 | CRAN (v1.4-0) |
? | ? | ? | ? | ? |
| ComPairWise | GPL | CRAN (v1.01) |
? | ? | ? | ? | ? |
| Geiger | GPL | CRAN (v.1.0-91) |
None yet | None | - | - | New branch, I guess |
| Laser | GPL v2 | CRAN (v1.0) |
None yet | None | - | - | - |
| Mesquite | LGPL 2.1 | Zip file tgz file svn | Mesquite SVN | svn | Yes | Yes, but so far only core team | trunk |
| OUCH | GPL v2 | CRAN (v1.2-4) |
? | CVS | N | N | ? |
| PaleoTS | GPL v2 | CRAN (v0.2-1) |
? | ? | ? | ? | ? |
| PhyloGR | GPL v2 | CRAN (v1.0-6) |
? | ? | ? | ? | ? |
| PhySim | GPL v2 | CRAN (v1.0) |
? | ? | ? | ? | ? |
| Picante | GPL v2 | ? | ? | ? | ? | ? | ? |
| Notes | Source code license | Released source code download, hyperlinked to download URL | Repository server, hyperlinked to URL of repository tree (if publicly visible) | name of version control software (e.g., rcs, cvs, or svn) | Yes or no, possibly qualified by conditions (if any) | Yes or no, possibly qualified by conditions (if any) | Policy for committing possibly experimental code (e.g., main trunk, development branch, or new branch) |
(1) An access to the ade4 cvs would require either to create new accounts on the server of University Lyon 1 (not allowed, at least within the week), or to allow anonymous r/w access via ssh (not allowed by system administrator). I will bring a local copy of the cvs.--Jombart 08:14, 4 December 2007 (EST)
