<?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: Magento, license could be a serious trouble</title>
	<atom:link href="http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/feed/" rel="self" type="application/rss+xml" />
	<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/</link>
	<description></description>
	<lastBuildDate>Wed, 19 May 2010 15:38:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: phill</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-35508</link>
		<dc:creator>phill</dc:creator>
		<pubDate>Fri, 15 May 2009 03:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-35508</guid>
		<description>wow.

I never knew this about Magento!
I had searched for a week for an ecommerce solution, now I have to rethink...

One thing was very odd.
You can download Magento directly and examine its code if you wish, but YOU CANNOT DOWNLOAD THE MAGENTO EXTENSIONS!

you have to enter some &quot;extensions code&quot; in the Magento admin screen, and IT downloads and installs...dont like that at all, also it means I cant have a bunch of files that make up a magento site ready for use when I want it... oh well.... luckily there are other free products</description>
		<content:encoded><![CDATA[<p>wow.</p>
<p>I never knew this about Magento!<br />
I had searched for a week for an ecommerce solution, now I have to rethink&#8230;</p>
<p>One thing was very odd.<br />
You can download Magento directly and examine its code if you wish, but YOU CANNOT DOWNLOAD THE MAGENTO EXTENSIONS!</p>
<p>you have to enter some &#8220;extensions code&#8221; in the Magento admin screen, and IT downloads and installs&#8230;dont like that at all, also it means I cant have a bunch of files that make up a magento site ready for use when I want it&#8230; oh well&#8230;. luckily there are other free products</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mani</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-32698</link>
		<dc:creator>Mani</dc:creator>
		<pubDate>Fri, 17 Apr 2009 14:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-32698</guid>
		<description>Hi,

I know a little about License and certainly NOT the expert in this area. I agree to some of the points mentioned by Fabrizio Balliano.

But, anyhow my concern totally different.
From the Page: http://www.magentocommerce.com/license/
&lt;i&gt; Can I use the “Magento” trademark in one of my domain names or URLs?
 No. You may not use the Magento trademark or any other mark associated with the Magento offering from our company in your domain name or URL. (For instance &quot;www.magentohosting.com&quot; is not allowed. See more on this topic below.)  &lt;/i&gt;

I think, this is very strange. Suppose If i am a web developer or blogger, how can i avoid magento name from my URL ? Nowadays almost all the CMS comes with SEO friendly build-in engine, then how can I avoid Magento in my URL ? 
Why cant I have the Magento in my URL or domain name ?
Does this License speaks anything about it ? or it is condition from the author of Magento ?
one more qns: Is there any open source which has similar conditions ?

sorry, I am wrong. Just i am writing this comments to clarify. 
Magento is one of the BEST available ecom solun now. 
Thanks for that Great Work!!!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I know a little about License and certainly NOT the expert in this area. I agree to some of the points mentioned by Fabrizio Balliano.</p>
<p>But, anyhow my concern totally different.<br />
From the Page: <a href="http://www.magentocommerce.com/license/" rel="nofollow">http://www.magentocommerce.com/license/</a><br />
<i> Can I use the “Magento” trademark in one of my domain names or URLs?<br />
 No. You may not use the Magento trademark or any other mark associated with the Magento offering from our company in your domain name or URL. (For instance &#8220;www.magentohosting.com&#8221; is not allowed. See more on this topic below.)  </i></p>
<p>I think, this is very strange. Suppose If i am a web developer or blogger, how can i avoid magento name from my URL ? Nowadays almost all the CMS comes with SEO friendly build-in engine, then how can I avoid Magento in my URL ?<br />
Why cant I have the Magento in my URL or domain name ?<br />
Does this License speaks anything about it ? or it is condition from the author of Magento ?<br />
one more qns: Is there any open source which has similar conditions ?</p>
<p>sorry, I am wrong. Just i am writing this comments to clarify.<br />
Magento is one of the BEST available ecom solun now.<br />
Thanks for that Great Work!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Affero GNU Public License is now OSI approved @ Fabrizio Balliano's blog</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-484</link>
		<dc:creator>Affero GNU Public License is now OSI approved @ Fabrizio Balliano's blog</dc:creator>
		<pubDate>Fri, 14 Mar 2008 08:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-484</guid>
		<description>[...] This post is a sort of answer to post about Magento&#8217;s license where Roy Rubin (CEO of Varien) told me that AGPL wasn&#8217;t OSI approved (it was true in that [...]</description>
		<content:encoded><![CDATA[<p>[...] This post is a sort of answer to post about Magento&#8217;s license where Roy Rubin (CEO of Varien) told me that AGPL wasn&#8217;t OSI approved (it was true in that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Black Cat</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-428</link>
		<dc:creator>Black Cat</dc:creator>
		<pubDate>Tue, 11 Mar 2008 03:30:13 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-428</guid>
		<description>è possibile avere una traduzione dell&#039;articolo in italiano? ^^</description>
		<content:encoded><![CDATA[<p>è possibile avere una traduzione dell&#8217;articolo in italiano? ^^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustavo G. Mármol</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-395</link>
		<dc:creator>Gustavo G. Mármol</dc:creator>
		<pubDate>Sat, 08 Mar 2008 03:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-395</guid>
		<description>Larry,

GNU, said:

&quot;The Open Software License is a free software license. It is incompatible with the GNU GPL in several ways. Recent versions of the Open Software License have a term which requires distributors to try to obtain explicit assent to the license. This means that distributing OSL software on ordinary FTP sites, sending patches to ordinary mailing lists, or storing the software in an ordinary version control system, is arguably a violation of the license and would subject you to possible termination of the license. Thus, the Open Software License makes it very difficult to develop software using the ordinary tools of free software development. For this reason, and because it is incompatible with the GPL, we recommend that no version of the OSL be used for any software. We urge you not to use the Open Software License for software you write. However, there is no reason to avoid running programs that have been released under this license&quot;.

And, you in your article establish that: &quot;licenses And the Manifestation of Assent&quot;...Perhaps the most obvious linguistic difference between OSL 3.0 and the GPL Licenses is that OSL 3.0 uses terms of art and expressions from contract law to say precisely what it means&quot;...&quot;There is nothing in OSL 3.0 itself, owever, that requires the formation of a contract in order to grant -or to revoke the grant- of the license to the copyrighted work&quot;

And...&quot;to encourage contract formation, OSL 3.0 requires that downstream licenses who in turn distribute must make a reasonable effort under the circunstances to obtain the express assent of recipients to ther terms of this License&quot;

And in Clause 9 &quot;Acceptance and Termination&quot;. License OSL 3.0:&quot;If, at any time, You expressly assented to this license, that assent indicates your clear and irrevocable acceptance of this License and all of its terms and conditions. If you distribute or communicate copies of the original work or Derivate work, you must make a reasonable effort under the circunstances to obtain the express asssent of recipients to ther terms of this License.&quot; 

From my view, and according with my interpretation of the License OSL 3.0, the sine qua non condition to exercise the rights granted by the Licensor are limited to fullfil 1.c) &quot;with the proviso that copies of the original work or derivative works that you distribute or communicate shall be licensed under this OSL.&quot;. That means you accepted the terms of the license at the moment you decide to create a derivative work based upon the original work. This is the moment that reflect the acceptance of the license by the licensee.

In the other hand, Clause 9, establish &quot;If, at any time, you expressly assented to this license..&quot; 

The meaning of &quot;IF&quot; means only the possibility&quot;, that is to say, you must make a reasonable effort to obtain the express assent of recipients to the terms of the license (in downstream licenses), but, you are not obligated to get it, just because only you have to prove &quot;reasonable effort&quot; to demostrate, in any case, that you intent to obtain the express assent, but in no way can someone understand that this act is a violation of the license.

Also, the License not establish the termination  of the license under this circunstances. 

The License only shall terminte when the licensee failure to honor the conditions in section 1.c.

Thanks, Gustavo.</description>
		<content:encoded><![CDATA[<p>Larry,</p>
<p>GNU, said:</p>
<p>&#8220;The Open Software License is a free software license. It is incompatible with the GNU GPL in several ways. Recent versions of the Open Software License have a term which requires distributors to try to obtain explicit assent to the license. This means that distributing OSL software on ordinary FTP sites, sending patches to ordinary mailing lists, or storing the software in an ordinary version control system, is arguably a violation of the license and would subject you to possible termination of the license. Thus, the Open Software License makes it very difficult to develop software using the ordinary tools of free software development. For this reason, and because it is incompatible with the GPL, we recommend that no version of the OSL be used for any software. We urge you not to use the Open Software License for software you write. However, there is no reason to avoid running programs that have been released under this license&#8221;.</p>
<p>And, you in your article establish that: &#8220;licenses And the Manifestation of Assent&#8221;&#8230;Perhaps the most obvious linguistic difference between OSL 3.0 and the GPL Licenses is that OSL 3.0 uses terms of art and expressions from contract law to say precisely what it means&#8221;&#8230;&#8221;There is nothing in OSL 3.0 itself, owever, that requires the formation of a contract in order to grant -or to revoke the grant- of the license to the copyrighted work&#8221;</p>
<p>And&#8230;&#8221;to encourage contract formation, OSL 3.0 requires that downstream licenses who in turn distribute must make a reasonable effort under the circunstances to obtain the express assent of recipients to ther terms of this License&#8221;</p>
<p>And in Clause 9 &#8220;Acceptance and Termination&#8221;. License OSL 3.0:&#8221;If, at any time, You expressly assented to this license, that assent indicates your clear and irrevocable acceptance of this License and all of its terms and conditions. If you distribute or communicate copies of the original work or Derivate work, you must make a reasonable effort under the circunstances to obtain the express asssent of recipients to ther terms of this License.&#8221; </p>
<p>From my view, and according with my interpretation of the License OSL 3.0, the sine qua non condition to exercise the rights granted by the Licensor are limited to fullfil 1.c) &#8220;with the proviso that copies of the original work or derivative works that you distribute or communicate shall be licensed under this OSL.&#8221;. That means you accepted the terms of the license at the moment you decide to create a derivative work based upon the original work. This is the moment that reflect the acceptance of the license by the licensee.</p>
<p>In the other hand, Clause 9, establish &#8220;If, at any time, you expressly assented to this license..&#8221; </p>
<p>The meaning of &#8220;IF&#8221; means only the possibility&#8221;, that is to say, you must make a reasonable effort to obtain the express assent of recipients to the terms of the license (in downstream licenses), but, you are not obligated to get it, just because only you have to prove &#8220;reasonable effort&#8221; to demostrate, in any case, that you intent to obtain the express assent, but in no way can someone understand that this act is a violation of the license.</p>
<p>Also, the License not establish the termination  of the license under this circunstances. </p>
<p>The License only shall terminte when the licensee failure to honor the conditions in section 1.c.</p>
<p>Thanks, Gustavo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabrizio Balliano</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-333</link>
		<dc:creator>Fabrizio Balliano</dc:creator>
		<pubDate>Sun, 02 Mar 2008 11:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-333</guid>
		<description>@Saharian: no problem at all, I tried to fill the post with updates to correct the possible misreading :-) but you know... not being a native english speaker makes things difficult to me :-(</description>
		<content:encoded><![CDATA[<p>@Saharian: no problem at all, I tried to fill the post with updates to correct the possible misreading :-) but you know&#8230; not being a native english speaker makes things difficult to me :-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saharian</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-330</link>
		<dc:creator>Saharian</dc:creator>
		<pubDate>Sat, 01 Mar 2008 22:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-330</guid>
		<description>Thanks for clarification, indeed it could be read in few ways, as a call for action and as a possibility. 

Together with incorrect and not favourable one-way interpretation of the license I&#039;ve got bit overprotective for Magento, as I love the fresh air it brings to ecommerce market, and get annoyed by non-sense opposition.

Please accept my appologies.</description>
		<content:encoded><![CDATA[<p>Thanks for clarification, indeed it could be read in few ways, as a call for action and as a possibility. </p>
<p>Together with incorrect and not favourable one-way interpretation of the license I&#8217;ve got bit overprotective for Magento, as I love the fresh air it brings to ecommerce market, and get annoyed by non-sense opposition.</p>
<p>Please accept my appologies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabrizio Balliano</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-327</link>
		<dc:creator>Fabrizio Balliano</dc:creator>
		<pubDate>Sat, 01 Mar 2008 11:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-327</guid>
		<description>@Lawrence Rosen: it&#039;s nice to see your clarifications, the problem came from a consideration like &quot;direvative works are released under OSL, a patch is something that creates a derivative thus should be under OSL and thus there&#039;s the explicit assent thing to consider&quot;. if you say that this is different that&#039;s ok, I could be wrong. I&#039;ll write GNU to find out if they could correct their considerations.

@Saharian: &quot;other people could stop using magento&quot; does not mean &quot;I suggest you not to use magento&quot;, it&#039;s completely different and it&#039;s a warning I wanted to raise to the magento&#039;s team so they could take care of all the posts in their forums asking clarifications about liceses.

I do not imply anything, I just pointed out a situation, and anyway you can check my latest post about magento, and you would not say i&#039;m not constructive.</description>
		<content:encoded><![CDATA[<p>@Lawrence Rosen: it&#8217;s nice to see your clarifications, the problem came from a consideration like &#8220;direvative works are released under OSL, a patch is something that creates a derivative thus should be under OSL and thus there&#8217;s the explicit assent thing to consider&#8221;. if you say that this is different that&#8217;s ok, I could be wrong. I&#8217;ll write GNU to find out if they could correct their considerations.</p>
<p>@Saharian: &#8220;other people could stop using magento&#8221; does not mean &#8220;I suggest you not to use magento&#8221;, it&#8217;s completely different and it&#8217;s a warning I wanted to raise to the magento&#8217;s team so they could take care of all the posts in their forums asking clarifications about liceses.</p>
<p>I do not imply anything, I just pointed out a situation, and anyway you can check my latest post about magento, and you would not say i&#8217;m not constructive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Rosen</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-324</link>
		<dc:creator>Lawrence Rosen</dc:creator>
		<pubDate>Sat, 01 Mar 2008 01:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-324</guid>
		<description>You wrote: &quot;I write a patch for Magento. That patch is released under OSL becuase that&#039;s what OSL impose. I send the patch to some public mailing list or post it to a forum because I want to help developers creating a better and bug-free software. In this situation I&#039;m violating the license and I&#039;m loosing my right to use the software anymore. I think this is a serious trouble that should be avoided and solved.&quot;

This is totally wrong. You *always* retain the right to license your own work under as many licenses as you want. You can never violate your own license for your own software. Your patch is yours. 

But you can *never* change the license of Magento without the permission of its copyright owners. That&#039;s true of any open source license. It is not something special about OSL 3.0.

As the author of OSL 3.0, I can reassure you that your fears are mistaken. You&#039;re misreading the license and the copyright law.

/Larry Rosen</description>
		<content:encoded><![CDATA[<p>You wrote: &#8220;I write a patch for Magento. That patch is released under OSL becuase that&#8217;s what OSL impose. I send the patch to some public mailing list or post it to a forum because I want to help developers creating a better and bug-free software. In this situation I&#8217;m violating the license and I&#8217;m loosing my right to use the software anymore. I think this is a serious trouble that should be avoided and solved.&#8221;</p>
<p>This is totally wrong. You *always* retain the right to license your own work under as many licenses as you want. You can never violate your own license for your own software. Your patch is yours. </p>
<p>But you can *never* change the license of Magento without the permission of its copyright owners. That&#8217;s true of any open source license. It is not something special about OSL 3.0.</p>
<p>As the author of OSL 3.0, I can reassure you that your fears are mistaken. You&#8217;re misreading the license and the copyright law.</p>
<p>/Larry Rosen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saharian</title>
		<link>http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/comment-page-1/#comment-322</link>
		<dc:creator>Saharian</dc:creator>
		<pubDate>Sat, 01 Mar 2008 01:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://fabrizioballiano.net/2008/02/27/magento-license-could-be-a-serious-trouble/#comment-322</guid>
		<description>&lt;blockquote&gt;hemmm where did I write not to use magento? you don’t see the real meaning of this post, I’m sorry.&lt;/blockquote&gt;

Here&#039;s where you write it:

&lt;blockquote&gt;We all know that many people do not pay serious attention to all the license implications, but &lt;b&gt;all the others could stop using Magento&lt;/b&gt; because of all the problems above and I don’t think this is a good thing for the project.&lt;/blockquote&gt;

Maybe the meaning behind this statement is different from how i understand it, in that case please clarify.

&lt;blockquote&gt;anyway GNU should not be considered one of the biggest player in the open source license game? are you kidding me? if they write those considerations about OSL then Mr. Rosen should contact them and clarify every aspect and (maybe) they could make both *GPL/OSL become compatible, if everyone keeps saying different things than no one could understand anything. We all need a clarification, it will be good for OSL too.&lt;/blockquote&gt;

&quot;one of the biggest player&quot; - yes, not absolute authority that dictate eligibility of other licenses. And I do not think they by themselves take what they write as absolute truth, but as just &lt;b&gt;their opinion&lt;/b&gt;. You take it as an established fact without digging into their statements and giving it benefit of a doubt.

&lt;blockquote&gt;it’s GNU saying that. read GNU considerations.&lt;/blockquote&gt;
I know it is very convenient not to take responsibility over your aquired statements by relaying it on the source, but if you repeat them without understanding, be prepared to take a heat if they&#039;re not correct. 

Explain me this logic:
* GPLv2 is not compatible with GPLv3 - no problem
* OSL is not compatible with GPL - big problem, stop using OSL software.

&lt;blockquote&gt;another consideration, look at magento’s forum and you’ll find a bunch of posts asking “hey can I do this or that with this license?”, this should make you think that MAYBE the license is not as clear as you think, MAYBE.&lt;/blockquote&gt;

If you read the posts carefully, you will see that most of the questions are about TRADEMARK, not LICENSE. Many people confuse these 2 terms, but it&#039;s their problem and it&#039;s being explained in one of the posts i think. The questions are about usage of &quot;Magento&quot; (tm) word in their domain names.

Saharian, I’d like everyone of us (open source players) to be costructive, if an issue is raised let’s work together to solve it and make free software always better.

Do you imply by that that you&#039;re being more constructive than me? The 2 suggestions you have made were using AGPL3, which you have retracted later, and to stop using Magento.

Very constructive.</description>
		<content:encoded><![CDATA[<blockquote><p>hemmm where did I write not to use magento? you don’t see the real meaning of this post, I’m sorry.</p></blockquote>
<p>Here&#8217;s where you write it:</p>
<blockquote><p>We all know that many people do not pay serious attention to all the license implications, but <b>all the others could stop using Magento</b> because of all the problems above and I don’t think this is a good thing for the project.</p></blockquote>
<p>Maybe the meaning behind this statement is different from how i understand it, in that case please clarify.</p>
<blockquote><p>anyway GNU should not be considered one of the biggest player in the open source license game? are you kidding me? if they write those considerations about OSL then Mr. Rosen should contact them and clarify every aspect and (maybe) they could make both *GPL/OSL become compatible, if everyone keeps saying different things than no one could understand anything. We all need a clarification, it will be good for OSL too.</p></blockquote>
<p>&#8220;one of the biggest player&#8221; &#8211; yes, not absolute authority that dictate eligibility of other licenses. And I do not think they by themselves take what they write as absolute truth, but as just <b>their opinion</b>. You take it as an established fact without digging into their statements and giving it benefit of a doubt.</p>
<blockquote><p>it’s GNU saying that. read GNU considerations.</p></blockquote>
<p>I know it is very convenient not to take responsibility over your aquired statements by relaying it on the source, but if you repeat them without understanding, be prepared to take a heat if they&#8217;re not correct. </p>
<p>Explain me this logic:<br />
* GPLv2 is not compatible with GPLv3 &#8211; no problem<br />
* OSL is not compatible with GPL &#8211; big problem, stop using OSL software.</p>
<blockquote><p>another consideration, look at magento’s forum and you’ll find a bunch of posts asking “hey can I do this or that with this license?”, this should make you think that MAYBE the license is not as clear as you think, MAYBE.</p></blockquote>
<p>If you read the posts carefully, you will see that most of the questions are about TRADEMARK, not LICENSE. Many people confuse these 2 terms, but it&#8217;s their problem and it&#8217;s being explained in one of the posts i think. The questions are about usage of &#8220;Magento&#8221; &#8482; word in their domain names.</p>
<p>Saharian, I’d like everyone of us (open source players) to be costructive, if an issue is raised let’s work together to solve it and make free software always better.</p>
<p>Do you imply by that that you&#8217;re being more constructive than me? The 2 suggestions you have made were using AGPL3, which you have retracted later, and to stop using Magento.</p>
<p>Very constructive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
