Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub

Bissyandé, Tegawendé F.; Lo, David; Jiang, Lingxiao; Réveillère, Laurent; Klein, Jacques; Traon, Yves Le

doi:10.1109/issre.2013.6698918

Cited by 134 publications

(92 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Issues can be bugs, feature requests, enhancements and other types of reporting related to a repository [21] [22].…”

Section: Oss Hosting Platformsmentioning

confidence: 99%

“…Moreover, JavaForge has as well announced on March, 2016 that it will be shut down permanently [25]. Among the 10 platforms that were selected, GitHub is the largest one hosting the largest number of OSS projects [19], [20], [22], [35]. Other platforms such as Bitbucket, Gitlab, Codeplex and SourceForge are also popular platforms.…”

Section: Selected Oss Hosting Platformsmentioning

confidence: 99%

“…An issue tracker allows contributors and collaborators to collaborate on issues, and offers better management of bugs, defects, feature requests, tasks, enhancements… etc. [21] [22]. However, some platforms use bug trackers which mainly focus on bug reports, but the majority of the platforms use issue trackers allowing tracking of issues other than bugs [22].…”

Section: Collaboration Features Into the Oss Hosting Platformsmentioning

confidence: 99%

“…[21] [22]. However, some platforms use bug trackers which mainly focus on bug reports, but the majority of the platforms use issue trackers allowing tracking of issues other than bugs [22]. For instance, Launchpad uses a bug tracker where GitHub, Bitbucket, Codeplex and more use issue trackers.…”

Section: Collaboration Features Into the Oss Hosting Platformsmentioning

confidence: 99%

See 3 more Smart Citations

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Alamer¹,

Alyahya²

2017

JSW

View full text Add to dashboard Cite

Abstract:Open source software (OSS) has been gaining large attention lately. In fact, several studies have shown that the collaboration is a remarkably major factor influencing the OSS quality. In addition, there are several existing platforms providing mediums for collaborative development of the OSS projects and involve advanced features that assist in boosting the collaboration process. Such platforms which can be called as open source software hosting platforms are rich of collaborative workflows. Therefore, in this research a comprehensive investigation of the current OSS hosting platforms is held for the sake of studying their collaboration capabilities as well as pointing out any limitations related to collaboration that might hinder OSS from meeting high quality. The review has shown that the current OSS hosting platforms have some potential limitations. The identified limitations have been shared through a survey with developers working on OSS platforms and the results have generally revealed that there is a necessity to overcome these limitations.

show abstract

“…Issues can be bugs, feature requests, enhancements and other types of reporting related to a repository [21] [22].…”

Section: Oss Hosting Platformsmentioning

confidence: 99%

Section: Selected Oss Hosting Platformsmentioning

confidence: 99%

Section: Collaboration Features Into the Oss Hosting Platformsmentioning

confidence: 99%

Section: Collaboration Features Into the Oss Hosting Platformsmentioning

confidence: 99%

See 2 more Smart Citations

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Alamer¹,

Alyahya²

2017

JSW

View full text Add to dashboard Cite

show abstract

“…Every commit was automatically checked whether the word "bug" was in the commit header or the commit message. The term "bug" was used because a large-scale study on tens of thousands of GitHub software projects (Bissyande et al 2013) found out that the most popular tag used in GitHub issue reports is bug. Hence, we think that most programmers also use the term bug to commit defects.…”

Section: Data Collection Proceduresmentioning

confidence: 99%

Integrating software quality models into risk-based testing

Foidl

Felderer

2016

Software Qual J

View full text Add to dashboard Cite

Risk-based testing is a frequently used testing approach which utilizes identified risks of a software system to provide decision support in all phases of the testing process. Risk assessment, which is a core activity of every risk-based testing process, is often done in an ad hoc manual way. Software quality assessments, based on quality models, already describe the product-related risks of a whole software product and provide objective and automation-supported assessments. But so far, quality models have not been applied for risk assessment and risk-based testing in a systematic way. This article tries to fill this gap and investigates how the information and data of a quality assessment based on the open quality model QuaMoCo can be integrated into risk-based testing. We first present two generic approaches showing how quality assessments based on quality models can be integrated into risk-based testing and then provide the concrete integration on the basis of the open quality model QuaMoCo. Based on five open source products, a case study is performed. Results of the case study show that a risk-based testing strategy outperforms a lines of code-based testing strategy with regard to the number of defects detected. Moreover, a significant positive relationship between the risk coefficient and the associated number of defects was found.

show abstract

Resolving governance disputes in communities: A study of software license decisions

Puranam

Shrestha

et al. 2020

Strategic Management Journal

View full text Add to dashboard Cite

Research summary Resolving governance disputes is of vital importance for communities. Gathering data from GitHub communities, we employ hybrid inductive methods to study discussions around initiation and change of software licenses—a fundamental and potentially contentious governance issue. First, we apply machine learning algorithms to identify robust patterns in data: resolution is more likely in larger discussion groups and in projects without a license compared to those with a license. Second, we analyze textual data to explain the causal mechanisms underpinning these patterns. The resulting theory highlights the group process (reflective agency switches disputes from bargaining to problem solving) and group property (preference alignment over attributes) that are both necessary for the resolution of governance disputes, contributing to the literature on community governance. Managerial summary Online communities play an increasingly important role in how companies innovate across organizational boundaries and attract talent across geographic locations. However, online communities are no Utopia; disputes abound even (more) when we collaborate virtually. In particular, governance disputes can threaten the functioning and existence of online communities. Our study suggests that governance disputes in online communities either unfold as bargaining over which solution is better or searching for a satisfactory solution. The latter is more likely to reach a resolution, when there is common ground. Companies interested in leveraging the power of online communities should (a) identify or train certain participants to transform endless bargaining into collective problem solving and (b) foster shared knowledge and value basis among participants through recruitment and strong organizational culture.

show abstract

Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub

Cited by 134 publications

References 23 publications

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Integrating software quality models into risk-based testing

Resolving governance disputes in communities: A study of software license decisions

Contact Info

Product

Resources

About