Clojurians Log v2

Some very good news! @yannick.scherer has graciously offered to transfer rewrite-clj to clj-commons. He’s also kindly offered clojars deployment creds for xsc/rewrite-clj. My plan is to merge my work from rewrite-cljc-playground to rewrite-clj proper. This will offer nice continuity for existing rewrite-clj users! Much thanks to @yannick.scherer! @slipset how should we proceed?

@yannick.scherer has joined the channel

@lee I would need you to take lead on this, since I’m not quite up to speed on what needs to be done. What I’m very able to help with is deployment, as I’ve worked on some infrastructure related to that for clj-commons, so it would be very interesting to fit the needs of rewrite-clj into this.

So first thing is to get the repo over to clj-commons, right?

That means that @yannick.scherer who’s already a member of clj-commons need to transfer rewrite-clj to clj-commons.

Thanks @slipset yeah once the repo is over to clj-commons, I am happy to take ownership.

He can do that from github, I believe.

I can do that right now, if desired.

Awesome!

😕

Ah... that might be rewrite-cljs which was forked from rewrite-clj...

exactly

> To detach the fork and turn it into a standalone repository on GitHub, contact https://support.github.com/contact or https://premium.githubsupport.com. If the fork has forks of its own, let GitHub Support know if the forks should move with your repository into a new network or remain in the current network. For more information, see "https://docs.github.com/en/free-pro-team@latest/articles/about-forks."

Hey @yannick.scherer - thanks for rewrite-clj (and version-clj and others), it's been a good foundation for several clojure tooling libs, including clj-kondo.

Happy to see it's being moved to clj-commons for further support

I’m contacting github support now.

Cool, if you are not successful with support, we might be able to do something ourselves.

Yeah, I could easily transfer rewrite-cljs to my personal account for the time being.

But the problem would still remain if we are to keep both projects.

They’re quick!

I already got an answer.

Rewrite-cljs is now a historical artifact. I think we could delete it and re add it as a stand-alone?

Oh cool

So it’s in motion.

Wowzer, is it because we have a man on the inside?

Done

@yannick.scherer could you try to transfer again?

It is done.

woosh!

I’m not sure how xsc transfers clojar creds for xsc/rewrite-clj slipset, how does that go?

I think I'll give admin access to the rewrite-clj group to someone (who can then remove me)?

@slipset Is this you? https://clojars.org/users/erik @lee And you? https://clojars.org/users/lread I would make you both admins, then?

yes, that’s me

yup that is me!

Just to manage expectations a bit. New years is coming up quickly in my TZ, so I won’t be able to do much more today.

You're now both admins.

Awesome, rewrite-cljc is dead, long live rewrite-clj!

@yannick.scherer thanks for the transfer! @slipset thanks for the leadership!

Sure thing 🙂

I’ve set it up to build on circle.

Ok, cool, thanks! rewrite-cljc builds on github actions, I expect circle is not a requirement of clj-commons projects.

But this can all wait until next year, happy new year!

It’s not a requirement, but it’s all I know 🙂

What may or may not be a requirement is deploying to clojars without building on a local machine, preferably by pushing a release tag (as implemented in https://github.com/clj-commons/fs )

The pushing of tags is somewhat important as I generally tend to forget, and then a Debian person pings me to tag a release so he can get the tar-ball from github.

Anyhoop, feel free to ping me at any time @lee if you need any help with anything.

Thanks @slipset, I’m all for deploying from ci, makes sense to me.