{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Release Engineering (SIG/Core) Wiki","text":""},{"location":"#about","title":"About","text":"<p>The Rocky Linux Release Engineering Team (also known as SIG/Core) dedicates themselves to the development, building, management, production, and release of Rocky Linux. This group combines development and infrastructure in a single, cohesive unit of individuals that ultimately make the distribution happen.</p> <p>The \"SIG/Core\" reference name is not a strict Special Interest Group (as defined by the Rocky Linux wiki).</p> <p>The general goals (or \"interests\") is:</p> <ul> <li>To ensure Rocky Linux is built and released in a complete and functional manner</li> <li>To ensure proper collaboration and development of the Peridot Build System</li> <li>To ensure all users, developers, and Special Interest Groups are have a solid, stable platform to build upon</li> </ul>"},{"location":"#mission","title":"Mission","text":"<p>Release Engineering strives to ensure a stable distribution is developed, built, tested, and provided to the community from the RESF as a compatible derivative of Red Hat Enterprise Linux. To achieve this goal, some of the things we do are:</p> <ul> <li>Ensuring a quality and fully compatible release product</li> <li>Developing and iterating on the build systems and architecture</li> <li>Developing all code in the open</li> <li>Setting the technical direction for the build system architecture</li> <li>Release of beta and final products to the end users and mirrors</li> <li>Release of timely updates to the end users and mirrors</li> </ul> <p>See the What We Do page for a more detailed explanation of our activities.</p>"},{"location":"#getting-in-touch-contributing","title":"Getting In Touch / Contributing","text":"<p>There are various ways to get in touch with Release Engineering and provide help, assistance, or even just ideas that can benefit us or the entire community.</p> <ul> <li> <p>Chat</p> <ul> <li>Mattermost: ~development on Mattermost</li> <li>IRC: #rockylinux and #rockylinux-devel on libera.chat</li> </ul> </li> <li> <p>RESF SIG/Core Issue Tracker</p> </li> <li>Mail List</li> </ul> <p>For a list of our members, see the Members page.</p>"},{"location":"#resources-and-rocky-linux-policies","title":"Resources and Rocky Linux Policies","text":"<ul> <li>RESF Git Service</li> <li>Rocky Linux GitHub</li> <li>Rocky Linux GitLab</li> <li>Rocky Linux Image Guide</li> <li>Rocky Linux Repository Guide</li> <li>Rocky Linux Release Version Guide/Policy</li> <li>Special Interest Groups.</li> </ul>"},{"location":"#general-packaging-resources","title":"General Packaging Resources","text":"<ul> <li>RPM Packaging Guide</li> <li>Fedora Packaging Guidelines</li> <li>Basic Packaging Tutorial</li> </ul>"},{"location":"members/","title":"Members","text":"<p>ReleaseEngineering(SIG/Core)isamixofDevelopmentandInfrastructurememberstoensureahighqualityreleaseofRockyLinuxaswellastheuptimeoftheservicesprovidedtothecommunity.Thecurrentmembersofthisgrouparelistedinthetablebelow.SomemembersmayalsobefoundinvariousSpecialInterestGroups,suchasSIG/AltArchandSIG/Kernel.</p>RoleNameEmailMattermostNameIRCNameAffiliationReleaseEngineeringCo-LeadandInfrastructureLouisAbellabel@rockylinux.org@labelSokel/label/SombraIndependentReleaseEngineeringCo-LeadMustafaGezenmustafa@rockylinux.org@mustafamstgIndependentReleaseEngineeringandDevelopmentSkipGrubeskip@rockylinux.org@skip77CIQReleaseEngineeringandDevelopmentSherifNagysherif@rockylinux.org@sherifIndependentReleaseEngineeringandDevelopmentPabloGrecopgreco@rockylinux.org@pgrecopgrecoIndependentInfrastructureLeadNeilHanlonneil@resf.org@neilneilCIQInfrastructureLeadTaylorGoodwilltg@resf.org@tgotgIndependent<p>Note</p><p>SomemembersofReleaseEngineeringmaybeaffiliatedwithasponsoroftheRockyLinuxprojectortheRockyEnterpriseSoftwareFoundation,
