@article {261,
	title = {The GNOME Foundation Is All About People},
	journal = {Open Source Business Resource},
	year = {2009},
	month = {06/2009},
	publisher = {Talent First Network},
	type = {Articles},
	address = {Ottawa},
	abstract = {As open source projects mature, they tend to join or create foundations which manage the project{\textquoteright}s financial and software assets, provide a marketing and legal entity, and sometimes help to set the direction of the project. As non-profit organizations, foundations have a specific structure defined by the jurisdiction in which they were formed. This structure typically includes a volunteer board of directors and sometimes paid staff such as a secretary or executive director.

As Executive Director of the GNOME Foundation, I am often asked "what do you do?". This article will introduce the structure of the GNOME project and its Foundation, describe how the Foundation works to support the GNOME project, and discuss the roles of the people within the GNOME Foundation. 
 },
	issn = {1913-6102},
	url = {http://timreview.ca/article/261},
	author = {Stormy Peters}
}
@article {222,
	title = {The Role of Consumers Within an Open Source Community},
	journal = {Open Source Business Resource},
	year = {2009},
	month = {01/2009},
	publisher = {Talent First Network},
	type = {Articles},
	address = {Ottawa},
	abstract = {The software provided by the GNOME Project is produced by a large community comprised of several thousand developers, translators, quality assurance testers, and documentation writers. Consumers are represented in the community by technical users and organizations that distribute GNOME technologies. And while the community reaches out regularly to non-technical end users and welcomes any that approach the community, these two worlds rarely interact. 

This article draws upon our experience within the GNOME Project to examine the question "Why do consumers and the community rarely interact?". Our insights may prove useful for other projects and consumers wishing more interaction.},
	issn = {1913-6102},
	url = {http://timreview.ca/article/222},
	author = {Stormy Peters}
}
@article {54,
	title = {Enterprise Open Source Support},
	journal = {Open Source Business Resource},
	year = {2007},
	month = {11/2007},
	publisher = {Talent First Network},
	type = {Articles},
	address = {Ottawa},
	abstract = {Open Source Software (OSS) has permeated the enterprise. Some organizations still prohibit the use of OSS altogether, but they are unquestionably in the minority. For most companies, it{\textquoteright}s not a question of "should we use OSS"? but rather, "how and where can we best take advantage of open source solutions"? 

As companies have shifted from prohibiting OSS use to embracing it, they must now deal with technical support issues. This article examines the various option available to support companies that use OSS.},
	issn = {1913-6102},
	url = {http://timreview.ca/article/54},
	author = {Stormy Peters}
}
@article {65,
	title = {Open Source Licensing in the Enterprise},
	journal = {Open Source Business Resource},
	year = {2007},
	month = {10/2007},
	publisher = {Talent First Network},
	type = {Articles},
	address = {Ottawa},
	abstract = {Studies show that most open source projects are licensed under the General Public License (GPL) and it is estimated that over 75\% of open source projects are licensed under either the GPL or the LGPL (Lesser GPL). Yet, it has been my company{\textquoteright}s experience that the open source software used by our enterprise customers is primarily Apache licensed software. This article examines several factors which may shed some light on this disparity, including the issues raised by enterprise customers and the software product selection process used by OpenLogic (http://www.openlogic.com).},
	issn = {1913-6102},
	url = {http://timreview.ca/article/65},
	author = {Stormy Peters}
}
