Should I fork?

[azell]

Greetings,

I really like working with rulebook, and would like to see more features and bug fixes in a relatively timely manner. If resources are not available to handle pull requests, etc. would you recommend forking the project? Thank you for all the hard work to get the project to its current state :).

@Clayton7510

[Clayton7510]

RuleBook has development has been pretty slow. You are welcome to fork.
However, I am also going to change some things around and make easier to contribute, like automated pushes to Maven code owner approvers for merges into develop branch. In hindsight, I should have done that earlier. And this is a WAY delayed response. But if you or anyone else is interested in regular contributions, I'm happy to add you as a code owner to get RuleBook updates moving.

[Clayton7510]

I updated the develop branch so that 2 approvers are required on PRs, but those approvers can be any contributors, not just code owners. That should get things flowing a bit faster. I'm also going to adopt the GitHub Actions workflow from the terraform-maven [deliveredtechnologies] project, which pushes pre-release versions to Maven Central on merge into the develop branch, which should give people faster access to updates prior to a versioned release being cut. They still have to be approved in the com.deliveredtechnologies group when staged for release to Maven Central, but we found in terraform-maven that it makes things move much faster.