Community Update - December 2020

Community Update - December 2020

Summary

Our teams are working to coordinate the many individuals and organizations that have offered to help advance The Rocky Linux Foundation, Inc. (Rocky Linux). The core team is working to lay the infrastructure that will support the legal entity and the engineering efforts required to deliver and support an initial release. Updates regarding project news, release dates, and more will be announced on our forums, website, and other social media platforms.

Timeline

Transparency with the community and for those that will be relying on Rocky Linux to supplant their CentOS 8 installations before support expiration is paramount. We will soon be communicating a timeline for the delivery of the following:

  • Build systems and infrastructure readiness
  • Automatic package build infrastructures
  • When the testing package repository will be made public
  • Installer testing readiness
  • ETA for length of time needed for community testing
  • Release candidate availability

We are targeting Q2 2021 to deliver our first release of Rocky Linux, made available not only in standard commercial regions, but also GovCloud, and China.


Over the past three weeks, here is some of the progress we’ve made:

Infrastructure

  • We have selected and vetted auditing, logging, and user account management tooling.
  • Amazon Web Services (AWS):
    • The team selected AWS as the primary build platform for development of Rocky Linux. AWS was chosen primarily to protect the integrity of the software supply chain for Rocky Linux.
    • Unfortunately, donated hardware and rack space isn’t sufficient to meet our supply chain integrity needs.
    • Traditional physical hardware separate from our production build environment will still be necessary, and we expect a large portion of our infrastructure will exist outside of AWS for the purposes of business continuity, cost, and platform agnosticity.
    • We have outlined an infrastructure to best secure and facilitate our engineering efforts using multiple VPCs, subnets, and regions for high availability.
  • Data Centers:
    • We are negotiating with several data center providers for the secure hosting of our physical infrastructure.
    • After we have our physical infrastructure provider solidified, we will reach back out to those that have offered to donate hardware .
    • Discussions with the Oregon State University Open Source Lab (OSUOSL) regarding resources are in the works.

The core tenets of the Infrastructure Team are:

  • To provide a platform for the automatic and secure builds of packages and components which will allow for community participation without sacrificing security or trust in the resulting packages
  • The integrity of the build pipeline and software supply chain are paramount.
  • Be as vendor and platform agnostic as possible. Avoid vendor lock-in.
  • Be transparent with the community, to the extent possible and practical.

Release Engineering and Packaging

  • The build process for Rocky Linux will use Koji and MBS.
  • We are developing scripts and build tools to create a pipeline that allows pulling sources, debranding, and building through Koji and Mock.
  • The progress of proof of concepts and processes utilized by the Rocky Linux build process, including all errors and dependencies, is being documented in the wiki.

Security

  • The Security team has drafted a Data Classification Policy, which will be made available for public comment pending review.
  • Groups, members, and permissions structures for the build infrastructure have been laid out for review and evaluation.
  • In parallel with the infrastructure team, we have architected and designed AWS network and security topologies aligned with best practices and security standards.
  • Work has started on OpenSCAP documents for popular STIGs.
  • Plans are being made with the goal of Rocky Linux becoming FIPS compliant.

Web

  • In only 12 days, our forums have received nearly 150K page views.
  • Bandwidth to GitHub resources has exceeded the current plan, requiring an upgrade.

Community

  • We have chosen Red Barn Creative Team (formerly Hackerthreads ) as the designated / authorized vendor to sell Rocky Linux branded merchandise. We are awaiting proofs from their designers to present to the community, and will as well be accepting submissions for designs.
  • Over 370 people have responded to our form for registering volunteers and supporters.
  • A blog and mailing list for future announcements and community updates is in development.
  • We have outgrown Slack due to the size of the community and required feature sets, and will therefore be migrating to Mattermost. This open source platform has a number of features we’ll be taking advantage of, including: an IRC bridge, multi-factor authentication, advanced logging / auditing / security capabilities, and fidelity in channel and access permissions.
  • Social media following:
    • 4.3K active members on Slack
    • 169 followers on LinkedIn with 1.3K post impressions
    • 4K followers on Twitter with an average of 22K impressions and 3575 interactions per tweet
    • 3K members in /r/RockyLinux on Reddit.

Special Interest Groups (SIG)

  • We have received a number of requests for SIGs on a variety of different topics:
    • Desktop / Laptop
    • Enhanced Security
    • Kubernetes / Cloud Native
    • Minimal Install / OS Bootstrap
    • Storage appliance
    • HPC and next generation HPC
  • The evolution of a SIG should result in optional package repositories and/or custom installers.
  • We will need leaders for SIGs as well as proposals.
  • Timelines for these proposals will be coming soon.

Note: Rocky Linux is first and foremost a freely available Enterprise Linux clone. SIGs will optionally enhance that base and provide extra packages and capabilities to that stable base. At no point will a SIG affect the default core of Rocky Linux.

Sponsors

  • We have a number of companies who have stepped up to sponsor the Rocky Linux Foundation in the form of developers, hardware, cloud instances, and money.
  • Sponsorship will have different levels, and we are happy to speak with organizations interested in helping.
  • All contributors will be publicly thanked on our website.

Legal

  • The Rocky Linux Foundation, Inc. has been registered as a legal entity in the United States (Delaware).
  • An application for 501(​c)(3) non-profit status will be submitted as we mature and can afford the legal representation to do so.
  • We are considering licensing for our data that will enable the greatest flexibility for our community. At present, the team is leaning towards the 3 Clause BSD license, but community input is welcome on this decision.

Localization

  • A localization category has been created on our forums, with many people interested in helping with translations to a number of languages including Spanish, French, Italian, German, Chinese, Afrikaans, Greek, Turkish, and many more.
  • We will be working to ensure future newsletters are translated to as many languages as possible.

If you have an interest in assisting with translations, please reach out via the localization category of our forums.


Lastly, this wouldn’t at all be possible without you. We’re immensely grateful for the community’s enthusiasm, excitement, and help. Rocky Linux is, and will remain a community-driven effort.

If you would like to contribute to Rocky Linux, please take a moment to fill out our participation form if you haven’t already done so. This form will allow us to expand and gauge interest in teams.

If you have any questions, comments, concerns, suggestions, or would like to help out, please reach out to us via email at: hello@rockylinux.org.

Sincerely,
The Rocky Linux Foundation
https://rockylinux.org

33 Likes

Thanks for the update @jorp, great summary.

Minor nit, can we change the wording of ‘Spring 2021’ to something more internationally consistent? eg. a month or quarter in 2021.

That was a great suggestion and definitely not a nitpick in my book. I’ve edited accordingly, thank you for pointing that out.

GREAT,
thanks for the update.

1 Like

I’m suggesting something that maybe seen as a huge undertake that I don’t know if it’s even possible or at least could prove stable.
A migration script from CentOS 7/8 to our Rocky.

1 Like

@jorp Chinese translation:https://rockylinux.cn/rocky-linux-community-blockbuster-update20201223.html

2 Likes

I’m not a US citizen, and the only thing I know about Delaware is that is one of the few US states that provide lack of transparency on who owns and run a company, as well no way to access official financial statements.

Does the lack of transparency applies also to not-for-profit?

1 Like

Great!!, Thank you for sharing !!!

2 Likes

Thanks for this update. I was not aware of the form, just submitted it. Hope to be part of the (community)team.

1 Like

Hi @Faisal , this is already being discussed in the following thread:

And here:

3 Likes

Awesome. Looking forward to test new release when done.

2 Likes

Our choice of registering in Delaware has nothing to do with wanting to somehow hide officer names from the community, or conceal financial statements. There are many advantages of incorporating in Delaware. You can read about some of those here: https://www.upcounsel.com/why-incorporate-in-delaware

We’re pretty open about who is part of the Rocky Linux Foundation, you can even see all of our LinkedIn profiles linked on the wiki. As for financials, at present we have none. We don’t have a product to sell. It’s an open source effort run by volunteers. We will be using donations to help offset operational costs, which are presently being funded by individual contributions.

Also, non-profits can be searched publicly on the IRS website: https://www.irs.gov/charities-non-profits/tax-exempt-organization-search

Non-profit status enforces financial transparency.
Rocky won’t be there until after filing taxes.

2 Likes

Thank you for translating that for us!

It looks like 501(c)(3) is incorrectly formatted as 501©3.

2 Likes

Thanks for that, I’ve edited the post to reflect the correct format. The markdown engine that Discourse uses seems to automatically format (​c) as ©.

A neat workaround I discovered was pasting a zero-width space between ( and c, and then deleting it.

1 Like

It would be nice with an explicit description of which steps are taken to make sure that a corporate takeover or similar cannot happen (again).

Is there any problem to release Rocky Linux in China ? As soon as it’s a free and open software, it shouldn’t be a problem

Good question. Our build platform is going to be in AWS. In AWS there are commercial regions such as us-east-1, eu-west-1, etc., and there are ‘closed’ regions that don’t have any access to commercial. GovCloud and China are two such regions. So what we’re saying is that we intend to not only deploy Rocky to the standard commercial regions, but to GovCloud for our ITAR friends and to China for those folks over there.

Do you plan to self-manage it or work with a third-party foundation/compagny ?