We’ve had several contributors ask to move to GitHub or Gitlab as they find Pagure hard to use. Unless there is a concerted effort to improve the areas where Pagure is lacking, I propose to move the issues and docs sources to GitHub. It would then look like this: https://github.com/fedora-silverblue
The issues were initially put on Pagure because there was too much pushback to have them on GitHub. Fedora’s new strategy also means it is easier to use those building blocks that make sense and not use those that don’t.
This would mean that issues, docs, and website are all in one place. Other than that, there is only Twitter, IRC, and this forum which makes it easy to find things rather than have them scattered. Further down the line, when the website team has time to pick it up, the website should be just a redirect to a Silverblue section on https://spins.fedoraproject.org/. On that spin site, there should be just be links to the Discourse forum, an introduction to what Silverblue is, the docs link, and additional static resource links. The documentation is where the explanations should happen.
The long-term proposal is as follows:
- have docs and issues on GitHub to make it easy to use and discoverable, contributors benefit from a boost in their GitHub profile
- have the subdomain redirected to a Silverblue section on Fedora spins once the website team can pick it up (this ensures that the download links will always be up-to-date)
The documentation continues to live on the official Fedora documentation, only the source will be on GitHub. This also makes it easier for new people who do not have solid git knowledge to contribute to the documentation as most git tutorials cover GitHub whereas Pagure has an additional learning curve on its own due to its unfamiliar UX and missing features.
Please vote in this poll only if you are interested in using Silverblue, already using it, and/or intend to contribute to the documentation or issue tracking.
- move docs and issues to GitHub
- stay on Pagure with docs and issues