Commit eccfde38 authored by Tails developers's avatar Tails developers
Browse files

Move the notes about "patch'n'forget" contributors to the review process doc.

These notes are actually useful for reviewers, more than for code contributors.
parent e1b115b6
......@@ -18,10 +18,6 @@ page documents both.</p>
[[!inline pages="contribute/merge_policy/common_rules" raw=yes]]
# Newcomer / patch'n'forget contributor
[[!inline pages="contribute/merge_policy/newcomer" raw=yes]]
# Core developer
[[!inline pages="contribute/merge_policy/coredev" raw=yes]]
......
[[!meta title="Git merge policy: newcomer / patch'n'forget contributor"]]
## Pull once in *good enough* state
Changes proposed by new contributors, or by the patch'n'forget kind,
shall respectively be applied once they are in *good enough* state.
That is, once the core developers team feels like maintaining it on
the long run in case the initial submitter disappears. Such
maintenance includes: polishing the proposed changes to make them fit
for release; writing and updating the design and end-user
documentations; fixing bugs.
......@@ -10,6 +10,13 @@
`ssh reprepro@incoming.deb.tails.boum.org reprepro list [bugfix|feature]-<name-with-dashes>`
- Check the user and design documentation.
- Check the ticket.
- Changes proposed by new contributors, or by the patch'n'forget kind,
shall respectively be applied once they are in *good enough* state.
That is, once the core developers team feels like maintaining it on
the long run in case the initial submitter disappears. Such
maintenance includes: polishing the proposed changes to make them fit
for release; writing and updating the design and end-user
documentations; fixing bugs.
## Merge
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment