-
-
Notifications
You must be signed in to change notification settings - Fork 931
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
Mark gem as archived #4960
Draft
colby-swandale
wants to merge
10
commits into
master
Choose a base branch
from
colby/archive-flag
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Mark gem as archived #4960
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4960 +/- ##
==========================================
- Coverage 97.01% 96.87% -0.15%
==========================================
Files 420 422 +2
Lines 8724 8776 +52
==========================================
+ Hits 8464 8502 +38
- Misses 260 274 +14 ☔ View full report in Codecov by Sentry. |
colby-swandale
force-pushed
the
colby/archive-flag
branch
from
August 19, 2024 03:41
6e9b8fd
to
df83f08
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's this about?
Many of our older users in rubygems.org currently own gems they no longer wish to be responsible for. The way users have approached this issue is typically been:
We want to encourage users to keep projects alive by passing it to new owners, but often users wish to close the book entirely and move on. Which is understandable, but in this particular scenario, we want to encourage owners to keep their code published on rubygems.org, but we presently don't have a way to indicate to users that a gem is no longer being maintained.
This Pull Request is adding a new feature to allow gem owners to mark their gem as archived and notify users this gem will no longer receive any new updates.
User Story
Archiving a gem
When a user wishes to archive their gem, they can do so by logging into their rubygems.org account, navigating to their gem page and clicking on the "Archive gem" link. This will take the user to a confirmation page that will explain what happens to the gem when it has been archived:
If the owner decides to continue, the owner can click confirm and the gem is then marked as archived.
All owners will receive a confirmation email from rubygems.org notifying that the gem has been archived.
Unarchiving a gem
Of course, if the owner decides to reverse their decision, they have the option to unarchive their gem by navigating to the gem page and clicking on the "Unarchive gem" link.
Once processed, the gem will no longer display a notice message, new owners can be added & new versions can be published.
All owners will receive a confirmation email from rubygems.org notifying that the gem is no longer archived.
Screenshots