I guess Oracle just don't see MySQL as enough of a threat, or enough of a profit opportunity, to shackle to the mothership with contributor agreements.
Indeed it might even speed up MySQL development, potentially undercutting Oracle's serious open source rivals.
Oracle has a problem in that PostgreSQL is somewhat of a threat, in terms of features and similarity. OK, the default stored procedure language is not exactly the same, but it's fairly close to PL/SQL.
Nobody is going to mistake MySQL for Oracle, and I suspect Oracle wants to keep it that way, while dragging MySQL along just enough to prevent an exodus of FOSS developers to PostgreSQL.
I should probably re-evaluate MySQL again, but they scared the Hell out of me back in 2001 when I found it did not support rollback, nor foreign key constraints, nor transaction isolation at the time. I KNOW THEY HAVE FIXED THIS STUFF SINCE THEN, but the mentality that thought it was OK to leave that stuff out??? I did enough xBASE stuff in the 80s to know I did not want to back to that confusion. I would rather use an ISAM interface than debug query planning in SQL, but having to use SQL, and getting none of the data integrity benefits?!? Screw that!
Y'all enjoy your MySQL, and I hope the whole source code license issue works out well for you :-)
Indeed it might even speed up MySQL development, potentially undercutting Oracle's serious open source rivals.