Features/Problem Reports - Revision history

Wade: /* Detailed Description */

2009-12-20T14:23:33Z

Detailed Description

← Older revision		Revision as of 10:23, 20 December 2009
Line 24:		Line 24:
	After uploading, the user is given a Report ID number (a small decimal number). They can use this if they wish to follow up with the Sugar developers by email.		After uploading, the user is given a Report ID number (a small decimal number). They can use this if they wish to follow up with the Sugar developers by email.

	~~[[File:Problem-report.jpg]]~~

	==== For Deployments ====		==== For Deployments ====
Line 30:		Line 29:

	The URL of the log server is configured using a GConf key and can be customized per deployment.		The URL of the log server is configured using a GConf key and can be customized per deployment.

			It's important to understand that this system is intended to be as automated as possible, so deployments should not expect to have a staff of support personnel monitoring problem reports, but can instead use them to get a general sense of what problems are most common.

			[[File:Problem-report.jpg]]

	== Benefit to Sugar ==		== Benefit to Sugar ==

Wade: /* Detailed Description */

2009-12-20T14:22:05Z

Detailed Description

← Older revision		Revision as of 10:22, 20 December 2009
Line 25:		Line 25:

	[[File:Problem-report.jpg]]		[[File:Problem-report.jpg]]

			==== For Deployments ====
			Deployments can set up their own log collection server, if desired. All that is required is a web server with PHP and sqlite.

			The URL of the log server is configured using a GConf key and can be customized per deployment.

	== Benefit to Sugar ==		== Benefit to Sugar ==

Wade: /* Documentation */

2009-12-20T14:20:52Z

Documentation

← Older revision		Revision as of 10:20, 20 December 2009
Line 64:		Line 64:
	== Documentation ==		== Documentation ==
	Ideally this feature would be documented as part of the FLOSS manual.		Ideally this feature would be documented as part of the FLOSS manual.

			Also, instructions for deploying the log server and configuring the URL via gconf should be documented on the Wiki.

	== Release Notes ==		== Release Notes ==

FGrose at 04:39, 18 October 2009

2009-10-18T04:39:47Z

← Older revision		Revision as of 00:39, 18 October 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}
			[[Category:Feature Page Incomplete]]
			[[Category:Feature\|Problem Reports]]</noinclude>

	== Summary ==		== Summary ==
Line 69:		Line 71:
	* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]		* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]

	~~[[Category:Feature Page Incomplete]]~~
	~~[[Category:Feature]]~~
	----		----
	''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''		''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''

Wade at 02:31, 17 October 2009

2009-10-17T02:31:16Z

← Older revision		Revision as of 22:31, 16 October 2009
Line 10:		Line 10:
	== Current status ==		== Current status ==
	* Targeted release: 0.88		* Targeted release: 0.88
	* Last updated: ~~September 9th~~, 2009		* Last updated: October 16th, 2009
	* Percentage of completion: 80%		* Percentage of completion: 90%

	== Detailed Description ==		== Detailed Description ==

Wade at 02:29, 17 October 2009

2009-10-17T02:29:26Z

← Older revision		Revision as of 22:29, 16 October 2009
Line 37:		Line 37:

	== Scope ==		== Scope ==
	A prototype of the control panel and server have been finished and posted to [http://trac.sugarlabs.org/ticket/1439\| #1439] as patches.		A prototype of the control panel and server have been finished and posted to [http://trac.sugarlabs.org/ticket/1439 #1439] as patches.

			The collection server is currently running at logcollect.sugarlabs.org. Logs are emailed out to the sugar-reports@lists.sugarlabs.org mailing list.

	Work left to do:		Work left to do:
	* <strike>The control panel needs a SVG icon.</strike> [[File:Toolbar-bug.png]]		* <strike>The control panel needs a SVG icon.</strike> [[File:Toolbar-bug.png]]
	* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.		* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.
	* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).		* <strike>The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).</strike> The server is now live at logcollect.sugarlabs.org. The mailing list sugar-reports@lists.sugarlabs.org now exists.
	* For deployments, there should be a way to override the server URL.		* <strike>For deployments, there should be a way to override the server URL.</strike> The server URL now comes from Gconf.
	* <strike>The Log activity needs to have its Upload Logs button replaced by a button that opens the control panel.</strike> Most likely we will remove the button from Log, but patches for both options have been posted to the ticket.		* <strike>The Log activity needs to have its Upload Logs button replaced by a button that opens the control panel.</strike> Most likely we will remove the button from Log, but patches for both options have been posted to the ticket.

Wade: /* Scope */

2009-09-29T22:51:54Z

Scope

← Older revision		Revision as of 18:51, 29 September 2009
Line 40:		Line 40:

	Work left to do:		Work left to do:
	* The control panel needs a SVG icon.		* <strike>The control panel needs a SVG icon.</strike> [[File:Toolbar-bug.png]]
	* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.		* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.
	* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).		* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).
	* For deployments, there should be a way to override the server URL.		* For deployments, there should be a way to override the server URL.
	* The Log activity needs to have its Upload Logs button replaced by a button that opens the control panel.		* <strike>The Log activity needs to have its Upload Logs button replaced by a button that opens the control panel.</strike> Most likely we will remove the button from Log, but patches for both options have been posted to the ticket.

	== How To Test ==		== How To Test ==

Wade: /* Scope */

2009-09-27T20:27:45Z

Scope

← Older revision		Revision as of 16:27, 27 September 2009
Line 44:		Line 44:
	* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).		* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).
	* For deployments, there should be a way to override the server URL.		* For deployments, there should be a way to override the server URL.
			* The Log activity needs to have its Upload Logs button replaced by a button that opens the control panel.

	== How To Test ==		== How To Test ==

Wade: /* Scope */

2009-09-27T20:16:42Z

Scope

← Older revision		Revision as of 16:16, 27 September 2009
Line 37:		Line 37:

	== Scope ==		== Scope ==
	A prototype of the control panel and server have been finished and posted to ~~Trac~~ #~~NNN~~ as patches.		A prototype of the control panel and server have been finished and posted to [http://trac.sugarlabs.org/ticket/1439\| #1439] as patches.

	Work left to do:		Work left to do:
	* The control panel needs a SVG icon.		* The control panel needs a SVG icon.
	* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.		* When an activity exits, if its log contains an exception report, Sugar should offer to report the problem. When an activity fails to launch, Sugar should display an error on the launch window and offer to report the problem instead of timing out.
	* The server needs to be installed on the SugarLabs infrastructure.		* The server needs to be installed on the SugarLabs infrastructure and the reports mailing list needs to be created (sugar-reports@lists.sugarlabs.org?).
	* For deployments, there should be a way to override the server URL.		* For deployments, there should be a way to override the server URL.

Wade at 19:31, 27 September 2009

2009-09-27T19:31:06Z

← Older revision		Revision as of 15:31, 27 September 2009
Line 21:		Line 21:

	After uploading, the user is given a Report ID number (a small decimal number). They can use this if they wish to follow up with the Sugar developers by email.		After uploading, the user is given a Report ID number (a small decimal number). They can use this if they wish to follow up with the Sugar developers by email.

			[[File:Problem-report.jpg]]

	== Benefit to Sugar ==		== Benefit to Sugar ==