{"id":216,"date":"2006-11-27T18:37:29","date_gmt":"2006-11-28T01:37:29","guid":{"rendered":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/2006\/11\/27\/compromise-attribution-rider-on-any-osi-license\/"},"modified":"2006-11-27T18:37:29","modified_gmt":"2006-11-28T01:37:29","slug":"compromise-attribution-rider-on-any-osi-license","status":"publish","type":"post","link":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/2006\/11\/27\/compromise-attribution-rider-on-any-osi-license\/","title":{"rendered":"Compromise: attribution &quot;rider&quot; on any OSI license?"},"content":{"rendered":"<p>I&#8217;ve just reviewed <a href=\"http:\/\/ross.typepad.com\/blog\/2006\/11\/socialtext_prop.html\">Ross Mayfields proposal<\/a> for an <a href=\"http:\/\/www.socialtext.net\/stoss\/index.cgi?attribution_memo\">attribution provision<\/a> that can be added to any other OSI approved license and still remain OSI approved.<\/p>\n<p>First off, I&#8217;d like to say that I think the spirit is right here.&nbsp; Instead of approving specific attribution clauses in each of the licenses, come up with one that can be added to any license.&nbsp; This DOES help with proliferation!&nbsp; Well done!<\/p>\n<p>However, the specific text is still too broad to limit a world where <a href=\"http:\/\/www.nicholasgoodman.com\/bt\/blog\/2006\/11\/15\/open-source-has-a-little-secret-exhibit-b\/\">this<\/a> is possible.<\/p>\n<p>I&#8217;m one of the strongest critics of these licenses (I don&#8217;t really matter either).&nbsp; I&#8217;m a peon who has little to benefit if these particular companies succeed or fail.&nbsp; I do have a vested interest in the success of revenue generating Open Source (ie, companies that generate real $$ from OPEN SOURCE projects).<\/p>\n<p>I&#8217;d think that if you limited the attribution clause to an appropriate statement to allow for headless\/GUI-less uses and &#8220;reasonable attribution&#8221;<\/p>\n<blockquote>\n<p><a href=\"http:\/\/www.socialtext.net\/stoss\/index.cgi?attribution_memo\"> Generic Attribution Provision<\/a><\/p>\n<p> Redistributions of the original code in binary form or source code form, must ensure that each time the resulting executable program, a display of <font color=\"#ff0000\">items (a),(b),(c) <strike>same size <\/strike><strike>as found in the original code <\/strike><\/font>released by the original licensor <i><font color=\"#ff0000\">on a <strike>(e.g., <\/strike><\/font><\/i>splash screen <font color=\"#ff0000\">or about page<strike> or banner text<\/strike>)<\/font> of the original licensor&#8217;s attribution information <font color=\"#ff0000\">if such a splash screen or about page is present in redistribution<\/font>, which includes:<\/p>\n<p> (a) Company Name<br \/>(b) Logo (if any) and<br \/>(c) URL<br \/><font color=\"#ff0000\"><br \/>Original Licensor grants limited use of Trademark and Logo as necessary to fulfill obligations of this provision.<\/font><\/p>\n<\/blockquote>\n<p>  I think this is reasonable and in line with previous OSI approvals (ie, documentation, source code, executable startup, about box).&nbsp; The trademark grant is necessary to ensure that there can&#8217;t be a royalty tied to use of the software (clearly in violation of OSD) but only so much as to comply with this provision.&nbsp; Ie, if you HAVE to put their trademarked company name\/logo on your about page they can&#8217;t come after YOU and required you to pay for use fo that mark or to stop using it.<\/p>\n<p>Is this attribution, clearly identifying the original work fo the company and community sufficient?&nbsp; This is pretty common practice in creative commons as well.&nbsp; ie, Creative commons says you have to ATTRIBUTE, not that you have to attribute in EVERY PAGE of your magazine and blog.&nbsp;&nbsp; You just have to acknowledge somewhere.&nbsp; I still think this isn&#8217;t very &#8220;open source &#8211; eee&#8221; but it&#8217;d be something would remove most of my objections.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve just reviewed Ross Mayfields proposal for an attribution provision that can be added to any other OSI approved license and still remain OSI approved. First off, I&#8217;d like to say that I think the spirit is right here.&nbsp; Instead of approving specific attribution clauses in each of the licenses, come up with one that [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[9],"tags":[],"_links":{"self":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts\/216"}],"collection":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/comments?post=216"}],"version-history":[{"count":0,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/posts\/216\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/media?parent=216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/categories?post=216"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/wp-json\/wp\/v2\/tags?post=216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}