Category Archives: Ars Aperta

Seasonal Greetings

Posted on by
Reply

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.

A few thoughts on innovation

Posted on by
2

I was invited the other day to a conference about innovation in the information technology sector. There was nothing remarkable about that event, except perhaps that it led me to voice an opinion I held for years: I do not understand what people are really talking about when they talk about innovation, at least in software, that is.

It might be odd to write this, but if there’s any concept that’s both fuzzy and dangerously misleading in the software industry, that would be innovation. I have read for many years and listened to people explaining how to “stirr and create innovation” in a company or in a community. Maybe these words have been used for lack of a better term; but I still don’t see how you can create innovation. I think you might be able to stirr it somehow, as it’s already a humbler verb. But frankly, can someone out there tell me what does innovation mean in the software world?

In general terms, I would define innovation as the big and small changes constantly leading to a change of the art in any given field. I think that’s pretty much what one usually understands by that word. So why could this not be applied to software? Precisely because software is rarely -if at all- the result of big changes happening all of a sudden and by accident. Software development usually happens at an incremental pace, whether openly so (think about the agile development practices) or even when there’s a structured corporate environment favoring traditional code reviews and quality assurance processes through stable product development cycles. Software is not produced by accident. Software is the result of process, and in theory accidents do not happen there. In fact, I could also point out that incremental changes or a period of technological incubation might be observed right before the emergence of almost any given technology. Take the medieval rudder for instance: it’s been rumored to have been imported in Europe around the 12th century by Chinese ships, but there are tracks and evidence of previous try-outs by European sailors and shipyards to design wooden rudders and articulate them with a complete mechanism. Similarly, it is hard to say how “innovation” happened in the sixties when the U.S. decided to send manned flights to the moon, but the wave of small and not so small innovation that was the result of this huge project is still visible to everyone (think of the Tefal pans, among many other things).

Thus there are, I think, two points that need to be highlighted: First, innovation does not happen all of a sudden if the field of software field and more generally ICT. It is a set of processes that ultimately lead to new software, or software that’s supposedly not as bad as the former state of the art. Second, what’s unclear is how -to quote several people I listened to- innovation “happens”. It sounds sometimes that innovation is a mystery or the philosophers’ stone that require care and secrecy to happen. Yet in the software industry, it does not work that way, for all the marketing and bells and whistles that come out of software vendors do not brush aside the fact that even inside these corporations software development is a set of very well defined, but non-public, processes.

Innovation is not a mystery and I don’t think that you can track how it works. You can assume that a certain set of circumstances and an environment letting people code start-ups emerge and Free & Open Source Software projects grow will ultimately translate into something that someone, whether a journalist, consultant, politicians or venture capitalists will call innovation. Anything else besides that, innovation sounds more like vapor and magical boxes. This should probably express what I feel about software patents, by the way.

One last thing: Innovation is different than progress. Progress is usually applied to fields that do not necessarily belong to science or technology; it can be more a perception and may concern society as a whole. Yet the interesting thing is that while progress seems to be an even more elusive term than innovation, you can actually tell progress from regression or stagnation: people perceive it almost immediately, however relative it sometimes may be.

Enjoy the beginning of the Holiday season!

October wrap-up

Posted on by
1

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!

Short update on the LibreOffice Conference in Paris

Posted on by
1

I thought it would be useful to update everyone on the Paris LibreOffice Conference, as we received several inquiries especially from speakers of the conference. We have ended the selection process of the conference proposals and are right now dispatching each of the selected papers to a fixed room, day and time and have sent the confirmation or rejection email(s) to everyone of the submitter (if you have submitted a proposal and are reading this and you haven’t received anything do contact me).

Thanks to a great team work and a small contest we now have a very nice conference template that you may download here that will be used by the conference speakers as their presentation template during the event. The next big step is to publish the detailed schedule of the conference. Right now all you may see is an outdated and rather imprecise looking schedule. This will change in the coming days.

The conference will take place in two locations. One is called La Cantine and is a famous meeting place for hackers and researchers communities in France. The place itself is located in one of these nineteenth century “passages couverts” of the french capital that were built from early napoleonic times till the middle of the century. Do not expect something monumental, neither outside in the Passage or inside La Cantine. The whole point of the place is to meet and collaborate, and that’s why such a location matters. La Cantine is located very much in the centre of Paris, behind the old stock exchange and two metro stations away from the Opera Garnier. The other location is the IRILL an acronym standing for International Research Institute for Free Software. This place is located near the Place d’Italie in the southeastern quadrant of the city. This is part of a much larger university in Paris, and the building is shared with a large post office (you might have the feeling you’re entering a post office the first time you’re getting there).The inside has a modern design and will sport two large conference rooms with all the equipment (even streaming video) that you come to expect. One of the two rooms is on the top floor of the building and has a roof garden accessible from the room itself. The other one has sofas for informal meetings in a corner with espresso machine not far away.

But the conference won’t be “only” about conference and talks. We have several events for the evenings and nights. On the 12th at 6 pm there will be the cocktail party by Cap Digital and on the 13th a rather big event at the Paris Region headquarters where pretty much everyone from the IT community in Paris is invited and is simply called the LibreOffice Party at la Region. This is not just an opportunity to drink and eat “for free”, it’s an opportunity to learn about quite a few announcements we’ve been keeping under wraps.  We hope to see all of you (and more!) there. The evening parties don’t stop there: there will be the Friday Night’s special by AF83 with beer and music.

Stay tuned and don’t forget to register if that’s not already done. See you soon in Paris!

Links for the end of April

Posted on by
Reply

I am having a very busy month of April, but I mean, a really busy one. I am alive and kicking, but I am swamped.

Here’s a couple of links before an even more active month of May:

  • Ars Aperta has contributed to a pretty interesting project, dubbed ODFgr and hosted by the OpenDoc Society. The goal of this website is to provide any developer with even a limited knowledge of ODF with resources and tools to manipulated ODF documents. We tried to design a pedagogical platform that the largest number will understand. Most of the examples are listed by languages (we mostly have Python and Perl) and you can study both the explanation and learn how to reproduce and implement it. We hope it will be the right spot for anyone willing to get started on OpenDocument hacking and development.
  • Events-wise the month of May will be busy. I will attend the OASIS Board of Directors’ meetingin Berlin and meet with the Bitkom. The week after that Ars Aperta will join a session on the political and legal issues pertaining to Free Software development during the Linux Solutions 2011 event in Paris. I will also give another talk during the same event as part of the Document Foundation and our experience with forks. Spoons shall come next year.