Who Contributes the Most to LibreOffice?
Cedric Bosdonnat has been tracking contributions to LibreOffice since its announced fork from OpenOffice.org. He uses Git Data Miner to gleen results from the main branch of LibreOffice Git repositories. Git Data Miner is more commonly known as the tool used by Jonathan Corbet in his periodic kernel code reports.
Bosdonnat began tracking line contributions in the middle of September 2010 with the original 14 contributions being made by Oracle. Oracle actually contributes code to OpenOffice.org, and then LibreOffice merges those changes, thus resulting in Oracle's contributions to the new fork. These 112 contributions have continued throughout development, but are dwarfed by the contributions of new developers.
New contributors are those that have signed on to help with LibreOffice since the fork, either with code or translations. These contributions make up well over half of the total new changes found in LibreOffice as of mid-February. Weekly contributions in this area have averaged between 20 and 30 with a total number of 517 line contributions.
Those who worked on OpenOffice.org previously and are not employeed by any other major contributor are classified as known contributors. While their number of contributions have been fewer, they averaged approximately five per week since the fork. This totals 90 contributions in the 22 weeks of development.
Novell has been credited with a large portion of the contributions made to LibreOffice. When looking through changelogs the name Novell is seen over and over again. They were significant contributors to OpenOffice.org and many of their patches are used in LibreOffice to this day. Novell developers averaged in the neighborhood of 10 contributions per week for a total of 205 since the fork.
Red Hat, who also contributed to OpenOffice.org, has chipped in as well. With usually two contributions per week, Red Hat developers have provided 39 patches since the fork.
The newest known name to join the contributors list is Canonical. They contributed the Human theme and a later fix, but more Ubuntu integration code is likely. Björn Michaelsen contributed 2 patches in the last few weeks so far.
Bosdonnat says there are 133 new coders and 55 localizers since the fork. There seemed to be a slight dip at the end of last year according the graph and Bosdonnat attributes that to the festivities of the holiday season.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide