Happy New Year!

Picture by Eliane Domingos of the Document Foundation

 

 

 

 

 

 

 

 

 

 

This year we didn’t go party and celebrate the new year with friends. For some reason we felt lazy and decided we’d spend the new year’s even with our family, (parents, cousins) at my parents’ place. In the end both Melissa and I knocked on the door sick with sore throat and some mild flu. Needless to say, we didn’t drink much, we mostly ate and were dosing by 1am. It wasn’t a very exciting new year’s eve but it felt good to be among our loved ones; it was a really good new year’s eve and I’m glad we were able to spend the first hours of 2012 and most of the first day with our family. May love, health, success and joy fill your life for 2012. It’s likely to get tough, business wise, but I think we’re going to have some real fun.

Seasonal Greetings

It is this time of the year again; so… Merry Christmas, happy Hanukkah, Merry Winter Solstice celebrations wherever you are, and a happy healthy new (calendar) year 2012. It’s going to be quite a year on many fronts, but I think we’ll get out of this one stronger, and we’ll probably have real fun too. Thank you, dear readers, for following my blog regularly despite me not being so good at publishing regular posts.

 

Picture by Eliane Domingos of the Document Foundation

If you wish to read our official wishes, we have them here, and they come from all of us. My thanks go to everyone who is making the LibreOffice project possible and what it is today. We have grown quite a lot in 15 months, probably more than we would have thought. 2012 is going to be the opportunity for the Document Foundation to solidify its successes and turn them into a powerful entity and structure. It will also be the year where several strategic project, such as LibreOffice OnLine, will see their development hopefully take off. Adoption-wise things are already well on their way. Deployments are ongoing on a worldwide basis, large and small, and what we  need at this stage is to push our brand name in a more consistent way. It will also be the year where our friends at the Apache Foundation release their first Apache OpenOffice; what will be interesting will be not their first release(s) but the one that will see most of the Lotus stack be injected into it. This will actually be a good opportunity to clearly differentiate Apache OpenOffice, and that in turns will improve the Apache OpenOffice project’s health and its relation with the outside world (LibreOffice being one example).

But 2012 will be the year where you will be able to experiment the benefits of the LibreOffice development’s effort as we will bring the 3.5 and the 3.6 lines to life. I think it will illustrate that a community-based development model does effectively work and brings real and regular improvements and changes to an aging codebase.

On a more personal note, 2012 will be an important year: I’m getting married in June (expect full delays in blog posting) and this is something I was not expecting even a few years ago. But there are a few people in this world (in this case, only one) who can change everything for the best, and for this I’m truly blessed and very, very happy.

Last but not least, I would like to express my gratitude to my family and my friends at the Document Foundation and at Ars Aperta for making all this a reality. You truly rock. What else is there to wish? Health, happiness, and love.

Merry Christmas and a happy new year 2012.

On Citrus UI, and a zest of realism

A few days ago I was surprised to learn that LibreOffice was to get a brand new interface called Citrus. The series of mock-ups called Citrus are not a surprise, they are the result of the enthusiastic work of Mirek M. with the feedback of our Design team. However, the fact that a OMGUbuntu could write an article claiming that Citrus was going to become LibreOffice’s user interface got me thinking.

LibreOffice has an aging interface. It’s not just that it has many defaults, because, as much of the software packed with features tends to have this problem; it’s that LibreOffice looks a bit like it’s living in 2003. That reason alone is enough to want to change the whole UI. However the LibreOffice codebase is, despite constant clean-ups somewhat too complex to have its UI change overnight. Therefore we will be able to do so in an incremental fashion. What is needed is specifications developers can work with that target one specific user interface feature. With that, developers are able to “swallow” the specification and possibly implement it in a specific time frame. Will Citrus be the next LibreOffice UI? I don’t know. But if the design team is good at writing specifications (something some of its active members are in the process of learning) we might get to something that will have much in common with Citrus. The fineprint on this, however is that we need motivated volunteers able to work on UI improvements in an effective fashion, and developers’ resource to implement them.  If you are interested and would like to help, please join!

We are the 99%

The financial crisis people started to notice around 2008 is not just financial. It goes deeper than what we usually want to admit. It is about a fundamental shift in our civilization’s balance of power, our survival plans, our values and our way of life. I regret to say that anything like 9/11 pales in comparison of what we have been experiencing since 3 years or so. Just like the metaphor used by Geog Zoche in his excellent book “the clash of currencies”, we tend to think the initial shock is pretty much all what has made the crisis while we are witnessing the long agony and fall of the twin towers of our civilization and our economy. Let’s leave the not so interesting gesticulations that took place this past week in Brussels and the Chinese buyout of Europe (never forget, the European Commission has always acted has the de facto Chinese Chamber of Commerce) aside and fast forward on the Occupy Wall Street Movement that has spread thoughout the US and originated in a distributed fashion from the Middle East and Europe. This movement is the symptom of something powerful, of the need for profound and radical change. It is also the place to mix several ideas, concepts, technologies and models that liberate people. I recently read articles on whether this movement was open source or not (and the articles tended to agree with the “open source nature” of the movement), but even more interestingly such movements do claim and advocate Open Source models and approach for many, even non software related matters.

Fast forward to the LibreOffice Conference in Paris. On the evening of the 14th we thought we would set up some beer and music party in a hacklab and we contacted the LOOP in Paris. While they had to migrate from one location to another we ended up in an alternative cultural space shared by hackers but also completely different people as well. What was really interesting to watch was the general blending of these populations. In the end, it should remind us that even the coming of the Document Foundation was and is at the same time the answer to the decay of a free software project struggling under the iron fist of an irresponsible and greedy corporation (Oracle)  and the perfect example of a community deciding what’s good for itself, having reached a point where “enough is enough”.

The LibreOffice Project is thus more than a free software project developing an office suite. It has started a bit before the events in Tunisia, but roughly at the same time the Iranian revolts were taking place (and they’re still going on by the way). It is about freedom and the individual power to refuse the will and the agenda of a large corporation. It is about realizing that something had been failing in our community and that it was time to fix it.

The Document Foundation was started because of that; and just like the people on the streets of the world, it was prepared  somewhat in a stealth mode at first, otherwise it  would have failed. Now things have become quite different, and we just celebrated our first year as a project and as a free community where everyone can fit in and contribute meaningfully to the greater good. The numbers speak for themselves, and the OpenOffice.org community has chosen to go for LibreOffice, not just as a product but as model, as a set of values and as a refusal to compromise one’s freedom to corporate agendas. Our manifesto highlights the goals and the values of the LibreOffice community and why the Document Foundation has been created and set up.

Yet we are not one fork among others. We are the next chapter of the next decade. We are LibreOffice, we are the Document Foundation. We are the people of OpenOffice.org . We are no puppets and no useful idiots. We bow to no one. We are here to fulfill the destiny of this great project: to create instruments of freedom and tools for knowledge.  We are “OOO”, we “Occupy OpenOffice” we stand for freedom, community, excellence and collaboration.

We are the 99%. Expect us.

October wrap-up

This was quite a busy month. I was happy and exhausted by the LibreOffice Conference which went despite my immediate perception quite well. When you’re part of the organizers you tend to see all the small and not so small things that go wrong, and regardless of what the other participants notice or experience, you end up feeling that it’s just not as good as the others see it. Be it as it may, I would like to thank all the participants to the first LibreOffice Conference. It’s been very moving and heartwarming to see all of you, after a year of adventure and perils we have gone through. I would also like to thank all the organizers of the LibreOffice Conference, the community volunteers of France who made it possible, Sophie, Marie-Jo, Christophe, Jean-Baptiste, our hosts, La Cantine and the IRILL, and our sponsors. Among them, a special mention should be made to the Paris Region (Région Île de France) with whom we announced several exciting news. It’s all in the press now but I think that these announcements highlight how far we have come in one year. More importantly, it also shows how a Free Software community can work as it should, that is, with diverse contributors and a variety of stakeholders in a sustainable fashion. Of course, all this is far from being built and all the dots are not being connected. This year will therefore be exciting as we will continue to build and grow our community further.

I would like to come back shortly on two of the announcements we made, regarding the porting of the LibreOffice platform (not the interface) to iOS and Android, as well as LibreOffice OnLine. While these two projects are at various stages of completion and have different requirements they help to show not just the vitality of our community, they also shed some light on how we manage to embrace a bazaar-like approach to development and think about what I call our “development ecology” (which some could really translate into development strategy, but I think it’s more subtler than that). What you see through our online office suite project and platform porting announcements is that we are taking some great care in doing something paradoxal with respect to our stated intent to change the codebase as much as possible: we keep our codebase intact. Note that we do change, upgrade, clear and trim the codebase, but we do adopt a singular codebase approach where the code used in LibreOffice OnLine, and the underlying code on iOS and Android will essentially be the same than the one inside the LibreOffice Desktop suite. In other words, we do not release a product here and something completely different there, even if in the future, a specific work on the interface for tablets will have to be made (we won’t use the existing interface on these as it would not make sense).

This “universal” approach makes sense not just for “market growth” and adoption, it has two benefits. The first one is to pool the resources as much as we can, because maintaining millions of lines of code here while maintaining a million of new and different lines of code there would not require around 3 hundred developers; it would actually require 3 thousands of them. We thus keep the codebase as a coherent whole (hence Rob Weir’s confusion answered by something like “just pull the git”) while we will enjoy in the future the second benefit of being able to make changes (and even important ones) in one codebase, thus replicating the changes for the online version at the same time as they will be made available in the desktop or the tablet version.

Exciting times are ahead. Stay tuned!