re: > Also, if this is a new group you are creating, I'd recommend using `com.xn--lgc` instead. We're going to soon move to requiring new groups to be reverse-domain based and verified, so doing so now would put you ahead of the game. what is the recommendation for a new project? com.foo.project/project or com.foo/project ?

if it's a company project, com.companyname/the-project if it's a personal project, I'd probably lean to com.github.username/the-project given this guidance.

Or if you have your own domain that could be easily verified, something like org.mysite/the-project

And remember that your namespaces don't have to follow the group/artifact but your top-level namespace segment should be globally unique if you plan to publish it.

Hi there. I'm currently struggling with trying to upload my JAR to Clojars. However I think there's something wanky with how I'm setting up GPG. So I've created a key pair, published it to openkey and signed credentials.clj with it. Is there an additional step where I have to upload the public key to Clojars itself? Thanks in advance.

@clj149 as far as com.foo.project/project vs com.foo/project goes - that's up to you; both will be supported from a group verification perspective. I would personally only do com.foo.project as a group if the project was an umbrella for multiple libraries: com.foo.quibble/routing, com.foo.quibble/rendering, etc.

Thanks, that sounds good to me.