Difference between revisions of "PMC proposals/Repository reorganisation"
(just copy/paste stuff from my original & Gema's summary mails) |
m (move around a little) |
||
| Line 3: | Line 3: | ||
===Summary=== |
===Summary=== |
||
| − | The incubator module in SVN has |
+ | The <tt>incubator</tt> module in SVN has been quite successful in encouraging the contribution of less developed material; however, the range of development statuses is problematic. |
| + | In this proposal, we propose to split <tt>incubator</tt> into <tt>incubator</tt>, <tt>nursery</tt> and <tt>staging</tt>. |
||
| − | but the range of development statuses is problematic. |
||
| − | I propose that we split incubator into 'incubator' and 'staging' |
||
===In Detail=== |
===In Detail=== |
||
| − | + | <tt>trunk</tt> would contain pairs in "release" and "[alpha|pre]-release" status, and would exclude unreleased language pairs/software. |
|
| − | status an no pair without a release. |
||
| + | <tt>staging</tt> would contain pairs that build, and have an advanced status in all modules (dictionaries with closed categories and a decent coverage, an "ad hoc" PoS tagset and .prob, good coverage of main contrastive phenomena, testvoc clean, and a post-generator if needed). |
||
| − | STAGING: would contain pairs that builds and have an advanced status |
||
| − | of all modules (dictionaries with closed cathegories and a decent |
||
| − | coverage, an "ad hoc" PoS tagset and .prob, good coverage of main |
||
| − | contrastive phenomena, testvoc clean, and a post-generator if needed). |
||
| − | There should be a "PROBLEMS" file saying, IMO, status and major |
||
| − | problems found while reading translations done with this pair (so, not |
||
| − | a complete evaluation but a general compilation of big problems |
||
| − | detected at the output). That could be a middle solution between Fran |
||
| − | and Jim point of view. Would [Alpha|Pre]-releases also be allowed for |
||
| − | pairs in staging? |
||
| + | There should be an "ISSUES" file which gives an overview of the status of the module, and outlines specific known issues. |
||
| − | NURSERY: would contain pairs that build but that have not been |
||
| − | developed deeply or maybe data copied from other pairs that needs work |
||
| − | or very poor data on some modules, etc. |
||
| − | + | <tt>nursery</tt> would contain pairs that build but that have not been developed to an advanced stage. |
|
| + | |||
| + | <tt>incubator</tt> would contain pairs with pieces of translators or analysers. |
||
Revision as of 22:35, 8 February 2011
2011/02/08 #1: Repository Reorganisation
Summary
The incubator module in SVN has been quite successful in encouraging the contribution of less developed material; however, the range of development statuses is problematic. In this proposal, we propose to split incubator into incubator, nursery and staging.
In Detail
trunk would contain pairs in "release" and "[alpha|pre]-release" status, and would exclude unreleased language pairs/software.
staging would contain pairs that build, and have an advanced status in all modules (dictionaries with closed categories and a decent coverage, an "ad hoc" PoS tagset and .prob, good coverage of main contrastive phenomena, testvoc clean, and a post-generator if needed).
There should be an "ISSUES" file which gives an overview of the status of the module, and outlines specific known issues.
nursery would contain pairs that build but that have not been developed to an advanced stage.
incubator would contain pairs with pieces of translators or analysers.
