René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Review of Official DRF Public Channel Content Guidelines","articleBody":"## Review of Official DRF Public Channel Content Guidelines\n\n### Summary\n\nThis issue requests Steering Committee review of recent content posted or amplified through official DevRel Foundation public channels, including the DRF LinkedIn page.\n\nThe current [[DRF site contribution and content guidelines](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md) were established before the current Steering Committee. This issue asks whether those guidelines should apply consistently to all official DRF public and community-facing channels.\n\nThis issue is not intended to call out any individual. The goal is to clarify whether recent posts comply with DRF’s content guidelines, mission, values, and governance expectations.\n\n### Issue 1: Opinion article reposted on an official DRF public channel\n\nA recent post on the official DRF LinkedIn page reposted an article from an individual in the DevRel industry. The article included the following statement:\n\n\u003e “Trying to justify the profession to people who have already decided that, regardless, they need those meaningless results in the short term in order to appease the shareholders.”\n\nThis framing raises concern because it appears inconsistent with the DRF mission:\n\n\u003e “To elevate the professional practice of developer relations and increase awareness of it as a driver of business value.”\n\nThe LinkedIn repost also included this statement:\n\n\u003e “If this profession wants to keep great people, we have to do better. We need clearer expectations, healthier measures of success, and leadership that understands the long-term value of trust, education, and community. And we need to stop treating burnout as an individual failure when it is often a systems problem.”\n\nSome of these points may be reasonable and relevant to the profession. The concern is whether an official DRF public channel should amplify an external opinion article that may be viewed as adversarial, unsupported by cited data, or inconsistent with DRF’s mission to elevate the profession and demonstrate DevRel’s business value.\n\n### Relevant DRF content guidelines\n\nThe DRF content guidelines include [[Content We Welcome](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-welcome)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-welcome), which states that blog posts should:\n\n* Focus on Developer Relations Foundation best practices, frameworks, or insights.\n* Be applicable to our [[community personas](https://github.com/DevRel-Foundation/persona-library/blob/main/data/sets/dev-rel.org/DEVREL-FOUNDATION.md)](https://github.com/DevRel-Foundation/persona-library/blob/main/data/sets/dev-rel.org/DEVREL-FOUNDATION.md).\n* Provide practical value to DevRel professionals as a resource. We want solutions, not just questions and opinions.\n* Share knowledge about DevRel and Linux Foundation resources and projects.\n* Present vendor-neutral perspectives and solutions.\n* Include original insights, case studies, or research.\n\nThe guidelines also include [[Content We Don’t Publish](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish), which states that DRF will not publish:\n\n* Job postings or recruitment content unless it is about a DevRel Foundation resource.\n* Backlink farming or SEO-focused content.\n* Promoted events without broader community value.\n* Content primarily advertising third-party commercial products.\n* Personal opinions without broader applicability or incorporation into Foundation resources.\n* Content that violates our Code of Conduct.\n\nThis issue asks the Steering Committee to clarify whether these standards apply to official DRF social channels, including LinkedIn, Discord announcements, newsletters, and other Foundation-owned public communications.\n\nSuggested clarification:\n\n\u003e These content guidelines apply to all official DRF public and community-facing channels, including the website, blog, LinkedIn, Discord announcements, newsletters, and any other Foundation-owned communications channel.\n\n### Code of Conduct reference\n\nThe [[DRF Code of Conduct](https://github.com/DevRel-Foundation/governance/blob/main/code_of_conduct.md)](https://github.com/DevRel-Foundation/governance/blob/main/code_of_conduct.md) states that it applies within community spaces and when an individual is officially representing the community in public spaces, including “posting via an official social media account.”\n\nThis issue is not asking the Steering Committee to make an immediate Code of Conduct finding. It asks the Steering Committee to review whether official DRF public channel use aligns with current content guidelines, mission alignment, and governance expectations.\n\n### External community feedback\n\nSeveral current and former community members raised concerns about the post. Their names are not included here to respect their request for anonymity.\n\nComments shared include:\n\n1. “The tone is completely at odds with the foundation message.”\n\n2. “That framing feels inconsistent with a Foundation message intended to elevate the profession and build broader understanding of DevRel’s business value. It presents a negative, adversarial view that I do not believe reflects the broader community. The endorsement on our community page of this is troublesome and misaligned with our values as a DRF.”\n\n### Issue 2: Job postings on official DRF public channels\n\nThere have also been several job postings or reposts shared through official DRF public channels that do not appear to be affiliated with DRF or LF.\n\nThe current [[Content We Don’t Publish](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish) section states that DRF does not publish:\n\n\u003e “Job postings or recruitment content unless it is about a DevRel Foundation resource.”\n\nDRF is not currently positioned as a job board. If the Steering Committee wants DRF to support job sharing, that should be discussed and approved as a separate policy. For example, the SC may decide to create a dedicated Discord channel or another clearly designated space for job postings.\n\nAs a comparison point, [[TODO Group](https://todogroup.org/)](https://todogroup.org/) is also a community-driven Linux Foundation project. Its public LinkedIn presence appears focused on OSPO resources, research, events, and project-related updates, not on serving as a general job board for unrelated third-party roles.\n\nDRF should follow a similarly clear standard unless the Steering Committee votes to create a dedicated job-sharing policy or channel. Until then, DRF’s current content guideline should apply: DRF does not publish “job postings or recruitment content unless it is about a DevRel Foundation resource.”\n\nUntil then, job postings not affiliated with DRF or LF should not be posted through official DRF public channels, as this could create the appearance of selective or inconsistent content promotion.\n\nThere appear to be at least five recent job-related posts or reposts that should be reviewed against the current guidelines.\n\n### Related references\n\n* [[DRF site contribution and content guidelines](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md)\n* [[Content We Welcome](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-welcome)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-welcome)\n* [[Content We Don’t Publish](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#content-we-dont-publish)\n* [[Review Criteria](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#review-criteria)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#review-criteria)\n* [[Site-Wide Content Standards](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#site-wide-content-standards)](https://github.com/DevRel-Foundation/site/blob/main/CONTRIBUTING.md#site-wide-content-standards)\n* [[DRF Code of Conduct](https://github.com/DevRel-Foundation/governance/blob/main/code_of_conduct.md)](https://github.com/DevRel-Foundation/governance/blob/main/code_of_conduct.md)\n* [[DRF community personas](https://github.com/DevRel-Foundation/persona-library/blob/main/data/sets/dev-rel.org/DEVREL-FOUNDATION.md)](https://github.com/DevRel-Foundation/persona-library/blob/main/data/sets/dev-rel.org/DEVREL-FOUNDATION.md)\n* [[TODO Group](https://todogroup.org/)](https://todogroup.org/)\n\n### Requested Steering Committee review\n\n@DevRel-Foundation/steering-committee Please review this issue and provide input.\n\nThis issue requests Steering Committee review and vote on the following:\n\n1. Whether the reposted opinion article was appropriate for an official DRF public channel.\n2. Whether the post aligns with DRF’s current content guidelines, mission, values, and governance expectations.\n3. Whether job postings or recruitment content not affiliated with DRF or LF should be removed from official DRF public channels.\n4. Whether the current content guidelines should apply to all official DRF public and community-facing channels.\n5. Whether a content review or approval process should be required before posts are published or amplified from DRF-owned public channels.\n6. Whether a content committee or designated review group should be created.\n\n### Proposed interim approach\n\nUntil the Steering Committee reviews and votes on this issue, posts that raise reasonable concerns under the current content guidelines should be temporarily removed or paused from official DRF public channels.\n\nThis includes:\n\n* Personal opinion articles that have not been reviewed for mission alignment or broader Foundation applicability.\n* Job postings or recruitment content not affiliated with DRF or LF.\n* Third-party promotional content that does not clearly provide broader community value.\n* Posts that could reasonably be interpreted as an official DRF position without review or approval.\n\nIf the Steering Committee determines that a removed post aligns with DRF guidelines, the post can be restored.\n\n### Proposed response date\n\nPlease provide Steering Committee input by July 15, 2026.\n\nAfter that date, a proposal can be drafted to amend, clarify, or refine the current content guidelines where applicable.","author":{"url":"https://github.com/Kruzn1","@type":"Person","name":"Kruzn1"},"datePublished":"2026-07-03T20:26:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/36/.github/issues/36"}