Clojurians Log v2

@micha / @alandipert Are one of you able to set it up so that @mynomoto can maintain Hoplon?

I can hook that up this afternoon

Also I'll check up on flyboarder, see if he's ok

@mynomoto afaict you have all necessary github and clojars authorizations, is something missing you know of?

I think that permissions on GitHub and clojars are ok. I don't want to takeover maintenance on the project without asking first if it is ok.

@mynomoto i reached out to flyboarder by email to make him aware of the situation, in the meantime pls consider yourself maintainer 👑

Ok, thanks! I will try to get a release out soon and update docs and examples.

Hey @mynomoto, if you need an extra hand to maintain Hoplon, I'm more than happy to help out. I have some decent experience with shadow-cljs, which could come in handy.

BTW, a few years back, I put together a repo that includes a fairly complex Hoplon application. It makes use of shadow-cljs and a few newer libraries, such as reitit: https://github.com/rlander/conduit. If anyone finds it useful, I'd be happy to update it. Let me know if the Hoplon community thinks it's worth keeping around.

Hi @rlander, thank you for offering help. I think that your example app is very useful, so please update it when you can. Also, I think that getting examples and templates working again is very important as Hoplon itself never stopped working, but the tooling in examples and templates did on more recent versions of the JVM. If you could help with those too it would be amazing.

I got the tests running on my machine yesterday using a deps.edn setup, so that is a small step.

Hello @mynomoto, I am also interested in Hoplon as it is my go to ui library for my cljs (side) projects. It is cool that you switch it away from boot. Whenever you have a PR with the changes I can help testing it.

@mandimby.raveloarinja anything you would like to be prioritized? There are many things we need to update, so we could start with the ones people need more urgently.

as far as I can see it, switching out of boot will help for contributors finding bugs to submit fixes. Therefore, build (moving to shadow-cljs for instance) and documentation might be nice first priorities.

Ok. Since Hoplon is a library, deps.edn should be enough to replace boot. For templates, examples and projects we need to pick between shadow-cljs and figwheel-main. I think we could support both in templates but I think we should stick with shadow when we choose only one.