Home » Documentation » Page 22

Category: Documentation

FOSDEM Call for Papers: Open Document Editors DevRoom

fosdemFOSDEM is one of the largest gatherings of Free Software contributors in the world and happens each year in Brussels (Belgium) at the ULB Campus Solbosch. In 2017, it will be held on Saturday, February 4, and Sunday, February 5.

As usual, the Open Document Editors DevRoom will be jointly organized by Apache OpenOffice and LibreOffice, on Saturday, February 4, in room 4.401 in Building K (from 10:30AM to 6:30PM). The shared devroom gives every project in this area a chance to present ODF related developments and innovations.

We are now inviting proposals for talks about Open Document Editors or the ODF document format, on topics such as code, extensions, localization, QA, UX, tools and adoption related cases. This is a unique opportunity to show new ideas and developments to a wide technical audience.

Length of talks should be limited to a maximum of 30 minutes, as we would like to have questions after each presentation, and to fit as many presenters as possible in the schedule. Exceptions must be explicitly requested and justified. You may be assigned LESS time than you request.

All submissions have to be made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM17.

While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored at Pentabarf).

To submit your talk, click on “Create Event”, then make sure to select the “Open Document Editors” devroom as the “Track”. Otherwise, your talk will not be even considered for any devroom at all.

If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please contact ode-devroom-manager@fosdem.org.

The deadline is Monday, December 5th, 2016. Accepted speakers will be notified by Sunday, December 11th, 2016. The DevRoom schedule will be published on the same day.

Recording Permission

The talks in the Open Document Editors DevRoom will be audio and video recorded, and possibly streamed live too.

In the “Submission notes” field, please indicate that you agree that your presentation will be licensed under the CC-BY-SA-4.0 or CC-BY-4.0 license and that you agree to have your presentation recorded. For example: “If my speech is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, Name”.

LibreOffice Community Weeks: Wrapping up

LibreOffice Community Weeks

We’re already in to a new Month of LibreOffice, but in October we ran a series of Community Weeks, looking at what different teams in the LibreOffice project do, and how you can help them. So firstly, here’s a reminder of the articles, and then we’ll find out what effect they had…

Documentation

Development

Quality Assurance (QA)

Design

 

Feedback from the teams

So what effect did the Community Weeks have on the projects? Here’s what each team had to say:

Olivier Hallot (documentation): “The Community Weeks brought more people to the realm we are working in, and I had 3 new people showing up. One is a PhD professor from a university in India, who wrote a page on a set of Calc functions, and asked for more work. Another is a New Zealand national, involved in migrations and support, who is updating our books. I also got someone on IRC, but he did not came back. So overall, the week is positive, but we need people to return after their first contributions.”

Jan Iversen (development): “The week worked well – during the last period 15 people have got their first patch merged, and will appear by name in the 5.4 release notes. I often hear “but I cannot work full-time”, so it is important to realize that while roughly 50% of the changes are done by 20-30 people, the other 50% is done by hundreds of people making 1-10 patches a year. Every change counts and is very welcome! We arrange developers days, when a group wants help, so please contact us at mentor@documentfoundation.org if you need help.”

Xisco Fauli (QA): “There were 4-5 new users who showed up on IRC during the Bug Hunting Session, who may have joined from reading the Community Week posts. Also, we hope both posts from that week will help readers to report better bugs in the future (attaching simpler samples, adding clearer steps, and so forth).”

Heiko Tietze (design): “The campaign was interesting and encouraged readers to follow links to the Design Team Blog. Even if we didn’t get more active people showing up in the design project, comments are always welcome.”

Thanks to everyone who took part. We’ll do more Community Weeks next year, so if there’s something you want us to focus on, just let us know!

Community Week: Documentation – who’s who, the tools used, and how to get involved

Earlier in the week we talked to Olivier Hallot who’s heading up the documentation team in LibreOffice. But other people are contributing as well, so if you want to help out, here are some names to look out for:

  • Jean Weber is the author and original producer of the LibreOffice guides
  • Stan Horacek, Gabor Kelemen, Adolfo Jaime Barrientos and others are contributors to the help contents
  • Dennis Roczek and Lera Goncharuk work mostly on the wiki
  • Andrea Mussap just joined and under Olivier’s advice produced a help page for LibreOffice

The team communicates via the documentation mailing list (see the archives here), where you can post suggestions for updates or ask for areas that need help. Another alternative is to use the IRC channel (#libreoffice-doc on Freenode), which is better for more immediate discussion – but can be quiet at times, if it’s night-time where many of the participants are based.

Tools of the trade

LibreOffice’s documentation content is split into two main categories: online help, and the guidebooks. They are both fundamentally important to the office suite, but differ in the style of content and who it’s aimed at.

The user guides are available on the LibreOffice website, in ODT (for Writer) and PDF formats, and printed copies can be bought as well. You can see that the Getting Started guide for LibreOffice 5.x is the most up-to-date – so a good way to help out is to edit the other guides (eg for Writer and Calc) to bring them in line with the LibreOffice 5.x series as well.

In addition, there’s the help that’s built in to LibreOffice (usually accessible by pressing F1). Unlike the user guides, which provide detailed explanations of how to do tasks in LibreOffice, the built-in help focuses on answering questions about specific features. This is usually the first resource that users of the software consult if they have a problem, before looking in the user guides or searching the internet.

A list of frequently asked questions (FAQ) is available on the wiki, but some of the answers are dated. A better resource is the Ask LibreOffice site which lets people post and answer questions.

Get involved!

So you’ve seen what the documentation project does, who’s in the team, and what they’re working on. Why not help out yourself? If you’re interested in a career in technical writing, this is a great way to build up some experience. Or if you’re already familiar with such work, you can really make a difference to a major free and open source software project!

Getting started is easy:

  • Send a blank email to documentation+subscribe@global.libreoffice.org and follow the instructions to sign up to the mailing list
  • Introduce yourself – you don’t need to include a CV, but just provide a few lines of who you are and how you want to help
  • Someone on the docs team will answer and help you out

For newcomers, there is a meta bug in bugzilla bringing together various “easy hacks” – small tasks that you can do easily without much experience or long-term committment. Even the smallest fixes and tweaks can make all the difference.

Then there is the ODFAuthors site which has information on producing LibreOffice user guides, and is where a lot of the writing work takes place.

So that’s a summary of how the documentation project works, and we hope you will join us on the team soon! Drop by our IRC channel at any time for a chat:

LibreOffice Community Week: Documentation

LibreOffice Community Weeks

The LibreOffice project is made up of many communities working on different aspects of the software: source code, documentation, quality assurance, design and other matters. Some people are working full time, many others are volunteers, and we always try to make new contributors feel welcome.

So throughout October we’ll be running LibreOffice Community Weeks, looking at the different sub-projects in LibreOffice, what they do, and how to get involved. We start off this week by looking at the documentation project, and chat to Olivier Hallot, who is leading the effort to improve LibreOffice’s guide books and online help…

Olivier HallotWhat is your role in the documentation project?

My role in the documentation project is to elaborate plans, coordinate and increase the collaboration of the community and improve the contents of the documentation of LibreOffice.

How did you get involved in LibreOffice?

I am involved in LibreOffice since its beginning, and even before during the OpenOffice.org times in 2001. In the last decade I had an active position in the Brazilian community as member of the BrOffice NGO, and also because I coordinated and translated OpenOffice.org’s User Interface and Help Content to Brazilian Portuguese, a task I carry on to date with LibreOffice. I also took job on OpenOffice.org migration consulting in very large companies in Brazil and later I participated in the creation of The Document Foundation (TDF) in 2010, being member of its Board of Directors from 2010 to early 2014.

Having an experience in the corporate arena, I was concerned that gap between the documentation and Help Content of LibreOffice with respect to its features was dangerously growing, and that has to be reverted so the software and its collateral documentation has to go ideally hand on hand. On presenting the issue in our LibOConf in Aarhus (Quo Vadis HelpContent?), TDF understood that it was necessary to take action and here I am.

What does your typical workday look like?

Since I live in Rio de Janeiro, Brazil, I must admit that when I wake up, people in Europe are already working full steam ahead and I have a feeling that I am always late and sleepy (laugh) in the job. Anyway, usually I check my mails just after my breakfast, and I get ready for the online meetings that for me are in the morning.

Then with the list of task from the meetings, which I cross-check with the off-line mails, I start at least one task to get it done in the day. That includes support in chats, answering e-mails in lists and off-list, and also updating a document, a wiki page or a web page.

You see, writing documentation on LibreOffice is a task that requires several hours or days of concentration and we must be focused all the time. To be able to write or review a specific feature, you must test the feature in your installation, understand the implication of the feature and even add some of your personal knowledge to give the reader a quality text and content.

How many people are involved in the doc project?

The doc project has two main lines: The literature and the Help content. The Help content is itself divided into contents and technology modernization.

On the literature, we are about three to five people contributing once in a while and this is an exposure. We need to update our books in timely fashion because they are considered as the official TDF books for LibreOffice and are translated into several languages. Since the license is Creative Commons, these books are also sources for other books on LibreOffice in many languages and communities.

On the help content, we have the valuable contribution of many individuals (from 10 to 20 persons), from translators to developers that help us to correct the contents and adjust the help pages to the new features and UI changes. The accuracy of the help pages is also an exposure we carry and our task is to close the gap. It must be noted that the correct description of a new feature is important for legacy purposes: if later on in the LibreOffice project, the feature does not work anymore, we still have a description of its existence and normal behavior.

Finally we consider that the current Help system, which is based on XML files transformed into HTML3.2 pages displayed as Writer/web documents can evolve to a modern browser-based technology. There are some tech issues yet to solve, especially because the Help system translation process is consolidated, works satisfactorily and its content must be preserved.

What’s been the biggest success so far, and the biggest challenge?

We updated the Getting Started Book to version 5.1 of LibreOffice, and we managed to put the help pages directly into a web server, at least as proof of concept, showing that we can evolve and achieve a better, richer help content.

My personal challenge is to produce the TDF LibreOffice Guides as a genuine companion product of the software, where the LibreOffice brand provides not only the software but also the collateral products for those migration or training professionals that support the deployment of LibreOffice in organizations.

I also pretend to close the distance between the user and the documentation. The usual way for the user is to hit F1 to get help but if the help is not enough, users go to Google and try a search for contents he is looking for. This is a time consuming task and we have already put entries in the software Help menu to link the software to the documentation website and to community forums. We expect an increase of visits to these services in benefit for our installed base.

But then the challenge is to get more contributors to help with documentation of LibreOffice, in all areas above. Authoring, reviewing and updating a book is a task that can be carried by non-developers, provided they have good knowledge in the software as advance user and have time do dedicate to the LibreOffice literature. The same is for the local communities if they want to translate LibreOffice books.

On the technology of the Help, the challenge is to select a viable technology to replace the current Help system.

What sort of help are you looking for?

We look for more contributors, people that can write, review, advanced contents on LibreOffice. It is important that we see the TDF LibeOffice Guides as a genuine companion product of the sofware, where TDF provides not only the software but also the collateral products for those professionals that support the deployment of LibreOffice in organizations.

Stay tuned to the blog for more about the documentation team this week – including a list of who’s who in the project, the tools being used, and how to get involved yourself! See here for more information on the docs team.

Getting Started with LibreOffice 5.1, a new book from the community addresses the demand for updated documentation on the software

GS51-GettingStartedLOThe new manual supports the large number of organizations and individuals deploying LibreOffice “Still” 5.1 to get superior quality and stability

Berlin, August 16, 2016 – Volunteers active in LibreOffice Documentation Project within The Document Foundation announce the availability of the Getting Started Guide for LibreOffice 5.1. The book updates the traditional introductory text with the new features provided by the “still” version of the software, targeted to enterprise deployments and to individual users looking for superior quality and stability.

Updated by members of the community, the book is an effort to fill the gap in official documentation for LibreOffice. The Document Foundation is working hard to reduce the delay between the release of the software and its companion documentation, for a better user experience and a stronger competitive offering.

“Many communities consider the Getting Started Guide as a source for translation into their native language, to create localized textbooks for teaching LibreOffice in all environments, from academia to the enterprise,” says Olivier Hallot, documentation coordinator at TDF. “A timely release of these books will send a strong message about the commitment of the community for professional collaterals.”

“In addition to the free downloads of the book in PDF and ODT (editable) forms, users can buy printed copies,” says Jean Hollis Weber, volunteer writer, editor, and publisher of the official LibreOffice guides. “I’ve been working with a great group of other documentation volunteers, but we always need more people.”

To download or buy copies (from Friends of OpenDocument Inc., an Australia-based volunteer organization with members around the world, which supports the LibreOffice project), visit https://www.libreoffice.org/get-help/documentation.

LibreOffice documentation: join us in this adventure

olivier_hallot_07062010_964x1036
The LibreOffice documentation team produces the guidebooks, reference materials, wiki and online help to support users of the software. We’re working hard to add all the exciting new features and functions of recent LibreOffice versions, to show how your office productivity can be improved thanks to the free office suite – and your help would be very much appreciated! Even if you can only spare 30 minutes each week, your contribution would be very valuable, and you’ll also get experience with a big-name open source project. Read on for the full details…

(more…)

Press Releases

The Document Foundation announces the simultaneous availability of LibreOffice 26.2.2 and LibreOffice 25.8.6

Berlin, 26 March 2026 – The Document Foundation today announces the simultaneous release of LibreOffice 26.2.2 and LibreOffice 25.8.6. These…

Open Document Format

ODF is the future, OOXML is the past

Whenever a user, a government, a school or a business chooses the format in which to store and exchange its…