-
Notifications
You must be signed in to change notification settings - Fork 12
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
Would you consider allowing the LevelUP team to take over "leveldb" in npm? #52
Comments
👍 |
I am all for this. This repo started mainly to merge several peoples forked versions of the original source so thy I could use their various ideas. The big question is how do we move the stuff? The source is easy as you can just fetch and merge to yours or new repo which ever is eaisier for you and I can put a note on mine to point people to the new location. NPM looks like I can simply add a new owner, just need to know the new name. From their the new owner can upload new builds etc. Given that it seems the "done" state for this issue is getting me an NPM user name to add. Once access is verified the rest is easy. |
@my8bird great! If you |
Done, I will still be here so don't be shy if you need something On Sun, Apr 20, 2014 at 10:45 PM, Rod Vagg notifications@github.com wrote:
Hanlon's Razor - Never attribute to malice that which is adequately |
Since keeping up with V8 and Node changes is quite a challenge and we have a very active community around the LevelUP (JS) and LevelDOWN (C++) packages exposing LevelDB in Node perhaps you would consider allowing us to start publishing code under the "leveldb" name in npm? We get occasional bug reports about people trying to install our packages but using "leveldb" instead. There's also people new to the ecosystem who just pick the name because it's logical (e.g.).
We would bump the major version and leave historical releases intact for anyone that might still have old systems using working versions of this code.
Cheers.
The text was updated successfully, but these errors were encountered: