Transfer to official repo

[simonbengtsson]

Atmosphere currently hosts version 1.3.0 while the library is at 2.0.20. Don't really know what happened, but as the mainter of the official repo I am willing to take over responsibility to publish new versions. Would this be possible?

[chip]

Hey @simonbengtsson - Thanks for following up on this. I think @splendido and I lost momentum on this some time back, so I apologize for that.

One thing to consider is that Meteor 1.3 beta supports NPM modules, so maybe that is an option to consider (as opposed to sticking with the current wrapper approach).

I'd like to hear from @splendido on his thoughts on this. Please LMK how I can aid in this process. Thanks.

[simonbengtsson]

Exciting with npm support! Does that mean that atmosphere will be deprecated?

[chip]

That is an interesting question. I seriously doubt it because there are thousands of packages that are written purely for Meteor in mind as opposed to NPM, but we might see a lot of wrapper packages like this one provide instructions on how to install using npm install package-name instead of via Atmosphere (e.g., meteor add package-name).

[splendido]

@simonbengtsson I think @chip is right, we've defenitely lost momentum. I'm sorry for this too.
I'm more than happy to add you as a maintainer of the package, just let us know your Meteor Developer Account username! (just register on meteor.com if you don't have one already...)

Then you can chose whether to continue using this wrapper package or simply integrate the few needed files on your official repo. Again, just let us know.