Skip to content
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

Future of Tiny-lr #96

Closed
elwayman02 opened this issue Oct 1, 2015 · 8 comments
Closed

Future of Tiny-lr #96

elwayman02 opened this issue Oct 1, 2015 · 8 comments

Comments

@elwayman02
Copy link
Collaborator

Given that this project just went through what is apparently at least it's second almost-abandonment in the last few years, can we bring more contributors on board as maintainers who can manage releases for this project? The fact that it took 3 months after the npm v3 hotfix was merged to cut a release for it was a serious problem for a lot of projects (tiny-lr averages over half a million downloads each month).

I made my own fork, mini-lr to be a stand-in npm@3-compatible release in the meantime, but I'm not planning to continue that fork if we can be confident that the main project will be maintained moving forward. I'm not suggesting that I necessarily become a maintainer, either...I'd be happy to do so if you felt that was the right move, but given that only two people have more than 2 commits in the entire project, it's hard to say that anyone has the right knowledge to help maintain the project.

Regardless, something needs to be done to make sure this doesn't happen in the future. Thoughts? Pinging @shama as seemingly the only maintainer who is still around these days.

@shama
Copy link
Collaborator

shama commented Oct 1, 2015

Sorry about that! I am now watching this repo and dedicating more time to maintaining it. Feel free to ping me in an issue or call me out on https://twitter.com/shamakry if I'm ever being slow.

I think adding additional maintainers to prevent hold ups in the future is a good idea. It sounds like you are interested in at least having commit and publish access @elwayman02. @mklabs if you wouldn't mind, could you add him as a collaborator?

I understand we are all volunteers and our lives are more important than open source. So I don't think any individual should be held responsible to maintain a library. But we can mitigate that by continually opening a project to new contributors who currently have capacity and drive to help.

@elwayman02
Copy link
Collaborator Author

👍 not trying to call anyone out, it happens. Just working for a way forward to keep the project alive :)

ro0gr pushed a commit to ro0gr/ember-cli that referenced this issue Oct 3, 2015
An npm@3-compatible release was finally cut on the main project, so the fork isn't needed, pending the resolution of discussing the future of tiny-lr here: mklabs/tiny-lr#96

Reference: ember-cli#4897
@elwayman02
Copy link
Collaborator Author

@shama @mklabs any updates?

@shama
Copy link
Collaborator

shama commented Oct 11, 2015

@elwayman02 I haven't heard anything and don't have access to give out collaborator access. I am considering this option: https://twitter.com/shamakry/status/649396015515086848 as that would give collaborators more permissions.

@elwayman02
Copy link
Collaborator Author

@shama this is an intriguing idea, and one that I'd be interested in helping out with. Happy to chat about it at some point if you want.

@mklabs
Copy link
Owner

mklabs commented Oct 23, 2015

Hi

and sorry for the huge delay.

I agree, bringing in more collaborators couldn't hurt.

@elwayman02 I've added you as collaborator for both the github repo, and the npm package over at npmjs.com

Thanks!

@shama
Copy link
Collaborator

shama commented Oct 23, 2015

Thank you @mklabs! I really appreciate it!

@elwayman02
Copy link
Collaborator Author

👍 thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants