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

[Owen DeLong]

I’m OK with this proposed revision, but I suggest that such a withdrawal should
be for some defined time, rather than indefinite/permanent.

Owen


> On Dec 9, 2022, at 08:59, Chris Caputo via Pdb-gov <pdb-gov at lists.peeringdb.com> wrote:
> 
> There's been a revision to the draft, which the PeeringDB Board is now 
> considering.
> 
> New draft, and diff versus the previous draft, is below.
> 
> Feedback welcome!
> 
> 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. PeeringDB reserves the right to withdraw this
>    permission on a per entity basis.
> ----
> 
> Diff:
> 
> ----
> @@ -23,5 +23,6 @@
> 
>   - Members of the PeeringDB community are welcome to reference PeeringDB
>     in their own press releases, such sponsorship announcements, product
> -    release notes, etc.
> +    release notes, etc. PeeringDB reserves the right to withdraw this
> +    permission on a per entity basis.
> ----