On Fri, Jul 3, 2009 at 19:00, Frederick Grose<fgr...@gmail.com> wrote:
>
> On Fri, Jul 3, 2009 at 9:27 AM, Tomeu Vizoso <to...@sugarlabs.org> wrote:
>>
>> 2009/7/2 Sean DALY <sdaly...@gmail.com>:
>> > I don't know Tomeu, what do you think?
>>
>> I sincerely don't know but I hope that someone will explain what they
>> need from the development team to succeed.
>
> The idea is that *all* of Sugar Labs needs to think deeply about how we
> develop the next stage of Sugar and Sugar Labs.  What is most important to
> refine and advance, and what important pieces need to be added.
>
> This seems to be a followup to the call for *Champions* to advocate for the
> features needed to better serve our communities.  Champions that can
> integrate with the Design, Development, Activity, Education, Deployment,
> Marketing, and other Teams.
>
> For example, see this discussion thread on the 'netbook' as terminology,
> http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg05906.html,
> and the suggestion to push ad-hoc wireless networking into a native feature
> of Sugar.  This would give Sugar a large, advantageous multiplier effect for
> creating more pervasive networking to take advantage of our core feature,
> collaboration.
>
> Powerful ideas please step forward...

That's a good example, someone (several people?) have expressed in the
past that creating ad-hoc networks would be of great value, and at
some point I found some time and implemented it.

Development being driven by the development team doesn't mean that
only gets done what fancies us, we are always asking for feedback and
can be convinced to spend our time on other people's ideas.

Regards,

Tomeu

>            --Fred
>
>
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> i...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Reply via email to