The world's most popular open source database
Kaj is responsible for communicating and evangelizing MySQL within the software development community user community -- as well as representing the community's interests to MySQL's senior management team. Since the acquisition of MySQL by Sun, he has been MySQL's Ambassador to Sun. This involves meeting with Sun teams, customers and communities across organisational and geographical boundaries. Kaj has been with MySQL since 2001 in a variety of executive positions, including managing Services and Engeering. Prior to MySQL, he founded and was CEO of Polycon Ab, a training and professional services provider in Finland and Germany. He began his professional programming career with Datema and IBM.
With MySQL 5.1 having officially been in Release Candidate status since September 2007 and soon approaching GA status, the MySQL Community Team launches a competition for the users of new features of MySQL 5.1:
Submit your MySQL 5.1 Use Case Report to community(at)mysql.com by 30 September 2008 and have a chance of winning.
You may phrase your MySQL 5.1 Use Case Report freely, but the more colour you give it, the better your chances of winning.
By submitting the report, you also volunteer for appearing in our upcoming Use Case articles. We will consider any data you submit in your Use Case Report as public and quotable in our reports. However, you may ask us to anonymise certain aspects of your use case, should you otherwise not be able to participate in our competition.
This is the desired format of your submissions:
From: <you> To: Community(at)mysql.com Cc: <any of your colleagues you wish to inform> Subject: MySQL 5.1 Use Case Report: <Feature> / <App Name> MySQL Community Team, At <company/organisation> we've used <new 5.1 feature> since <date>. We're now on MySQL 5.1.<n> and we started development using <new 5.1 feature> with MySQL.5.1.<m>. Purpose of our appication: Reason we need <new 5.1 feature>: Development environment, OS, language: Deployment environment, OS, hardware: Relevant metrics on size/type of application: Our comment on how <new 5.1 feature> meets our needs: - comments on usability of feature - comments on clarity of documentation - comments on performance - comments on bugs encountered (if you've found bugs, then please follow our bug reporting instructions and share bug numbers from http://bugs.mysql.com in your use case report) Our greetings to the MySQL Engineering Team: Name and email of submitter / developer: Name of organisation: Geographic location (city, country): MySQL Enterprise customer: (YES/NO)
We're looking for Use Cases on all new MySQL 5.1 features, but especially on
Bugs must be reported to our bugs system. Reporting them in a email message is a waste of time for the sender and the receiver. If you have reported bugs about MySQL 5.1, please mention them in your use case with a link to the bug report. If you are affected by an existing bug, please comment on the bug report page in the bugs system, saying how the bug affects you. To your Use Case Report, feel free to add a reference to the bug through its bug number.