Changeset 663 for branches/PublicaMundi_David-devel/docs/contribute
- Timestamp:
- Jun 16, 2015, 11:59:50 AM (10 years ago)
- Location:
- branches/PublicaMundi_David-devel/docs/contribute
- Files:
-
- 1 added
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/PublicaMundi_David-devel/docs/contribute/code.rst
r659 r663 1 .. _contribute_code: 2 1 3 Contribute code 2 4 =============== 3 5 4 Anybody is welcome to share and contribute ideas, code, documentation or any relevant resource 5 using the following media. 6 Anybody is welcome to share source code and to report bugs or feature requests using the following instructions. 6 7 7 8 Submit new code 8 9 -------------------------- 9 10 11 For new comers 12 ************************* 10 13 11 Report a code issue 14 New source code or existing source code corrections (patches) should be submitted using the ZOO-Project bug tracking system (ZOO-Trac). 15 16 Create a new ticket in order to describe your code or patch and attach it to the ticket (attach all the needed files needed to use your code or patch). It will then be checked and discussed with the developers, and can potentially be merged with the trunk. 17 18 For registered developers 19 *************************** 20 21 ZOO-Project registered developers have direct svn access and can: 22 23 * Commit fixes, enhancement and new source directly to trunk 24 25 * Create and commit to a new branch of the svn 26 27 Bug tracking 12 28 -------------------------- 13 29 30 General information 31 ********************* 14 32 33 Bug reports and wishes can be submitted using the ZOO-Trac. This requires you to setup a user account (userid) using this section. 34 35 The following trackers are available: 36 37 * *defects* to report bugs and 'bad' features 38 * *enhancement* to describe feature wishes 39 * *task* to describe any different but relevant topic. 40 41 The following components are available: 42 43 * *Developemnt platform* to report bugs and 'bad' features 44 * *ZOO-Kernel* to report a bug or problem with the ZOO-Project WPS server 45 * *ZOO-Services* to report a bug or problem with the ZOO-Project WPS services 46 * *ZOO-API* to report a bug or problem with the ZOO-Project API 47 * *ZOO-Client* to report a bug or problem with the ZOO-Project Client 48 * *Documentation* to report a problem or suggest an enhancement to the documentation 49 50 Best practices 51 ********************* 52 53 Please consider the following when submitting bugs or feature requests: 54 55 * Check if the bug is still persistent in svn trunk before reporting. If you use an older version, please consider upgrading. 56 * Before reporting a bug, please search if it is yet unknown in the bug tracking system. 57 * Give an appropriate, starightforward and understandable title to your ticket using the *Summary* field 58 * Make sure the developers get all the needed information to recreate the bug using the *Description* field (e.g. tell about your configuration and explain every step to reproduce the bug). 59 * Select at least a *Type* of tracker and a *Component* for your new ticket. 60 * Report only one single bug by ticket. 61 62 -
branches/PublicaMundi_David-devel/docs/contribute/howto.rst
r659 r663 2 2 ================== 3 3 4 Please consider the following simple rules if you would like to 5 contribute to `ZOO-Project <http://zoo-project.org>`__ . 6 4 Please consider the following simple rules if you would like to contribute to the `ZOO-Project <http://zoo-project.org>`__ open source software. 7 5 8 6 Community 9 7 ------------------- 10 8 11 Anybody is welcome to share and contribute ideas, code, documentation 12 or any relevant resource. This should be done according to the directives stated in the ZOO-Project :ref:`contribute_index`. 9 Anybody is welcome to share and contribute ideas, code, documentation or any relevant resource. This should be done according to the directives stated in the ZOO-Project :ref:`contribute_index`. 10 11 Governance 12 ...................................... 13 14 `ZOO-Project <http://zoo-project.org>`__ activities are directed by the Project Steering Committee (PSC) and the software itself is being developed, maintained and documented by an international community of users and developers (aka `ZOO-Tribe <http://zoo-project.org/new/ZOO-Project/ZOO%20Tribe>`_). 15 16 Contributions are moderated and integrated in trunk at the discretion of the `ZOO-Project <http://zoo-project.org>`__ PSC. Commit access are usually granted to active contributors by vote from the PSC members. 13 17 14 18 Licensing 15 19 ...................................... 16 20 17 `ZOO-Project <http://zoo-project.org>`__ source code is open source and 18 made available under the `MIT/X-11 19 <http://opensource.org/licenses/MITlicense>`__ `license 20 <http://zoo-project.org/trac/browser/trunk/zoo-project/LICENSE>`__. You 21 must agree to the terms of that same license when creating, submiting 22 and releasing new source code. 21 `ZOO-Project <http://zoo-project.org>`__ source code is open source and made available under the `MIT/X-11 <http://opensource.org/licenses/MITlicense>`__ `license 22 <http://zoo-project.org/trac/browser/trunk/zoo-project/LICENSE>`__. You must agree to the terms of that same license when creating, submiting and releasing new source code. 23 23 24 `ZOO-Project <http://zoo-project.org>`__ documentation is open source and 25 made available under the `Creative Commons Attribution-ShareAlike 4.0 International Public License 26 <https://creativecommons.org/licenses/by-sa/4.0/legalcode>`__ . You 27 must agree to the terms of that same license when creating, submiting 28 and releasing a new documentation file. 29 30 31 Governance 32 ...................................... 33 34 24 `ZOO-Project <http://zoo-project.org>`__ documentation is open source and made available under the `Creative Commons Attribution-ShareAlike 4.0 International Public License 25 <https://creativecommons.org/licenses/by-sa/4.0/legalcode>`__ . You must agree to the terms of that same license when creating, submiting and releasing a new documentation file. 35 26 36 27 Available media 37 28 ------------------- 38 29 39 Discussions and contributions are encouraged using the following media30 Discussions and contributions to `ZOO-Project <http://zoo-project.org>`__ are encouraged using the following public media. 40 31 41 32 Mailing lists 42 33 ...................................... 43 34 44 Post any feedback, comment or idea to the general public mailing 45 list. For project managment or governance topics, use the PSC list. 35 Feel free to post any question, feedback, comment or idea to the general public mailing list. For project managment or governance topics, please use the PSC list. 46 36 47 37 .. csv-table:: … … 55 45 ...................................... 56 46 57 Join #zoo-project channel on irc.freenode.net to discuss with the ZOO-Tribe47 Join the **#zoo-project** channel on irc.freenode.net to discuss with the ZOO-Tribe at any time. 58 48 59 49 60 Tracker and wiki50 Tracker 61 51 ...................................... 62 52 63 Contributions and bug reports should be shared using the `ZOO-Project 64 <http://zoo-project.org>`__ bug tracking system, as specified in the 65 :ref:`contribute-code` section. Wiki pages can also be created to 66 describe contributions and or actions. 53 Bug reports and code patches should be shared using the `ZOO-Project <http://zoo-project.org>`__ bug tracking system, as specified in the :ref:`contribute-code` section. 54 55 Wiki 56 ...................................... 57 58 Wiki pages can also be created by registered users. They can be used in order to describe any concept, contribution and or action that benefits or is related to the project. -
branches/PublicaMundi_David-devel/docs/contribute/index.rst
r659 r663 15 15 howto 16 16 code 17 doc
Note: See TracChangeset
for help on using the changeset viewer.