almalinux.org icon indicating copy to clipboard operation
almalinux.org copied to clipboard

Poposal: post on fostering community discussions on reshaping AL

Open xsub opened this issue 2 years ago • 3 comments

We are still in discussions about how the future policy of the Synergy repository should look.

At the same time, I want to gather the best ideas from our users regarding the future of AlmaLinux OS.

I believe the simple format presented in this blog post, written for transparency, can be continued. This will facilitate discussions on Reddit and maintain a chronological history of topics in the form of articles on the blog, each informing about a specific ongoing discussion.

This is just an example and can be reshaped into what you would like it to be (if we decide to do it).

The aforementioned Reddit post is about to be written (today).

@bennyvasquez @jaboutboul @jonathanspw @codyro, WDYT?

xsub avatar Sep 06 '23 09:09 xsub

The blog post is missing Hugo front matter, so the preview won't work.

I am a proponent of this idea, although I would like some clarifications:

Would you find it beneficial to include [Emerging Technology] in the Synergy Repo? (poll)

This isn't mutually exclusive with the top two questions. The emerging technology could already be packaged upstream/EPEL. Why are we forcing the Synergy repo here? Is the intent of this series to bootstrap the Synergy repo?

Your input will help us better align the Synergy Repo with your needs, from enterprise solutions and scientific research to emerging technologies like IPFS. We believe that AlmaLinux is not just another OS, but a platform tailored to your exact requirements.

The answer to my above question appears to be "yes".

We're trying to run before we walk. I shared similar sentiments in https://github.com/AlmaLinux/releng/issues/1. Before we start running with this Synergy repository and making these unilateral/core changes, let's figure out what the Synergy repo is and how it functions within AlmaLinux before we start a full-blown series around it.

codyro avatar Sep 06 '23 15:09 codyro

We're trying to run before we walk. I shared similar sentiments in https://github.com/AlmaLinux/releng/issues/1. Before we start running with this Synergy repository and making these unilateral/core changes, let's figure out what the Synergy repo is and how it functions within AlmaLinux before we start a full-blown series around it.

I agree with this wholeheartedly. Synergy repo is cool, but in many cases what's being done with it thus far doesn't make much sense.

I'm going to continue my broken record speech that things that are candidates for EPEL should go to EPEL and Synergy should be reserved for things that are not good candidates for EPEL anyway. Synergy doesn't need to be this random mashup of whatever X maintainer is feeling like doing on a given day. It should be carefully curated and maintained long term so careful thought needs to be put into what goes into it.

There are a lot of questions to be answered such as:

  • Who oversees what goes into Synergy?
  • Who can contribute to Synergy?
  • What can go into Synergy?
  • How can the community at large submit packages to Synergy?
  • How do we handle CVEs in Synergy?
  • What is the policy on breaking changes/updates in Synergy?

and many more...

jonathanspw avatar Sep 06 '23 15:09 jonathanspw

I think this feels more structured than I would want to see around this kind of conversation, but maybe I'm wrong. I think I want to start with a simple post on Reddit or the forums and see how things evolve from there.

bennyvasquez avatar Sep 06 '23 15:09 bennyvasquez

Closing for now, since this wasn't really the right place for this conversation anyway. We should pick this conversation back up elsewhere as we can!

bennyvasquez avatar Apr 23 '24 20:04 bennyvasquez