@proceedings {1905,
	title = {Longitudinal Analysis of the Run-up to a Decision to Break-up (Fork) in a Community},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {204-217},
	publisher = {Springer},
	abstract = {In this paper, we use a developer-oriented statistical approach to understand what causes people in complex software development networks to decide to fork (break away), and what changes a community goes through in the run-up to a decision to break-up. Developing complex software systems is complex. Software developers interact. They may have the same or different goals, communication styles, or values. Interactions can be healthy or troubled. Troubled interactions cause troubled communities, that face failure. Some of these failures manifest themselves as a community split (known as forking). These failures affects many people; developers and users. Can we save troubled projects? We statistically model the longitudinal socio-grams of software developers and present early indicators and warning signs that can be used to predict an imminent break-up decision.

},
	keywords = {community of software developers, forks, longitudinal study},
	doi = {10.1007/978-3-319-57735-7_19},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_19},
	author = {Amirhosein {\textquotedblleft}Emerson{\textquotedblright} Azarbakht and Jensen, Carlos}
}
@book {1590,
	title = {Drawing the Big Picture: Temporal Visualization of Dynamic Collaboration Graphs of OSS Software Forks},
	series = {10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings},
	volume = {427},
	year = {2014},
	pages = {41 - 50},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {How can we understand FOSS collaboration better? Can social issues that emerge be identified and addressed as they happen? Can the community heal itself, become more transparent and inclusive, and promote diversity? We propose a technique to address these issues by quantitative analysis and temporal visualization of social dynamics in FOSS communities. We used social network analysis metrics to identify growth patterns and unhealthy dynamics; This gives the community a heads-up when they can still take action to ensure the sustainability of the project.},
	isbn = {978-3-642-55128-4},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-55128-4_5},
	author = {Amir Azarbakht and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.}
}
@inbook {1615,
	title = {An Exploration of Code Quality in FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {181-190},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

It is a widely held belief that Free/Open Source Software (FOSS) development leads to the creation of software with the same, if not higher quality compared to that created using proprietary software development models. However there is little research on evaluating the quality of FOSS code, and the impact of project characteristics such as age, number of core developers, code-base size, etc. In this exploratory study, we examined 110 FOSS projects, measuring the quality of the code and architectural design using code smells. We found that, contrary to our expectations, the overall quality of the code is not affected by the size of the code base, but that it was negatively impacted by the growth of the number of code contributors. Our results also show that projects with more core developers don{\textquoteright}t necessarily have better code quality.
},
	keywords = {Code Quality, FOSS, open source software, success metrics},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_26},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_26},
	author = {Ahmed, Iftekhar and Ghorashi, Soroush and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@inbook {1607,
	title = {Lessons Learned from Teaching Open Source Software Development},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {133-142},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Free/Open Source Software allows students to learn valuable real world skills and experiences, as well as a create a portfolio to show future employers. However, the learning curve to joining FOSS can be daunting, often leading newcomers to walk away frustrated. Universities therefore need to find ways to provide a structured introduction to students, helping them overcome the barriers to entry. This paper describes two courses taught at two universities, built around a Communities of Practice model, and the lessons learned from these. Suggestions and insights are shared for how to structure and evaluate such courses for maximum effect.
},
	keywords = {education, FOSS, Free/Open Source Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_18},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_18},
	author = {Morgan, Becka and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1691,
	title = {Older Adults and Free/Open Source Software},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The global population is aging rapidly, and older adults are becoming increasingly technically savvy. This paper explores ways to engage these individuals to contribute to free/open source software (FOSS) projects. We conducted a pilot diary study to explore motivations, barriers, and the contribution processes of first-time contributors in a real time, qualitative manner. In addition, we measured their self-efficacy before and after their participation. We found that what drove participants were intrinsic motivations, altruism, and internal values, which differed from previous work with older adults and with the general FOSS population. We also found that self-efficacy did not change significantly, even when participants encountered significant barriers or setbacks. The top 3 barriers were lack of communication, installation issues, and documentation issues. We found that asking for and receiving help, and avoiding difficult development environments were more likely to lead to success. To verify these results, we encourage a future large-scale diary study that involves multiple demographics. Given our pilot study, we recommend that future outreach efforts involving older adults focus on how to effectively communicate and build community amongst older contributors.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641589},
	author = {Davidson, Jennifer and Umme Ayda Mannan and Rithika Naik and Ishneet Dua and Jensen, Carlos}
}
@book {1545,
	title = {Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {232 - 244},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

In this exploratory study, we map the use of free and open source software (FOSS) in the United States energy sector, especially as it relates to cyber security. Through two surveys and a set of semi-structured interviews{\textemdash}targeting both developers and policy makers{\textemdash}we identified key stakeholders, organizations, and FOSS projects, be they rooted in industry, academia, or public policy space that influence software and security practices in the energy sector. We explored FOSS tools, common attitudes and concerns, and challenges with regard to FOSS adoption. More than a dozen themes were identified from interviews and surveys. Of these, drivers for adoption and risks associated with FOSS were the most prevalent. More specifically, the misperceptions of FOSS, the new security challenges presented by the smart grid, and the extensive influence of vendors in this space play the largest roles in FOSS adoption in the energy sector.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_17},
	author = {Kuechler, Victor and Jensen, Carlos and Bryant, Deborah},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1451,
	title = {Exploring the Role of Outside Organizations in Free / Open Source Software Projects},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {201-215},
	publisher = {IFIP AICT},
	abstract = {Free/Open Source Software (FOSS) projects have a reputation for being grass-roots efforts driven by individual contributors volunteering their time and effort. While this may be true for a majority of smaller projects, it is not always the case for large projects. As projects grow in size, importance and complexity, many come to depend on corporations, universities, NGO{\textquoteright}s and governments, for support and contributions, either financially or through seconded staff. As outside organizations get involved in projects, how does this affect their governance, transparency and direction? To study this question we gathered bug reports and commit logs for GCC and the Linux Kernel. We found that outside organizations contribute a majority of code but rarely participate in bug triaging. Therefore their code does not necessarily address the needs of others and may distort governance and direction. We conclude that projects should examine their dependence on outside organizations},
	keywords = {bug reports, commit, Community sustainability, Contributor affiliation, gcc, governance, linux kernel, Participation metrics},
	url = {http://research.engr.oregonstate.edu/hci/sites/research.engr.oregonstate.edu.hci/files/papers/forrest2012exploring.pdf},
	author = {Forrest, Darren and Jensen, Carlos and Mohan, Nitin and Davidson, Jennifer}
}
@proceedings {1444,
	title = {Gender Differences in Early Free and Open Source Software Joining Process},
	volume = {378},
	year = {2012},
	note = {"We examined subscriber logs and data for six FOSS projects..."
"We examined the differences between posters and non-posters to determine the attrition rate..."
"Using data from the US Census, we matched names to lists of the most common female and male names. We identified 666 users using this process."},
	month = {09/2012},
	pages = {78-93},
	publisher = {IFIP AICT, Springer},
	address = {Eighth International Conference on Open Source Systems (OSS 2012)},
	abstract = {With the growth of free and open source software (FOSS) and the adoption of FOSS solutions in business and everyday life, it is important that projects serve their growingly diverse user base. The sustainability of FOSS projects relies on a constant influx of new contributors. Several large demo- graphic surveys found that FOSS communities are very homogenous, dominated by young men, similar to the bias existing in the rest of the IT workforce. Building on previous research, we examine mailing list subscriptions and posting statistics of female FOSS participants. New participants often experience their first interaction on a FOSS project{\textquoteright}s mailing list. We explored six FOSS projects {\textendash} Buildroot, Busybox, Jaws, Parrot, uClibc, and Yum. We found a declining rate of female participation from the 8.27\% of subscribers, to 6.63\% of posters, and finally the often reported code contributor rate of 1.5\%. We found a disproportionate attrition rate among women along every step of the FOSS joining process.},
	keywords = {buildroot, busybox, diversity, email, jaws, joining process, mailing lists, parrot, uClibc, Yum},
	author = {Kuechler, Victor and Gilbertson, Claire and Jensen, Carlos}
}
@conference {1481,
	title = {Joining Free/Open Source Software Communities: An Analysis of Newbies{\textquoteright} First Interactions on Project Mailing Lists},
	booktitle = {2011 44th Hawaii International Conference on System Sciences (HICSS 2011)},
	year = {2011},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Kauai, HI},
	abstract = {Free/Open source software (FOSS) is an important part of the IT ecosystem. Due to the voluntary nature of participation, continual recruitment is key to the growth and sustainability of these communities. It is therefore important to understand how and why potential contributors fail in the process of transitioning from user to contributor. Most newcomers, or "newbies", have their first interaction with a community through a mailing list. To understand how this first contact influences future interactions, we studied eight mailing lists across four FOSS projects: MediaWiki, GIMP, PostgreSQL, and Subversion. We analyzed discussions initiated by newbies to determine the effect of gender, nationality, politeness, helpfulness and timeliness of response. We found that nearly 80\% of newbie posts received replies, and that receiving timely responses, especially within 48 hours, was positively correlated with future participation. We also found that while the majority of interactions were positive, 1.5\% of responses were rude or hostile.},
	keywords = {email, email archive, gimp, mailing list, mediawiki, postgresql, subversion},
	isbn = {978-1-4244-9618-1},
	doi = {10.1109/HICSS.2011.264},
	author = {Jensen, Carlos and King, Scott and Kuechler, Victor}
}
@conference {Yatani:2009:UWO:1518701.1518853,
	title = {Understanding how and why open source contributors use diagrams in the development of Ubuntu},
	booktitle = {Proceedings of the 27th international conference on Human factors in computing systems},
	series = {CHI {\textquoteright}09},
	year = {2009},
	note = {"To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort{\textemdash}Ubuntu."
"Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants{\textquoteright} OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants."},
	pages = {995{\textendash}1004},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.},
	keywords = {developers, diagramming, interviews, open source software (oss), software development, Ubuntu, visual representation},
	isbn = {978-1-60558-246-7},
	doi = {http://doi.acm.org/10.1145/1518701.1518853},
	url = {http://doi.acm.org/10.1145/1518701.1518853},
	author = {Yatani, Koji and Chung, Eunyoung and Jensen, Carlos and Truong, Khai N.}
}
