clj-commons 2019-12-17

well, that would be interesting 😉 Was thinking the org would ask for support, with many contributors getting support for hours they will do for 3 months. Would need a lot of coordinating. And not sure if money would be a good motivator here. After 3 months, things could be get back to way they were..

maybe it's more natural if projects are stewarded by companies or individuals who are real stakeholders

one example where clj-commons worked great for me personally was when secretary had a critical bug, but we could have fixed it in our own company fork which is public

it's better if there is one fork which gets collective contributions than a lot of scattered forks though

but the previous owner should then nominate an official follow up fork or maintainer, and this is usually where it breaks, since some maintainers just stop responding after a while

stats would be nice: how the moving to clj-commons has effected in commits, fixes issues, releases and downloads.

This is probably why clj-commons should probably be a bit more conservative about taking projects on -- projects really do need a committed maintainer within the commons group, otherwise projects might just as well stay unmaintained elsewhere.

Yeah I’ve had an extremely busy year and have bitten off a bit more than I could chew with new job, 3 overseas trips, big Clojurists Together changes, and a new baby on the way

I should have more time to focus on clj commons early next year

Sorry 😥

maybe clj-commons should apply funding from Clojurists Together?

@ikitommi not sure how that would help. @danielcompton would then be busy organizing himself :)