On Thu, Apr 20, 2017 at 08:33:23PM +0200, Till Maas wrote:
Hi,
On Thu, Apr 20, 2017 at 03:45:16PM +0200, Pierre-Yves Chibon wrote:
- With pkgdb out of the loop, we'll need to figure some things out:
- Where/How to store the contact info for bugzilla
- Not sure relying on pagure's ACLs there is the way to go since we would loose a level of granularity in the ACLs that I know people like and ask for (having commit w/o being on the CC list in bugzilla or being on the CC list w/o being a packager)
- How/when to require people be part of the packager group in FAS?
- Since one of the idea of pagure is to make it easier for "drive-by" contribution to spec files, requiring to be a packager should only be there for maintainers, but pagure doesn't have this level of information/requirement, so we would need to find something or some place to add this requirement or see if that requirement still stands
sorry if I missed it, but pkgdb manages some more things where I not yet understand how this maps to the pagure dist-git workflow:
- Request a new package to be added to pagure dist-git/a package to be unretired
New package to add == request for a new PoC of a new component in bugzilla
- Requests for new (EPEL) branches
== request for a new PoC in Fedora EPEL in bugzilla
- Orphan/Retire a package
Orphan == request to change the PoC of the component in bugzilla
- Manage development status of collections (In development, live, EOL)
This is going away with the modularity effort and could be ported to PDC in the mean time.
- Configuring upstream release monitoring
- Manage koshei integration
We could include these two in the substitute of our current pkgdb.
The only remaining item which I'm not entirely sure how to handle it is retiring a package.
Do note that this is all currently WIP or rather thoughts in progress :)
Pierre