[Sugar-devel] Adding committers on gitorious (was: Re: [PATCH] Remove nbsp chars from the html string before parsing)
tomeu at sugarlabs.org
Mon Aug 9 04:27:58 EDT 2010
On Mon, Aug 9, 2010 at 07:19, James Cameron <quozl at laptop.org> wrote:
> On Fri, Aug 06, 2010 at 09:05:24AM +0200, Tomeu Vizoso wrote:
>> On Fri, Aug 6, 2010 at 01:47, Marco Pesenti Gritti <marco at marcopg.org> wrote:
>> > On 6 Aug 2010, at 00:20, James Cameron <quozl at laptop.org> wrote:
>> >> On Thu, Aug 05, 2010 at 09:06:03AM +0200, Tomeu Vizoso wrote:
>> >>> Another option is having some script that adds committers to all sugar
>> >>> core modules in one go, that would be similar to what GNOME does.
>> >> There are too many core modules, in my opinion (and Michael Stone's). ?I
>> >> see no good reason why there isn't just one git repository for the
>> >> whole of Sugar.
>> > Yeah, I think we need to look into merging core in a single repository.
>> At the end it's basically the same problem we find again and again: we
>> spend days-person discussing some big changes, eventually may reach an
>> agreement (or not), then nobody finds time to actually do the work.
> Michael Stone did it. I tested it on an XO. It worked.
Our software doesn't get into hands of children in that way. It
requires the work of individuals such as Jonas, Peter, Aleksey and
many others and any discussion on such a change should have included
their point of view.
>> It happened with the code review process and I see very well it
>> happening here because it would require coordination with packagers,
>> updating lots of wiki pages, etc.
> Well, apart from the actual code and git repository changes, there's
> nothing obvious that needs fixing. It's the code that counts. I don't
> go looking for trouble in Wiki pages or packagers. Wiki pages that
> document code should be in the code repository, not in the Wiki.
> Packagers can be told what the changes are and they will adjust
Are you suggesting to just leave the wiki pointing to obsolete repos
because you personally don't care about any documentation that is in
the wiki? Guess not, but then I don't understand what you are
> You seem to think something else is required to complete this task, but
> I knew nothing of those things. Perhaps that is why things are not
Such a change requires that somebody presents a serious plan. As
things are now, as a maintainer I would need to do quite a bit of work
to make sure that the change can be made without serious negative
I appreciate that it's very important to make it easier to install our
development environment, but if you expect me to do that work now, you
are asking from me more than what I can give.
> James Cameron
More information about the Sugar-devel