The Apache Flagon project, encompassing its child projects, faces operational fragmentation resulting from the polyrepo approach used for its version controlling. This fragmentation imposes challenges in maintaining project consistency, ensuring community health, and attracting as well as retaining contributors.
Solution
I believe migrating to a monorepo approach would vastly lower technical debt by simplifying the project structure. Over time this will pay dividends which will help us increase our velocity and hopefully spur more community growth.
Details
I've circulated an email to dev@flagon.apache.org requesting feedback on this RFC in Google Docs itself. I highly encourage participation from the community.
TL;DR
Problem
The Apache Flagon project, encompassing its child projects, faces operational fragmentation resulting from the polyrepo approach used for its version controlling. This fragmentation imposes challenges in maintaining project consistency, ensuring community health, and attracting as well as retaining contributors.
Solution
I believe migrating to a monorepo approach would vastly lower technical debt by simplifying the project structure. Over time this will pay dividends which will help us increase our velocity and hopefully spur more community growth.
Details
I've circulated an email to dev@flagon.apache.org requesting feedback on this RFC in Google Docs itself. I highly encourage participation from the community.