Contributing Source Code to OpenPetra.org: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (24 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
==Tracking of Bugs and Things to do== | ==Tracking of Bugs and Things to do== | ||
We are managing the projects, todo lists, feature requests, and bugs all in one place, | We are managing the projects, todo lists, feature requests, and bugs all in one place, at Github issues. | ||
We use | ===Github issues Information=== | ||
We use Github issues for tracking of those things. You can get there via this link: https://github.com/openpetra/openpetra/issues<br /> | |||
'''These issues are ''public'', i.e. everyone with web access can get to it and see the Bugs.''' <br /> | |||
* The fact that the issue tracking system for OpenPetra is public needs to be kept in mind when filing bugs or adding information and attachments and screenshots! | |||
'''Before you record something you think is not working, or does not seem what you think it ought to do, or if the application issues an error dialog, please have a look if someone already posted a similar issue.'''<br> | |||
''When you file bugs or request features please make sure that you are following our [[Mini-guide for Bug reporting]]!'' | |||
==Questions and Discussions== | ==Questions and Discussions== | ||
Questions and discussions should happen in the '''Forum'''. It can be found here: [https://forum.openpetra.org/t/developer-area Developer Forum] | |||
==Documentation== | ==Documentation== | ||
| Line 21: | Line 22: | ||
** documents outside the wiki might become forgotten on the local machine of a developer (or on a network drive) and no-one else will have (easy) access to them | ** documents outside the wiki might become forgotten on the local machine of a developer (or on a network drive) and no-one else will have (easy) access to them | ||
==Contributing Code and Patches== | |||
== | See [[Submitting patches and features]] for more information. | ||
==Copyright of Contributions== | ==Copyright of Contributions== | ||
We need to still discuss how we deal with the copyright of contributions. See also the discussion on this blog about [http://blogs.gnome.org/bolsh/2009/04/08/copyright-assignment-and-other-barriers-to-entry/ copyright assignment]. <br /> | We need to still discuss how we deal with the copyright of contributions. See also the discussion on this blog about [http://blogs.gnome.org/bolsh/2009/04/08/copyright-assignment-and-other-barriers-to-entry/ copyright assignment]. <br /> | ||
Please let us know what you would prefer! OM is a charity, and it might be a good copyright holder to make relicensing easier. But if that is a big problem for you, please let us know, and we can discuss it. | Please let us know what you would prefer! OM is a charity, and it might be a good copyright holder to make relicensing easier. But if that is a big problem for you, please let us know, and we can discuss it. | ||
Latest revision as of 19:33, 4 November 2020
Tracking of Bugs and Things to do
We are managing the projects, todo lists, feature requests, and bugs all in one place, at Github issues.
Github issues Information
We use Github issues for tracking of those things. You can get there via this link: https://github.com/openpetra/openpetra/issues
These issues are public, i.e. everyone with web access can get to it and see the Bugs.
- The fact that the issue tracking system for OpenPetra is public needs to be kept in mind when filing bugs or adding information and attachments and screenshots!
Before you record something you think is not working, or does not seem what you think it ought to do, or if the application issues an error dialog, please have a look if someone already posted a similar issue.
When you file bugs or request features please make sure that you are following our Mini-guide for Bug reporting!
Questions and Discussions
Questions and discussions should happen in the Forum. It can be found here: Developer Forum
Documentation
- Technical details of an implementation in OpenPetra should always be documented in this OpenPetra wiki.
- Do not use documents (of any file format) for documentation of technical details of an implementation in OpenPetra, because
- the wiki should be the single central source of information about OpenPetra
- documents in various file formats don't usually have a change history, but the wiki keeps track of the change history
- documents outside the wiki might become forgotten on the local machine of a developer (or on a network drive) and no-one else will have (easy) access to them
Contributing Code and Patches
See Submitting patches and features for more information.
Copyright of Contributions
We need to still discuss how we deal with the copyright of contributions. See also the discussion on this blog about copyright assignment.
Please let us know what you would prefer! OM is a charity, and it might be a good copyright holder to make relicensing easier. But if that is a big problem for you, please let us know, and we can discuss it.