<div dir="ltr"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div>For web apps, you can add an attribution file at a known path, e.g: <a href="http://foo.com/attribution.md">foo.com/attribution.md</a>, this is easy to check even if the link is not visible.</div><div><br></div><div>For desktop apps, in the menu you can add a "about" entry somewhere. Many open source apps are crediting the project developers this way.</div><div dir="ltr"><br style="color:rgb(111,123,138);font-family:Arial;font-size:13px"><br style="color:rgb(111,123,138);font-family:Arial;font-size:13px"><table style="border-spacing:0px;border-collapse:collapse;background-color:transparent;color:rgb(111,123,138);font-family:Arial;font-size:13px"><tbody><tr><td width="80" style="padding:0px"><a href="https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures" style="background-color:transparent;color:rgb(13,99,143);outline:0px" target="_blank"><img src="http://img-cdn.prestashop.com/signatures/signature-logo.png" alt="PrestaShop" width="68" height="85" border="0" style="border:0px;vertical-align:middle"></a></td><td style="padding:0px"><p style="margin:0px;font-stretch:normal;font-size:15px;line-height:normal;font-family:"Open Sans",Arial,Helvetica,sans-serif;color:rgb(52,57,67)"><span style="font-weight:700">Antoine Thomas aka ttoine</span></p><p style="margin:0px 0px 4px;font-stretch:normal;font-size:12px;line-height:normal;font-family:"Open Sans",Arial,Helvetica,sans-serif;color:rgb(52,57,67)">Developer Advocate</p><p style="margin:0px 0px 4px;font-stretch:normal;font-size:12px;line-height:normal;font-family:"Open Sans",Arial,Helvetica,sans-serif;color:rgb(104,115,127)"><span style="display:inline-block">t: +33 (0)6 63 13 79 06</span></p><p style="margin:0px 0px 7px;font-stretch:normal;line-height:normal;font-family:"Open Sans",Arial,Helvetica,sans-serif;color:rgb(104,115,127)"><a href="mailto:antoine.thomas@prestashop.com" style="background-color:transparent;color:rgb(104,115,127);outline:0px" target="_blank">antoine.thomas@prestashop.com</a></p></td></tr><tr><td colspan="2" height="10" style="padding:0px;font-size:1px"><br></td></tr></tbody></table><br></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 4 Dec 2018 at 11:35, <Simon.Cox@csiro.au> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, a cluttering of logos is clearly a risk if everyone did this. <br>
<br>
It is not meant as 'advertising' in the conventional sense - rather, it is a form of attribution. We are a team within a public sector agency. Locally we prefer to release most of our products as open-source, but this is somewhat under suspicion from some folk up the chain. Our argument for doing it is that we have bigger impact this way, and that as a public sector organization it is appropriate for the community as a whole to get the benefit of our work. But our bosses are also accountable further up the chain for the public funding that supports the work, and need to have evidence of its impact. If credits were visible on all the websites that had deployed our applications, then that would do. <br>
<br>
In the cases that we know about we've been able to negotiate it through informal channels. But there are other deployments that we come across that we were unaware of, and the one-on-one approach is not scalable above a handful. It would all be cleaner if we could just point to a license that included the requirement, then if that were respected (!) then everyone would be happy - the users would have open-source software, and we would have evidence that it was in use to show to our paymasters. <br>
<br>
I don't think the intention is counter to the spirit of the OSD. But is there a better approach? <br>
<br>
Simon <br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 4 Dec 2018 07:07:41 +0000<br>
From: <Simon.Cox@csiro.au><br>
To: <<a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a>><br>
Subject: [License-discuss] Open source license with obligation to<br>
display an attribution?<br>
Message-ID:<br>
<<a href="mailto:3155add0d064491fad317abcb622abe4@exch1-mel.nexus.csiro.au" target="_blank">3155add0d064491fad317abcb622abe4@exch1-mel.nexus.csiro.au</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Is there an open source license that also includes an obligation on the user to make public attribution of use of the software in a specific form?<br>
<br>
What I have in mind is for software that is used to drive a web-site, where we just want to request that a logo with the words "Powered by ACME technology" is displayed on the website.<br>
<br>
Simon J D Cox<br>
Research Scientist - Environmental Informatics<<a href="https://research.csiro.au/ei" rel="noreferrer" target="_blank">https://research.csiro.au/ei</a>><br>
Team Leader - Environmental Information Infrastructure<br>
CSIRO Land and Water<<a href="http://www.csiro.au/Research/LWF" rel="noreferrer" target="_blank">http://www.csiro.au/Research/LWF</a>><br>
<br>
E simon.cox@csiro.au<mailto:<a href="mailto:simon.cox@csiro.au" target="_blank">simon.cox@csiro.au</a>> T +61 3 9545 2365 M +61 403 302 672<br>
Mail: Private Bag 10, Clayton South, Vic 3169<br>
Visit: Central Reception, Research Way, Clayton, Vic 3168 ///honey.zebra.chip<<a href="https://w3w.co/honey.zebra.chip" rel="noreferrer" target="_blank">https://w3w.co/honey.zebra.chip</a>><br>
Deliver: Gate 3, Normanby Road, Clayton, Vic 3168<br>
<a href="http://people.csiro.au/Simon-Cox" rel="noreferrer" target="_blank">people.csiro.au/Simon-Cox</a><<a href="http://people.csiro.au/Simon-Cox" rel="noreferrer" target="_blank">http://people.csiro.au/Simon-Cox</a>><br>
<a href="http://orcid.org/0000-0002-3884-3420" rel="noreferrer" target="_blank">orcid.org/0000-0002-3884-3420</a><<a href="http://orcid.org/0000-0002-3884-3420" rel="noreferrer" target="_blank">http://orcid.org/0000-0002-3884-3420</a>><br>
<a href="http://researchgate.net/profile/Simon_Cox3" rel="noreferrer" target="_blank">researchgate.net/profile/Simon_Cox3</a><<a href="https://www.researchgate.net/profile/Simon_Cox3" rel="noreferrer" target="_blank">https://www.researchgate.net/profile/Simon_Cox3</a>><br>
<a href="http://github.com/dr-shorthair" rel="noreferrer" target="_blank">github.com/dr-shorthair</a><<a href="https://github.com/dr-shorthair" rel="noreferrer" target="_blank">https://github.com/dr-shorthair</a>><br>
<a href="http://lov.okfn.org/dataset/lov/agents/Simon%20Cox" rel="noreferrer" target="_blank">lov.okfn.org/dataset/lov/agents/Simon%20Cox</a><<a href="http://lov.okfn.org/dataset/lov/agents/Simon%20Cox" rel="noreferrer" target="_blank">http://lov.okfn.org/dataset/lov/agents/Simon%20Cox</a>><br>
Twitter @dr_shorthair<<a href="https://twitter.com/dr_shorthair" rel="noreferrer" target="_blank">https://twitter.com/dr_shorthair</a>><br>
Skype dr_shorthair<skype:dr_shorthair><br>
<a href="https://xkcd.com/1810/" rel="noreferrer" target="_blank">https://xkcd.com/1810/</a><br>
<br>
PLEASE NOTE<br>
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20181204/b2260236/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20181204/b2260236/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 4 Dec 2018 01:24:03 -0800<br>
From: Danese Cooper <<a href="mailto:danese@gmail.com" target="_blank">danese@gmail.com</a>><br>
To: <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
Subject: Re: [License-discuss] Open source license with obligation to<br>
display an attribution?<br>
Message-ID:<br>
<<a href="mailto:CALKqTu-Z_vPzjXg7Z-1W_%2BZcJUTESOLZHq6WMvtfNse-hOAHrw@mail.gmail.com" target="_blank">CALKqTu-Z_vPzjXg7Z-1W_+ZcJUTESOLZHq6WMvtfNse-hOAHrw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Yes. We created one back in 2002, in response to SugarCRM decision to<br>
impose a ridiculous requirement that their attribution be permanently<br>
displayed in the center of any page using derivatives of their code. We<br>
felt that the persistence of the display in their requirement was an<br>
obvious attempt to halt reuse of their code, which is counter to the spirit<br>
of the OSD. But we did decide that a brief attribution might be a desirable<br>
gesture in some cases. The resulting OSI-approved (though seldom-used)<br>
license is called the Attribution Assurance License.<br>
<br>
D<br>
<br>
On Mon, Dec 3, 2018 at 11:08 PM <Simon.Cox@csiro.au> wrote:<br>
<br>
> Is there an open source license that also includes an obligation on the<br>
> user to make public attribution of use of the software in a specific form?<br>
><br>
><br>
><br>
> What I have in mind is for software that is used to drive a web-site,<br>
> where we just want to request that a logo with the words ?Powered by ACME<br>
> technology? is displayed on the website.<br>
><br>
><br>
><br>
> *Simon J D Cox *<br>
><br>
> Research Scientist - Environmental Informatics<br>
> <<a href="https://research.csiro.au/ei" rel="noreferrer" target="_blank">https://research.csiro.au/ei</a>><br>
><br>
> Team Leader ? Environmental Information Infrastructure<br>
><br>
> CSIRO Land and Water <<a href="http://www.csiro.au/Research/LWF" rel="noreferrer" target="_blank">http://www.csiro.au/Research/LWF</a>><br>
><br>
><br>
><br>
> *E* simon.cox@csiro.au *T* +61 3 9545 2365 *M* +61 403 302 672<br>
><br>
> *Mail:* Private Bag 10, Clayton South, Vic 3169<br>
><br>
> * Visit: *Central Reception, Research Way, Clayton, Vic 3168<br>
> ///honey.zebra.chip <<a href="https://w3w.co/honey.zebra.chip" rel="noreferrer" target="_blank">https://w3w.co/honey.zebra.chip</a>><br>
><br>
> * Deliver: *Gate 3, Normanby Road, Clayton, Vic 3168<br>
><br>
> <a href="http://people.csiro.au/Simon-Cox" rel="noreferrer" target="_blank">people.csiro.au/Simon-Cox</a><br>
><br>
> <a href="http://orcid.org/0000-0002-3884-3420" rel="noreferrer" target="_blank">orcid.org/0000-0002-3884-3420</a><br>
><br>
> <a href="http://researchgate.net/profile/Simon_Cox3" rel="noreferrer" target="_blank">researchgate.net/profile/Simon_Cox3</a><br>
> <<a href="https://www.researchgate.net/profile/Simon_Cox3" rel="noreferrer" target="_blank">https://www.researchgate.net/profile/Simon_Cox3</a>><br>
><br>
> <a href="http://github.com/dr-shorthair" rel="noreferrer" target="_blank">github.com/dr-shorthair</a><br>
><br>
> <a href="http://lov.okfn.org/dataset/lov/agents/Simon%20Cox" rel="noreferrer" target="_blank">lov.okfn.org/dataset/lov/agents/Simon%20Cox</a><br>
><br>
> Twitter @dr_shorthair <<a href="https://twitter.com/dr_shorthair" rel="noreferrer" target="_blank">https://twitter.com/dr_shorthair</a>><br>
><br>
> Skype dr_shorthair<br>
><br>
> <a href="https://xkcd.com/1810/" rel="noreferrer" target="_blank">https://xkcd.com/1810/</a><br>
><br>
><br>
><br>
> *PLEASE NOTE*<br>
><br>
> The information contained in this email may be confidential or privileged.<br>
> Any unauthorised use or disclosure is prohibited. If you have received this<br>
> email in error, please delete it immediately and notify the sender by<br>
> return email. Thank you. To the extent permitted by law, CSIRO does not<br>
> represent, warrant and/or guarantee that the integrity of this<br>
> communication has been maintained or that the communication is free of<br>
> errors, virus, interception or interference.<br>
><br>
><br>
><br>
> *Please consider the environment before printing this email.*<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> License-discuss mailing list<br>
> <a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20181204/1f4d2b9e/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20181204/1f4d2b9e/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 4 Dec 2018 09:30:14 +0000<br>
From: David Woolley <<a href="mailto:forums@david-woolley.me.uk" target="_blank">forums@david-woolley.me.uk</a>><br>
To: <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
Subject: Re: [License-discuss] Open source license with obligation to<br>
display an attribution?<br>
Message-ID: <<a href="mailto:d0f39ef4-47e1-1f60-62c6-bfbdc4061c73@david-woolley.me.uk" target="_blank">d0f39ef4-47e1-1f60-62c6-bfbdc4061c73@david-woolley.me.uk</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
On 04/12/2018 07:07, Simon.Cox@csiro.au wrote:<br>
> Is there an open source license that also includes an obligation on the<br>
> user to make public attribution of use of the software in a specific form?<br>
><br>
<br>
The original BSD licence had an advertising clause, but advertising<br>
clauses are now considered a bad idea because effective use of the open<br>
source concept would result in user interfaces being cluttered by dozens<br>
of adverts.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of License-discuss Digest, Vol 81, Issue 1<br>
**********************************************<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
</blockquote></div>