Lanedo supports LibreOffice

In our recent announcement of the Engineering Steering Committee, we wrote that Michael Natterer from Lanedo is having a seat in this body, contributing further to the development of LibreOffice. Here’s their statement of support: “Lanedo is proud to support LibreOffice, and participate in development and inside the Engineering Steering Committee (ESC)” said Martyn Russell, Managing Director, “our contribution underlines the quality and effectiveness of our software development and support services around LibreOffice.”

Developer Interview : Rob Snelders

LibreOffice can only exist because people are working on it: so please, tell us a bit about yourself.

I am Rob Snelders, a 28 years old Dutch guy. I am a programmer at a manufacturer of household equipment. I have studied Computer Sience at the Fontys University in Eindhoven.

In what other software projects have you been involved ?

I am also involved in T-Dose (www.t-dose.org), Ubuntu-NL.

What do you do when you’re not working on LibreOffice ?
(more…)

LibreOffice Hackfest in Munich

Together with their Linux migration team (LiMux), we’re planning a LibreOffice Hackfest in the City of Munich, Germany. To determine the best date for it, let us know all your possible dates! Like last time, the Hackfest is open for newbies as well as for routined hackers. More details will follow soon, but first, we need the date. So, let’s vote!

The poll is at http://doodle.com/i7pw9wubvdhdyzm4

NOTE: The Hackfest will run from Friday evening to Sunday lunchtime. For the ease of voting, we have just mentioned the respective Saturday.

Why TDF should be the place for one united Community

I have not been subscribed to the OpenOffice.org marketing list for months, but due to Louis’ recent Cc, I was made aware of the discussion going on — so, as a representative of TDF, but also as someone for whom personally the community means a lot, let me say a few words.

I indeed see the current situation as an ideal basis for uniting things. The diversity the Community is in now doesn’t help anyone. If you now think we, TDF, are happy and get satisfaction out of the current situation, you are terribly wrong. Even if we expected something like that to happen, our intention was to safeguard the project from this eventuality, not to profit from it.

We all have similar goals: a free office suite, available to everyone. So let’s not discuss about the past, about what has happened and about the reasons that led to this, but rather focus on the future.

I want to openly repeat our invitation to everyone to join The Document Foundation and the LibreOffice Community. Why do I think that we are the right place to continue the work?

In yesterday’s blog post, we summed up where we stand, and reading it will help to understand the current situation:

http://blog.documentfoundation.org/2011/05/24/updates-on-the-foundation/

  1. We are vendor neutral. I am sorry that I have to object to Louis’ statement of us being a proxy for Microsoft — nothing can be further from the truth. I must confess, that by statements like these, I feel even personally insulted. I spend many hours per day on a pure volunteer basis, and if anyone can point on those of my doings that are proxying for Microsoft, I would be interested to hear them. Otherwise, I’ll ask to stop spreading those wrong assumptions — as they are simply that: wrong.

  2. We have a strong legal backing, not only by the German nonprofit “Freies Office Deutschland e.V.”, but also by the Software in the Public Interest (SPI), and we are on track with establishing the Foundation as a legal entity. Even right now, we have all options needed for dealing with legal aspects, accepting and spending money. We already can and do maintain trademarks, brands and other assets.

  3. We have an independent infrastructure that works and is not controlled by nor depends on a single entity. In addition, as we are not using a fixed web framework, we are very flexible in what we do.

  4. We have not only gained a lot of momentum, but also a strong developer base of more than 200 volunteers, amongst them 40 who contribute on a very regular basis. Yes, of course, any contribution corporations with paid developers do are highly welcome and help a lot — but already right now, we are in a status where we could drive the project without them, if the worst case would occur. This is something we never managed to achieve in ten years’ of OpenOffice.org.

When I first read the Oracle announcement from April, talking about an independent, noncommercial entity, my first thoughts were — and still are — “this is exactly what TDF is doing”. I have seen proposals of setting up another foundation, or moving to an existing foundation that is not TDF. Honestly, this does not make very much sense to me. It would again lead to a diversity, would require many efforts, and would continue to irritate the market at large.

Why reinvent the wheel? OpenOffice.org is already very special in many of its processes. Having it under the umbrella of another, existing entity, would require lots of changes to fit in there. TDF has, from the very beginning, been shaped as a new entity with processes that fit to what we have accomplished the last years. We changed things that didn’t work, and improved things that do work — isn’t this the best basis to build on? Let’s not waste energy in once again trying to fit under an umbrella, but rather work jointly together on our future.

I am not saying that TDF does everything right and 100% perfect. We are giving our best, and I think we do a fairly good job. I’ve seen comments that TDF is missing big corporate support, and that the whole ecosystem is at risk. Again, I consider this terribly wrong. Of course, we would love to have much more support from corporations already, but building this up needs time, requires trust and confidence, and after all, support is growing rapidly. If anyone thinks by setting up a new foundation or by doing a few phone calls you can get big corporate support, I must say that almost sounds illusionary. And does it really make sense that in the future, two entities will try that out? Wouldn’t it be much better to speak united, with one voice?

In my letter of resignation last October (http://www.mail-archive.com/dev@marketing.openoffice.org/msg11691.html), I’ve said that I am looking forward to talking again about options to cooperate. I feel that time has come now.

So, I would be really interested of what actually prevents from cooperating with TDF, and uniting once again. Are there any valid reasons? Let’s leave out what happened in the past — a lot of bad words have been said, but digging into that does not help.

What compelling reasons are there to not work together again, in one Community?

TDF is there, TDF is open, and to me, it would be the ideal home of a united Community. The decision about that requires no leader, but you, anyone of you, can make it on your own.

Our future can be bright. Let’s make it together.

The Document Foundation announces the members of the Engineering Steering Committee

The body coordinates development activities and defines the technology evolution of LibreOffice

The Internet, May 23, 2011 – The Document Foundation presents the members of the Engineering Steering Committee, the second body to be announced – after the Membership Committee – of those envisioned by the foundation bylaws. The ESC has come into being in early 2011, and is now officially in place to coordinate all development activities and set future technology directions.

The 10 members of the ESC are Andras Timar (localization), Michael Meeks and Petr Mladek of Novell, Caolan McNamara and David Tardon of RedHat, Bjoern Michaelsen of Canonical, Michael Natterer of Lanedo, Rene Engelhard of Debian, and the independent contributors Norbert Thiebaud and Rainer Bielefeld (QA). The ESC convenes once a week by telephone to discuss the progress of the time-based release schedule and coordinate development activities. Their meetings routinely include other active, interested developers and topic experts.

The members have been appointed by the Steering Committee, and are drawn from key members of the community of developers, which has been steadily growing since late September 2010 and is now close to 200 code hackers, with another 200 people involved in localization and QA. “This is a phenomenal success,” says Caolan McNamara of RedHat, “Especially if you look at the OOo project, where external contributors were a small group, and had to deal with significant obstacles.”

There are around 120 developers hacking LibreOffice code on a regular basis; these can be divided in three groups based on their experience: 20 core developers working on features, fixes, and packaging the software; 40 more regular devs working on features, fixes and easy hacks; and 60 less-regular devs working on easy hacks and code cleaning. In addition, there are around 80 developers who are contributing occasionally, or have just started to dig into the code. TDF is also grateful for the influx of students who will be paid to work full-time over the summer by the Google Summer of Code program.

“The ESC has brought the necessary discipline in the development process, which is organized in a completely different way from the past at OOo, where there was a single company in charge of the decisions, which was at the same time a strength – as it was easy to coordinate – and a single point of failure,” says André Schnabel, a member of TDF Steering Committee. “We have instead built an independent process, where corporate sponsors are still valued, but the community is able to take the software forward even without the backing of any of these companies.”