On Tue, Dec 03, 2019 at 11:27:33AM +0100, Fabio Valentini wrote: > On Tue, Dec 3, 2019, 10:42 Pierre-Yves Chibon <[1]pingou@xxxxxxxxxxxx> > wrote: > > On Mon, Dec 02, 2019 at 11:25:13PM +0100, Fabio Valentini wrote: > > On Mon, Dec 2, 2019, 22:44 Kevin Kofler > <[1][2]kevin.kofler@xxxxxxxxx> wrote: > > > > Igor Gnatenko wrote: > > > * Should any other packager (not that maintainer) be able to > request > > > new branches on that repo? > > > * Should provenpackager be able to do the same request? > > > > Since I do not give a darn about what happens to my packages on > EPEL, I > > am > > fine with anybody requesting EPEL branches for them as long as > they do > > the > > work and don't expect me to do anything to those branches (which > is not > > going to happen). > > > > I think this might be a good time point out that it's actually > possible to > > override the default assignee for a component for EPEL bugs (also > for > > fedora) in bugzilla by adding this override in the > > releng/fedora-scm-requests repo for the respective package, like > here: > > > [2][3]https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/jackson-databind > > (Note that lef was actually deemed non-responsive some months back, > so > > this is probably not a good example of a package where this split > > responsibility "worked".) > > Just a note on that subject, we're actively working on getting ride of > this git > repo and move this back to dist-git as well :) > > Hi Pierre, > That's good to hear, the current workflow is a bit involved. > Do you plan to store this data in a file in each dist-git branch, or in a > file containing the whole information on a separate, non-buildable orphan > (semantic overload here ...) git branch? I think the latter would have the > benefit of not interfering with dist-git contents at all, while still > being stored in the same repo. The idea is to store this in the database on pagure, no git repo involved. Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
