Ritikesh

@mcclayton - would it be possible for you to discuss with the other maintainers within Procore (if you're still in touch with them) and see if they'd be willing to...

I've tried reaching out to the maintainers via various forums (gitter, issues, PRs) from the past 1-1.5 years, but the project seems increasingly inactive going ahead. Even this issue has...

Released - https://github.com/blueprinter-ruby/blueprinter/issues/1.

The fork has had some traction and we've pushed several updates including performance improvements, CI via github actions, support for non-AR objects to name a few. You can checkout the...

@lessthanjacob appreciate the transparency and updates. I had created the fork with the below caveat, that I'd happily move/contribute-back all the relevant changes to the upstream, provided Procore changes their...

thanks @lessthanjacob for recognising. we'll wait to hear soon from you. cheers.

@lessthanjacob thanks for the update. We'll also need to discuss about how we want to merge upstream changes from [#blueprinter-ruby/blueprinter](https://github.com/blueprinter-ruby/blueprinter) to this repo as well. > Wanted to provide a...

Thanks @lessthanjacob. I'll work towards creating a PR and also setting up the process on sunsetting the fork.

@lessthanjacob - PR raised - https://github.com/procore-oss/blueprinter/pull/327 > Thanks @lessthanjacob. I'll work towards creating a PR and also setting up the process on sunsetting the fork.

@jasonkarns this is a good suggestion - would you be willing to raise a PR for it? Let's ensure backward compatibility is maintained though with a deprecation notice for the...