[Sugar-devel] Eliminate Glucose co-maintainers

Martin Dengler martin at martindengler.com
Sun Nov 21 21:04:45 EST 2010


I propose we eliminate "co-maintainers" from Glucose[1] because they
reduce the responsibility and pressure of a sole maintainer.

Recall that the role of maintainer is:

a) accept features [2]
b) accept patches [3]
c) make releases [4]

Having more than one person making these decisions risks reducing the
responsibility of the sole maintainer to maintain a quality release.
Essentially, it's too easy to leave maintainer work if you think
someone else could be helping you.

Thoughts?

Martin

Footnotes: 
[1]  http://wiki.sugarlabs.org/go/Development_Team/Release/Modules#Glucose

[2]  http://wiki.sugarlabs.org/go/Features/Policy#Roles

[3]  "accepting patches is a maintainer matter" http://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Log-2009-11-20

[4]  http://wiki.sugarlabs.org/go/Development_Team/Release#Module_release
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20101122/859b057f/attachment.pgp>


More information about the Sugar-devel mailing list