01940nas a2200337   4500008004100000022001400041245004500055210004500100260004200145300000900187490000600196520109200202653001301294653002101307653001501328653001201343653001501355653001601370653000901386653001301395653002701408653001501435653001501450653001001465653002001475100001801495700002001513700001601533700001601549856003701565       2017                        eng d  a1927-032100aReflecting on 10 Years of the TIM Review0 aReflecting on 10 Years of the TIM Review  aOttawabTalent First Networkc07/2017  a5-200 v73 aIn 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 – 31% from Asia, 30% from the Americas, 26% from Europe, 8% from Africa, and 5% from Oceania – with over 25,000 readers now accessing the site each month. 10abusiness10aentrepreneurship10ainnovation10ajournal10amanagement10aopen source10aOSBR10aresearch10ascientometric analyses10atechnology10aTIM Review10atopic10atopic modelling1 aMcPhee, Chris1 aSantonen, Teemu1 aShah, Ahmed1 aNazari, Ali  uhttp://timreview.ca/article/108702511nas a2200253   4500008004100000022001400041245006100055210006100116260004200177300001000219490000600229520182100235653001802056653001402074653001802088653000802106653001202114653001602126653002102142100001602163700001902179700002302198856003602221       2016                        eng d  a1927-032100aLicense Compliance in Open Source Cybersecurity Projects0 aLicense Compliance in Open Source Cybersecurity Projects  aOttawabTalent First Networkc02/2016  a28-350 v63 aDevelopers 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'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.10acontamination10acopyright10acybersecurity10aGPL10alicense10aopen source10athird-party code1 aShah, Ahmed1 aSelman, Selman1 aAbualhaol, Ibrahim  uhttp://timreview.ca/article/966