Updates / project status?

[jamesvl]

@handnot2 I've noticed merge requests have been sitting open a for a while, and with OTP 24 out now deprecated some functions used here, are you still interesting in maintaining this project moving forward? If not, would you consider letting others help out in some fashion?

I know this work has been hugely valuable for me to do some SSO integrations I would not have been able to do (via samly) otherwise, and am willing to pitch in to make sure both remain viable going foward.

[tcrossland]

@jamesvl agreed, I think it would be useful for the community if this project were more actively maintained. I believe the BSD license allows the work to be modified and would be supportive of moving the maintenance effort to a fork if this repository is no longer active.

@handnot2, @arekinath many thanks for all your work on esaml. Please respond if you would rather continue to use this repo for maintaining esaml.

[arekinath]

I'm happy to create a "esaml" org account and move the original repo there, and give @handnot2 admin on the org (and commit access to others who are maintaining it), if that seems useful?

[jamesvl]

I'd certainly be willing to help triage or do reviews if we pursued this path.

Having an official move of the repo would be nice for anyone using the hex packages; it would be ideal to avoid creating a new hex project if we could.

[tcrossland]

@arekinath the esaml org account seems like a good idea to me... the only issue is that @handnot2 doesn't seem to be responding and has no contribution activity since april 2019, so it might be a good idea to have some other admins from the community (@jamesvl or myself, for example).

What do you think?

[k-cross]

I have forked this to maintain it through dropbox here: https://github.com/dropbox/esaml

I'm currently in the process of getting ownership of the project through hex.pm too. Are there any other places that I should try to take over ownership? I've been handling all of the corporate takeover stuff since October.