30
A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla The story of merge requests and bug reports Athanasios-Ilias Rousinopoulos <[email protected]> Alpen-Adria University September 9, 2014

A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Embed Size (px)

Citation preview

Page 1: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

A scientific analysis of openSUSE collaborationpatterns in OBS and Bugzilla

The story of merge requests and bug reports

Athanasios-Ilias Rousinopoulos<[email protected]>

Alpen-Adria University

September 9, 2014

Page 2: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Introduction

Page 3: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Goals

• Mine openSUSE Factory data• Analyze the data• Correlate bugs with accepted requests• Publish the source code

3 of 30

Page 4: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Data

• Period of study: 3 years• Requests submitted to openSUSE Factory repository (via OBS)• Bugs for openSUSE Factory distribution in Bugzilla

4 of 30

Page 5: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Bugzilla

Page 6: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Mining process

• Bicho• 8 products• 6 projects [KDE,GNOME,Apache,BaseSystem,Kernel,Xfce]

6 of 30

Page 7: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Problem

7 of 30

Page 8: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

OBS Factory

Page 9: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Mining process

• Download the OBS data in XML format• Develop an XML parser in Python• Parsed data are stored in MySQL database

9 of 30

Page 10: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Metrices

• Requests• Submitters (or Requesters)• Reviews• Reviewers• Packages• Accepters• Time deltas

10 of 30

Page 11: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Data Summary

Project Name Requests Reviews Reviewers PackagesGNOME:Factory 8355 10371 14 571KDE:Distro:Factory 6508 14144 16 340

11 of 30

Page 12: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

GNOME:Factory

Page 13: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Requests per state

13 of 30

Page 14: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Submitters

14 of 30

Page 15: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Reviewers

15 of 30

Page 16: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Reviewed requests (accepted)

16 of 30

Page 17: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Accepters

17 of 30

Page 18: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Acceptance Time

18 of 30

Page 19: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

KDE:Distro:Factory

Page 20: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Requests per state

20 of 30

Page 21: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Submitters

21 of 30

Page 22: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Reviewers

22 of 30

Page 23: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Reviewed requests (accepted)

23 of 30

Page 24: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Accepters

24 of 30

Page 25: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Acceptance Time

25 of 30

Page 26: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Source code

Page 27: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Get the source

• Alpha version• OBSParser

27 of 30

Page 28: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Conclusion

• Higher number bugs will lead us to better observations• The majority of requests are accepted in less than 10 days• People who submitt a request may also review or accept it• High percentage of non reviewed but accepted requests

28 of 30

Page 29: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Questions?

Page 30: A scientific analysis of openSUSE collaboration patterns in OBS and Bugzilla - The story of merge requests and bug reports

Thank you for your attention.

30 of 30