13 |
|
|
14 |
Maintainers (w/ write privs) indicate ownership by `[USERNAME]'. |
Maintainers (w/ write privs) indicate ownership by `[USERNAME]'. |
15 |
Use `[ACTUAL-OWNER:MAINTAINER]' to indicate sponsorship, where |
Use `[ACTUAL-OWNER:MAINTAINER]' to indicate sponsorship, where |
16 |
both elements are usernames. |
both elements are usernames. Actually, sponsorship is a form of |
17 |
|
review so MAINTAINER could be the start of a list of REVIEWERs, |
18 |
|
using ":" to separate. |
19 |
|
|
20 |
Upon completion, simply change the "-" to a "+", but do not |
Upon completion, simply change the "-" to a "+", but do not |
21 |
delete the item. At release time, the "+" entries will be |
delete the item. At release time, the "+" entries will be |
55 |
[Probably after some discussion this section can be written.] |
[Probably after some discussion this section can be written.] |
56 |
|
|
57 |
|
|
58 |
|
Requesting Review |
59 |
|
|
60 |
|
Sometimes after a change you'd like someone else to review your |
61 |
|
work for whatever reason. Use the "R" flag to indicate this. |
62 |
|
The reviewer appends :REVIEWER to yours, and after the review |
63 |
|
either removes the "R" if everything's ok, or leaves it there, |
64 |
|
indicating further review requested. |
65 |
|
|
66 |
|
It's a good idea to get something out of the review more than |
67 |
|
mere approval. "Peer review process" means different things to |
68 |
|
everyone, however, so try to cut slack in both directions. |
69 |
|
|
70 |
|
|
71 |
Individual TODO Files |
Individual TODO Files |
72 |
|
|
73 |
Feel free to keep individual todo files either in this directory |
Feel free to keep individual todo files either in this directory |