Features/License selection in Journal: Difference between revisions

Created page with '<noinclude>{{TOCright}} Category:Feature Page Incomplete CC selection in Journal </noinclude> == Summary == While we encourage learners to create and sh…'
 
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>{{TOCright}}
<noinclude>[[Category:Feature Page Incomplete]]
[[Category:Feature Page Incomplete]]
[[Category:Feature|License selection in Journal]]
[[Category:Feature|CC selection in Journal]]
</noinclude>
</noinclude>


Line 17: Line 16:


== Detailed Description ==
== Detailed Description ==
Based upon the work of  
Based upon the work of Jon Phillips at www.creativecommons.org, we propose to add a widget to the Journal that lets user choose a license for their work. See this old ticket along with screen shots: https://dev.laptop.org/ticket/3529
 
We'll have to reexamine Jon's original [http://cctools.svn.sf.net/svnroot/cctools/liblicense-sugar/trunk/journal.patch patch] and look at some tickets that were at the time (2 years ago) blockers: [https://dev.laptop.org/ticket/3531] [https://dev.laptop.org/ticket/7551] [https://dev.laptop.org/ticket/7551]
 
There is [http://lists.laptop.org/pipermail/sugar/2008-May/005571.html an old thread] on this feature as well.


== Benefit to Sugar ==
== 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?''
I believe that it is wrong to have a learning platform for creating content that ignores the licensing issue. It would be of benefit to our users to be introduced to concept and practice of licensing and this feature provides that mechanism.
 
''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.''


== Scope ==
== Scope ==
Line 28: Line 29:


==UI Design==
==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.''
Jon's original design: [https://dev.laptop.org/attachment/ticket/3529/journal_default.png] [https://dev.laptop.org/attachment/ticket/3529/journal_entry.png] [https://dev.laptop.org/attachment/ticket/3529/journal_start.png]
 
Additional mock ups by the design team are [http://wiki.laptop.org/go/Designs/Creative_commons here].


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