Who Cares About My Feature Request?

Heppler, Lukas; Eckert, Remo; Stuermer, Matthias

doi:10.1007/978-3-319-39225-7_7

Cited by 4 publications

(6 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, contributors did not thoroughly maintain the publicly reported issues, e.g., bugs or missing functionalities, resulting in a constantly growing issue pool. As also outlined in previous research [4], features requested by external parties often get unrecognized by core-developers. Lacking to meet requests from users can be frustrating for the community and may impact the project negatively [1].…”

Section: Motivation To Introduce Product Ownersmentioning

confidence: 71%

Introducing Agile Product Owners in a FLOSS Project

Müller

Schindler

Slany

2019

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

and how it introduced agile product owners. Product owners communicate the product vision, provide a general direction, decide about features, and prioritize requirements that are implemented by the community, i,e., they are ultimately responsible for the product. This agile approach is intended to ensure a certain outcome, such as business objectives, but also to react to the needs of community members and users on a short-term basis. This paper presents how therefore this role has been defined and the processes have been adapted.

show abstract

Section: Motivation To Introduce Product Ownersmentioning

confidence: 71%

Introducing Agile Product Owners in a FLOSS Project

Müller

Schindler

Slany

2019

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

show abstract

“…Firstly, table 6 shows the distribution of different creator roles in different categories. The acceptance rate of 11 . In addition, we investigate the relationship between acceptance rate and frequency.…”

Section: Methodmentioning

confidence: 99%

“…Role stands for whether the creator is a developer or a user. Heppler et al have confirmed that reports filed by regular users have less chances of being implemented than that of developers 11 . In order to distinguish developers from users, we use the creator and assigned_to metadata in the data set, where creator refers to the email of the reporter who filed the report and assign_to is the email of the developer who was assigned the report.…”

Section: Creator Profilementioning

confidence: 99%

“…Fortunately, more properties can be mined beyond the texts. Heppler et al found that the probability of successful implementation of enhancement reports is twice as likely if the reports originate from developers rather than from common users 11 . The reason is that developers are more familiar with the application and are more skilled at proposing understandable reports.…”

Section: Introductionmentioning

confidence: 99%

“…The reason that creator profiles are useful can be explained from the following two aspects. Firstly, creators of different roles may have different approval rate according to Heppler's investigation 11 . So, distinguishing role of creators can be helpful.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Utilizing Creator Profiles for Predicting Valuable User Enhancement Reports

Niu

Chen

et al. 2023

Preprint

View full text Add to dashboard Cite

Users of software applications use Issue Tracking Systems (ITSs) to file enhancement reports, which leads to a large quantity of user requests. Indeed, these reports have become an important source for software requirements because they help to continuously improve software applications. Usually, developers and maintainers evaluate them and decide which user reports can be accepted. However, enhancement reports are continuously being raised one after another, which makes this process time-consuming and labor-intensive. Timely handling and implementation of these enhancement reports can effectively improve user satisfaction and product competitiveness. Thus, research has focused on automated methods for predicting which enhancement reports are likely to be approved, to maximum the value derived from user reports. However, reported results of existing approaches are typically not good enough for practical use. In this paper, we propose a novel creator-profile-based method to explore dependencies among enhancements to improve the prediction performance. Firstly, we define the concept of a creator profile, including a general method of how to generate creator profiles from the data set. Then we explain how to employ creator profiles to the problem of enhancement report approval prediction. Finally, we evaluate our approach on 40,551 enhancement reports collected from ITSs. The experimental results indicate that our proposed approach greatly improve on existing state of the art, especially in predicting approved reports. For cross-application prediction, the accuracy is 80.7%, while for non-cross-application prediction, the overall accuracy is 83.6%. That is, with the proposed approach, over 80% of user requests can be automatically identified for exacting valuable user requirements, which significantly reduces labor costs. Replication package is available at: https://anonymous.4open.science/r/approval_prediction-507E

show abstract

How Can Open Source Software Projects Be Compared with Organizations?

Eckert

2018

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

The existence of a community plays a central role in the development of Open Source Software (OSS). Communities are commonly defined as a group of people sharing common norms or values. The common interest of an OSS project is obvious: to develop software under an OSS license. When we look at the rather general definition of a community, we see that there is a similarity to the term 'organization'. This paper draws parallels between OSS projects and the general elements of an organization and shows the different elements comprised in an OSS community: people, organization and assets. Each of those elements is enriched with examples from different research in the corresponding OSS research stream and provides a broad overview of the elements of OSS projects. With the help of this comparison, research on OSS can be made more focused and aligned with organizational research.

show abstract

Who Cares About My Feature Request?

Cited by 4 publications

References 30 publications

Introducing Agile Product Owners in a FLOSS Project

Introducing Agile Product Owners in a FLOSS Project

Utilizing Creator Profiles for Predicting Valuable User Enhancement Reports

How Can Open Source Software Projects Be Compared with Organizations?

Contact Info

Product

Resources

About