Now that EPEL 9 is in full swing, I'd like to start planning ahead for what comes next. CentOS Stream 10 is expected to be available in 2024. We should be able to start EPEL 10 around the same time. Until then, we have the opportunity to evaluate what we can improve in EPEL.
I am proposing a new workflow and structure for EPEL 10. The high level summary is for EPEL 10 to have unique branches, build targets, and repos for each minor version of RHEL 10, including CentOS Stream 10 as the upcoming minor version. This would be a significant change from how EPEL works today, but I think it would address several pain points for maintainers and users. I am opening this topic for discussion as early as possible before the EPEL 10 launch to gather feedback. Please note that this is currently just a proposal and has yet to be voted on by the EPEL Steering Committee.
Please visit this thread on the Fedora Discussion site for the full proposal.
https://discussion.fedoraproject.org/t/epel-10-proposal/44304
I would also ask that feedback be provided there instead of as email replies here on the list.
On Wed Nov 23, 2022 at 00:52 CST, Carl George wrote:
I would also ask that feedback be provided there instead of as email replies here on the list.
I don't think there's been a formal discussion about moving EPEL discussions over to the forums. We already have communication split between the issue tracker and the ML, so I'm -1 to also adding the forums. In general, I find it easier to keep up with and participate in discussions on mailing lists than on forums. However, it seems to me that this is just for this one proposal, so I guess my comment is off topic.
-- Best,
Maxwell G (@gotmax23) Pronouns: He/Him/His
On Wed, Nov 23, 2022 at 2:27 PM Maxwell G via epel-devel epel-devel@lists.fedoraproject.org wrote:
On Wed Nov 23, 2022 at 00:52 CST, Carl George wrote:
I would also ask that feedback be provided there instead of as email replies here on the list.
I don't think there's been a formal discussion about moving EPEL discussions over to the forums. We already have communication split between the issue tracker and the ML, so I'm -1 to also adding the forums. In general, I find it easier to keep up with and participate in discussions on mailing lists than on forums. However, it seems to me that this is just for this one proposal, so I guess my comment is off topic.
-- Best,
Maxwell G (@gotmax23) Pronouns: He/Him/His _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org 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@lists.fedoraproject... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
EPEL is part of Fedora. discussion.fpo is one of the official places to talk about Fedora things [0]. We already have an #epel tag there with multiple posts [1]. The platform (discourse) has some support for email if you prefer that. On the tag page there is a bell icon that lets you subscribe to a tag, which I believe will email you for every topic started in that tag. You can reply to topics by replying to those emails. The regular mailing lists are also a valid place to discuss Fedora things, but in this instance I wanted to use discussion.fpo for two specific reasons: 1) I wanted to use markdown tables, and 2) I wanted to be able to edit the original post to add FAQ items as feedback comes in.
[0] https://docs.fedoraproject.org/en-US/project/help/#_fedora_discussion [1] https://discussion.fedoraproject.org/tag/epel
epel-devel@lists.fedoraproject.org