Understanding Open Source Developers’ Evolution Using TransFlow

Costa, Jean; Santana, Francisco W.; Souza, Cleidson R. B. de

doi:10.1007/978-3-642-04216-4_6

Cited by 3 publications

(3 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Research on FLOSS development has brought a series of interesting topics into the Software Engineering research agenda, such as the social structure of development communities [23], [24], [6], [7], communication and work flow patterns in FLOSS projects, [25], [26], developer evolution and participation [27], [20], and attractiveness of FLOSS projects [19], [18].…”

Section: B Using Data From Floss Projects In Software Engineering Rementioning

confidence: 99%

Free and Open Source Software Development and Research: Opportunities for Software Engineering

Kon

Meirelles

Lago

et al. 2011

2011 25th Brazilian Symposium on Software Engineering

View full text Add to dashboard Cite

Abstract-Free/Libre/Open Source Software (FLOSS) communities have produced a large amount of valuable software that is directly or indirectly used daily by any person with access to a computer. The field of Software Engineering studies processes, mechanisms, tools, and frameworks for the development of software artifacts. Historically, however, most of Software Engineering research and education does not benefit from the large and rich source of data and experimental testbeds offered by FLOSS projects and their hundreds of millions of lines of working code. In this paper, we discuss how Software Engineering research and education can greatly benefit from the wealth of information available in the FLOSS ecosystem. We then evaluate how FLOSS has been used, up to now, by papers published in the Brazilian Symposium on Software Engineering. Finally, we present an agenda for the future, proposing concrete ways to exploit the synergies between research and education in Software Engineering and FLOSS projects.

show abstract

Section: B Using Data From Floss Projects In Software Engineering Rementioning

confidence: 99%

Free and Open Source Software Development and Research: Opportunities for Software Engineering

Kon

Meirelles

Lago

et al. 2011

2011 25th Brazilian Symposium on Software Engineering

View full text Add to dashboard Cite

show abstract

“…4 Instead of mining the commit information from the code repository, we extracted the commit data from the Project Dash. For each project, we identified the users who had committed code to the project.…”

Section: Identifying Committers and Commit Datesmentioning

confidence: 99%

“…Other research that has investigated aspects of developer participation in open-source projects includes studies of developer demographics (e.g., [5]) and evolution of developer participation in terms of specialization, generalization, and movement from periphery to core (e.g., [4]). …”

Section: Related Workmentioning

confidence: 99%

Entering the circle of trust

Sinha

Mani

Sinha

2011

Proceedings of the 8th Working Conference on Mining Software Repositories

View full text Add to dashboard Cite

The success of an open-source project depends to a large degree on the proactive and constructive participation by the developer community. An important role that developers play in a project is that of a code committer. However, code-commit privilege is typically restricted to the core group of a project. In this paper, we study the phenomenon of the induction of external developers as code committers. The trustworthiness of an external developer is one of the key factors that determines the granting of commit privileges. Therefore, we formulate different hypotheses to explain how the trust is established in practice. To investigate our hypotheses, we developed an automated approach based on mining code repositories and bug-tracking systems. We implemented the approach and performed an empirical study, using the Eclipse projects, to test the hypotheses. Our results indicate that, most frequently, developers establish trust and credibility in a project by contributing to the project in a non-committer role. Moreover, the employing organization of a developer is another factor-although a less significant one-that influences trust.

show abstract