-
Notifications
You must be signed in to change notification settings - Fork 224
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
Need help for maintenance? #54
Comments
I'd be happy to help, we'll use this package quite a bit with TypeScript Julien Fontanet [email protected] schrieb am Mi., 13. Mai 2015
|
I had some ideas on how to improve this library, and even have custom code that works well in another project (full commit) for debugging front-end errors (accurate stack traces, I was already planning on extracting this code into another library. It might be worth having here, in which case I'd be willing to help. On the other hand, this code downloads source from the server in order to print the line above the |
@joeyespo I think it is also implemented in this module. |
I'd be happy to help too... I'm currently maintaining it through my fork, but I'd prefer to join changes in here instead of duplicating... :) |
I propose we wait some time (2 weeks?) for @evanw to express his point of view, after what we could create a fork and maybe try to take the module name on npm. |
@julien-f Nice! It wasn't working right at the time I implemented it. I'll try using purely this lib again. |
Sure, help sounds great! My startup is very time-consuming and it's very hard for me to find time for my open-source stuff. I would definitely prefer to keep this library alive and centralize our efforts instead of causing fragmentation. Let me know how you want to proceed. |
I think you should start by adding all of us as collaborators on this repository to help you with issues triage and PRs merge, and keep the ownership of the npm package and the responsibility to make releases for now. After a while you could share this responsibility too with the people you see the most fit. |
Alright, there you go. I've added you as collaborators. Thanks for helping out. |
@evanw It seems the project is still lagging and issues are rising, unfortunately I do not have the time much time to help. I think we should also release more often, to prevent users from waiting too much their fixes to be released and in doing. |
@evanw Ping? |
Whoops sorry, just saw this. Sounds great to me. What's your npm user info? |
|
I looked but I didn't see a way to do that in GitHub's UI. Collaborators don't have configurable permissions. How do I do that? |
Ok, you should be listed as an owner on npm now. |
I have no idea, I thought it was possible :/ I am afraid you will have to add them yourself, any volunteers? @LinusU @tugend, @AndreasMadsen? |
@evanw @julien As far as I know, owners can only be added in organizations.
Sorry, I won't have time to maintain something I don't use. But I'm happy to answer questions related to the v8 Error API and |
I was actually going to start use this again for a project, I'd be happy to help maintain. I'm linusu on npm. |
Thanks @LinusU. I've added you on GitHub and npm. |
👍 |
@evanw You have not been much available lately to answer/close/merge issues and PRs, do you need help maintaining this package?
Are there any other people willing to help? (cc @joeyespo, @marcominetti, @mprobst)
The text was updated successfully, but these errors were encountered: