|
| 1 | +{%extends "base/page.html"%} |
| 2 | +{%block title%}Archives Policy{%endblock%} |
| 3 | +{%block contents%} |
| 4 | + |
| 5 | +<h1>Archives Policy <i class="fas fa-gavel"></i></h1> |
| 6 | + |
| 7 | +<p><em>Last updated: February 6, 2019</em></p> |
| 8 | + |
| 9 | +<p>The PostgreSQL <a href="/list/">mailing lists</a> are archived at |
| 10 | + www.postgresql.org. This site is intended to provide an accurate |
| 11 | + representation of the activity on the lists, and as such will not be |
| 12 | + modified.</p> |
| 13 | + |
| 14 | +<h2>Why won't you remove my post?</h2> |
| 15 | + |
| 16 | +<p>There are a number of reasons why we will not remove or modify messages in |
| 17 | + the archives:</p> |
| 18 | + |
| 19 | +<ul> |
| 20 | + <li>We want the archives to accurately represent the history of our public |
| 21 | + mailing lists. |
| 22 | + </li> |
| 23 | + <li>Messages posted to our mailing lists are archived by other organisations |
| 24 | + outside of our control, as well as in every list subscriber's inbox. |
| 25 | + Removing a message from our archives would only be the tip of the |
| 26 | + iceberg. |
| 27 | + </li> |
| 28 | + <li>Due to the way the archives are stored and occasionally regenerated from |
| 29 | + archived mailbox files, there is no way to permanently modify a message. |
| 30 | + </li> |
| 31 | + <li>We have limited volunteer resources to run the project (and no |
| 32 | + non-volunteer resources) and would prefer to use those resources to |
| 33 | + produce great database management software than to rewrite history. |
| 34 | + </li> |
| 35 | +</ul> |
| 36 | + |
| 37 | +<h2>E-Mail Disclaimers and Licencing</h2> |
| 38 | + |
| 39 | +<p>Some companies or organization add footers to outgoing e-mail messages with |
| 40 | + that group's e-mail policies, such as this simple example:</p> |
| 41 | + |
| 42 | +<blockquote>This e-mail is confidential and only for use by the intended |
| 43 | + recipient. |
| 44 | +</blockquote> |
| 45 | + |
| 46 | +<p>These disclaimers are incompatible with sending messages to the PostgreSQL |
| 47 | + mailing lists. When the mailing list is the "intended recipient", that |
| 48 | + includes all of its current subscribers and the archives. These archives are |
| 49 | + public, archived, and searchable; they cannot be made confidential.</p> |
| 50 | + |
| 51 | +<p>By choosing to send messages to a PostgreSQL mailing list, you are implicitly |
| 52 | + granting your permission for that message to be archived in that fashion, |
| 53 | + regardless of any e-mail disclaimer it might have. Additionally, source code |
| 54 | + submissions to mailing lists such as pgsql-hackers are considered |
| 55 | + submissions to the PostgreSQL project, falling under the project's |
| 56 | + <a href="/about/licence/">PostgreSQL licence</a>. Please make sure you have |
| 57 | + permission to share information with these lists before sending your |
| 58 | + message.</p> |
| 59 | + |
| 60 | +{%endblock%} |
0 commit comments