[Sugar-devel] [PATCH sugar-toolkit-gtk3] Add MAINTAINERS file

[Chris Leonard]

On Sat, Dec 17, 2011 at 7:42 PM, Bernie Innocenti <bernie at codewiz.org> wrote:
>> Great. Can we do the same for all modules?
>
> I mean: replacing the MAINTAINERS file with a simple link to the wiki
> page.
>
> Looking at the wiki page, I just noticed that sugar-toolkit-gtk3 is
> maintained by you and Simon, which makes it different from all the other
> modules.
>
> Presently it doesn't really matter, but when the rest of glucose
> switches to gtk3, this arrangement would bring us back to the time when
> getting any non-trivial change merged required seeking the combined
> approval of multiple module maintainers.
>
> So I'd propose that we continue to have glucose share the same set
> maintainers, either by making Silbe co-maintain sugar-toolkit-gtk3, or
> by adding you to the other glucose modules. I think it's important to
> keep our review process smooth and avoid frustrating our contributors
> with patches stuck in a half-approved state.

While we have all have been indoctrinated with the concept of
"least-required-privilege" as a security principle, we are also a FOSS
a project that like others, grants privileges on the basis of trust,
backed by reputation capital as collateral.

In this case, I would go with the easiest technical workaround to keep
the patches flowing.  All three maintainers (silbe, erikos, dsd) of
the various Sugar core components have more than adequate reputation
capital to support entrusting them with privs on any and all modules.
The arrangements made amongst themselves (and described to this list)
to divide the work need not be strictly regulated by access control
methods.  It is my opinion that some redundancy of privileges is
actually desirable as long as the social contract they have reached on
"primary" control of modules is respected, and I have no doubts that
it would be.

We should probably make sure that the wiki page is wiki-admin edit only.

Just my two cents,

cjl