Election of the TDF Membership Committee – List of Candidates

Dear Community,

as previously announced, all members of The Document Foundation are called to vote on a new Membership Committee.

Members of The Document Foundation as of 2012-07-01 are eligible to vote in the elections. The nomination period is now over, and we have received the following candidacies, in order of receipt:

  • David Emmerich Jourdain
  • Sophie Gautier
  • Fridrich Štrba
  • Simon Phipps
  • Leif Lodahl
  • Jean Weber
  • Eike Rathke
  • Cor Nouws
  • Florian Reisinger

If you nominated yourself for elections, or have been nominated by someone else, and are not mentioned in the above list, please get in touch with us as soon as possible at elections@documentfoundation.org

From all candidates, we also need full name, e-mail, corporate affiliation (if any), and a description of your reasons for wanting to serve as a committee member. If you didn’t send in any of these so far, please do so as soon as possible to elections@documentfoundation.org

We’ll soon reach out to all of you with further details. As previously announced, the actual election period will start at 2012-09-09 00:00 UTC and end at 2012-09-16 23:59 UTC.

We are looking forward to the elections, and would like to thank you for your work, engagement and dedication for The Document Foundation!

Meeting Richard Stallman

Following his speech the day before at the University of Munich, TDF Chair Florian Effenberger and admin team member Alexander Werner, together with a group of students, had the chance of meeting Richard Stallman. It was a fun day getting input from the President of the Free Software Foundation, who alongside many others, are a key member of our Advisory Board. The picture below shows the group enjoying some Italian ice cream. 😉

Meeting Richard Stallman

LibreOffice 3.6 Bug Hunting Party – July 6 & 7

TDF announces the LibreOffice 3.6 Bug Hunting Party to improve the quality and stability of the best free office suite ever

Berlin, June 29, 2012 – The Document Foundation (TDF) announces the LibreOffice 3.6 bug hunting party, to be held in a virtual environment on July 6 and 7, 2012.
Volunteer bug hunters will gather on the Internet from the five continents to spot software problems of the upcoming new major release, featuring a large number of improvements and new functions, in order to make LibreOffice 3.6 again the best free office suite ever.

Participating is easy, and fun.
Details are available at the wiki of The Document Foundation, where one can also find a comprehensive list of LibreOffice 3.6 new and improved features.

All you need to join is a PC with Windows, MacOS X or Linux, and LibreOffice 3.6 Beta 3 (or Beta 2), plus a lot of enthusiasm.
The LibreOffice 3.6 Beta is to be downloaded from the pre-releases web-page.

Filing bugs will be easy, thanks to the improved bug submitting assistant and the help of several experienced people who will be around to help users and supporters with tips, on the QA mailing list (libreoffice-qa@freedesktop.org) and IRC channel (irc://chat.freenode.net/libreoffice), where many people are expected to join from 8AM to 10PM UTC on both days.
And of course there is a webpage withinformation on filing bugs.

People joining the LibreOffice Bug Hunt Parties not only do so for hunting new bugs. Checking and possibly categorising already submitted bugs also is a popular and interesting activity.

Community Meetings at LibOCon

As previously announced, the next LibreOffice Conference will take place from

    October 17th to 19th
    in Berlin, Germany

with the Call for Papers currently running (http://conference.libreoffice.org), and the final program to be announced in early September.

All three days of the conference are open for the general public. In addition, on

    October 16th
    i.e. one day before the official Conference

we will, in good tradition, host the so-called Community Meetings. While they are not per se private, they are – in comparison to the rest of the Conference – mainly targetted towards existing project members, and take place in form of meetings and workshops rather than lectures.

Currently planned are meetings for the following groups:

  • Board of Directors
  • Advisory Board
  • Membership Committee
  • Engineering Steering Committee
  • regional groups, like the German, French, Italian or Brazilian community
  • marketing
  • website
  • design and user experience
  • QA and localization
  • system administrator and infrastructure
  • certification

If you are part of any of those groups, committees or bodies, we strongly recommend planning your trip so you can attend on October 16th already. The Community Meetings serve the purpose to meet your fellow colleagues and friends, discuss the successes of the last twelve months, and plan the achievements of the next year.

Looking forward to seeing you in Berlin!

Developer Interview: Lionel Elie Mamane, LibreOffice Base Maintainer and Volunteer

(Interview by Michael Meeks, edited by Marc Paré)

In our continuing series “Developer Interview”, Lionel Elie Mamane discusses his work with LibreOffice code and of his particular interest with Base. His lead role in maintaining the Base module is helping raise the use of Base among the LibreOffice community at large.

Lionel Elie Mamane

How did you hear about LibreOffice?

Debian switched to it from OpenOffice.org.

LibreOffice can only exist if people are working on it; so please, tell us a bit about yourself. In what other software projects have you been involved?

Mainly Debian, but I’ve always sent patches left and right to scratch my itches; a more or less random selection:

  • IPv6 support for privoxy, an anonyimising HTTP proxy
  • bugfix for gfax, a graphical interface to send faxes: handle spaces in telefax numbers gracefully
  • Linux, the kernel: In SIT tunnels set to “tos inherit”, propagate IPv6 transport class byte from the inner packet to the ToS byte in the outer packet, like IPIP and GRE tunnels already did
  • Pan (newsreader): fix interaction with mutt (email user agent)
  • Pan: bug in thread filter
  • Fixes in some LaTeX packages
  • mutt (email user agent): fix parsing of mailto: URLs

What do you do when you’re not working on LibreOffice?

Finish up my PhD dissertation in theoretical computer science/computer mathematics.

What is your thesis?

The field is proof assistants, that is programs that help mathematicians make theorems (proofs), manage them, etc. But also that check that a proof is correct.

My thesis is that the way current / historic proof assistants are going at it, we will “never” have a nice proof that we can show to a human and that will be “nice” to read. We have to change a bit (but not that much) how they are organized, both as concrete systems (programs), but also the theoretical underpinnings.

I handle the IT needs of a small (15 people) company.

What company? Can you give us a link and tell us of it’s products?

The company is Gestman S.A.. It does administrative, accounting and juridic work.

I’m also adviser to a charitable foundation called: Matanel. Its mission statement is summarized as “Matanel Spirit: The Matanel foundation, granted to give, encourages social entrepreneurship in all over the world.”  The full version of Matanel’s mission statement explains this in more detail.

Additionally to more “classic” charitable stuff (food, education, culture, …), I’m to blame for the logo being on Debconf11, Debconf12. You’ll notice my employer (Gestman s.a.) is also a sponsor of these conferences, and also pays my attendance to the same: http://debconf8.debconf.org/corporate.xhtml.en

When do you usually spend time on the project?

If I was interrupted in mid-thought or mid-bugfix by my carshare, I finish at home.

So European waking hours?

Yes.

Why did you get involved?

Because I want to use it as a programming platform for database-driven custom business applications at work. As a Microsoft Access killer, if you want. I started fixing bugs and adding small features that were useful to me, and before I really realized it, I find myself being the LibreOffice database expert.

Lovely, that’s exciting! What do your business applications do? Can you flesh that out a bit?

The business applications do:

  • customer database
    • contact data
    • track who is authorized to order which action on behalf of customer
  • billing: manual, automated, semi-automated
    • when customer asks for out-of-package work, bill by hourly tariff
    • statistics on which employee works how many billable/in-package/non-billable hours
    • statistics (for each customer) on how many hours spent on in-package work vs price of package.
  • tracking of assets and investments we manage
  • track advancement of work that needs to be done, and its bouncing from employee to employee or external entity.
  • For example, filing a company’s tax return:
    • accountant prepare balance sheet: employee 1
    • account manager validates: employee 2
    • send to auditor: employee 3
    • waiting for auditor: external service
    • file tax return as certified by auditor: employee 4
    • did we get the filing acknowledgment from the tax authority?

What was your initial experience of contributing to LibreOffice like? And how did that make you feel?

Very welcoming community. Err… Very welcome? My skills are recognized, contributions valued …

What was your first contribution to LibreOffice?

My first “applied as I wrote it” patch seems to be (date:   Sat Jan 15 05:39:40 2011 +0100):

#116187: report left/right page margin setting ignored on Unix 64 bit

The bug was: when one changed the left or right margin of a report on a 64 bit arch, all changes done in that dialog were lost.

What have you done since then?

Fixed a lot of stuff in Base, and a bit in scripting.

Great! Can you expand on the importance of fixing base?

Nearly all “enterprise/business applications” are more or less “read this from that database; do this work on it; push that to the database, …”. LibreOffice will never be a rapid application development platform à la Microsoft Office + Visual Basic for Applications without a solid database access / management / … component.

How will that improve things for users?

Users will be able to use LibreOffice for database access without crippling bugs.

What is your vision for the future and/or what would you like to see improved?

  • Ideally I’d like to have a rich, vibrant Developer/Tester/QA/ … community around base.
  • Interested in database stuff or scripting in LibreOffice? Come join  us! You can be useful at many different levels, with many different skills and levels of specialization: programming, bug triage, QA, testing, documentation writing, …
  • The reporting system is a bit primitive and could use a real upgrade.
  • It would be nice if forms could show several records at once (not only in grid mode).
  • The many dependencies on Java are a liability, and I’d like to have them curtailed / removed.

What do you think of the new build system?

gbuildification is a nice step forward, but it is “recursive make”, which is bad; see http://miller.emu.id.au/pmiller/books/rmch/  At least now it is not “much worse” than most other projects.

Errata: Actually, it was now explained to me that the “recursive” nature of our gbuild system is transitory, and that wen everything will be gbuildified, it won’t be recursive anymore (everything will be in the tail_build module). Great news!

I’m 100% convinced that our dependency information is incomplete and/or too low granularity. I still have build problems solved by a “make module.clean” or some such. And, when I try to do a more surgical “rm”, it often fails BECAUSE THAT FILE IS NOT REDONE, so, compilation of a different file fails with message “file you removed missing”.

Which is your preferred text editor and why?

Emacs. Habit (keybindings in muscle memory), features, programmability in a decent language (I’m a functional programming guy at heart), …

What would you encourage new contributors to work on with you?

I’ve made a few “easy hacks” with suggestions.

Anything else interesting you get up to when not hacking?

No, hacking is my life 😉

Thanks for your time and commitment to the project!