-
Notifications
You must be signed in to change notification settings - Fork 5
Can we get this pushed up to rubygems as a new gem? #1
Comments
Hey @toddnestor, apologies for the delayed response. I was just waiting to see if the original maintainers add anything on the issue you've just mentioned. Since there has been no action yet from their side, I plan on using the next week to setup this repository as the alternative blueprinter. Pushing to rubygems and updating readme would be the first steps towards that goal. Post that, I'll start accepting PRs and respond to issues and eventually allow more maintainers to the project based on the contributions made - the delay in adding more maintainers would also allow me to setup some basic processes around the project as well. |
Apologies for the delay in making this happen. Have released version 1.0.0 to rubygems 🎉. |
Thank you @ritikesh! |
Thanks @ritikesh, I'm proposing internally that we shift to this one. |
I added it to rubytoolbox/catalog#725 |
Hello, I work at RaiseMe (www.raise.me), we had started migrating from ActiveModel::Serializer to Blueprinter a year or so ago, was disappointed to learn recently that Blueprinter is not really being maintained anymore.
I would love to join you as a maintainer for this new fork and help get blueprinter updated and ensure it works with the latest ruby versions (perhaps it already does, I'm going to be testing soon).
We are so far along in our migration process that I don't want us to change to yet another library, so if we can get this new fork pushed as a new gem and start maintaining it then we will be set up to more confidently complete the migration work in our own codebase.
Let me know your thoughts. I came across this fork from where you had linked to it on the original blueprinter repo's issues.
The text was updated successfully, but these errors were encountered: