Motorola and Google join the GNOME Foundation advisory board

freesoftware, gnome 5 Comments

Big news yesterday! Motorola and Google joined the GNOME Foundation advisory board.

Just let that sink in a little…

Google and Motorola are two huge companies, showing support for, and confidence in, the GNOME project. While it might be possible to dismiss Google’s participation as just helping us out, it’s interesting to see what Christy Wyatt has to say about GNOME and Motorola’s strategy: “For mobile Linux, Motorola believes in open standards and open source technologies”.

What this implies to me is that while Motorola may be trending towards Android for their next generation of smart phones, they’re going to be keeping the MotoMagx option open, even as they turn away from LiMo. Perhaps a small strategic skunkworks project, pottering away and keeping an eye on how things develop?

In any case, I welcome Motorola to the foundation, and I hope that we have a long and fruitful collaboration.

Jerry Maguire on the future of the free software industry

community, freesoftware, marketing, work No Comments

[Reposted from my professional site]

Suddenly, it was all clear. The answer was fewer clients. Less money. Caring for them and caring for ourselves.

Jerry Maguire

“Fewer clients. Less money.” Sacrilege in a world where the goal is to grow the first billion dollar “open source vendor”. But that chimera that Matt Asay holds a torch for may never come. Free software has a lot of selling points – and the main one is that if your vendor is charging you too much money, you can find a different, smaller one who will charge you less.

That doesn’t mean that the originator of the software can’t make money – knowing the software better than anyone else, and being able to customise the software, is a pretty powerful selling point and a clear path to building a profitable small business.

As many commentators have said (and I agree), support is not a scalable business model. Other smaller, more agile, companies can start businesses around your product, gain expertise, become contributors to your project, and syphon off some of that yummy support and maintenance cash you’re hunting for.

But so what? Free software doesn’t get developed like proprietary software, why should the free software industry look like the proprietary software industry?

Here’s my vision of the future: Smaller businesses. Each with fewer, happier clients. Less money. Lots of them, all over the world.

Call to release team: Open shop on GNOME 3.0 planning!

freesoftware, gnome 6 Comments

vuntz has blogged today about some of the brainstorming that has come out of the Summit this year – and that’s great. The Summit’s an important chance to get a lot of focussed work done.

It’s a start on the road to a GNOME 3.0, but it’s not enough. what I’d like to see happen now, if the Release Team (and indeed the GNOME community) is serious about implementing a two-step 4/4 beat in the project, where every 2 to 3 years we have a major version, and we continue with our 6 month drives, then we need to get serious about co-ordinating those major feature arcs.

I’ve discussed this a few times in private, but nothing’s been announced – so as I threatened to do at the JDLL, here’s what I think that the release team should do: Open a consultation period when the community proposes major themes/feature arcs for the desktop – proposals might be conservative or ambitious, it doesn’t matter. They should be realistic, but exciting and over-arching.

Some examples I can think of are “Integrate with web services where appropriate” – and give examples of the web services and applications in question – or “Make contacts first class objects” – and show the interface for this, how we start to depend on libsoylent, various applications that include presence, more than just throwing out an idea, getting concrete about what needs to be done for the feature arc.

After the (short) consultation period, the release team announces the theme for GNOME 3.0, consults with the various maintainers concerned to ensure we’re all on the same page, and that major features are added to the mid-term roadmaps of all the applications concerned. And then magic happens, code gets written, and we have a major new feature arc for our desktop in 1 to 2 years time.

Rinse, repeat, every 2 years or so – in the run-up to a major release, we pick a new major feature arc and drive for that. In the absence of this kind of co-ordination, we will continue to have the kind of piecemeal progress that we’ve seen over the past few years – all our apps are improving, the GNOME experience is better than ever, but we don’t have a story to tell.

Maemo Summit day 1: Meeting people, learning stuff

community, freesoftware, maemo, work 4 Comments

Coming to the end of the first day of the Maemo Summit in C-Base in Berlin. From just outside, you have a view of the antenna of the space station that the C-Base group have been mapping out for the past few years. For those who don’t know, this is the terraforming space station which brought life to earth, and which crashed in what is now Berlin 4.5 billion years ago. Only the central tower, now in use as a television tower, is visible above ground.

The two days in OSiM World were useful and educational. I got to meet people from companies trying to learn how to work well with Free Software, which gave a great opportunity to affect real change by talking to the decision makers in those companies. I also got to meet some Maemo people who came to OSiM to meet up and hang out at the Maemo/Nokia stand (by far the most active stand in the conference, by the way).

But the Maemo Summit is a refreshing counter-weight to that – some of the observations that people made this morning were:

  • We got better wireless and power for free than at the high-powered conference people paid thousands of euros to attend (given that the CCC is involved in C-Base, that was not surprising to me)
  • The vocabulary has totally shifted. We’ve moved from value propositions, cost-benefit analysis, return on investment and fragmentation to people getting excited about tracemonkey, PowerVR, OMAP3, Clutter, hacks, crashes and bugs… the people who are down in the trenches and know what free software is are here.
  • Less suits, more t-shirts

It has been an amazing day so far – some big news from Peter Schneider this morning that the interface for the Fremantle will be Clutter based – Rodrigo Novo  went into more details:  Nokia are funding new tablet-oriented widgets and off-screen support for GTK+, the integration of Clutter, and more.The lightning talks were fascinating for the breadth and depth of things which people are doing with Maemo – everything from using them in police cars to porting PyPy through running Debian in a chrooted environment as a Maemo application (presentation given in OO.o running in said Debian on an N810!!!).

As usual, what’s most impressive at these things is meeting old friends and making new ones. I’ve got to spend lots of time with Stormy, Paul Cooper, Jim Zemlin, Lefty, Bdale and others, and today I had a chance to have a good chat with Rob Taylor, Philippe Kalaf, Murray Cumming, Simon Budig and more. I was very happy to put a face to Tero Cujo’s name, the latest addition to Nokia’s maemo.org team. I’m a little disappointed not to have met anyone from Nemein here yet after working with them for so long – but Henri is in Korea for an international Haedong Kumdo competition, and getting his 23rd Dan (or something like that) confirmed by a master while there.

In addition to the summit, there is also a desktop search hackfest happening over the next two days, with people involved in Tracker, Beagle and Xesam getting together to agree on interfaces and work on implementation, to bring rocking search to desktops and tablets of the future.

There’s a heavy GNOME influence at the conference, which makes the various noises I hear about Nokia backing away from GNOME seem exceedingly over-stated. It looks to me like Nokia are using more and more of the GNOME and freedesktop.org stack, and are more than any other company right now setting a direction for GNOME in the future with investments in technologies like Clutter.

So far, great stuff! Looking forward to the party tonight, and day 2 tomorrow.

Community management

community, freesoftware, maemo, work 2 Comments

On Thursday I’ll be participating in a panel at OSIM World“Effectively Building and Maintaining an Open Source Community”. It was a happy coincidence when I saw Matt Asay writing about the issue on Friday, and again today – it gives me a chance to think a bit more about the issues involved, and provides a data point which is very close to the experience that I have repeatedly seen when companies decide to use free software, be it peripherally or strategically.

On several occasions I have seen a lone developer decide to use a free software library to do some job for him. It doesn’t quite fit his needs, but he hacks up the extra feature or two in a couple of days, finds a few bugs that he fixes along the way to make things work as he needs them to, and ships it to a client as part of a larger solution.

At this point, one of two things will happen. The external project either stays as-is in the SCM of the company, awaiting a future upgrade request from the client, or the developer (usually because he is “the Linux guy” in the company and knows about these things) bundles up a couple of patches, heads along to the bug database for the project, signs up for Yet Another Bugzilla Account, and creates three or four bug entries with bug fixes attached, and another one for the new feature he hacked up. All told, he spends maybe half a day cooking up patches, navigating account creation, and submitting his work.

Usually, the patches will sit there for weeks or months before being reviewed. In most projects, if you don’t go onto a mailing list or IRC channel and ask the right guy to take the time to look at them, you can expect to wait. He has a backlog, gets lots of bugzilla nag mail already, and anyway, he’s working on a new feature he wants to get done this weekend between playing with the kids and doing the grocery shopping.

When they do get reviewed, the code base is likely to have shifted, so the patches don’t apply cleanly. Perhaps they don’t conform accurately to the coding conventions of the project. The feature, while useful, was done quickly (since it was only a minor part of a larger project), wasn’t accompanied by unit tests, and has a couple of issues that need resolving.

Of the four or five bug reports that our hacker created, one gets marked INVALID, another one is a DUPLICATE, and one patch gets applied and the bug fixed. The feature request status gets set to NEEDINFO, since there are some open issues to be addressed, but our hacker is now 6 months away from the code, 3 projects down the line, and has less time to write unit tests, review and resubmit the code.

Maybe he’ll do it anyway – and maybe he won’t.

In fact, I would say that the vast majority of the features people code up for free software projects  never make it into an upstream bugzilla – developers are perfectly happy shipping a 10 year old version of GNU Kermit with hairy patches sticking out all over the place. And of those patches that do make it into an email or bugzilla, a small percentage ever make it into the upstream code base.

I would argue that when a project is strategic to a company product (as Lucene is to Alfresco), then the company has every interest in having someone who is regularly contributing to the project, who knows the key people in the community, and who is a trusted member of the community themselves. This ensures that your code is getting the care and attention it deserves when submitted upstream, and helps contribute to reducing your maintenance cost long run (as well as giving you influence over a project you depend on).

All this is to say that reducing the argument to “throw code over wall bad, participate good” is slightly over-simplifying – in the case where the project is a core part of your business, I agree wholeheartedly. If you’re using free software libraries as product, and merely tweaking to your needs, then the cost of participating outweighs the benefits in most cases. Reducing that cost by lowering the barrier of entry to participating is key to developing a vibrant community. But increased availability and a very low barrier to entry also incurs a cost on the community. Like most community-related issues, the balancing act is not an easy one to get right.

Live from OSCON

freesoftware, gnome, maemo, marketing, running 1 Comment

OSCON has been pretty cool this year so far. It’s been really weird, since I haven’t been in North America too often in the past, and this is my first ORA conference, to be meeting people I’ve exchanged email with for years in the corridors, and bumping into people that I’ve been hearing about for ages. There’s also a decent scattering of people I already knew, too. Far too many to name individually without leaving people out & insulting somebody…

I arrived on Friday, and to help get over jet-lag, I decided to go out for an hour-long run. After losing all sense of orientation, and going North when I thought I was going East, that ended up being a 2 hour run.  Which was nice.

Over the weekend, the FLOSS Foundations group met, and we talked about lots of stuff – accounting, membership, CRM & donor management software that non-profits can use (there isn’t any that works well enough), merging foundations, and how umbrella foundations work (targeted funding, etc), best practices for dealing with donors (big and small), merchandising, CLAs, trademark policies, and a really interesting discussion on university outreach, the creation, aggregation & distribution of open course materials and university outreach.

All in all, a very valuable 2 days.

On Monday, I attended OMX, the first edition of the Open Mobile Exchange. Myself & Paul Cooper stepped in at the last minute to give a tag-team presentation on GNOME Mobile which went, to my mind, very well. Having 2 people was great, because it meant that all of the things we wanted to say got said (usually I end up being quite non-linear and saying “oh, earlier, I forgot to mention…”, with Paul that didn’t happen). There was a decent amount of GNOME Mobile presence in any case – Jim Zemlin had nice things to say about us, and Jenny Minor from Vernier and Lefty Schlessinger from Access gave presentations from the perspective of a device manufacturer and a platform developer.

Tuesday was a quiet day for me – finally got to have quality phone time with Anne, and attended the Maemo sprint meeting on IRC before eating with Stormy – we talked about a couple of cool things I’ve been working on for the past two days that I hope to be able to announce in the next few days.

All in all, a great conference, social & work merged, mixed, mashed, and with a spot of early-morning running & Tour de Francing.Happy happy joy joy.

Tonight: RedMonk beer tastes Good.

GUADEC in hindsight

freesoftware, gnome, guadec, maemo 1 Comment

It’s been a hectic week, but I really wanted to write up some notes from this year’s GUADEC for posterity, and to share some of the great stuff that happened that people might not know about.

GNOME Mobile

After arriving late (very late) on Monday, I was up early to go & lead the GNOME Mobile BOF in the nice luxury bar on the top floor of the building.

The meeting location had been changed the day before, so we left people an extra half an hour to find the room. Unfortunately, we were a couple of days late to appear in the printed program once we’d decided when to hold the BOF, so some people who really wanted to be there found out afterwards.

The BOF went well – some really interesting discussions, and, I hope, some momentum to carry us through to a successful 2.24 GNOME Mobile release and a productive collaboration effort over the coming months.

We will be working on updating the website to list the active participants, collect and publish success stories from GNOME Mobile developers and users, and provide a more fruitful collaboration forum for participants.

Keynotes

I loved Leisa Reichelt and Matt Webb‘s keynotes. Since I was the one who invited them, I’m glad that they seemed well received by those who attended. Matt’s keynote suffered a little by being at 10am, but unfortunately he had to fly away early in the afternoon, being the FOO that he is. Interesting factoid: the book that Matt co-authored for O’Reilly, “Mind Hacks”, was not for sale at the ORA stand. I bet that we could have set up a signing session if she had some 😉

I also enjoyed Chris Blizzard’s keynote, and Alp Toker and Kristian Reitveld’s sessions were choc a bloc with interesting technical stuff.

Unfortunately, I didn’t see Federico’s talk as I was already at the airport, and thus I also missed the closing plenary, the foundation meeting, and (with great regret) the lightning talks.

Presentations

I did get to catch some great presentations though. Clutter Guts was great – really fascinating stuff, and as always, pippin gives a mean demo.

I caught Travis Reitter’s Soylent talk, and I think I missed most of the feature presentation & demos in the first 5 minutes… which was unfortunate. It seems to me like libsoylent is aiming to provide the type of API I was kind of expecting from Telepathy… I don’t know if that’s a pair representation.

I also caught Owen Taylor presenting Big Board and the GNOME Online Desktop – promising stuff, and it seems like it’s almost at that inflection point you get in a project where it goes from a small project to one that gets adapted everywhere. It seems to be, as I tweeted at the time, like Gimmie, brought through to completion.

I think the only other presentation (outside of keynotes) I caught was my own, which seemed fairly well received. I managed to give Chris 20 minutes break before his keyboard too, which was great.

GTK+ 3

I’m not going to take any part in the whole GTK+ 3 discussion, though, except to share my own experiences with third party developers. Having worked with a company that had a GTK+ 1.2 interface that we were supporting for years for a client because the client didn’t want to pay to have it ported to GTK+ 2.x, I see where Miguel is coming from. I also understand that it would be good to have some idea of the things people don’t like in the current platform before committing to an API freeze for at least 2 – 3 years again.

Perhaps that would be a good first step – going beyond the initial rant to say “OK, what features do people not like? What do we need to change/add to the current platform to address the needs application developers have?”.

Like I said, I’m going to mostly stay out of it, except to reiterate one point I made on the marketing list – I think it’s a bad idea to connect a change in major version number in GNOME to a change in the API of the platform. GNOME version numbers indicate compelling new features to users, API version numbers convey something about the API, which users (and, by extension, press) don’t care about. We need to concentrate on the user when talking about GNOME versions.

GUADEC selection

I was happy to sit in with the board on the discussion with KDE eV when the three bids for GUADEC/Akademy 2009 were considered. Based on what I’ve learned from being involved in GUADEC organisation every year since Kristiansand, I recommended that the final cost to attendees (with particular thought for companies sending many developers from the US) be the primary deciding factor, the organising committee and their community credentials second, with the location itself being third.

While I’m happy to see the Canaries chosen as the final choice, I don’t think that my suggestions were particularly given precedence in the decision making process. In any case, I hope I’ll be able to help make GUADEC 2009 a success.

Stormy

I know what she’s thinking – “I’ve had enough publicity at this stage, let’s get people talking about GNOME” – but I am really really pleased to see Stormy come on board as the new Executive Director. When I mentioned it to her back in April, I really didn’t think that she would be interested, but I saw from that first spark of interest that she has wanted to work with the GNOME project for a long time. The stars were aligned and it has come to pass.

I know, when we decided to hire for the role a couple of years back (yes, it’s been that long) Jeff had major concerns about the title – he wanted to set different expectations to those we had of Tim. I agree with that – and I think that the board have done a good job of setting those expectations with Stormy. She is our relationships person, and we direly needed one working full time.

Outside the conference

The FreeFA World Cup has its third running this year, with 3 teams battling it out in the Turkish sun (I’m still trying to work out if we were mad dogs or Englishmen) before battling with Turkish rush-hour traffic (for some reason, Istanbul rush hour seems to be around 8pm). Others have written about it already. In spite of the considerable handicap of wearing the most heat-absorbant t-shirts, the black team won through against the red & white teams, thanks to a rock solid defense. There’s no praise like self-praise they say.

SMASHED was again a great success – this is the third time I’ve brought a bottle to a conference, after buying a Glenrothes 10yo on my way to China for the Linux Foundation Developers Summit and bringing a bottle I’ve completely forgotten to Austin for the Collaboration Summit in April.

This time, I will definitely not forget – the Glengoyne 12yo cask strength I brought was a lovely bottle among other lovely bottles. We spread the whisky love around, I hope that all the whisk[e]y lovers on the boat got at least one wee dram. Karl & John Carr were feeling a little worse for wear at the end of the evening. I managed to be a little more reasonable than those two… but only slightly. And the nightcap of reki on the pillows put paid to any hope I had of making it into the conference the following morning.

I really enjoyed getting some quality time with Luis, jrb, Lefty, vuntz and Stormy, and the many discussions I had on the rooftop, in the hallways, and on the boat. The really best thing about GUADEC is the conversations happening all the time.

iTWire – Shuttleworth has some nice words for KDE???

freesoftware, gnome, maemo 12 Comments

I hate to give attention to Sam Varghese, but he is, after all, my favourite free software Shock Jock – always looking for conflict, or the controversial angle on the most innocuous statement.

This week, he wrote:

Is Mr Ubuntu, Mark Shuttleworth, slowly warming towards KDE?[…]

Given the amount of flak that the recent KDE release – 4.0 – has taken from the pro-GNOME pundits at sites like linux.com, you would think that the worst possible thing any supporter of GNOME – as Shuttleworth is perceived to be – could do is to speak out in support of anything associated with KDE.

But you would be wrong. Shuttleworth is now floating the idea that there can be a QT-based GNOME.

So we look farther, and see that Sam is referring to the article in derStandard.at which Andreas wrote in GUADEC. Mark says, and I paraphrase: “GNOME’s platform licencing is company friendly, QT’s isn’t, but if QT were to change their licencing strategy to a company-friendly licence, GNOME would have some hard choices to make”.

To be fair, let’s get the direct quote in here:

A lot is going to depend on what Nokia is going to do from a licensing point of view. And separately what GNOME is going to do if Nokia makes the QT-licenses effectively compatible with the GNOME vision, can they embrace QT as a platform? […] I think it would be perfectly possible to deliver the values of GNOME on top of QT. There are licensing issues, GNOME is very much built on the LGPL, allowing companies to build their own products on a free software system, giving them some freedom and flexibility in their choice of licensing. That’s very frankly been a huge drive for the adoption of GNOME by corporate ISVs.

So, let me read between the lines (well, in fact, I’m just reading *on* the lines): if QT became LGPL or X11 or BSD, that would instantly make it a more attractive platform for commercial developers. Mark thinks that it’s possible to bring the GNOME vision of universal access through a beautiful, simple, accessible, internationalised, integrated user experience to the QT platform.

I may be nuts, but isn’t that more an indictment of KDE than a recommendation? Isn’t he saying “the KDE guys should be more like GNOME”? Isn’t he suggesting that if QT were available as LGPL or more liberal that we all become C++ hackers and port GNOME over to QT?

As it happens, I think that’s extremely unlikely, given the investment in C that GNOME has already made – changing the underlying platform would mean re-writing every single application, and leaving a lot of dead & wounded behind. Plus, I have a lot of faith that through improved bindings and a less shackled GTK+, combined with the 2-3 year “vision” arcs that the release team proposed at GUADEC, that we can inject a healthy dose of adrenaline into the heart of GNOME over the next couple of years.

Live from RMLL

francais, freesoftware, gnome, guadec, marketing No Comments

I’m coming to the end of my two days in Mont de Marsan (and, as it happens, to the end of the charge in my laptop battery). I think the GNOME Accessibility presentation I gave went very well, certainly people seemed to get a lot from it. I’ll put my slides online at some stage (before the weekend), and I was filmed, when I have a link to the video I’ll throw that up too.

As usual, the great thing about conferences is meeting old friends, and making new ones, and there are a lot of familiar faces around.

One thing that did come out of my presentation is the need for those storyboards I proposed a while back. In particular, I tripped up when demoing Orca (no real plan to show off its functionality, other than turning on TTS, and “doing stuff”, then turning on magnification, and “doing stuff”, etc…), Dasher (it’d be handy to have a few phrases to type rather than coming up with something on the spot), and sticky & slow keys.

I hit a few problems with the keyboard a11y. When I had both sticky & slow keys activated, I got double letters (I’m sure it was a configuration issue, but anyway…). And when I used the keyboard shortcut to navigate to the top bar, I hit two bugs – if I open a menu in the top menubar, I can’t navigate away with the keyboard (Ctrl-Alt-Tab doesn’t work any more), and I can’t navigate to the notification area with the keyboard. And I got some comments on MouseTweaks (“we need a way to temporarily disable it for times when you’re reading a document or a web page, for example”) and Dasher (“not really suitable for certain classes of users” – I’ll try to get more information).

Yesterday’s presentation “Building bridges” went less well – it was a dry run for my GUADEC presentation, and I’ve taken away 3 or 4 good ideas for improvements. But like all the English presentations here, attendance was poor – I have about 10 or 12 attendees. And at 9am this morning, there was one person who turned up for my presentation in English on accessibility in GNOME – lucky enough, since when I tested my laptop with the projector, I had a bunch of problems! Many thanks to Claude Paroz, who helped me identify the problem (old driver + options which were necessary in Ubuntu 6.06 and 7.04, but have since been deprecated) and the solution (dpkg-reconfigure xserver-xorg). My laptop works with projectors! Yay!

“We all have some learning to do”

freesoftware, maemo 10 Comments

“We all have some learning to do” – that was the core message of Ari Jaaksi’s presentation, which has turned into a massive shitstorm over the past few days.

Yet again, I’m amazed at a knee-jerk populist reaction to a news story, and completely stunned at the spin which has been given to this, and swallowed hook, line & sinker by a large group of supposedly intelligent people. It’s been going on for years, so perhaps one more time shouldn’t surprise me, but it does.

For the benefit of those living in a burrow, here’s the quote that started it all:

“We want to educate open-source developers,” said Jaaksi, who is Nokia’s vice president of software and heads up the Finnish handset manufacturer’s open-source operations. “There are certain business rules [developers] need to obey, such as DRM, IPR [intellectual property rights], SIM locks and subsidised business models.”

That’s the bit, since quoted without context, from an article which included the quote with little context in the first place. Look a little further, and you will see that this is the same message that Dr. Jaaksi delivered in San Francisco a few months ago: Nokia is learning how to interact with free software projects, but if free software developers want the software to be adopted further in mass-market products, then we need to understand the constraints that businesses work under, and address them.

In my mind, that’s a big “if”. Companies work under a bunch of constraints which don’t sit well with free software – DRM, the need for differentiation and a competitive edge. But also dealing with sub-contractors and suppliers who have their terms and conditions under which they’re prepared to work.

Some of the most outrageous things I’ve read these past few days:

“No more Nokia for me, I’m buying an iPhone”

Yeah, because Apple are a really free software friendly company.

 “If Nokia can’t get the specs for chips from their suppliers, they should just build their own”

Uhmmm… do you really think that Nokia wants to go into competition with every micro-electronics company in the world? How much resources do people think Nokia really has?

Some people think that Nokia should use only free software in all their devices, regardless of the consequences of that (the consequences would be more difficult government validation of your phone with the GSM networks, no operator take-up of the phones, and thus no cheap phones subsidised when you take a subscription, and underpowered and outdated hardware). That may be fine for a user to have as an option if they don’t mind paying hundreds of dollars fora phone that doesn’t do as much as one that they can get for a tenth of the price or less – in fact, the Freerunner is aimed right at that market. It’s a niche market, not a mass market. One day, maybe…

In the meantime, the conclusion I draw from this is that the slashdot crowd aren’t as reasoned as I had hoped, many people who should know better are jumping to conclusions based on news headlines. What ever happened to critical thought?

Free software is great, a momentous gift to the world, but does not provide the answer to all questions. Sometimes, free software will not be the answer. Some sets of constraints will exclude us from the start. The battle is to change the constraints. But you cannot expect a business to lose money to satisfy philosophical arguments. If you’re ever talking to someone and trying to “sell” them free software, your starting point should be: “how will this (make|save) me money?”

Usually that answer will be easy to find – lower R&D costs, licencing fees, support costs you control better by deciding when to buy support, on what terms. But occasionally, there is no argument. There is no way to persuade Microsoft that releasing Office under the GPL would be a money-making move for them – it plainly wouldn’t be.

So if the answer to that question is “it won’t”, then wish them well, perhaps recommend something that will, and move on to another subject.

« Previous Entries Next Entries »