> If Patrick can use his AI-based kung-fu to get things to where they're > working, don't break backwards compatibility / old branches, have a sane > sustainable workflow, and have updated docs that look good and are > maintainable on trunk - God Speed. We should all be rooting for him.
Yes, aligned here. > If you have specific "this approach isn't going to work because of > non-obvious, non-documented constraints A-Z" based concerns, please by all > means air them. Those are things we should write down and codify in the repo > so people that come along with interest and energy have the context they need > to know what constraints they're working with. If it's instead "this is > making too many changes at once to a thing", I'd contend that the thing he's > looking to make changes to is something that's not being heavily actively > maintained and that has a lot of gaps. Yes, there are specific concerns, and some are documented (jira tickets and todo/fixme comments) and others are not. I'm trying to air them. And yes, docs are living and actively maintained (despite pain-points and debt): - https://github.com/apache/cassandra-website/commits/trunk/ - https://github.com/apache/cassandra/commits/trunk/doc
