Re: [IAEP] Bug reporting
Walter Bender wrote: I am not sure that generally enabling all activities to have net access is a good idea... too easy to exploit. But there is a mechanism in the Log Activity to send logs with just one mouse click. (Not sure what is sent and to where. Maybe adding an optional field for annotating the problem to go with the log file?) In any case, this seems like an important feature to sort out for 0.88. I agree. In my view, part of the solution is to make the Activity logs available via the Journal. In the special case where an Activity crashes during startup, the Journal entry should show [name] failed to launch, and the contents should be the logfile as text/plain. Coupled with a generic uploading mechanism, this would make it much easier to diagnose and report at least this one kind of bug. This obviously also feeds back into our education mission. In Sugar, we can make the most of failure by letting users explore how the system has failed. signature.asc Description: OpenPGP digital signature ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Bug reporting
On Wed, Sep 16, 2009 at 19:01, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: Walter Bender wrote: I am not sure that generally enabling all activities to have net access is a good idea... too easy to exploit. But there is a mechanism in the Log Activity to send logs with just one mouse click. (Not sure what is sent and to where. Maybe adding an optional field for annotating the problem to go with the log file?) In any case, this seems like an important feature to sort out for 0.88. I agree. In my view, part of the solution is to make the Activity logs available via the Journal. In the special case where an Activity crashes during startup, the Journal entry should show [name] failed to launch, and the contents should be the logfile as text/plain. Coupled with a generic uploading mechanism, this would make it much easier to diagnose and report at least this one kind of bug. This obviously also feeds back into our education mission. In Sugar, we can make the most of failure by letting users explore how the system has failed. Sounds good to me, there has also been suggested that we display the activity logs in the view source dialog. Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Bug reporting
I just created a ticket for this feature request: http://bugs.sugarlabs.org/ticket/1366 -walter On Wed, Sep 16, 2009 at 1:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Wed, Sep 16, 2009 at 19:01, Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote: Walter Bender wrote: I am not sure that generally enabling all activities to have net access is a good idea... too easy to exploit. But there is a mechanism in the Log Activity to send logs with just one mouse click. (Not sure what is sent and to where. Maybe adding an optional field for annotating the problem to go with the log file?) In any case, this seems like an important feature to sort out for 0.88. I agree. In my view, part of the solution is to make the Activity logs available via the Journal. In the special case where an Activity crashes during startup, the Journal entry should show [name] failed to launch, and the contents should be the logfile as text/plain. Coupled with a generic uploading mechanism, this would make it much easier to diagnose and report at least this one kind of bug. This obviously also feeds back into our education mission. In Sugar, we can make the most of failure by letting users explore how the system has failed. Sounds good to me, there has also been suggested that we display the activity logs in the view source dialog. Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Bug reporting
hi Dennis, I share your dissatisfaction. Luke and I and others looked at two alternatives. Get Satisfaction and LaunchPad. Neither are perfect but LaunchPad is open source and helpful so we are leaning that way. Here is a possible vision the Teacher/End user bug reporting. We add a link to browse to this page, although probably under Sugar not Soas. https://answers.launchpad.net/soas People then ask a question about whatever they are experiencing, be it bug, confusion, inspiration etc. When they enter the question it searches existing answers and maybe its been asked/answered already. The community then answers question or it gets moved/linked to a bug put in by a developer of support-gang member. 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 wiki.sugarlabs.org but that won't help the average teacher. 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. On Tue, Sep 15, 2009 at 11:40 PM, Dennis Daniels dennisgdani...@gmail.comwrote: Greetings, I have roughly diagrammed the bug reporting process for Sugar here: http://wiki.sugarlabs.org/go/File:Reporting_a_bug.png I also timed it using Sugar as the UI for entering the bugs. I'd say it took nearly five minutes... and I have some idea of what I'm doing (though there are reasons to doubt that as well) and my internet connection is 900Kb /per sec normally. As it's apparently not possible to post a bug anonymously the added burden of logging in compounds the problem. I for one, as a teacher, would find it hard to justify a student spending5+minutes of time in class reporting a bug. My solution: using python's URL tools post an error log, using the same idea as ubiquitous 'view source' now a 'post bug' now, straight to a pastebin like interface that uses the IP address of the user plus the user name. The user doesn't need to know much more than typing a problem desc. and submitting. The logs are gathered up and posted straight to a 'pastebin/wiki' like page so that devs can see what's hot in the bug area for users. The user is given the URL of the bug on the wiki and can go and add more data if necessary. It's a lot looser bug tracking system but targeting the bugs that users bump into most often and FIXING those will go along way towards making SUGAR look and feel user friendly. The tool I'm using for the diagrams is Umbrello. I'd be happy to post the XMI to these diagrams if someone is interested. Dennis lost and found: +15047567321 +18586833669 GoogleTalk: dennisgdaniels skype : dennisdaniels EOF Sent from New Orleans, Louisiana, United States ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Bug reporting
Hi Dennis, On 16 Sep 2009, at 04:40, Dennis Daniels wrote: Greetings, I have roughly diagrammed the bug reporting process for Sugar here: http://wiki.sugarlabs.org/go/File:Reporting_a_bug.png -- snip -- The tool I'm using for the diagrams is Umbrello. I'd be happy to post the XMI to these diagrams if someone is interested. What, so you didn't stick with the Labyrinth Activity? ;-) I'm working on v8 at the moment, mostly likely just a revision bump for supporting the new 0.86 toolbars, MIME support, and a few minor bug fixes. Remember, right click to drag :-b Regards, --Gary ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
