[Sugar-devel] Sugar Contribution

[Walter Bender]

Catching up on some old threads.

James, we have procedures in place for transferring maintenance and
have invoked these procedures on occasion. Essentially it entails
contacting the maintainer and after a timeout, making a clone of the
project. Since we know most of the maintainers, we don't get surprised
too often. Note that in the case that triggered this thread, the
contributor got almost immediate feedback from community members once
the issue was brought to the attention of the community (10 minutes).
Not sure we can do better than that.

regards.

-walter

On Sat, Feb 21, 2015 at 3:29 PM, Gonzalo Odiard <godiard at sugarlabs.org> wrote:
> That already happened... and happen on every open source project,
> what is the question? Is about if we have a procedure?
>
> Gonzalo
>
> On Thu, Feb 19, 2015 at 6:24 PM, James Cameron <quozl at laptop.org> wrote:
>>
>> Concerning to lose contributions just because a maintainer takes a
>> break.  What if a maintainer goes missing?
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
>
> --
> Gonzalo Odiard
>
> SugarLabs - Software for children learning
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org