On Fri, Dec 21, 2018 at 6:16 PM Dennis Gilmore <dennis(a)ausil.us> wrote:
On Fri, 2018-12-21 at 16:23 -0500, Ben Cotton wrote:
> Hi Ben,
> Thanks for drafting this. I think it's a great step in the right
> direction. You're right that these are all minor annoyances that
> aggregate to a bigger problem, so it's good to take a holistic
> approach to addressing them. Right now it seems focused on replacing
> the features lost by the deprecation of pkgdb. I'd encourage you to
> think about what other changes could be made to improve the overall
> packaging experience. Before it comes up for a vote, I'd like to see
> more concrete goals and a rough idea of how they'd be achieved.
> Obviously some of the specifics will become clear and evolve as the
> work goes on.
I would like to echo Ben here, I think that a package experience
objective should look at how to automate the tedious manual repetitive
bits in maintaining packages and allow people to only have to deal with
things that truely need a person to look at them. I would like to see
steps from fully automating package reviews and updates, and letting
packagers know when they have something needing attention, to
rethinking the workflows entirely. I think that there could be a lot of
tie in with the CI objective.
Hi Dennis and Ben,
Sorry for the delay in responding here; I admit I wasn't thinking too
much about Fedora over vacation...
Thanks a lot for the feedback! I think it definitely makes sense to
broaden the proposal to include more than just cleaning up after the
pagure migration-- though I still think that's a good place to start,
since it's something that happened relatively recently.
I do have some thoughts about other areas of the workflow that could
be improved (like the review process, which I just added a section on
to the wiki page), but I think I'll first take this back to the devel
list to solicit interest and ideas from others. Then, perhaps, we can
try to set some more concrete goals and create a more specific plan
for accomplishing them.
(Part of this might be identifying what can be done in the next 12-18
months and what's a longer term goal to keep working on in the future,
too. For instance, I think a short-term goal for the review process
might be to get fedora-review ran automatically on all review tickets,
but a longer-term goal might be to replace Bugzilla entirely and write
a new reviews app. The short-term goal might be something we'd want to
get done explicitly as part of the Objective, while the long-term goal
might be something for the "packager quality of life" SIG/WG to keep
working on over time.)