Language Selection

English French German Italian Portuguese Spanish

Measuring the true success of OpenOffice.org

Filed under
OOo

What is success ?

Is success measured in downloads, or up-loads ? are bugs filed as good as bugs fixed ? are volunteer marketers as valuable as volunteer developers ? If we have lots of bugs filed and lots of volunteer management material is that success ? is the pace of change important ? Does successful QA exist to create process to slow and reject changes, or by accelerating inclusion of fixes improve quality ? Is success having complete, up-to-date and detailed specifications for every feature ? Is success getting everyone to slavishly obey laborious multi-step processes, before every commit ? Alternatively does success come through attracting and empowering developers, who have such fun writing the code that they volunteer their life, allegiance and dreams to improve it ?

Magnitude of contributions

This graph is more meaningless than it might first appear, the raw data still shows noise like individuals committing obvious sillies copying chunks of OO.o to the binfilter eg. To some extent it is further distorted by us trying to clean this up for the past couple of years before giving up.

So the data is not that useful. Is it more useful to look at an individual to see if they are contributing something ? If we threshold the data we can at least approximate an activity metric / boolean. The graph below shows two developers - the Sun developer Niklas Nebel, and the Novell hacker Kohei Yoshida. Both work primarily on calc, and you can see the large bar when Kohei committed his solver to a branch at the end of 2006.

More Here




More in Tux Machines

digiKam Software Collection 4.3.0 released...

After a long bugs triage, we have worked hard also to close your reported issues.. A long list of the issues closed in digiKam 4.3.0 is available through the KDE Bugtracking System. Read more

Seneca College realizes value of open source

Red Hat has done a lot of work with CDOT, lately specializing in Fedora for ARM processors. Pidora, the Fedora Linux Remix specifically targeted to the Rasberry Pi, was primarily developed at CDOT. Another company that we have been working with lately is Blindside Networks. They do a lot of work with CDOT on the BigBlueButton project, which is a web conferencing tool for online education. NexJ is a Toronto-based software development firm that has worked with CDOT on various aspects of open health tools on the server side and integration of medical devices with smart phones. We have recently started working on the edX platform, where developers around the globe are working to create a next-generation online learning platform. Read more

Today in Techrights

Initial impressions of PCLinuxOS 2014.08

I spend more time looking at the family trees of Linux distributions than I do looking at my own family tree. I find it interesting to see how distributions grow from their parent distribution, either acting as an extra layer of features which regularly re-bases itself or as a separate fork. New distributions usually tend to remain similar in most ways to their parent distro, using the same package manager and maintaining similar philosophies. When I look at the family trees of Linux distributions one project stands out more than others: PCLinuxOS. Read more