Clojurians Log v2
clj-commons 2023-11-25
Is there a way to add @alexyakushev as an admin of dirigiste on clojars, or is administration lumped together at the group level (i.e., org.clj-commons)?
I’ll put on my best Alex Miller impersonation and say something like: “It sounds like you’re proposing a solution to an unstated problem”
I'm not even sure what "an admin of dirigiste on clojars" means -- @kingmob are you asking for @alexyakushev to be able to cut releases of clj-commons/dirigiste and deploy them to Clojars? So he needs to be a member of the clj-commons group? (members can deploy releases -- they don't need to be admins, right @slipset)
Interestingly, I see clj-commons/dirigiste 1.0.3 on Clojars but on my dashboard, if I go into the clj-commons group, I don't see dirigiste listed in that group -- so maybe my understanding of Clojars groups is a bit off?
@seancorfield, There is also org.clj-commons. Maybe it is under there?
Yup, org.clj-commons/dirigiste is there (as expected!). BTW, @kingmob you're already an admin of that group so you could add @alexyakushev as a member yourself (I assume you were made admin because you maintain a bunch of projects under that group?)
Being a member of the group should be enough to be able to push releases. But I think Matthew wanted a way to give push permissions for a particular project, not the whole group. I can just pinky swear to not push other artifacts and we'll call it a day:).
I think Clojars orgs pretty much have to rely on the honor system 🙂 What's your clojars username @alexyakushev and I'll add you?
It's https://clojars.org/users/alexander_yakushev, thanks! ❤️
@eugen.stan, my offer still stands. I'm happy to convert those .rtf files to .adoc for you and ensure they look good in cljdoc.
thanks @lee. I will add this to the issue. Let's wait a bit and see if one of the original devs replies. If not, we can probably move forward with this.