Bug 1127715
Summary: | RFE: Add support for group projects | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | Nikolai Kondrashov <nikolai.kondrashov> |
Component: | frontend | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | ignatenko, jzeleny, karlthered, orion, vgologuz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-15 09:45:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nikolai Kondrashov
2014-08-07 11:52:38 UTC
I think other option can be let adding groups to access management (permissions in webUI) Igor, this would still leave the owner's account name in the URL, which would be very nice to avoid. I still see value in mapping FAS groups to "virtual" users in copr. A practical use case is openstack packaging, we're now reusing my fellow packager Jakub account to create our repositories. Advantages: * no SPOF, any group member would be able to create repositories in the same namespace. * centralized group membership (in FAS) instead per repo * proper branding We really need this. e.g. KDE COPR for EPEL7 really needs more people working on it other than Rex. We would appreciate this in DNF as well since we would like to host our nightly builds in COPR. Version with this fix has been just deployed to production. Thanks a lot, Miroslav! |