@proceedings {1824, title = {Data Sets: The Circle of Life in Ruby Hosting, 2003-2015}, year = {2016}, month = {05/2016}, pages = {452-455}, publisher = {IEEE}, abstract = {Studying software repositories and hosting services can provide valuable insights into the behaviors of large groups of software developers and their projects. Traditionally, most analysis of metadata collected from hosting services has been conducted by specifying some short window of time, typically just a few years. To date, few - if any - studies have been built from data comprising the entirety of a repository{\textquoteright}s lifespan: from its birth to its death, and rebirth. Thus, the first contribution of this data set is to support the historical analysis of over ten years of collected metadata from the now-defunct RubyForge project hosting site, as well as the follow-on successor to RubyForge, the RubyGems hosting facility. The data sets and sample analyses in this paper will be relevant to researchers studying both software evolution and the distributed software development process.}, url = {https://docs.google.com/presentation/d/1rtdrwkfxt-p5gQBwMNT1WDlLMg0pJ4gxfM5jSAH-UUA/edit?usp=sharing}, attachments = {https://flosshub.org/sites/flosshub.org/files/preprint.pdf}, author = {Squire, Megan} } @proceedings {1854, title = {Differentiating Communication Styles of Leaders on the Linux Kernel Mailing List}, year = {2016}, note = {Slides link: https://docs.google.com/presentation/d/1_5kqOXBYwH33ayfGKCncCtCondfUYtsHSDBS3DBig6Y/edit?usp=sharing Edited to fix typo in abstract. New version is v3.pdf}, month = {08/2016}, publisher = {ACM}, abstract = {Much communication between developers of free, libre, and open source software (FLOSS) projects happens on email mailing lists. Geographically and temporally dispersed development teams use email as an asynchronous, centralized, persistently stored institutional memory for sharing code samples, discussing bugs, and making decisions. Email is especially important to large, mature projects, such as the Linux kernel, which has thousands of developers and a multi-layered leadership structure. In this paper, we collect and analyze data to understand the communication patterns in such a community. How do the leaders of the Linux Kernel project write in email? What are the salient features of their writing, and can we discern one leader from another? We find that there are clear written markers for two leaders who have been particularly important to recent discussions of leadership style on the Linux Kernel Mailing List (LKML): Linux Torvalds and Greg Kroah-Hartman. Furthermore, we show that it is straightforward to use a machine learning strategy to automatically differentiate these two leaders based on their writing. Our findings will help researchers understand how this community works, and why there is occasional controversy regarding differences in communication styles on the LKML.}, keywords = {email, flossmole, linus torvalds, linux, lkml}, attachments = {https://flosshub.org/sites/flosshub.org/files/v3_0.pdf}, author = {Schneider, Daniel and Spurlock, Scott and Squire, Megan} } @proceedings {1722, title = {The diffusion of pastebin tools to enhance communication in FLOSS mailing lists}, year = {2015}, month = {05/2015}, pages = {45-57}, abstract = {This paper describes how software developers who use mailing lists to communicate reacted and adjusted to a new supplementary collaboration tool, called a pastebin service. Using publicly-available archives of 8800 mailing lists, we examine the adoption of the pastebin tool by software developers and compare it to the model presented in Diffusion of Innovation (DoI) theory. We then compare the rate at which software developers decided whether to accept or reject the new pastebin tools. We find that the overall rate of pastebin adoption follows the S-curve predicted by classic DoI theory. We then compare the individual pastebin services and their rates of adoption, as well as the reaction of different communities to the new tools and the various rationales for accepting or rejecting them.}, doi = {http://dx.doi.org/10.1007/978-3-319-17837-0_5}, attachments = {https://flosshub.org/sites/flosshub.org/files/pastebinOSS2015Preprint.pdf}, author = {Squire, Megan and Smith, Amber} } @conference {1317, title = {Describing the Software Forge Ecosystem}, booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences}, year = {2012}, note = {http://flossmole.org/content/everything-you-ever-wanted-know-about-software-forges-code-forges-june-2011}, month = {01/2012}, pages = {3416-3425}, abstract = {Code forges are online software systems that are designed to support teams doing software development work. There have been few if any attempts in the research literature to describe the web of people, projects, and tools that make up the free, libre, and open source (FLOSS) forge ecosystem. The main contributions of this paper are (1) to introduce a classification of FLOSS-oriented forges according to their characteristics; (2) to describe the forge-level and project-level data and artifacts currently available at each FLOSS forge; (3) to show various patterns already discovered in the FLOSS forge ecosystem, such as timelines of creation or arrangements by size or feature; (4) to make some recommendations to forge providers and data collectors about how to expose the structure and information in the forges; and (5) to describe the effort needed to extend our publicly- available information about the FLOSS forge ecosystem into the future.}, keywords = {features, FLOSS, forge, hosting, metrics}, attachments = {https://flosshub.org/sites/flosshub.org/files/SquireWilliamsHICSS2012.pdf}, author = {Squire, Megan and Williams, David} } @conference {77, title = {Do the Rich Get Richer? The Impact of Power Laws on Open Source Development Projects}, booktitle = {2004 Open Source Conference (OSCON)}, year = {2004}, type = {conference presentation}, address = {Portland, OR, USA}, keywords = {open source, power law, social network analysis, sourceforge}, author = {Conklin, Megan} }