Difference between revisions of "Features/Journal data tagged private or public"

Latest revision as of 23:28, 21 November 2011

Summary

Provide a way to identify Journal entries as private for the owner or public.

Owner

Name: Walter Bender, Gonzalo Odiard
Email: Walter --AT-- sugarlabs.org, Gonzalo --AT-- laptop.org

Current status

Targeted release: 0.96
Last updated:
Percentage of completion:

Detailed Description

Modes private / public: A problem raised by some teachers, is that Journals of his students (and on school servers) are filled with music or games. With this proposal, Sugar would offer you to work in "public" when working at school or doing homework, or, if you are using Sugar for personal interests, then put your work in "private" category. This tag would be recorded in the Journal, and could also be changed in the detail view. This mode also works as a filter, so at school all the games and songs are not listed in the Journal. Furthermore, the school server would backup only those items recorded as public. This solves server space problems and helps preserve the privacy of students.

Benefit to Sugar

There are multiple benefits:

Better use of school servers disks and bandwidth.
Enable the deployments to analyze the work of kids without invading their privacy.

Scope

UI Design

We need add a way to set the mode public/private, a filter in the journal, and a way to switch the tag in the detail view.

How To Test

Features/Journal data tagged private or public/Testing

Comments and Discussion

See discussion tab for this feature

@@ Line 1: / Line 1: @@
-<noinclude>{{TOCright}}
+<noinclude>
-[[Category:Feature Page Incomplete]]
+[[Category:Feature|Journal data tagged private or public]]
-[[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>
-'''Comments and Explanations:'''
+== Summary ==
-There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
-<!-- 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 ==
+Provide a way to identify Journal entries as private for the owner or public.
-''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''
 == Owner ==
-''This should link to your home wiki page so we know who you are''
+* Name: [[User:Walter| Walter Bender]], [[User:Godiard| Gonzalo Odiard]]
-* Name: [[User:AcountName| Your Name]]
+* Email: Walter --AT-- sugarlabs.org, Gonzalo --AT-- laptop.org
-''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
 == Current status ==
-* Targeted release: (SUGAR_VERSION)
+* Targeted release: 0.96
-* Last updated: (DATE)
+* Last updated:
-* Percentage of completion: XX%
+* Percentage of completion:
 == Detailed Description ==
-''Expand on the summary, if appropriate.  A couple of sentences suffices to explain the goal, but the more details you can provide the better.''
+Modes private / public: A problem raised by some teachers, is that Journals of his students (and on school servers) are filled with music or games. With this proposal, Sugar would offer you to work in "public" when working at school or doing homework, or, if you are using Sugar for personal interests, then put your work in "private" category.  This tag would be recorded in the Journal, and could also be changed in the detail view. This mode also works as a filter, so at school all the games and songs are not listed in the Journal. Furthermore, the school server would backup only those items recorded as public. This solves server space problems and helps preserve the privacy of students.
 == Benefit to Sugar ==
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
-''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''
+There are multiple benefits:
+* Better use of school servers disks and bandwidth.
+* Enable the deployments to analyze the work of kids without invading their privacy.
 == Scope ==
-''What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''
 ==UI Design==
-''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''
+We need add a way to set the mode public/private, a filter in the journal, and a way to switch the tag in the detail view.
 == How To Test ==
 {{:{{PAGENAME}}/Testing}}
-== User Experience ==
-''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
-== Dependencies ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
-== 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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
-== Documentation ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''
-== Release Notes ==
-''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
 == 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. -->