montywi

6 ms·

1.
by montywi 10y ago
The old versions of MaxScale will of course get security and critical bug fixes. The MariaDB corporation will also accept patches to the GPL and BSL versions of the code.
2.
by montywi 10y ago
When it comes to MaxScale, the older versions will get all security fixes and also critical bug fixes. The MariaDB corporation is also happy to accept contributions to the GPL and BSL code, so there is really no reason to do a fork, except
3.
by montywi 10y ago
I have been in several business discussions regarding source code in escrow and in all of them they have agreed that having the code released as BSL or eventually Open Source would be ok with them. After all, companies using your software w
4.
by montywi 10y ago
Not that MySQL was created before Open Source was coined. MySQL was hugely popular (several millions of users) way before it was GPL. David and I always planned to make MySQL Free Software, but we needed first to get enough momentum to be a
5.
by montywi 10y ago
PHP was supporting MySQL way before MySQL was Open Source. MySQL was released in 1995 under a liberal but commercial license (You should pay if you make money with MySQL) but was changed to GPL in 2000 "when we had got enough money in
6.
by montywi 10y ago
Agree. However Dual licensing (on GPL) only works with software that other companies want to embed into their Software. BSD was created to give similar benefits as Dual Licensing for software, like MaxScale, that is not embeddable. Dual lic
7.
by montywi 10y ago
Most usage of MaxScale is one of the following: - One Master with one Slave (for backup and high availability) - Galera with 2 masters and the Galera Arbitrator This covers possible 90% or more of the common usage cases. MaxScale is usually