| 1 |
On Thu, Jan 16, 2014 at 8:20 AM, Alexander Berntsen <alexander@××××××.net>wrote: |
| 2 |
|
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA256 |
| 5 |
> |
| 6 |
> We have quite a few dedicated developers now. To ensure that good |
| 7 |
> taste is exercised, and that best practices are followed, patches |
| 8 |
> should be signed. |
| 9 |
> |
| 10 |
> My proposals: |
| 11 |
> Signed-off-by: Wrote (a substantial portion of) the patch |
| 12 |
> Reviewed-by: Reviewed the patch thoroughly |
| 13 |
> Tested-by: Tested the patch thoroughly |
| 14 |
> Acked-by: Approved the concept but did not read the patch in detail |
| 15 |
> (typically used by the maintainer of a specific portion, or our lead) |
| 16 |
> Suggested-by: Designed the implementation |
| 17 |
> Reported-by: Reported the bug/feature request |
| 18 |
> |
| 19 |
> These suggestions all stem from the Linux project. |
| 20 |
> - -- |
| 21 |
> Alexander |
| 22 |
> alexander@××××××.net |
| 23 |
> http://plaimi.net/~alexander |
| 24 |
> -----BEGIN PGP SIGNATURE----- |
| 25 |
> Version: GnuPG v2.0.22 (GNU/Linux) |
| 26 |
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 27 |
> |
| 28 |
> iF4EAREIAAYFAlLX3JsACgkQRtClrXBQc7VhEQD9FKmFbyf9zxl+hLylkhQN/kv6 |
| 29 |
> o3DSM4xBr9fH4+1eokYA/3MbFLtDpli311d6ZqGD17kGLfz5wNj+5kPRATbiC256 |
| 30 |
> =cJNe |
| 31 |
> -----END PGP SIGNATURE----- |
| 32 |
> |
| 33 |
> |
| 34 |
So, how would this work with emails to this list, exactly? An email should |
| 35 |
be sent any time one of those fields is changed? |
| 36 |
I think that would be overkill in our specific context. That makes much |
| 37 |
more sense if we had a CR tool, where changes to a patch could be seen in |
| 38 |
one place, and email passes to be only a 'notification tool'. |
| 39 |
|
| 40 |
Do you have a more detailed plan on how would this work? |
| 41 |
|
| 42 |
Cheers, |
| 43 |
|
| 44 |
-- |
| 45 |
Jesus Rivero (Neurogeek) |
| 46 |
Gentoo Developer |
Archives