As agreed upon yesterday on out meeting, let’s discuss how to migrate our pagure repo to forgejo.
Based on my current knowledge, I would suggest initially aiming for the following structure:
repo: wg-conducts The subject matter is the ongoing completion of our tasks and projects. Data includes, in particular, tracking issues and long-term (sub)project planning and discussion.
repo: usrdoc The subject matter is the maintenance of our user documentation articles and, in particular, factual issues and PRs (https://docs.fedoraproject.org/en-US/fedora-server/). We should separate this from our WG documentation, which we currently maintain in a shared repository. The workflows are very different.
repo: wgdoc The subject here is the text of our WG documentation (https://docs.fedoraproject.org/en-US/server-working-group/). We should not maintain this together with our user documentation in one repository. It may be useful to merge these into the wg-conducts repo.
repo: ansiblesupport The subject here is our Ansible scripts for supporting the administrative installation and maintenance of various Fedora Server Services.
I think that's what we need first and foremost. And for each repo, we then have to look for ways to meet our requirements, e.g., notifications for new issues or commits, formatting a preview for documentation pages, etc.
If we start our Homelab Server Appliance project we may create another repo for that.
The migration tool does not offer any way to modify the repository to be migrated. This must be done either before or after using standard Git procedures.
Let's discuss the plannings so that we can decide on the best course of action at next week's meeting and then get started right away (and let’s get the naming and wording right).
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast
server@lists.fedoraproject.org
-
Peter Boy