NetarchiveSuite|
Size: 1273
Comment:
|
← Revision 7 as of 2010-08-16 10:24:36 ⇥
Size: 1279
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| [[Action(edit)]] | <<Action(edit)>> |
| Line 4: | Line 4: |
| Description of how to contribute is given by the process description (especially the [:Process/Tracker Issue Lifecycle:Tracker Issue Life-Cycle] process which includes an [:Process/Implementation:Implementation] process) and various coding guidelines (including unit test). If you read it and follow the suggestions therein, you will not only make it easier to get your changes to !NetarchiveSuite be accepted into the main distribution, you will also likely improve the quality of your code overall. | Description of how to contribute is given by the process description (especially the [[Process/Tracker Issue Lifecycle|Tracker Issue Life-Cycle]] process which includes an [[Process/Implementation|Implementation]] process) and various coding guidelines (including unit test). If you read it and follow the suggestions therein, you will not only make it easier to get your changes to !NetarchiveSuite be accepted into the main distribution, you will also likely improve the quality of your code overall. |
| Line 8: | Line 8: |
| If possible, use our [https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse patch-tracker] to transmit the patch to us. The [:Process/Create Tracker Issue:Create Tracker Issue process] describes how. | If possible, use our [[https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse|patch-tracker]] to transmit the patch to us. The [[Process/Create Tracker Issue|Create Tracker Issue process]] describes how. |
| Line 10: | Line 10: |
| If sending patches by email, please follow the [:Process/Create Tracker Issue:Create Tracker Issue process] as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting. | If sending patches by email, please follow the [[Process/Create Tracker Issue|Create Tracker Issue process]] as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting. |
| Line 12: | Line 12: |
| For further information please to the ["Communication"] tab. | For further information please to the [[Communication]] tab. |
How to contribute with patches to NetarchiveSuite
Description of how to contribute is given by the process description (especially the Tracker Issue Life-Cycle process which includes an Implementation process) and various coding guidelines (including unit test). If you read it and follow the suggestions therein, you will not only make it easier to get your changes to NetarchiveSuite be accepted into the main distribution, you will also likely improve the quality of your code overall.
We're always happy to receive patches, though we may choose not to apply them if the implemented features go against our purposes or the code quality is too low.
If possible, use our patch-tracker to transmit the patch to us. The Create Tracker Issue process describes how.
If sending patches by email, please follow the Create Tracker Issue process as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting.
For further information please to the Communication tab.