Clojurians Log v2

@slipset @seancorfield @lee and I have been maintaining https://github.com/lread/clj-graal-docs but we'd love this to live in a "neutral" place like clj-commons so it can be more seen as a community effort. We would still be the admins/maintainers of this repo, so we're not just dropping this into the hands of clj-commons and then would abandon it. Is clj-commons a good place for this?

Preferably we would also merge with @bruno.bonacci's graalvm-clojure repo if he is open to it, so we have one central place for all things related to Clojure + GraalVM documentation/howto

@bruno.bonacci has joined the channel

I see no problem with that even though the project seems far from abandoned.

yeah, it is not a typical use case, but seems to make sense,

let's hear what @bruno.bonacci has to say about this idea.

And @seancorfield might have some wisdom/guidance on this idea too, but to me it seems like a good idea.

Hi @borkdude, clj-commons is a place for projects which for any reason can't be maintained by their original maintainer. Does this mean that you are not able to contribute to clj-graal-docs anymore?

@bruno.bonacci No that's not the point, see above

(brb, meeting)

(perhaps @lee can tell more)

sorry you might have already discussed this, but since i wasn't in this channel I and i was just added i can only see the latest 4-5 messages.

@bruno.bonacci So the thinking was: lread + me have clj-graal-docs you have graalvm-clojure we could merge the repos and host it under clj-commons/graalvm-clojure and join efforts and to make it seem more like a community repo

while we would still all be "admins" of this repo

Also see this conversation in #graalvm for context: https://clojurians.slack.com/archives/CAJN79WNT/p1624357494220000

Of course, you could merge the two projects and keep them under one of them, without moving to clj-commons. I’ll leave you to hash that out.

Yes, true! The clj-commons org idea is to convey these docs are truly a community collaboration. They are really only under the lread org because I happened to create the repo.

There are definitely pros and cons to this. My first reaction would be to suggest putting them under a clojure-graalvm organization on GitHub instead of a personal account and build that up as a community hub — I don’t think clj-commons per se buys you anything useful.

clj-commons is really intended to be a place for otherwise unmaintained project that are still important to the community to find a home where a group of volunteers can keep them ticking along without needing to do a lot of active maintenance on them.

(and as an org it already has a bunch of projects that satisfy neither of those criteria, but that’s a separate discussion)