From Fedora Project Wiki
< Changes
Pbrobinson (talk | contribs) (Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...") |
(→Owner: updated release note owner) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} | <!-- {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}} --> | ||
<!-- Self Contained or System Wide Change Proposal? | <!-- Self Contained or System Wide Change Proposal? | ||
| Line 34: | Line 34: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* Name: [[User:Pbrobinson| Peter Robinson]] | |||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: pbrobinson at fedoraproject dot org | * Email: pbrobinson at fedoraproject dot org | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: [[User: mccann2| Sandra McCann]] <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 57: | Line 57: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1238431 #1238431] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 71: | Line 71: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
This feature will let all involved projects like Fedora and Sugar Labs profit, as it brings the latest and greatest bits from the Sugar community for education into Fedora. By making Sugar more readily available, it's easier for users to play with it, become involved, and contribute back. It will allow us to capture the interest in developing for OLPC and Sugar Labs on the Fedora platform. | This feature will let all involved projects like Fedora and Sugar Labs profit, as it brings the latest and greatest bits from the Sugar community for education into Fedora. By making Sugar more readily available, it's easier for users to play with it, become involved, and contribute back. It will allow us to capture the interest in developing for OLPC and Sugar Labs on the Fedora platform. | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Update to the latest Sugar UX, update and test Activities and other integration with the distro. | ||
<!-- What work do the feature owners 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?--> | <!-- What work do the feature owners 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?--> | ||
| Line 130: | Line 129: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora 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 "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) | * Contingency mechanism: (What to do? Who will do it?) Feature is already mostly complete, upstream stable release is scheduled will within the required release window <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 150: | Line 149: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF23]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 13:29, 13 August 2015
Sugar 0.106
Summary
Update Sugar to the new upstream 0.106 stable feature release.
Owner
- Name: Peter Robinson
- Email: pbrobinson at fedoraproject dot org
- Release notes owner: Sandra McCann
Current status
Detailed Description
We want to provide the new version of the Sugar desktop environment as well as more activities to allow further building upon the collaborative environment.
Users curious about the Sugar interface can test out Sugar on an existing Fedora system by selecting the Sugar environment from their display manager.
Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop.
Benefit to Fedora
This feature will let all involved projects like Fedora and Sugar Labs profit, as it brings the latest and greatest bits from the Sugar community for education into Fedora. By making Sugar more readily available, it's easier for users to play with it, become involved, and contribute back. It will allow us to capture the interest in developing for OLPC and Sugar Labs on the Fedora platform.
Scope
- Proposal owners: Update to the latest Sugar UX, update and test Activities and other integration with the distro.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Feature is already mostly complete, upstream stable release is scheduled will within the required release window
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)