[Sugar-devel] core maintainers

[David Farning]

On Mon, Jun 21, 2010 at 6:59 AM, Martin Dengler
<martin at martindengler.com> wrote:
> On Mon, Jun 14, 2010 at 02:02:57PM -0500, David Farning wrote:
>> On Mon, Jun 14, 2010 at 12:36 PM, Tomeu Vizoso <tomeu at sugarlabs.org> wrote:
>> > On Fri, Jun 11, 2010 at 18:39, David Farning <dfarning at gmail.com> wrote:
>> >> Over the past couple of months it has appeared that the ramp up of
>> >> deployment submitted patches has stretched the core maintainers rather
>> >> short.
>> >>
>> >> I would like to consider having Deployment Support Network developers
>> >> start accepting additional maintainership responsibility and
>> >> authority.  Specifically, I am interested in which core activities are
>> >> in need of a maintainer and which core modules are up for adoption.
>> >>
>> >> With this information, I can start identifying and recruiting
>> >> potential maintainers.
>> >
>> > From my POV, in order of need/suitability:
>> >
>> > - Read
>> > - Write
>>
>> AC will accept responsibility for  Read and Write.
>
> Please update
> http://wiki.sugarlabs.org/go/Development_Team/Release/Modules then.
> It'd also be nice to know who the people are and why they are
> qualified (code patches seem a good way to do this, as implied by
> http://lists.sugarlabs.org/archive/sugar-devel/2010-June/024616.html
> ).

I apologize for my lack of clarity.  I have distinct definitions for
the terms responsibility and authority.

Responsibility means, "We will figure out how to provide the resources
necessary get the work done."

Authority for the activities still resides in the meritocracy of the
development team.  I expect that it will take weeks or even months
before the new developers earn the trust of the exiting developers to
become the official maintainers of the activities.

david