If you love a software product, you should try to improve it, and not be afraid of criticizing it. This principle has guided me with MySQL (where I have submitted many usability bugs, and discussed interface with developers for years), and it proves true for Tungsten Replicator as well. When I started working at Continuent, while I was impressed by the technology, I found the installation procedure and the product logs quite discouraging. I would almost say disturbing. Fortunately, my colleagues have agreed on my usability focus, and we can enjoy some tangible improvements. I have already mentioned the new installation procedure, which requires just one command to install a full master/slave cluster. I would like to show how you can use the new installer to deploy a multiple source …

A href="http://us1.campaign-archive1.com/?u=33d934c165e69e4b507504c2b&id=8771dc3ae5&e=77c352ede8#mctoc1">report
from the Peer to Patent initiative shows
that the project is having salutary effects on the patent system.
Besides the greater openness that Peer to Patent promotes in
evaluating individual patent applications, it is creating a new
transparency and understanding of the functioning of the patent system
as a whole. I'll give some background to help readers understand the
significance of Manny Schecter's newsletter item, which concerns prior
art that exists outside of patents. I'll add my own comments about
software patents.

Let's remind ourselves of the basic rule of patenting: no one should
get a patent for something that was done before by someone else. Even
if …

Guest blogger Pamela Samuelson is the Richard M. Sherman Distinguished Professor of Law and Information at the University of California, Berkeley. She teaches courses on intellectual property, cyberlaw, and information privacy, and she has written and spoken extensively about the challenges that new information technologies pose for traditional legal regimes. A version of this material is scheduled to appear in the November 2010 issue of Communications of the ACM.

Two-thirds of the approximately 700 software entrepreneurs who participated in the 2008 Berkeley Patent Survey report that they neither have nor are seeking patents for innovations embodied in their products and services. These entrepreneurs rate patents as the least important mechanism among seven options for attaining competitive advantage in the marketplace. Even software startups that hold patents regard …

In response to the IEEE's report on Patent Power, which lists the top companies ranked by number of patents, Ari Shahdadi and Brad Burnham made trenchant comments in email that I thought were worth sharing (with their permission):

Ari wrote:

The main article is sad to read, with choice quotes like this: "Clearly, the global recession seriously hampered innovation in the United States." If I'd like to do anything, it's end the use of patenting statistics as a metric for innovative activity, especially by groups like the IEEE.

Brad responded:
…

On Thursday the 8th, we delivered the most successful italian MySQL webinar ever. We had about 350 registrations, thanks for your support and constant participation!
We also awarded a wonderful MySQL t-shirt to the one who first answered correctly to a trivia question, congratulations to the winner.

Looking into the story of italian webinars, here is the ranking in terms of registrations:

1. Getting Started with MySQL on Windows
2. Scalable MySQL High Availability Architectures
3. A guide to Scaling MySQL
4. MySQL Performance Tuning - Top 5 Tips
5. Introducing MySQL 5.0

If you were unable to participate you can click here and listen to the on-demand …

The big news to kick off this week was Oracle’s announced acquisition of Sun Microsystems. There is already a lot of discussion of the integration challenges, how Oracle is getting into hardware (or as Matt Asay describes it, having an ‘iPod moment’) and of course, the implications for open source software. What stands out to me is the fact that the world’s biggest proprietary database player — one of few software giants that still sells and supports primarily proprietary software — will own the world’s most popular open source database, MySQL. It is unclear how significantly MySQL figures into the deal, but given Sun spent $1b acquiring it and further invested in its enterprise readiness and use, …

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 contributed to the ideas and practices behind these rules.

A) …

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 contributed to the ideas and practices behind these rules.

A) …

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 contributed to the ideas and practices behind these rules.

A) …

This is Zak Greant's weekly report on his activities for the Mozilla Foundation from December 29th, 2008 to January 4th, 2009.

Overview

Another week of the Christmas and New Year holidays with many of my Mozilla colleagues unavailable. As with the previous week, I focused on 2009 program development and engagement.

The program development work was in the form of brainstorming, planning and research for upcoming 2009 Mozilla activities.

The engagement work focused on participating in the Mozilla blogorama. I kept up with Planet Mozilla, commented on blog posts I found interesting and continued a series of lightweight blog posts.

More details on both activities follow:

Program Development

I finished drafting a new statement of work and sent this to …