@inbook {1741,
	title = {First Results About Motivation and Impact of License Changes in Open Source Projects},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {137-145},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and open source software is characterized by the freedoms and criteria that are warranted by specific licenses. These licenses describe the rights and duties of the licensors and licensees. However, a licensing change may be necessary in the life of an open source project to meet legal developments or to allow the implementation of new business models. This paper examines the motivations and impacts of license changes in open source projects. After a state of the art on the subject, a set of case studies where projects changed their license is presented. Then a set of motivations to change licenses, the ways to legally make this change, the problems caused by this change and a set of benefits of the license change are discussed.
},
	keywords = {Business model, Contributor agreement, intellectual property, license, open source},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_13},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_13},
	author = {Viseur, Robert and Gregorio Robles},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@conference {789,
	title = {Legal issues of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {320-321},
	abstract = {From the legal standpoint, Open Source amounts to distributing rights and obligations in software license agreements in such a way, that they would (1) both grant users control over the program and (2) facilitate the sharing of improvements. The Open Source idea aims at reversing the process usually referred to as proprietary licensing and equaling the rights of the users with these of the authors. To some extent, it attempts to destroy monopolies created by copyright laws and to prevent them to arise again. There is much in the discussion on the legal issues of Open Source. The first voices came from the programmers who started the movement.},
	keywords = {cooperation, copyright law, freedom, intellectual property, legal issue, license, open source software},
	url = {http://pascal.case.unibz.it/handle/2038/974},
	author = {Siewicz, Krzysztof}
}
@article {flosswp77,
	title = {Guarding the Commons: How Community Managed Software Projects Protect Their Work},
	journal = {Research Policy},
	volume = {32},
	year = {2003},
	note = {"Data was collected from three primary sources: 1) observation at project and user group meetings, technical presentations and conferences; 2) informant interviews; and 3) project data archived on the Internet that detailed project interactions and structural developments."

"Project data was collected from online archives and included documents such as: mission statements, charters, bylaws, meeting minutes, and mailing list archives."},
	month = {February},
	pages = {1179-1198},
	edition = {7},
	abstract = {Theorists often speculate why open source and free software project contributors give their work away. Although contributors make their work publicly available, they do not forfeit their rights to it. Community managed software projects protect their work by using several legal and normative tactics, which should not be conflated with a disregard for or neglect of intellectual property rights. These tactics allow a project?s intellectual property to be publicly and freely available and yet, governable. Exploration of this seemingly contradictory state may provide new insight into governance models for the management of digital intellectual property.},
	keywords = {Common Pool Resources, email, email archives, intellectual property, mailing list, open source, Public Goods, Software, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-omahony.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
