I would be happy to have any kind of collaboration with the CDF Press team. We do not have many contributors in this area, and having a extra professional contributors would help the community a lot. At the same time I am *-1* for just delegating press management to the Continuous Delivery Foundation or to any other entity outside the Jenkins community. It may happen on a case by case basis, but IMHO in must not be a default behavior.
We have 5 governance board members who represent the community. We also have 5 officers who represent the community within the area of their responsibility. Any component maintainer can represent a sub-community of that component. This is how the community represented, and I see no reason to change that. The https://www.jenkins.io/press/#press-contacts page referenced by Tracy is indeed dated and needs to be updated. My counter-proposal is to work closely with the CDF and other interested parties under the umbrella of the Advocacy&Outreach SIG. - Advocacy&Outreach SIG coordinates PR for Jenkins, all interested individual and institutional contributors are welcome to join it. - The SIG provides a venue for coordination of the PR events and initiatives via its mailing list and regular meetings. Discourse might be also used once established. - If needed, we establish new dedicated channels for press communications where we have interested contributors, the CDF team, and other parties who want to join. - Private communications and NDAs, if needed for the PR activities, should be confirmed according to the standard Jenkins governance process. > In 2020 CDF started taking on some of this e.g. fielding questions from reporters during DevOps World I have a lot to say about these particular events, but this has nothing to do with the Jenkins community. DevOps World communications are managed by CloudBees, and in the particular case the company made a decision to channel questions to the CDF instead of letting some of its employees speak to reporters. No further comments, unrelated to the matter IMO. Best regards, Oleg Nenashev Jenkins Governance Board Member On Friday, June 4, 2021 at 8:30:52 PM UTC+2 Alyssa wrote: > +1 for CDF to handle Jenkins press releases. Having an experienced, > dedicated resource on this is a valuable benefit, imo. > > On Wed, Jun 2, 2021 at 10:43 AM Tracy Miranda <[email protected]> > wrote: > >> Hi all, >> >> The Continuous Delivery Foundation (CDF) offers public relations (PR) >> services to all CDF projects e.g we co-ordinated the Jenkins Graduation >> <https://www.prnewswire.com/news-releases/cd-foundation-announces-jenkins-graduation-301105709.html> >> >> announcement. >> >> *Note:* PR = public relations (not pull request) for this email >> >> *TL;DR* I'd like to propose updates to https://www.jenkins.io/press/ and >> processes around PR announcements & related activities to formalize CDF >> providing PR support for Jenkins. >> >> Background: >> Jenkins PR has been previously handled by Kohsuke, volunteer press >> contacts & the CloudBees PR team e.g Jenkins & AWS >> <https://www.cloudbees.com/press/jenkins-community-establishes-native-support-aws-serverless-application-model-creation> >> , Jenkins & Docker >> <https://www.cloudbees.com/press/jenkins-community-and-cloudbees-announce-docker-integration-next-wave-continuous-delivery> >> In >> 2020 CDF started taking on some of this e.g. fielding questions from >> reporters during DevOp World >> >> While at the simplest level blog posts can serve as community >> announcements (and should continue to do so) PR offers that next level of >> support and services typically include: >> - building relationships with relevant reporters in the space >> - pitching newsworthy announcements to reporters >> - co-ordinating announcements when there are multiple 3rd parties involved >> - identifying & co-ordinating community folks to respond to incoming >> requests >> - tracking mentions and stories related to the project >> - issuing corrections to reporters as needed (e.g this happens now & then >> around security advisories) >> (For more details see: 6 public relations lessons for open source >> projects >> <https://opensource.com/life/11/4/six-public-relations-lessons-open-source-projects> >> ) >> >> For Jenkins I'd suggest the press page be updated to [email protected]. >> At CD.Foundation we work with Jesse Casman of Story Changes Culture who >> would then sync with the governing board or any identified contacts (e.g >> security officer) to respond to incoming requests. >> >> It would also be ideal to work with the community on a related >> growth-plan with at least 1-2 announcements targeted for the year. >> >> I'll wait to hear any feedback then go ahead and submit a pull request to >> reflect some of the suggested changes. >> >> Regards, >> Tracy >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAJ2Kh8mMo4fngifx49p%2BiKxEBkFeaxLmPy0SJ5NZvAGn9%2BhBRg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAJ2Kh8mMo4fngifx49p%2BiKxEBkFeaxLmPy0SJ5NZvAGn9%2BhBRg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/18004e1b-97f7-4739-bb7f-ffae2183b57dn%40googlegroups.com.
