[EPEL-devel] Re: EPEL packagers building packages without permission, not taking care of them

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

 





On Tue, 5 Nov 2024 at 07:29, Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote:


On Tue, 5 Nov 2024 at 04:59, Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
Hello,

I appreciate all the heroic efforts to get EPEL 10 going.

However, could you please stop building packages in EPEL if you did not get ack
from the Fedora maintainers, or if you don't intend to take care of the package
after building it?

I repeatedly saw and called out this behavior. I even assigned the one who did
this as a primary package maintainer for EPEL. Yet they don't respond to EPEL
bugzillas (not even to requests for EPEL 10 branching of packages I assigned to
them after they did this in EPEL 9).

I don't want to shame and blame, so I am not sharing any names or links
publicly. But seriously, please, stop this.


Could you please open a ticket with the names of the people involved in this. If they are not responding to tickets and being jerks by building packages without taking ownership then it needs to be dealt with <PERIOD>.


Calling people jerks on a mailing list was uncalled for on my part. I have no excuse for it and should have done better. 

I do think that if there are packages like this which have been forked and built without permission then they need to have the epel-sig group as a co-owner so someone can hopefully take care of them. Also the same with packages which are having bugzilla tickets missed. That would hopefully allow for an automation report to show which tickets are for epel related packages needing CVE, bug fixes, or other updates.

--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
-- 
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux