adaptation-slr/SLR_references_total/both_waves_references/t2-acm-2.bib

@inproceedings{10.1145/1125170.1125182,
author = {Li, Yan and Tan, Chuan-Hoo and Teo, Hock-Hai and Mattar, A. Talib},
title = {Motivating open source software developers: influence of transformational and transactional leaderships},
year = {2006},
isbn = {1595933492},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1125170.1125182},
doi = {10.1145/1125170.1125182},
abstract = {Open Source Software (OSS) is developed by geographically distributed unpaid programmers. The success of such a seemingly chaotic OSS project will largely depend on how the project leader organizes and motivates the developers to contribute. Grounded on leadership and motivation theories, we proposed and tested a research model that seeks to explain the behavioral effects of a leader on the developers' motivation to contribute. Survey data collected from 118 OSS developers on Sourceforge.net was used to test the research model. The results indicate that leaders' transformational leadership is positively related to developers' intrinsic motivation and leaders' active management by exception, a form of transactional leadership, is positively related to developers' extrinsic motivation.},
booktitle = {Proceedings of the 2006 ACM SIGMIS CPR Conference on Computer Personnel Research: Forty Four Years of Computer Personnel Research: Achievements, Challenges \& the Future},
pages = {34–43},
numpages = {10},
keywords = {leadership, motivation, open source software development},
location = {Claremont, California, USA},
series = {SIGMIS CPR '06}
}

@inproceedings{10.1109/COMPSAC.2008.171,
author = {Nakagawa, Elisa Yumi and Machado de Sousa, Elaine Parros and de Brito Murata, Kiyoshi and de Faria Andery, Gabriel and Morelli, Leonardo Bitencourt and Maldonado, Jos\'{e} Carlos},
title = {Software Architecture Relevance in Open Source Software Evolution: A Case Study},
year = {2008},
isbn = {9780769532622},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/COMPSAC.2008.171},
doi = {10.1109/COMPSAC.2008.171},
abstract = {Software architecture has received increasing attention of practitioners and researchers, since it has played a significant role in determining the success and quality of software systems. At the same time, the success of Open Source Software (OSS) has also sparked interest of researchers in the universities and in the software industry. OSS has been largely used and developed and, as a consequence, the OSS quality has been a concern and an interesting subject for researchers. However, in spite of narrow relation between software architecture and software quality, there is lack of more detailed works that investigate how software architecture can influence OSS quality. In this paper, we present a case study reporting how software architecture is directly related to OSS quality. We have hence proposed architecture refactoring activity in order to repair software architectures, aiming at improving mainly maintainability, functionality and usability of these systems.},
booktitle = {Proceedings of the 2008 32nd Annual IEEE International Computer Software and Applications Conference},
pages = {1234–1239},
numpages = {6},
keywords = {software architecture, open source software, open source software quality},
series = {COMPSAC '08}
}

@inproceedings{10.1109/ARES.2007.84,
author = {Wahyudin, Dindin and Tjoa, A Min},
title = {Event-Based Monitoring of Open Source Software Projects},
year = {2007},
isbn = {0769527752},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/ARES.2007.84},
doi = {10.1109/ARES.2007.84},
abstract = {Project management traditionally has a strong focus on human reporting that fits well a tightly coupled form of organization to ensure the quality of project reporting. For loosely coupled forms of organization, such as open source systems (OSS) development projects, there are very few approaches to ensure the quality of project reporting; a promising approach can be to augment human reporting with data analysis based on the communication and state changes in an OSS project. In this paper we propose a concept and an initial measurement approach for event-based monitoring of OSS projects to better understand the actual benefit of tool-supported gathering, correlating and analyzing processes event data from the OSS community as a supplement for traditional software project monitoring data collection. We report on an empirical feasibility study investigating success and risk indicators of five OSS projects listed in the Apache Incubator.},
booktitle = {Proceedings of the The Second International Conference on Availability, Reliability and Security},
pages = {1108–1115},
numpages = {8},
series = {ARES '07}
}

@inproceedings{10.1145/1632149.1632165,
author = {Munga, Neeshal and Fogwill, Thomas and Williams, Quentin},
title = {The adoption of open source software in business models: a Red Hat and IBM case study},
year = {2009},
isbn = {9781605586434},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1632149.1632165},
doi = {10.1145/1632149.1632165},
abstract = {Free / Libre open source software (FLOSS/OSS) has gained increasing popularity and utilisation in commercial and governmental organisations. Universities like Harvard and Stanford now offer courses on open source as a business and also on how businesses can compete with open source firms. However, very little research has been published in regards to the influence of OSS on business strategies; the use of OSS as a viable business or its value proposition within a commercial entity. The business model, a powerful tool for extracting economic value from the potential of technological innovation, clearly plays an important role in the success of a business. In this paper we investigate the role of open source in the business models of Red Hat and IBM and describe how OSS has contributed to their success. A framework recently developed by some of the authors is used to evaluate and identify the key factors important to the integration of OSS strategies into traditional business models.},
booktitle = {Proceedings of the 2009 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists},
pages = {112–121},
numpages = {10},
keywords = {business models, case study, open source software},
location = {Vanderbijlpark, Emfuleni, South Africa},
series = {SAICSIT '09}
}

@inproceedings{10.1109/APSEC.2004.93,
author = {Ishikawa, Masahiko},
title = {Software Product Line and Open Source Software},
year = {2004},
isbn = {0769522459},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/APSEC.2004.93},
doi = {10.1109/APSEC.2004.93},
abstract = {A similar set of open source software is selected on many systems even if these systems in which the software is applied are in different domains. It must be primary type of core asset on Product Line Software Engineering. And next, I want to discuss about success of many network appliances run on open source OS.},
booktitle = {Proceedings of the 11th Asia-Pacific Software Engineering Conference},
pages = {567},
numpages = {1},
series = {APSEC '04}
}

@inproceedings{10.1109/HICSS.2010.385,
author = {Van Antwerp, Matthew and Madey, Greg},
title = {The Importance of Social Network Structure in the Open Source Software Developer Community},
year = {2010},
isbn = {9780769538693},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2010.385},
doi = {10.1109/HICSS.2010.385},
abstract = {This paper outlines the motivations and methods for analyzing the developer network of open source software (OSS) projects. Previous work done by Hinds [5] suggested social network structure was instrumental towards the success of an OSS project, as measured by activity and output. The follow-up paper by Hinds [4] discovered that his hypotheses, based on social network theory and previous research on the importance of subgroup connectedness, were vastly different than the results of his study of over 100 successful OSS projects. He concluded that the social network structure had no significant effect on project success. We outline how his approach disregarded potentially important factors and through a new study evaluate the role of the OSS developer network as it pertains to long-term project popularity. We also present an initial investigation into the adequacy of using the SourceForge activity percentile as a long-term success metric. In contrast with Hinds, we show that previously existing developer-developer ties are an indicator of past and future project popularity.},
booktitle = {Proceedings of the 2010 43rd Hawaii International Conference on System Sciences},
pages = {1–10},
numpages = {10},
series = {HICSS '10}
}

@inproceedings{10.5555/2337223.2337491,
author = {Serrano Zanetti, Marcelo},
title = {The co-evolution of socio-technical structures in sustainable software development: lessons from the open source software communities},
year = {2012},
isbn = {9781467310673},
publisher = {IEEE Press},
abstract = {Software development depends on many factors, including technical, human and social aspects. Due to the complexity of this dependence, a unifying framework must be defined and for this purpose we adopt the complex networks methodology. We use a data-driven approach based on a large collection of open source software projects extracted from online project development platforms. The preliminary results presented in this article reveal that the network perspective yields key insights into the sustainability of software development.},
booktitle = {Proceedings of the 34th International Conference on Software Engineering},
pages = {1587–1590},
numpages = {4},
location = {Zurich, Switzerland},
series = {ICSE '12}
}

@inproceedings{10.1109/HICSS.2007.426,
author = {Asundi, Jai and Jayant, Rajiv},
title = {Patch Review Processes in Open Source Software Development Communities: A Comparative Case Study},
year = {2007},
isbn = {0769527558},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2007.426},
doi = {10.1109/HICSS.2007.426},
abstract = {In spite of the overwhelming success of Free/Open Source Software (F/OSS) like Apache and GNU/Linux, there is a limited understanding of the processes and methodologies that specify this form of software development. In this paper, we examine the process of patch reviews as a proxy for the extent of code-review in F/OSS projects. While existing descriptions of patch review processes are mostly narrative and based on individual experiences, we systematically analyze the email archives of five F/OSS projects to characterize this process. While doing so, we make a distinction between contributions (patches or review comments) by core members and casual contributors to grasp the role of core members in this process. Our results show that while the patch review processes are not exactly identical across various F/OSS projects, the core members across all projects play the vital role of gate-keepers to ensure a high level of review for submitted patches.},
booktitle = {Proceedings of the 40th Annual Hawaii International Conference on System Sciences},
pages = {166c},
series = {HICSS '07}
}

@inproceedings{10.1145/1227310.1227495,
author = {Ellis, Heidi J. C. and Morelli, Ralph A. and de Lanerolle, Trishan R. and Damon, Jonathan and Raye, Jonathan},
title = {Can humanitarian open-source software development draw new students to CS?},
year = {2007},
isbn = {1595933611},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1227310.1227495},
doi = {10.1145/1227310.1227495},
abstract = {In this paper, we present an example humanitarian open-source software project that has been used since January 2006 at a small liberal-arts college as an experiment in undergraduate CS education. Sahana (Sinhalese for relief) is a free and open-source disaster management system developed in Sri Lanka by a group of IT professionals following the 2004 Asian tsunami. It is a web-based tool that addresses the IT coordination problems that typically occur in trying to recover from a large-scale disaster. We are currently exploring the wider use of Sahana as a sustainable model and platform for teaching about open-source software development while at the same time allowing CS students and educators to make a socially useful contribution of their time, effort, and expertise. This paper presents our experiences with Sahana including the benefits for both academia and industry.},
booktitle = {Proceedings of the 38th SIGCSE Technical Symposium on Computer Science Education},
pages = {551–555},
numpages = {5},
keywords = {curriculum development, open source software, software engineering},
location = {Covington, Kentucky, USA},
series = {SIGCSE '07}
}

@article{10.1145/1227504.1227495,
author = {Ellis, Heidi J. C. and Morelli, Ralph A. and de Lanerolle, Trishan R. and Damon, Jonathan and Raye, Jonathan},
title = {Can humanitarian open-source software development draw new students to CS?},
year = {2007},
issue_date = {March 2007},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
volume = {39},
number = {1},
issn = {0097-8418},
url = {https://doi.org/10.1145/1227504.1227495},
doi = {10.1145/1227504.1227495},
abstract = {In this paper, we present an example humanitarian open-source software project that has been used since January 2006 at a small liberal-arts college as an experiment in undergraduate CS education. Sahana (Sinhalese for relief) is a free and open-source disaster management system developed in Sri Lanka by a group of IT professionals following the 2004 Asian tsunami. It is a web-based tool that addresses the IT coordination problems that typically occur in trying to recover from a large-scale disaster. We are currently exploring the wider use of Sahana as a sustainable model and platform for teaching about open-source software development while at the same time allowing CS students and educators to make a socially useful contribution of their time, effort, and expertise. This paper presents our experiences with Sahana including the benefits for both academia and industry.},
journal = {SIGCSE Bull.},
month = mar,
pages = {551–555},
numpages = {5},
keywords = {curriculum development, open source software, software engineering}
}

@inproceedings{10.5555/776816.776950,
author = {Feller, Joseph and Fitzgerald, Brian and Hissam, Scott and Lakhani, Karim},
title = {The 3rd workshop on Open Source Software Engineering},
year = {2003},
isbn = {076951877X},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Building on the success of "Making Sense of the Bazaar" and "Meeting Challenges and Surviving Success" --- the 1st and 2nd Workshops on Open Source Software Engineering (ICSE 2001 and ICSE 2002) --- this workshop ("Taking Stock of the Bazaar') brings together researchers and practitioners for the purpose of discussing the diverse array of techniques --- as well as supporting tools and social/organizational contexts --- which can be observed in the domain of open source software.},
booktitle = {Proceedings of the 25th International Conference on Software Engineering},
pages = {785–786},
numpages = {2},
location = {Portland, Oregon},
series = {ICSE '03}
}

@inproceedings{10.1109/HICSS.2009.63,
title = {An Exploratory Study on the Two New Trends in Open Source Software: End-Users and Service},
year = {2009},
isbn = {9780769534503},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2009.63},
doi = {10.1109/HICSS.2009.63},
abstract = {Many have been envisaging the emergence of Open Source Software (OSS) for general end-users and the enhancements in providing services and support, as the most critical factors for OSS success, and at the same time, the most critical issues which are holding back the OSS movement. While these two distinct waves in OSS evolution have become more observable, researchers have not yet explored the characteristics of these two distinct new waves. The current study found evidence for these two waves and further explored the two waves by empirically examining two hundred projects hosted in Sourceforge.net. We compared the characteristics of OSS projects that are intended for two disparate audiences: developers and end-users and found that projects for end-users supported more languages but also had more restrictive licenses as compared to projects for developers.},
booktitle = {Proceedings of the 42nd Hawaii International Conference on System Sciences},
pages = {1–10},
numpages = {10},
series = {HICSS '09}
}

@inproceedings{10.1145/2788993.2789830,
author = {Barcomb, Ann},
title = {A multiple case study of small free software businesses as social entrepreneurships},
year = {2015},
isbn = {9781450336666},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2788993.2789830},
doi = {10.1145/2788993.2789830},
abstract = {Free/libre and open source software are frequently described as a single community or movement. The difference between free software and open source ideology may influence founders, resulting in different types of companies being created. Specifically, the relationship between free/libre software ideology and social entrepreneurships is investigated. This paper presents seven case studies of businesses, five of which were founded by people who identify with the free/libre software movement. The result is a theory that small businesses founded by free/libre software advocates have three characteristics of social entrepreneurships. First, social benefit is prioritized over wealth creation. Second, the business's social mission is not incidental but is furthered through its for-profit activities, rather than supported by the company's profits. Third, the company's success is defined in part by the success of its social mission. Free/libre software entrepreneurs who recognize their activities as social entrepreneurships can benefit from the existing literature on the unique challenges faced by socially-oriented businesses.},
booktitle = {Proceedings of the 11th International Symposium on Open Collaboration},
articleno = {1},
numpages = {8},
keywords = {free software, open source software, public good, small business, social entrepreneurship, social ventures},
location = {San Francisco, California},
series = {OpenSym '15}
}

@inproceedings{10.1109/SITIS.2008.57,
author = {Wagener, G\'{e}rard and Dulaunoy, Alexandre and Engel, Thomas},
title = {An Instrumented Analysis of Unknown Software and Malware Driven by Free Libre Open Source Software},
year = {2008},
isbn = {9780769534930},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/SITIS.2008.57},
doi = {10.1109/SITIS.2008.57},
abstract = {Reverse engineering is often the last resort for analyzing unknown or closed source software. Such an investigation is motivated by a risk evaluation of closed sourceprograms or by evaluating consequences and countermeasures against infections by malicious programs that are often closed source. This article presents a success storywhere we used and modified free software serving as environment for analyzing unknown software. We explain howa malware sandbox can be constructed based on free software. Moreover we describe how we modified free softwareto improve malware analysis with additional features or ex-tensions. Free software helped us to increase the accuracyof malware or unknown software analysis.},
booktitle = {Proceedings of the 2008 IEEE International Conference on Signal Image Technology and Internet Based Systems},
pages = {597–605},
numpages = {9},
keywords = {free software, malware, network security, reverse engineering, sandbox, sofware analysis},
series = {SITIS '08}
}

@inproceedings{10.1145/512035.512055,
author = {Nakakoji, Kumiyo and Yamamoto, Yasuhiro and Nishinaka, Yoshiyuki and Kishida, Kouichi and Ye, Yunwen},
title = {Evolution patterns of open-source software systems and communities},
year = {2002},
isbn = {1581135459},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/512035.512055},
doi = {10.1145/512035.512055},
abstract = {Open-Source Software (OSS) development is regarded as a successful model of encouraging "natural product evolution". To understand how this "natural product evolution" happens, we have conducted a case study of four typical OSS projects. Unlike most previous studies on software evolution that focus on the evolution of the system per se, our study takes a broader perspective: It examines not only the evolution of OSS systems, but also the evolution of the associated OSS communities, as well as the relationship between the two types of evolution.Through the case study, we have found that while collaborative development within a community is the essential characteristic of OSS, different collaboration models exist, and that the difference in collaboration model results in different evolution patterns of OSS systems and communities. To treat such differences systematically, we propose to classify OSS into three types: Exploration-Oriented, Utility-Oriented, and Service-Oriented. Such a classification can provide guidance on the creation and maintenance of sustainable OSS development and communities.},
booktitle = {Proceedings of the International Workshop on Principles of Software Evolution},
pages = {76–85},
numpages = {10},
keywords = {case study, open-source software (OSS), open-source software community, software evolution},
location = {Orlando, Florida},
series = {IWPSE '02}
}

@inproceedings{10.5555/776816.776867,
author = {Ye, Yunwen and Kishida, Kouichi},
title = {Toward an understanding of the motivation Open Source Software developers},
year = {2003},
isbn = {076951877X},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {An Open Source Software (OSS) project is unlikely to be successful unless there is an accompanied community that provides the platform for developers and users to collaborate. Members of such communities are volunteers whose motivation to participate and contribute is of essential importance to the success of OSS projects. In this paper, we aim to create an understanding of what motivates people to participate in OSS communities. We theorize that learning is one of the motivational forces. Our theory is grounded in the learning theory of Legitimate Peripheral Participation, and is supported by analyzing the social structure of OSS communities and the co-evolution between OSS systems and communities. We also discuss practical implications of our theory for creating and maintaining sustainable OSS communities as well as for software engineering research and education.},
booktitle = {Proceedings of the 25th International Conference on Software Engineering},
pages = {419–429},
numpages = {11},
location = {Portland, Oregon},
series = {ICSE '03}
}

@inproceedings{10.5555/1260984.1261215,
author = {German, Daniel M.},
title = {Using software distributions to understand the relationship among free and open source software projects},
year = {2007},
isbn = {0769528309},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Success in the open source software world has been measured in terms of metrics such as number of downloads, number of commits, number of lines of code, number of participants, etc. These metrics tend to discriminate towards applications that are small and tend to evolve slowly. A problem is, however, how to identify applications in these latter categories that are important. Software distributions specify the dependencies needed to build and to run a given software application. We use this information to create a dependency graph of the applications contained in such a distribution. We explore the characteristics of this graph, and use it to define some metrics to quantify the dependencies (and dependents) of a given software application. We demonstrate that some applications that are invisible to the final user (such as libraries) are widely used by end-user applications. This graph can be used as a proxy to measure success of small, slowly evolving free and open source software.},
booktitle = {Proceedings of the 29th International Conference on Software Engineering Workshops},
pages = {24},
series = {ICSEW '07}
}

@inproceedings{10.1109/MSR.2007.32,
author = {German, Daniel M.},
title = {Using Software Distributions to Understand the Relationship among Free and Open Source Software Projects},
year = {2007},
isbn = {076952950X},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/MSR.2007.32},
doi = {10.1109/MSR.2007.32},
abstract = {Success in the open source software world has been measured in terms of metrics such as number of downloads, number of commits, number of lines of code, number of participants, etc. These metrics tend to discriminate towards applications that are small and tend to evolve slowly. A problem is, however, how to identify applications in these latter categories that are important. Software distributions specify the dependencies needed to build and to run a given software application. We use this information to create a dependency graph of the applications contained in such a distribution. We explore the characteristics of this graph, and use it to define some metrics to quantify the dependencies (and dependents) of a given software application. We demonstrate that some applications that are invisible to the final user (such as libraries) are widely used by end-user applications. This graph can be used as a proxy to measure success of small, slowly evolving free and open source software.},
booktitle = {Proceedings of the Fourth International Workshop on Mining Software Repositories},
pages = {24},
series = {MSR '07}
}

@inproceedings{10.1007/978-3-319-39483-1_63,
author = {Laugasson, Edmund and Quaicoe, James Sunney and Jeladze, Eka and Jesmin, Triinu},
title = {Bridging Digital Divide in Schools in Developing Countries: Perceptions of Teachers of Free Software Opportunities},
year = {2016},
isbn = {978-3-319-39482-4},
publisher = {Springer-Verlag},
address = {Berlin, Heidelberg},
url = {https://doi.org/10.1007/978-3-319-39483-1_63},
doi = {10.1007/978-3-319-39483-1_63},
abstract = {21st century information society requires more and more use of ICT (information and communication technology) in everyday life. Nowadays there is much talk about the digital divide, which means economical and social disparities in digital technology use and availability in society of a particular country and among different countries. In this paper we sought to explore teachers knowledge and use of ICT resources in the context of free/libre and open-source software (FLOSS). When relying permanently on free tools there are several benefits which in turn will grow sustainable information society and will fortify economy in larger scale. For the mentioned purpose we use Technology Acceptance Model (TAM) first version. We found that TAM model is not ideal to accomplish mentioned tasks, especially in educational institutions. If teachers will be aware of FLOSS then they can increase ICT resources use in schools in a meaningful way. This in turn will reduce also disparity in schools and we may call it as a digital turn.},
booktitle = {Learning and Collaboration Technologies: Third International Conference, LCT 2016, Held as Part of HCI International 2016, Toronto, ON, Canada, July 17-22, 2016, Proceedings},
pages = {695–706},
numpages = {12},
keywords = {Technology Acceptance Model, Adoption, Digital divide, Free/libre and open-source software},
location = {Toronto, ON, Canada}
}

@inproceedings{10.1109/HICSS.2006.213,
author = {Lin, Lihui},
title = {Impact of Users' Expertise on the Competition between Proprietary and Open Source Software},
year = {2006},
isbn = {0769525075},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2006.213},
doi = {10.1109/HICSS.2006.213},
abstract = {Despite the availability of source code, deploying open source software (OSS) in an enterprise environment requires expertise. Recent surveys show that the skills of IT staff in an organization are one of the key factors in OSS adoption decisions. This paper develops a model where users choosing between proprietary software and OSS are heterogeneous in their expertise. The paper finds that as users become more skilled in OSS, the price of proprietary software will decline. Second, the equilibrium market structure is influenced by both users' expertise and network effects. It is not surprising that proprietary software can drive OSS out of the market in presence of network effect, but counter-intuitively, this happens when users are highly skilled in OSS. Third, in presence of network effect, OSS may survive in the market only when it is customizable by skilled users and therefore provides significant higher benefits to users than proprietary software.},
booktitle = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences - Volume 08},
pages = {166.1},
series = {HICSS '06}
}

@inproceedings{10.1145/2948076.2948090,
author = {Haskel, Lisa and Graham, Paula},
title = {Whats GNU got to do with it? participatory design, infrastructuring and free/open source software},
year = {2016},
isbn = {9781450341363},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2948076.2948090},
doi = {10.1145/2948076.2948090},
abstract = {In this paper we link Participatory Design (PD) to Free and Open Source Software (FOSS) via Infrastructuring. We describe the characteristics of FOSS focusing on extensibility, generativity and their communities of practice. We discuss how FOSS products and communities provide valuable resources to PD projects beyond the design phase. We use evidence from our long-running, community based PD project to show how FOSS provides essential elements of infrastructure that contribute to the sustainability of this project and suggest that the mutual learning outcomes of PD, together with FOSS resources, can support users' participation after design. We contribute to PD by providing a point of view from developers and facilitators, who combine FOSS and PD, that furthers an understanding of how these two areas are related.},
booktitle = {Proceedings of the 14th Participatory Design Conference: Short Papers, Interactive Exhibitions, Workshops - Volume 2},
pages = {17–20},
numpages = {4},
keywords = {Drupal, free and open source software, infrastructuring, participatory design, sustainability},
location = {Aarhus, Denmark},
series = {PDC '16}
}

@inproceedings{10.1145/973620.973725,
author = {Yordanova, Lina and Boychev, Georgi and Tsvetanova, Yanka and Hrisuleva, Vania and Kiryakova, Gabriela},
title = {Development of a web-based course on informatics via open-source software package MOODLE},
year = {2003},
isbn = {9549641333},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/973620.973725},
doi = {10.1145/973620.973725},
abstract = {The current study discusses the implementation of an Open-source Learning Management System platform MOODLE for establishment of Web-based course on Communication and Information Systems subjects. Our shared experience about searching, choosing, installation and implementation of an Open Source platform is a good example for starting with e-Learning development as the used strategy led to success. Future work could be encouraging and training students to use the designed and created course.},
booktitle = {Proceedings of the 4th International Conference Conference on Computer Systems and Technologies: E-Learning},
pages = {629–633},
numpages = {5},
keywords = {LMS platform, e-Learning, open-source, web-based course},
location = {Rousse, Bulgaria},
series = {CompSysTech '03}
}

@inproceedings{10.5555/1565142.1565145,
author = {Michlmayr, Martin},
title = {Software Process Maturity and the Success of Free Software Projects},
year = {2005},
isbn = {1586035592},
publisher = {IOS Press},
address = {NLD},
abstract = {The success of free software and open source projects has increased interest in utilizing the open source model for mature software development. However, the ad hoc nature of open source development may result in poor quality software or failures for a number of volunteer projects. In this paper, projects from SourceForge are assessed to test the hypothesis that there is a relationship between process maturity and the success of free software and open source projects. This study addresses the question of whether the maturity of particular software processes differs in successful and unsuccessful projects. Processes are identified that are key factors in successful free software projects. The insights gained from this study can be applied as to improve the software process used by free software projects.},
booktitle = {Proceedings of the 2005 Conference on Software Engineering: Evolution and Emerging Technologies},
pages = {3–14},
numpages = {12},
keywords = {Free Software, Open Source, Process Maturity, Quality Improvement}
}

@inproceedings{10.5555/647881.737775,
author = {Chandra, Subhachandra and Chen, Peter M.},
title = {Whither Generic Recovery from Application Faults? A Fault Study using Open-Source Software},
year = {2000},
isbn = {0769507077},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {This paper tests the hypothesis that generic recovery techniques, such as process pairs, can survive most application faults without using application-specific information. We examine in detail the faults that occur in three, large, open-source applications: the Apache web server, the GNOME desktop environment, and the MySQL database. Using information contained in the bug reports and source code, we classify faults based on how they depend on the operating environment. We find that 72-87\% of the faults are independent of the operating environment and are hence deterministic (non-transient). Recovering from the failures caused by these faults requires the use of application-specific knowledge. Half of the remaining faults depend on a condition in the operating environment that is likely to persist on retry, and the failures caused by these faults are likely to require application-specific recovery. Unfortunately, only 5-14\% of the faults were triggered by transient conditions, such as timing and synchronization that naturally fix them during recovery. Our results indicate that classical application-generic recovery techniques, such as process pairs, will not be sufficient to enable applications to survive most failures caused by application faults.},
booktitle = {Proceedings of the 2000 International Conference on Dependable Systems and Networks (Formerly FTCS-30 and DCCA-8)},
pages = {97–106},
numpages = {10},
keywords = {Faults, Heisenbugs, Recovery, Software, Transient},
series = {DSN '00}
}

@inproceedings{10.1145/2538862.2544315,
author = {DeCausemaker, Remy and Jacobs, Stephen},
title = {Adventures in hackademia: leveraging humanitarian free/open source software development in the class room (abstract only)},
year = {2014},
isbn = {9781450326056},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/2538862.2544315},
doi = {10.1145/2538862.2544315},
abstract = {This poster will briefly describe the components of the Humanitarian Free/Open Source Software Development (HFOSS) course offered by the Department of Interactive Games and Media at Rochester Institute of Technology in Upstate NY. It will depict this model of an "Open" Course (i.e. Open Courseware, Open Curriculum, Open Classroom, and Open Code) informed both by academic theory, and industry best practice. It will show the results of designers, developers, and project leaders, working in tandem with professors, staffers, and administrators to offer students a chance to apply research, and put theory into practice. It will discuss strategies of engagement, metrics of success and failure, and what resources are available for others to do the same.},
booktitle = {Proceedings of the 45th ACM Technical Symposium on Computer Science Education},
pages = {723–724},
numpages = {2},
keywords = {foss, free/open source software, open source},
location = {Atlanta, Georgia, USA},
series = {SIGCSE '14}
}

@inproceedings{10.1109/APSEC.2004.58,
author = {Senyard, Anthony and Michlmayr, Martin},
title = {How to Have a Successful Free Software Project},
year = {2004},
isbn = {0769522459},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/APSEC.2004.58},
doi = {10.1109/APSEC.2004.58},
abstract = {Some free software projects have been extremely successful. This rise to prominence can be attributed to the high quality and suitability of the software. This quality and suitability is achieved through an elaborate peer-review process performed by a large community of users, who act as co-developers to identify and correct software defects and add features. Although this process is crucial to the success of free software projects, there is more to the free software development than the creation of a 'bazaar'. In this paper we draw on existing free software projects to define a lifecycle model for free software. This paper then explores each phase of the lifecycle model and agrees that, while the bazaar phase attracts the most attention, it is the initial modular design that accommodates diverse interventions. Moreover, it is the period of transition from the initial group to the larger community based development that is crucial in determining whether a free software project will succeed or fail.},
booktitle = {Proceedings of the 11th Asia-Pacific Software Engineering Conference},
pages = {84–91},
numpages = {8},
keywords = {development process, free software, software lifecycle},
series = {APSEC '04}
}

@inproceedings{10.1109/SBES.2010.26,
author = {Terceiro, Antonio and Rios, Luiz Romario and Chavez, Christina},
title = {An Empirical Study on the Structural Complexity Introduced by Core and Peripheral Developers in Free Software Projects},
year = {2010},
isbn = {9780769542737},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/SBES.2010.26},
doi = {10.1109/SBES.2010.26},
abstract = {Background: Several factors may impact the process of software maintenance and evolution of free software projects, including structural complexity and lack of control over its contributors. Structural complexity, an architectural concern, makes software projects more difficult to understand, and consequently more difficult to maintain and evolve. The contributors in a free software project exhibit different levels of participation in the project, and can be categorized as core and peripheral developers. Research aim: This research aims at characterising the changes made to the source code of 7 web server projects written in C with respect to the amount of structural complexity added or removed and the developer level of participation. Method: We performed a observational study with historical data collected from the version control repositories of those projects, recording structural complexity information for each change as well as identifying each change as performed by a core or a peripheral developer. Results and conclusions: We have found that core developers introduce less structural complexity than peripheral developers in general, and that in the case of complexity-reducing activities, core developers remove more structural complexity than peripheral developers. These results demonstrate the importance of having a stable and healthy core team to the sustainability of free software projects.},
booktitle = {Proceedings of the 2010 Brazilian Symposium on Software Engineering},
pages = {21–29},
numpages = {9},
keywords = {Core and Periphery, Empirical Software Engineering, FLOSS, Free Software, Open Source software, Structural Complexity},
series = {SBES '10}
}

@inproceedings{10.1145/581339.581436,
author = {Feller, Joseph},
title = {Meeting challenges and surviving success: the 2nd workshop on open source software engineering},
year = {2002},
isbn = {158113472X},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/581339.581436},
doi = {10.1145/581339.581436},
booktitle = {Proceedings of the 24th International Conference on Software Engineering},
pages = {669–670},
numpages = {2},
location = {Orlando, Florida},
series = {ICSE '02}
}

@inproceedings{10.1109/HICSS.2014.406,
author = {Carillo, Kevin Daniel Andr\'{e} and Huff, Sid and Chawner, Brenda},
title = {It's Not Only about Writing Code: An Investigation of the Notion of Citizenship Behaviors in the Context of Free/Libre/Open Source Software Communities},
year = {2014},
isbn = {9781479925049},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/HICSS.2014.406},
doi = {10.1109/HICSS.2014.406},
abstract = {Attracting a large number of new contributors has been seen as a way to ensure the survival, long-term success, and sustainability of Free/Libre/Open Source Software (FLOSS) communities. However, this appears to be a necessary, but not a sufficient condition, as the well-being of FLOSS communities also relies on members behaving as "good citizens," to nurture and protect the community. This paper investigates the notion of FLOSS community citizenship behaviors in light of the organizational citizenship behaviors literature. Relying on 11 semi-structured interviews with FLOSS project leaders and community managers, the papers identifies key instances of citizenship behaviors along two dimensions: CCB-I (community citizenship behaviors oriented towards the benefits of other individuals), and CCB-P (community citizenship behaviors oriented towards the benefits of the project and its community).},
booktitle = {Proceedings of the 2014 47th Hawaii International Conference on System Sciences},
pages = {3276–3285},
numpages = {10},
keywords = {citizenship behaviors, free software, open source software communities},
series = {HICSS '14}
}

@inproceedings{10.1145/3663529.3663777,
author = {Khan, Nafiz Imtiaz and Filkov, Vladimir},
title = {From Models to Practice: Enhancing OSS Project Sustainability with Evidence-Based Advice},
year = {2024},
isbn = {9798400706585},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3663529.3663777},
doi = {10.1145/3663529.3663777},
abstract = {Sustainability in Open Source Software (OSS) projects is crucial for long-term innovation, community support, and the enduring success of open-source solutions. Although multitude of studies have provided effective models for OSS sustainability, their practical implications have been lacking because most identified features are not amenable to direct tuning by developers (e.g., levels of communication, number of commits per project). 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
In this paper, we report on preliminary work toward making models more actionable based on evidence-based findings from prior research. Given a set of identified features of interest to OSS project sustainability, we performed comprehensive literature review related to those features to uncover practical, evidence-based advice, which we call Researched Actionables (ReACTs). The ReACTs are practical advice with specific steps, found in prior work to associate with tangible results. Starting from a set of sustainability-related features, this study contributes 105 ReACTs to the SE community by analyzing 186 published articles. Moreover, this study introduces a newly developed tool (ReACTive) designed to enhance the exploration of ReACTs through visualization across various facets of the OSS ecosystem. The ReACTs idea opens new avenues for connecting SE metrics to actionable research in SE in general.},
booktitle = {Companion Proceedings of the 32nd ACM International Conference on the Foundations of Software Engineering},
pages = {457–461},
numpages = {5},
keywords = {Literature Review, Open Source Software, Research Actionable, Sustainability},
location = {Porto de Galinhas, Brazil},
series = {FSE 2024}
}

@inproceedings{10.5555/998675.999508,
author = {Feller, Joseph and Fitzgerald, Brian and Hissam, Scott and Lakhani, Karim},
title = {Collaboration, Conflict and Control: The 4th Workshop on Open Source Software Engineering},
year = {2004},
isbn = {0769521630},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Building on the success of the first three workshops inthe series, which were held at ICSE 2001 (Toronto), ICSE2002 (Orlando) and ICSE 2003 (Portland), the 4thWorkshop on Open Source Software Engineering,("Collaboration, Conflict and Control") brings togetherresearchers and practitioners for the purpose ofdiscussing the platforms and tools, techniques andprocesses, and the organizational structures that are usedto support and sustain communication, collaboration andconflict resolution within and between open sourcesoftware communities.},
booktitle = {Proceedings of the 26th International Conference on Software Engineering},
pages = {764–765},
numpages = {2},
series = {ICSE '04}
}

@inproceedings{10.1145/3383219.3383242,
author = {Alami, Adam and Cohn, Marisa Leavitt and W\k{a}isowski, Andrzej},
title = {How Do FOSS Communities Decide to Accept Pull Requests?},
year = {2020},
isbn = {9781450377317},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3383219.3383242},
doi = {10.1145/3383219.3383242},
abstract = {Pull requests are a method to facilitate review and management of contribution in distributed software development. Software developers author commits, and present them in a pull request to be inspected by maintainers and reviewers. The success and sustainability of communities depends on ongoing contributions, but rejections decrease motivation of contributors. We carried out a a qualitative study to understand the mechanisms of evaluating PRs in open source software (FOSS) communities from developers and maintainers perspective. We interviewed 30 participants from five different FOSS communities. The data shows that acceptance of contributions depends not only on technical criteria, but also significantly on social and strategic aspects. This paper identifies three PR governance styles found in the studied communities: (1) protective, (2) equitable and (3) lenient. Each one of these styles has its particularities. While the protective style values trustworthiness and reliability of the contributor, the lenient style believes in creating a positive and welcoming environment where contributors are mentored to evolve contributions until they meet the community standards. Despite the differences, these governance styles have a commonality, they all safeguard the quality of the software.},
booktitle = {Proceedings of the 24th International Conference on Evaluation and Assessment in Software Engineering},
pages = {220–229},
numpages = {10},
keywords = {FOSS governance, Open source software, code review, community management, decision making, pull request},
location = {Trondheim, Norway},
series = {EASE '20}
}

@inproceedings{10.1109/ICSE.2019.00100,
author = {Barcomb, Ann and Stol, Klaas-Jan and Riehle, Dirk and Fitzgerald, Brian},
title = {Why do episodic volunteers stay in FLOSS communities?},
year = {2019},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/ICSE.2019.00100},
doi = {10.1109/ICSE.2019.00100},
abstract = {Successful Free/Libre and Open Source Software (FLOSS) projects incorporate both habitual and infrequent, or episodic, contributors. Using the concept of episodic volunteering (EV) from the general volunteering literature, we derive a model consisting of five key constructs that we hypothesize affect episodic volunteers' retention in FLOSS communities. To evaluate the model we conducted a survey with over 100 FLOSS episodic volunteers. We observe that three of our model constructs (social norms, satisfaction and community commitment) are all positively associated with volunteers' intention to remain, while the two other constructs (psychological sense of community and contributor benefit motivations) are not. Furthermore, exploratory clustering on unobserved heterogeneity suggests that there are four distinct categories of volunteers: satisfied, classic, social and obligated. Based on our findings, we offer suggestions for projects to incorporate and manage episodic volunteers, so as to better leverage this type of contributors and potentially improve projects' sustainability.},
booktitle = {Proceedings of the 41st International Conference on Software Engineering},
pages = {948–954},
numpages = {7},
keywords = {community management, episodic volunteering, open source software, volunteer management},
location = {Montreal, Quebec, Canada},
series = {ICSE '19}
}

@inproceedings{10.1145/3611643.3617848,
author = {Feng, Zixuan},
title = {The State of Survival in OSS: The Impact of Diversity},
year = {2023},
isbn = {9798400703270},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3611643.3617848},
doi = {10.1145/3611643.3617848},
abstract = {Maintaining and retaining contributors is crucial for Open Source (OSS) projects. However, there is often a high turnover among contributors (in some projects as high as 80\%). The survivability of contributors is influenced by various factors, including their demographics. Research on contributors’ survivability must, therefore, consider diversity factors. This study longitudinally analyzed the impact of demographic attributes on survivability in the Flutter community through the lens of gender, region, and compensation. The preliminary analysis reveals that affiliated or Western contributors have a higher survival probability than volunteer or Non-Western contributors. However, no significant difference was found in the survival probability between men and women.},
booktitle = {Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering},
pages = {2213–2215},
numpages = {3},
keywords = {Disengagement, Open Source, Survivability},
location = {San Francisco, CA, USA},
series = {ESEC/FSE 2023}
}

@inproceedings{10.1145/1540438.1540461,
author = {Beaver, Justin M. and Cui, Xiaohui and St Charles, Jesse L. and Potok, Thomas E.},
title = {Modeling success in FLOSS project groups},
year = {2009},
isbn = {9781605586342},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/1540438.1540461},
doi = {10.1145/1540438.1540461},
abstract = {A significant challenge in software engineering is accurately modeling projects in order to correctly forecast success or failure. The primary difficulty is that software development efforts are complex in terms of both the technical and social aspects of the engineering environment. This is compounded by the lack of real data that captures both the measures of success in performing a process, and the measures that reflect a group's social dynamics. This research focuses on the development of a model for predicting software project success that leverages the wealth of available open source project data in order to accurately forecast the behavior of those software engineering groups. The model accounts for both the technical elements of software engineering and the social elements that drive the decisions of individual developers. Agent-based simulations are used to represent the complexity of the group interactions, and the behavior of each agent is based on the acquired open source software engineering data. For four of the five project success measures, the results indicate that the developed model represents the underlying data well and provides accurate predictions of open source project success indicators.},
booktitle = {Proceedings of the 5th International Conference on Predictor Models in Software Engineering},
articleno = {16},
numpages = {8},
keywords = {Bayesian belief networks, FLOSS, agent-based simulation, data-based models, software engineering},
location = {Vancouver, British Columbia, Canada},
series = {PROMISE '09}
}

@inproceedings{10.1145/3183440.3195047,
author = {Zhang, Yuxia and Tan, Xin and Zhou, Minghui and Jin, Zhi},
title = {Companies' domination in FLOSS development: an empirical study of OpenStack},
year = {2018},
isbn = {9781450356633},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3183440.3195047},
doi = {10.1145/3183440.3195047},
abstract = {Because of the increasing acceptance and possibly expanding market of free/libre open source software (FLOSS), the spectrum and scale of companies that participate in FLOSS development have substantially expanded in recent years. Companies get involved in FLOSS projects to acquire user innovations [3, 12], to reduce costs [8, 11], to make money on complementary services [13], etc. Such intense involvement may change the nature of FLOSS development and pose critical challenges for the sustainability of the projects. For example, it has been found that a company's full control and intense involvement is associated with a decrease of volunteer inflow [13]. Sometimes a project may fail after one company pulls resources from the project [13]. This raises concerns about the domination of one company in a project. In large projects like OpenStack, there are often hundreds of companies involved in contributing code. Despite substantial researches on commercial participation, whether or not one company dominates a project and the impact of such domination has never been explicitly explored. We investigate four main projects of OpenStack, a large ecosystem that has had a tremendous impact on computing and society, to answer the following research questions: Does one company dominate the project's development (RQ1)? If the answer to RQ1 is yes, does the domination affect the community (RQ2)?},
booktitle = {Proceedings of the 40th International Conference on Software Engineering: Companion Proceeedings},
pages = {440–441},
numpages = {2},
location = {Gothenburg, Sweden},
series = {ICSE '18}
}

@inproceedings{10.5555/3666122.3666579,
author = {Engelken, Rainer},
title = {Gradient flossing: improving gradient descent through dynamic control of jacobians},
year = {2023},
publisher = {Curran Associates Inc.},
address = {Red Hook, NY, USA},
abstract = {Training recurrent neural networks (RNNs) remains a challenge due to the instability of gradients across long time horizons, which can lead to exploding and vanishing gradients. Recent research has linked these problems to the values of Lyapunov exponents for the forward-dynamics, which describe the growth or shrinkage of infinitesimal perturbations. Here, we propose gradient flossing, a novel approach to tackling gradient instability by pushing Lyapunov exponents of the forward dynamics toward zero during learning. We achieve this by regularizing Lyapunov exponents through backpropagation using differentiable linear algebra. This enables us to "floss" the gradients, stabilizing them and thus improving network training. We demonstrate that gradient flossing controls not only the gradient norm but also the condition number of the long-term Jacobian, facilitating multidimensional error feedback propagation. We find that applying gradient flossing prior to training enhances both the success rate and convergence speed for tasks involving long time horizons. For challenging tasks, we show that gradient flossing during training can further increase the time horizon that can be bridged by backpropagation through time. Moreover, we demonstrate the effectiveness of our approach on various RNN architectures and tasks of variable temporal complexity. Additionally, we provide a simple implementation of our gradient flossing algorithm that can be used in practice. Our results indicate that gradient flossing via regularizing Lyapunov exponents can significantly enhance the effectiveness of RNN training and mitigate the exploding and vanishing gradients problem.},
booktitle = {Proceedings of the 37th International Conference on Neural Information Processing Systems},
articleno = {457},
numpages = {28},
location = {New Orleans, LA, USA},
series = {NIPS '23}
}

@inproceedings{10.1145/3576915.3623188,
author = {Yang, Su and Xiao, Yang and Xu, Zhengzi and Sun, Chengyi and Ji, Chen and Zhang, Yuqing},
title = {Enhancing OSS Patch Backporting with Semantics},
year = {2023},
isbn = {9798400700507},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3576915.3623188},
doi = {10.1145/3576915.3623188},
abstract = {Keeping open-source software (OSS) up to date is one potential solution to prevent known vulnerabilities. However, it requires frequent and costly testing and may introduce compatibility issues. Consequently, developers often choose to backport security patches to the vulnerable versions instead. Manual backporting is time-consuming, especially for large OSS such as the Linux kernel. Therefore, automating this process is urgently needed to save considerable time. Existing automated approaches for backporting patches involve either automatic patch generation or automatic patch migration. However, these methods are often ineffective and error-prone since they failed to locate the precise patch locations or generate the correct patch, operating only on the syntactic level.In this paper, we propose a patch type-sensitive approach to automatically backport OSS security patches, guided by the patch type and patch semantics. Specifically, our approach identifies patch locations with the aid of program dependency graph-based matching at the semantic level. It further applies fine-grained patch migration and fine-tuning based on patch types. We have implemented our approach in a tool named TSBPORT and evaluated it on a large-scale dataset consisting of 1,815 pairs of real-world security patches for the Linux kernel. The evaluation results show that TSBPORT successfully backported 1,589 (87.59\%) patches, out of which 587 (32.34\%) could not be backported by any state-of-the-art approaches, significantly outperforming state-of-the-art approaches. In addition, experiments also show that TSBPORT can be generalized to backport patches in other OSS projects with a success rate of 88.18\%.},
booktitle = {Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security},
pages = {2366–2380},
numpages = {15},
keywords = {patch backporting, patch semantics, patch type},
location = {Copenhagen, Denmark},
series = {CCS '23}
}

@inproceedings{10.5555/1260984.1261210,
author = {English, Robert and Schweik, Charles M.},
title = {Identifying Success and Tragedy of FLOSS Commons: A Preliminary Classification of Sourceforge.net Projects},
year = {2007},
isbn = {0769528309},
publisher = {IEEE Computer Society},
address = {USA},
abstract = {Free/Libre and Open Source Software (FLOSS) projects are a form of commons where individuals work collectively to produce software that is a public, rather than a private, good. The famous phrase "Tragedy of the Commons” describes a situation where a natural resource commons, such as a pasture, or a water supply, gets depleted because of overuse. The tragedy in FLOSS commons is distinctly different -- it occurs when collective action ceases before a software product is produced or reaches its full potential. This paper builds on previous work about defining success in FLOSS projects by taking a collective action perspective. We first report the results of interviews with FLOSS developers regarding our ideas about success and failure in FLOSS projects. Building on those interviews and previous work, we then describe our criteria for defining success/tragedy in FLOSS commons. Finally, we discuss the results of a preliminary classification of nearly all projects hosted on Sourceforge.net as of August 2006.},
booktitle = {Proceedings of the 29th International Conference on Software Engineering Workshops},
pages = {131},
series = {ICSEW '07}
}

@inproceedings{10.1007/978-3-031-78090-5_10,
author = {Miura, Chiaki and Ito, Kensuke},
title = {Incentivize Peer Review Without Rewarding: Using OSS-Like Citation Pull Request},
year = {2024},
isbn = {978-3-031-78089-9},
publisher = {Springer-Verlag},
address = {Berlin, Heidelberg},
url = {https://doi.org/10.1007/978-3-031-78090-5_10},
doi = {10.1007/978-3-031-78090-5_10},
abstract = {Scholarly communication is experiencing significant growth in publication volume. However, due to a lack of incentives, the current peer review system struggles to secure a sufficient number of diverse referees. Learning from the recent success in Open-Source Software (OSS) development, several alternative review models have been proposed, though none have focused on the mechanisms behind contribution-driven development. We introduce Push Citation, which combines a reversed citation with a revision to prior articles. Citation metrics incentivize article owners to perform reviews and encourage contributors to make suggestions. An experiment on workload balancing demonstrates that Push Citation is robust against the increasing demand for reviews and the uneven distribution of the burden. Potential drawbacks and countermeasures are also discussed.},
booktitle = {Information Integration and Web Intelligence: 26th International Conference, IiWAS 2024, Bratislava, Slovak Republic, December 2–4, 2024, Proceedings, Part I},
pages = {110–124},
numpages = {15},
keywords = {Incentivize Peer Review, Open Science, Open-Source Software, Scholarly Communication},
location = {Bratislava, Slovakia}
}

@inproceedings{10.1109/FLOSS.2007.9,
author = {English, Robert and Schweik, Charles M.},
title = {Identifying Success and Tragedy of FLOSS Commons: A Preliminary Classification of Sourceforge.net Projects},
year = {2007},
isbn = {0769529615},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/FLOSS.2007.9},
doi = {10.1109/FLOSS.2007.9},
abstract = {Free/Libre and Open Source Software (FLOSS) projects are a form of commons where individuals work collectively to produce software that is a public, rather than a private, good. The famous phrase "Tragedy of the Commons" describes a situation where a natural resource commons, such as a pasture, or a water supply, gets depleted because of overuse. The tragedy in FLOSS commons is distinctly different -- it occurs when collective action ceases before a software product is produced or reaches its full potential. This paper builds on previous work about defining success in FLOSS projects by taking a collective action perspective. We first report the results of interviews with FLOSS developers regarding our ideas about success and failure in FLOSS projects. Building on those interviews and previous work, we then describe our criteria for defining success/tragedy in FLOSS commons. Finally, we discuss the results of a preliminary classification of nearly all projects hosted on Sourceforge.net as of August 2006.},
booktitle = {Proceedings of the First International Workshop on Emerging Trends in FLOSS Research and Development},
pages = {11},
series = {FLOSS '07}
}

@inproceedings{10.1109/ICSE-SEET52601.2021.00009,
author = {Tan, Shin Hwei and Hu, Chunfeng and Li, Ziqiang and Zhang, Xiaowen and Zhou, Ying},
title = {GitHub-OSS fixit},
year = {2021},
isbn = {9780738133201},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/ICSE-SEET52601.2021.00009},
doi = {10.1109/ICSE-SEET52601.2021.00009},
abstract = {Many studies have shown the benefits of introducing open-source projects into teaching Software Engineering (SE) courses. However, there are several limitations of existing studies that limit the wide adaptation of open-source projects in a classroom setting, including (1) the selected project is limited to one particular project, (2) most studies only investigated on its effect on teaching a specific SE concept, and (3) students may make mistakes in their contribution which leads to poor quality code. Meanwhile, software companies have successfully launched programs like Google Summer of Code (GSoC) and FindBugs "fixit" to contribute to open-source projects. Inspired by the success of these programs, we propose GitHub-OSS Fixit, a team-based course project where students are taught to contribute to open-source Java projects by fixing bugs reported in GitHub. We described our course outline to teach students SE concepts by encouraging the usages of several automated program analysis tools. We also included the carefully designed instructions that we gave to students for participating in GitHub-OSS Fixit. As all lectures and labs are conducted online, we think that our course design could help in guiding future online SE courses. Overall, our survey results show that students think that GitHub-OSS Fixit could help them to improve many skills and apply the knowledge taught in class. In total, 154 students have submitted 214 pull requests to 24 different Java projects, in which 93 of them have been merged, and 46 have been closed by developers.},
booktitle = {Proceedings of the 43rd International Conference on Software Engineering: Joint Track on Software Engineering Education and Training},
pages = {1–10},
numpages = {10},
keywords = {open-source software, program repair, software engineering},
location = {Virtual Event, Spain},
series = {ICSE-JSEET '21}
}

@inproceedings{10.1145/3611643.3616288,
author = {Fronchetti, Felipe and Shepherd, David C. and Wiese, Igor and Treude, Christoph and Gerosa, Marco Aur\'{e}lio and Steinmacher, Igor},
title = {Do CONTRIBUTING Files Provide Information about OSS Newcomers’ Onboarding Barriers?},
year = {2023},
isbn = {9798400703270},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3611643.3616288},
doi = {10.1145/3611643.3616288},
abstract = {Effectively onboarding newcomers is essential for the success of open source projects. These projects often provide onboarding guidelines in their ’CONTRIBUTING’ files (e.g., CONTRIBUTING.md on GitHub). These files explain, for example, how to find open tasks, implement solutions, and submit code for review. However, these files often do not follow a standard structure, can be too large, and miss barriers commonly found by newcomers. In this paper, we propose an automated approach to parse these CONTRIBUTING files and assess how they address onboarding barriers. We manually classified a sample of files according to a model of onboarding barriers from the literature, trained a machine learning classifier that automatically predicts the categories of each paragraph (precision: 0.655, recall: 0.662), and surveyed developers to investigate their perspective of the predictions’ adequacy (75\% of the predictions were considered adequate). We found that CONTRIBUTING files typically do not cover the barriers newcomers face (52\% of the analyzed projects missed at least 3 out of the 6 barriers faced by newcomers; 84\% missed at least 2). Our analysis also revealed that information about choosing a task and talking with the community, two of the most recurrent barriers newcomers face, are neglected in more than 75\% of the projects. We made available our classifier as an online service that analyzes the content of a given CONTRIBUTING file. Our approach may help community builders identify missing information in the project ecosystem they maintain and newcomers can understand what to expect in CONTRIBUTING files.},
booktitle = {Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering},
pages = {16–28},
numpages = {13},
keywords = {FLOSS, novices, onboarding, open source, software engineering},
location = {San Francisco, CA, USA},
series = {ESEC/FSE 2023}
}

@inproceedings{10.1109/GHTC.2011.82,
author = {Babu, Satish},
title = {FOSS as a Tool for Development: The Kerala Experience},
year = {2011},
isbn = {9780769545950},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/GHTC.2011.82},
doi = {10.1109/GHTC.2011.82},
abstract = {The mainstreaming of Free and Open Source Software(FOSS) has been one of the most visible changes inthe domain of software in the last decade. Starting out as arallying point for techno-activists, FOSS is today a valued optionsupported by Governments, Businesses as well as the civil societyin most parts of the word. The State of Kerala in southernIndia, already quite unique on a variety of social, democratic andpolitical indicators, was the first to adopt FOSS as an instrumentof State policy in 2001. As it celebrates a decade of FOSS in 2011,Kerala demonstrates the remarkable transition of FOSS into acost-effective, pragmatic, and technologically sound strategy thatsimultaneously upholds the principles of freedom and democracy.Given that software is set to permeate most aspects of humanendeavor, the use of FOSS is an example for a highly sustainable -- socially, politically and technologically -- model of use of ICTs forhumanity.},
booktitle = {Proceedings of the 2011 IEEE Global Humanitarian Technology Conference},
pages = {108–110},
numpages = {3},
keywords = {FOSS, Free Software, Kerala, Open Source, Sustainable Development},
series = {GHTC '11}
}

@inproceedings{10.1109/GHTC.2011.78,
author = {Tucker, Allen and Morelli, Ralph and Lanerolle, Trishan de},
title = {The Humanitarian FOSS Project: Goals, Activities, and Outcomes},
year = {2011},
isbn = {9780769545950},
publisher = {IEEE Computer Society},
address = {USA},
url = {https://doi.org/10.1109/GHTC.2011.78},
doi = {10.1109/GHTC.2011.78},
abstract = {Begun in 2006, the Humanitarian Free and Open Source Software Project (HFOSS Project) is an educational initiative whose goal is to engage undergraduates in computer science by building free and open source software that benefits humanity, both locally and globally. During its short lifetime, the Project has inspired increasing numbers of students and instructors to make significant contributions to several humanitarian open source software development projects. In the last four years, the HFOSS Project has received material support from several partners, including the National Science Foundation, Accenture, Google, and Mozilla. This support has enabled the Project to expand its reach to add new college and university partners and to add more humanitarian software projects. Contributions to the HFOSS Project come from professionals in academia, IT organizations, and non-profit organizations that engage undergraduate students in courses, research projects, and summer internship experiences. Its curriculum is accessible to a wide range of undergraduates, since it includes courses for non- majors as well as computer science and engineering majors. This paper describes all these activities and their impact on undergraduate computing education, local non-profit organizations, and global FOSS communities. It concludes by identifying the progress that the HFOSS Project has made toward developing a sustainable infrastructure.},
booktitle = {Proceedings of the 2011 IEEE Global Humanitarian Technology Conference},
pages = {98–101},
numpages = {4},
keywords = {curriculum, education, humanitarian, open source, software engineering, tools and techniques},
series = {GHTC '11}
}

@inproceedings{10.1007/978-3-031-64171-8_4,
author = {Kree, Lukas and Helmke, Ren\'{e} and Winter, Eugen},
title = {Using Semgrep OSS to Find OWASP Top 10 Weaknesses in PHP Applications: A Case Study},
year = {2024},
isbn = {978-3-031-64170-1},
publisher = {Springer-Verlag},
address = {Berlin, Heidelberg},
url = {https://doi.org/10.1007/978-3-031-64171-8_4},
doi = {10.1007/978-3-031-64171-8_4},
abstract = {Given PHP’s continuous success, it remains an important task to ensure security in its applications. While code reviews are a common measure to catch bugs during development, they lack scalability, are error-prone, and time-consuming [2, 38, 41]. Thus, static analysis tools like Semgrep emerged to provide programmatic feedback on code. But static analyses often show low precision, which can jeopardize utility.In this case study, we investigate precision rates for Semgrep OSS for common web weaknesses from the OWASP Top 10 [35]. We explore method and tool limitations in weakness detection, OWASP classes, and Semgrep’s public PHP rule set. We apply the latter to 300 open source applications, invest 34 h in manual sample validation, and derive precision rates for each OWASP class.Our validation shows that the rules correctly detected weaknesses for seven OWASP classes with 86\% precision, demonstrating the tool’s utility. Yet, we estimate that most findings are not exploitable (81\%). Thus, there is still considerable assessment overhead for users. Our work further highlights that only a subset of weaknesses are detectable, as dimensions such as runtime context and insecure design remain hidden. Finally, we advise practitioners to not exclusively rely on public rules, as translating application-specific business logic and design choices may open up to the detection of previously uncovered weaknesses.},
booktitle = {Detection of Intrusions and Malware, and Vulnerability Assessment: 21st International Conference, DIMVA 2024, Lausanne, Switzerland, July 17–19, 2024, Proceedings},
pages = {64–83},
numpages = {20},
location = {Lausanne, Switzerland}
}

@inproceedings{10.1145/3611643.3617849,
author = {Nguyen, Emily},
title = {Do All Software Projects Die When Not Maintained? Analyzing Developer Maintenance to Predict OSS Usage},
year = {2023},
isbn = {9798400703270},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3611643.3617849},
doi = {10.1145/3611643.3617849},
abstract = {Abstract:  Past research suggests software should be continuously maintained in order to remain useful in our digital society. To determine whether these studies on software evolution are supported in modern-day software libraries, we conduct a natural experiment on 26,050 GitHub repositories, statistically modeling library usage based on their package-level downloads against different factors related to project maintenance.},
booktitle = {Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering},
pages = {2195–2197},
numpages = {3},
keywords = {Open Source, Open Source Sustainability, Survival Analysis},
location = {San Francisco, CA, USA},
series = {ESEC/FSE 2023}
}

@inproceedings{10.1145/3589335.3651559,
author = {Russo Latona, Giuseppe and Gote, Christoph and Zingg, Christian and Casiraghi, Giona and Verginer, Luca and Schweitzer, Frank},
title = {Shock! Quantifying the Impact of Core Developers' Dropout on the Productivity of OSS Projects},
year = {2024},
isbn = {9798400701726},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3589335.3651559},
doi = {10.1145/3589335.3651559},
abstract = {Open Source Software (OSS) projects play a critical role in the digital infrastructure of companies and services provided to millions of people. Given their importance, understanding the resilience of OSS projects is paramount. A primary reason for OSS project failure is the shock caused by the dropout of a core developer, which can jeopardize productivity and project survival. Using a difference-in-differences (DiD) analysis, this study investigates the repercussions of this shock on the productivity of 8,234 developers identified among 9,573 OSS GitHub projects. Our findings reveal the indirect impact of the core developer's dropout. The remaining developers experienced a 20\% productivity drop. This observation is troubling because it suggests that the shock might push other developers to drop out, putting the collaboration structure of the project at risk. Also, projects with higher productivity before the shock experienced a larger drop-down after the shock. This points to a tradeoff between productivity and resilience, i.e., the ability of OSS projects to recover from the dropout of a core developer. Our findings underscore the importance of a balanced approach in OSS project management, harmonizing productivity goals with resilience considerations.},
booktitle = {Companion Proceedings of the ACM Web Conference 2024},
pages = {706–709},
numpages = {4},
keywords = {causal inference, online collaboration networks, resilience},
location = {Singapore, Singapore},
series = {WWW '24}
}

@inproceedings{10.1145/3478905.3478923,
author = {Liu, Peng and Gui, Liang},
title = {Structural Analysis of Collaboration Network in OSS Communities∗},
year = {2021},
isbn = {9781450390248},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3478905.3478923},
doi = {10.1145/3478905.3478923},
abstract = {The success of open-source software (OSS) depends on the self-organizing collaboration of developers and the structure of developer collaboration network are intensively investigated in the literature. However, the research on the relationship between network structure and developers’ contribution is still insufficient. This paper investigates developer collaboration networks in three OSS communities by data analytics. The results indicate that real networks are mainly characterized by the modular small-world structure, which is inherently correlated with the sub-project participation of developers. Most module members are single-dimensional developers whose coding-collaboration focuses on a small number of sub-projects (called the main dimension of the module), while a small proportion of module members are multi-dimensional developers who conduct coding-collaboration in the main dimension of different modules. These results may deepen our understandings of the collaborative pattern of OSS communities, and also have some reference value for the studies of open collaborative innovation in large-scale crowds.},
booktitle = {2021 4th International Conference on Data Science and Information Technology},
pages = {84–91},
numpages = {8},
location = {Shanghai, China},
series = {DSIT 2021}
}

@inproceedings{10.1109/ICSE48619.2023.00218,
author = {Guizani, Mariam and Castro-Guzman, Aileen Abril and Sarma, Anita and Steinmacher, Igor},
title = {Rules of Engagement: Why and How Companies Participate in OSS},
year = {2023},
isbn = {9781665457019},
publisher = {IEEE Press},
url = {https://doi.org/10.1109/ICSE48619.2023.00218},
doi = {10.1109/ICSE48619.2023.00218},
abstract = {Company engagement in open source (OSS) is now the new norm. From large technology companies to startups, companies are participating in the OSS ecosystem by open-sourcing their technology, sponsoring projects through funding or paid developer time. However, our understanding of the OSS ecosystem is rooted in the "old world" model where individual contributors sustain OSS projects. In this work, we create a more comprehensive understanding of the hybrid OSS landscape by investigating what motivates companies to contribute and how they contribute to OSS. We conducted interviews with 20 participants who have different roles (e.g., CEO, OSPO Lead, Ecosystem Strategist) at 17 different companies of different sizes from large companies (e.g. Microsoft, RedHat, Google, Spotify) to startups. Data from semi-structured interviews reveal that company motivations can be categorized into four levels (Founders' Vision, Reputation, Business Advantage, and Reciprocity) and companies participate through different mechanisms (e.g., Developers' Time, Mentoring Time, Advocacy \& Promotion Time), each of which tie to the different types of motivations. We hope our findings nudge more companies to participate in the OSS ecosystem, helping make it robust, diverse, and sustainable.},
booktitle = {Proceedings of the 45th International Conference on Software Engineering},
pages = {2617–2629},
numpages = {13},
keywords = {open source, OSS, companies in open source, motivations, diversity},
location = {Melbourne, Victoria, Australia},
series = {ICSE '23}
}

@inproceedings{10.1145/3510003.3510196,
author = {Xiao, Wenxin and He, Hao and Xu, Weiwei and Tan, Xin and Dong, Jinhao and Zhou, Minghui},
title = {Recommending good first issues in GitHub OSS projects},
year = {2022},
isbn = {9781450392211},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3510003.3510196},
doi = {10.1145/3510003.3510196},
abstract = {Attracting and retaining newcomers is vital for the sustainability of an open-source software project. However, it is difficult for newcomers to locate suitable development tasks, while existing "Good First Issues" (GFI) in GitHub are often insufficient and inappropriate. In this paper, we propose RecGFI, an effective practical approach for the recommendation of good first issues to newcomers, which can be used to relieve maintainers' burden and help newcomers onboard. RecGFI models an issue with features from multiple dimensions (content, background, and dynamics) and uses an XGBoost classifier to generate its probability of being a GFI. To evaluate RecGFI, we collect 53,510 resolved issues among 100 GitHub projects and carefully restore their historical states to build ground truth datasets. Our evaluation shows that RecGFI can achieve up to 0.853 AUC in the ground truth dataset and outperforms alternative models. Our interpretable analysis of the trained model further reveals interesting observations about GFI characteristics. Finally, we report latest issues (without GFI-signaling labels but recommended as GFI by our approach) to project maintainers among which 16 are confirmed as real GFIs and five have been resolved by a newcomer.},
booktitle = {Proceedings of the 44th International Conference on Software Engineering},
pages = {1830–1842},
numpages = {13},
keywords = {good first issues, onboarding, open-source software},
location = {Pittsburgh, Pennsylvania},
series = {ICSE '22}
}