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

Abandoned? #184

Closed
gabegorelick opened this issue Aug 9, 2019 · 4 comments
Closed

Abandoned? #184

gabegorelick opened this issue Aug 9, 2019 · 4 comments

Comments

@gabegorelick
Copy link

Has this module been abandoned? The last commit was in January. The last release was in May 2018. PRs get no response. Requests to publish a new version have gone unanswered.

It's totally fine if Clever doesn't want to maintain this anymore. But if that's the case, can some new maintainers be added to the project? Or should the community fork?

@SJAnderson
Copy link

SJAnderson commented Aug 14, 2019

+1 for community forking.

Edit: what's a good alternative than this library?

@gabegorelick
Copy link
Author

what's a good alternative than this library

I haven't used it myself, but https://samlify.js.org looks promising.

@cozmo
Copy link
Contributor

cozmo commented Aug 19, 2019

Hey all!

First of all, sorry for the radio silence here. It's "back to school" right now, which is Clever's busiest time of the year, and we've all been a little underwater.

That said - This library is certainly not abandoned, we use it in production to serve millions of logins per day. As such, for Clever's use case, we'd consider this library relatively feature complete. That said we recognize that the potential surface area of SAML is large, and this library currently covers a small part of it. While Clever may not be investing resources in expanding the scope of this library, we want to be good open source citizens and encourage/support ongoing development of features. As such in the coming weeks we'll be

  1. Investing in modernizing the codebase. In practice this will likely mean converting to Typescript, updating/improving the documentation, making sure the CI testing/publishing works, etc.
  2. Merging any outstanding issues/PRs that are in a good state to merge/resolve.
  3. Commenting/providing feedback on issues/PRs that are waiting for feedback from Clever
  4. Closing issues/PRs that are no longer relevant etc.
  5. Making sure we have the processes internally to stay on top of issues/PRs going forward.

Please let us know if there are additional questions.

@gabegorelick
Copy link
Author

Thank you @cozmo. That is a satisfying answer to me, so I will close this issue.

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