Move to "level" org?

[rvagg]

I'm a bottleneck and it's holding this project up and I know there are people here who could be pushing it forward if it weren't for me being both the figurehead that people feel they need to look to for permission and also the one with the ability to npm publish.

Is it time we moved this to github/level an put everyone who's a collaborator here on the Owners team there? It would also mean moving leveldown and abstract-leveldown, possibly also lmdb--it's not so core but it could do with some of the love that comes from shared ownership. There's some other modules that I could transfer if others think it's a good idea, for instance I recently handed over publish responsibility for level-ttl to @ralphtheninja and it's in wide use.

Thoughts from collaborators?

[jcrugzz]

Admirable move @rvagg. You have been a hell of a leader in getting this community together and grow as much as it did. I think its quite fitting to make the next step if you truly feel you are holding it back. I know its tough when you are juggling ALL THE THINGS. I'm 👍 on this.

[ralphtheninja]

@rvagg You will always be my hero! :)

👍 Moving stuff to Level organization and having more publishers is a good move.

[No9]

Also 👍
The fact you have the option to give it to the community is vindication of OPEN open source.
Choosing to do so is yet another example of how well you have led our little soirée

Thanks

[nolanlawson]

👍

[dominictarr]

Yes, I agree this is a wise and noble move. The level culture has been well established, and everyone understands how to make decisions by consensus. I don't think it would have worked out as well as it has without your guidance @rvagg and I for one have learnt a lot about collaboration by being involved in level. Excited to see this enter the next phase!

[heapwolf]

👍 Rod Vagg you are the levelup community biological dad. v nice.

[mcollina]

👍 I agree too! Thank so much @rvagg for creating this awesome community, and for proving that OPEN Open Source can actually work :). I am not active myself, and my last contributions are in the leveldown side: @rvagg is the one that said to me "we need more maintainers for the C++ part, you should learn it". So I did, thanks @rvagg :).

[juliangruber]

👍 I couldn't agree more with what Dominic said!

[ralphtheninja]

@rvagg When can you start moving the repositories?

[ekristen]

+1

[rvagg]

@Level/owners I've moved this repo as well as abstract-leveldown and node-leveldown to the level org. While I was at it I also transferred memdown and level-ttl which are effectively maintained by others at the moment as well.

I've added @ralphtheninja to npm so he can publish things and not have me hold things up. I'm not necessarily proposing that he be the release master for all of these packages but he's currently very active here and has obvious concern for these projects so he's a good interm hand-off at least and we can get more organised later on.

I'm sorry to have been such a bottleneck recently, it's not that I've lost interest in this ecosystem and its projects it's that that (a) I'm busy with work and (b) io.js is sucking up all of the remaining time I have and I view that project as vital for the future health of the entire Node ecosystem so it's worth a bit of focus at least for the short term and apparently I have something to add there for now. Perhaps that'll change as things settle down in some form. The node/io.js reconciliation looks to be coming together and if that occurs then the organisational structure will change and the type of activity will too and I don't know where my slot will be there.

Feel free to pull me into GitHub discussions but I'm also trying to control the torrent of GitHub notifications and if you don't hear from me then a direct email or Twitter DM may be a better bet!

[ralphtheninja]

🍻

[juliangruber]

💃 thanks rod :)