Saturday Oct 30, 2010

Into the sunset

sunset

After four years working with the MySQL team, under three different companies, it's time for me to pursue a new career.

Tomorrow is my last working day at Oracle. (Working? But it's Sunday! So, ehm, kind of, anyway, you got the point.)

You may look at my personal blog in the coming days to know what I am going to do next.

Right now, I would like to just say thank you to all my colleagues in the MySQL Team, and to all the community people with whom I have shared the wonderful experience of these four years.

And also, thanks to all the ones who have offered me a job. Really. There were many offers. I am sorry I could not take them all and I had to choose one in the end, but thanks, my friends, for believing in me.

See you around!

P.S.: This blog will not be updated anymore.

Sunday Jul 04, 2010

MySQL track at the German Oracle User Group conference

DOAG

As we have seen for other events, the MySQL community has been invited to attend and participate in conferences organized by the Oracle User Groups.

After the past, present and future events in the United States, now we start with Europe.

There is a MySQL Track at the DOAG 2010 Conference, the main event of the German Oracle User Groups, and the CfP expires on July 10th.

The event is of course important for German speakers, but English speakers are also accepted.

As the other events in the US, this is a good occasion for MySQL users to get acquainted with the independent Oracle user group organization, and find common business needs. There are many MySQL users among the Oracle User Group members, and much curiosity about this small database that powers the Internet.

If you want to get a talk at this conference, feel free to submit a proposal. Or simply mark the dates: November 16th to 18th.

MySQL users, don't be shy!

Follow Paul McCullagh's example, and get ready to explore a yet uncharted but promising territory.

Saturday Jul 03, 2010

Monty doesn't say ...

Monty says:

During the last 2 years, I have seen a lot of the people that originally worked at MySQL AB and who joined Sun together with me, go away in different directions. More than 50 % of them have already left Sun/Oracle.

Matthew Montgomery commented...

I'm curious where you are getting that > 50% number? How would you have any access to that sort of HR information? Sounds like one of those numbers that falls under the "83% of all statistics are made up" rule.

And Monty answered

The MySQL Alumini in linkedin group has close to 200 members, a majority that also joined Sun and this group doesn't include all people that have left. I have also heard the number 50 % from MySQL people that recently left Oracle, so I have good reasons to believe that this figure is reasonable accurate.

Then I left a comment, but I haven't seen it published yet. So here goes

Monty,

Your figure is far from being accurate.

The MySQL Alumni group includes at least 75 people (hand counted, there may be more) who are still working with MySQL at Oracle.

The Sakila Alumni is a group of former MySQL AB employees. I am also part of that group, but I still work with the MySQL team at Oracle. You'd be also pleased to acknowledge that, as of January 16, 2008, when MySQL AB was acquired by Sun, the number of all-time hired employees was way over 600. On that day, there were already more than 200 former MySQL AB employees.

If you have better information that doesn't come from hearsay, I'd like to know.

Giuseppe

Actually, if you go to the MySQL Alumni group on LinkedIn, and click on "members", and then on "advanced search", you get this summary:

So, according to LinkedIn, out of 194 Alumni, 49 are at Oracle, 49 at Sun Microsystems, and 21 in a time machine still at MySQL. That makes 120 people out of 194 who are still with the team, unless their "current company" is not up to date.

And, to make things more clear, let me add something. I was challenged to publish the current staffing numbers to settle the matter. Let me remind everyone who wants to get involved in this silly claim that the burden of proof lies with the claimant. I have no obligation to release company confidential records to dispel FUD.

Friday May 21, 2010

MySQL 5.1.47 and 5.0.91 released - Two strong reasons to upgrade

MySQL security MySQL has released security updates for MySQL 5.1.47 and 5.0.91. The most important changes in these releases are fixes of three security bugs. One of them is a problem that had been lurking in the code for many years, and it was found by chance when one of our developers, testing something unrelated, stumbled upon one of the vulnerabilities. Later on, when analyzing the bug, the developers found one more issue, and they fixed it as well.

MySQL 5.1.47

In addition to the security update, MySQL 5.1.47 is also very important for an additional reason. The InnoDB plugin that ships with this version has been updated to 1.0.8, which is considered to be of General Availability (GA) quality.

There are more changes, including some twists to the error log, to make replication administration more robust.

MySQL 5.0.91 security update

Together with MySQl 5.1.47, there is a security update of MySQL 5.0.91.

Since MySQL 5.0 is now in Extended Support state, the binaries are not in the main download pages, but only in the archives. As the MySQL Lifecycle Policy says, only serious security bugs are fixed, and the binaries are provided at the company's discretion.

If you are still using MySQL 5.0, this is a good moment to upgrade to 5.1.

Tuesday May 04, 2010

The MySQL Community meets the Independent Oracle Users Group

ioug After the MySQL Conference, while most of my European colleagues were busy with volcanic disruptions and seeking alternative routes to the Old Continent, I headed to Las Vegas, to attend Collaborate10 a conference different from the ones I have been used so far.

Collaborate10 is the conference of the Oracle Users Groups. I had been asked to participate with a few talks on MySQL, and I was curious of meeting this for me new organization. I prepared three talks, one introduction to MySQL and two advanced ones, and thus equipped I ventured along the immense corridors of the Mandalay Bay convention center.

The conference started on Monday, but the convention center had plenty of activity on Sunday as well. Part of the action, and a big surprise for me, is that the board of directors of the Independent Oracle Users Group (IOUG) wanted to meet me, and not just informally in front of a coffee cup, but in one of the board rooms, where I was seated at the head of a long conference table and asked to talk to them about MySQL and its community.

Boy! That was quite an experience. That meeting was very pleasant and informative. I learned that the IOUG is very well organized, with national and regional groups, publications, benefits for members, several conferences, and much more that I don't feel qualify to convey in full.

The process of mutual learning called for a presentation of MySQL and its community, which looks comparatively very much scattered and hard to fit under a single umbrella. Nonetheless, we managed to explain the relative positions, and I was impressed by the high relevance given to community in this organization, independently from Oracle, the company. Also very relevant to me is the attitude of the IOUG members, who are very much technically oriented, and thus quite similar to many MySQL users, who like a direct involvement with their tools.

There was not room for final decisions, but we ended the meeting with the understanding that it makes sense for both communities to explore each other and find out how they can eventually interact in common activity, such as group meetings and conferences. The root of the IOUG interest in MySQL is not only in the Sun acquisition by Oracle, but also in the results of a recent survey among their 20,000 members, where 44% of them say that in addition to historical Oracle products, they also use MySQL. Of course this fact calls for a desire of knowing MySQL users and exchanging notes.

Therefore, this is my first pass. I am letting the MySQL community know that the IOUG is willing to know more on MySQL and the MySQL community, and is eager to facilitate the introduction of MySQL groups among its ranks, in the ways that will be mutually determined by the interested parties. Therefore, MySQL users, if you know someone who is a member of the IOUG, you may start getting acquainted and exploring the possibilities offered by this mature institution, and explore in which ways the two sets may overlap.

I am not suggesting any rushed move from either side. Some preliminary courtship and information gathering must precede more serious commitments. But both sides can start thinking about the advantages that one group's exposure to the other can bring along. There is business to be done on both sides of the ditch, as many Oracle users are also MySQL users. There is going to be need for training, consulting, conference talks, integration, migration, and much more may come to mind after some pondering.

For the Oracle community, being in contact with MySQL users may be a refreshing and enlightening experience, since MySQL users are traditionally well versed in Web related issues, and can teach one trick or two to users whose experience is delimited by the walls of corporate rules. On the other hand, the MySQL community can have a similar epiphany by comparing experiences with their Oracle counterpart. I did that for the four days of the conference, and I must say that the questions that I got from this particular audience were quite revealing and useful.

After meeting the IOUG, I managed to meet another board of directors, this time it was the Oracle Development Tools Users Group (ODTUG), a group of very skilled people, who produce high level training sessions that are always sold out and a conference that gathers the best experts on Oracle development tools. The ODTUG is interested in the MySQL community for the same reasons that raises the IOUG attention. But their interest is somehow more pressing, because the main conference, Kaleidoscope, is quickly approaching. Therefore, they wanted to get in touch with some MySQL community people immediately, in order to include some MySQL contents in their conference. The conference is in Washington, and I was going back to Europe, since the volcanic ashes, by the time of my scheduled return trip, weren't a threat anymore. Therefore I gladly absolved my task by involving two super heroes of the MySQL community, who have recently been awarded the title of Oracle ACE Director: Ronald Bradford and Sheeri Cabral. Having left the matter in their capable hands, it wasn't long before they came up with a full emergency schedule for the conference, with an understanding for an integrated and more thoroughly planned schedule for next year. You can see the rest in The MySQL community impacting the Oracle community.

Finally, I would like to spend a few words to thank my hosts at the IOUG conference for their hospitality, for the excellent organization shown, and for providing some fun among all the business, which this picture can describe better than any words.

Friday Dec 11, 2009

Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want to play with MySQL 4.1 binaries, you will have only two choices: becoming a customer (binaries for all versions are kept forever (or as long as someone uses them) for the MySQL Enterprise users) or build it yourself by extracting the code from the Bazaar archives.(1)

For more information, check the calendar and the fine print at the MySQL lifecycle page.

(1) That is not entirely true. There is another way, but I leave it as an exercise to the astute reader.

Tuesday Aug 18, 2009

MySQL Labs : server snapshots available for download

Users familiar with the MySQL development process will remember that our developers use a tool called pushbuild, which builds the server code with the latest changes, using several operating systems, and runs the test suite.

MySQL Labs

This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.

For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community team persisted and kept banging at the door until, at last, we can announce that the binaries are available for download at labs.mysql.com.

These binaries are temporary. You will find online for a few days, and they will eventually be replaced by newer ones. The exact dates of updates are not known. We build every day, but not all the builds are successful. Builds that fail to compile don't produce any binary, and builds that fail the test suite are not exported to the snapshot pages either.

But the binaries will be available fairly often, allowing the community to do early testing on bug fixes or new features.

A word of caution. These binaries have passed a test suite, but they have not been tested extensively like the monthly releases. Therefore, these binaries are for testing only, not for production. To make things clear, the package names include the word "snapshot" and the build date. And the files are not in the same page as the official releases.

Currently (2009-08-18) there are two branches: the latest 5.1 builds and the 5.1 GIS. For each branch, we plan to keep online at least the latest two builds before purging the oldest ones, but we may increase this number if we see that storage is not a problem.

Further releases will be introduced next month.

Notice that, unlike the normal releases, only a few platforms are included, and there are no dedicated packages (.dmg, .pkg, .deb, .rpm) but only tarballs (tar.gz, or zip for Windows). These packages are supposed to be used for testing only. In every Unix system, you can install them using MySQL Sandbox or, if it suits you, a manual installation.

I would like to thank the web and build teams who have worked together to provide this feature, and especially Daniel Fischer and Markus Popp, who delivered the ultimate goods.

Your feedback is valuable. Please let us know what you did with the snapshots.

Monday Jul 13, 2009

The MySQL Librarian is here!

I have had a wish for a few years. I wanted to find a way to put together the valuable information that the community produces about MySQL, a way that would let me easily find the interesting content that I may have missed when on vacation, or when busy with a conference, a company meeting, or a long stream of coding.

That wish started to take shape last year, when I was traveling with Dups during the East Coast tour. I drove, he took notes. He drove, I took more notes. During meals and walking breaks we discussed and refined the idea. When we went back home, a plan was ready. Dups started coding in January.

At first, his changes were completely invisible. He was refactoring the Planet MySQL code to integrate it with the advanced features that had been developed for the main site. After a series of secondary changes, there came the substantial one. The voting system allows people to show their appreciation or dislike of a post. The tagging system makes the blog posts easy to search.

However, that's only blogs. What about presentations, videos, pictures? Welcome to the MySQL Librarian, the coronation of my wish. My congratulations to Dups for coding it under the pressure that a community relations manager is subject to, while traveling across the continent several times, talking at conferences, dealing with communities, paperwork, blogging, his cat, and some more stray duties that fall on his head regularly.

The Librarian is the place where the community creates, collects, improves, and maintain high quality contents. What you find in the Librarian is not the result of a search engine. It's the refined outcome of cherry picking MySQL related articles, videos, presentations, and pictures, done by dedicated users. The MySQL Community. You. Me. Everyone interested.

There is a detailed description of the Librarian in the Dev Zone. No need to duplicate it here.

Please, share my dream. Come make the MySQL community Librarian the best place to find and post valuable information.

Thanks to the early testers for their patience and valuable advice. The MySQL Librarian is good also because of their comments!

Thursday Jun 11, 2009

MySQL has a new release model

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:

  • The trunk is always at least in beta quality.
  • A milestone starts in beta quality ( never in alpha) with a merge between the trunk and a stage tree;
  • Milestone releases, with RC quality, released every three to six months.
  • Integration windows between milestones allow the insertion of new features from stage trees
  • GA releases happen every 12 to 18 months;
  • There are not more than two releases in active support.

The practical consequences of this model adoption is that what was planned for the previous development is now canceled. MySQL 6.0 planned features (Falcon, Maria, Online Backup) are not a priority for the time being.

The next stage tree will be Azalea, which will include the 6.0 features that are stable enough to have a chance to be merged with 5.4 (mainly, subquery optimization batched key access, the fix for Bug#989, out parameters in stored procedures, information_schema.parameters, and some more).

The fundamental difference between this version and the previous one is that Azalea is not blocking. In the previous model, nothing could be released until all the features were ready. In this model, if the features in Azalea are not stable by the time of the intended GA for 5.4, we will rollback, and release only what is ready and stable.

This sort of train model, which has been quite successful with other open source projects, is more dynamic, easy to understand, and more open to participation.

The details of the model are explained in a MySQL University session, today, June 11, at 14:00 UTC (16:00 CET), where Tomas Ulin, director of engineering for the MySQL server, will explain the model and answer questions.

Thursday Jun 04, 2009

MYSQL Planet now with tags and search

Planet MySQL

All this started during a long drive from Charlottesville to Washington, back in November 2008, when I and Dups discussed the status of MySQL Community web presence.

We agreed that we needed to enhance the usefulness of the tools for the community, and MySQL Planet was the first candidate for change. Externally, you have noticed very little until now. First, a login, then the voting system, the Buzz, the Italian, Japanese, and Russian aggregators, an improved treatment for group blogs, and finally the Tags and Searching.

Behind the scenes, there is much more. Dups has been refactoring most of the Planet MySQL code, with the goal of integrating it with the main site. The idea is to eventually allow users to search and use the information available in several formats, such as blogs, forums, presentations, articles, events, and to connect them to each other.

With today's release, we finally see a good reason for logging in to Planet MySQL. Now you can edit tags, thus making the blog posts more useful and easily searchable.

Kudos to Dups and Lenz for the results we got so far. However, there is much more in the making. Stay tuned for the next improvements.

Tuesday Apr 28, 2009

MySQL Community awards 2009

Attending the MySQL Users Conference in 2006, I had one of the best days of my career. At the morning keynote, my name was called, and I found myself on stage, together with Markus Popp, Roland Bouman, and Rasmus Lerdorf, being awarded a Community Member of the year crystal ball. That day is permanently in my mind as a very fond memory.

For this reason, it is a particular pleasure for me to be in a position to suggest the next ones who will hold the community awards. It is a collegial decision, not my own. Each member of the community team submits a few names, we discuss the pros and the cons, and then we settle for the first three names in the list.

This year, the agreement fell on three names, who were included for different reasons.

MYSQL UC 2009 - Marc Delisle Marc Delisle should be familiar to anyone working with MySQL.

As the author of phpMyAdmin, he deserves gratitude and respect from the community.

For the few who are unfamiliar with it, phpMyAdmin is a web based GUI for MySQL, which has helped millions of users to improve their experience with MySQL from beginner to expert.

Probably the only question that everyone in the community will ask is "what? He was never awarded before?". Indeed. This award was long overdue.

Good job, Marc! The MySQL community would not be as large and happy without your contributions.

MYSQL UC 2009 - Ronald Bradford Ronald Bradford has been a community member for long time, with with a genuine passion for MySQl and its ecosystem.

I remember when, in 2006, he fought Sheeri in an auction to get a T-shirt with the developers name. At the end of the day, he had earned himself a mention in MySQL source code, and a solid reputation as a lover of community.

After a brief period as MySQL employee, Ronald has gone back to the trenches, and his contributions to the community have always been constant and of high quality.

Whenever I can, I enjoy working with him. He is a fine analyst and a hard worker.

Well done, Ronald!

MySQL UC2009 - Shlomi Noach

Shlomi Noach is the new blood among the award winners.

His contributions are proof that you don't need to be a superhero to become a good community member. As Sheeri said in her keynote, you just need to do something well. If there is something that you enjoy and can help others, don't ask questions, and do it.

Shlomi's fresh approach in the community arena is a very welcome and necessary addition. The community needs both the extremely advanced articles of Matt Yonkovit and Shlomi's wake-up posts that make some experts scratch their heads and keep them on their toes.

Thanks, Shlomi. Keep being curious! We like it.

The pursuit of openness

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 in our internal mailing lists.

Sakila closed 2

Contributions were scarce, with no good signs for the future. The binary split between community and enterprise servers made bug fixes contributions very unlikely. The impossible roadmap, with contributions going theoretically to version 6.1, in the distant features, practically discouraged any new proposal of code contribution, except for a few brave souls. On top of it, the Contributor License Agreement (CLA) had only recently been set up, yet formed a formidable obstacle for many people.

Sakila closed 1

Faced with such challenges, several people left. Either to new jobs inside the company or to new shores. The challenge is that you can't fix such a problem in one sweep. Changing practices in a company, especially from a position in which you can't take decisions, is really hard.

But not everyone left. The ones who stayed, in spite of the adverse circumstances, share a strong belief in the values of open source, and were determined to succeed, no matter what it takes.

With a little help of my team mates, Colin, Lenz, and Dups, I continued to support Kaj's internal action to spearhead the changes. While my younger colleagues were busy managing the community, Kaj and I were gently wrestling the rest of the company, to steer its direction towards a more open course.

The results arrived. Slowly, but surely.

  • In 2007, many developers opened the IRC gates, and started using freenode.net;
  • June 2008 - The open source Bazaar replaced the previous lock-in proprietary software Bitkeeper, which didn't allowed handling of the source from the outside;
  • In October 2008, we got rid of the CLA, in favor of the more open Sun Contributor Agreement.
Sakila open 1

The major obstacles were still the binary split and the long release cycle. There were much discussion internally, pleading and cajoling, to convince people that we were on the wrong path, and that our business model required a more open approach. Our team was under pressure. We were between the hammer of the community, shouting at us for not being open, and the anvil of the sales and marketing teams, unwilling to accept the assumption that a happy community generates future customers.

We kept going, and we kept pushing, until we got the announcement at the MySQL Conference 2009, stating the end of the binary split. Now the community server binaries will be published as often as the enterprise ones. The rationale of this request is that the strength of MySQl is in its wide community. We claim that the MySQL server is tested by millions of users, and yet we were giving the GA (mature) binaries only to a handful of customers.

This looked like a privilege, but it was in fact, from an engineering standpoint, a disadvantage. As a customer, I would gladly adopt a software that has been installed by a few million people, rather than being the privileged first one to try it in production.

With this announcement, we are back to the position that has made MySQL so popular and trusted. A database with a large user community.

The last barrier to fall will be the roadmap. So far, we have been tied to an impossible roadmap, with a wish list of features that had little chance of being released. The experience of MySQL 5.1, which took 37 months to release, has taught us a hard lesson. The next version, 6.0, has been in alpha for 25 months, with no near end in sight. Now we took the hard decision to replace the previous roadmap, where we piled features over features in an impossible attempt of pleasing future customers, with a milestone model, where we release features as they are mature, without waiting for all the features in the list to be ready. It means that we renounce the goal to release Falcon and Maria and the Online Backup as one single big bundle released at the same time in 6.0, and we put them aside. The MySQL engineers will schedule features for release as soon as they reach beta status, without waiting for the trailing ones.

Furthermore, we have now a process in place to accept contributions and to review them, with active participation from core developers. Yet, we have still work to do, to smooth the rough edges both internally and externally.

Sakila open 2

To our developers, who have not succumbed to the pressure, and have delivered top class software, while accepting our team's (not always) gentle suggestions to more openness, a hearty thank you!

To the many who have believed in MySQL and in our single and team efforts, thank you! To the many, who have suggested improvements, and contributed actively to our changes, thank you! To the ones who have not joined the flame war when unjustified rumors spread across the net, thank you!

To the ones who spread FUD, and twist every tiny piece of news in the shape of a conspiracy, I say wake up. Have you considered the possibility that we actually strive for the best for our community?

To the naysayers, who shout at us and abuse our goodwill from their self appointed righteousness, which often hides a secret business agenda, I say that we have always be working with the community in mind, and we will continue to improve. The path is still uphill, but the community team, the guardians of MySQL ubiquity, is happy with the progress so far, and will continue on this course!

Tuesday Mar 03, 2009

BoFs welcome at the MySQL Users Conference and Expo 2009

As usual, the MySQL Users Conference and Expo includes Birds of a Feather (BoF) sessions.

For the uninitiated, a BoF is an informal discussion group about a common topic. There is no registration and no fee for a BoF. You can organize one even if you don't plan to attend the main event. If your BoF is accepted and scheduled, you can organize it as you like. You won't get a free pass for a BoF, though.

We provide the rooms. You bring in the ideas. Submit a BoF proposal!

Almost everything is suitable for a BoF. We only ask that it is related to MySQL.

  • Do you have a project that you are developing and it is still in vaporware stage? No chances for the main conference, but perfectly OK for a BoF.
  • A topic that you feel is missing from the main schedule? Make a BoF.
  • Your favorite connector is neglected? A BoF may revamp the community attention.
  • Have you created a killer scheme that solves MySQL replication one-master-many-slaves limitation? Show it in a BoF.
  • Your fork of the Archive engine is the best thing since sliced bread? Boast it in a BoF!

Imagination is the only limit. Get a good idea. Make it known!

Friday Jan 23, 2009

MySQL Users Conference with embedded MySQLCamp

Well, I announced it a few months ago, and now Sheeri made it happen. The MySQL Users Conference and Expo 2009 will have a MySQL Camp embedded.

What is it? Asked most of the people I know, including many colleagues, some of them worried that I was giving away the company jewels.

For starters, it is not a competitor of the Users Conference. It won't duplicate its contents, nor is a way of sneaking into the main conference without a pass. It is a camp, and if you have attended either one of the previous MySQL Camps or the OpenSQLCamp, you know what I mean.

MySQL Camp is a gathering of MySQL geeks, developers, enthusiasts, code twisters, gurus, who want to exchange views on deeply technical matters. It is not run by Sun. While we have given Sheeri the task of organizing the event inside the event, we have purposely avoided being involved in the task itself. We want the camp to be a community event, and by community we mean you not us.

Let me just remind the rules of the game, as stated in my original post. Sun provides the room for the event and the rest is up to Sheeri, with two main guidelines.

  • Only MySQL related contents. This is the MySQL conference, and thus, if you want to hack a videogame or the latest music player, this is not the place to bring it.
  • No advertising. The Camp is a place for hacking code and exchanging technology. If you want to advertise your company, the main conference provides sponsoring and partner agreements that will allow anyone to promote their products.

Other than that, have fun!

Thanks, Sheeri, for organizing this event with your usual dedication and efficiency!

Tuesday Dec 09, 2008

Planet MySQL in Italian, and a new buzz!

New features for Planet MySQL.

Lenz has opened a new section for Italian blogs (I should say blogs in Italian, since there are blogs that are hard to classify).

Thanks, Lenz. We'll try to fill it with some good contents.

In the meantime, Dups was creating a new feature for the Planet. MySQL Buzz is a window on living contents about MySQL, from forums to blog posts, to news and videos.

The Buzz has a fun part. A cloud of most frequently used words. If you look closely at the forum cloud, you will see a THANKS. Forums are powered by the community. Kindness included!

About

Giuseppe Maxia

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today