I for one would love to learn a new way to hack on my sugar and easily share patches. <br>If we can do better than jhbuild does (user experience wise), I would love it!<br><br>Icarito<br><br><div class="gmail_quote">2009/12/14 Tomeu Vizoso <span dir="ltr"><<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>></span><br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On Mon, Dec 14, 2009 at 17:01, Aleksey Lim <<a href="mailto:alsroot@member.fsf.org">alsroot@member.fsf.org</a>> wrote:<br> > On Mon, Dec 14, 2009 at 04:19:51PM -0200, Tomeu Vizoso wrote:<br> >> On Mon, Dec 14, 2009 at 11:25, Benjamin M. Schwartz<br> >> <<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote:<br> >> > Aleksey Lim wrote:<br> >> >> So, I have<br> >> >> strong intension to switching development focus from core team,<br> >> >> which develops sucrose - glucose(core) and fructose(some core<br> >> >> activities) to wide range of developers/doers thus some kind of<br> >> >> decentralization of development process.<br> >> ><br> >> > I agree. I think this has been a central part of the Sugar design<br> >> > philosophy from the beginning. I think your message is very much on the<br> >> > right track.<br> >><br> >> While I think this is in the spirit of my vision for Sugar, my<br> >> experience with how Sugar is being used and deployed _today_ makes it<br> >> quite uninteresting and too invasive to consider for the near future.<br> >><br> >> The current barriers for people to contribute to Sugar development and<br> >> share their work are mostly cultural. We can make the technology a<br> >> thousand times easier to modify, but if people still think that they<br> >> can be only users, we won't gain anything.<br> >><br> >> If we really want more people to realize their power and modify sugar<br> >> and share their work, we need to, in order:<br> >><br> >> - show how the community can address some of their needs, as perceived by them,<br> >><br> >> - show how they can better address the rest of their needs by working<br> >> within the community.<br> >><br> >> The rest is just icing on the top, IMHO.<br> ><br> > well, thats all true but it doesn't exclude easy to change and easy to<br> > share possibility of doer's changes e.g. if I want to hack Journal by<br> > adding wallpaper support(and of course want to expose my changes) the<br> > worst way that could be is proposing my changes to core team(e.g. think<br> > about proposing your patches to <a href="http://kernel.org" target="_blank">kernel.org</a> team - maybe exaggerating but<br> > the same level issue). Having ready to use sugarized 0install<br> > environment gives developers easy sharing method.<br> <br> </div></div>As I said, I agree with your points of view and also agree something<br> should be done in the path you show. But I also think that presently,<br> what would bring more users and deployers on board, is by caring of<br> their more immediate needs.<br> <br> Regards,<br> <font color="#888888"><br> Tomeu<br> </font><div class="im"><br> --<br> ŤSugar Labs is anyone who participates in improving and using Sugar.<br> What Sugar Labs does is determined by the participants.ť - David<br> Farning<br> _______________________________________________<br> </div><div><div></div><div class="h5">IAEP -- It's An Education Project (not a laptop project!)<br> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br> </div></div></blockquote></div><br><br clear="all"><br>-- <br>Sebastian Silva<br>Colectivo FuenteLibre<br><a href="http://blog.fuentelibre.org/">http://blog.fuentelibre.org/</a><br>