Features/License selection in Journal - Revision history

FGrose: FGrose moved page Features/Feature CC selection in Journal to Features/License selection in Journal: simplify name

2014-01-31T17:27:27Z

FGrose moved page Features/Feature CC selection in Journal to Features/License selection in Journal: simplify name

← Older revision	Revision as of 13:27, 31 January 2014
(No difference)

FGrose: sort in category page

2014-01-31T17:26:45Z

sort in category page

← Older revision		Revision as of 13:26, 31 January 2014
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>

Walter: /* UI Design */

2009-12-01T23:16:56Z

UI Design

← Older revision		Revision as of 19:16, 1 December 2009
Line 30:		Line 30:

	==UI Design==		==UI 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]		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].		Additional mock ups by the design team are [http://wiki.laptop.org/go/Designs/Creative_commons here].

Walter: /* UI Design */

2009-12-01T23:16:37Z

UI Design

← Older revision		Revision as of 19:16, 1 December 2009
Line 32:		Line 32:
	[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]		[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 ~~referenced in the ticket~~.		Additional mock ups by the design team are [http://wiki.laptop.org/go/Designs/Creative_commons here].

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

Walter: /* UI Design */

2009-12-01T23:15:22Z

UI Design

← Older revision		Revision as of 19:15, 1 December 2009
Line 30:		Line 30:

	==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~~.''		[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 referenced in the ticket.

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

Walter: /* Detailed Description */

2009-12-01T23:14:25Z

Detailed Description

← Older revision		Revision as of 19:14, 1 December 2009
Line 18:		Line 18:
	== Detailed Description ==		== Detailed Description ==
	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		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

	~~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~~

	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]		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]

Walter: /* Benefit to Sugar */

2009-12-01T23:09:01Z

Benefit to Sugar

← Older revision		Revision as of 19:09, 1 December 2009
Line 30:		Line 30:

	== 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 ==

Walter: /* Detailed Description */

2009-12-01T23:07:16Z

Detailed Description

← Older revision		Revision as of 19:07, 1 December 2009
Line 17:		Line 17:

	== 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

			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

			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 ==

Walter: Created page with '{{TOCright}} Category:Feature Page Incomplete CC selection in Journal == Summary == While we encourage learners to create and sh…'

2009-12-01T22:54:05Z

Created page with '<noinclude>{{TOCright}} Category:Feature Page Incomplete CC selection in Journal </noinclude> == Summary == While we encourage learners to create and sh…'

New page

<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|CC selection in Journal]]
</noinclude>

== Summary ==
While we encourage learners to create and share their work, we provide no mechanism for them to assign licenses to their work. This feature introduces a license field to the Journal to give the learner an opportunity to assign a Cc license to their work.

== Owner ==
* Name: [[User:Walter|Walter Bender]]
* Email: <walter AT sugarlabs DOT org>

== Current status ==
* Targeted release: (0.88)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
Based upon the work of

== 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.''

== 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.''

== 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]]