-
Notifications
You must be signed in to change notification settings - Fork 57
Repo and org name chnges #96
Comments
👍 I'm personally in favor of lowercase repo name to be consistent with the artifacts. |
👍 on Between the two, I prefer the one that matches the artifacts as well. I Don't like dealing with caps as much as the next guy. Edited the post to reflect the change. |
I'll go for Crypt4s / crypto4s but I'd prefer Crypto4s / crypto4s. I think it could be worth trying to make contact with the owner of https://github.com/Crypto4s since it might be just a ghost repo or directly with GitHub customer service (I just made contact), there are a few happy stories out there (http://awolski.com/request-your-github-username/). Another option could be registering the domain |
I like |
Digging up an old issue, I've seen some orgs named like |
I was able to acquire https://github.com/crypto4s -- I can start adding folks. |
Also got crypto4s.org that we can point at GH pages. |
Background
TSec has been gaining more following. More people are interested in the project, I've been getting more PR interest from first time contributors, and more suggestions on stuff..
This is even before the release of tsec-libsodium and while it's still in milestone "break all binary and many apis every PR" mode. This means that even with the fact that we're still a fledging project, the interest is there and it's growing.
This has made me quite happy, and I'm guessing the maintainers as well.
That said, my vision for tsec even from the begginning wasn't like, a "library for crypto stuff and that's it", it's been "Improve the cryptography and security environment in scala". This means that eventually, time permitting, I/We'd like to create different, high level crypto applications using tsec as a base (you could think of many: server-side admin panel frameworks, key distribution servers, TLS, cryptocurrencies... list goes on).
This means that eventually the repo needs to transcent my sole-ownership and become an org, to be able to host more complicated applications under one free, open-source banner. At the same time, the name
tsec
was the drop-in emergency replacement for the initial edgy repo name I was playing with inspired by circe's original, dank name.Proposal
Org name (Because Crypto4s was taken 😠 ):
Repo name:\
Names for both org and repo name are open for discussion, but eventually we will be renamed and transferred
The text was updated successfully, but these errors were encountered: