A native English reader can understand from this statement that Oracle was the original author. Please give the original Swedish authors and contributors credit, rather than the current owner Oracle.
I get your point but it’s been over 10 years, I think it’s fair to read this as “being developed by”, especially as the article is about 5.6 + 5.7 + 8.0, none of which seemed to have originated even in the Sun days.
It took a couple of years to complete porting all of these features. By the time we got to the end, we had evaluated more than 2,300 patches and ported 1,500 of those to 8.0.
This sounds like some terrible engineering practices right there. Forking a core component you rely on should never be taken lightly, but if you do, at least try to upstream your changes (and track their progress) so that you don’t end up with such a situation. Or try and keep pace with upstream and keep reintegrating your changes if they must remain secret at all costs.
They probably have a good story of why they did what they did, and I know they have near endless amounts of money, but this doesn’t strike me as particularly cost-effective.
No, because they don’t distribute the software, they only provide a web service to the public. You would need AGPL for this to take effect. And even then I’m not sure if they would have to do it, since users don’t interact with the MySQL servers directly.
A native English reader can understand from this statement that Oracle was the original author. Please give the original Swedish authors and contributors credit, rather than the current owner Oracle.
I get your point but it’s been over 10 years, I think it’s fair to read this as “being developed by”, especially as the article is about 5.6 + 5.7 + 8.0, none of which seemed to have originated even in the Sun days.
It might be somewhat better if it said “being developed by”, but it does not.
This sounds like some terrible engineering practices right there. Forking a core component you rely on should never be taken lightly, but if you do, at least try to upstream your changes (and track their progress) so that you don’t end up with such a situation. Or try and keep pace with upstream and keep reintegrating your changes if they must remain secret at all costs.
They probably have a good story of why they did what they did, and I know they have near endless amounts of money, but this doesn’t strike me as particularly cost-effective.
I think MySQL is still GPL, doesn’t that mean that FB has to publish their code changes/improvements?
No, because they don’t distribute the software, they only provide a web service to the public. You would need AGPL for this to take effect. And even then I’m not sure if they would have to do it, since users don’t interact with the MySQL servers directly.
Aha! This distinction has never been clear to me, until now.