The Document Foundation Planet

 

September 16, 2014

David Ostrovsky

Gerrit User Summit/Conference in Mountain View, CA

As you may know i was participating in this year Gerrit User Summit, 21-26 March, followed by Developer Hackathon in Mountain View, CA.

I had three presentations: Gerrit@LibreOffice with detailed explanation of Gerrit Buildbot plugin and two feature requests:

Among other presentations Edwin summarized new features in upcoming Gerrit 2.9 release, that was later converted to regular documentation page in Gerrit. Shawn presented plans for future Gerrit/Git development:

  • Moving from database to Git to store meta data
  • Provide alternative Git storage backend(s) to file system backend.
  • Improving Git submodule feature set

During the Hackathon i continued the work on inline edit feature: to allow to change code during review directly in browser. It should also have support to create a new empty isolated change and a follow-up change from a given change directly in browser and allow to populate it with code changes.

On Sunday we had mountain bike tour in Santa Cruz national park. Thanks Edwin for these great pictures:

Big thank to The Document Foundation for funding my participation.

by davido at September 16, 2014 06:49 AM

September 14, 2014

Andreas Mantke

New Account Request Form for LibreOffice Plone Sites

Because the infra team of the Document Foundation wants to shut down the OTRS instance I worked on a new Plone addon that sends the data of a form to an imap account. The header and content of the email seemed to be in a good shape. Let’s see if the tests validate.

by andreasma at September 14, 2014 07:59 PM

Charles Schulz

Marketing Strategy Workshop 2014: More engagement, better conversations

Last week we had a great LiboCon 2014 in Bern, organized by a great team and a great (and often not known well enough) city. We had what has become some sort of tradition, by which I mean the Libreoffice Marketing Strategy Workshop. This year was a bit special however in that the workshop itself came after a series of other workshops dedicated to media training and messaging by Italo Vignoli and another session aimed at helping non-native English speakers promote LibreOffice in their language. All these sessions did prepare the audience to the strategy workshop but were also a very nice addition to it. I was also happy to notice a stronger attendance than previous years to the workshop, as well as a more diverse one that included at the same time active contributors, contributors of native-language projects, and “simple” visitors of the conference. Some of them actively contributed to the session, and I found that to be very useful.

While there was no shakedown of the marketing strategy this year, there was however a strong focus on online campaigning and volunteers’engagement methods. It was also a good opportunity to let everyone share ideas and experiences. Below are the main discussion points of the workshop. You may download the slides supporting the workshop directly here.

Achievements

This year we had several notable successes, despite remaining a project with a small marketing team. First, our new website has been one of our most visible achievements and has been in most cases very well received. LibreOffice needed a more visually appealing website, and there was an interesting discussion as to how we were conveying the idea of what LibreOffice is, both as a software and as a project. We will come back to that in the latter part of the post.

Second, there is a real momentum around LibreOffice on social networks, with the presence on each online service acting like a specific channel for a certain type of activity and conversations. For instance, Facebook is our the network with our biggest outreach, yet it is probably the most passive one, with very few conversations taking place. The volume of the audience however makes it worth maintaining an active presence there. On Twitter we have two accounts, @tdforg and @libreoffice . We started tweeting irregularly through @tdforg and got lots of success for three years; but we had kept @libreoffice under wraps. Starting in 2014, we started to differentiate between @tdforg being more about official announcements, and @libreoffice tweeting several times a day. In both cases we reached several thousands of subscribers and are engaging in (short) conversations with users on a regular basis. Google + is also a big success and a quite interesting one. Here again, we have several thousands of followers but what’s really interesting is that it is a place where people discuss topics and post new ones. Users support is also happening sometimes there.

Reddit was a modest (several dozens of members) channel for us and has now grown to several hundreds so it’s definitely something to keep an eye on.

All this work described above has led to one specific and recurring objective: Increasing LibreOffice’s brand awareness and growing our contributor’s base. We still have lots of work to do, and we had a discussion about the results of the LibreOffice ad in the german special edition of Die Zeit. We realized that should we decide to go for these traditional ads, we would need to have a more comprehensive campaign with an actual story line in order to yield measurable results.

Another set of achievements has been the real improvements in how the communications on the LibreOffice releases are handled  throughout the community. Thanks to a clearer and more inclusive process, the LibreOffice native-language teams have the time to localize the release and announce it by translating the press release in due time. This is no little effort when you consider the work put into the localization, the quality assurance on the various betas and release candidates, and the translation of the PR itself. Last but not least, and before we skip to the other parts of the workshop, this year was also a successful year in terms of articles written about LibreOffice and the Document Foundation. This also helps us increase the brand awareness and help us grow our userbase and our community.

Challenges & Solutions

Despite our achievements, our marketing team remains small (around 4 individuals contributing on a non permanent basis, sometimes daily, sometimes weekly). The discussion this year suggested that we put more effort into contributor’s engagement and while this used to be somewhat of a tricky question, I think we now have enough hindsight to make it work. In order to understand the situation one needs to take a step back and consider the following.

When the LibreOffice project was created it was one of the best opportunities to start afresh in the way the community and how each of us contributes to the project was valued. As a result, it was decided that a strong meritocracy would be instrumental in improving the low rate of contributions of the former OpenOffice.org project in a substantial way. It worked and still works really well for most of the project, but marketing or promotion did not overly benefit from that. Of course, it helped us gain time and stop wasting energy dealing with distractions such as endless (and pointless) discussions on “product marketing mixes” and so on. Yet it did not help us multiply our base of marketing contributors. The principle, which remains the same, that in order to be acknoledged by the community you must first contribute something to it, did not, however, handle too well the kind of contributors who would be happy just with little things, such as badges. While developers tend to not pay any kind of importance to these details, we also had to deal with the fine line between handing someone a badge and some sort of formal role, and giving a title to someone just because he or she would have asked for it. A title in itself is little, and probably nothing. Yet our experience with OpenOffice.org showed that it was very easy to have titles, and even easier to do nothing to earn it. Thus, anything that had to do with badges was viewed with skepticism, if not prejudice.

This year, we are going to start improving the quality of our contributors’ engagement with the project at least in non-technical areas. A badge does not imply any sort of hierarchy, or formal role. It does not replace the membership to the Document Foundation. It is just what it is, a badge.

At the same time, we would like to drive the same experiment than the one our Design and UX team had a few months ago: a full migration to the RedMine platform hosted on the project’s infrastructure. While we may stick to a few of our existing tools (the existing wiki), RedMine essentially turns your team’s activity into a project and tasks’ based workflow, while eliminating much of the noise. The discussion, because of the tools, are directly related to tasks, and tasks behave pretty much like issues opened in a bug tracker.

We had an interesting discussion about the need to engage in communication campaigns that tie in to specific news or moments. We should be able to “join the conversation”, when one of our competitors claim something we can talk about as well. These campaigns would definitely help us raise our brand awareness too. This will also require that the marketing team starts working on its own banners and online material without necessarily hogging the resources of the Design team.

Last but not least, we have experimented with something called LOWN (LibreOffice Weekly Newsletter), thanks to William Gathoye. This newsletter is not really meant for people outside our community. On the contrary it is designed for community members, who want to stay in touch with all corners of the project and learning about what’s going on in other teams. We may want to make it a montly newsletter, but it is encouraging to see this becoming a community based effort.

As a conclusion to this very long post, I would like to thank everyone who joined the workshop this year, it was a great moment of sharing and I think it will help us moving forward for next twelve months, be a better community and a more efficient project.

by Charles at September 14, 2014 09:27 AM

September 13, 2014

Caolán McNamara

More Font Support

Playing around with some Mac OS X fonts under Linux I noticed that LibreOffice wasn't listing a lot of them despite fontconfig announcing their existence. A little digging and some very small tweaks means that we now have mac ttf fontname encoding support along with support for version 2 ttc fonts. This is more fixing some oversights (version 2 of ttc came into existence after the ttc support was added so there was a "only if version is 1" condition) than implementing anything particularly new, but now LibreOffice under Linux works with a lot more ttf/ttc/otf fonts than it did before.

by Caolán McNamara (noreply@blogger.com) at September 13, 2014 01:27 PM

Leif Lodahl

Apache Open Office and LibreOffice should join forces

p { margin-bottom: 0.25cm; line-height: 120%; } This proposal has been said many times over the last couple of years and lately repeated by Daniel Brunner, head of the IT department of Switzerland's Federal Supreme Court.https://joinup.ec.europa.eu/community/osor/news/open-and-libre-office-projects-should-reunite. And from the first point of view I can only agree. There is no reason what

by Leif Lodahl (noreply@blogger.com) at September 13, 2014 08:01 AM

September 12, 2014

Joel Madero

Why TDF Doesn’t Do Crowd-Funding

Notice: These are my opinions as an individual, not as a member of the Board of Directors

Note: Slight updates to “accounting” section due to clarification from my good friend :)

From bug reporting on bugzilla, to user/QA mailing lists, all the way to the QA chat, users (and contributors) ask “why not just do a targeted crowd-funding for X,Y,Z.” X,Y,Z has been mostly large projects and/or ideas– including but not limited to Android development, revamping our UI, or even individual “pet bugs” that people have reported. So, in theory crowd-funding sounds fantastic…right? Well, here I’ll try to convince the doubters that TDF doing targeted crowd-funding is indeed, anything but a great idea :)

Accounting

This is perhaps the easiest one to explain. TDF is incorporated in Germany (this is not implying that it would be any easier in another Country) and with that comes of course, German laws (which are likely the same in other countries). These just add a new layer of having to track different “pools” of funding.

The next accounting related issue is what happens if we are short or over (ie. we don’t hit our #’s or we overshoot the #). Well then we’re in a pickle. On one side, if we undershoot the target, do we refund people? Do we merge the money with general funds? Do we just indefinitely hold it in case we ever hit the #? All of these sound quite tiresome/time consuming/confusing. Now if we overshoot, again the same problems arise. Do we refund the extra money? Do we put it in the general funds? Either way accounting for these can be difficult and time consuming.

When push comes to shove, this would just eat up our employee’s (or a tremendously dedicated volunteer’s) time just tracking the #’s and I don’t think anyone would be happy with these results.

Expectations

Donor expectations are another area that becomes overly complicated with targeted funds. Person X donates $100 to “make UI better”, person Y donates $10 to “make UI better.” Now the two don’t agree on what making it better means (one suggests one mock up, the other suggests a radically different mock up). Who wins? If we decide on person Y’s mock up, does person X get a refund because they actually think it’s a horrible UI? What about the difference in contributions – one gave 10x the amount of the other, should that matter at all? Perhaps it shouldn’t…but try explaining that to person X with a straight face. Do we put it to a vote? And then the losers of such a vote get the option to demand a refund?

The reality is that targeted funds come with expectations, and no matter how clear the message of the targeted funds, someone is bound to be unhappy with the result. We’d hate to offend our donors by saying “deal with it” if they get a result that they aren’t happy with and contributed funds specifically for that thing.

Funding for “Less Sexy” Things

Person X has $20, they go to the donation page and they see “general fund” (with some description of what that mean) and then they see “awesome NEW FEATURE!” . . . where do they donate? Exactly, you get the point. While it’s fun to fund new exciting and sexy things, the “non sexy” things are quite (probably a lot more) important. These include paying for infra (quite expensive), employees (who do amazing work), and events. Worst case would be to have a bank account with $50k for “awesome sexy flying monkey feature” and $0 for “general operating expenses.” The response might be “set aside some amount in advance for day to day,” in theory possible, but time consuming and when that amount runs dry – what do we do? Pull “sexy awesome flying monkey feature” from the donation page to “encourage” donors to donate for the necessities?

 

As you can see all of this is quite complicated.

So…Now What?

Well there are indeed options and the Board takes this (and similar) issues seriously. For instance with Android port – we heard, and we acted. We now have a public tender which we are using to solicit bids to start the port to Android. Beyond that:

  1. There are of course grass roots crowd sourcing sites, we don’t vouch for any of them, but we don’t discourage trying to use them. That being said, please note that the risk is on you (the founder of the campaign) and not on TDF to deliver. If you raise $100k and promise to fly everyone to the moon, it’s on you to deliver. But in all honesty, if you raise money and “think” that it might be enough to fix some pet bug or something, ask around the dev channel to see if anyone is interested in doing it for that price – but please please please be aware that if you have no background in programming, you’re likely going to underestimate the cost of development by multiple factors. Before starting a campaign, best to ask for a rough guess at cost from someone who knows the code.
    1. Options: kickstarter of course, and freedomsponsors – again I am not endorsing either, I’ve just seen both used
  2. Volunteer time
    1. Do the leg work! Our group is a meritocracy, doing the leg work tremendously pays off. For instance instead of saying “fix the UI” – build a community, get support for a concrete proposal, get documentation together for functionality, etc… etc… Too often I see a mockup with nothing more (a single image done in an hour or two) and then demands that we implement – this simply won’t work.
  3. Join our public board call – trust me, we’re happy to have the public in (that’s why it’s a public call). If you have strong feelings about something (and are willing to put in work/time/money/etc…) we’re willing to listen. This does not mean jump into the call and demand the world and not give anything in return – again this won’t get us closer to anything other than a headache.
  4. Despite the cons listed above, TDF hasn’t 100% ruled out the possibility, we’re just not ready to make the leap right now. Perhaps at some point in the future it will happen, but until then, I highly encourage our users, donors and contributors, all to find creative ways to get their projects done.

 

 


by joelmadero at September 12, 2014 04:22 PM

User Prompt

Understanding Icons: Participate in magic survey #9

In this icon test we take a look at another colored icon set. Please, again, participate and help us to learn more about the usability of icon design.

Please participate in our little game! (Study closed)

It is fun, takes a maximum of 5 minutes and helps us to better understand effects of icon design.

For more information please check our initial post on the idea and background of this series of small icon tests.

by Björn Balazs at September 12, 2014 09:48 AM

September 11, 2014

Andreas Mantke

Moving away from OTRS

The LibreOffice extensions and template site uses currently the ticket system OTRS for the admin workflow. Because The Document Foundation is moving away from this system to Redmine I have to work on a solution for the extension and template site. The infra team decided to use an imap account instead of OTRS. I made some tests with such a setup and in general it would work. But I need to work on a Plone addon first to get the user message in an appropiate way into the mail account. Hope to get that done in the next days.

by andreasma at September 11, 2014 08:53 PM

>Andrzej Hunt

LibreOffice on Android #3 – Calc Documents

After a somewhat painful debugging experience*, it’s now possible to view Calc documents on Android too.

This combines the Calc Tiled Rendering work (thanks to the Google Summer of Code) with the LibreOffice Android Viewer developed by Collabora (thanks to Smoose):

Calc on Android

This work is still on a branch (as some of the changes affect Calc’s normal rendering, and still need to be fully verified as to not introduce unwanted bugs there), but should hopefully be mergeable soon.

* Using the r10-ndk it was possible to at least set (and make use of) breakpoints on methods, however gdb seemed to be blind to any other debug-info, making this a pointless exercise. With the r9d-ndk, gdb wasn’t even able to connect to the application. (Fortunately we can still get log output via adb logcat — resulting in slow but useable debugging.)

by Andrzej Hunt at September 11, 2014 05:06 AM

September 10, 2014

>Efe Gürkan Yalaman

Bern Conference

Merhaba,

First of all thanks all of the guys for the great conference. It was a great experience for me as always. So I am making another blog post which is more like a travel post, so it will be on my main blog instead of this.

So I will summarize shortly what I learned. About project itself.

- LibreOffice code itself is big, but the people who working on it is not that much. Yes, yes I know there are 2-3 person projects which are awesome. Yes I know we are huge if you compare us with them. But we are not “THAT” big.

-LibreOffice development speed is fast. I mean fast as the car which overtakes you in autobahn when you were going 180kph, and you couldn’t see the color of the car.

-Unit tests are important.

-Use icecream! And don’t tell your colleagues. :-)

-We have much more better OOXML support compared to last year. I mean much much much more better.

-Unit tests are important!

-Watching Fridrich presenting is the best thing I have done in my entire life!

-Did I mentioned Unit tests are important? If I didn’t, Unit tests are important!

-We have OpenGL on charts and Impress ! How cool is that!

-Unit tests ar……… *cough* *cough*…

 

Here are some pictures I took with my cellphone. So they are potato quality photos.

https://plus.google.com/photos/115301608275454477024/albums/6055704218280733569

If you don’t like your presence on the photos contact me so I can delete it if you want.

 

Thanks everyone! Stay awesome!


by namcojoulder at September 10, 2014 09:32 AM

September 09, 2014

Kohei Yoshida

Slides for my talk at LibreOffice conference in Bern

I’d like to share the slides I used for my talk at LibreOffice Conference 2014 in Bern, Switzerland.

slides preview

During my talk, I hinted that the number of unit tests for Calc have dramatically increased during the 4.2 bug fix cycle alone. Since I did not have the opportunity to count the actual number of unit test cases to include in my slides, let me give you the numbers now.

ucalc filters subsequent-filters subsequent-export total
4.1 65 10 49 9 133
4.2 107 13 54 15 189
master 176 15 67 34 292

unit-test-count

The numbers represent the number of top level test functions in each test category. Since sometimes we add assertions to existing test case rather than adding a new function when testing a new bug fix, these numbers are somewhat conservative representation of how much test case we’ve accumulated for Calc. Even then, it is clear from this data set that the number has spiked since the branch-off of the 4.2 stable branch.

Now, I’ll be the first to admit that the 4.2 releases were quite rough in terms of Calc due to the huge refactoring done in the cell storage structure. That said, I’m quite confident that as long as we diligently add tests for the fixes we do, we can recover from this sooner rather than later, and eventually come out stronger than ever before.

by Kohei Yoshida at September 09, 2014 08:59 PM

Caolán McNamara

change image option in writer context menu

Change Image in Writer

Thanks to Jennifer Liebel, writer now has a change image option in its graphic context menu like Impress/Draw.

by Caolán McNamara (noreply@blogger.com) at September 09, 2014 12:28 PM

September 08, 2014

Michael Meeks

2014-09-08: Monday

  • Mail chewage, tried to re-arrange tasks into some sort of sensible order with Andras, Kendy & Tim's help. Lunch. Reviewed and merged a rather nice string speedup which was a victim of a previous String to OUString conversion.
  • Lots of partner / customer interaction backlogged from last week. Wrote an LXF column. Sam put up a nice LibreOffice from Collabora team picture from the conference.

September 08, 2014 04:52 PM

Naruhiko Ogasawara

LibreOffice Conference 2014 in Bern, Switzerland

Some of our community people already wrote some good reports about this awesome conference, but please let me add some with my poor English ;).

Bern is small but really beautiful city with the quite nice river (as a kayak lover, I checked the river), and University of Bern, which is our venue, is also nice.
Every food provided local crew was so yummy (especially cheese in sandwiches), and "hacker's energy" drink!  I love it.

All of the talks really excited me, and everyone who I met was so kind.  Really nice community, I love all of you!

Thanks to Kohei and Kendy, I had an opportunity to do a lightning talk.  Here is my slide.
<iframe allowfullscreen="" frameborder="0" height="356" marginheight="0" marginwidth="0" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/38827118" style="border-width: 1px; border: 1px solid #CCC; margin-bottom: 5px; max-width: 100%;" width="427"> </iframe>


Thanks you, and see you next year!
This group photo is taken by a kind passer-by girl using Matthias's camera.

PS. I might add some photo in this post later.

by Naruhiko Ogasawara (noreply@blogger.com) at September 08, 2014 03:00 PM

Miklos Vajna

LibreOffice Conference 2014, Bern

This year’s LibreOffice conference was held in Bern, Switzerland. Links to my slides:

During the sessions I also had some time to hack on the followings:

  • RTF export: added support for custom wrap polygon of Writer pictures

  • fixed fdo#82067 FILEOPEN: RTF images not in correct position

  • fixed fdo#82078 FILEOPEN: RTF bold text spilling over to non-bold text

  • fixed abi#10039 crasher on RTF export of page-anchored pictures

Regarding the number of attendees, draw your own conclusions from the group picture — probably around 300 attendees, counting all days.

Thanks for the organizers for this beautiful event — and also the sponsors! :-)

My pictures are available here (and I also made a panorama).

September 08, 2014 10:11 AM

September 07, 2014

Michael Meeks

2014-09-07: Sunday

  • To NCC, good to catch up with all & sundry. Lunch. Out for a run with N. across the heath - fun; lazed in the garden in the sun suitably.
  • Practised quartet a little, starting to sound quite good having moved lots of the blacker notes from E. to H. David over for a fine roast dinner.

September 07, 2014 09:00 PM

>Andrzej Hunt

Calc & Impress Tiled Rendering, and LOKDocView

At the Libreoffice Conference 2014 in Bern I gave some very brief talks, both related to my work this summer on tiled rendering (and the possibilities of reuse in external applications):

Calc and Impress Tiled Rendering

A shortish talk (as part of the GSOC Panel) on the implementation of Tiled Rendering for Calc and Impress:

bern14_ahunt_calcimpress_tiled

(Click on image for Hybrid PDF)

LOKDocView: the LibreOfficeKit GTK+ Widget

A very brief lightning talk on how to use our shiny new LibreOfficeKit GTK+ Widget (named LOKDocView). Is hopefully easy to use, hence one slide of real content should hopefully be enough to explain how to use it.

bern14_lightningtalk_ahunt_lokdocview

(Click on image for Hybrid PDF)

Attending the conference was a very valuable experience; allowing me to see past and future work by fellow contributors in addition to useful technical advice from some of the most important LibreOffice developers.

by Andrzej Hunt at September 07, 2014 05:48 PM

September 06, 2014

Michael Meeks

2014-09-06: Saturday

  • Up early - packed, set off for the rather nicer AirBnB venue; team all together - had a conference review / update with everyone - fun. Rather a late Pizza lunch, review of where we're at.
  • Off to the airport with Kendy & Lubos, very packed train. Pleased to see Eliane's link to a new (English): LibreOffice Video.
  • Lots of travel, eventually got home, bed exhausted.

September 06, 2014 09:00 PM

September 05, 2014

Michael Meeks

2014-09-05: Friday

  • Caught up with Adam & team. In-person Board meeting in the afternoon. Caught the end of Moggi's talk on 3D charting.
  • Gave a talk on faster XML Parsing with Matus:

    Still plenty to do to further accelerate our threaded parser.
  • Final open session with the board, with some useful input from the attendees - voted thanks to Mathias & team for their great work.
  • Out to the Indiana restaurant nearby again, and ate in the street with all & sundry until rather late; fun.

September 05, 2014 09:00 PM

Jan Holešovský

DrawingLayer: What Should You Know about It, and my other LibreOffice Conference 2014 presentations

At the LibreOffice Conference 2014, I had three presentations. The first one was about DrawingLayer, one of the core technologies in LibreOffice that is not known enough, which consequently leads to people not using it, or being afraid of doing changes there:
Click to see the presentation.

Based on the research I've done for the presentation, I extended the DrawingLayer's README and svx's README.

The other presentation was a Lightning talk giving a bit of a detail about the boost::unordered_map removal I've done, that was mentioned in the Miklos' blog post:

Click to see the presentation.
And the last presentation was about how to create a custom widget using the LibreOffice's widget toolkit, VCL:
Click to see the presentation.

The LibreOffice Conference is awesome, I'm extremely glad I can be here, and present to so many great people!

by Jan Holesovsky (noreply@blogger.com) at September 05, 2014 12:51 PM

September 04, 2014

Michael Meeks

2014-09-04: Thursday

  • Up early, to the university; gave a getting into the code for beginners talk - always nice to update that each year and dung out the cruft from the year before.
  • Catch up with Alberto & Caolan, fun. Lots of good talks on various topics.
  • Out to a rather fine meal with drinks at a nearby University venue - once again, excellent food & company. Encouraging (as a sponsor) to see funding applied to supporting collective meals & drinks through the day.

September 04, 2014 09:00 PM

Official TDF Blog

Tender for base framework for an Android version of LibreOffice with basic editing capabilities (#201409-01)

The Document Foundation (TDF), the charitable entity behind the world’s leading free office suite LibreOffice, seeks for companies to

develop the base framework for an Android version of LibreOffice with basic editing capabilities

to start work as soon as possible.

TDF currently plans to invest into getting LibreOffice, its free office suite, to mobile Android devices like tablets and smartphones, extending the existing desktop version of the software. For the volunteer community and the ecosystem to work on concrete features and an enduser-ready version that can be published, a base framework including the LibreOffice program modules Writer, Calc, Impress, Draw and Math is required. TDF seeks for companies to deliver this as a turnkey project until the end of February 2015.

Experience with the LibreOffice source code, mobile development on Android, as well as managing development projects and interacting with an international open source community is required. Current engagement and involvement in the community is highly appreciated.

Based on the technical design decisions that have already been taken during the basic implementation of a LibreOffice viewer for Android, which is built on the Mozilla for Android framework, the project includes, amongst other items, the following work packages. It is targetted towards basic framework and integration tasks to provision for basic editing capabilities:

1.) infrastructure

  • integration of on-screen keyboard that is only visible in editing mode
  • routing Android events to LibreOffice app
  • performance considerations
  • triggering updates of views
  • rendering and invalidation of tiles
  • insertion and deletion of content
  • threading

2.) selections (everything to be done in a separate layer)

  • texts and lists
  • tables for Writer and Impress
  • tables for Calc
  • pictures and shapes
  • support for OpenGL
  • rendering of selections on overlays
  • routing of application information from the program module’s core

3.) touch user interface for basic editing (based on Android design standards)

  • toolbar with basic controls, like bold, italics and underlined
  • context menu
  • menu items
  • deleting selections
  • loading and saving of documents
  • jointly working with our volunteer UX and design team for design considerations

4.) cloud storage and e-mail

  • provide basic interface for the community and ecosystem participants to develop integration of their preferred cloud storage
  • e-mail integration for sending documents via Android framework

Applicants are expected to include required project management as well as required writing of detailed specifications in their bid.

Note that the nightly builds at http://dev-builds.libreoffice.org/daily/master/Android-ARM@24-Bytemark-Hosting/ will not (!) be used as technical platform for this project. Instead, the technical platform will be the work that is currently carried out for having a LibreOffice viewer for Android, which is built on the Mozilla for Android framework, with source code available at core/android/experimental/LOAndroid3 in the public git master repository.

LibreOffice development is based mainly on C++ and C, as well as some Python and Java code. We exclusively use free, libre and open source (FLOSS) software for development whereever possible.

Previous experience with such tasks is highly suggested, given the complexity of the project. Communication on the project will happen exclusively in English language. Some fixed availability is required to coordinate with the developer community, which is mostly based in Europe (UTC+1 timezone).

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Companies applying can be located anywhere in the world.

Applications from bidding groups are welcome, so are bids on individual work packages. Companies with certified LibreOffice developers are preferred over other applicants.

A timing and cost estimation for

  • the additional work leading to a fully-fledged Android version,
  • with full editing capabilities,
  • a fully-fledged touch user interface with more controls, based on input from our volunteer UX and design team,
  • available at Google Play (taking the 50 MB size limit into account, providing mechanism for downloading missing components),

built on the framework outlined before, are welcome.

TDF is looking forward to receiving your applications, including company presentation, your financial expectations (name the final price for the turnkey project), and the earliest date of your availability, via e-mail to Florian Effenberger at floeff@documentfoundation.org no later than October 6, 2014. You can encrypt your message via PGP/GnuPG.

Applicants who have not received feedback by October 31, 2014 should consider their application has not been accepted.

by Florian Effenberger at September 04, 2014 09:06 AM

September 03, 2014

Official TDF Blog

Membership Committee elections – List of candidates

Dear members,

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 the day before the announcement are eligible to vote in the elections. The nomination period is now over, and we have received the following candidacies, in order of receipt:

  • Leif Lyngby Lodahl
  • Jean-Baptiste Faure
  • Charles-H. Schulz
  • Jan Holešovský
  • David Emmerich Jourdain
  • Andras Timar
  • László Németh
  • Sigrid Carrera
  • Cor Nouws
  • Cédric Bosdonnat
  • Jesús Corrius Llavina
  • Klaus-Jürgen Weghorn
  • Zeki Bildirici
  • Gabriele Ponzo
  • Gerald Geib

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, but no later than 2014-09-03, 20:00 CET/UTC+2, at elections@documentfoundation.org.

There are five (5) committee, and two (2) additional deputy seats to be filled during this election. Therefore a total of seven (7) slots are available, and will be selected by a single transferable vote system, seats filled in decreasing order of preference. Should more than two of the top seven vote-getters be affiliated with the same company, only the two with the most votes will be considered elected. This election is according to our statutes (non-binding English translation http://www.documentfoundation.org/statutes.pdf), and the term of office is two years.

All discussion related to the elections should be held on board-discuss@documentfoundation.org where members are invited to ask questions to one or all candidates. Instructions explaining how to vote will be sent via e-mail to all eligible voters in time before the election.

As previously announced, the actual election period will START at 2014-09-04, 00:00 CET/UTC+2 and END at 2014-09-11, 24:00 CET/UTC+2.

All eligible voters will receive an individual voting token via e-mail sent to the address we have registered in the membership database, with a subject of “Your Document Foundation 2014 Membership Committee Voting Token”. Please do not share this token with anyone as only you are entitled to use it. In case you have not received your token within 24 hours after the start of the election as outlined above, and after having checked your spam folder, please write to elections@documentfoundation.org AS SOON AS POSSIBLE.

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

On behalf of the Board of Directors,
Thorsten Behrens

by Florian Effenberger at September 03, 2014 04:02 PM

Tomaž Vajngerl

LibreOffice on Android

Thanks to Smoose, we are now able to do some real progress with the Android version of LibreOffice. The idea is to first build a LibreOffice document viewer, which is able to display any type of document that is supported by LibreOffice. Afterwards build on that and provide more features and eventually editing. The application itself should be a Android native application and use LibreOffice (interfacing through LibreOfficeKit) to provide tiles of a rendered documents and other needed pieces.

In the last couple of weeks I have been working on making this plan a reality. The first goal is to prepare the base of the application so I used the Fennec (Firefox for Android) source code. Fennec already solves many of the problems that we would need to solve - especially concerning drawing of tiles, touch handling, scrolling, tools and removed the rest, that will not be needed or needed later in development.

The calls to Gecko (rendering engine in Firefox) were replaced with our own implementation either in Java or a facade to LibreOfficeKit. By using a mock document tiles (tiles of the document that are part of the application's assets)  I was able to make the application work without actually interfacing with LibreOffice yet. With this the application  looked something like this:

At this stage the application was able to show a mock document with working scrolling and touch handling. The next big step was integration of LibreOffice and writing a JNI facade to LibreOfficeKit so that a real document rendered by LibreOffice could be show on a screen. With a big help from kendy we managed to integrate LibreOffice and correctly initialize LibreOfficeKit. After that the a real LibreOffice rendered document appeared:

See application in action video here.

Finally some results! There are some issues at the tile borders but this will be eventually resolved. The application uses OpenGL ES 2 for rendering so the user experience is smooth for the most parts (there are still things to optimize). This is the current state of the application but it is still far from complete however a lot of quite difficult technical challenges have been resolved and true development and polishing can now start.

Next steps are cleaning up and refactor a lot of code, integrate useful parts of previous attempt (LibreOffice4Android), tune tile loading and invalidation (when to load or remove which tile), making parts asynchronous to reduce blocking and improve the user experience, text selection and copy/paste, ...

I am really excited with what we have achieved and really looking forward to see where we go from here. By the time of LibreOffice 4.4 we should have a working and polished document viewer application ready. Thanks again to Smoose for funding for the work on this important step!

 Tomaž



by Tomaž Vajngerl (noreply@blogger.com) at September 03, 2014 02:18 PM

Caolán McNamara

aarch64 libreoffice


Thanks to Stephen Bergmann of Red Hat, Inc. LibreOffice is now ported to aarch64. No new ports for years, and then two 64bit ports landed within a week of aarch64 and ppc64le.

by Caolán McNamara (noreply@blogger.com) at September 03, 2014 07:24 AM

September 02, 2014

User Prompt

Understanding Icons: Participate in high contrast survey #8

In this icon test we take a look at a high contrast set. Please, again, participate and help us to learn more about the usability of icon design.

Please participate in our little game! (survey closed)

It is fun, takes a maximum of 5 minutes and helps us to better understand effects of icon design.

For more information please check our initial post on the idea and background of this series of small icon tests.

by Björn Balazs at September 02, 2014 09:00 AM

September 01, 2014

Charles Schulz

On my way to the LiboCon 2014!

I am on my way to the LibreOffice Conference 2014 today and I’m travelling by train all the way to Bern in Switzerland. There are many, many interesting talks this year, and I cannot resist to remind you of the two talks I’ll be giving, even though Italo and I will also be on the deck for a few talks about LibreOffice marketing especially on Wednesday.LibOCon_2014Bern_cross_88

My first talk will be on Thursday at 9h30 in the morning and will be about promoting LibreOffice in your language. I hope it will be a good opportunity to share ideas about this crucial topic for a project like LibreOffice as well. At 16h30 the same day, we will have our now traditional Marketing Strategy Workshop, on which I will report extensively on this blog later in September.

Last but not least, LibreOffice Conferences are always a few exciting days each year when everyone can meet in person, so these days are charged with emotions, things get decided and done sometimes on the spot, and it’s truly exhilarating . I’m looking forward meeting all of you in Bern and will keep our absent ones in mind.

Cheers!

 

by Charles at September 01, 2014 06:00 AM

August 30, 2014

User Prompt

Understanding Icons: Participate in survey ’7 of 9′ (or more)

With this next icon test we take a look at the Elementary icon set. Please, again, participate and help us to learn more about the usability of icon design.

Please participate in our little game! (Study closed)

It is fun, takes a maximum of 5 minutes and helps us to better understand effects of icon design.

For more information please check our initial post on the idea and background of this series of small icon tests.

by Björn Balazs at August 30, 2014 07:09 PM

August 29, 2014

User Prompt

Intermediate results of the icon tests: Tango

With a series of icon tests we currently study effects on the usability of icon design. This article however does not focus on these general design effects but presents findings specific to the Tango icon set.

Introduction

The introduction of the new Breeze icon set in KDE let us again wonder, what aspects of an icon set actually takes what impact on the usability of it. We investigated Oxygen and Tango Icons for the LibreOffice project before, but our focus then was on checking all icons of the standard tool bar. This time we focus on different icon sets and will use 13 common actions to compare them.

With this series we are going to test at least 10 different free icon sets: Breeze, Oxygen, Tango, Faenza, Nuvola, Nitrux, Elementary, Crystal Project, Humanity and Treepata. These icon sets differ on various aspects: use of color and details, flat or not and sometimes even on the metaphor used.

So, we generally want to analyze effects of icon design on the overall performance of an icon set. Statistics on this issue can obviously only be done after all icon sets have been tested. But with every test, we win some specific insights in strengths and weaknesses of each icon set tested.

In this post we share some findings about the Tango icon set.

The study was finished by 531 participants (drop-out rate 3%) with an average handling time of 2:08 min.

Results of Tango icons

Table 1 lists the aggregated quality indicators. They show how well all icons that we used for the test were suited to symbolize the different terms. It has a range from 1 (no fit) to 10 (perfect fit), whereas you would expect values of at least 9 for well represented terms.

Table 1: Quality of the icon set for different terms based on assignment ratio (percentage of missing assignments) and conspicuity (or speed of picking icons).
Term
Quality Indicator
Remove9.5
Save9.5
Print9.5
Paste9.5
Link9.5
Add10
New10
Open10
Search10
Copy10
Cut10
Redo10
Undo10

Table 2 shows a cross-table with the percentage of false associations. These are terms where the intended icon was not chosen by the users, but some other icon was.

Table 2: Cross-table of icons and terms with percentage of false associations. The direct match is inverted (1-value, e.g. 0.99 for Add) to obtain comparable data.

Results_Icontest-Tango 

Discussion

Tango gets the best results in this series so far. There is no icon that does not work well. Tango uses the standard metaphors for Copy and Paste. As we have found these metaphors to be not working well before, it is not surprising that these icons perform comparably bad. We also find the normal mix-up between Undo and Redo.

A couple of things are surprising though. First, Tango chooses a non-floppy-disc metaphor for Save. And it is working really well – but not quite as good as the floppy disc in other tests.

Also the Printer icon is working slightly worse than in other tests. When comparing the picture with those from other icon sets, the Tango printer has no paper feeder on top. Perhaps this paper feeder is an important part of our mental prototype of a printer (even though they often look different today). But it definitely makes the icon more unique.

If you know how to design icons and would like to help us to identify metaphors that work better, please contact us. Also, all raw results are publicly available on our open usability platform UserWeave.

As mentioned before: These results only reflect the internal quality of the Tango icon set. The final interpretation will be done after all sets have been tested. So stay tuned and please participate in our follow-up tests. And, of course, feel free to discuss these findings with us.

by Björn Balazs at August 29, 2014 09:37 AM

August 28, 2014

Jean Hollis Weber

LibreOffice 4.2 Impress Guide Published

Impress 4.2 Guide front coverThe Documentation Team has published the LibreOffice 4.2 Impress Guide, covering the presentations (slide shows) component.

Free PDFs of individual chapters and the full book can be downloaded from The Document Foundation’s wiki.

Printed copies can be purchased here. (Published by Friends of OpenDocument Inc.)

by Jean at August 28, 2014 10:30 PM

LibreOffice Documentation

LibreOffice 4.2 Impress Guide Published

The Documentation Team has published the LibreOffice 4.2 Impress Guide, covering the presentations (slide shows) component. Free PDFs of individual chapters and the full book can be downloaded from The Document Foundation’s wiki. Printed copies can be purchased here. (Published by Friends of OpenDocument Inc.)

by Jean at August 28, 2014 10:22 PM

Charles Schulz

Emacs & the obsessive email mongerer

I had already mentioned in passing here that I am using Emacs for a variety of tasks: outline, project management and planning with Org-Mode, IRC (go figure, my default email client on all my machines is Emacs’ ERC), notes editing or quick scribbling with the Scartch buffer (happens to me all day long), and regularly, albeit less frequently than in 2013, various editing of html pages, javascript and sometimes even Python when I dare to edit one or two things in Python scripts. A consequence of all these use cases is that I have Emacs open almost everyday on almost any of my machines. While most of my “training” aims at perfecting my use of org-mode, I have slowly become interested in the various email components of Emacs. This is where my insistence on choosing the perfect (graphical) email client in the past comes back kicking. To be sure, I am not ready to dump my beloved Claws Mail just yet, and I may just as well never go for a non-graphical client. However, I took this vacation time to configure my Emacs with one of my email accounts and give it a shot, and I’ve spent two weeks with it now.

1. Some explanations in the background

I won’t make this overly technical, but it is important to first state that Emacs does not come with one or several email clients: rather, it uses a set of different software components to process email, some of them being part of Emacs and some others, working in conjunction with Emacs (such as SendMail, OfflineImap, etc.) running outside as completely standalone programs. Now, it is also important to state that I have not used nor tried every email “client” on Emacs, and I don’t think I will. However, I’m a taker for information on some of these, given that I have specific requirements that may be satisfied with a few of these. I’m listing the requirements below:
– multiple email accounts and mailboxes (that works for pretty much any choice available in Emacs)
– IMAP and POP (I can live without POP, but it would still be nice to have the POP support)
– encryption support with GPG
– MH or MailDir mailboxes: please no standard Unix mailbox (aka mbox). It may sound weird, but I have large inboxes and stuffing everything in more or less one file is an utter catastrophy. On top of this, mbox support is of different quality given the email clients I have used in the past: Thunderbird, Mozilla Mail, Apple Mail, etc. Basically I had horror stories with mbox and I’m not keen on living them again. These days all my mail is in MH folders.
– Active development/maintenance
– Speed (If I bash Thunderbird or Evolution for resources hogging and slow performance, I will do exactly the same with any Emacs email tool).
– something to handle html mail or in general mail sent by people who have no clue about email, such as regular people. I know html mail sucks, however I do know a lot of people who send this kind of annoyances, and believe me, there are many of them out there.
– Not critical at this stage, but good contacts managements, calendar integration and even org-mode are a big plus. Fortunately this is the case with almost every email components in Emacs, except perhaps for contacts management.
– I know Mutt. I have heard of Mutt. Perhaps one day I will actually choose Mutt, but right now I’m not considering Mutt. If you want to tell me to use Mutt, then please go read buzzfeed.com and leave me alone.

2. My choice

mu4e. Well I do know that I didn’t go for the two or three most obvious choices (RMail, Gnus, VM) and I’d like to explain a bit why. Part of my choice is based on the requirements listed above of course, but in one case it is also based on complexity. You see, I believe to be accurate if I write that based on my requirements, Gnus does entirely satisfy all of them. I have started to investigate Gnus, but the documentation makes it seem… very complex, and I’m not far from thinking that it looks more complex than it really is. However, I went for an easier option as a first attempt. RMail would also satisfy almost all of them (using the MailUtils package available on any Unix-like system), however it seems that RMail only uses the mbox (and earlier Babyl) mailbox format, so that is a no-go for me, unfortunately. VM and other tools, nmh, mh-e do not seem to be developed or even maintained anymore. I might be wrong. Any pointer on this approeciated.

mu4e (mu for Emacs) was my choice over a rather similar solution called Wanderlust, but it seems Wanderlust runs into many bugs and has a slow development now. Plus, the author of mu and mu4e makes a good case of his own project vs. Wanderlust.

3. The experience

The installation and setup of mu4e is actually rather straightforward. The “mu” package (mu4e is part of mu) is readily available directly from ArchLinux, and you mostly need to install a few other programs such as offlineimap to have your imap acess configured. That’s a small python script to configure, and we are talking about entering details such as the server URL, your username and password. Nothing (too) fancy. After this you need to read a rather clear set of documentation directly available on the author’s website -there are very useful blogs on the topic as well- but it amounts to pretty much the same kind of settings anyone would need to add or configure when configuring a graphical email client. Once this is done, both offlineimap and mu -not mu4e- need to run for the first time. Offlineimap fetches your mail via imap and mu itself indexes your email you just downloaded. Note that these two are executed outside of Emacs, in your regular terminal, although you may of course run your terminal inside, er… Emacs, by using the Term or the EShell modes. After that, you need to open Emacs, and call in mu4e within emacs (it won’t run anywhere else).

At this stage, it is perhaps important to state that you need a working knowledge of how to use Emacs. By this I mean that you must have the ability to know how to switch from one mode to another, the main keyboard shortcuts, etc. Let me stress however that I am not a developer and that I have learned this rather comfortably in just a few months. Learning how to use Emacs (and this would apply to Vim as well and many other software) really amounts to read the tutorial(s) and then practice what the tutorial explains. Now when you have done that and feel confident to install and use mu4e, you will find what I’ve described above rather easy and straightforward. Otherwise you may perhaps think that I’m talking gibberish. The first thing mu4e shows is a default buffer with shortcuts to the inbox, bookmarks and other commands. Any of these is accessible through keyboard shortcuts. Refresh your mail for instance is done by typing a capital “U” (Shift + u) accessing your inbox first means to jump (j) to your inbox (i). You are then presented with a rather standard list of your email. Shortcuts (arrows) will select an email, press Enter and the content of the email are displayed by default in the lower region of your buffer, but you could have them displayed in a completely separate buffer. Sending email is also straightforward (Shift + c). You only need to write the email address next to the coloured line with a “To:” and the same goes for “Subject:” and “cc:”. A small separation line points to the area where you can compose your actual email.mu4e

My first reaction was that it was not that much of a radical departure from the traditional graphical clients. Of course there is nothing fancy, no “tabbed interface”, etc. but nothing that does not make any sense either. I have not spent enough time playing with the various options available. For instance I am not sure I can ever get the vertical three pane view that I have on every one of my email clients. I might, but I just need to check what needs to be configured. I didn’t choose a large inbox, so obviously things went fast, although it is not like they felt faster than Claws Mail for instance. There is of course a bit of disorientation due to the new interface. Questions such as “where are my menus?” take a whole new meaning here. Yet so far, I’m not ready to make the jump.

Why?
I need to sort out whether specific options are available (such as the vertical three pane view) but there are others. Also, I probably need to give Gnus a more serious look. But more to the point, I feel that switching to any kind of email management (for the lack of a better term) in Emacs only makes sense if I’m enthralled by the capabilities of tools I could be using; so far I like what I see but I hadn’t had an epiphany yet; and more importantly, using Emacs to handle mail really makes sense if I’m using Emacs all day long for pretty much everything aside perhaps browsing. This, however, is clearly not the case for me. For instance I use LibreOffice for most of my documents handling, even if I take notes with Emacs. I create graphical presentations, and must often handle complex Word documents. I hear Emacs handle tables very well, but so far I’m not dabbling in this area, and LibreOffice Calc serves more than my needs. I use Claws, browse the web with a combination of browsers (Firefox, Chromium, Gnome Web, Midoru and even ReKonq) and I do all of these things outside of Emacs. I estimate my workload to be happening somewhere around 20% on Emacs in one way or another. This is not enough for me to move… yet. However I am impressed, I’m pleased by what I’ve experienced, and I learned a lot more on Emacs than I thought. That was worth all the trip but as far as email goes, I’ll stick to my Claws…

by Charles at August 28, 2014 07:26 PM

Miklos Vajna

Cleanup of ooxmltok in LibreOffice

(via aigle_dore)

In June, we decided to get rid of XSLT usage in writerfilter, the module responsible for RTF and DOCX import in LibreOffice. As usual with cleaning up mess, this took time (about two months), but I’m now happy to say that I’m mostly done with this. :-)

See the doctok blog post for some background, the topic here was to clean up the OOXML tokenizer, that is that building block that turns a zipped XML document into a token stream.

The following problems are now solved:

  • Part of the module was generated code, the generator was implemented mostly in XSLT, but some bits were written in Perl and sed. About 4200 lines of XSLT code is now rewritten in Python, in about 1300 lines.

  • Given that we have much more developers who speak Python, compared to XSLT, nontrivial changes are now much easier in the generator: Jan Holesovsky cleaned up boost::unordered_map usage at places where we depended on the order of elements. (Yes, you read it correctly, that was the situation up till now!) This also helps reducing the size of the resulting writerfilter shared library.

  • The input of the code generator was the large model.xml file, and generator scripts only extracted interesting information from it, so if you mistyped something, you got no error messages, just silent failures. I’ve removed quite some XML elements and attributes from it which were parsed by none of the generator scripts and written a relax-ng schema for the remaining markup. Validating against this schema is part of the default build, so no more typos without a build failure. ;-) (The schema also contains quite some documentation, finally.)

  • A gperf hash of all possible OOXML elements / attribute names were duplicated in writerfilter, even if that information was already available from the oox module. This is now fixed, reducing the size of the shared library even further.

  • Also, both oox and writerfilter had a list of namespace URL’s, mapping them to an integer enumeration, and when the two lists didn’t match, Bad Things happened (read: usually resulted in a crash.) This is the past, I’ve refactored writerfilter to use the same namespace alias names as oox, and this allowed to get rid of the writerfilter copy of the namespace alias list. So in the future, if new namespaces have to added, only oox has to be extended.

Oh and the bonus feature: I’ve implemented a script called watch-generated-code.sh, which can record a good state of the generated code, and then compare later generated results against that, so that refactoring of the generator can now be performed in a safe way: you can change the generator in any way to make it better, and still avoid accidental output changes. :-) This is particularly useful, as it only diffs the end result of the whole generation process (cxx and hxx files), not temporarily files, which are OK to change, as long as the end result is the same.

As a conclusion, here are sizes of a stripped dbgutil version of the writerfilter shared library, from the libreoffice-4-3-branch-point and today’s master:

$ git checkout oldest
HEAD is now at b3130c8... 2014-05-21
vmiklos@o9010:~/git/libreoffice/daily$ ls -lh opt/program/libwriterfilterlo.so
-rwxr-xr-x 1 vmiklos users 8,3M aug   28 14:00 opt/program/libwriterfilterlo.so
$ git checkout master
Switched to branch 'master'
vmiklos@o9010:~/git/libreoffice/daily$ ls -lh opt/program/libwriterfilterlo.so
-rwxr-xr-x 1 vmiklos users 6,1M aug   28 14:01 opt/program/libwriterfilterlo.so

Again, the 8,3MB → 6,1MB size reduction is mostly thanks to Kendy’s map cleanups + the duplicated gperf hash going away. :-)

August 28, 2014 12:04 PM

Official TDF Blog

LibreOffice 4.3.1 “Fresh” announced

The software on show next week at the LibreOffice Conference in Bern

Berlin, August 28, 2014 – The Document Foundation announces LibreOffice 4.3.1, the first minor release of LibreOffice 4.3 “fresh” family, with over 100 fixes (including patches for two CVEs, backported to LibreOffice 4.2.6-secfix, which is also available for download now).

All LibreOffice users are invited to update their installation as soon as possible to avoid security issues. This includes users who are running LibreOffice 4.2.6 as originally released on August, 5th 2014.

LibreOffice 4.3.1 and LibreOffice 4.2.6 will be shown on stage at the LibreOffice Conference in Bern, from September 3 to September 5, with a large number of sessions about development, community, marketing and migrations. The program of the event is available here: https://conference.libreoffice.org/2014/program.

In addition to the sessions in English, there will be a track in German focusing on open source adoptions in governments and enterprises in Switzerland, Germany and Austria: https://conference.libreoffice.org/2014/professional-user-track.

People interested in technical details about the release can access the change log here: https://wiki.documentfoundation.org/Releases/4.3.1/RC1 (fixed in RC1) and https://wiki.documentfoundation.org/Releases/4.3.1/RC2 (fixed in RC2).

CVEs patched in LibreOffice 4.3.1 and LibreOffice 4.2.6 are CVE-2014-3524 “CSV Command Injection and DDE formulas” and CVE-2014-3575 “Arbitrary File Disclosure using crafted OLE objects”.

Download LibreOffice

LibreOffice 4.3.1 and LibreOffice 4.2.6 are immediately available for download from the following link: http://www.libreoffice.org/download/.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at http://donate.libreoffice.org. Money collected will be used to grow the infrastructure, and support marketing activities to increase the awareness of the project, both at global and local level.

by italovignoli at August 28, 2014 10:06 AM

User Prompt

Understanding Icons: Participate in 6th survey ‘Take a breeze’

Our next icon test features the Breeze icon set, that might (or will?) become the default KDE icon set. Please, again, participate and help us to learn more about the usability of icon design.

Please participate in our little game! (Survey closed)

It is fun, takes a maximum of 5 minutes and helps us to better understand effects of icon design.

For more information please check our initial post on the idea and background of this series of small icon tests.

by Björn Balazs at August 28, 2014 08:35 AM

Florian Reisinger

SI GUI – Now with SDK + Naming

Hi all :)

So right before LibreOffice Conference I finished SI-GUI’s LibreOffice SDK support. You are now able to download the SDK and install it via the GUI.

Speaking of GUI, here it is:

sigui-4302

 

Another thing where I need your help is the following:

<figure class="wp-caption alignleft" id="attachment_1014" style="width: 64px;">Current icon<figcaption class="wp-caption-text">Current icon</figcaption></figure>

The name was always bad and it is time to find a better one, although this will break some links…. And with a name, we need 1 icon (I attached the current). So if you have an idea and an icon, that would be perfect. [This icon is available in 256x256,128x128,48x48,32x32,16x16]

I am happily looking forward to hear your ideas. Enjoy SI-GUI :)

BTW: Tell me if you are using it and whether you like it or not :)


Tagged: C#, coding, LibreOffice, SDK, Server Installation GUI

by Florian Reisinger at August 28, 2014 07:40 AM

August 27, 2014

Jacobo Aragunde Pérez

Speaking in the next LibreOffice conference

I’m happy to announce that I will be taking part in the 2014 edition of LibreOffice Conference as a speaker. I’ll overview the status of accessibility in our favorite productivity suite, starting with an introduction to accessibility support and how application are supposed to implement it, we will check the particular case of LibreOffice: which accessibility backends are implemented and how the architecture is designed to support multiple backends while maximizing code reuse.

The conference program looks hot too, and this time I’m particularly interested on hearing from the success cases that will be presented there, looking for ideas and lessons to apply to new deployments.

Igalia is one of the sponsors of the conference, taking our compromise with LibreOffice project a step further. The company will also be sponsoring my flight and stay in Bern.

Last but not least, it will be great to meet the community members again, and get to know those I haven’t met yet in previous conferences or hackfests. Looking forward to seeing you at Bern!

Igalia & LibreOffice

by Jacobo Aragunde Pérez at August 27, 2014 10:00 AM

Florian Reisinger

SI-GUI hotfix release

This is a hotfix release for the 4.3 has a problem saving your settings. What cannot be done in this version:

  • Abort downloads 
  • Guess the name for shortcuts [You have to enter/ copy paste it manually]

Please do NOT report those. I try to fix them tomorrow!

I am sorry for the inconveniences! But with this build you should be able to continue doing an awesome job!

PS: As you see in this build, SDK integration in SI-GUI is on its way ;)


Tagged: hotfix, Server Installation GUI

by Florian Reisinger at August 27, 2014 09:19 AM

August 25, 2014

Eike Rathke

Happy Birthday, Linux!

23 (!) years ago Linus Torvalds wrote a message to the comp.os.minix newsgroup (does anyone remember newsgroups?) in which he announced that he was doing a free operating system (just a hobby, won't be big and professional like gnu) LOL and he liked to know what features most people would want.

He failed in predicting the future though:
It is NOT protable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(

Well done, Linus, and Happy Birthday, Linux! Live long and prosper, both!


by erAck at August 25, 2014 12:22 PM

August 23, 2014

Eike Rathke

Seilbahn? Echt? Nee, lass man..

Ich darf ja selbst als Hamburger nicht abstimmen, das hat der Senat gefickt eingeschädelt als er die Sache an den Bezirk übergeben hat. Aber ich hoffe innigst, dass wenigstens die sogenannten Betroffenen sich nicht von bunten Broschüren, Voraus-Freikarten, Spenden-Versprechen und ähnlichem haben einkaufen lassen und bis morgen beim Bürgerentscheid ihre Entscheidung eindeutig gegen die Seilbahn abgeben.

Der Stern hat die Sache ganz gut auf den Punkt gebracht: Seilbahn in Hamburg: Geschenkt ist noch zu teuer

Lasst euch nicht verarschen!


by erAck at August 23, 2014 02:13 PM