Re: Auto-assign packager sponsors to tickets?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> It absoletely does. ;)

And it even allows us to retrospectively see how many packagers were
sponsored in the last month/year/...
https://gist.github.com/FrostyX/47defa18348fbb917e73d7b2e7660ca2

Fedora-messaging is awesome :-)

On Mon, Apr 3, 2023 at 10:33 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
>
> On Mon, Apr 03, 2023 at 01:52:49PM -0500, Jason Tibbitts wrote:
> > >>>>> Miroslav Suchý <msuchy@xxxxxxxxxx> writes:
> >
> > > No, I'm not saying that. Somebody has enough courage to open the
> > > package review, discuss it, get to the point that the package review
> > > was approved. But did not have the courage to reach sponsors. It was
> > > road block for them.
> >
> > That's an odd case, I suppose.  I have trouble understand how someone
> > could make it through all of that process and then not be able to ask
> > for one more thing, and I would tend to attribute most issues in that
> > area to process overload and lack of documentation.  But then, that
> > points out a possibility for automation: When the review flag gets set
> > to '+' on a NEEDSPONSOR bug, automatically alert the sponsors.  If this
> > can file the ticket at https://pagure.io/packager-sponsors/ then great;
> > otherwise there is a mailing list, though it's much easier to lose a
> > random list message.
> >
> > I have no idea how to actually make that happen, unless bugzilla things
> > generate messages on the bus.
>
> It absoletely does. ;)
>
> https://apps.fedoraproject.org/datagrepper/raw?rows_per_pager=20&category=bugzilla
>
> Someone could write a toddler that listens for those and acts on the
> ones desired. Just like the current one that listens for scm requests.
>
> kevin
> _______________________________________________
> 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
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux