Archive for the ‘Open Source’ Category
Yesterday I attended CPOSC 2009. The conference was great. It was very well run, and I liked the sessions. I would definitely attend this conference again, and will recommend that Percona sponsor it next year. I attended the following talks:
- Stop Worrying and Start Monitoring with Nagios (Andrew Libby)
- DRBD, Network Raid, High Availability and General Awesomeness (Brian Gorka)
- MySQL Performance Tuning for non-DBAs (Tom Clark)
- Wonderful Desktop Tricks, and Aesthetics (Seth Jerome)
- Jump Start Django: The Web Framework for Perfectionists with Deadlines (Rob Yates)
- Watching and Manipulating Your Network Traffic (Josiah Ritchie)
And then of course I gave my own talk on Maatkit (slides). I didn’t follow the slides. I took a quick poll of who was interested in learning about making an open-source project that can support a full-time employee, and nobody was, so I skipped that and talked about what the tools can do.
In meta-news, it seemed that a lot of people already knew about Maatkit, and Percona’s name and open-source software (high-performance versions of the MySQL database server, XtraDB storage engine) seemed pretty well known too. Someone asked if Percona can support a MySQL Cluster project that has stalled with another vendor, and I was happy to say we can. Several people complimented Percona’s training, which is really a compliment to Morgan Tocker.
I just adore Google Code. But the default wiki view (a list of pages, sorted by last-modified) is lacking something. Fortunately, it’s fixable. Here’s the before:
And here’s the after:
- Create a wiki page called TableOfContents, or something like that. Using normal wiki syntax, enter links and text for your table of contents. The best way to do this is to use bulleted lists to organize and outline the pages. Keep in mind that we’ll use this same text for the sidebar, so keep it brief.
- Go to Administer/Wiki and enter that wiki page’s name in the “Wiki Sidebar” box. Save the changes.
- Go to Administer/Tabs and enter the same page in the Wiki box. Save the changes.
Now both the wiki “homepage” and the sidebar will contain the page you created. No more ugly list-of-pages. And as you navigate through the wiki pages, the sidebar automatically expands and closes the outline to show where you are.
If you want, you can use a different homepage and sidebar, but I’ve found that it works well for me to use the same page for both. It’s a preference, that’s all.
There’s one more trick I’d like to share: you can add the text
<wiki:toc /> at the top of any page to create a small table of contents for that page. There are ways to customize it — check the documentation for more options.
At the MySQL conference, a person who used to hold an important position in an important sales organization told us something like the following: “You know, you guys at Percona are great, but you have a big problem. You don’t have any $500,000 customers who only file one support incident per year. Those customers are where you can really make big money.”
We were well aware of the investigations this person did into which customers are the most profitable, and we had decided a long time ago that chasing huge sales without delivering matching services is flawed. I told this person as much: “that model is fundamentally broken because it doesn’t align cost with value delivered.”
Actually, we do have customers who rank in the top 50 of the Fortune 500. I’m thinking of one right now. They filed only one case so far. And they’ve paid us for exactly the amount of hours we spent on that case. And far from being a problem, this is exactly where we’re doing things right.
Some people may see us as shrinking the pie by billing just a few thousand dollars for “huge jobs.” They might think we’re silly for telling the customer that a few hours on the phone and remotely is going to be better for them than a week onsite. They may consider us small peanuts because we don’t have 10-million-dollar deals. What they are missing is what the customers see clearly: it’s good to write win-win contracts and leave something on the table. If it looks like table scraps to Mr. Million Dollar Salesman, that’s okay. Those bloated “profitable” contracts are short-term thinking, and they’re actually a serious weakness. Don’t celebrate our “problem” too much. Keep an eye in the rearview mirror. Is it a problem, or is it our secret sauce?
One problem I think we might actually have is how to get a good sales person with our model. You see, we don’t actually have any sales staff at all right now. I am not sure the math would work out the way a traditional sales person would like. But that’s because a traditional sales person is used to being rewarded for “earning money for the company,” which I think is really broken, at least in the way it’s traditionally implemented.
I’ve said before that I think one of the reasons MySQL was unable to create an open-source business model is that their sales folks pushed the company in the direction of closed source. I’m honestly not sure what the best open-source sales model is. I know that I really feel good about our services delivery model and our pricing model; right now our sales model is nonexistent. We are passive; we just answer inquiries and sign contracts. As things stand now, nobody’s doing any sales.
Still, I think this is a good problem to have, and I trust that the right person will come along and see the opportunity to create a good salary at the same time as really providing a service to Percona and the customers. That person will explain to us how cost (salary) and value (service to us and customers) can be impedance-matched too. And that will probably be an innovation, or at least unconventional. With all the other ways Percona is unconventional, I don’t expect us to create a conventional sales model either.