Their priorities may not align with yours, but it's not such a bad policy. If you don't like it, fork it?
Their priorities may not align with yours, but it's not such a bad policy. If you don't like it, fork it?
Recently watched Angular Material first dismiss a glaring problem with datepicker, then sit on their hands [0] while some bloke made a complete fix, adjusting anything they brought up, then sit on their hands again [1] after it was finished until someone started building pressure again.
[0][1]: I didn't actually verify that. They might have had some really busy days. Point is they stuck to Google communication policy: try to not say anything at all.
Facebook's lawyers did some very questionable things to "open source" here.
Facebook differs from the standard in that they require your address, but I assume that is to make sure the CLA has the correct form
They even require you to sign their CLA just for README.md updates - that's not "being safe", that's "being willingly idiotic".
Facebook legal is not interested in changing the CLA requirements to something that doesn't discriminate, and despite the rather large number of people who work on their open source projects, who would all love for that CLA to fuck off so they can do open source properly, Facebook as an organisation is still not a good citizen in the open source space. They're still trying to put up a walled garden as much as they legally can, even if you think you can't see the wall anymore.