NetarchiveSuite|
Size: 1326
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 1: | Line 1: |
| = Communication = The ["Developer Manual"] is the main piece of description of how to contribute. 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. |
= How to contribute with patches to NetarchiveSuite = <<Action(edit)>> |
| Line 4: | Line 4: |
| If you have technical or general questions about the use of the tools, you are welcome to contact us via [[MailTo(netarchivesuite-users AT lists DOT gforge DOT statsbiblioteket DOT dk)]][[FootNote(You need to be logged in to !NetarchiveSuite in order to see mail addresses properly)]]. You can subscribe to the mailing list [https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users here] |
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 7: | Line 6: |
| If you want mails on announcement of releases, change in roadmap, events etc., you are welcome to subscribe to the mailing list [[MailTo(netarchivesuite-announce AT lists DOT gforge DOT statsbiblioteket DOT dk)]][[FootNote(You need to be logged in to !NetarchiveSuite in order to see mail addresses properly)]]. You can subscribe to the mailing list [https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-announce here] |
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. |
| Line 10: | Line 8: |
| Alternatively, technical questions can be posted to the [https://gforge.statsbiblioteket.dk/forum/forum.php?forum_id=6 developer forum]. | 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 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. 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.