First 2016 meeting of the LibreOffice Indian community

CYcrDHsUoAAeZpMToday, the LibreOffice Indian community meets in Delhi, the capital of India, at Social Cops, to discuss 2016 activities. The event is supported by the FUEL Project, one of the largest localization communities worlwide (India alone has a large number of native languages, and localization is one of the first issues to tackle for any free software community).

The development of the LibreOffice Indian community is a very important objective for the entire project, as the Republic of India is the second largest country in the world by population, with over 1.2 billion inhabitants. In addition to Hindi, the official language of the Union, there are 21 officially recognised regional languages: Assamese, Bengali, Bodo, Dogri, Gujarati, Kannada, Kashmiri, Konkani, Maithili, Malayalam, Manipuri, Marathi, Nepali, Odia, Punjabi, Sanskrit, Santali, Sindhi, Tamil, Telugu and Urdu.

LibreOffice mini Conference 2016 Osaka

banner_2000x667The Japanese community has just organized their LibreOffice mini Conference 2016 in Osaka. We have asked Takeshi Abe, a leading member of the Japanese community, a few questions about the event.

Can you tell us more about the context of the Japan LibreOffice Mini-Conference?

In 2012, the idea of a mini Conference in Japan has emerged from discussions in LibreOffice Japanese Team, in charge of the organization of the series of events. Our team consists of the most active contributors in the Japanese community, serving as a NLP (native language project) now.

To explain the situation, let’s summarize the history of the Japanese community since the OOo era (please note that this is based on
my personal opinions). OOo had earned huge expectations from Japanese users. It was obvious both from the number of migrations [1] in the country, and the fact that a government agency was leading a technical research project for specific features of Japanese Language [2].

Unfortunately, like other communities in the OOo project, Japanese volunteers suffered from the bureaucratic nature of the project. Core members of the NLP faced difficulty to focus on contribution. They eventually parted ways, and some of them formed the so-called “users group” [3] in 2002, to try to manage the situation better than the “official” NLP. The dispute seems to remain unresolved until today.

This kind of separation resulted in fewer collaboration between volunteers and in a poor communication within the community. Worse, even, user and business organizations became skeptical about the availability of skilled people who could help to send the right feedback to the project. This resulted in even fewer contributions over time.

Time passed and the launch of LibreOffice struck. Its manifesto sounded exactly essential to us. Sure, meritocracy is the key. Early members of the LibreOffice Japanese Team have chosen a flat structure with no lead. Our team has encouraged each one to do what he/she could do in his/her favorite manner. It worked magically, and it still works today.

We have a practical issu, though: how can we communicate effectively outside the project to promote LibreOffice, recruit new volunteers or exchange ideas with the industry, when we have neither the authority nor a structured organization?

One of the answers was quite simple: let’s gather and ask people who are interested. This is how the mini Conference was born.

Is LibreOffice known in Japan and are there known deployments in the public or private sector?

Yes. You can find visible deployments at https://wiki.documentfoundation.org/JA/Marketing/CaseStudy.

Last question: do you have any specific goal for this mini-conference that would make you and the Japanese community happy?

Yes. We gather people annually to unify the community. Also, our Japanese Team has the time to have a face-to-face off-line meeting.

The last mini Conference was held in late 2014, focused on code development from the Japanese community. It was not only a success with interesting presentations by young hackers, but also provided a tutorial for newbies about how to start hacking LibreOffice.

This time we plan to meet people with broader interests. We have called for both long and short form of presentations on whatever,
whoever in the community would like to share. Accepted papers include ones from users, volunteers, academia and companies providing value-added service.

In addition, we have Kohei Yoshida as our guest speaker, talking about “five years of LibreOffice”.

I am sure that meeting friends in the community in early January and enjoying the refreshingly cold air in Osaka will be a great start for the activities in 2016.

[1] http://ossforum.jp/jossfiles/OpenOffice.org_use_cases_0.pdf
[2] https://web.archive.org/web/20070506220203/http://www.ipa.go.jp/software/open/ossc/2007/theme/koubo1_t01.html
[3] http://oooug.jp/

Third bug hunting session for LibreOffice 5.1

noun_83830_ccBerlin, January 7, 2016 – The LibreOffice community is working hard on the next major release of LibreOffice 5.1 – planned for early February – with a bug hunting session focused on new features and fixes for bugs and regressions, to test the second release candidate.

The session will last 3 days, from January 15 to January 17, 2016. On those dates, mentors will be available from 08AM UTC to 10PM UTC to help volunteers to triage bugs, on the QA IRC channel and via email on the QA mailing list.

In addition, there will be two dedicated sessions for Writer between 3PM UTC and 5PM UTC on Friday, January 15, and for Calc between 3PM UTC and 5PM UTC on Saturday, January 16. During the dedicated sessions, mentors and volunteers will concentrate all the efforts on a single module with the objective of confirming, reproducing and documenting bugs and regressions in a better way.

Those who cannot join during the bug hunting session are always welcome to help chasing bugs and regressions when they have time. The second release candidate of LibreOffice 5.1 will be available until late January.

Builds of LibreOffice 5.1 RC 2 will be available from the pre-releases directory before the bug hunting session: http://dev-builds.libreoffice.org/pre-releases/. On the wiki of The Document Foundation there is a page for the bug hunting session: https://wiki.documentfoundation.org/BugHunting_Session_5.1.0_RC2.

LibreOffice: the numbers

The LibreOffice project keeps growing, and 2015 numbers have just confirmed this positive trend.

downloadsuniqueipsDownloads since September 2010 are close to 120 million, with a rather steady increase of weekly numbers. In 2013 there have been visible spikes after the launch of LibreOffice 4.0 and 4.1, as these versions were representing a significant growth in term of features over previous releases. Unique IPs pinging for updates are around 150 million since 2012 (when we have started counting them). Combined, the two charts provide a flavour of the growth of the installed base. Of course, all the usual caveats apply to the numbers, based on The Document Foundation own data.

monthlygrowthserialgrowthWhen LibreOffice has launched, one of the most important challenges was the growth of developers working on the source code (because it was considered extremely hard to approach, based on the OOo experience). The numbers after 60+ months show that the issue was represented by the approach and not by the complexity of the source code. In fact, Libreoffice has attracted at least 3 new developers per month since September 2010: a result which can be considered rather extraordinary in the free software environment. At the end of October 2015, this combined serial growth has reached the figure of 1,000 developers. Charts are based on OpenHub data, crunched – of course – with LibreOffice Calc.

committerscommitsOf course, reaching 1,000 developers would be a meaningless achievement if the number of hackers contributing on a monthly basis were not enough to guarantee a continuity. These two charts show that over the last 24 months the number of developers contributing on a monthly basis has been around 80 (with a few small ups and downs), and the number of commits has always been higher than 1,250 per month (with peaks up to 3,000 in early 2014 and up to 2,000 on a regular basis). On a yearly basis, the number of active committers has slowly decreased from 350 to 275 (red line on the left chart, showing the yearly running average), but this is probably a consequence of the lower number of easy hacks which make the first step more challenging (an issue tackled with the hiring of a development mentor). Also these two charts are based on OpenHub data, crunched – of course – with LibreOffice Calc.

donationsxmonthdonationsxquarterAnother measurement of the LibreOffice success is based on donations. Most donations happen just after the download. Looking at the charts, it is rather clear that there has been a rather sharp increase in donations during the last two quarters (after the launch of LibreOffice 5.0 in early August 2015). Of course, these numbers do not represent the user attitude about LibreOffice (as we do not know anything about the demographics of the people who have donated), but the trend is encouraging.

blogThe last chart shows Pageviews and Unique IPs from The Document Foundation blog, over the same timeframe (from August 1st to December 31, 2015). It is rather clear that there has been a spike for the launch of LibreOffice 5.0, and then – after almost three months of flat numbers – there has been a sharp increase in Pageviews starting from November (the same timeframe of the increase in donations of the last two months). Another encouraging trend.

[high resolution charts can be opened by double clicking on the thumbnail]

 

LibreOffice: Advent Tip #24

Bugzilla Main PageLibreOffice last tip of the series (a huge success, according to the numbers) is slightly different from the previous ones, because is not a real tip but an invitation to help the project by submitting bugs and regressions.

In fact, only with the help of our large user community (stay tuned for the numbers…) we will be able to improve the quality of LibreOffice, release after release.

To file a bug or a regression, there is a specific resource: Bugzilla (the image on the left is a thumbnail of the home page). The process might look difficult for a first time user, but there is a nice tutorial (download PDF) which explains the different steps in detail.

Increasing and improving the number of bugs and regressions filled correctly would be the best gift that users could do to the project in 2016 and beyond.

Behind the scenes at TDF: Release Engineering

cloph_headLibreOffice proper

The year 2015 started off with LibreOffice 4.4.0 and 4.3.6 rc1 – only the first of a whopping 42 (of course!) tags that were created and for which a build was uploaded to our mirror network – and ends with the stable releases 4.4.7 and 5.0.4 and with the first RC for LibreOffice 5.1.0 (for those interested: that’s a total of 216GB for the binary builds).

This constant stream of builds allows our volunteer testers to always stay on top, not waste time with testing stuff only to find out a fix has already been checked in weeks ago.

But even the constant stream of full builds sometimes is not recent enough. Daily builds provided by various tinderboxes fill this gap. Not only do they constantly monitor the buildability of all current branches (and nag committers in case our continuous integration platform didn’t catch the problem before it ended up in the code), many also provide one installationset per day. That way users don’t have to fiddle with building LibreOffice themselves, but still can run the current code.

We also changed our release baseline:

since LibreOffice 4.4 we require Mac OS X 10.8 or later and dropped the 32bit version

since LibreOffice 5.0 we added 64bit builds for Windows (requiring Vista or later, 32bit build requires Windows XP SP3 or later)

since LibreOffice 5.1 the new baseline for Linux is CentOS 6 (kernel 2.6.32 or later, glibc 2.12 or later)

Pootle

But the year was not only spent on LibreOffice alone. After having migrated bugzilla to our own infrastructure, it was time to tackle pootle. As mentioned in the last behind-the-scenes, we upgraded our version of pootle to run on TDF-hosted hardware and added master workflow. This allowed translators to start with their work for the 5.0 and subsequently 5.1 much earlier than with the old process (where translation could only begin after the branch was created).

Android

Good news everyone, there’s now a LibreOffice Viewer for Android! While still in its infancy, it is a first step to an editor application that you can use to give your documents the final touch when on the road.

If you own a smartwatch, then you also might be interested in the updated Impress Remote for Android, that now integrates with Android Wearable devices.

Hackfests

Continuing from last year, Hackfest-VMs were provided for the various gatherings that took place in 2015 and will be provided to those happening in 2016. Participants don’t have to roll thumbs waiting until the build is finished on their personal machines, but can instead start digging into the code on a fast virtual machine, and also do some bibisecting to warm up/find an easy entry point.

tl;dr

nearly one LibreOffice build per week on top of that daily builds from tinderboxes

Impress Remote for Android got support for Wearables

LibreOffice Viewer for Android with basic editing capabilities

Bugzilla was migrated to TDF-Infrastructure

Pootle server was upgraded and moved to TDF-Infrastructure, with translators now being able to work on master branch