-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Maintainers Needed - please read #169
Comments
Hi, /Johan |
What's the maintainer-ship of this project now? Is @JohanObrink doing it, or are you still looking for help? |
@JohanObrink has offered to help out but the more help we can get the better. Are you interested? |
Yeah, but I'm not sure how much time I'll be able to commit to it. I'll can try to help where I can. |
I'd be more than happy to lend a hand too |
The thing I need most help with right now is working through the pull requests in two areas. First, verifying the pull request works and has appropriate testing. And second, should the pull request be incorporated. The project is used by enough people now that I don't want to be the sole person deciding what features are in or out. Would you guys mind briefly looking through the pull requests and commenting with you opinions on the value of each one? Would it be generally useful? Does it make the code too complex? Etc. That would be incredibly helpful to me and greatly appreciated. |
Hi together, I'm currently working on a project called umigrate. It's a reverse migrator with diffing capabilities and should provide migration abilities by itself. For this purpose this project is wrapping db-migrate currently and I intend to to keep db-migrate as the migrator. Thats the reason why I would also be interested in maintaining this project, but more then actively developing at it and pushing it forward. Currently db-migrate is missing travis, a code style definition and has outdated dependencies/docs. These are things that should be added. I especially would need to know the code style, to format the code correctly for this project. @kunklejr |
@kunklejr Is there currently anyone maintaining this project? It seems to be pretty dead right now :/ |
@wzrdtales Please see your email for a message I just sent you. |
@kunklejr thanks, have answered you. |
Over the past year or so,
db-migrate
has become a relatively popular project in the node community. Its popularity and the associated community demand have outpaced my ability to maintain it at a level I can be proud of and that it deserves.When the project was initially created I was using node and db-migrate every day, making it really easy to add new features, fix bugs, etc. However, my job changed about a year ago and and node was no longer part of the job description. For a long time (too long) I held on to the notion that I could keep up with things on nights and weekends, but life kept getting in the way. Helping my kids with schoolwork, coaching my sons' sports teams, ramping up on the new job, and hanging out with my wife once in a while ate up all that time. And I've finally realized that none of that is going to change.
It's not fair to let everyone's effort to report issues and submit pull requests fall prey to my selfish desire to hang on to my most popular project. I truly appreciate all the interest and contributions to the project, even if my slow response implies otherwise. But now it's time to make a change.
So today I'm asking for volunteers to officially help maintain the project. I'm not asking anyone to take over the project right away. A small group of people who commit to helping when they can is probably a good start, and certainly needed to ensure the project remains healthy and useful to the community. So if you have the time and are interested, please let me know.
Thanks,
Jeff
The text was updated successfully, but these errors were encountered: