| 31 | | * After some years private websites often go away and the code is lost |
| 32 | | * From the start all code there is licensed under the GPL (or compatible), so all can use the content there without worry, and mature modules may be moved into the main GRASS code as needed. |
| 33 | | * The code will be widely backed up and if the main source code ever moves, all the addons will move with it in parallel |
| 34 | | * Ability to take advantage of the svn history and trac system integration (this is really quite a good thing) |
| | 31 | * Community building: It gets people involved and educated - contributing to the main GRASS code uses the exact same website, software, and commands. Thus the trip from contributer to full developer requires a minimum of training. |
| | 32 | * Archival: After some years it is common that people move on, then private websites fade away and the code is lost. The code will be widely backed up and if the main source code ever moves, all the addons will move with it in parallel. |
| | 33 | * Guaranteed license: From the start all code there is licensed under the GPL (or compatible), so all can use the content there without worry, and mature modules may be promoted into the main GRASS code as needed. |
| | 34 | * Caretaking: In years to come others may easily contribute bug fixes and upgrades if a flaw is found or the GRASS API changes. |
| | 35 | * Infrastructure: Ability to take advantage of the svn history and trac system integration, including bug tracker. (these are really quite good things) |
| | 36 | |
