Computer Science ›› 2015, Vol. 42 ›› Issue (12): 43-46.

Previous Articles     Next Articles

Evolution of Contributors in Open Source Software Development

LI Qi-feng and LI Bing   

  • Online:2018-11-14 Published:2018-11-14

Abstract: Open source software development is heavily based on voluntary contributions.Developers are self-selected.But as open source software projects evolve,changes in the development team affect their organization and decision structure.New members enter the group and others leave.From the related research it is known that a small group of very active developers are responsible in general for the proper evolution of a project.But it does not attend to the time axis that evolution requires.In this paper,we analyzed how software developers evolve in open source software projects.As case studies,we selected GNU/Linux for researching the behavior of contributors to work on a open source software project.Our aim is to give quantitative insight about the evolution of maintainers.We studied how many these develo-pers remain from the beginning of the project and what happens to packages maintained by those developers who left the project.

Key words: Open source software,Developer,Co-evolution

[1] Crowston K,Howison J.The social structure of Free and Open Source software development [J].First Monday,2005,10(2):2
[2] Long Y,Siau K.Social Network Structures in Open Source Software Development Teams [J].Journal of Database Management,2007,18(2):25-40
[3] Xu J,Gao Y,Christley S,et al.A topological analysis of the open source software development community [C]∥Proc.of the 38th Hawaii International Conference on System Sciences (HICSS 2005).USA,2005:198a
[4] Singh P.The small-world effect:The influence of macro-level properties of developer collaboration networks on open-source project success [J].ACM Transactions on Software Engineering and Methodology,2010,20(2):6
[5] Treude C,Storey M-A.How tagging helps bridge the gap between social and technical aspects in software development [C]∥Proc.of the 31st International Conference on Software Engineering (ICSE 2009).Canada,2009:12-22
[6] Treude C,Storey M-A.Work Item Tagging:CommunicatingConcerns in Collaborative Software Development [J].IEEE Transactions on Software Engineering,2012,38(1):19-34
[7] StoreyM-A,Ryall J,Singer J,et al.How Software Developers Use Tagging to Support Reminding and Refinding [J].IEEE Transactions on Software Engineering,2009,35(4):470-483
[8] Tamrawi A,Nguyen T T,Al-Kofahi J M,et al.Fuzzy set-based automatic bug triaging [C]∥Proc.of the 33rd International Conference on Software Engineering (ICSE 2011).USA,2011:884-887
[9] Chen L,Wang X,Liu C.An Approach to Improving Bug Assignment with Bug Tossing Graphs and Bug Similarities [J].Journal of Software,2011,6(3):421-427
[10] Anvik J,Murphy G C.Reducing the effort of bug report triage:Recommenders for development-oriented decisions [J].ACM Transactions on Software Engineering and Methodology,2011,20(3):10
[11] Zou W,Hu Y,Xuan J,et al.Towards Training Set Reduction for Bug Triage [C]∥Proc.of the 35th IEEE Annual Computer Software and Applications Conference (COMPSAC 2011).Germany,2011:576-581
[12] Jeong G,Kim S,Zimmermann T.Improving bug triage with bug tossing graphs [C]∥Proc.of the 7th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering (ESEC/FSE 2009).Netherlands,2009:111-120

No related articles found!
Full text



No Suggested Reading articles found!