Tomeu,<div><br></div><div>thanks a lot for picking this up again, I'm very sorry that I totally dropped the ball on the deployment feedback topic even though I had intended to really follow-up on it... :-/</div><div><br> </div><div>Anyway, if it's useful you can use my previously created questionnaire draft (<a href="http://spreadsheets.google.com/viewform?formkey=dG50R2wzakRZX0h6WjI4Y29RMkZacUE6MA.">http://spreadsheets.google.com/viewform?formkey=dG50R2wzakRZX0h6WjI4Y29RMkZacUE6MA.</a>.) as a starting point, just send me an offlist message with you @gmail address so I can give you access to it.</div> <div><br></div><div>Thanks,</div><div>Christoph<br><br><div class="gmail_quote">On Tue, Oct 6, 2009 at 7:48 PM, Tomeu Vizoso <span dir="ltr"><<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br> <br> as you may know, the Sugar code is officially maintained by a few<br> people, even though the code base is quite big.<br> <br> This has improved recently with Aleksey taking maintenance of the<br> datastore and the journal, but still I think that ideally each module<br> should be maintained by one or two different people. The present<br> accumulation of functions is affecting adversely the quality of our<br> work, as there are lots of important tasks that are slipping through<br> our fingers.<br> <br> In the longer term, I think we'll see deployers of Sugar devoting<br> their resources to these tasks, but this is still at least one or two<br> releases away. It's important that we reach that point because there's<br> a limit to how us volunteers can know what is best for deployers and<br> users.<br> <br> For now, I think we should accept that people far away from<br> deployments are going to be leading the development of Sugar and we<br> should plan accordingly. Meaning by this that we should make extra<br> efforts in making sure that whatever changes are done to Sugar, or<br> features added, they are a win for our users and not a loss. Also, I<br> think that by closely relating the work that needs to be done with<br> needs in the field, we can better ask for help and get more volunteers<br> involved in Sugar development.<br> <br> People at OLPC have shown interest in working with us so we get the<br> best feedback possible, so I think we have good chances of getting<br> very good feedback, though it might take a few iterations to build the<br> best possible relationships with those deployers.<br> <br> So in the immediate term I'm going to work on a very simple<br> questionnaire that will gather a first insight on what is going well,<br> what is going bad, which opportunities for improvement are, etc. from<br> each deployment, and then finding a way to present this information to<br> developers. I know this is not all the feedback that is wanted from<br> deployments, but we need to start with something and I think that by<br> showing clearly that we care about their needs we'll be able to build<br> more complex relationships in the future.<br> <br> I will be proposing a Google Spreadsheet form in the next few days<br> that deployments will fill if they choose to. I think we'll need to<br> have one for OLPC deployments and another for the other deployments<br> because in some cases those filling up the form won't be able to<br> easily differentiate between hardware and software issues.<br> <br> Regards,<br> <br> Tomeu<br> <font color="#888888"><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> Sugar-devel mailing list<br> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> </font></blockquote></div><br><br clear="all"><br>-- <br>Christoph Derndorfer<br>co-editor, olpcnews<br>url: <a href="http://www.olpcnews.com">www.olpcnews.com</a><br>e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br> </div>