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

Parse and display arbitrary gem metadata, controllable by gem owners #637

Closed
bf4 opened this Issue Dec 20, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@bf4
Copy link
Contributor

bf4 commented Dec 20, 2013

Summary:

Wouldn't it be great to tell the world things like:

  • "Please don't download this gem. It is unmaintained. Use this one" or
  • "Looking for maintainers" or
  • "Security policies"

Some proposal details:

We could surface such info on rubygems.org via a conventional key in the gemspec metadata, allowing metadata to be published on demand via the rubygems.org gem edit page, or possibly add a maintainership or maintainer notes field to the gem edit page (e.g. bf4-metric_fu could have a free text field that says, do not use).

Currently, if I need to deprecate a gem, I create a major version release with no content and a post-install message about what to do. e.g. metric_fu-rood v3.0.0 has the post-install message "Please install roodi. It is now being maintained. And gem uninstall metric_fu-roodi. Thanks :)"

Background:

I was recently asked about some gems that I published once, e.g. bf4-metric_fu, but have since deprecated. Because I'm nice, I didn't yank every single version out there. However, if there were a convention to surface the gem status, perhaps with a 'maintainership' key in the gemspec metadata, I could add that to the published gem.

A bonus, is that people programmatically getting info on gems could check if they're being maintained.

A possible integration could be made with the http://stillmaintained.com/ source project

@qrush

This comment has been minimized.

Copy link
Member

qrush commented Nov 28, 2014

This is way too open-ended. Let's pare it down to more concrete features and we'll consider them one by one.

@qrush qrush closed this Nov 28, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment