[Sugar-devel] Code Review process changes
dfarning at gmail.com
Tue May 4 09:34:12 EDT 2010
I have been trying to keep quite about this until we have had results
flowing in.... Over the past couple of months Bernie, Caroline, and I
have been looking at businesses around Sugar and OLPC. One of the
ideas that we are exploring is service and support for deployments.
As such, we are contracting developers to fix specific bugs that
deployments hire us to fix or issues that Bernie identifies as high
priority at the deployment in Paraguay. There are several
organizations and companies already working in this field. The key
difference between our company and others, in the field, is that our
issues are not considered _complete_ until 1) the fix the customer's
problem and 2) the fixes have been accepted upstream by Sugar Labs,
OLPC, or Debian.
I don't understand the pros and cons of the various of maintainer
workflows to have a opinion. I would like to inform the community
1) You will be seeing a continued increase of deployment related bug fixes.
2) As these new developers become more experienced I will be happy to
fund them to to maintain portions of Sugar.
On Tue, May 4, 2010 at 2:13 AM, Simon Schampijer <simon at schampijer.de> wrote:
> Sorry for being late in the discussion, just a few words from a Sugar
> module maintainer's point of few.
> I don't think the tool we used was the bottleneck. Of course there could
> have been some enhancements (like reminders to the ml), but in general
> it was ok. I personally had just too many things to do, Feature process,
> Release process etc. So we are in need of more man power, like laid out
> here several times. Mainly people taking responsibilities. I don't think
> we want to cut away the maintainers, this is important to keep the
> quality high.
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel