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

Add new repo #2

Open
fomojola opened this issue Apr 2, 2019 · 0 comments
Open

Add new repo #2

fomojola opened this issue Apr 2, 2019 · 0 comments

Comments

@fomojola
Copy link

fomojola commented Apr 2, 2019

Sorry to file this: happy to close it but couldn't think of a superior way to communicate with you guys. I recently fixed a bug in passport-intuit (https://github.com/jaredhanson/passport-intuit) by forking the main package and just changing the dependency to @passport-next/passport-openid (the actual forked package is at https://github.com/fomojola/passport-intuit). Seeing as @passport-next is providing a home to updated passport strategies is there a process (formal or otherwise) to bring packages such as this up to snuff and then adopt them into @passport-next? I'd happily pass my fork over or switch to using a fork you make: right now I'm depending directly on my github link in production which makes me a bit nervous, and I can't be the only person experiencing this issue so having it in @passport-next seems like The Right Thing To Do (TM).

I'd love to do the work to pull up the dependencies on a couple of the passport strategies I'm using and pass them to you guys to vet and publish?

Thanks!

Femi.

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

1 participant