pagure issue tracker needs to be shut down #59
Labels
No labels
category
budget
category
docs
category
limesurvey
category
meta
category
physical events
category
swag
category
virtual events
Q1
Q2
Q3
Q4
charter
ambassadorship
charter
events
charter
recognition
good first issue
help wanted
needs
event report
needs
reporter feedback
needs
vote
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
team
advocates
team
ambassadors
team
commops
team
council
team
design
team
docs
team
g11n
team
marketing
team
mindshare
team
websites-apps
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mindshare/tickets#59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If one goes to https://pagure.io/mindshare, it's clear that that repo is No Longer The Place.
However, if you land at https://pagure.io/mindshare/issues from a bookmark, link somewhere, or web search, it's not at all apparent.
All of the issues from that tracker should be migrated if they're not already, and issue-tracking disabled for the project.
I kinda forgot this was a thing but you can actually set Pagure issue trackers to read-only so it preserves existing issues but disallows creation of new ones - so that's set now. We should go through the open issues remaining in pagure and close them or move them (probably close them all, none of them have been updated in over a year), but at least noone can file a new one now.
assigned to @jwflory
This repository was established before we had the Pagure to GitLab export tool by @gridhead. The completion criteria for this issue is to either close or migrate the remaining issues open on Pagure to this repository. Once those 15 issues are closed out, we can re-set the Pagure repository to read-only. For archival reasons, the Pagure issue tracker should not be disabled because it will hide the historical discussion and decisions made by the Committee in that repository.
Thanks for taking care of this @pbokoc.
I can take up the task of getting the 15 issues closed out. I might as well draft a community blog announcement post that the tracker has moved and ask the community to refrain creating new issues on pagure.
added 1 design
This is now done. Closing as complete. 🎬