@article {1849,
	title = {Folding and unfolding : balancing openness and transparency in open source communities},
	journal = { Information Systems Research},
	year = {2016},
	publisher = {Institute for Operations Research and the Management Sciences},
	abstract = {Open source communities rely on the espoused premise of complete openness and transparency of source code and development process. Yet, openness and transparency at times need to be balanced out with moments of less open and transparent work. Through our detailed study of Linux Kernel development we build a theory that explains that transparency and openness are nuanced and changing qualities that certain developers manage as they use multiple digital technologies and create, in moments of needs, more opaque and closed digital spaces of work. We refer to these spaces as digital folds. Our paper contributes to extant literature: by providing a process theory of how transparency and openness are balanced with opacity and closure in open source communities according to the needs of the development work; by conceptualizing the nature of digital folds and their role in providing quiet spaces of work: and, by articulating how the process of digital folding and unfolding is made far more possible by select elite actors{\textquoteright} navigating the line between the pragmatics of coding and the accepted ideology of openness and transparency.

},
	url = {http://wrap.warwick.ac.uk/78627/},
	author = {Maha Shaikh and Vaast, Emmanuelle}
}
@proceedings {1283,
	title = {Framing the Conundrum of Total Cost of Ownership of Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {208-219},
	publisher = {Springer},
	abstract = {This paper reflects the results of phase I of our study on the total cost of ownership (TCO) of open source software adoption. Not only have we found TCO to be an intriguing issue but it is contentious, baffling and each company approaches it in a distinctive manner (and sometimes not at all). In effect it is a conundrum that needs unpacking before it can be explained and understood. Our paper discusses the components of TCO as total cost of ownership and total cost of acquisition (and besides). Using this broad dichotomy and its various components we then analyze our data to make sense of procurement decisions in relation to open source software in the public sector and private companies.},
	keywords = {benefits, exit costs, open source software, software adoption, Survey, tco, total cost of ownership},
	author = {Maha Shaikh and Cornford, Tony}
}
@conference {1255,
	title = {{\textquoteright}Letting go of Control{\textquoteright} to Embrace Open Source: Implications for Company and Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {It is increasingly understood across the information technology and services sector that engagement with the open source software model can serve as a means for firms to capture intellectual energy, learn about productive software processes, access relevant technical skills, identify and recruit staff, as well as obtain valuable resources including code. This paper reports a study undertaken within two large global IT companies that have been actively involved with open source for more than ten years. The study involved over 30 semi-structured interviews with employees of the companies drawn from top, middle, and lower level management, and included active and experienced developer as well as open source community members. Our findings indicate how these companies have adapted their day-to-day management practices to take into account the need for flexibility and freedom expected by open source communities. This paper focuses on how they {\textquoteright}let go of control{\textquoteright} and what the implications of this are for both companies and the communities involved. Our data reveals a number of themes and in this paper we focus on three principal ones; issues of requirements, total cost of adoption, and alignment of open source engagement with long term company strategy.},
	keywords = {adoption, companies, interviews, organizations},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-01.pdf},
	author = {Maha Shaikh and Cornford, Tony}
}
@conference {1646,
	title = {An Examination of the Use of Open Source Software Processes as a Global Software Development Solution for Commercial Software Engineering},
	booktitle = {2009 35th Euromicro Conference on Software Engineering and Advanced Applications},
	year = {2009},
	pages = {20 - 27},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Patras, Greece},
	abstract = {This paper outlines the phenomenon of Inner Source software development and places it in the context of existing open source literature. Our study includes an analysis of multiple case studies of Inner Source in use in large scale global software development companies. The lessons learned from these case studies help us to contrast traditional open source principles with Inner Source principles, and we then gather these lessons, to create our preliminary framework, in order to make sense of when and how firms can adopt Inner Source. Our framework helps to make sense of the practical issues of adopting and managing Inner Source. We have highlighted the emerging trends in the Inner Source phenomenon and surrounding areas. Awareness of this may be of great benefit to researchers in the area and industrial practitioners.},
	isbn = {978-0-7695-3784-9},
	doi = {10.1109/SEAA.2009.86},
	author = {Gaughan, Gary and Fitzgerald, Brian and Maha Shaikh}
}
@article {flosswp106,
	title = {Version Management Tools: CVS to BK in the Linux Kernel},
	year = {2003},
	month = {May},
	abstract = {Version management tools might be seen as a prerequisite for open source development today as projects become too large to be managed by maintainers alone. Yet the OS process depends on fluid coordination and collaboration, with the underlying qualities of this process based on firm trust and respect for fellow developers. This paper is a study of how debate over version tools reflects governance and decision making in an OS community. The paper is based on a study of the Linux kernel community as it first saw a partial acceptance of the CVS tool, and then later adopted BK. The paper explains the adoption processes in relation to governance concerns, licence issue, and questions of technical performance.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaikhcornford.pdf},
	author = {Maha Shaikh}
}
