Comments on: Communication Challenges for the MySQL Community Team http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/ MySQL, FOSS, Sun and Community plus a dash of running and mountaineering Sun, 12 Oct 2008 13:15:19 +0000 http://wordpress.org/?v=2.6.1 By: javamorg http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/#comment-18514 javamorg Wed, 15 Aug 2007 06:21:58 +0000 http://www.planetmysql.org/kaj/?p=124#comment-18514 java.org » http://javam.org/mysql-kapaniyor/ MySQL kapanıyor !!! MySQL kaynak kodu enterprise’a eklenerek ücretli hale getirildi. Özetle: * Açık kaynak topluluğu kendi haline bırakılacak * Para ödeyen enterprise kullanıcılarına öncelik verilip onların dertleriyle ilgilenilecek... java.org »
http://javam.org/mysql-kapaniyor/
MySQL kapanıyor !!!
MySQL kaynak kodu enterprise’a eklenerek ücretli hale getirildi.
Özetle:
* Açık kaynak topluluğu kendi haline bırakılacak
* Para ödeyen enterprise kullanıcılarına öncelik verilip onların dertleriyle ilgilenilecek…

]]> By: gvenaas http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/#comment-18512 gvenaas Wed, 15 Aug 2007 06:14:01 +0000 http://www.planetmysql.org/kaj/?p=124#comment-18512 I disagree with You in that the separation is a good thing. In my work I have always favoured open source, and MySql has been one of my choices. The main reason for this is that I believe that an open source commuity with ALL source code available is the best solution in the long run. The road You have selected now says to me that the MySql company uses more of its resources on making even more money. So the next step from You will likely be another move in that money direction I feel that You have started a direction that will lead to the fact that a MySql solution after a while will hav taken it self away from the potition it has today, as the obvious choice. Stick to the "make money on service" way.... gvenaas I disagree with You in that the separation is a good thing.

In my work I have always favoured open source, and MySql has been one of my choices.

The main reason for this is that I believe that an open source commuity with ALL source code available is the best solution in the long run.

The road You have selected now says to me that the MySql company uses more of its resources on making even more money.

So the next step from You will likely be another move in that money direction

I feel that You have started a direction that will lead to the fact that a MySql solution after a while will hav taken it self away from the potition it has today, as the obvious choice.

Stick to the “make money on service” way….

gvenaas

]]> By: MySql kapanıyor !!! http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/#comment-18505 MySql kapanıyor !!! Tue, 14 Aug 2007 23:15:19 +0000 http://www.planetmysql.org/kaj/?p=124#comment-18505 [...] http://www.planetmysql.org/kaj/?p=124 [...] [...] http://www.planetmysql.org/kaj/?p=124 [...]

]]> By: dbnewz » Blog Archive » Kaj repond à Mike et Jeremy… http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/#comment-18320 dbnewz » Blog Archive » Kaj repond à Mike et Jeremy… Thu, 09 Aug 2007 18:13:40 +0000 http://www.planetmysql.org/kaj/?p=124#comment-18320 [...] Kaj réagit aux discussions d’hier. Mais qu’est ce que cela va changer pour le user landa? Va-t-il se tourner vers la version enterprise? Sachant que j’ai encore des serveurs qui tournent MySQL du 3.23, du 4.0 et du 4.1, cette restructuration aura-t-elle un impact pour moi? Non je ne crois. Pour des grosses sociétés, tous les bugs sont trouvés en phase de test… si la version courante est buggé, je prendrais la précédente. [...] [...] Kaj réagit aux discussions d’hier. Mais qu’est ce que cela va changer pour le user landa? Va-t-il se tourner vers la version enterprise? Sachant que j’ai encore des serveurs qui tournent MySQL du 3.23, du 4.0 et du 4.1, cette restructuration aura-t-elle un impact pour moi? Non je ne crois. Pour des grosses sociétés, tous les bugs sont trouvés en phase de test… si la version courante est buggé, je prendrais la précédente. [...]

]]> By: adaniels http://blogs.mysql.com/kaj/2007/08/09/communication-challenges-for-the-mysql-community-team/#comment-18318 adaniels Thu, 09 Aug 2007 15:45:13 +0000 http://www.planetmysql.org/kaj/?p=124#comment-18318 I think that the most important point of the uprising of the community is left in silence. The enterprise version will have a monthly release schema, while the community version will only be released once each quarter. This means that even though patches for bugs and security issues are available and tested, MySQL AB will not release them to the community until months after. Which is especially disturbing since finding bugs is mostly a community effort. Just imagine how frustrating it is to report a bug, now that has been solved, but simply not getting access to the patch. I can't imagine most enterprise customers would mind if bug fixes are also released to the general public right away. But it feels like MySQL AB is trying to pull the even last doubter towards the enterprise server, by withholding patches to the community. And that just doesn't seem right. I think that the most important point of the uprising of the community is left in silence.

The enterprise version will have a monthly release schema, while the community version will only be released once each quarter. This means that even though patches for bugs and security issues are available and tested, MySQL AB will not release them to the community until months after. Which is especially disturbing since finding bugs is mostly a community effort. Just imagine how frustrating it is to report a bug, now that has been solved, but simply not getting access to the patch.

I can’t imagine most enterprise customers would mind if bug fixes are also released to the general public right away. But it feels like MySQL AB is trying to pull the even last doubter towards the enterprise server, by withholding patches to the community. And that just doesn’t seem right.

]]>