On 1/10/19 10:58 AM, Ben Rosser wrote: > Hello, > > We had a recent discussion on this list last month about (among other > things) the current state of Pagure as a replacement for pkgdb [1]. > > I mentioned in that discussion that there are various issues which > have arisen from the deprecation of pkgdb that have made the packager > workflow ever so slightly worse. But it's not just pkgdb-- there are > lots of places where the packager workflow could use improvement. > There are parts of the process that are tedious and manual which could > be replaced with (partial) automation, or parts where automation > exists but is in need of improvement. > > For example, there are tools (namely, the "fedora-review" script) to > automate parts of the package review process. But fedora-review has > been lagging behind the packaging guidelines for some time, and has to > be manually ran by packagers over review requests. But, there's no > reason we couldn't run fedora-review automatically over every package > submission-- which might save both reviewers and submitters a lot of > time. Well, the issues in the past that have come up with that: * non free submissions. What if someone submits non free content and we build and host it? That would not be great. * DOS or security concerns. This is possibly not as big of a deal as it was in the past, and could be mitigated by using copr or a seperate koji just for this purpose. > Or, as another example, there's currently a lot of work going on in > the distribution to support new packaging formats-- like containers > and modules. New workflows for making containers or modules out of > existing packages are being created, and I think it's vital we make > sure these workflows and processes are designed in such a way to make > things as easy as possible for packagers. agreed! > Anyway, as part of that discussion, I was encouraged to propose a new > Fedora Community Objective focused on improving the packaging > experience and workflow in Fedora. Community Objectives are approved > by the Fedora Council and intended to be 12-18 month goals for the > entire project. The goal of this Objective would be to identify > problems with the current packager workflow(s), put together a group > of packagers interested in fixing things, and then fix them! > > If this sounds like something you'd be interested in helping out with, > great! The Objective will need two things, if it's to succeed: > > 1. People who are interested in helping! Some people did express > interest in the other thread, but I thought I would put out a general > call for interested packagers and volunteers. Anyone who is interested > and thinks they'll have some available time is more than welcome. I'm super busy, but I think this is quite important, so I would be happy to help out with history of things, getting you all access to make the changes you want or at least pointing you to the right people/place to submit changes. > 2. A concrete list of goals to accomplish. What glitches are there in > the current workflow, and how can they be fixed? What do you wish was > simpler, or better, or easier to do? What, basically, would make your > life easier a packager? Yes please, and then we should try and prioritize these since there's likely to be a bunch. :) Thanks a bunch for working on this! kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
