m (→Dependencies) |
|||
| Line 129: | Line 129: | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- 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: | * Contingency mechanism: Do not add the repo during F21. <!-- 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: | * Contingency deadline: I doesn't matter, it doesn't influence Fedora main repo. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? Doesn't block a product. Another repo, different than Playground, could be, but we are not providing any other at this moment. | * Blocks product? Doesn't block a product. Another repo, different than Playground, could be, but we are not providing any other at this moment. | ||
Revision as of 16:02, 26 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: MarcelaMašláňová
- Name: other names?
- Email: mmaslano@redhat.com
- 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 lives [here].
Benefit to Fedora
Users can install interesting packages, developers can offer their packages more quickly and their packages can be find easier on one place.
Packages can be included in distribution, possible bugs can be found before inclusion in Fedora main repo.
The main benefit will be easily installable software, which:
- is waiting for review too long (ugly sw, bundles, ...)
- requires exact version of sw not included in Fedora
Scope
- Proposal owners: Env and Stack WG
- Other developers:
- Copr devs
- Ability to mark an individual COPR for inclusion in the Playground repository.
- Build from a git repository URL and revision hash
- Copr deployment that's considered reliable enough to build packages for this repo
- Infra
- Disk space for the yum/dnf repositories
- Continuously regenerating repodata
- Daily composes of the Playground repository
- Copr deployment that's considered reliable enough to build packages for this repo
- Copr devs
- Release engineering:
- Nice to haves - deltarpms, multilib.
- Policies and guidelines:
- Packages must follow the Legal Guidelines. In particular, the license for all packages must be approved in the Legal Guidelines.
- Packages may violate other Fedora Packaging Guidelines.
Upgrade/compatibility impact
Main repository won't be harmed by Playground.
How To Test
0. Build your package or set of packages in Copr
1. Ask for marking your packages as Playground
2. Wait for addition into Playground repository
3. Add Playground repo and install by PackageKit/yum
User Experience
User should be able add new repository providing lot of new stuff easily.
Dependencies
Contingency Plan
- Contingency mechanism: Do not add the repo during F21.
- Contingency deadline: I doesn't matter, it doesn't influence Fedora main repo.
- Blocks release? No
- Blocks product? Doesn't block a product. Another repo, different than Playground, could be, but we are not providing any other at this moment.
Documentation
Will be.