How we handle patches (mmoved): Difference between revisions
Content added Content deleted
No edit summary |
|||
| Line 2: | Line 2: | ||
* 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) |
* 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 |
* Join IRC and ping someone with deployment access (e.g., ''paulproteus'') until it gets reviewed |
||
* If it passes review, it should get deployed immediately. |
* If it passes review, it should get deployed immediately. |
||
Revision as of 19:04, 30 September 2010
As a patch submitter
- 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)
- 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'."