[Sugar-devel] Bug tracking Vs Patch review

James Cameron quozl at laptop.org
Mon Aug 30 23:44:24 EDT 2010


On Mon, Aug 30, 2010 at 02:44:58PM +0200, Tomeu Vizoso wrote:
> Went through http://wiki.sugarlabs.org/go/0.88/Platform_Components and
> googled for how each project prefer patches to be submitted:
> 
> == Prefer a tracker ==
> 
> * http://www.gstreamer.net/wiki/SubmittingPatches
> * http://dbus.freedesktop.org/doc/dbus-faq.html#id305110
> * http://www.python.org/dev/patches/
> * http://live.gnome.org/Git/Developers#Contributing_patches
> * http://telepathy.freedesktop.org/wiki/Review%20Procedure
> * http://wiki.immuexa.com/display/sq/Starting+with+Etoys+Development#StartingwithEtoysDevelopment-stepstomakeachange
> * http://new.scipy.org/dev-zone.html#source-code
> 
> == Prefer a mailing list ==
> 
> * http://www.abisource.com/developers/
> * http://www.pygame.org/wiki/patchesandbugs
> 
> == Unknown ==
> 
> * eSpeak
> * csound
> * libffi

I don't think this is a valid comparison, because:

1.  these are the public statements intended to be read by non-core
developers, such as occasional contributors,

2.  some development would normally occur without following the public
statements.

What I think we are missing is the collaboration that I see on other
projects, where those who are in agreement with a patch either merge it
into their own trees or contribute to fixes within it.

-- 
James Cameron
http://quozl.linux.org.au/


More information about the Sugar-devel mailing list