Summary of Projects: Difference between revisions
Line 8: | Line 8: | ||
For technical details of an implementation, we should document that in the wiki. | For technical details of an implementation, we should document that in the wiki. | ||
Only the core developers have write access to the Git code repository of OpenPetra at Sourceforge. For all other developers, it will be necessary to check out the Git repository anonymously, and then create a branch for yourself (see [[Notes about Git]]). | Only the core developers have write access to the Git code repository of OpenPetra at Sourceforge. For all other developers, it will be necessary to check out the Git repository anonymously, and then create a branch for yourself (see [[Notes about Git]]). Please see [[Submitting patches and features]] for submitting patches. | ||
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]. 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. | 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]. 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. |
Revision as of 09:02, 4 October 2010
Contributing code to OpenPetra.org
It is probably good to manage the projects, todo lists, feature requests, and bugs all in one place, also called a tracker. We use Mantis for that. A quick link is: http://tracker.openpetra.org
Everyone can report issues (we will revise that if the spam becomes too much...).
For discussion, it might be useful to have those discussions in the forum.
For technical details of an implementation, we should document that in the wiki.
Only the core developers have write access to the Git code repository of OpenPetra at Sourceforge. For all other developers, it will be necessary to check out the Git repository anonymously, and then create a branch for yourself (see Notes about Git). Please see Submitting patches and features for submitting patches.
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.
General list of things todo
Please have a look on the Mantis Tracker for all sorts of things that need to be done!
Projects to get started with OpenPetra.org
These are projects that might be easy for developers to get started with OpenPetra.org:
- Design some database diagrams: see also SQL Diagram creation
- Please also have a look at the old Petra 2.1 diagrams (download 9 png files in a zip file). The diagrams might need to be a bit smaller and more specific, otherwise they get too big and complicated.
- Caching datatables on the client in an SQLite db: Details in Tracker
- Create a WebMin Module for OpenPetra.org for the server running on Linux: Details in Tracker
- data liberation: Import/Export of data
High priority projects
- OpenPetra Installers
- Import sample partner data (names, addresses) (see Details in Tracker)
- Banking plugins
- Link to office applications
Non Programmer projects
There is also work that needs to be done, and can/should be done by people who are not programmers.
- Translation: see this article about HowTo help with Translation
- Design: we might need additional icons for the toolbar buttons etc., so let us know if you are gifted in that area and want to help us.