Benevol 2008: Relationship between Orphaning and Productivity

8/8/2019 Benevol 2008: Relationship between Orphaning and Productivity

1/31

Introduction to OrphaningApproach

Results and Work in ProgressFurther Work

Relationship between Orphaning and Productivityin Evolution and GIMPProjects

BENEVOL 2008. Eindhoven.

Daniel Izquierdo Cortazar

[email protected]/Libresoft, Universidad Rey Juan Carlos - University of Mons-Hainaut

December 11, 2008

Daniel Izquierdo Cortazar Relationship between Orphaning and Productivity in Evolution a
http://find/http://goback/


2/31



(cc) 2008 Daniel Izquierdo Cortazar.Some rights reserved. This document is distributed under the Creative

Commons Attribution-ShareAlike 2.5 licence, available inhttp://creativecommons.org/licenses/by-sa/2.5/

Daniel Izquierdo Cortazar Orphaning and Productivity


3/31



Table of contents

1 Introduction to Orphaning

2 Approach

3 Results and Work in Progress

4 Further Work



4/31



Index


2 Approach


4 Further Work


I d i O h i


5/31



Developer Turnover

Developer turnover is a problem.

There is a knowledge gap when senior developers leave aproject

New developers need some time to become familiar withexisting source code


I t d ti t O h i


6/31



Knowledge

Tacit knowledge: Not measurable

Explicit knowledge: It remains in the company/projectartifacts, such as code or documentation


Introduction to Orphaning


7/31



Knowledge Sharing

It is complicated to share tacit knowledge, but ...

We can measure explicit knowledge:

Source code management (CVS, SVN, Git, ...)

Mailing lists

Bug tracking systems




8/31



Research Question

How can we measure the knowledge loss due to

developer turnover?

Approach to measure knowledge gap left by developersIs this knowledge gap a good indicator for the projectshealth?

Useful for managers, to determine risky zones

We can measure the impact in number of lines of codewithout author present in the current team




9/31



Index


2 Approach


4 Further Work




10/31



Previous Definitions

Committer: Developer with write access to the SCM system.

Author: Original developer of a line of codeNon-Active Committer: Committer with no activity since agiven date

Orphaned Line: Line of code whose author is a non-active

committer




11/31

p gApproach


CVS Log

[...]1.246 (pj 13-Nov-01): /* Optional arg STRING supplies menu name for the keymap1.246 (pj 13-Nov-01): in case you use it as a menu with x-popup-menu. */)1.246 (pj 13-Nov-01): (string)1.8 (rms 11-Sep-92): LispObjectstring;1.8 (rms 11-Sep-92):1.8 (rms 11-Sep-92): LispObjecttail;1.8 (rms 11-Sep-92): if (!NILP (string))1.8 (rms 11-Sep-92): tail = Fcons (string, Qnil);1.8 (rms 11-Sep-92): else1.8 (rms 11-Sep-92): tail = Qnil;1.1 (jimb 06-May-91): return Fcons (Qkeymap,1.137 (rms 13-May-97): Fcons (Fmakechartable(Qkeymap,Qnil), tail));1.1 (jimb 06-May-91):

..




12/31

p gApproach


Studying each period

Monthly analysis

Snapshots from each month




13/31

gApproach


Detection of non-active committers

When does a committer leave the project?

How many lines were authored by her?

new orphaned lines




14/31

ApproachResults and Work in Progress

Further Work

Tools

Libresoft-tools: publicly available

https://forge.morfeo-project.org/projects/

libresoft-tools/

CVSAnalY: It parsers CVS, SVN or Git log and stores thedata in SQL format (MySQL, PostgreSQL or SQLite)

Carnarvon: It parsers each line of code and stores data

regarding to author, date, revision and so on in MySQLdatabase.


Introduction to OrphaningA h
https://forge.morfeo-project.org/projects/libresoft-tools/https://forge.morfeo-project.org/projects/libresoft-tools/https://forge.morfeo-project.org/projects/libresoft-tools/https://forge.morfeo-project.org/projects/libresoft-tools/http://find/http://goback/


15/31


Further Work

Index


2 Approach


4 Further Work


Introduction to OrphaningA h


16/31


Further Work

Case Studies: GIMPand Evolution

GIMP (GNU Image Manipulation Program) is a graphicseditor




17/31


Further Work


Evolution combines e-mail, calendar, address book and tasklist managements functions




18/31


Further Work


Both started at the same time (around 1998. At least usingthe Source Code Management system)

Both are included by default in the GNOME desktop (usingthe same process and release cycle)




19/31


Further Work

Orphaned Lines vs Size

1998-02-28 2000-02-28 2002-03-28 2004-03-28 2006-03-28

Time

0

200000

400000

600000

800000

1000000

1200000

NumberofLines

Ev. Total LinesEv. Orph. LinesGIMP Total LinesGIMP Orph. Lines

Size an Orp ane Lines Evo ution



20/31



21/31

ppResults and Work in Progress

Further Work

Orphaned Lines GIMP

Just a big jump

Core group of developers remain stable during the wholeproject

Evolution of orphaned lines continuously decrease

Nowadays, the number of orphaned lines reach 13%!



22/31



23/31


Matching Orphaningand Productivity

Work in Progress:Hypothesis: High orphaning is correlated with lowproductivity



R l d W k i P


24/31


Matching Orphaningand Productivity:Evolution

1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008

Time

0

500

1000

1500

2000

ModifiedFIles

Productivity Evolution Project

1998 2002 2006

Time

0

100000

200000

300000

400000

#O

rphanedL

ines

Orphaned Lines Evolution - Evolution Project



R lt d W k i P


25/31


Matching Orphaningand Productivity:GIMP

1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008

Time

0

500

1000

1500

2000

2500

3000

ModifiedFiles

Productivity GIMP Project

1998 2002 2006

Time

0

100000

200000

300000

400000

500000

#O

rphanedLines

Orphaned Lines Evolution - GIMP Project



Results and Work in Progress


26/31


Conclusions

Evolution: New set of developers = Increase of the

productivity (Surprising for us!)Evolution: Old core group tended to disappear = big jumps inorphaning and productivity

GIMP: Risky situation, if some of the core group developersdisappear





27/31


Conclusions

Evolution: company-driven project. People have to deal withthat code, they are paid for that job.

GIMP: community-driven project. People just choose, perhapsthey prefer to start from scratch.





28/31


Index


2 Approach


4 Further Work





29/31


Productivity

Detection of files with high levels of orphaning

Measure how they evolve

New Hypothesis: High levels of orphaning (in a file) iscorrelated with low levels of productivity (in that file)





30/31

gFurther Work

Enrich the approach

More projects, more data.

Working on Apache 1.3, GTK++, Wireshark and some others.





31/31

gFurther Work

Thanks for your attention

Thanks for your attention!


Benevol 2008: Relationship between Orphaning and Productivity

Documents

Transcript of Benevol 2008: Relationship between Orphaning and Productivity