<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Open Source Contract Considerations</title>
	<atom:link href="http://alexking.org/blog/2009/07/01/open-source-contract-considerations/feed" rel="self" type="application/rss+xml" />
	<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations</link>
	<description>Alex King, Denver Web Developer</description>
	<lastBuildDate>Thu, 24 May 2012 16:30:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Links 07/09/2009: New Debian, Linux 2.6.31 @ RC9 &#124; Boycott Novell</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-101304</link>
		<dc:creator>Links 07/09/2009: New Debian, Linux 2.6.31 @ RC9 &#124; Boycott Novell</dc:creator>
		<pubDate>Mon, 07 Sep 2009 23:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-101304</guid>
		<description>[...] Open Source Contract Considerations  At Crowd Favorite we work primarily with WordPress, but also with many other Open Source projects. We are often working with larger companies that have standard Master Services Agreements (MSAs) or Professional Services Agreements (PSAs). These agreement templates are designed so that these companies have a known legal foundation to work from, and include a variety of requirements and terms that apply to the consultants working for them and governing the Deliverables created by those consultants. These agreements often have standard language in them that have some interesting side-effects when you are working with Open Source. [...]</description>
		<content:encoded><![CDATA[<p>[...] Open Source Contract Considerations  At Crowd Favorite we work primarily with WordPress, but also with many other Open Source projects. We are often working with larger companies that have standard Master Services Agreements (MSAs) or Professional Services Agreements (PSAs). These agreement templates are designed so that these companies have a known legal foundation to work from, and include a variety of requirements and terms that apply to the consultants working for them and governing the Deliverables created by those consultants. These agreements often have standard language in them that have some interesting side-effects when you are working with Open Source. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Haugen</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-99872</link>
		<dc:creator>Bob Haugen</dc:creator>
		<pubDate>Tue, 01 Sep 2009 14:48:04 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-99872</guid>
		<description>Very interesting and useful advice.  

Have you (or anyone you know) written about open source intellectual property concerns for contracts?  For example, if you want the resulting code to be open source?  Or if the client wants work-for-hire that they own, how you clearly differentiate between what is and what ain&#039;t, since you will probably be re-using some of your previous open source code along with new client-specified code?

(I do understand your note that this post is over a month old, and did check later for followups.)</description>
		<content:encoded><![CDATA[<p>Very interesting and useful advice.  </p>
<p>Have you (or anyone you know) written about open source intellectual property concerns for contracts?  For example, if you want the resulting code to be open source?  Or if the client wants work-for-hire that they own, how you clearly differentiate between what is and what ain&#8217;t, since you will probably be re-using some of your previous open source code along with new client-specified code?</p>
<p>(I do understand your note that this post is over a month old, and did check later for followups.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecosystems &#187; links for 2009-08-31</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-99665</link>
		<dc:creator>tecosystems &#187; links for 2009-08-31</dc:creator>
		<pubDate>Tue, 01 Sep 2009 01:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-99665</guid>
		<description>[...] Open Source Contract Considerations &#124; alexking.org had this one open for a long while: excellent advice from a practitioner (tags: alexking opensource contract ip contracts legal indemnity infringement warranty patent) [...]</description>
		<content:encoded><![CDATA[<p>[...] Open Source Contract Considerations | alexking.org had this one open for a long while: excellent advice from a practitioner (tags: alexking opensource contract ip contracts legal indemnity infringement warranty patent) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Contrats de prestations de services et open source &#124; Philippe.Scoffoni.Net</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-72007</link>
		<dc:creator>Contrats de prestations de services et open source &#124; Philippe.Scoffoni.Net</dc:creator>
		<pubDate>Wed, 08 Jul 2009 22:41:18 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-72007</guid>
		<description>[...] cours de mes lectures je suis tombÃ© sur un article anglais qui m&#8217;a rappelÃ© les quelques annÃ©es passÃ©es Ã  faire des prestations de services. Ce [...]</description>
		<content:encoded><![CDATA[<p>[...] cours de mes lectures je suis tombÃ© sur un article anglais qui m&#8217;a rappelÃ© les quelques annÃ©es passÃ©es Ã  faire des prestations de services. Ce [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-07-05 &#124; GFMorris.com</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-71333</link>
		<dc:creator>links for 2009-07-05 &#124; GFMorris.com</dc:creator>
		<pubDate>Mon, 06 Jul 2009 02:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-71333</guid>
		<description>[...] Open Source Contract Considerations &#124; alexking.org At Crowd Favorite we work primarily with WordPress, but also with many other Open Source projects. We are often working with larger companies that have standard Master Services Agreements (MSAs) or Professional Services Agreements (PSAs). These agreement templates are designed so that these companies have a known legal foundation to work from, and include a variety of requirements and terms that apply to the consultants working for them and governing the Deliverables created by those consultants. These agreements often have standard language in them that have some interesting side-effects when you are working with Open Source. (tags: opensource contracts) [...]</description>
		<content:encoded><![CDATA[<p>[...] Open Source Contract Considerations | alexking.org At Crowd Favorite we work primarily with WordPress, but also with many other Open Source projects. We are often working with larger companies that have standard Master Services Agreements (MSAs) or Professional Services Agreements (PSAs). These agreement templates are designed so that these companies have a known legal foundation to work from, and include a variety of requirements and terms that apply to the consultants working for them and governing the Deliverables created by those consultants. These agreements often have standard language in them that have some interesting side-effects when you are working with Open Source. (tags: opensource contracts) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-07-02 &#124; burningCat</title>
		<link>http://alexking.org/blog/2009/07/01/open-source-contract-considerations#comment-70859</link>
		<dc:creator>links for 2009-07-02 &#124; burningCat</dc:creator>
		<pubDate>Thu, 02 Jul 2009 08:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/?p=3389#comment-70859</guid>
		<description>[...] Open Source Contract Considerations [...]</description>
		<content:encoded><![CDATA[<p>[...] Open Source Contract Considerations [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

