modular-bitfield
modular-bitfield copied to clipboard
Is this crate maintained?
I'm not seeing a lot of commits, and am wondering whether a co-maintainer would be welcome? Or if new PRs would be accepted?
I understand that after the xz incident you might be wary of accepting a co-maintainer, and maybe the best option would be to fork (or just live with the flaws), but I'm reluctant to do either of those. I'm also not sure that I'm willing to step up as a co-maintainer, just exploring the state of the crate.
Hi @droundy and thank you very much for asking.
Best would be someone who can be trusted as a co-maintainer, however, that "becoming trusted" to maintain with a high quality and diversity of use cases in mind is hard to come by. The simplest was to fork this crate and maintain your own fork for a while and eventually take over upstream once proven that the fork is actually better and of higher quality.
I also thought about coming back to this old crate and give it some well deserved love. Problem for me is that it seems a re-write of the macro system is less work to fix all the issues and limitations that have accumulated over the years - not very approachable.
Hi, I am now assisting in maintenance and am in the process of resuscitating this crate. There should be a new release fairly soon with bug fixes, as my time permits.
@csnover Thank you very much for doing this work! I posted on URLO to let others know.
@csnover Thank you very much for doing this work! I posted on URLO to let others know.
Thanks! No name dropping is needed, my ego is big enough on its own and I don’t think it’s healthy to focus so much on such things :-). I just happen to be the person doing this thing at this time. I am glad that I have been able to offer some limited ongoing support for a thing that other people find valuable.