Differences
This shows you the differences between two versions of the page.
|
contributing [2012/05/16 10:11] erickson [Submitting code to the project] |
contributing [2012/11/12 11:23] (current) rjs7 [Procedures and conventions for contributing to the Evergreen project] Remove extra space |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| A major goal of the Evergreen ILS Project is to become a long term, sustainable, community driven development effort. As such, it is necessary to define in concrete terms the acceptable procedures by which one can contribute to the overall improvement of Evergreen. There are many ways in which one can contribute, including, but not limited to, QA, bug fixes, code clean up, new features, enhancements to existing features, entirely new subsystems, end user documentation, technical documentation and translation/internationalization. All of these efforts are important for the ongoing success of the project, and none are any more important than the others for the long term success of Evergreen as a whole. The overarching goal of these procedures is to facilitate as much communication as possible among community members, and that communication occur early and often during the development process. It is the opinion of the original core development team that this communication is absolutely key to our continued success. | A major goal of the Evergreen ILS Project is to become a long term, sustainable, community driven development effort. As such, it is necessary to define in concrete terms the acceptable procedures by which one can contribute to the overall improvement of Evergreen. There are many ways in which one can contribute, including, but not limited to, QA, bug fixes, code clean up, new features, enhancements to existing features, entirely new subsystems, end user documentation, technical documentation and translation/internationalization. All of these efforts are important for the ongoing success of the project, and none are any more important than the others for the long term success of Evergreen as a whole. The overarching goal of these procedures is to facilitate as much communication as possible among community members, and that communication occur early and often during the development process. It is the opinion of the original core development team that this communication is absolutely key to our continued success. | ||
| - | This is a living document. It is meant to provide the reader, and potential contributor, with a set of clear guidelines that will help the contributor usher new material through the community process in an efficient manner . It is not meant to create undue roadblocks to any individual or set of potential contributors. If defects or inefficiencies in this process are identified and brought to the attention of the community to be addressed, then this set of guidelines may be amended from time to time. Nothing is written in stone. | + | This is a living document. It is meant to provide the reader, and potential contributor, with a set of clear guidelines that will help the contributor usher new material through the community process in an efficient manner. It is not meant to create undue roadblocks to any individual or set of potential contributors. If defects or inefficiencies in this process are identified and brought to the attention of the community to be addressed, then this set of guidelines may be amended from time to time. Nothing is written in stone. |
| - | Throughout this document you will see references to the "core team" or "committers". This is the group of Evergreen developers that have Subversion commit privileges, and are responsible for integrating code contributions directly into the source of Evergreen. To see a list of these core committers, go to the [[contributing:contributors|contributors]] page. From time to time, and as individual community members become more familiar and skilled with the complete codebase of Evergreen, some individuals may be asked to join the core team. We see this as both an honor and a responsibility, as this group is charged with being the final quality control mechanism for the source code, as well as helping other less experienced community members come up to speed. It is not simply a way to get code into Subversion, but also about mentoring new contributors and helping to keep the overall vision of the project in focus, tempered by the history and evolution of the code and lessons learned from past successes and failures. | + | Throughout this document you will see references to the "core team" or "committers". This is the group of Evergreen developers that have git commit privileges, and are responsible for integrating code contributions directly into the source of Evergreen. To see a list of these core committers, go to the [[contributing:contributors|contributors]] page. From time to time, and as individual community members become more familiar and skilled with the complete codebase of Evergreen, some individuals may be asked to join the core team. We see this as both an honor and a responsibility, as this group is charged with being the final quality control mechanism for the source code, as well as helping other less experienced community members come up to speed. It is not simply a way to get code into the git repository, but also about mentoring new contributors and helping to keep the overall vision of the project in focus, tempered by the history and evolution of the code and lessons learned from past successes and failures. |
| ===== Before you contribute ===== | ===== Before you contribute ===== | ||
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
