Moving to Meteor Community

HI @raix! I’d like to help maintain the Ground DB project, since I use it in just about every project I work on (and have incorporated it into my npdev:collections package). I don’t actually think it needs much work to keep it updated - mostly just needs someone to merge PR #211 and do a release.

To that end, would you be open to migrating the project to the Meteor Community Packages group? The idea is that once there, we can get a set of reliable professionals to help with that sort of maintenance. For this project (and perhaps the ones on which is relies) I’d be happy to take point.

I look forward to hearing from you. By the way, I’m happy to chat here, or via email or Slack (we have a Meteor Community Slack channel), or any other way about any of this.

[copleykj]

@raix If you want to just go ahead and transfer all of them to @Meteor-Community-Packages org, one of us will take care of setting up teams and what not. The only other thing we’ll require you to do is add the communitypackages Meteor org as a maintainer meteor admin maintainers <package name> --add communitypackages

[CaptainN]

Any more thoughts to this? I’d like to get at least the few updates I have in there already released, since they are not blocking updating core components (like mongo and minimongo) to the latest versions in projects that use this. I’d be happy to work in this group directly. Whatever you like.