Call for maintainers

[zol]

Since I'm no longer actively developing an app that uses migrations, I've lost touch with the codebase and the project. I'm looking for folks to take over development and maintenance, please raise your hand if you're interested.

[npu3paka]

I can continue if you want to. I will make sure it will work with the latest version with no problems.

[zol]

Thanks! I'll add you as a collaborator to the repository.

[npu3paka]

Thank you man :)

[emmanuelbuah]

I'd like to help but interested in making an node npm package that can be used in a none meteor project. Let me know if its possible with the current standing and if not, I'd be happy to turn it into an npm package for generic node application without dependency on meteor.

[hexsprite]

@zol I'm still using this package, would be happy to help maintain.

[zol]

@emmanuelbuah Turning this into an Npm package would be great but I fear probably tricky to do well because of the tight Mongo dependency.

[zol]

Thanks for helping out @hexsprite . I've added you to the repo.

[emmanuelbuah]

@zol Totally agree. I already forked and made the changes for an npm package. I will publish it in a few. I think a plug-in architecture can be implemented with ease to support other storage types.

I looked at other migration packages such as https://github.com/okv/east (with pluggable storage) but decided to convert your package into an npm package due to the auto migration (forward or backwards) nature. Most of the migration packages out there require explicitly using an up or down/rollback API to perform migration instead of auto detecting and migration to the right version based on the current version.

[zol]

@emmanuelbuah Awesome, thanks for working on that!

[hexsprite]

@emmanuelbuah maybe this package can be refactored to use the npm package as a dependency instead then...

[emmanuelbuah]

Certainly. I will let you know when I check in my changes. 

Emmanuel Quame Buah

https://twitter.com/emmanuelbuah

On Wed, Oct 12, 2016 at 12:26 PM Jordan Brant Baker

<
mailto:Jordan Brant Baker notifications@github.com

wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

https://github.com/emmanuelbuah
maybe this package can be refactored to use the npm package as a dependency instead then...

—

You are receiving this because you were mentioned.

Reply to this email directly,
#59 (comment)
, or
https://github.com/notifications/unsubscribe-auth/AAaaGJiOOvkoDdouiOKFEJ8_z0bdEbNWks5qzRhVgaJpZM4IM7Ry
.

[emmanuelbuah]

Hi, sorry this took much much longer than expected. Finally got around to it. I have refactored the package and published it at https://www.npmjs.com/package/mgdb-migrator and https://github.com/emmanuelbuah/mgdb-migrator. Cheers!

[juliedavila]

Curious, since @hexsprite and @npu3paka have become maintainers (assumed from this thread) why is this issue still open and why is there still a call for maintainers on the README?

[emmanuelbuah]

Close away!

[dburles]

@emmanuelbuah nice work, happy to put a link to your version in the readme

[emmanuelbuah]

Sure. Thanks. Let me know if there's anything else I can do to help

…

On Wed, Jul 26, 2017 at 6:38 PM David Burles ***@***.***> wrote: @emmanuelbuah <https://github.com/emmanuelbuah> nice work, happy to put a link to your version in the readme — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#59 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaaGOjO3mH1KuyadLLsuiIBOn5-yjHMks5sR84QgaJpZM4IM7Ry> .

[dburles]

Thanks, will close the thread for now