Difference between revisions of "ODBL non-compliance/Example email"

From Open Food Facts wiki
Jump to navigation Jump to search
(Page creation)
 
m (+ forum)
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{otherlang
 +
  | fr=FR:Non_respect_des_licences/Exemple_d'email
 +
}}
 +
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 10: Line 14:
 
The text should of course be modified according to the situation.
 
The text should of course be modified according to the situation.
  
 
+
<code><br />Subject: Open Food Facts proper credit</code>
 
<pre>
 
<pre>
 
Hello,
 
Hello,
Line 20: Line 24:
 
However, I noticed that the <data and/or the photos> seem to lack the proper credit.
 
However, I noticed that the <data and/or the photos> seem to lack the proper credit.
 
Open Food Facts's license requires that you both credit Open Food Facts and make users aware of the data license (by linking to our copyright
 
Open Food Facts's license requires that you both credit Open Food Facts and make users aware of the data license (by linking to our copyright
page). For more information, see:
+
page). Moreover, if you collect new data based on Open Food Facts data, you need to share back these data to the Open Food Facts database (share-alike clause of the licence). For more information, see:
  
 
https://world.openfoodfacts.org/terms-of-use
 
https://world.openfoodfacts.org/terms-of-use
  
The correct attribution helps to avoid misunderstandings about the source of the data or pictures, as well as what others are allowed to do with it. For the time being, ten thousands of contributors and dozens of organizations are collaboratively participating in this common pot. It creates a common ecosystem that benefits to all. This ecosystem is working as long as the common pot and its attribution is respected.
+
To properly mention Open Food Facts data and share back data based on it, we provide guidelines here: https://wiki.openfoodfacts.org/ODBL_License#How_to.3F
 +
 
 +
The correct attribution helps to avoid misunderstandings about the source of the data or pictures, as well as what others are allowed to do with it. For the time being, tens of thousands of contributors and dozens of organizations are collaboratively participating in this common pot. It creates a common ecosystem that benefits to all. This ecosystem is working as long as the common pot and its attribution are respected.
  
 
If you need help making the changes or have further questions, feel free to ask me in reply to this mail, or others in one of Open Food Facts' communication channels:
 
If you need help making the changes or have further questions, feel free to ask me in reply to this mail, or others in one of Open Food Facts' communication channels:
Line 30: Line 36:
 
* our Slack space: https://slack.openfoodfacts.org/
 
* our Slack space: https://slack.openfoodfacts.org/
 
* our global contact email: contact@openfoodfacts.org
 
* our global contact email: contact@openfoodfacts.org
 +
* our forum: https://forum.openfoodfacts.org
  
More importantly attribution helps us spread the word about Open Food Facts and attract new contributors and build the community.
+
More importantly, attribution and share-alike helps us spread the word about Open Food Facts, improve the database, attract new contributors and build the community.
This is incredibly important to improving the quality of the database that you and millions of others rely on.
+
This is incredibly important to improve the quality of the database that you and millions of others rely on.
  
 
Acknowledgement of receipt would be appreciated.
 
Acknowledgement of receipt would be appreciated.
Line 39: Line 46:
 
<name>
 
<name>
 
</pre>
 
</pre>
 +
 +
[[Category:Legal]]

Revision as of 11:46, 1 June 2023

Other languages:
/ français /

This page is highly inspired from OpenStreetMap practices, from Lacking proper attribution/Example email page.

This is an example email to use in case you spot lacking attribution or license violation.

Please stay polite and friendly in a manner that the receiver is not scared away from using Open Food Facts, but encouraged to use it with correct attribution.

The text should of course be modified according to the situation.


Subject: Open Food Facts proper credit

Hello,

As an Open Food Facts contributor, I am pleased to see that you are using Open Food Facts on your website:

<website or app>

However, I noticed that the <data and/or the photos> seem to lack the proper credit.
Open Food Facts's license requires that you both credit Open Food Facts and make users aware of the data license (by linking to our copyright
page). Moreover, if you collect new data based on Open Food Facts data, you need to share back these data to the Open Food Facts database (share-alike clause of the licence). For more information, see:

https://world.openfoodfacts.org/terms-of-use

To properly mention Open Food Facts data and share back data based on it, we provide guidelines here: https://wiki.openfoodfacts.org/ODBL_License#How_to.3F

The correct attribution helps to avoid misunderstandings about the source of the data or pictures, as well as what others are allowed to do with it. For the time being, tens of thousands of contributors and dozens of organizations are collaboratively participating in this common pot. It creates a common ecosystem that benefits to all. This ecosystem is working as long as the common pot and its attribution are respected.

If you need help making the changes or have further questions, feel free to ask me in reply to this mail, or others in one of Open Food Facts' communication channels:

* our Slack space: https://slack.openfoodfacts.org/
* our global contact email: contact@openfoodfacts.org
* our forum: https://forum.openfoodfacts.org

More importantly, attribution and share-alike helps us spread the word about Open Food Facts, improve the database, attract new contributors and build the community.
This is incredibly important to improve the quality of the database that you and millions of others rely on.

Acknowledgement of receipt would be appreciated.

Thanks,
<name>