Changes/Playground repository

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

We are still working on details but the main ideas are finished and described in the [draft].

Packages for the repository are built in COPR. The COPR owner can propose the repository as a whole for inclusion into the Playground repository by marking it as such in COPR. Repositories/packages successfully built and satisfying the Playground repository's Policies are marked as the Playgroud repository. The one Playground repository includes many Copr repositories.

Playground repository is meant only for F-21+. It's Beta, which means usage of dnf is fine.

Benefit to Fedora

Users can install interesting packages from ONE place, 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
• bundle

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

• 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. Mark your packages as Playground wanted

2. Wait for addition into Playground repository

3. Add Playground repo and install by PackageKit/dnf

User Experience

User should be able add new repository providing lot of new stuff easily.

Dependencies

• Copr - partially done
• dnf - plugin for Coprs must replace yum, otherwise Playground stays in Beta

Contingency Plan

• Contingency mechanism: Do not add the repo during F21.
• Contingency deadline: It 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

There will documentation of the repository, how to work it and and so on, when we finally figure out all details.