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

bindings_for_other_languages: List unmaintained. #156

Merged
merged 5 commits into from
Mar 31, 2022
Merged

bindings_for_other_languages: List unmaintained. #156

merged 5 commits into from
Mar 31, 2022

Conversation

samuel-lucas6
Copy link
Collaborator

@ektrah mentioned cleaning up the .NET bindings in terms of providing guidance on which ones to use, but I noticed that a lot of the bindings appear to be unmaintained, so I've attempted to classify them. My criteria was whether the library has had any commits in the last year or two and whether the owner has done commits on their account in the last few months in more ambiguous cases.

Some are very clearly unmaintained (e.g. archived, a notice, no response to issues/PRs for years), so at the very least, I think it would be beneficial to have a note in those cases.

@jedisct1
Copy link
Owner

Thanks a lot!

Sometimes, projects move to a different repository/organization. But it's hard to see track of everything.

We should probably just remove unmaintained entries from the list.

@samuel-lucas6
Copy link
Collaborator Author

samuel-lucas6 commented Mar 15, 2022

We should probably just remove unmaintained entries from the list.

Sounds good to me. Is there specific criteria you'd like me to follow? I don't want to accidentally remove libraries that are being maintained version wise (supporting 1.0.18) but haven't had recent commits. For example, I could remove everything below 1.0.18 and any archived, with a notice, etc. I could also create an issue in some and see if I get a quick reply.

@jedisct1
Copy link
Owner

Creating an issue and see what maintainers respond (if they do) may be the best way to go.

This was referenced Mar 15, 2022
@samuel-lucas6
Copy link
Collaborator Author

samuel-lucas6 commented Mar 15, 2022

I'm sorry if this filled up your inbox Frank. Hopefully it will make things easier to track. I'll edit this comment when I hear back from people.

Archived before contact

  • libsalty
  • libstodium
  • kalium
  • ocaml-sodium
  • Pharo/Squeak: Crypto-NaCl (believe I read this was no longer maintained in another repo)
  • NaOH

Still/going to be maintained after contact

  • erlang-libsodium (in the future)
  • sodium-wrapper (in the future)
  • Natrium (in the future - says feel free to remove for now)
  • natrium-browser (no commits since 2015 - says working as is but will be reassessed later this year)
  • Andhell.Crypto (may be in the future - says feel free to remove for now)
  • js-nacl (just updated)
  • Crypt-Sodium (says feel free to remove to give other bindings priority)
  • Tafelsalz (may be in the future - says feel free to remove for now)
  • libsodium-ada

Confirmed unmaintained after contact

  • libsodium-net
  • libsodium-core
  • fortium
  • datkt / sodium
  • php-sodium
  • stouset / sodium
  • cl-sodium
  • libsodium.nim
  • chloride
  • Robosodium
  • sodiumpp
  • sodium.nim
  • erlang-nacl
  • chicken-sodium
  • haskell-libsodium
  • mruby-libsodium
  • guile-nacl

@samuel-lucas6
Copy link
Collaborator Author

There are about 30 maintainers who haven't replied yet. Should we wait another week? Half a week?

@jedisct1
Copy link
Owner

Thank a ton for that hard work, Samuel, this is fantastic, and very useful for people looking for up-to-date, maintained bindings. Also good to see that some maintainers may update their code after your message :)

We can make the changes to the documentation now, and re-add projects later if you get a response from their maintainer.

@samuel-lucas6
Copy link
Collaborator Author

Just to check, does this look ok to merge @jedisct1? Haven't had any replies recently.

@jedisct1
Copy link
Owner

Let's do it!

@jedisct1 jedisct1 merged commit 9cd11a7 into jedisct1:master Mar 31, 2022
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

Successfully merging this pull request may close these issues.

2 participants