• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

An Antic Disposition

  • Home
  • About
  • Archives
  • Writings
  • Links
You are here: Home / Archives for OpenOffice

OpenOffice

OpenOffice, LibreOffice and the Scarcity Fallacy

2011/06/13 By Rob

As you’ve probably heard, the proposal to move OpenOffice.org to the Apache Software Foundation was approved by a wide margin.  Volunteers interested in helping with this project continued to sign up, even during the 72-hour ballot, giving the project 87 members, as well as 8 experienced Apache  mentors, at the end of the vote.  The volunteers signed up included an impressive number of programmers from OpenOffice.org, RedOffice and Symphony,  as well as QA engineers, translators, education project experts, OOo user forum moderators and admins,  marketing project members, documentation leads, etc.    The broad range of support for this new project, from volunteers as well as voters, was very encouraging.

Of course, this is not the end of our recruitment effort.  In some sense it marks only the beginning.    What I wrote about in my previous notes, about the Apache meritocracy remains true.  However, now that the proposal has advanced and an Apache “Podling” (a probationary project) has been created, the way to sign up has changed.    You should now sign up to the project’s mailing lists directly.  For example, an email to ooo-dev-subscribe@incubator.apache.org will get you onto the project’s main dev mailing list.  Anyone interested in participating needs to get onto this list,  including those who already earlier expressed interest as “proposed committers” as well as new volunteers.

I would be negligent if, in mentioning the successful approval of the Apache OpenOffice proposal, I did not acknowledge that there were other, dissenting, opinions expressed.   That is fine and indeed welcome.  It is good that we don’t all think the same.  However, in order to have a plurality of views, and to give users a plurality of applications to choose from, we also need plurality of projects in the open source world.  So it was disappointing to witness a small but vocal minority of non-Apache members who disagreed with the proposal and who attempted to derail it.  The day closed minded open source advocates decide to smother a new project in its crib, because they personally favor a different project, is the day that FOSS dies.

I believe that one unstated assumption in their reasoning was that there is a scarcity of developers and a scarcity of users in the personal productivity application area, and that the success of a new project can only come at the expense of another project, in this case at the expense of LibreOffice.  The assumption was that we’re playing a zero-sum game, and like junk yard dogs we’re fighting to the death over scraps.  In this view (which I believe to be false), as illustrated below,  LibreOffice supporters see Apache OpenOffice as a mortal threat to their project,  since its gain comes only at their expense.

Of course, this is inaccurate in many ways.  For example, the market share of LibreOffice, although strong on Linux, is actually quite low in the much larger Windows platform, where OpenOffice is still the leading open source office suite.  So overall, OpenOffice has greater market share than LibreOffice has today.

And in the real world, outside of FOSS blogs, the world runs predominately Microsoft Office, a proprietary set of applications.  The other proprietary applications, like Corel WordPerfect and Google Docs  and Apple iWork,  combined with Microsoft Office represent well over 90% of the market.  Open source, of all varieties, including LibreOffice, is rather small.

So rather than fighting over the remaining 5%, I think we should set our sights on a more transformative engagement with the market.  This need not be a zero-sum, I-Win/You-Lose situation.  OpenOffice and LibreOffice can both win.  OpenOffice and LibreOffice and Calligra Suite and AbiWord and Gnumeric can all gain users at the same time.  And this can happen at the same time that mixed-source applications based upon OpenOffice also grow and gain users.

There is no scarcity but scarcity in vision.

Apache OpenOffice, with its permissive license, is an excellent basis now for open source as well as mixed source business models, business models that drive investment back into the ecosystem.  The mixed source segment will grow the most,  I believe.  But so will the pure open source version, because of the increased investment.   We’ve had LGPL with OpenOffice for 10 years now.  We’ve seen the modest success with which business models based on LGPL advanced in this segment of the market.  Do we think another 10 years of the same will do much better?  Personally, I think it is time, after a decade, to try enabling additional options,  things that have not been tried yet.

So rather than the scarcity fallacy, the impact of Apache OpenOffice will be more like the following diagram:

So let’s stop this nonsense, this fallacy of scarcity. Let’s stop fighting over that little 5% box.  Instead, let’s look toward how we restore the choice and diversity that we had in this market segment back in 1990, but do it better.  We have something now we didn’t have back then, and that is an International Standard for document exchange, ODF.   This can and should be the basis for interoperability among competing application suites.

  • Tweet

Filed Under: Apache, Open Source, OpenOffice

Apache OpenOffice: How to Get Involved

2011/06/03 By Rob 16 Comments

A follow-up to my previous post on the  Apache Incubation proposal to move OpenOffice.org over to Apache and continue the project there.  In that post, I described how Apache projects are run via a meritocracy, that members gain additional rights and responsibilities based on the approval of their peers, etc.  But I have received a variety of questions related to this, and I’ve done my best to track down some answers.   So here are what I found out, in my words, paraphrasing the questions and giving answers, possibly with my mistakes, but I’ll correct them as they are identified.

Question:  How do I sign up to be a project member?

Answer:  For now, since we’re in the proposal stage, and the project has not officially started, we don’t have a website, mailing lists,  a repository, etc.  So there is no direct project work to do yet.  However, anyone who wants to “get in on the ground floor” with Apache OpenOffice, can sign up by adding their name to the “Initial Committers” table at the proposal wiki.  If you don’t have a login for the wiki (and you probably don’t) then you can quickly get one by clicking “log in” and then following the instructions to create a new account.  If you have interest in this, I’d encourage you to sign up.  Even though we can’t code yet, we can edit the proposal itself, and there are thin spots there that we could certainly use help filling in.  If you want to contribute you should also sign up on the incubator general list.  This is where the proposal is being discussed.

Question: This meritocracy sounds very programmer-oriented. But OpenOffice.org,  as an end-user, mass-market application, involves a broader community of contributors, from test to translation to documentation to marketing, etc.  Do they fit into this meritocracy at all?  Is a marketing person or an event organizer or a build engineer a valued contributor?

Answer:  Yes.  Absolutely.  Each Apache project determines the criteria used to identify those members whose sustained contributions to the project warranted recognition and advancement.   I think that in the case of an end-user facing application like OpenOffice.org, contributions come in many flavors.  It is not limited to coders, or even to those who check in “assets” like translations and test scripts.  We’ll need a wide range of contributors with a diverse set of skills to take OpenOffice.org to the next level.

Question:  Do I need to sign a copyright assignment to contribute to Apache?  I heard a lot of bad things about the paperwork that Sun required from OpenOffice contributors.

Answer:  In Sun’s case it was the JCA by which the copyright of all code contributions was assigned to Sun.  Instead Apache has a “Contributor License Agreement” which they have in both individual and corporate forms.  This agreement does not require copyright assignment to a single entity, not even to Apache.  It does not aggregate copyright.  But it does require that you agree to license the copyright to Apache as well as to anyone using the software.  IANAL, but this sounds like a good thing.  If you are comfortable with the Apache 2.0 license, I can’t see why you would have a problem with the Apache iCLA, since it pretty much restates those same terms.

Question:  What kinds of contributors are you looking for?  What roles and skills?

Answer: If you look at the range of skills and contributors that went into making OpenOffice.org, you will have a good idea of what is involved:

  • C++ and Java programmers — same thing really, any programmer over 40 ;-)
  • Testers, both manual as well as those able to help with test automation
  • Translators — I’d especially like to see some OOo National Language Projects sign up.
  • Documentation / technical writers
  • Accessibility
  • Web admin /server admin — We’re going to take over the OpenOffice.org website, but we’ll need to migrate to our own server
  • Build engineer / build management
  • Community development
  • Event organizing
  • Marketing / brand development
  • Education / training / certification
  • Package and liaise with Linux distros

What we don’t need, at least not at the project level, are things that are more in the nature of foundation-defined roles, like fundraisers, board of director members, membership committees, press release authors, etc.  In this sense Apache OpenOffice is different from the OOo under Sun/oracle or from LibreOffice.  We’re imbedded in a very capable and well-respected open source foundation.  Apache has governance already established.  Certainly individuals can get involved in that if they wish, and more importantly if they have the support and votes of their peers to advance to that point, but this is not something we need to reinvent for the project.  We can concentrate on the project work itself.  100% of the effort will be on improving OpenOffice.

In particular, I’d welcome existing contributors from the OpenOffice.org community, including those from Oracle Hamburg (check with  HR first, of course), from the Symphony team and from other parts of IBM (send me a note if you have questions), from companies with desktop Linux distributions (you need a strong story for productivity applications to be viable in the enterprise), from those other companies with downstream business based on OpenOffice (consultants, trainers, authors, migration experts), and of course members of the large and vibrant LibreOffice community.

And remember, contributing to an Apache project is not an exclusive thing.  You as the author of code, documentation, translations, etc., own the copyright to your original work. You may choose to license your work under  Apache 2.0 and contribute it to Apache OpenOffice and then attach a different set of licenses and contribute it to LibreOffice.    This is a good way to get your work out to the maximum number of users.  And who knows?  You might find out that you like Apache and decide to move your tent over there.  That’s your choice.  If you do that, you can contribute just to  Apache and then have LO suck down the changes from the Apache project.  This is because Apache 2.0 and GPLv3 are compatible in that direction.  So you still can impact both projects by contributing code to one place, namely Apache.  But it does not work in the other direction.

  • Tweet

Filed Under: OpenOffice

An Invitation to Apache OpenOffice

2011/06/01 By Rob 110 Comments

As you have probably heard, Oracle has followed through with their earlier promise to “move OpenOffice.org to a purely community-based open source project.”  OpenOffice is moving to Apache.

I’d like to offer you my own thoughts on this new opportunity and what it means.  I recommend also the insights of my colleagues Ed Brill and Bob Sutor.

First, we should all be excited to see OpenOffice move to a foundation with the stature and track-record of Apache.  If you are a web developer or server admin, then you of course know about the eponymous Apache http server and Tomcat.  If you are a developer you know about Ant, Maven and Subversion.   If you work with XML you know about Apache Xerces, Xalan, FOP and Batik.   And if you don’t know about Apache Hadoop yet, then please do your résumé a favor and study up on it.   All said Apache is custodian of nearly 170 open source projects, including 5 of the top 10 open source downloads.  I’m hoping that soon, as OpenOffice transitions to Apache, they will be able to claim 6 of the top 10!

These diverse projects are run according to meritocratic development process, a tried and tested governance model, strong shared technical infrastructure, a pragmatic, commercially-friendly open source license and a set of social conventions known as the “Apache Way”.

I’d point out in particular that the Apache 2.0 open source license was recently blessed by the Free Software Foundation:

The Apache License 2.0 is the best non-copyleft license that does what a copyright license can to mitigate threats from software patents. It’s a well-established, mature license that users, developers, and distributors alike are all comfortable with. You can tell it’s important by the way that other free software licenses work to cooperate with it: the drafting processes for GPLv3 and the Mozilla Public License 2.0 named compatibility with the Apache License 2.0 as a goal from day one. The Apache Software Foundation deserves a lot of credit for pushing to do more to tackle software patents in a license, and implementing an effective strategy in the Apache License.

As you can tell, when it comes to Apache I’m a fan.   I’ve experienced much of this first-hand.  I was a committer in the Apache Xalan project many years ago (1999-2000).  It was a great experience then, and  when the opportunity came to add my name to the OpenOffice incubation proposal I did not hesitate.  It was an honor.   I look forward to coming back to Apache and participating in this continuation of OpenOffice.  I am planning on getting directly involved with the engineering effort of this project.

So what are the next steps?  As I understand it (and I’m not an Apache process expert), it is not accurate to say that “Apache OpenOffice” really exists yet.  We’re not quite there.  At Apache, you can’t just walk in off the street, drop some code and call yourself an Apache project.  There is a multi-step  process for initiating, reviewing and approving a new project.  We’re at the first step, with the proposal submission, which Oracle made earlier today.  This proposal will now be reviewed and voted on by the Apache Incubator Project Management Committee (PMC) over the next few days.  If approved, the project then advances into incubation as a “Podling”.  Incubation at Apache is a probationary stage, where the project recruits new members, reviews the code to establish IP provenance,  adapts the project to the Apache infrastructure,  and so on.   We’ll undergo periodic reviews, and at some point, when we are ready, we can then be approved to “graduate” to be a new top-level Apache project, ideally something like  http://openoffice.apache.org.  There is no fixed time for how long this incubation state takes, but I’m told it generally takes several months.  I don’t think we should rush it.  Everything that occurs during incubation is for the long-term benefit of the project, so I think we want to soak up the help and special attention from our Apache mentors as much as we can.   For more details on the process, I recommend the process diagram here and the associated process description.

The Apache process is based on a strong meritocracy. Developers who regularly provide high quality patches get elected as “Committers” and they then help review submitted patches as well as write their own code.  And those Committers who remain active and have earned the respect of their peers typically then get elected to the Project Management Committee (PMC) and steer the direction of the project.  And those who are most valued on the PMC may become the PMC Chair for their project, which also ranks them as an Apache Foundation Vice President.  And some then have the opportunity to serve on the Apache Board of Directors.   With this cursus honorum, it is recommended that those with leadership ambitions get involved early.  When the Apache OpenOffice project begins, there will be project decisions to make and leadership roles to fill, and this will happen fast once we get started.   Obviously, you can’t advance in the meritocracy if you are absent.  Although, you can join anytime you want, there are clear advantages to “getting in on the ground floor”.

In particular, we need to attract a wide variety of project specialists.  This includes C++ programmers (on Linux, Mac and Windows), QA (also on all platforms), help/documentation, UI/UCD, translation/globalization, accessibility, install, etc.  Please keep your eyes open for an announcement from Apache in the next week or two, saying that the OpenOffice incubator project has been set up and is ready to accept members.

(I know that OpenOffice.org prided itself on a strong marketing committee as well.  I think this is important, but it is not clear to me yet how that fits into an Apache project.  Certainly this aspect is more critical to an end-user facing project like OpenOffice than it would be to a developer tool.  Maybe someone out there in Apache-land will be able to offer some suggestions on how best to integrate this function into an Apache project?)

An extraordinarily cool thing to look forward to, once Apache OpenOffice graduates to be a top-level project (TLP), is that we will be able to sponsor other incubation proposals that would be a good fit for OpenOffice.  So other components, plugins, toolkits, modules, even entire complementary productivity applications, could be brought into the project, via the incubation process, to help enhance the OpenOffice application suite.  Imagine having a mind maps editor?  Or a project planning tool?  Or a standalone outliner?  Or smaller, lighter, component-based editors?  All these things — and more — are possible.

I have a vision of a free, high quality productivity suite, one based on open standards and open source, one that doesn’t treat the web and mobile and tablet form factors as a design afterthought,  one that has a strong extensibility and programmability model that makes it the preferred platform for innovation, one that has a dedicated community of supporters.  I’ll need your help to get there.

  • Tweet

Filed Under: OpenOffice

At the Setting of the Sun

2010/01/21 By Rob 4 Comments

Sunset at First Encounter Beach, Eastham, Massachusetts (photo by Rob Weir)

As my readers have no doubt heard by now, today the EC cleared Oracle’s proposed acquisition of Sun Microsystems.  This will undoubtedly have a significant impact on all Sun employees,  many of whom I have worked with toward common purposes, on standards or open source projects, and whom I am proud to call my colleagues.  I wish them all best of luck.

I know a little of what they will be going through in the weeks and months ahead, having worked for Lotus Development Corporation when IBM acquired it in 1995.  So here is my unsolicited advice.  Some day they will come.  It may be in weeks, maybe months from now, maybe early in the morning, maybe after hours or on the weekend.  But that day will come.  They will come and strip the Sun logo from the wall in the lobby and replace it with the Oracle logo. Watch for that day, that narrow window of opportunity.  Save the logo.  It is your trophy, your icon, your totem.  You will always be Sun.  Don’t let them take it away.

  • Tweet

Filed Under: OpenOffice Tagged With: Oracle, Sun

  • « Go to Previous Page
  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Go to page 4

Primary Sidebar

Copyright © 2006-2023 Rob Weir · Site Policies

 

Loading Comments...