Fork me on GitHub
#clj-commons
<
2022-10-05
>
slipset07:10:14

I see that I don’t have permissions to publish potemkin under its original potemkin clojars group. Are you guys in favor of moving it to org.clj-commons/potemkin or you prefer I ask Zach for permissions to publish to potemkin . I prefer moving.

lread12:10:32

@slipset, my 3 cents: The big benefits of preserving artifact coordinates are: • continuity for users of the lib • users can discover updates via tools like antq • users won’t suffer the chance of clashing nses (for example if both potemkin and org.clj-commons/potemkin are on the classpath) So I think it would be worth asking Zach, and if that doesn’t work out, as a last resort publish to new coords. I was very happy, for example, when I finally got the rights to reuse existing coords for rewrite-clj.

lread13:10:14

Yeah, good point, before I got those rights to reuse the rewrite-clj artifacts coords, I was going with a new rewrite-cljc namespace. So glad I did not have to do that.

lread13:10:19

@slipset I uploaded the lovely clj-commons logo you created/inspired for use on slack: clj-commons

slipset18:10:52

I did not make it, that was @tonsky

lread19:10:17

Thanks for clj-commons @tonsky!

❤️ 1