Re: Auto-assign packager sponsors to tickets?

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

 



Jason Tibbitts kirjoitti 3.4.2023 klo 20.09:
Miroslav Suchý <msuchy@xxxxxxxxxx> writes:

In any case, what I wrote was the procedure I documented it when I set
it up.  If all of that documentation was lost, then I don't know what to
say but that's not what was intended.

I drove the change that made this happen.  I made sure the documentation
(in the wiki at the time) referenced the procedure.  If that was lost
after the time when I was able to be very active in Fedora, then that's
a sad state of affairs and I don't know why that would happen, but it
would be really good if it could un-happen.  Did FESCo revert the policy
change or something?

Somewhat recently, the Packager sponsor policy [1] has been rewritten. The history is that moved content over from the wiki to the Package Maintainer Docs, then edited it to make things more clear. Later, I realized that what I edited was actually intended to be a FESCo-approved policy, just not clearly marked as such in the wiki and editable by anyone. So I went to FESCo to get the material officially approved - see the pull request [2].

The result of this is that it is currently a FESCo policy that for new packages, the sponsorship is requested by blocking the FE-NEEDSPONSOR Bugzilla, and for all other paths by filing a Pagure ticket. The reason why I wrote the pull request like that is that at that time, there was discussion about this on devel where I proposed using Pagure tickets for new packages also, but got negative feedback [3].

The gist of that negative feedback was "very few sponsors are looking at the Pagure tickets, we cannot process that many". From this thread I get the opposite impression, that Pagure tickets are processed quickly and FE-NEEDSPONSOR blockers are not looked at. If so, I propose the policy is updated to ask for a Pagure ticket in every case.

[1]: https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_policy/
[2]: https://pagure.io/fesco/fesco-docs/pull-request/59
[3]: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/X54HX23AFVNPHROX5ULPAEW5YGKWOLPI/
_______________________________________________
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