[IAEP] Bug reporting

Tomeu Vizoso tomeu at sugarlabs.org
Wed Sep 16 13:06:24 EDT 2009


On Wed, Sep 16, 2009 at 19:01, Benjamin M. Schwartz
<bmschwar at 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


More information about the IAEP mailing list