-
Notifications
You must be signed in to change notification settings - Fork 492
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
Still maintained? #118
Comments
We use mina to deploy a lot of apps. I'm willing to help mantaining it. Please @luislavena let me know if you decide to work on your fork! |
@marcosbeirigo I've sent some pull requests around 0.2.x codebase (#123) Since we need several of the patches we sent, I've pushed 0-2-stable branch in our fork: https://github.com/area17/mina/tree/0-2-stable Hope that helps. |
@luislavena, we have neglected maintaining the project for quite some time now. But we'll be finding some time to work on it in the next few weeks. |
@mikong thank you for your response and looking forward for the merges! ❤️ ❤️ ❤️ |
❤️ |
The last commit was 8 months ago. Is this project still maintained? :( |
Given the community interest and the lack of merges, I think not. Let's rally around one of the forks and carry the banner from here on out. I'm glad to fork the project and head it unless someone else would be interested. Let's have a discussion here and see how we want to proceed. |
Hi @luislavena @julian7 @fnando @chernesk, as @rstacruz announced on #181, we've started maintaining the project from today :). We will soon release a new version, clean up the open issues/PRs and open more communication channels towards making Mina even better! :) Thanks for reaching out and please spread the voice that the project is alive 💃!! |
Hello,
I see several issues and pull requests that remain without comments (or not merged) for quite some time.
Just yesterday sent two to solve rbenv #106 (pull #117) and 1.9 hash usage #116
Is this project still maintained?
Please let us know so I can work directly on the master of our fork and use that instead.
Thank you.
The text was updated successfully, but these errors were encountered: