Skip to content

[RFC] Repository Archive Check-list #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gsteel
Copy link
Member

@gsteel gsteel commented Nov 8, 2024

Initial rev of a check-list for archiving repositories

Signed-off-by: George Steel <[email protected]>
@gsteel gsteel added Documentation Improvements or additions to documentation Review Needed RFC labels Nov 8, 2024
@froschdesign
Copy link
Member

Suggestion for the documentation theme:

Abandoned

(based on the site name)

koka500000

This comment was marked as spam.


## Close all existing PRs and Issues

Once the pull request has been merged, close all open issues and PRs, and ideally, leave a comment with a reason for the closure such as: "This library/project has been abandoned".
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this necessary? Archiving the repo already prohibits new replies 🤔

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My opinion is that it's decent to let whomever opened the PR/Issue know that it's not getting fixed/merged. I don't think it's necessary per se

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements or additions to documentation Review Needed RFC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants