As a Rocky Linux Special Interest Group member, I need to understand the guidelines for contributing RPM packages. Find the required directory structure for source files within the `src` subgroup in GitLab, and the branch naming conventions for managing different project versions across Rocky Linux releases. State both.
Navigate to 'https://docs.rockylinux.org/guides/contribute/sig-guide/' On the 'SIG Guide' page, locate the section titled 'Importing to the Rocky Linux GitLab'. Within 'Importing to the Rocky Linux GitLab', identify the 'RPM Format Rules' subsection and extract the required directory structure for source files. Within 'Importing to the Rocky Linux GitLab', identify the 'Branch Names' subsection and extract the expected branch naming conventions for multiple versions and projects. Synthesize the extracted information on source file directory requirements and branch naming conventions into a concise answer.
Successfully navigate to the 'SIG Guide' page. State that the `src` subgroup requires `_` for light text files/scripts, `SPECS` for the single spec file, and `SOURCES` for listing source archives. Describe the expected branch naming conventions, including how they handle multiple versions and projects (e.g., `rX` for Rocky Linux release branches, `rX-Y` for specific versions, `main` for development, and `project-branch` for specific projects).