What Google+ is missing

When Google + was announced I was very much excited at the prospect of using a more open social network that would also bring something different and refreshing to everyone. I do not really like Facebook. It’s not just their privacy policies, or the never stressed enough notion that if you’re not the customer then you must be the product -that also applies to Google +- it’s the website itself. I grew increasingly frustrated of Facebook, I got tired of what I consider to be a lack of elegance (the violet to indigo-blue palette is getting old) and a constant will to confuse users in pushing them to reveal more and more personal data.

For sure I do use Facebook, I am “on Facebook” just like many other people. But I also use Google Plus and Diaspora. While Diaspora aims at being something really different and relies on a fundamentally distributed model, it is in its infancy and I will not discuss it in this post. I will focus on Google + instead.

I had big hopes for Google + and still do. I still believe it is a better built, more powerful and less harmful service than Facebook, but I also believe that while any service has shortcomings of its own its operator/owner tends to correct them over time by bringing in more features for instance, something Google does not seem to be doing, hence my points below:

  • Tastes and colours should not be discussed as everyone has his or her own tastes and yet… I still like Google + much more than Facebook for that matter, however, something seems not all right in Google +: could users customize the look of their page(s), or are they condemned to the everlasting white background? (on the other hand you could point out that simplicity in design never hurt anyone).
  • Profiles: it’s amazing how hard it is to see someone’s profile. For this Facebook tends to be much simpler and clearer, Why can’t I just access someone’s profile in one click, instead of searching its own activity feed?
  • Sharing and circles is probably what Google + does best, although in many ways it was a Diaspora’s concept that was itself hinted in the discussions around the DISO concept (the early days of a distributed social network) but there is something, specifically about sharing, that I do not understand: sharing beyond circles, such as sharing on Twitter or StatusNet, let alone on Facebook is not possible. I know about the hack for identi.ca and twitter that works by sharing with one specific profile but why would I want to share that with this probably sympathetic, yet unknown person? The most surprising part of this is that neither Google, nor Twitter, nor Facebook, seem to be willing to provide that feature (the same goes for sharing from Twitter, StatusNet and Facebook to Google +). This issue alone, to me, is a major one, and I am pretty sure it’s the same for many people. Because of that posting on Google + is somewhat of a solitary exercise; you have to repost specifically on Google +.
  • More distributed content : obviously Google does perform data mining on the content we share on Google + and any of its other services, that’s not news to anyone. But while Google does handle data portability seriously (a big plus!) it might benefit from enabling some sort of “sandboxes”, that is, private spaces that could be self-hosted, yet easily connectable to the “central” Google + network. This would also allow many people to both feel more secure and enrich the overall content aggregation scheme; you would be able to use Google + as a content transport layer in between “pods” or peers and still using the big social network itself if you want to.
  • A Google Wave like timeline : as people become increasingly aware that their past posts and interactions can be monitored, reused by others or simply by and for themselves, an easy to use timeline, something completely missing on Facebook, might be useful and fun to use.
  • A professional page or job search as well as other specific services might also be useful; but it seems that Google + is very much like other services launched at Google: an experiment first, a product afterwards. I am usually fine with this approach, but Google + needs attention and extra features if it wants to stay and grow instead of being dumped and filed such as Google Buzz was. I really hope that won’t be the case.

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.

A few thoughts on innovation

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

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!

Links under the snow

  • Julian Assange goes out of jail, fears for his life, while Bank of America blocks payments to Wikileaks. I didn’t know that Bank of America had so high moral standards. This is why I do expect that, after blocking the payments process to Wikileaks, Bank of America will also block payment processes flowing to Saudi Arabia and Pakistan whose regimes feed and harbor terrorists. What? Did I say something I shouldn’t have? Okay, so how about this: After having taken part in the most serious financial crisis in the western History, engulfed billions of tax payers’ money, gobbled up those same billions to its own traders and executives, it is only normal that Bank of America takes a unequivocal actions to protect the United States. Aha. When I was a kid I used to think we, the “free world” stood against this sort of things. Now it just reminds me of a quite dark reenactment of the french drama “Tartuffe” by Molière. Meanwhile Private Manning is tortured in a maximum security prison, without any trial.  Did someone say “Soviet Union”?
  • It’s Holiday Season, nonetheless, and I thought you may want to take a look at how Christmas looks in Paris, especially under the snow. (Paris is a city that looks particularly beautiful under the snow). Prête-moi Paris has all the details.
  • The EIF and EIS 2.0 are published at last. In many ways it is disappointing, but it is at the same time a clear political gesture in favor of open standards and true interoperability.

Best wishes for the Season!