@article {409, title = {Best Practices in Multi-Vendor Open Source Communities}, journal = {Open Source Business Resource}, year = {2011}, month = {01/2011}, publisher = {Talent First Network}, type = {Articles}, address = {Ottawa}, abstract = {Multi-vendor open source communities enable companies to lower development costs and gain access to wider addressable markets. This article describes best practices for companies considering this approach. First, the different types of open source business strategies are examined along the types of participants that contribute to the communities that support them. Next, five best practices are detailed to show how companies can maximize their engagement with open source communities. Finally, the importance of foundations in implementing multi-vendor open source communities is discussed. }, issn = {1913-6102}, url = {http://timreview.ca/article/409}, author = {Ian Skerrett} } @article {219, title = {Collaborative Software Development in the Enterprise}, journal = {Open Source Business Resource}, year = {2009}, month = {01/2009}, publisher = {Talent First Network}, type = {Articles}, address = {Ottawa}, abstract = {Open source has been many things to many people. In most cases, open source software has focused on the tools and the infrastructure software used to build and deploy applications. Relative to infrastructure, little use or investment has occurred in the development of industry specific or vertical oriented open source solutions. This is not only a missed opportunity for organizations, but it is also possibly the next wave of open source collaborations. An important lesson of OSS is a development process that requires collaboration between individuals and organizations that isn{\textquoteright}t necessarily driven by a traditional hierarchy of command and control. Information technology departments are driven to be more efficient while simultaneously creating innovative new solutions to meet their business needs. More and more, companies are turning to external sources for ideas that drive innovation. A series of books by Henry Chesbrough has coined the term "innovation networks" to discuss research and development departments that treat their research and development systems as an open system. They describe how to include partners, customers and even competitors as part of an extended research and development team. However, that series does not answer the question "can OSS can be used to establish innovation networks for IT departments?". Further, what steps are required to establish a successful software innovation network and what are the resulting benefits for organizations? For the most part, this article will draw upon the experiences of Eclipse open source projects. These projects often include competing independent software vendors that collaborate on building a common platform for developer tools integration.}, issn = {1913-6102}, url = {http://timreview.ca/article/219}, author = {Ian Skerrett} } @article {160, title = {TIM Lecture Series: Building Technical Communities}, journal = {Open Source Business Resource}, year = {2008}, month = {06/2008}, publisher = {Talent First Network}, type = {Articles}, address = {Ottawa}, abstract = {On June 4, 2008, Ian Skerrett from the Eclipse Foundation delivered a presentation entitled " Building Technical Communities". This section provides the key messages from Ian{\textquoteright}s lecture. Ian used his observations of working in the Eclipse community to explain why community building is important, its critical elements, and how the traditional roles within an organization relate.}, issn = {1913-6102}, url = {http://timreview.ca/article/160}, author = {Ian Skerrett} }