2010 7th International Conference on Ubiquitous Intelligence &Amp; Computing and 7th International Conference on Autonomic &Amp 2010
DOI: 10.1109/uic-atc.2010.113
|View full text |Cite
|
Sign up to set email alerts
|

Mining Frequent Development Patterns of roles in Open Source Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

1
3
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 1 publication
1
3
0
Order By: Relevance
“…This is not an irrelevant implication, as according to [10], "bugs reported by core members are solved more rapidly when more duplicates are found [...]", and according to [3], core developers perform core development activities, while peripheral developers solve smaller issues. We found confirmation from the research in [15], that the combination "Software Developer"↔''Project Manager", is the most common within projects. Our angle was a bit different, in that we focused on the developers -getting typical roles combinations within projects, and not on projects -getting the most relevant combinations of roles within projects.…”
Section: Discussionsupporting
confidence: 71%
See 1 more Smart Citation
“…This is not an irrelevant implication, as according to [10], "bugs reported by core members are solved more rapidly when more duplicates are found [...]", and according to [3], core developers perform core development activities, while peripheral developers solve smaller issues. We found confirmation from the research in [15], that the combination "Software Developer"↔''Project Manager", is the most common within projects. Our angle was a bit different, in that we focused on the developers -getting typical roles combinations within projects, and not on projects -getting the most relevant combinations of roles within projects.…”
Section: Discussionsupporting
confidence: 71%
“…Our angle was a bit different, in that we focused on the developers -getting typical roles combinations within projects, and not on projects -getting the most relevant combinations of roles within projects. This meant that in [15], also single project developers were mined. In our analysis, we found the importance of "All-handpersons": our interpretation is that they bring more multidisciplinary competence to projects.…”
Section: Discussionmentioning
confidence: 99%
“…Although there may be few surveys on OSS success, many organizations, companies as well as individuals have adopted evaluation methods along with their specific needs to determine which software to use. According to user classification, the OSS evaluation can be generally divided into three perspectives: user, developer, and tester (Cheng and Guo 2019;Yuan et al 2010). In particular, due to prior works and our research on employees from one famous company, users generally choose OSS that meets their functional requirements.…”
Section: Evaluation Perspective and Typical Evaluation Methods For Ossmentioning
confidence: 99%
“…Developers generally develop their own software that meets their requirements and exist little or no license risk (Lerner and Tirole 2005;Fershtman and Gandal 2004). Tester is generally a third party, mainly testing whether OSS has a significant impact on company and society (Yuan et al 2010).…”
Section: Evaluation Perspective and Typical Evaluation Methods For Ossmentioning
confidence: 99%