Features/Problem Reports: Difference between revisions

Wade (talk | contribs)
No edit summary
Wade (talk | contribs)
 
(3 intermediate revisions by 2 users not shown)
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 21: Line 23:


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.
==== 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.
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]]
[[File:Problem-report.jpg]]
Line 62: Line 72:
== 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 ==
Line 69: Line 81:
* 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]]''