[Sugar-devel] [IAEP] Development team mission
Wed Dec 3 06:49:42 EST 2008
On Mon, Dec 1, 2008 at 2:05 PM, Morgan Collett <morgan.collett at gmail.com> wrote:
> On Sat, Nov 29, 2008 at 16:08, Walter Bender <walter.bender at gmail.com> wrote:
>> You were quite articulate about this at Sugar Camp: An important part
>> of the mission is to make sure that the contributions come from
>> broadest base possible; that suggests that documentation is as
>> important as coding.
> Usually I've seen mission statements developed in conjunction with
> vision statements, with the vision being "Where are we going" and the
> mission being "How are we going to get there".
> What would the vision statement be for the development team? Something
> like "Sugar everywhere, easily modifiable by by all users, who can
> contribute their changes upstream, where a sustainable community of
> developers implement new features and maintain the upstream codebase"?
> The mission would then include something like "Develop new features,
> maintain the existing codebase, and lower the bar for community
> contributions through documentation and by soliciting, revewing and
> merging community contributions".
> I have focused more on the process than the desired end result: What
> Sugar ought to be. Perhaps that should be incorporated as well to
> guide what the new features should be...
I like both statements, but I'm a bit worried that most people won't
be able to understand what they mean because use concepts not
generally used in the wide societies.
How could we simplify them while retaining enough meaning?
>> On Sat, Nov 29, 2008 at 8:55 AM, Marco Pesenti Gritti
>> <marcopg at sugarlabs.org> wrote:
>>> I have not yet wrote down a mission for the development team. Part of
>>> that is laziness (sorry!), part is that I'm trying to figure out what
>>> exactly our mission should be.
>>> So far our focus has been on implementing as many features as possible
>>> and on fixing as many bugs as possible. I would like to refocus a bit
>>> and I have several ideas about which direction to move in... But
>>> before making a proposal I'd like to hear ideas and opinions from
>>> other team members and from the community as a whole.
>>> What should our mission be? How can we help Sugar Labs to survive and succeed?
>>> Thanks in advance for any feedback!
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>> Walter Bender
>> Sugar Labs
>> IAEP -- It's An Education Project (not a laptop project!)
>> IAEP at lists.sugarlabs.org
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
More information about the Sugar-devel