Skip to content
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 as abandoned #39

Open
marcandre opened this issue Oct 21, 2020 · 2 comments
Open

Mark as abandoned #39

marcandre opened this issue Oct 21, 2020 · 2 comments

Comments

@marcandre
Copy link

It looks like this project has been abandoned.

If so, please update the README.

@anatol
Copy link

anatol commented Apr 15, 2021

Yeah, it does not work with ruby 3 :(

@e2
Copy link
Owner

e2 commented Apr 15, 2021

I'd appreciate a PR that makes the readme say what you want to say. (Or solves the problem you're having).

Here was the thinking behind this project:

  • reporting vulnerabilities in the interpreter itself (not many vulnerabilities anymore, Ruby is usually packed or deployed in buildpacks that take care of vulnerabilities)

  • encouraging people to migrate away from Ruby 1.8, so open source developers don't waste their lives slaving away to backport all new code to Ruby 1.8, just because some corporation doesn't want to spend any money and wants free support (those companies should've gone with Java or COBOL instead, and not manipulate the Ruby open source community to pay for their own business incompetence)

  • finding a way to have the reporting be part of the gem development process (which didn't work out well, because it was a "chicken and egg" problem)

I appreciate you all for caring about Ruby 3.0 support! It's people like you who helped made this project obsolete and I'm happy for it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants