[Sugar-devel] Bug tracking Vs Patch review

Bernie Innocenti bernie at codewiz.org
Fri Sep 3 08:07:56 EDT 2010

El Fri, 03-09-2010 a las 04:46 +0100, Marco Pesenti Gritti escribió:

> Sounds good to me. I would put the notes somewhere on the wiki as
> experimental/unofficial so that we can integrate improvements. 

Done: http://wiki.sugarlabs.org/go/Talk:Development_Team/Code_Review

> > It's a useful aid on the side, but I don't think it needs to get in the
> > middle of the patch workflow. People are generally good at keeping track
> > of threads in mailing list within their MUA.

> Some people are, some are less, included our most active maintainer :)
> I think we agree about patchwork being an additional tool anyway.

Sure, let me know if the current service works well enough, or if you'd
like me to configure it differently. Anyone who would like admin
privileges for the web administration interface and access to the
codebase on sunjammer, just ping one of us sysadmins on #sugar.

> This is a bit simplistic. The submitter might just think we don't care
> and stop submitting patches.  Let's forget about that for now though,
> we need to make this work well for the existing contributors before we
> even start thinking about involving more.

Fair enough. These social dynamics are complex even when all
contributors share the same culture. Let's promote an attitude of
violen^W friendliness towards new contributors, especially those
unfamiliar with the engagement rules of FLOSS projects.

   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

More information about the Sugar-devel mailing list