[PDB Gov] Draft PeeringDB Press Release Policy - feedback requested

[Chris Caputo]

On Tue, 29 Nov 2022, Brad Raymo wrote:
> The policy seems contradictory. In one statement all press releases 
> require board approval and then further down it states it is not 
> required. If I am reading this incorrectly, please let me know.

Hi Brad,

Good catch. The intent is to clarify the process by which PeeringDB will 
entertain a joint press release, rather than attempt to police non-joint 
press releases.

Thus I wonder if it would be sufficient to clarify as follows. (new draft 
& diff below)

> The AUP does not reference press releases so either the AUP needs to be 
> updated or the policy needs to remove reference to the AUP.

I have also updated this section below.

Thanks,
Chris

----
  - DRAFT
  - PeeringDB
  - Press Release Policy
  - Approved by Board [Month Date, Year]

  - Since PeeringDB serves a large diverse community in the public 
    interest, PeeringDB does not normally collaborate on press releases.

  - Any joint press release that includes PeeringDB and another entity,
    requires approval by a majority of the PeeringDB Board.

  - Only exceptional circumstances should be brought to the PeeringDB 
    Board for joint press release consideration.

  - An example of an exceptional circumstance would be a donor wishing a 
    joint press release accompany a donation that dramatically exceeds
    our highest published sponsorship tier.

  - Routine collaboration with the Internet operations community, such as 
    for a portal that facilitates the interconnection of Internet 
    networks, would not normally be considered exceptional.

  - Members of the PeeringDB community are welcome to reference PeeringDB 
    in their own press releases, such sponsorship announcements, product 
    release notes, etc.
----

Diff:

----
@@ -7,15 +7,15 @@
   - Since PeeringDB serves a large diverse community in the public 
     interest, PeeringDB does not normally collaborate on press releases.
 
-  - Any press release that includes PeeringDB, requires approval by a 
-    majority of the PeeringDB Board.
+  - Any joint press release that includes PeeringDB and another entity,
+    requires approval by a majority of the PeeringDB Board.
 
   - Only exceptional circumstances should be brought to the PeeringDB 
-    Board for press release consideration.
+    Board for joint press release consideration.
 
   - An example of an exceptional circumstance would be a donor wishing a 
-    press release accompany a donation that dramatically exceeds our 
-    highest published sponsorship tier.
+    joint press release accompany a donation that dramatically exceeds
+    our highest published sponsorship tier.
 
   - Routine collaboration with the Internet operations community, such as 
     for a portal that facilitates the interconnection of Internet 
@@ -23,6 +23,5 @@
 
   - Members of the PeeringDB community are welcome to reference PeeringDB 
     in their own press releases, such sponsorship announcements, product 
-    release notes, etc., provided there is adherence to the PeeringDB 
-    Acceptable Use Policy.
+    release notes, etc.
----