hi Dennis,<div><br></div><div>I share your dissatisfaction.</div><div><br></div><div>Luke and I and others looked at two alternatives. Get Satisfaction and LaunchPad.</div><div><br></div><div>Neither are perfect but LaunchPad is open source and helpful so we are leaning that way.</div>
<div><br></div><div>Here is a possible vision the Teacher/End user bug reporting.</div><div><br></div><div>We add a link to browse to this page, although probably under Sugar not Soas.</div><div><br></div><div><a href="https://answers.launchpad.net/soas">https://answers.launchpad.net/soas</a></div>
<div><br></div><div>People then ask a question about whatever they are experiencing, be it bug, confusion, inspiration etc.</div><div><br></div><div>When they enter the question it searches existing answers and maybe its been asked/answered already.</div>
<div><br></div><div>The community then answers question or it gets moved/linked to a bug put in by a developer of support-gang member.</div><div><br></div><div>Right now you still have to log in to ask a question. I wish you didn't. Luke says we can do single sign-on with the <a href="http://wiki.sugarlabs.org">wiki.sugarlabs.org</a> but that won't help the average teacher. </div>
<div><br></div><div>Luke and I both started school and the Class Acts Book Sprint happened so we haven't made much progress yet. But we would very much appreciate you also thinking with us on ways to improve the process.<br>
<br><div class="gmail_quote">On Tue, Sep 15, 2009 at 11:40 PM, Dennis Daniels <span dir="ltr"><<a href="mailto:dennisgdaniels@gmail.com">dennisgdaniels@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Greetings,<br>
I have roughly diagrammed the bug reporting process for Sugar here:<br>
<a href="http://wiki.sugarlabs.org/go/File:Reporting_a_bug.png" target="_blank">http://wiki.sugarlabs.org/go/File:Reporting_a_bug.png</a><br>
<br>
I also timed it using Sugar as the UI for entering the bugs. I'd say<br>
it took nearly five minutes... and I have some idea of what I'm doing<br>
(though there are reasons to doubt that as well) and my internet<br>
connection is 900Kb /per sec normally.<br>
<br>
As it's apparently not possible to post a bug anonymously the added<br>
burden of logging in compounds the problem. I for one, as a teacher,<br>
would find it hard to justify a student spending5+minutes of time in<br>
class reporting a bug.<br>
<br>
My solution:<br>
using python's URL tools post an error log, using the same idea as<br>
ubiquitous 'view source' now a 'post bug' now, straight to a pastebin<br>
like interface that uses the IP address of the user plus the user<br>
name.<br>
<br>
The user doesn't need to know much more than typing a problem desc.<br>
and submitting. The logs are gathered up and posted straight to a<br>
'pastebin/wiki' like page so that devs can see what's hot in the bug<br>
area for users. The user is given the URL of the bug on the wiki and<br>
can go and add more data if necessary. It's a lot looser bug tracking<br>
system but targeting the bugs that users bump into most often and<br>
FIXING those will go along way towards making SUGAR look and feel user<br>
friendly.<br>
<br>
The tool I'm using for the diagrams is Umbrello. I'd be happy to post<br>
the XMI to these diagrams if someone is interested.<br>
Dennis<br>
<br>
lost and found:<br>
+15047567321<br>
+18586833669<br>
GoogleTalk: dennisgdaniels<br>
skype : dennisdaniels<br>
<br>
<br>
<br>
EOF<br>
Sent from New Orleans, Louisiana, United States<br>
_______________________________________________<br>
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>
</blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>
</div>