m (→Policies) |
|||
| Line 50: | Line 50: | ||
* Do we allow replacement of other packages in the Playground Repository? (How do we stop this in our implementation?) | * Do we allow replacement of other packages in the Playground Repository? (How do we stop this in our implementation?) | ||
** Do we allow "backdoor replacement" in the playground repo? | ** Do we allow "backdoor replacement" in the playground repo? | ||
* How do we deal with multiple versions of same package provided by different coprs? | |||
[[Category:Env and Stacks]] | [[Category:Env and Stacks]] | ||
[[Category:Drafts]] | [[Category:Drafts]] | ||
Revision as of 14:52, 27 February 2014
It is still under construction and content may change. Do not rely on the information on this page. This document will eventually contain a roadmap for implementing the Playground repository. It will outline what the playground repository is and what groups, manpower, and other resources will be needed in order to implement it.
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.
Description
Policies
- 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.
How the repository will work
Packages for the repository are built in copr. The copr owner can mark the repository as a whole as being part of the Playground Repository. Packages successfully built for marked copr's are copied into the Playground Repository. [marcela] Who is copr owner? The project owner on copr? We need additional feature in copr for "mark as worth of Playground".
Identified needs
| Groups to Coordinate with | How necessary | Need |
| Infra | Necessary | Disk space for the yum repositories (Open question -- is this mirrored?) |
| Infra/Copr devs | Very nice to have | Copr deployment that's considered reliable enough to build packages for this repo |
| Copr devs | Necessary | Ability to mark an individual copr for inclusion in the playground repository |
| Copr devs | Optional but nice to have | Build from a git repo url and revision hash |
Open Questions
We'll need to answer these questions and by their answers, flesh out the [#Description] and add additional work items to the [#Identified_needs] section.
- deltarpms?
- signing?
- how do updates work (rolling? bodhi? Will we constantly be regenerating the repodata [like the rawhide build repo?])
- is there a testing repo?
- does it need adding to mirrormanager?
- will fedup support upgrades with packages there?
- Does it need to be mashed in order to get multilib support?
- self hosting (all packages needed to build the packages are in the repo)?
- Is there any review of repos/packages in the repos?
- Does the review differ depending on who is building the package (cla+1 vs in the packager group)?
- Do we allow conflicts with packages in the main repo?
- Do we allow replacement of packages in the main repo?
- Do we allow "backdoor replacement" of packages in the main repo? ie: Let's say I have a package in the playground repo: NetworkManager2.1. And that conflicts with NetworkManager. Is that allowed? Is it allowed as long as it doesn't have any virtual provides/obsoletes that would automatically allow it to replace the package in the main repo?
- Do we allow conflicts between packages in the Playground Repo?
- Do we allow replacement of other packages in the Playground Repository? (How do we stop this in our implementation?)
- Do we allow "backdoor replacement" in the playground repo?
- How do we deal with multiple versions of same package provided by different coprs?