-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project Support #41
Comments
I'd be happy to help out here as well. |
@jeffutter Thanks for bringing this up. With issues like #42 that break Statix on the newest OTP, it's becoming more pressing to keep the project maintained. Otherwise, I suspect there will be lots of forking to patch it. It'd be handy to at a "fork of truth" that's maintained until this question is resolved. I'd wager that Bleacher Report would be a good candidate for that fork. Do you have one shared publicly? |
@mroach We don't have our own fork. We're either using the hex release or https://github.com/rodrigues/statix/tree/events_checks. However, I can create a fork under our org that includes |
My biggest concern with a fork is how it will handle inclusion in |
@jeffutter That'd be great to have a fork on the Bleacher Report org. Since statix is now broken, I think we'll see a ramp-up in users looking for a maintained package as they upgrade. |
I've created a fork over at https://github.com/bleacherreport/statix that has a couple of commits merged in that we use. I also have a branch that fixes OTP-21.3.8.4 here: https://github.com/bleacherreport/statix/tree/otp-21.3.8.4-support I think it works, but it probably needs some cleanup and testing. |
Hi folks, I apologise for not responding faster. |
Hi @lexmag ,
I was wondering if this project could use some additional help with support and maintenance. It looks like there have been no releases for a while and not much activity on the repo even with a handful of open PRs.
We use this library in a few projects at Bleacher Report and would be glad to help out where we can.
I would be in support of adding another maintainer or two, or moving the repo to an organization. Feel free to let me know how I can help or use this thread to discuss further.
The text was updated successfully, but these errors were encountered: