English
| Showing entries 1 to 30 of 30 |
Topics for this podcast:
*Oracle, Java, the Apache Software Foundation and open source
*An update on some open source database and data management players
*CorraTech grows with support for open source application alternatives
*Red Hat-Makara acquisition analysis and impact
*Linux kernel report shows strong support, but what now for Novell?
iTunes or direct download (29:31, 5.1MB)
A new round of GPL-based BusyBox suits has been filed, targeting big names in electronics and IT. We’ve long covered these series of GPL-based suits and settlements, but this latest round comes at an interesting time for open source software and its licensing.
First, we have the backdrop of the Oracle-Sun-MySQL acquisition, with opponents arguing to the world and the European Commission, which is reviewing the proposed merger before approving it, in part that the GPL is, ironically, granting too much power to its user, in this case Oracle. I’ve been quoted in the press and honestly
[Read more...]
+0 
-0
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
+0
-0
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
+0
-0
If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.
(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)
In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.
There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.
The basic principles of this model are:
In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.
There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.
The basic principles of this model are:
In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.
There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.
The basic principles of this model are:
+4
-2
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success.
The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices.
Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our code review process, although technically demanding and very thorough, was kept
[Read more...]
+0
-0
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success.
The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices.
Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our code review process, although technically demanding and very thorough, was
[Read more...]
+0
-0
When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success.
The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices.
Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our code review process, although technically demanding and very thorough, was
[Read more...]Kazuho Oku of Cybozu Labs, Inc., a community contributor to MySQL and SCA signatory, gives a talk on Q4M, a message queue stroage engine for MySQL.
Kazuho Oku of Cybozu Labs, Inc., a community contributor to MySQL and SCA signatory, gives a talk on Q4M, a message queue stroage engine for MySQL.
Kazuho Oku of Cybozu Labs, Inc., a community contributor to MySQL and SCA signatory, gives a talk on Q4M, a message queue stroage engine for MySQL.
It is all about one bug fix, one little feature, one step at a time.
Armin Schöffmann fixed a bug (Deadlock in mysql_real_query with shared memory connections, is what Armin calls it), Armin signed the Sun Contributor Agreement (24 March 2009), Vladislav Vaintroub and Davi Arnaut reviewed, committed and queued the patch to MySQL 5.0 bug team (26 and 27th of March, 2009).
That's a great example of open, contribution-based MySQL development with real results.
Thank you Armin!
Thank you Vlad!
Thank you Chad!
Thank you Davi!
Thank you ... the one whose name I've left out! (Feel free to leave a comment below.)
It is all about one bug fix, one little feature, one step at a time.
Armin Schöffmann fixed a bug (Deadlock in mysql_real_query with shared memory connections, is what Armin calls it), Armin signed the Sun Contributor Agreement (24 March 2009), Vladislav Vaintroub and Davi Arnaut reviewed, committed and queued the patch to MySQL 5.0 bug team (26 and 27th of March, 2009).
That's a great example of open, contribution-based MySQL development with real results.
Thank you Armin!
Thank you Vlad!
Thank you Chad!
Thank you Davi!
Thank you ... the one whose name I've left out! (Feel free to leave a comment below.)
It is all about one bug fix, one little feature, one step at a time.
Armin Schöffmann fixed a bug (Deadlock in mysql_real_query with shared memory connections, is what Armin calls it), Armin signed the Sun Contributor Agreement (24 March 2009), Vladislav Vaintroub and Davi Arnaut reviewed, committed and queued the patch to MySQL 5.0 bug team (26 and 27th of March, 2009).
That's a great example of open, contribution-based MySQL development with real results.
Thank you Armin!
Thank you Vlad!
Thank you Chad!
Thank you Davi!
Thank you ... the one whose name I've left out! (Feel free to leave a comment below.)
I just checked the "Sun Contributor Agreement" (SCA) signatories list, and there are already 11 people who have signed the contributor agreement with an intent to contribute to MySQL.
Among the signatories, you will also notice Paul McCullagh of PrimeBase/PBXT fame. (To learn about how to submit your SCA paperwork, see here.)
Signing the SCA with an intent to contribute to any given Sun-sponsored open-source project would also suffice when it comes to contributing to any other Sun-sponsored open-source project.
So, as an example, Nils Goroll is
[Read more...]I just checked the "Sun Contributor Agreement" (SCA) signatories list, and there are already 11 people who have signed the contributor agreement with an intent to contribute to MySQL.
Among the signatories, you will also notice Paul McCullagh of PrimeBase/PBXT fame. (To learn about how to submit your SCA paperwork, see here.)
Signing the SCA with an intent to contribute to any given Sun-sponsored open-source project would also suffice when it comes to contributing to any other Sun-sponsored open-source project.
So, as an example, Nils Goroll
[Read more...]I just checked the "Sun Contributor Agreement" (SCA) signatories list, and there are already 11 people who have signed the contributor agreement with an intent to contribute to MySQL.
Among the signatories, you will also notice Paul McCullagh of PrimeBase/PBXT fame. (To learn about how to submit your SCA paperwork, see here.)
Signing the SCA with an intent to contribute to any given Sun-sponsored open-source project would also suffice when it comes to contributing to any other Sun-sponsored open-source project.
So, as an example, Nils Goroll
[Read more...]There are some basic, golden rules when it comes to having a vibrant community of contributors.
The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.
Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having
[Read more...]There are some basic, golden rules when it comes to having a vibrant community of contributors.
The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.
Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having
[Read more...]There are some basic, golden rules when it comes to having a vibrant community of contributors.
The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.
Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having
[Read more...]
Until a few months ago, the MySQL community had several complaints about the contribution process. The two biggest obstacles were an unfriendly revision control system and a too demanding contributor agreement.
The revision control system was changed in June. Exit BitKeeper, enter Bazaar. And now goes the second obstacle. Today, Kaj Arnö announced that MySQL has adopted the Sun Contributors Agreement. Kudos!
There are still a few impediments, but the database group
[Read more...]A while ago, MySQL developed a Community Contribution Agreement for community contributions to the MySQL source code. While browsing the MySQL Forge Wiki I came across:
http://forge.mysql.com/wiki/Community_Contributions
This page shows that the Community Contribution Agreement has changed — it is no longer the document MySQL AB created. It is now Sun Microsystem’s standard Sun Contributor Agreement, which CEO Mårten Mickos recently explained to me was “more accepted than the agreement MySQL had come up with.”
I am happy to see some of the great Sun practices trickle down to replace some issues that MySQL did not handle smoothly. All in all, I agree with Mårten Mickos and think the Sun Contributor Agreement is much better….
….but what do you think?
-0
CREATE TABLE t1 (
my_date DATE,
my_month VIRTUAL INT AS (DATE_FORMAT(d,'%Y%m'))
);I hear now about a new competition for the MySQL® Users. The ‘MySQL® 5.1 Use Case Competition’ has been just launched by the Community Team @ SUN|MySQL.
If you submit a MySQL® 5.1 Use Case Report to the Community Team by 31 August 2008 you will have a chance of winning:
More information at
[Read more...]| Showing entries 1 to 30 of 30 |