-
Notifications
You must be signed in to change notification settings - Fork 54
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
Looking for help in maintaining this project #26
Comments
I'm using activeadmin-globalize in a few projects and I don't see myself leaving it anytime soon, Would you mind listing the issues you want resolved for a 1.0.0 release? I'm guessing #4, but anything else? |
@mauriciopasquier thanks for your interest. I think that the most important thing is to fix #4, and may verify and fix #5. Also there are a couple of interesting pull requests, but I didn't had the time to review them, some of them are trivial to merge. |
Ok, I'll start digging there then. |
Hey @fabn, I would love to collaborate, as @mauriciopasquie, I also use Active Admin + Globalize in my current project. Let me know where I can start helping! |
Same things as above, there are some PR to review and code should be update to work with latest version of involved gems. I can add you as collaborator to this repo if you wish. Once some code is fixed to work we can potentially release a new gem version to be present on rubygems.org |
Great, @fabn! I could start reviewing PR#28 for example |
Sorry all, I started digging into this but unexpectedly my projects migrated to mobility instead of globalize, so I had to drop it. |
Currently I do not have much spare time and not using AA+globalize anymore in my active projects.
It would be nice to fix current issues now that AA has released a stable version there's room for improvements in this project too.
If someone want to help please and become a maintainer for this project please contact me.
The text was updated successfully, but these errors were encountered: