Before I hit the transfer button, this is a good moment to consider the repo name, which is currently "clojure-humanize"; would just "humanize" be better ("clojure-" feels redundant)?
Transfered. https://github.com/clj-commons/humanize. It's public. I'll work on renaming namespaces and such soon.
I guess it's good to go through this process with something relatively trivial. That being said, I really like this library, because I'm all about good feedback.
wouldn't renaming namespaces be a breaking change? or it this an intentionally clean start?
Different coordinates so that's OK?
(as I did with HoneySQL -- so you can have code depending on both transitively without conflict)
yep, makes sense
means the namespaces need to be completely disjoint then right?
org.clj-commons.humanize is what I'm planning on
@hlship This is what I've settled on for digest: https://github.com/clj-commons/digest/blob/master/src/clj_commons/digest.clj
which had a single-segment namespace, but this caused issues with graalvm. I left the single segment namespace + added clj-commons.digest
So not ; works for me.