Developing an h-index for OSS developers

2012 9th IEEE Working Conference on Mining Software Repositories (MSR) Pub Date : 2012-06-02 DOI:10.1109/MSR.2012.6224288

A. Capiluppi, Alexander Serebrenik, A. Youssef

{"title":"Developing an h-index for OSS developers","authors":"A. Capiluppi, Alexander Serebrenik, A. Youssef","doi":"10.1109/MSR.2012.6224288","DOIUrl":null,"url":null,"abstract":"The public data available in Open Source Software (OSS) repositories has been used for many practical reasons: detecting community structures; identifying key roles among developers; understanding software quality; predicting the arousal of bugs in large OSS systems, and so on; but also to formulate and validate new metrics and proof-of-concepts on general, non-OSS specific, software engineering aspects. One of the results that has not emerged yet from the analysis of OSS repositories is how to help the “career advancement” of developers: given the available data on products and processes used in OSS development, it should be possible to produce measurements to identify and describe a developer, that could be used externally as a measure of recognition and experience. This paper builds on top of the h-index, used in academic contexts, and which is used to determine the recognition of a researcher among her peers. By creating similar indices for OSS (or any) developers, this work could help defining a baseline for measuring and comparing the contributions of OSS developers in an objective, open and reproducible way.","PeriodicalId":383774,"journal":{"name":"2012 9th IEEE Working Conference on Mining Software Repositories (MSR)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-06-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"16","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2012 9th IEEE Working Conference on Mining Software Repositories (MSR)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MSR.2012.6224288","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 16

Abstract

The public data available in Open Source Software (OSS) repositories has been used for many practical reasons: detecting community structures; identifying key roles among developers; understanding software quality; predicting the arousal of bugs in large OSS systems, and so on; but also to formulate and validate new metrics and proof-of-concepts on general, non-OSS specific, software engineering aspects. One of the results that has not emerged yet from the analysis of OSS repositories is how to help the “career advancement” of developers: given the available data on products and processes used in OSS development, it should be possible to produce measurements to identify and describe a developer, that could be used externally as a measure of recognition and experience. This paper builds on top of the h-index, used in academic contexts, and which is used to determine the recognition of a researcher among her peers. By creating similar indices for OSS (or any) developers, this work could help defining a baseline for measuring and comparing the contributions of OSS developers in an objective, open and reproducible way.

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

为开源软件开发人员开发h指数

开源软件(OSS)存储库中可用的公共数据有许多实际用途:检测社区结构;确定开发人员中的关键角色;理解软件质量;预测大型OSS系统中的bug，等等;还要在一般的、非oss特定的软件工程方面制定和验证新的度量标准和概念证明。从对OSS存储库的分析中尚未出现的结果之一是如何帮助开发人员的“职业发展”:给定在OSS开发中使用的产品和过程的可用数据，应该有可能产生识别和描述开发人员的度量，这可以在外部用作识别和经验的度量。本文建立在学术环境中使用的h指数之上，h指数用于确定研究人员在同行中的认可度。通过为OSS(或任何)开发人员创建类似的索引，这项工作可以帮助定义一个基线，以客观、开放和可重复的方式度量和比较OSS开发人员的贡献。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文去求助

来源期刊

2012 9th IEEE Working Conference on Mining Software Repositories (MSR)

自引率

0.00%

发文量

期刊最新文献

MINCE: Mining change history of Android project Co-evolution of logical couplings and commits for defect estimation Analysis of customer satisfaction survey data Do faster releases improve software quality? An empirical case study of Mozilla Firefox Why do software packages conflict?