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

Need help for maintenance? #54

Open
julien-f opened this issue May 13, 2015 · 21 comments
Open

Need help for maintenance? #54

julien-f opened this issue May 13, 2015 · 21 comments

Comments

@julien-f
Copy link
Collaborator

@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)

@mprobst
Copy link
Collaborator

mprobst commented May 13, 2015

I'd be happy to help, we'll use this package quite a bit with TypeScript
and Angular.

Julien Fontanet [email protected] schrieb am Mi., 13. Mai 2015
10:24:

@evanw https://github.com/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
https://github.com/joeyespo, @marcominetti
https://github.com/marcominetti, @mprobst https://github.com/mprobst)


Reply to this email directly or view it on GitHub
#54.

@joeyespo
Copy link
Collaborator

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, ^, etc).

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 ^, so that may very well be outside the scope here. So the answer is maybe :-)

@julien-f
Copy link
Collaborator Author

@joeyespo I think it is also implemented in this module.

@marcominetti
Copy link
Collaborator

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... :)

@julien-f
Copy link
Collaborator Author

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.

@joeyespo
Copy link
Collaborator

@julien-f Nice! It wasn't working right at the time I implemented it. I'll try using purely this lib again.

@evanw
Copy link
Owner

evanw commented May 14, 2015

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.

@julien-f
Copy link
Collaborator Author

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.

@evanw
Copy link
Owner

evanw commented May 15, 2015

Alright, there you go. I've added you as collaborators. Thanks for helping out.

@joeyespo
Copy link
Collaborator

Thanks, @evanw.

And nice job so far, @julien-f!

@julien-f
Copy link
Collaborator Author

@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.
What do you think about adding me as a maintainer on npmjs (disclaimer: it is a risk, I could steal the package, which I obviously won't do :p)?
It would also be great if I could be able to had new collaborators on the GitHub repo.

@julien-f
Copy link
Collaborator Author

julien-f commented Oct 7, 2015

@evanw Ping?

@evanw
Copy link
Owner

evanw commented Oct 13, 2015

Whoops sorry, just saw this. Sounds great to me. What's your npm user info?

@julien-f
Copy link
Collaborator Author

julien-f, but we also needs more collaborators on this repository as I don't have the time to manage it by myself…

@evanw
Copy link
Owner

evanw commented Oct 13, 2015

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?

@evanw
Copy link
Owner

evanw commented Oct 13, 2015

Ok, you should be listed as an owner on npm now.

@julien-f
Copy link
Collaborator Author

I have no idea, I thought it was possible :/

I am afraid you will have to add them yourself, any volunteers? @LinusU @tugend, @AndreasMadsen?

@AndreasMadsen
Copy link

I have no idea, I thought it was possible :/

@evanw @julien As far as I know, owners can only be added in organizations.

I am afraid you will have to add them yourself, any volunteers?

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 stack-chain.

@LinusU
Copy link
Collaborator

LinusU commented Oct 13, 2015

I was actually going to start use this again for a project, I'd be happy to help maintain. I'm linusu on npm.

@evanw
Copy link
Owner

evanw commented Oct 14, 2015

Thanks @LinusU. I've added you on GitHub and npm.

@LinusU
Copy link
Collaborator

LinusU commented Oct 14, 2015

👍

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

7 participants