<html><head><style type="text/css"></style></head><body><div style="font-family:'Courier New', courier, monaco, monospace, sans-serif;font-size:12pt"><div>... that I haven't responded until now. I have been taking a multiple-week video editing class. I would definitely like to edit more videos for you all. Sorry again about the delay, but there is actually no internet access at the campus. Let me know what you want done and I can begin work asap.<div><br></div><div>Please forward this message to list serve as I can't send to it for some reason</div><div><br><div><br></div><div>Dave C. <br><p style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> </p></div></div></div><div style="font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> David Farning <dfarning@sugarlabs.org><br><b><span style="font-weight: bold;">To:</span></b> iaep <iaep@lists.sugarlabs.org>; Sugar-dev Devel <sugar-devel@lists.sugarlabs.org>; Sugar Labs Marketing <Marketing@lists.sugarlabs.org><br><b><span style="font-weight: bold;">Sent:</span></b> Monday, August 3, 2009 11:10:15 AM<br><b><span style="font-weight: bold;">Subject:</span></b> [Marketing] First step towards an efficient feedback process<br></font><br> One of the challenges over the next couple of months will be figuring<br>out how to turn 'feedback' from deployments into useful 'information'<br>which the bug squad and deployment team can use.<br><br>As a first step, I would like to suggest that we keep deployment<br>related threads on <a ymailto="mailto:iaep@sl.o" href="mailto:iaep@sl.o">iaep@sl.o</a>. After all, deployments are the<br>education part of the it's an education project. There will be a<br>number of benefits to this:<br><br>1. Developers 'like' to work from bug trackers. Our bug tracker is<br>at <a target="_blank" href="http://dev.sugarlabs.org">dev.sugarlabs.org</a> . An example of a good bug report is at<br><span><a target="_blank" href="http://dev..sugarlabs.org/ticket/1100">http://dev.sugarlabs.org/ticket/1100</a> . In this report Gary does a</span><br>good job of clearly describing the problem. It is very common for bug<br>reports to turn into conversation very similar to mailing list<br>conversations as the bug reporter and bug fixer narrow in on the exact<br>cause of the bug. There is some very useful metadata at the top<br>report describing exactly which version and component you can find the<br>bug. Finally, there is a the Ownedby field. If a bug is identified<br>on a mailing list it is likely to be forgotten within minutes.. Once a<br>bug is entered into the tracker, someone owns the bug until they<br>assign it to someone else.<br><br>2. Developers like to work from feature requests. Sugar stores<br>feature requests on the wiki at<br><span><a target="_blank" href="http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore">http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore</a> . A good</span><br>example of a feature request is<br>at<a href="http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore" target="_blank">http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore</a> . The<br>format of the feature request make it easy for developer to figure out<br>how a new feature fits into the exist code base and how to prioritize<br>the feature.<br><br>These two process are not just 'make work.' Most non-teachers, have<br>very little grasp of the processes teacher use to keep a class room of<br>squirmy kids focused on a learning objective. It is just going to<br>take awhile until we learn to understand deployers need and<br>specialized vocabulary.<br><br>3. By keeping the deployment discussion on iaep, we can work together<br>to figure out how turn feedback into usable information for developers<br>before turning it into bug reports or feature requests.<br><br>4. We can create a culture in which deployers and developers equally<br>respected members of the sugar community.<br><br>5. By clearly splitting up the roles and responsibilities between<br>developer and deployers we start to lay the foundation for reviving<br>the deployment team.<br><br>david<br>_______________________________________________<br>Marketing mailing list<br><a ymailto="mailto:Marketing@lists.sugarlabs.org" href="mailto:Marketing@lists.sugarlabs.org">Marketing@lists.sugarlabs.org</a><br><span><a target="_blank" href="http://lists.sugarlabs.org/listinfo/marketing">http://lists.sugarlabs.org/listinfo/marketing</a></span><br></div></div><div style="position:fixed"></div></div><br> </body></html>