BuildSys Analysis

Use Cases

User logs in using OpenId.
User creates a repo. POLICY: who can create a repo, how many repos?
- The repo has a multiple mock-configs, e.g. fedora(/centos?) release and architecture.
  - Each mock-config can be altered: adding more yum repos, altering minimal buildroot. To be prepared for some kind of dist-git, we should have both SRPM build mock configs and RPM build mock configs, using only RPM build mock configs in the first version. When both are used, they should come in pairs (e.g. each RPM build mock config should have either none or one associated SRPM build mock config).
- POLICY: Each repo has only repo-level permissions. The permissions should be divided at least into these groups: repo-admin (specifies permissions of other users for the repo), repo-rel-eng (can add/modify/delete mock configs), repo-packager (can build packages, delete old builds). No package-level permissions are considered for first version.