[IAEP] SoaS as a Sugar Labs project.

Bernie Innocenti bernie at codewiz.org
Fri Aug 28 12:05:36 EDT 2009

El Fri, 28-08-2009 a las 09:50 +0200, Martin Langhoff escribió:
> On Fri, Aug 28, 2009 at 9:32 AM, Bernie Innocenti<bernie at codewiz.org> wrote:
> > +1.  And after dinner we could get a laptop and write down some notes on
> > workable management practices for blessed projects like SoaS.
> Get onto some coding -- it's more fun and productive than policy-ing :-)

You know how I'm all for a loosely managed community with low entry
barriers, informal rules and few policies, don't you?  In another life,
I was a manager, and ran away from it because it wasn't nearly as much
fun as real hacking for me.

Though, Michael proposed that traditional management practices might
increase our productivity.  It seems that David's idea of borrowing the
concept of projects from Apache and Eclipse would be a wonderful
opportunity to test Michael's proposal in practice:

--------- Mensaje reenviado --------
De: David Farning <dfarning at sugarlabs.org>
Para: Bernie Innocenti <bernie at codewiz.org>
Cc: Michael Stone <michael at laptop.org>, iaep <iaep at lists.sugarlabs.org>
Asunto: Re: [IAEP] SoaS as a Sugar Labs project.
Fecha: Sun, 23 Aug 2009 16:22:07 -0500


Bernie, would you be interested in creating the project policy for
Sugar Labs?  There is a very good page at
http://wiki.eclipse.org/Development_Resources . The 'Leads: Managing A
Project' and guidelines sections are very valuable.

If I were to work on the policy I would:
1. Take the Eclipse and Apache policies and strip them down to the bare minum.
2. Combine the Eclipse and Apache policies and modify them for Sugar Labs.
3. Identify two initial projects and make sure the policies work for
both of them.
4. Present the project policy for feedback on iaep.
5. Post the draft policy to the wiki

Something as significant as a project-policy will likely take several
iterations through 1-5.


More information about the IAEP mailing list