Behind the scenes at TDF: marketing and PR

italovignoli-cheersMarketing and PR at TDF are a very demanding task, as we are covering the entire world from a single point in Europe. It is a challenging role, and also a very rewarding one (because we continue to increase the project visibility with each announcement, and this is a testament to the quality of the software).

During the last six months, we have worked at two major announcements: the finalization of LibreOffice 5.0 announcement, which has been a success under any point of view, and has raised the visibility of LibreOffice over the other free office suites, and the preparatory work for the announcement of LibreOffice 5.1, which will be finalized in early February 2016.

In between, we have had the Aarhus Conference – with a number of community related announcements – and the 1,000th developer joining the project since 2010, a significant achievement for a project which until 2010 was considered one of the most difficult to contribute to, because of the size and the characteristics of the source code.

In July, we prepared the announcement, planned for August 5, 2015. Apart from drafting the usual press release, we developed a “road to LibreOffice 5.0” text and visual to underline the importance of our time based release schedule, and the key features of every previous major release.

In addition, a couple of weeks before the announcement, we started poking top editors for a pre-release conference call, to provide additional information to the people interested in offering some insights. Conference calls were scheduled both the week before the announcement and on the Monday and Tuesday before our Wednesday, August 5, announcement.

We organized two group conference calls, and one publisher specific conference call. On the day of the announcement, LibreOffice 5.0 received a large coverage, with a corresponding spike in donations and downloads. All in all, the launch of LibreOffice 5.0 was the most successful ever.

In September, we supported the LibreOffice Conference in Aarhus with the traditional “state of the project” presentation, plus several community related announcements (sent as press releases after the end of the conference).

In October, it was business as usual, i.e. the usual flow of LibreOffice releases updating the LibreOffice 4.4 “still” branch and the LibreOffice 5.0 “fresh” family. Each new release confirmed the uptake of donations, which have increased since the announcement of LibreOffice 5.0. This is probably also due to the growth of the awareness, based on a large number of articles in the media.

In November, we have started planning the LibreOffice 5.1 announcement, scheduled for early February 2016. The challenge is to outperform what we have achieved with the announcement of LibreOffice 5.0, which was a success. In order to improve results, we have planned a number of actions starting from December, when the first Release Candidate will be available.

In addition, we plan to produce several documents to describe LibreOffice 5.1 to specific user clusters, such as enterprises and individual users (which represent the majority of our users). Later on, we will try to add a document targeted to schools, where LibreOffice is rather popular.

To reach a wider media audience, we have also started to add other journalists to our mailing lists, and to purge the existing mailing lists from outdated or wrong addresses.

We have a total of over 13,000 journalists in our global and local mailing lists, which are becoming more accurate after the distribution of each press release. All people covering LibreOffice are cherry picked and added to a specific mailing list, which is becoming the core of our press release distribution system.

Stay tuned, exciting marketing times ahead of us.

Behind the scenes at TDF: Jan Iversen, mentoring development lead

janiversensmallI started working for Document Foundation in November. I live and work in southern Spain, Malaga, a nice warm place. I wrote my first program in 1975, so I have been active in the pre-unix, pre-linux, pre-pc worlds, and have been involved in developing drivers, micro kernels and compilers. I retired from my international companies in 2011, dedicating time to open source.

LibreOffice is one of the most complex and biggest open source software packages, and at the same time one of the most well known. Today, having developed open source is a big plus on a CV, but starting with LibreOffice can be a challenge. In the upcoming period, I will be focusing on making a simple non-complex step by step guide to make the first patch, and will personally be there for new (and old) people.

In open source projects, it is perfectly normal to have people come and go, although – as a community – we would like people to stay and grow their development experience. I will devote time researching what can be done to make our community even more attractive, by getting input from people who are less experienced developers.

Many mature open source projects have a “not invented here” attitude, simply because senior developers know how to do things, and tend to refer new people to a lot of information. The core LibreOffice developers have a very open attitude, but are also very busy. So, my role will be to connect newcomers to the most relevant developer.

My mailbox is always open, so if you have any comment/suggestion/complaint please e-mail me.

Behind the scenes at TDF: Karl Morten Ramberg, marketing intern

kmr2I am working as marketing intern since October, living and working out of Lillehammer, Norway. I have been working with open source software and projects since around the year 2000. Before that I was a development manager for ERP software for some years. I have also been heavily involved in using office suites as front ends to ERP and other systems both in private industry and the public sector.

Currently, I am working at the release planning of LibreOffice 5.1, with a focus on putting together the information for the product flyers – for both private users and enterprises – we will make available for the product launch. I have also been participating in a business exhibition in Stuttgart, and coordinating with native language groups via Sophie.

Based on previous experiences and impressions from the event, I have also written a market segmentation/positioning document, which will be broken down into prioritized actions and deliverables.

Hopefully, we will be able to streamline the upcoming major release announcements, based on the improved process we are using for LibreOffice 5.1.

Behind the scenes at TDF: L10N and NLP in the first half of 2015

_SDS5526Now that the summer vacation time is over for many of us, it’s time to have a look at what has been happening behind the scenes with our fantastic native-language community. And indeed – it’s a lot of exciting things!

Now that TDF has launched the Android Viewer and even if the application itself is not yet available other than in en_US language, we could at least give its description in several languages. We offer the download description in about 16 languages. If yours is not there, just join us on the localization list and we will help you to achieve it.

This is THE big news of this second quarter: Pootle has been moved two versions further and after a testing period, the server went live and we are now using this version to translate 5.0 strings. Imagine a big big database which needs several days to be saved and pushed, then a first migration to the intermediate version, then to the 2.7 which is the actual version we are using. Dwayne and his team have done a tremendous work during this migration, fixing bugs almost as soon as they were reported.

We have also changed our workflow while preparing 5.0.0 release.  The teams are now translating on master which allows more small steps in translation work instead of working on a large bunch of changes. Some new teams have joined the group and I would like to underline the work done by Giovanni to get the Guarani version done for 5.0. It was a challenge and he won it! We even have an emoji language in our translated versions, have you tried it already?

With the launch of the 5.0 version, several press releases have been translated and sent to the local press. Thanks to all who participated to this effort, that has allowed a very good coverage of the news in numerous countries.

At the same time, we also have made the annual report available in English and thus available for translation. This year, it was first written in English and then translated to German to be available for the German authorities. If it has not been translated in your language, you’ll find it here: https://wiki.documentfoundation.org/File:TDF2014AnnualReport.pdf. It’s a very nice document, which explains the many facets of our project.

We are preparing the LibreOffice conference in Aarhus (Denmark) in September, and we are very pleased to see that the Native Language and Localization teams will be well represented this year, with a full workshop and several talks. If you can’t attend, there will be an IRC channel available where we will report and discuss. Don’t hesitate to check the conference site, as even if you don’t attend, there will be several news here: http://conference.libreoffice.org.

Behind the scenes at TDF: Marketing and Communications

Italo VignoliThe months between April and the first half of August have been rather busy, as I have been working – together with the other members of TDF staff and several volunteers – at different projects: the first TDF Annual Report, the final development stage of LibreOffice 5.0, including two bug hunting sessions, the announcement of the publication of ODF 1.2 by ISO, and the launch of LibreOffice 5.0. In addition, I have worked at smaller tasks such a announcements of minor releases.

The bigger task, as everyone can imagine, has been the launch of LibreOffice 5.0, as we wanted to make a real impact with this new major release.

First of all, I started to update the mailing lists for the distribution of press releases, which are a fundamental tool for the success of the launch. Since January, TDF is using a dedicated open source tool – phpList – which is saving a lot of work, especially when keeping mailing lists updated. In fact, phpList keeps track of all bounces, which are stored in each record, making it easier to spot old or wrong email addresses.

Journalists move around quite frequently, and only a small percentage remembers to update their record. For all the others, you have to chase them using a combination of search engines and other tools such as LinkedIn and About.Me. It is a rather tedious activity, but is key to ensure the success of each press release.

Since TDF has a combined mailing list of over 13,000 journalists worldwide, I have had to review and update around 10% – or over 1,000 email addresses – between May and July. To avoid being burned by this task, I have done a few each evening, while watching TV.

In early July, I have started to work at the launch documents, by looking at new features and trying to identify those which were more important. I have also set the announcement date at August 5. In addition, together with Jan Holesovsky and Charles Schulz, and the graphic designer Barak Paz, we have worked at a new identity for LibreOffice 5.0, with a new splash screen and a new start center.

In mid July, I have started to “leak” some news to a selected number of journalists, to start getting coverage on the upcoming major release. I have sent short messages to all the editors who clicked on our previous announcements, showing some interest on our press releases. I have also invited these editors to pre-release conference calls on August 3, or to 1to1 interviews on August 3 or August 4.

In late July, I distributed the final draft of the press pack, which was based on a press release, a feature backgrounder, and a “road to LibreOffice 5.0” document highlighting the major features of all the previous LibreOffice releases since January 2011. I also developed a timeline infographics, to explain the three stages of LibreOffice development: 3.x for code cleaning, 4.x for code refactoring, and 5.x for UI and feature innovations. This document was published on TDF blog as a teaser release on July 29.

I also prepared a short slide show to introduce LibreOffice 5.0 to journalists, with some visuals which were supposed to be used also to embellish the articles.

On August 3, I hosted pre-announcement conference calls for journalists based in Europe and in the US, for a total of 8 journalists (Extension Media, Genbeta, Golem, IDG News, ITWeb, PC World, The Inquirer and V3). I also sent the Press Kit under embargo to Betanews, ECT News, Liliputing, IT World and Network World.

On August 4, together with Michael Meeks, I hosted the pre-announcement 1to1 interview with InfoWorld. In addition, I have provided some quick answers to questions raised by journalists who received the press kit.

On August 5, I published the announcement message and the blog post, and distributed the press release to over 4,000 journalists worldwide. Over 30% viewed the announcement and clicked on the link, and half of them – around 600 journalists – published an article. As a consequence, we had a spike of visits to the blog and a spike of donations (which are proportional to downloads). All in all, a very successful announcement, thanks to the work of our developer community who has been able to put together a fantastic product, and of the other volunteers who have contributed with ideas and comments to make LibreOffice 5.0 stand out from the office suite crowd.

Behind the scenes at TDF: LibreOffice QA, so much accomplished so far this year!

Many of you are familiar with LibreOffice or one of its predecessors (StarOffice, OpenOffice.org, etc..), but you may not be aware of the immense amount of work that goes into the production of the software and the careful testing of each release. Although there are many different teams within the LibreOffice community who each perform essential roles in the collaborative development process, I don’t have enough space to cover them all today, so I’ll focus on the LibreOffice QA Team, a group of volunteers and employees of various companies around the world who work tirelessly to identify issues with LibreOffice on all platforms, including issues of interoperability, process, accessibility, and ease of use.

robinson-in-brusselsThe QA Team has accomplished much in the first quarter of this year, including significant reduction of UNCONFIRMED bug count, broad testing of our support for media on all major platforms, migration of our Bugzilla bug tracker to our own infrastructure, information and advice for our Annual Report, exhaustive work testing our LibreOffice Android port, and major improvements with our bibisect repositories. I’m sure I’ve omitted something from that list, but the sentence was getting long enough that I figured I should stop before I ran out of breath 😉

As of mid-December of last year, our UNCONFIRMED bug count was steadily dropping, but was still above 500. Throughout the holiday season and into January, the QA Team amazed everyone by lowering the number of bugs that needed triage to sub-400, then to 359, and even down below 280. Although our current count has stabilized around 350, we hope that with increased participation we can continue to chip away at the remaining pile.

Although most of the code for displaying images is cross-platform, LibreOffice uses different libraries on Win, Mac, and GNU/Linux for audio and video playback. With confusion about media playback a persistent issue, the QA Team created a set of wiki pages to help clarify the extent and quality of media support on all of our platforms, as well as provide user-friendly information about what codecs we recommend for use. Test support is ongoing, and we very much welcome additional test results or suggestions on how we can increase our playback support on proprietary platforms such as Windows and Mac OS X.

QA’s biggest project this year to date has been our Bugzilla Migration from Freedesktop.org to TDF (The Document Foundation) infrastructure. With careful planning and dry-runs tested over many weeks, our migration went very smoothly and had minimal interruption to the overall development of LibreOffice. With TDF control of Bugzilla in place, we’ve been able to make additional changes to the bug tracker, add new Components and Products for all of our current software projects, and even make small tweaks and add well-crafted messages to assist our users in reporting, updating, and interacting with our bugtracker, with the QA Team, and our developers. We will continue to make changes and improvements to Bugzilla throughout 2015, and are eager to hear from you about any bugs you’ve found in LibreOffice or suggestions you have for enhancement. Please file all bugs and enhancement requests at: https://bugs.documentfoundation.org/.

Throughout 2014, people continually asked me about running LibreOffice on Android, and by the beginning of 2015, I was excited to hear that our port was on its way! Upon the arrival of editing support (currently in beta) in the LibreOffice for Android app, QA has provided insightful feedback about various aspects of document use, feature support, and even special, edge-case problems that affect only a limited number of our users, but which we would like to eliminate (as with all bugs!) With volunteers stepping up to test on phones, tablets, and even laptops, the QA Team has provided extensive testing of our port of LibreOffice to Android, and has committed to keeping UNCONFIRMED bugs for Android in the single digits.

As in 2014, our bibisect repositories remain one of the best investigative tools of the QA Team to help identify the point at which regressions have been introduced into the codebase. With the ability to use binary search and pre-built binaries to quickly focus-in on a particular regression, we can use our time much more effectively, avoiding building and re-building the same versions. The more steps that QA can take to ferret-out the particular commit that caused a crash or changed program behavior, the faster that developers can create a fix and patch the code for the next version of LibreOffice.

Historically, our bibisect repositories have contained only a fraction of all commits to our mainline repository. Due to a confluence of factors, including server resources, software limitations, and hard disk sizes, it was most prudent for us to include only every 60th commit, allowing us to drastically narrow the search field to a much more manageable size. Armed with faster hardware and some careful optimization of non-relevant commits, superstar volunteer Matthew Francis has created a breed of “max” bibisect repositories that include all relevant commits in a single repository. These new repositories will give the QA Team the ability to delve much deeper into the particulars of a given regression, often identifying the particular developer who committed the change, allowing us much faster feedback and progressed towards a clean and consistent codebase.

Of course, QA works on many other tasks as well, including testing and triaging our Android Impress Remote, providing feedback about our websites and infra, helping the Document Liberation Project, and helping to identify new enhancements for LibreOffice. Although our primary focus is the LibreOffice suite, we do our best to keep track of everything else in the ecosystem, so that we can identify any potential problems before they affect many users.

With new platforms such as LibreOffice Online announced, and more interesting developments on the horizon, the members of the QA Team will definitely have more than enough work to keep them busy throughout 2015. If you’re interested in joining our efforts, or just curious about what’s involved in testing such a large project, drop by #libreoffice-qa on Freenode or say hello on our mailing list.

Cheers, Robinson