On Thu, Jan 16, 2014 at 8:20 AM, Alexander Berntsen <alexander@plaimi.net> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

We have quite a few dedicated developers now. To ensure that good
taste is exercised, and that best practices are followed, patches
should be signed.

My proposals:
Signed-off-by: Wrote (a substantial portion of) the patch
Reviewed-by: Reviewed the patch thoroughly
Tested-by: Tested the patch thoroughly
Acked-by: Approved the concept but did not read the patch in detail
(typically used by the maintainer of a specific portion, or our lead)
Suggested-by: Designed the implementation
Reported-by: Reported the bug/feature request

These suggestions all stem from the Linux project.
- --
Alexander
alexander@plaimi.net
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlLX3JsACgkQRtClrXBQc7VhEQD9FKmFbyf9zxl+hLylkhQN/kv6
o3DSM4xBr9fH4+1eokYA/3MbFLtDpli311d6ZqGD17kGLfz5wNj+5kPRATbiC256
=cJNe
-----END PGP SIGNATURE-----

So, how would this work with emails to this list, exactly? An email should be sent any time one of those fields is changed?

I think that would be overkill in our specific context. That makes much more sense if we had a CR tool, where changes to a patch could be seen in one place, and email passes to be only a 'notification tool'.

Do you have a more detailed plan on how would this work?

Cheers,

--
Jesus Rivero (Neurogeek)
Gentoo Developer