Would you be interested in joining forces?

Problem/Motivation

We were asked to make revision log messages across all our revision-able content entity types required for a client this year. I saw this module, and while it looked very polished, it only worked for node entities, so we wrote a custom module to support blocks, nodes, and media. We approached the problem a broader scope than this module, but the fundamental idea is similar.

We recently got approval to release our work to the community, and I'm trying to figure out if it makes sense to join forces with this module or create yet another version of "require revision log message".

Unfortunately the code we have is quite different than this module since we were solving for multiple entity types, and there were a number of edge cases we had to consider when expanding the scope. Examples: media library add forms, inline (layout builder) versus reusable blocks, revision log messages on the layout builder form when saving nodes, content moderation integration, etc.

I feel like if we did integrate, the module code we have might need to replace a large section of the code in this module. I'd also really want to be a co-maintainer in that case. It looks like there is some desire to expand to other revision-able entity types per #3293857: Support all entities that implement the RevisionLogInterface.

What are your thoughts? I totally understand if it doesn't make sense to integrate, but I wanted to at least reach out before creating a very similar module.