Now that the Silverblue train is chugging along, would it be smart to rename this repo to be more Silverblue-specific?
The current name doesn't really lend itself to being discoverable by folks who want to hack on/contribute to Silverblue.
i don't disagree, but let's keep it where it is until we are out of freeze on the fedora side of the house.
can you bring this back up when we are out of beta freeze?
I think the main problem here is that Pagure doesn't support renaming repositories (while preserving issues/PR history etc.).
yeah I thought about that, but i don't know if we should worry too much about the issues/PR information here. preserving git history, yes, which we can easily do by importing this git history into the new repo.
Makes sense to me
ok, I was going to say that we should go ahead and do this, but looks like renaming a repo is an outstanding RFE against pagure so unless we want some pain, let's leave it as-is for now.
https://pagure.io/pagure/issue/2103
Given that: - Pagure development has slowed down, - the issue blocking repo rename is still open, - we're now using this repo for rpm-ostree deskopt variants and not just for Silverblue, I'm closing this issue even thought the repo names does not exactly match the content.
I've opened https://github.com/fedora-silverblue/issue-tracker/issues/334 to discuss moving this repository to another location. We could then do the rename as part of the migration.
Metadata Update from @siosm: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.