For a Rocky Linux Special Interest Group (SIG) developing RPM packages, identify the required directory structure for source files within the `src` subgroup in GitLab. Additionally, determine the expected branch naming conventions for managing multiple versions of a project across different Rocky Linux releases within GitLab.
Navigate to 'https://docs.rockylinux.org'. Click on the 'Guides' link in the main navigation. Locate and click on the 'SIG Guide' or a similarly named guide related to Special Interest Groups. Within the 'SIG Guide', find the section related to 'Importing to the Rocky Linux GitLab'. Identify the 'RPM Format Rules' subsection and extract the required directory structure for source files. Identify the 'Branch Names' subsection and extract the expected branch naming conventions for multiple versions and projects. Synthesize the information on source file directory requirements and branch naming conventions into a concise answer.
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).