Status of the project

[bopm]

@thomas-mcdonald, what is this project's current standing? Based on contribution activity and the number of PRs collected, it's in hibernation mode. Looking at the owner organization, you are only one of three members who has been active in the last year. Open PRs contain some important improvements from looking at them. Any idea for the project's intermediate future? Should it be considered for use at all keeping these problems in mind?

[thomas-mcdonald]

I am not actively using Rolify in my day job anymore. I volunteered to fix, merge and ship some performance issues that were impacting us at the time. I am happy to help steward where I can, but I'm not really a great person to be driving it forward and I think to some extent it is 'ok' if Rolify is feature complete, as long as there are no showstopper bugs - we used rolify for a long time and it worked fine! Broadly cognisant of the following risks:

• People who are using Rolify are using it for critical aspects of their application and I am quite risk averse. As an example - I wanted to ship the has_many through: PR but concerned about potential impact on changing the association type for existing users who might rely on that behaviour.
• There is a whole branch of code dedicated to MongoDB I have never used and tests do not pass with modern gems. I would love to cut this out, would make the surface area so much more approachable.
• The API is probably too flexible, even with decent(ish) test coverage, it's hard to fully reason about how a change might affect consumers.

I think if there are important improvements that should be released and you have the motivation and time to get them mergeable I am happy to press the buttons as required!

[januszm]

@thomas-mcdonald I'm going to use this gem in production apps for longer time, happy to join the maintaners team