Anyone here have context on https://github.com/adambard/failjure? Last commit 2023-04-29, 15 open issues, ~4yr stale correctness bug (#31). @adambard still GH-active in general but seems to have stepped away from this one specifically. Several of us depend on it in production. Opened https://github.com/adambard/failjure/issues/41 to discuss upstream — wondering if clj-commons would consider receiving a transfer?
got https://github.com/adambard/failjure/issues/41#issuecomment-4937601899 from library owner. how do I initial the transfer process?
The owner—or someone with admin privs—of the failjure repo would need to initiate the transfer. We'd have to give them write access to the clj-commons org first, I believe, so we'd need to know the GH username.
https://github.com/adambard is the owner, who also gave the https://github.com/adambard/failjure/issues/41#issuecomment-4937601899.
I can also volunteer to be a maintainer since we use it at work, if this makes it easier.
@gzmask I sent Adam an invite to clj-commons, so he can initiate the transfer. What's your GH and I'll invite you?
thanks! my handle is https://github.com/gzmask
Okay, you should get an invite too.
And "Thank you!" for volunteering to (help) maintain it going forward.
Can you also ask Adam if he's willing to open up the failjure group on Clojars so we can continue publishing artifacts under the same group ID?
He could add me as a group admin <mailto:sean@corfield.org|sean@corfield.org> or seancorfield and I can then manage whatever is needed by clj-commons for automated releases from CI.
(otherwise, we'll switch to publishing it under the clj-commons group, but that breaks continuing for users when upgrading, and would require all the nses to change as well to avoid conflicts if two different versions end up on the classpath)
that make sense, so downstream users don't need to update their clojar url. I will ask in the issue.