@article {1087,
	title = {Reflecting on 10 Years of the TIM Review},
	journal = {Technology Innovation Management Review},
	volume = {7},
	year = {2017},
	month = {07/2017},
	pages = {5-20},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {In July 2007, the first issue of this journal was published under the banner of the Open Source Business Resource. Re-launched with a broader scope in 2011 as the Technology Innovation Management Review, the journal now celebrates its 10th anniversary. In this article, we review the 10-year history of the journal to examine what themes have been covered, who has contributed, and how much the articles have been read and cited. During those 10 years, the journal has published 120 monthly issues, including more than 800 publications by more than 800 international authors from industry, academia, the public sector, and beyond. As discovered with topic modelling, the journal has covered seven themes: open source business, technology entrepreneurship, growing a business, research approaches, social innovation, living labs, and cybersecurity. Overall, the website has attracted over 1 million readers from around the world {\textendash} 31\% from Asia, 30\% from the Americas, 26\% from Europe, 8\% from Africa, and 5\% from Oceania {\textendash} with over 25,000 readers now accessing the site each month. },
	keywords = {business, entrepreneurship, innovation, journal, management, open source, OSBR, research, scientometric analyses, technology, TIM Review, topic, topic modelling},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/1087},
	url = {http://timreview.ca/article/1087},
	author = {Chris McPhee and Teemu Santonen and Ahmed Shah and Ali Nazari}
}
@article {962,
	title = {Editorial: Cybersecurity (February 2016)},
	journal = {Technology Innovation Management Review},
	volume = {6},
	year = {2016},
	month = {02/2016},
	pages = {3-4},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {cybersecurity, intrusion, licensing, literature reviews, machine learning, malware, multisided platforms, new domains, open source},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/962},
	url = {http://timreview.ca/article/962},
	author = {Chris McPhee and Dan Craigen}
}
@article {966,
	title = {License Compliance in Open Source Cybersecurity Projects},
	journal = {Technology Innovation Management Review},
	volume = {6},
	year = {2016},
	month = {02/2016},
	pages = {28-35},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Developers of cybersecurity software often include and rely upon open source software packages in their commercial software products. Before open source code is absorbed into a proprietary product, developers must check the package license to see if the project is permissively licensed, thereby allowing for commercial-friendly inheritance and redistribution. However, there is a risk that the open source package license could be inaccurate due to being silently contaminated with restrictively licensed open source code that may prohibit the sale or confidentiality of commercial derivative work. Contamination of commercial products could lead to expensive remediation costs, damage to the company{\textquoteright}s reputation, and costly legal fees. In this article, we report on our preliminary analysis of more than 200 open source cybersecurity projects to identify the most frequently used license types and languages and to look for evidence of permissively licensed open source projects that are likely contaminated by restrictive licensed material (i.e., containing commercial-unfriendly code). Our analysis identified restrictive license contamination cases occurring in permissively licensed open source projects. Furthermore, we found a high proportion of code that lacked copyright attribution. We expect that the results of this study will: i) provide managers and developers with an understanding of how contamination can occur, ii) provide open source communities with an understanding on how they can better protect their intellectual property by including licenses and copyright information in their code, and ii) provide entrepreneurs with an understanding of the open source cybersecurity domain in terms of licensing and contamination and how they affect decisions about cybersecurity software architectures.},
	keywords = {contamination, copyright, cybersecurity, GPL, license, open source, third-party code},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/966},
	url = {http://timreview.ca/article/966},
	author = {Ahmed Shah and Selman Selman and Ibrahim Abualhaol}
}
@article {944,
	title = {Q\&A. In the Innovation Game, Why Do So Many Companies Stay on the Sidelines?},
	journal = {Technology Innovation Management Review},
	volume = {5},
	year = {2015},
	month = {11/2015},
	pages = {35-39},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {co-creation, co-innovation, collaboration, innovation, lead users, Open innovation, open source},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/944},
	url = {http://timreview.ca/article/944},
	author = {Katri Valkokari}
}
@article {757,
	title = {The Businesses of Open Data and Open Source: Some Key Similarities and Differences},
	journal = {Technology Innovation Management Review},
	volume = {4},
	year = {2014},
	month = {01/2014},
	pages = {12-17},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {business models, entrepreneurship, licensing, open data, open source},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/757},
	url = {http://timreview.ca/article/757},
	author = {Juho Lindman and Linus Nyman}
}
@article {758,
	title = {Overcoming Barriers to Collaboration in an Open Source Ecosystem},
	journal = {Technology Innovation Management Review},
	volume = {4},
	year = {2014},
	month = {01/2014},
	pages = {18-27},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Leveraging open source practices provides value to businesses when entrepreneurs and managers understand how to collaborate effectively in an open source ecosystem. However, the complex mix of different actors and varying barriers to effective collaboration in the ecosystem pose a substantial challenge. How can a business create and capture value if it depends on effective collaboration among these different groups? In this article, we review the published research on open source collaboration and reveal insights that will be beneficial to entrepreneurs and managers. We organize the published research into four streams based upon the following actor groups: i) governance actors, ii) competitors, iii) complementors, and iv) the core community. Then, through induction and synthesis, we identify barriers to collaboration, first by ecosystem and then by actor group. Finally, we offer six recommendations for identifying and overcoming barriers to collaboration in an open source ecosystem.},
	keywords = {business ecosystem, collaboration, collaboration barriers, communities, competitors, complementors, core community, governance, open source},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/758},
	url = {http://timreview.ca/article/758},
	author = {Derek Smith and Asrar Alshaikh and Rawan Bojan and Anish Kak and Mohammad Mehdi Gharaei Manesh}
}
@article {643,
	title = {Editorial: Open Source Sustainability (January 2013)},
	journal = {Technology Innovation Management Review},
	volume = {3},
	year = {2013},
	month = {01/2013},
	pages = {3-6},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {governance, open source, oss, sustainability},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/643},
	url = {http://timreview.ca/article/643},
	author = {Chris McPhee and Maha Shaikh}
}
@article {647,
	title = {Going Open: Does it Mean Giving Away Control?},
	journal = {Technology Innovation Management Review},
	volume = {3},
	year = {2013},
	month = {01/2013},
	pages = {27-31},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Open source software has evolved from being an effort driven by a collective of volunteers to become an integral part of commercial software. Constant demands for new features besides maintaining product quality made companies seek open source as an answer for these demands. These growing demands brought with them control of quality, architecture, contribution management, and community management. 

This article explores the governance strategies adopted by open source software projects to manage the quality of complements (such as plug-ins that extend a platform{\textquoteright}s functionality) developed by community members outside the core team. The outcomes of the research contribute to our understanding of the strategies followed by different open source platform owners (the open source project initiators) to manage external innovation in the case of platform extensions in two areas: i) governance models and ii) regulatory tools. },
	keywords = {and collaboration, governance, Open innovation, open source, platforms, regulatory tools},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/647},
	url = {http://timreview.ca/article/647},
	author = {Nadia Noori and Michael Weiss}
}
@article {650,
	title = {Q\&A. Is Open Source Sustainable?},
	journal = {Technology Innovation Management Review},
	volume = {3},
	year = {2013},
	month = {01/2013},
	pages = {46-49},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {Apache, GPL, licenses, open source, sustainability},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/650},
	url = {http://timreview.ca/article/650},
	author = {Matt Asay}
}
@article {649,
	title = {Sustainability and Governance in Developing Open Source Projects as Processes of In-Becoming},
	journal = {Technology Innovation Management Review},
	volume = {3},
	year = {2013},
	month = {01/2013},
	pages = {40-45},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Sustainability is often thought of as a binary state: an open source project is either sustainable or not. In reality, sustainability is much more complex. What makes this project more sustainable than that one? Why should it be assumed in the first place that sustainability is a prolonged state of an ingraced project? The threads are pulled from their yarns in many directions. 

This article attempts to reconceptualize some assumed notions of the processes involved in developing open source software. It takes the stance in favour of studying the fluctuant nature of open source and the associated artefacts, not as well-defined objects, but as commons that are continually built upon, evolved, and modified; sometimes in unexpected ways. Further, the governance of these commons is an ongoing process, tightly linked with the way in which these commons are allowed to further develop. This perspective of "in-becoming" is useful in understanding the efforts and processes that need to be provided to sustainably govern the development of open source projects and the advantages for managing requirements derived therein. 
},
	keywords = {becoming, emergence, governance, open source, Ostrom, processes, requirements, sustainability},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/649},
	url = {http://timreview.ca/article/649},
	author = {Daniel Curto-Millet}
}
@article {576,
	title = {Being Disruptive: How Open Growth is Delivering Effective Social Change at a Fast Pace},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {07/2012},
	pages = {16-20},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Both innovators and funders need tools that map the entire constellation of solutions in a sector. Innovators, often labeled and isolated as system disruptors, need to be linked with their global peers offering and seeking each others proven strategies to accelerate positive change. The impact investing space needs a simple, open, and transparent way to find, convene, support, and track the progress of innovators.

This article describes how the Ashoka Changemakers.com online community creates a space for: investors to find and support multiple innovations; social innovators to find each other, work together, and source funds; and disruptive innovations to grow over time where disruptive change is needed, fast. Crowd-sourcing, transparency, and open growth are keys to accelerating large-scale change and creating a world of changemakers.
},
	keywords = {crowdsourcing, open growth, open source, scaling-up, social entrepreneurship, social innovation, social networks, transparency},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/576},
	url = {http://timreview.ca/article/576},
	author = {Elisha Muskat and Delyse Sylvester}
}
@article {636,
	title = {Governance of Open Source Software Foundations: Who Holds the Power?},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {12/2012},
	pages = {37-42},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {The research reported in this article attempts to discover who holds the power in open source software foundations through the analysis of governance documents. Artificial neural network analysis is used to analyse the content of the bylaws of six open source foundations (Apache, Eclipse, GNOME, Plone, Python, and SPI) for the purpose of identifying power structures. Results of the research suggest that: i) the actions of an open source software foundation are centered around one of three groups: Members, Chairman/President/Executive Director, and Board of Directors; ii) in only one of the six foundations is the Board of Directors responsible for both the community and the product; and iii) artificial neural network analysis of the content of bylaws provides unbiased insights of the power structure of open source software foundations. These results may prove useful to those who contribute to open source foundations and use their products and services.},
	keywords = {artificial neural network, content analysis, keystones, management structures, open source, open source software foundations, organization, power},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/636},
	url = {http://timreview.ca/article/636},
	author = {Ludovico Prattico}
}
@article {512,
	title = {A New Way of Measuring Openness: The Open Governance Index},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {01/2012},
	pages = {18-24},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Open source software is now "business as usual" in the mobile industry. While much attention is given to the importance of open source licenses, we argue in this article that the governance model can be as necessary to a project{\textquoteright}s success and that projects vary widely in the governance models - whether open or closed - that they employ. Open source governance models describe the control points that are used to influence open source projects with regard to access to the source code, how the source code is developed, how derivatives are created, and the community structure of the project. Governance determines who has control over the project beyond what is deemed legally necessary via the open source licenses for that project. The purpose of our research is to define and measure the governance of open source projects, in other words, the extent to which decision-making in an open source project is "open" or "closed". We analyzed eight open source projects using 13 specific governance criteria across four areas of governance: access, development, derivatives and community.

Our findings suggest that the most open platforms will be most successful in the long term, however we acknowledge exceptions to this rule. We also identify best practices that are common across these open source projects with regard to source code access, development of source code, management of derivatives, and community structure. These best practices increase the likelihood of developer use of and involvement in open source projects.},
	keywords = {Android, governance, open source, open source licenses},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/512},
	url = {http://timreview.ca/article/512},
	author = {Liz Laffan}
}
@article {514,
	title = {Q\&A. What Are the Long-Term Effects of Open Source?},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {01/2012},
	pages = {29-30},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {code quality, collaboration, growth, open source, open standards},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/514},
	url = {http://timreview.ca/article/514},
	author = {Carlo Daffara}
}
@article {513,
	title = {Q\&A. What Is the Secret of Red Hat{\textquoteright}s Success?},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {01/2012},
	pages = {25-28},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {collaboration, community, innovation, open source, Red Hat},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/513},
	url = {http://timreview.ca/article/513},
	author = {Ruth Suehle}
}
@article {619,
	title = {TIM Lecture Series - Growing a Global Company Anchored on Open Source Software},
	journal = {Technology Innovation Management Review},
	volume = {2},
	year = {2012},
	month = {10/2012},
	pages = {38-40},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {BigBlueButton, entrepreneurship, global company, licenses, open source, startup, web conferencing},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/619},
	url = {http://timreview.ca/article/619},
	author = {Fred Dixon}
}
@article {494,
	title = {Editorial: Recent Research (November 2011)},
	journal = {Technology Innovation Management Review},
	volume = {1},
	year = {2011},
	month = {11/2011},
	pages = {3-3},
	publisher = {Talent First Network},
	address = {Ottawa},
	keywords = {business ecosystems, entrepreneurship, innovation, open source, policy, research},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/494},
	url = {http://timreview.ca/article/494},
	author = {Chris McPhee}
}
