On Fri, Aug 06, 2010 at 09:05:24AM +0200, Tomeu Vizoso wrote: > On Fri, Aug 6, 2010 at 01:47, Marco Pesenti Gritti <ma...@marcopg.org> wrote: > > On 6 Aug 2010, at 00:20, James Cameron <qu...@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. > 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 wonderfully. 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 completed? -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
