Changes

28 bytes added ,  00:25, 18 October 2009
m
no edit summary
Line 1: Line 1: −
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
+
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 +
[[Category:Feature Page Incomplete]]
 +
[[Category:Feature|Bug Report]]</noinclude>
    
<!-- All fields on this form are required to be accepted.
 
<!-- All fields on this form are required to be accepted.
Line 8: Line 10:  
== Summary ==
 
== Summary ==
   −
Provide simple way for non-tech users(one click way) to enable debug mode(export proper environment variables) and send logs from ~/sugar/defuult/logs to SL infrastructure.
+
Provide simple, one-click way for non-technical users to enable debug mode (export proper environment variables) and send logs from ~/sugar/default/logs to the Sugar Labs infrastructure.
    
== Owner ==
 
== Owner ==
Line 24: Line 26:  
== Detailed Description ==
 
== Detailed Description ==
   −
It could be useful to provide as simple as possible method for non-tech users e.g. sugar could send info to predefined server instead of asking questions.
+
It could be useful to provide as simple as possible method for non-tech users, i.e., sugar could send info to predefined server instead of asking questions.
    
This functionality should be kept out of the way of regular usage paths. It will be of no use to the majority of our users (young children, most unable to speak more than very basic English, often completely lacking connectivity). One approach might be to implement a script similar to olpc-log, which made a tarball of all the important logs for the purpose of being sent along with bug reports. -[[User:DanielDrake|DanielDrake]] 16:07, 17 August 2009 (UTC)
 
This functionality should be kept out of the way of regular usage paths. It will be of no use to the majority of our users (young children, most unable to speak more than very basic English, often completely lacking connectivity). One approach might be to implement a script similar to olpc-log, which made a tarball of all the important logs for the purpose of being sent along with bug reports. -[[User:DanielDrake|DanielDrake]] 16:07, 17 August 2009 (UTC)
Line 56: Line 58:     
== Contingency Plan ==
 
== Contingency Plan ==
''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''
+
''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
    
== Documentation ==
 
== Documentation ==
Line 69: Line 71:  
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
   −
  −
[[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]]''