New items in our merchandise shop

As you may know, The Document Foundation has a merchandise shop with clothing, accessories, phone/tablet covers and various other items. Many of the designs feature the LibreOffice logo on its own, but we thought we’d update the shop with some items that highlight the benefits of LibreOffice.

But given limited space, what benefit should really stand out? After discussing this in our marketing community (join in and get involved!), we settled on this: LibreOffice puts you in control. Because it’s free, open source, multi-platform and built on open standards, it gives end users complete control over their documents and data.

So we’ve added four new items to the shop:

T-shirts for men and women, plus a cool new mug and a mousemat as well. If you love LibreOffice, want to help spread the word and support The Document Foundation, head over to the shop and place your order! If these designs are popular, we may add more items as well — stay tuned…

LibreOffice Migration Workshop in Tirana

I have spent the last weekend in Tirana, the capital city of Albania, with a group of young members of the local LibreOffice/FLOSS community – Anxhelo Lushka, Augest Dalliu, Greta Doci, Jona Azizaj, Kristi Progri, Mariana Balla, Marinela Gogo, Redon Skikuli, Sidorela Uku, Silva Arapi and Suela Palushi – for a LibreOffice Migration Workshop.

As everyone can see from the picture, the LibreOffice/FLOSS community in Albania is different from any other open source community, as it has a large majority of women: in fact, the workshop was attended by seven women – Greta, Jona, Kristi, Mariana, Marinela, Sidorela, Silva and Suela (plus another two or three for a few hours) – and three men: Anxhelo, Augest and Redon.

We have planned the workshop at the end of OSCAL, the local FLOSS conference I have attended in mid-May, after a meeting with several representatives of the city of Tirana – organised by Redon Skikuli, and attended by Anxhelo Lushka, Jona Azizaj and me – during which the authorities have expressed their interest in LibreOffice.

During the two days of the workshop, we have covered a large number of topics, from the history of LibreOffice – including development, and activities focused on improving quality and reliability of the software such as Coverity Scan and OSS-Fuzz – to the Migration Protocol and the Training Protocol.

We have gone through every step of the Migration Protocol and we have focused on the different activities included in the analysis, as during the upcoming months the local team will support the city of Tirana for this stage of the project, to help understand the challenges of the migration to LibreOffice.

Last, but not least, I have presented – for the first time – the new slide deck explaining the advantages of ODF vs OOXML to end users, based on the extensive research on the subject I have done during the last six months.

All slide decks will be uploaded to TDF wiki during the next weeks (https://wiki.documentfoundation.org/Gallery_Presentations).

 

LibOCon 2017 Call for Papers

The Document Foundation invites members and volunteers to submit proposals for papers for the conference in Roma. Whether you are a seasoned presenter or have never stood up in public before, if you have something interesting to share about LibreOffice, we want to hear from you!

Proposals should be filed by August 15th, 2017 in order to guarantee that they will be considered for inclusion in the conference program.

The conference program will be based on the following tracks:

a) Development, APIs, Extensions, Future Technology
b) Quality Assurance
c) Localisation, Documentation and Native Language Projects
d) Appealing Libreoffice: Ease of Use, Design and Accessibility
e) Open Document Format, Document Liberation and Interoperability
f) Advocating LibreOffice

Business track:
– Enterprise Deployments and Migrations, Certifications and Best Practices, Building a successful business around LibreOffice.
– Round table with company representatives
– Small local businesses, governments and non-profits, to be conducted in Italian language

Presentations, case studies, workshops, and technical talks will discuss a subject in depth, and will last 30 minutes (including Q&A). Lightning talks will cover a specific topic and will last 5 minutes (including Q&A). Sessions will be streamed live and recorded for download.

Please send a short description/bio of yourself as well as your talk/workshop proposal to the program committee address: conference@libreoffice.org

If you do not agree to provide the data for the talk under the “Creative Commons Attribution-Share Alike 4.0 License”, please explicitly state your terms. In order to make your presentation available on the TDF YouTube channel, please do not submit talks containing copyrighted material (music, pictures, etc.).

If you want to give multiple talks, please send a separate email for each.

LibreOffice contributor interview: Daniel A. Rodriguez

Having concluded our video interviews from FOSDEM, we now return to our regular LibreOffice contributor interviews on the blog. Today we talk to Daniel A. Rodriguez, an Argentinian LibreOffice and Free Software supporter, who helps with marketing, translations and design.

Where do you live, and are you active on social media?

I live in Posadas, the capital of Misiones in the north-east of Argentina. Here’s my Google+ profile.

Do you work for a LibreOffice-related company or just contribute in your spare time?

I use my spare time to contribute.

How did you get involved with LibreOffice?

When the LibreOffice project started (as a continuation of OpenOffice.org) I was still quite a new GNU/Linux user, but wanted to return something to the global community which had helped me many times before. So, I subscribed to mailing lists and – I don’t remember exactly how – in January 2011 I started to translate the LibreOffice website into Spanish.

What areas of the project do you normally work on? Anything else you want to tackle?

I try to stay tuned to marketing, translating press releases, design blog posts and developer blog posts. I maintain several social media profiles as “Comunidad LibreOffice Argentina”:

All of these can, I think, help to attract volunteers to the project. But we must recognize that the Spanish community is fragmented into several geographical regions. And that’s why at the end of 2016, with help from two
other community member (Adolfo Jaime Barrientos and Carlos Parra Saldivar), we started a new blog at The Document Foundation. Now it has another well known LibreOffice user and advocate: Ricardo Berlasso. The goal is to get more people participating, now and then.

Sometimes I work on ideas that others can bring into reality – such as the airport advertisement for the launch of LibreOffice 4.0, or more recently the MUFFIN illustration for the blog post in December.

What was your initial experience of contributing to LibreOffice?

Being able to participate actively in an international community, with the push and motivation that revolves around LibreOffice and Free Software, was – and still is – indescribable.

What does LibreOffice need most right now?

I think that an option for automatic updates, like Firefox has for example, would be great.

Finally, what do you do when you’re not contributing to LibreOffice?

I work the whole day in a secondary school with a technical orientation. My obligations are to maintain the infrastructure on which different systems work: institutional management, Virtual Education Environment, proxy cache, DNS, among others.

Thanks Daniel! And thanks to everyone else involved in marketing and localisation of LibreOffice. If you’re reading this and want to join the friendly, worldwide LibreOffice community, get involved!

LibreOffice Quality Assurance: six months in statistics (part 2)

This is the second part in our blog series about the LibreOffice QA (quality assurance) community – see here for the first part.

Regressions

During the six month period from 23 November 2016 to 21 May 2017, 553 bugs were identified as regressions by 61 people. This means a feature behaved correctly in the past – but a change in the code made it work incorrectly. This is an expected problem in any software project, especially when many changes to the code are done every day. For that reason it’s very important to determine whether a bug is a regression or not – and to identify regressions as soon as possible to maintain the quality of the software.

It’s also important to mention the tremendous amount of effort developers spend on adding new unit tests in order to avoid regressions from being introduced again. More information about that here.

Top 15 regression identifiers:

  1. Xisco FaulĂ­ (190)
  2. Buovjaga (81)
  3. Telesto (50)
  4. Áron Budea (35)
  5. Alex Thurgood (32)
  6. Justin L (11)
  7. Cor Nouws (11)
  8. tommy27 (11)
  9. Julien Nabet (9)
  10. Yousuf Philips (jay) (9)
  11. m.a.riosv (9)
  12. V Stuart Foote (7)
  13. Kevin Suo (6)
  14. Luke (6)
  15. Jacques Guilleron (6)

These are the statuses of the bugs identified as regressions:

More than half of these bugs have been RESOLVED (243), or resolved and VERIFIED (57) – 54.2% to be exact.

Bisected

Once we identify that a bug is a regression, we can use a tool called bibisect to identify at which point the regression was introduced, allowing us to speed up the process of fixing the bug.

During the last 6 months, 346 bugs have been bisected by 14 people.

Top 14 ‘bisecters’:

  1. Xisco FaulĂ­ (186)
  2. Áron Budea (77)
  3. raal (50)
  4. Justin L (10)
  5. Terrence Enger (6)
  6. Michael Stahl (4)
  7. Mike Kaganski (4)
  8. Miklos Vajna (3)
  9. Buovjaga (1)
  10. Kevin Suo (1)
  11. Luke (1)
  12. Jean-Baptiste Faure (1)
  13. CaolĂĄn McNamara (1)
  14. Katarina Behrens (1)

And these are the statuses of the bugs bisected:

Of the bisected bugs, 55.7% are either RESOLVED (148), or resolved and VERIFIED (45).

Backtraces

Another way to accelerate the fixing process is by providing a debug trace when there’s a crash, slowness or a freeze in the software.

During the last 6 months, a debug trace has been added to 140 bugs by 14 people.

Top 13 debug trace providers:

  1. Julien Nabet (48)
  2. Xisco FaulĂ­ (35)
  3. Buovjaga (28)
  4. fiftyigfuci_f_mi (10)
  5. Alex Thurgood (6)
  6. V Stuart Foote (4)
  7. Áron Budea (4)
  8. Telesto (3)
  9. Terrence Enger (3)
  10. Yousuf Philips (jay) (2)
  11. JoNi (2)
  12. Kevin Suo (1)
  13. Cor Nouws (1)

These are the statuses of the bugs with a debug trace:

More than two-thirds of these bugs have been RESOLVED (74), or resolved and VERIFIED (22) – 69.4% to be exact.

Duplicate bugs

Knowing that many bugs are reported everyday, it’s important to identify if a certain bug was reported previously and therefore whether it’s a duplicate or has never been reported before.
During the last six months, 757 bugs have been identified as duplicates by 91 people.

Top 20 duplicate identifiers:

  1. Xisco FaulĂ­ (142)
  2. Buovjaga (116)
  3. V Stuart Foote (79)
  4. Áron Budea (40)
  5. Telesto (31)
  6. Alex Thurgood (28)
  7. m.a.riosv (27)
  8. Julien Nabet (26)
  9. Heiko Tietze (20)
  10. Timur (19)
  11. Khaled Hosny (18)
  12. Yousuf Philips (jay) (15)
  13. Maxim Monastirsky (14)
  14. Adolfo Jayme (13)
  15. GĂĄbor Kelemen (11)
  16. Mike Kaganski (10)
  17. Cor Nouws (10)
  18. Jacques Guilleron (8)
  19. Bartosz (8)
  20. Regina Henschel (6)

Resolved bugs

The cornerstone of the project is its development work. During the six month period, 955 bugs were set to RESOLVED FIXED by 147 people.

Top 20 fixers:

  1. CaolĂĄn McNamara (73)
  2. Miklos Vajna (53)
  3. Eike Rathke (41)
  4. Michael Stahl (39)
  5. Julien Nabet (38)
  6. Justin L (36)
  7. Adolfo Jayme (33)
  8. Heiko Tietze (29)
  9. Samuel Mehrbrodt (29)
  10. Xisco FaulĂ­ (26)
  11. GĂĄbor Kelemen (25)
  12. Yousuf Philips (jay) (23)
  13. Maxim Monastirsky (22)
  14. Markus Mohrhard (22)
  15. V Stuart Foote (19)
  16. Zolnai TamĂĄs (18)
  17. Mike Kaganski (18)
  18. Katarina Behrens (17)
  19. Khaled Hosny (16)
  20. Winfried Donkers (15)

Verified fixed bugs

Finally, once a bug has been fixed, it’s important to verify that it has indeed been fixed.

During the last six months, 212 fixes have been verified by 28 people.

Top 15 verifiers:

  1. Justin L (65)
  2. Xisco FaulĂ­ (24)
  3. Buovjaga (18)
  4. Timur (16)
  5. m.a.riosv (11)
  6. Julien Nabet (9)
  7. Heiko Tietze (7)
  8. Terrence Enger (7)
  9. Jean-Baptiste Faure (7)
  10. Thomas Lendo (6)
  11. Áron Budea (6)
  12. raal (4)
  13. Yousuf Philips (jay) (4)
  14. Cor Nouws (4)
  15. V Stuart Foote (3)
  16. Kevin Suo (3)
  17. Luke (3)
  18. Jacques Guilleron (3)
  19. Zineta (2)
  20. Alex Arnaud (2)

Get Involved!

So, you’ve seen what the QA team is doing across the LibreOffice project – why not get involved and help out? Even if you only have half an hour of spare time each week, by confirming bugs (and fixes) you can make LibreOffice better for millions of people around the world. And in addition, you build up valuable experience working with a large project and open source community – which could be very useful for a future career! Discover more about the QA team in our video interview with QA engineer Xisco Fauli.

(Notes about this blog post: raw data can be checked here. For more stats, visit the stats page in the QA wiki.)

Design with LibreOffice: Styles and Templates

Friends of OpenDocument has just released another excerpt from Bruce Byfield’s book Designing with LibreOffice, called Styles and Templates.

Styles and Templates contain most of the information on the subject included in Designing with LibreOffice, with some alterations in structure and edits for continuity. It is intended for those who want information on LibreOffice styles and templates but would prefer not to have the complete book.

Both publications are released under the Creative Commons Attribution ShareAlike license, and are available for download from http://www.designingwithlibreoffice.com. The page also contains a link for buying hardcopy versions of both books.

The Document Foundation All Rights Reserved 2025
Proudly powered by WordPress | Theme: Refined Magazine Pro by Candid Themes.