Skip to content
This repository has been archived by the owner on Nov 29, 2021. It is now read-only.

Repo and org name chnges #96

Open
jmcardon opened this issue Dec 27, 2017 · 7 comments
Open

Repo and org name chnges #96

jmcardon opened this issue Dec 27, 2017 · 7 comments

Comments

@jmcardon
Copy link
Owner

jmcardon commented Dec 27, 2017

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 nametsec 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 😠 ):

  • Crypt4s
  • HoneyBadgerCrypto (Gets my vote)

Repo name:\

  • Crypto4s
  • crypto4s (Gets my vote)
  • ???

Names for both org and repo name are open for discussion, but eventually we will be renamed and transferred

@ChristopherDavenport
Copy link
Collaborator

👍 HoneyBadgerCrypto/crypto4s

I'm personally in favor of lowercase repo name to be consistent with the artifacts.

@jmcardon
Copy link
Owner Author

👍 on crypto4s actually... I didn't really take into account the case.

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.

@gvolpe
Copy link
Contributor

gvolpe commented Dec 27, 2017

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 crypto4s.org, currently available, and claim the repository name with GitHub (I guess it's possible but a bit of a headache).

@hrhino
Copy link
Collaborator

hrhino commented Dec 28, 2017

I like crypto4s as well, especially if we can get the org name. kryptos was my other thought but that's taken by a really-real person.

@asoltysik
Copy link

Digging up an old issue, I've seen some orgs named like foo-org so crypto4s-org is also an option.

@jarreds
Copy link
Contributor

jarreds commented Oct 25, 2018

I was able to acquire https://github.com/crypto4s -- I can start adding folks.

@jarreds
Copy link
Contributor

jarreds commented Oct 26, 2018

Also got crypto4s.org that we can point at GH pages.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants