Do you use OSS projects that cannot follow their own policies?

Question

recently i came across a large project that is interesting and i want to use. the project name specifically likely doesnt matter and may change the discussion so keeping it vague. but i realized all the way up their chain they cannot follow their own policies documented on their site. though any one trying to contribute is criticized for every small detail including having the policies rubbed in their face.the project is a bit too big and complex for me to just fork and do my own thing.what do you all do in these cases? use the project or no? and if so do you try and somehow discuss or point out the policies to others when its appropriate and in a diplomatic way?

giantg2 · Accepted Answer

I work for a large enterprise. We have similar issues with people not following company policies, including the people who's job it is to know those policies - the managers.The best approach I've found so far is to act dumb and ask for the policy documentation so you can "improve" yourself. On your next commit, try to work on a piece of code with lots of violations by others and correct their "tech debt" to be consistent with the policies. Act naive and helpful. This should hopefully seed the idea in the other person that there are existing problems and you just want to help. Ideas are always more powerful when we think we came up with them ourself.