From Fedora Project Wiki

(Created page with "= Overview = == Name == The name El Niño project suggested by Stephen Gallaher. It contains "enterprisy" reference but also highlights the fact that it is a place for perma...")
 
(Update the name explanation.)
Line 2: Line 2:
== Name ==
== Name ==


The name El Niño project suggested by Stephen Gallaher. It contains "enterprisy" reference but also highlights the fact that it is a place for permanent work in progress for experimenting and development, rather than a finished product.
The name of the EL Niño project was suggested by Stephen Gallagher. It contains "enterprisy" reference but also highlights the fact that it is a place for permanent work in progress for experimenting and development, rather than a finished product.
 
=== Explanation of the puns ===
* The "EL" is a reference to the distribution tag for RHEL/CentOS: "EL" stands for Enterprise Linux.
* The Niño portion is the Spanish word for "child (male)". The implication of this reference is that the project should always represent the "immature" version of what will "grow up" into Enterprise Linux.
* Collectively, "El Niño" is also the name of a type of weather pattern that often brings storms with it. The meaning here should therefore be fairly obvious!


== Purpose ==
== Purpose ==

Revision as of 21:25, 2 March 2020

Overview

Name

The name of the EL Niño project was suggested by Stephen Gallagher. It contains "enterprisy" reference but also highlights the fact that it is a place for permanent work in progress for experimenting and development, rather than a finished product.

Explanation of the puns

  • The "EL" is a reference to the distribution tag for RHEL/CentOS: "EL" stands for Enterprise Linux.
  • The Niño portion is the Spanish word for "child (male)". The implication of this reference is that the project should always represent the "immature" version of what will "grow up" into Enterprise Linux.
  • Collectively, "El Niño" is also the name of a type of weather pattern that often brings storms with it. The meaning here should therefore be fairly obvious!

Purpose

  • Create infrastructure and tooling, which allows experiments with the build process of Fedora distribution.
  • Use this infrastructure to build Fedora packages in the way which resembles the CentOS and RHEL process and provide feedback loop for Fedora maintainers.
    • Events like "package can not be built" or compose failures will be reported to maintainers involved.
  • Some other features (like CPU update) can be incorporated into the same build process if they can be tested in parallel. New feature requests will be approved by El Niño SIG under general supervision of FESCo and Fedora Council.

Scope

While originally we named this project as "Alternative buildroot", its scope includes the entire process of how the Fedora sources are built and composed into the shippable artifact.

This includes:

  • buildroot configuration, rpm macro and compile flags,
  • comps files and the compose content,
  • compose itself and the pipeline which builds it.

Under this umbrella we are going to have:

  • disttag which allows to tweak rpm spec files,
  • Koji tag which allows to control the buildroot,
  • fork of the pungi configuration which describes the compose
  • pipeline which builds periodic compose based on that configuration
  • storage for such composes and additional pipelines which will verify the quality of the compose and test additional scenarios on top of it.

Stakeholders

Who benefits from the implementation of this feature:

  • Fedora Infrastructure
    • As we are going to try and test new infrastructure for composes.
  • Fedora Minimization
    • As we are going to modify the compose content according to minimization goals.
  • CentOS Stream, EPEL and RHEL
    • As we are going to try to build Fedora packages into the multi-repo structure of the compose similar to the one from CentOS and RHEL.
  • Fedora Community
    • The feedback pipelines build for the project will allow downstream developers to open up their work and bring it closer to Fedora.
    • The tooling developed for this project will allow development of the changes in Fedora Infrastructure without blocking the regular Fedora packaging and release process.

Tools

Disttag: eln

El Niño packages are going to be build directly from the same code as Fedora Rawhide. There still might be cases where the change in the spec will be required. For this cases we would like to reserve the disttag (eln) and the associated conditional in the RPM spec file.

SIG

    • El Niño SIG** is going to be responsible for the project and the infrastructure for it.

Responsibilities

  • Own the scope of the eln disttag.
    • As the project evolves the scope might change. There might be additional features which will be included into the tag or excluded from it.
  • Own the configuration of the compose.
  • Maintain infrastructure required to build packages and composes.
  • Track the status of package builds and composes. Work with Fedora package maintainers to resolve the issues.
  • Keep track of the eln-conditionals in RPM spec files.

Members

Resources

Taiga board:


Links

Retrieved from "https://fedoraproject.org/w/index.php?title=ELN&oldid=567323"