Hi Chris et. al., 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.
Any press release that includes PeeringDB, requires approval by a majority of the PeeringDB Board. 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. 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. Below is an edited suggestion: - Since PeeringDB serves a large, diverse community in the public interest, PeeringDB does not typically collaborate on press releases. - Routine collaboration with the Internet operations community, such as a portal that facilitates the interconnection of Internet networks, would not typically be considered exceptional. - Members of the PeeringDB community are welcome to reference PeeringDB in their press releases, such as sponsorship announcements, product release notes, etc.. -Any other press release not specified above requires a majority approval from the PeeringDB Board. Thanks, Bradley Raymo Vice President Network Strategy | StackPath P: +1 (480)739-6719 M: +1(623)703-5300Book Time on my calendar On Nov 29, 2022, at 7:26 AM, Chris Caputo via Pdb-gov <[email protected]> wrote: Happy Holidays! The PeeringDB Board is considering the below draft Press Release Policy, to be posted at: https://docs.peeringdb.com/gov/#policies ---- - 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 press release that includes PeeringDB, requires approval by a majority of the PeeringDB Board. - Only exceptional circumstances should be brought to the PeeringDB Board for 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. - 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., provided there is adherence to the PeeringDB Acceptable Use Policy. ---- In regards to the high donation example, there is no donor in mind at the present time. Feedback/questions/corrections/suggestions/objections/approval about the intent or language/grammar, etc., is welcome! Feel free to discuss on this list or provide feedback directly to the PeeringDB Stewards (Board, Officers, Committee Chairs, Product Manager) at: PeeringDB Stewards <[email protected]> I intend to facilitate a vote of the Board on this subject after December 6th. Humbly, Chris Caputo PeeringDB Secretary/Treasurer CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
