@conference {1523,
	title = {Social coding in GitHub},
	booktitle = {Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work - CSCW {\textquoteright}12},
	year = {2012},
	pages = {1277},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Seattle, Washington, USA},
	abstract = {
Social applications on the web let users track and follow the activities of a large number of others regardless of location or affiliation. There is a potential for this transparency to radically improve collaboration and learning in complex knowledge-based activities. Based on a series of in-depth interviews with central and peripheral GitHub users, we examined the value of transparency for large-scale distributed collaborations and communities of practice. We find that people make a surprisingly rich set of social inferences from the networked activity information in GitHub, such as inferring someone else{\textquoteright}s technical goals and vision when they edit code, or guessing which of several similar projects has the best chance of thriving in the long term. Users combine these inferences into effective strategies for coordinating work, advancing technical skills and managing their reputation.
},
	keywords = {github},
	isbn = {9781450310864},
	doi = {10.1145/2145204.2145396},
	url = {http://www.cs.cmu.edu/afs/cs/Web/People/xia/resources/Documents/cscw2012_Github-paper-FinalVersion-1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw2012_Github-paper-FinalVersion-1.pdf},
	author = {Laura Dabbish and Colleen Stuart and Jason Tsay and Herbsleb, Jim}
}
@conference {1482,
	title = {Group awareness in distributed software development},
	booktitle = {2004 ACM conference on Computer supported cooperative work  - CSCW {\textquoteright}04},
	year = {2004},
	pages = {72-81},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Open-source software development projects are almost always collaborative and distributed. Despite the difficulties imposed by distance, these projects have managed to produce large, complex, and successful systems. However, there is still little known about how open-source teams manage their collaboration. In this paper we look at one aspect of this issue: how distributed developers maintain group awareness. We interviewed developers, read project communication, and looked at project artifacts from three successful open source projects. We found that distributed developers do need to maintain awareness of one another, and that they maintain both a general awareness of the entire team and more detailed knowledge of people that they plan to work with. Although there are several sources of information, this awareness is maintained primarily through text-based communication (mailing lists and chat systems). These textual channels have several characteristics that help to support the maintenance of awareness, as long as developers are committed to reading the lists and to making their project communication public.},
	keywords = {email, email archive, mailing list},
	isbn = {1581138105},
	doi = {10.1145/1031607.1031621},
	author = {Schneider, Kevin and Gutwin, Carl and Penner, Reagan}
}
