Re: Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

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

 



On 6/29/22 8:45 PM, Vitaly Zaitsev via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 29/06/2022 20:24, Maxwell G wrote:
> I'm a bit confused. You say this sounds like a "package hijack attempt," but
> then you also say you don't like that it only allows access to epel* branches.

It is not possible to restrict access to only selected branches. EPEL maintainers can commit to Fedora branches and vice versa.

Thus, the newly added EPEL maintainers can do Fedora updates, and Fedora package maintainer can't prevent this. That's why I called this a "package hijack attempt".



What do you mean it is not possible? Isn't the new "collaborator" role exactly for this?

Best regards,

Ribert-André Mauchin
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[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