<?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: OMG! Someone Stole My Code</title>
	<atom:link href="http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/</link>
	<description>Trying to walk that thin line between intelligence and ignorance</description>
	<lastBuildDate>Thu, 29 Jul 2010 20:54:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: kurt schroeder</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24991</link>
		<dc:creator>kurt schroeder</dc:creator>
		<pubDate>Thu, 14 Jan 2010 22:57:45 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24991</guid>
		<description>I wish more people would steal my code. Then i&#039;d feel like i was doing something right more of the time. I would love to have it reported by a concerned other too so i could put it on my resume as a noted achevement! May, 2010: My REST example was stolen by ***** ***** and is currently being used in a comercial site. That&#039;s future, because i&#039;m learning REST meaning i&#039;m the one who is stealing, but i do make note of it in just those terms. Code stolen from (by permission) ***** ******!

I appreicated the person who reported the theft and can understand a certain anoyance with others who do not note where the idea came from. Giving credit where it is due is more than just courtisy, but I really feel that&#039;s a good enough reason. Giving credit will let others know where they may find good other ideas. It can be disheartening to some when another takes credit for an idea they had a hand in, but at a certain point yo just have to allow the public free access. In the film Michael, staring John Travolta, The beer drinking cigerette smoking angel said one day, (paraphrase) &quot;see that, those people are standing in line. You know, I invented that!&quot; (what did they do before?) &quot;...they just stood round.&quot; I mean someone has to be first, right?</description>
		<content:encoded><![CDATA[<p>I wish more people would steal my code. Then i&#8217;d feel like i was doing something right more of the time. I would love to have it reported by a concerned other too so i could put it on my resume as a noted achevement! May, 2010: My REST example was stolen by ***** ***** and is currently being used in a comercial site. That&#8217;s future, because i&#8217;m learning REST meaning i&#8217;m the one who is stealing, but i do make note of it in just those terms. Code stolen from (by permission) ***** ******!</p>
<p>I appreicated the person who reported the theft and can understand a certain anoyance with others who do not note where the idea came from. Giving credit where it is due is more than just courtisy, but I really feel that&#8217;s a good enough reason. Giving credit will let others know where they may find good other ideas. It can be disheartening to some when another takes credit for an idea they had a hand in, but at a certain point yo just have to allow the public free access. In the film Michael, staring John Travolta, The beer drinking cigerette smoking angel said one day, (paraphrase) &#8220;see that, those people are standing in line. You know, I invented that!&#8221; (what did they do before?) &#8220;&#8230;they just stood round.&#8221; I mean someone has to be first, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter F.</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24830</link>
		<dc:creator>Peter F.</dc:creator>
		<pubDate>Wed, 13 Jan 2010 17:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24830</guid>
		<description>To your point about OSS projects, some IT departments have inane rules about allowing open-source projects to be used within their code.  I&#039;ve seen entire OS libraries snuck in by repackaging the code as part of some internally developed &quot;Shared&quot; library.  Clearly, this is foolish on so many fronts:

1) now there are two maintenance branches and it&#039;s unlikely the shadow copy will keep up with the OS project changes
2) all the documentation and supporting community are left out (developers need to know about the actual library (&quot;our ORM, wink wink...&quot;)
3) large code-bases are intimidating and hard to grok, it&#039;s so much easier to teach concepts and APIs
4) it creates a liability for the company
5) most developers don&#039;t want to &quot;steal&quot; the code! they just want to reuse an existing library, not feel like thieves
6) from a management perspective, the average code-quality of mature OSS vs in-house is heavily weighted in favor of OSS

But it&#039;s a reality.  The cases where a developer wants to pass off other people&#039;s code as their own are in a different category.

Love the blog, btw.



P.S. 

heh, the reCAPTCHA for this post was &quot;debutante found&quot; -- found where?</description>
		<content:encoded><![CDATA[<p>To your point about OSS projects, some IT departments have inane rules about allowing open-source projects to be used within their code.  I&#8217;ve seen entire OS libraries snuck in by repackaging the code as part of some internally developed &#8220;Shared&#8221; library.  Clearly, this is foolish on so many fronts:</p>
<p>1) now there are two maintenance branches and it&#8217;s unlikely the shadow copy will keep up with the OS project changes<br />
2) all the documentation and supporting community are left out (developers need to know about the actual library (&#8220;our ORM, wink wink&#8230;&#8221;)<br />
3) large code-bases are intimidating and hard to grok, it&#8217;s so much easier to teach concepts and APIs<br />
4) it creates a liability for the company<br />
5) most developers don&#8217;t want to &#8220;steal&#8221; the code! they just want to reuse an existing library, not feel like thieves<br />
6) from a management perspective, the average code-quality of mature OSS vs in-house is heavily weighted in favor of OSS</p>
<p>But it&#8217;s a reality.  The cases where a developer wants to pass off other people&#8217;s code as their own are in a different category.</p>
<p>Love the blog, btw.</p>
<p>P.S. </p>
<p>heh, the reCAPTCHA for this post was &#8220;debutante found&#8221; &#8212; found where?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kjörling</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24800</link>
		<dc:creator>Michael Kjörling</dc:creator>
		<pubDate>Wed, 13 Jan 2010 13:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24800</guid>
		<description>Agreed with #4 Peter Zsoldos.

Also, if those are terms you are comfortable with, you may want to look into using the CC0 license in the future. http://creativecommons.org/choose/zero</description>
		<content:encoded><![CDATA[<p>Agreed with #4 Peter Zsoldos.</p>
<p>Also, if those are terms you are comfortable with, you may want to look into using the CC0 license in the future. <a href="http://creativecommons.org/choose/zero" rel="nofollow">http://creativecommons.org/choose/zero</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Zsoldos</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24779</link>
		<dc:creator>Peter Zsoldos</dc:creator>
		<pubDate>Wed, 13 Jan 2010 09:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24779</guid>
		<description>Licensing/copyrights/copylefts aside, it would be beneficial for maintainers/new developers to have a link to the documentation (blog posts) of the DAL.</description>
		<content:encoded><![CDATA[<p>Licensing/copyrights/copylefts aside, it would be beneficial for maintainers/new developers to have a link to the documentation (blog posts) of the DAL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davy Brion</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24761</link>
		<dc:creator>Davy Brion</dc:creator>
		<pubDate>Wed, 13 Jan 2010 07:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24761</guid>
		<description>@Jason

i replied to her email before i wrote this post, stating pretty much the same thing.  I did thank her for the notification, and she already let me know that she understands now why i don&#039;t really care about it.</description>
		<content:encoded><![CDATA[<p>@Jason</p>
<p>i replied to her email before i wrote this post, stating pretty much the same thing.  I did thank her for the notification, and she already let me know that she understands now why i don&#8217;t really care about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitriy Nagirnyak</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24723</link>
		<dc:creator>Dmitriy Nagirnyak</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24723</guid>
		<description>I wouldn&#039;t ever wanted to work with a person who &quot;reports&quot; co-workers to the &quot;Authority&quot;.
Not that I disrespect the licensing and stuff, but it is just about the trust within the team.
She hadn&#039;t even bother to read Creative-Commons license.
In any case they had to solve the licensing &quot;issue&quot; inside the team and not throw bricks at each other.

The atmosphere in that team is probably very untruthful, unhealthy; last stage of cancer.

Why can&#039;t people just respect each other and stop freaking talks behind the back...</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t ever wanted to work with a person who &#8220;reports&#8221; co-workers to the &#8220;Authority&#8221;.<br />
Not that I disrespect the licensing and stuff, but it is just about the trust within the team.<br />
She hadn&#8217;t even bother to read Creative-Commons license.<br />
In any case they had to solve the licensing &#8220;issue&#8221; inside the team and not throw bricks at each other.</p>
<p>The atmosphere in that team is probably very untruthful, unhealthy; last stage of cancer.</p>
<p>Why can&#8217;t people just respect each other and stop freaking talks behind the back&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://davybrion.com/blog/2010/01/omg-someone-stole-my-code/comment-page-1/#comment-24712</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://davybrion.com/blog/?p=2170#comment-24712</guid>
		<description>I feel bad for the person that contacted you - she was clearly trying to help and you sided with the person who stole your code. I know, you don&#039;t care about the license on blogged code but at the end of the day she was trying to be helpful and did not have access to the feelings which you just made explicit or your justification for including a license.</description>
		<content:encoded><![CDATA[<p>I feel bad for the person that contacted you &#8211; she was clearly trying to help and you sided with the person who stole your code. I know, you don&#8217;t care about the license on blogged code but at the end of the day she was trying to be helpful and did not have access to the feelings which you just made explicit or your justification for including a license.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.306 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-07-29 22:59:45 -->
