Pylons Project projects follow acoding style with minimum standards. All substantive code contributions to the Pylons Project must be tested. SeeUnit Testing Guidelines. Documentation contributions should follow thePylons Project Documentation Style Guide.
For substantive contributions to its major projects, The Pylons Project requires the following of its contributors:
"Signing" a contribution agreement is simple: just add your name and a date to the bottom of a "CONTRIBUTORS" file found in the root of the Pylons Project project to which you would like to contribute. Optimally, this will be done when you submit code through GitHub (whether via a pull request from a separate repository fork, or by direct push if you have push access to the canonical project repository). Your intent to abide by the contributor agreement is signified by your commit to the "CONTRIBUTORS.md" file with your name and a date.
Examples of "substantive" contributions:
For bugfixes and other minor contributions, signing the contributor file is usually not required. However, the reviewer of a particular submission is the arbiter of whether that submission requires the signing of the contributors file.
A sample of the current contributor agreement is reproduced in full below:
Pylons Project Contributor Agreement====================================The submitter agrees by adding his or her name within the section belownamed "Contributors" and submitting the resulting modified document tothe canonical shared repository location for this software project(whether directly, as a user with "direct commit access", or via a "pullrequest"), he or she is signing a contract electronically. The submitterbecomes a Contributor after a) he or she signs this document by addingtheir name beneath the "Contributors" section below, and b) the resultingdocument is accepted into the canonical version control repository.Treatment of Account---------------------Contributor will not allow anyone other than the Contributor to use hisor her username or source repository login to submit code to a PylonsProject source repository. Should Contributor become aware of any suchuse, Contributor will immediately notify Agendaless Consulting.Notification must be performed by sending an email towebmaster@agendaless.com. Until such notice is received, Contributorwill be presumed to have taken all actions made through Contributor'saccount. If the Contributor has direct commit access, AgendalessConsulting will have complete control and discretion over capabilitiesassigned to Contributor's account, and may disable Contributor's accountfor any reason at any time.Legal Effect of Contribution----------------------------Upon submitting a change or new work to a Pylons Project sourceRepository (a "Contribution"), you agree to assign, and hereby do assign,a one-half interest of all right, title and interest in and to copyrightand other intellectual property rights with respect to your new andoriginal portions of the Contribution to Agendaless Consulting. You andAgendaless Consulting each agree that the other shall be free to exerciseany and all exclusive rights in and to the Contribution, withoutaccounting to one another, including without limitation, the right tolicense the Contribution to others under the Repoze Public License. Thisagreement shall run with title to the Contribution. Agendaless Consultingdoes not convey to you any right, title or interest in or to the Programor such portions of the Contribution that were taken from theProgram. Your transmission of a submission to the Pylons Project sourceRepository and marks of identification concerning the Contribution itselfconstitute your intent to contribute and your assignment of the work inaccordance with the provisions of this Agreement.License Terms-------------Code committed to the Pylons Project source repository (Committed Code)must be governed by the Repoze Public License(http://repoze.org/LICENSE.txt, aka "the RPL") or another licenseacceptable to Agendaless Consulting. Until Agendaless Consultingdeclares in writing an acceptable license other than the RPL, only theRPL shall be used. A list of exceptions is detailed within the"Licensing Exceptions" section of this document, if one exists.Representations, Warranty, and Indemnification----------------------------------------------Contributor represents and warrants that the Committed Code does notviolate the rights of any person or entity, and that the Contributor haslegal authority to enter into this Agreement and legal authority overContributed Code. Further, Contributor indemnifies Agendaless Consultingagainst violations.Cryptography------------Contributor understands that cryptographic code may be subject togovernment regulations with which Agendaless Consulting and/or entitiesusing Committed Code must comply. Any code which contains any of theitems listed below must not be checked-in until Agendaless Consultingstaff has been notified and has approved such contribution in writing.- Cryptographic capabilities or features- Calls to cryptographic features- User interface elements which provide context relating to cryptography- Code which may, under casual inspection, appear to be cryptographic.Notices-------Contributor confirms that any notices required will be included in anyCommitted Code.Licensing Exceptions====================NoneList of Contributors====================The below-signed are contributors to a code repository that is part ofthe project named "XXX". Each below-signed contributor has read,understand and agrees to the terms above in the section within thisdocument entitled "Pylons Project Contributor Agreement" as of the datebeside his or her name.Contributors------------- Wile E. Coyote, 2010/11/08