186
edits
Changes
Jump to navigation
Jump to search
Features/Statistics gathering (view source)
Revision as of 23:09, 21 November 2011
, 23:09, 21 November 2011Created page with "<noinclude> Category:Feature Page Incomplete <Feature Name> <!-- You can add categories to tie features back to real deployments/schools requesting them,..."
<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|<Feature Name>]]
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
</noinclude>
<!-- All fields on this form are required to be accepted.
We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->
== Summary ==
''The software improvement process requires usage statistics data to learn from our users.''
== Owner ==
* Name: [[User:Sebastian| Sebastian Silva]]
* Email: sebastian at sugarlabs.org
== Current status ==
* Targeted release: 0.96
* Last updated: 2011.11.21
* Percentage of completion: 0%
== Detailed Description ==
There have been efforts to gather statistics from the Journal as well as from Sugar error logs. However this is not sufficient. We would like there to be an optional logging of user interaction events that would make statistical analysis of usage viable.
== Benefit to Sugar ==
Sugar will benefit from being easier to work with for researchers trying to study computer in education implementations. Also deployments can engage in user experience tracking and help provide helpful (hard data) feedback to developers who can improve the platform.
The Local Lab in Peru sees this feature as strategic for Local Labs sustainability.
== Scope ==
Not sure.
==UI Design==
No UI changes necessary.
== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
N/A.
== Dependencies ==
Determining relevant metrics.
== Contingency Plan ==
Push for next release.
== Documentation ==
To come.
== Release Notes ==
To come.
== Comments and Discussion ==
* 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|<Feature Name>]]
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
</noinclude>
<!-- All fields on this form are required to be accepted.
We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->
<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->
== Summary ==
''The software improvement process requires usage statistics data to learn from our users.''
== Owner ==
* Name: [[User:Sebastian| Sebastian Silva]]
* Email: sebastian at sugarlabs.org
== Current status ==
* Targeted release: 0.96
* Last updated: 2011.11.21
* Percentage of completion: 0%
== Detailed Description ==
There have been efforts to gather statistics from the Journal as well as from Sugar error logs. However this is not sufficient. We would like there to be an optional logging of user interaction events that would make statistical analysis of usage viable.
== Benefit to Sugar ==
Sugar will benefit from being easier to work with for researchers trying to study computer in education implementations. Also deployments can engage in user experience tracking and help provide helpful (hard data) feedback to developers who can improve the platform.
The Local Lab in Peru sees this feature as strategic for Local Labs sustainability.
== Scope ==
Not sure.
==UI Design==
No UI changes necessary.
== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
N/A.
== Dependencies ==
Determining relevant metrics.
== Contingency Plan ==
Push for next release.
== Documentation ==
To come.
== Release Notes ==
To come.
== Comments and Discussion ==
* 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. -->