And we save money by relying on GitHub's excellent tools, rather than wasting it, trying to recreate or stand up a similar platform. The communities wanted closer integration with GitHub (what they knew/used elsewhere), so we made it happen.
That is simply not true. Please take your conspiracy theories elsewhere.
Apache maintains clones of all our GitHub org's repositories. GitHub has no leverage over our repositories. We have a fallback mechanism for contributors to push to our server, if they deny GitHub T&Cs.
Apache has the support of GitHub and Microsoft, from the CEOs of both, and through the organizations.
Correct. We are pragmatic-focused. The communities asked for better integration with GitHub, so we provided it. (nothing to do with non/copyleft licensing regimes)
Mind you, we maintain private mirrors and have restrictions on some of the GitHub access/workflows (eg. ICLA on file, and 2FA required). We still need to track provenance, and must be able to operate independently, if it comes to that.
Not to us here at Apache. We wanted the GitHub tools to be available to our projects. Why try and recreate all that on our own? Waste of resources. The ASF is for creating software for the public good; having a great version control tool website is not in that mission. We chose to leverage GitHub instead.
And yes, lots of our communities have been asking for better GitHub support (read: access to its tools). So we made it happen for them.
Yes, it works just fine. Many projects at Apache rely on MIT-licensed code, and I know that several of the Apache projects are looking towards Preact as a replacement for their dependency upon React.
