Unless they plan for their repo to have zero contrib policy and open merge rights, they will also have to follow rules and force people to follow their (third p

Unless they plan for their repo to have zero contrib policy and open merge rights, they will also have to follow rules and force people to follow their (third party) rules. Sometimes it's worthwhile to consider that the "third party rules" you don't want to abide, are there for good reason. Furthermore, sometimes the underlying reason for those rules is something you can hack on and open up. "Oh we won't ever support feature X because of legacy arch Y so no PRs for feature X please". Well, perhaps you can solve legacy arch Y and help everyone at a more fundamental level.