To be fair, we discussed a few times write a policy about what to do in
these cases,
but never agreed in the terms. In particular how much time we should wait.
Other projects call MIA (missing in action) the situation, but we proposed
something less dramatic :)
Gonzalo
On Tue, Feb 24, 2015 at
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
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 qu...@laptop.org wrote:
Concerning to lose contributions just because a maintainer takes a
break. What if a
I was reviewing patches for Calculate recently.
Our most recent repository is here
https://github.com/godiard/sugarlabs-calculate
I approved the bugs opened now
Gonzalo
On Thu, Feb 19, 2015 at 12:15 PM, Walter Bender walter.ben...@gmail.com
wrote:
The maintainer has been away for the past two
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@lists.sugarlabs.org
Forwarding to the development team.
On 17/02/15 20:52, Alexandra Castelli wrote:
Hello!
We have a team that is trying to contribute to the Sugar Calculate
activity. If this email is not directed to the correct person, would you
mind pointing me in the right direction?
We submitted a bug
The maintainer has been away for the past two weeks. He is back on
line now, so I suspect you'll hear back from him soon.
regards.
-walter
On Thu, Feb 19, 2015 at 10:06 AM, Bernie Innocenti ber...@codewiz.org wrote:
Forwarding to the development team.
On 17/02/15 20:52, Alexandra Castelli
7 matches
Mail list logo