From Fedora Project Wiki
< Changes
m (→Scope) |
|||
| Line 72: | Line 72: | ||
<!-- What work do the developers have to accomplish to complete the change 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 developers have to accomplish to complete the change 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?--> | ||
* Proposal owners: | * Proposal owners: Env and Stack WG | ||
<!-- 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 78: | Line 78: | ||
<!-- What work do other 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?--> | <!-- What work do other 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?--> | ||
* Release engineering: | * Release engineering: It's not a System Wide Change, because it doesn't break other software, but it will be needed releng for creating repos and similar stuff. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
* Policies and guidelines: | * Policies and guidelines: Most of guidelines will be [[https://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_%28draft%29 here]] for now. There need to be document with policies, but existing docs shouldn't change.<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 20:06, 1 March 2014
Playgrounds repository
Summary
The Playground Repository gives contributors a place to host packages that are not up to the standards of the main Fedora Repository but may still be useful to other users. For now the playground repository contains both packages that are destined for eventual inclusion into the main Fedora Repositories and packages that are never going to make it there. Users of the repository should be willing to endure a certain amount of instability to use packages from here.
All packages in Playground must play nice - no bad licenses, no proprietary software, no patented software.
Owner
- Name: Your Name
- Email: <your email address so we can contact you, invite you to meetings, etc.>
- Release notes owner:
- Responsible WG: Env and Stacks WG
Current status
- Targeted release: Fedora 21
- Last updated: 2014-03-01
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
For now the whole proposal leaves [here].
Benefit to Fedora
The main benefit will be easily installable software, which:
- could be for a long time in review queue, waiting for reviewers.
- is ugly or hard to package and review (e.g. bundling).
- has requirements on different version of libraries than currently is in Fedora.
Users can install more packages, developers can offer their packages more quickly.
Scope
- Proposal owners: Env and Stack WG
- Other developers: N/A (not a System Wide Change)
- Release engineering: It's not a System Wide Change, because it doesn't break other software, but it will be needed releng for creating repos and similar stuff.
- Policies and guidelines: Most of guidelines will be [here] for now. There need to be document with policies, but existing docs shouldn't 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: N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
- Blocks product? Unknown at this point
Documentation
N/A (not a System Wide Change)