How we handle patches (mmoved): Difference between revisions
Content added Content deleted
imported>Paulproteus No edit summary |
imported>Ehashman No edit summary |
||
| (29 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
{{Hacking OpenHatch}} |
{{Hacking OpenHatch}} |
||
== As a patch submitter == |
|||
We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org [http://openhatch.readthedocs.org/en/latest/getting_started/handling_contributions.html Handling contributions] |
|||
* File a bug on https://openhatch.org/bugs/ with a link to your code (for example, a git repository somewhere on the Internet, or with patch files as attachments in bug itself) |
|||
** Read about [[How to generate patches with git format-patch]] |
|||
* Join IRC and ping someone with deployment access (e.g., ''paulproteus'') until it gets reviewed |
|||
* If it passes review, it should get deployed immediately. |
|||
== As a reviewer == |
|||
* Ping the author on IRC (or something) to see if she's/he's uploaded the most recent version. |
|||
* Ask the author to do this: "Please email devel@lists.openhatch.org saying that you're okay with your work being under AGPLv3. If you're willing, it'd be nice if you say 'the Affero GPL, version 3 or later, at your option'." |
|||
Latest revision as of 16:30, 25 August 2014
This is a page about improving or modifying OpenHatch.
We call that "Hacking OpenHatch," and there is a whole category of pages about that.
We are updating our documentation system. This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org Handling contributions