On Wed, Dec 18, 2024 at 12:55:07PM +0000, Davide Cavalca wrote:
MkDocs (https://www.mkdocs.org/) is a Markdown-based website maker, geared towards technical documentation. The CentOS Project has historically used MkDocs for SIG documentation, and the CentOS Docs SIG has recently standardized on MkDocs for the overall project, leading to the creation of a collated documentation site at https://docs.centos.org (sources: https://gitlab.com/CentOS/docs/docs.centos.org).
To ease this work, I've been working on getting the MkDocs stack back in shape in Fedora, with the goal of eventually branching it for EPEL 10. Because MkDocs is quite sprawling, I'd like to setup a lightweight SIG around it to ease package maintenance of the stack. By "lightweight" I mean that I expect this will mostly be used for package ACLs and bug triage. While I mostly expect folks from the CentOS Docs SIG to join in, this is by all means open to anybody interested in collaborating.
For completeness, this is the infra request
https://pagure.io/fedora-infrastructure/issue/12337
cc Packaging group to see if we should consider making the process of creating a new SIG better documented
FESCo has a policy document on specific SIGs' rules https://docs.fedoraproject.org/en-US/fesco/SIG_policy/
but the only document I see for creating a SIG is still only a wiki page
https://fedoraproject.org/wiki/Creating_a_Fedora_SIG
Best regards,
packaging@lists.fedoraproject.org