Fork me on GitHub
#clojars
<
2022-06-14
>
Albert09:06:04

how can I help on maintaining clojars?

xlfe10:06:54

I'm also keen to help-out (I think!)

victorb11:06:56

Same here! I can dedicate some hours/week to maintaining Clojars. Have experience running infrastructure, writing Clojure code and been involved in package management before (even running my own package registries!)

victorb11:06:23

@danielcompton might want to share some more info on how people can get started helping out šŸ™‚

tcrawley12:06:45

Hi @dpsutton @kayulai2 @felix @victorbjelkholm429! Thanks for your interest! What we're looking for initially is just having more folks familiar with the system and contributing to the codebase. I think from there we can chat about becoming a maintainer. I've done a little grooming on the issues we currently have, and marked ones that would be good to work on with the ready-for-work tag: https://github.com/clojars/clojars-web/labels/ready-for-work I'm happy to chat about any of those! For a system overview, you can look at https://github.com/clojars/clojars-server-config I'm also happy to host a Zoom session to go over how the system works and the codebase, and answer any questions if there is interest in that!

victorb12:06:12

Great, thanks for the introduction! Will take a look at getting it running locally and take a stab at some issue. Otherwise, I'd be interested in participating in a Zoom session to get an introduction if it's happening, although the codebase seems small enough that I'd be able to find my way around by just asking minor questions async over Slack.

tcrawley12:06:14

Sounds good, thanks Victor! Feel free to ping me on anything.

šŸ‘ 1
tcrawley12:06:34

(I'm tobias on GitHub if you ping me there)

Albert13:06:31

I'm zerg000000 on github. Thanks for the introduction, will look into it.

lispyclouds14:06:39

Hey @U06SGCEHJ I too would like to help out and would love to know of the expectations in the zoom call too! Had been part of maintenance of lambdaisland's infra at some point and currently help maintain #babashka and other @U04V15CAJ goodies more from the infra perspective šŸ˜„ I'm lispyclouds on Github.

borkdude14:06:36

Also, @U7ERLH6JX has a professional background/still active career in clojure + ops work

tcrawley17:06:33

Thanks all! I'll try to get a zoom set up for folks that want that.

šŸ™ 1
Faris04:06:31

Iā€™m quite interested as well! Hope to be able to join if you do a zoom call.

victorb17:06:08

Is there any difference between just the latest released version, and the latest "promoted" version? Looking at https://github.com/clojars/clojars-web/issues/332 and https://github.com/clojars/clojars-web/issues/398, the only difference between the issues is that the latter mentions "promoted" version, but not sure what that entails exactly

tcrawley17:06:14

Clojars used to have a way to promote releases to a secondary repo, but that was never really finished and had issues, so was removed (see https://github.com/clojars/clojars-web/issues/415). This is likely a reference to that.

victorb17:06:06

Thanks for the clarification. I'm guessing #398 should be closed as well then

tcrawley11:06:48

I think so, yes. I'll do that.

victorb17:06:43

First PR done at least šŸ‘ addressing the first issue linked above (#332): https://github.com/clojars/clojars-web/pull/836

šŸŽ‰ 2
tcrawley17:06:04

This is great, thanks! I'll try to review it soon.

šŸ‘ 1