Skip to content

Fix pmc email - #40988

Merged
damccorm merged 2 commits into
masterfrom
damccorm-patch-2
Nov 4, 2026
Merged

damccorm merged 2 commits into
masterfrom
damccorm-patch-2

Conversation

@damccorm

@damccorm damccorm commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions Bot added website size/xs XS: <10 lines changed labels Nov 4, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📋 Review Summary

This PR updates the security contact email in the Beam security documentation (website/www/site/content/en/security/_index.md) from pmc@beam.apache.org to the valid ASF private PMC mailing list private@beam.apache.org. The change is accurate and ready to merge.

🔍 General Feedback

  • LGTM! No issues found.

💡 Tip: Comment /gemini review on this pull request to trigger a new Gemini code review.

@ppkarwasz

ppkarwasz commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Hi @damccorm,

I think you should remove private@beam.apache.org. In the ASF there are currently two kinds of PMCs:

  • Those that use security@apache.org as security contact (numerical majority). We triage their reports and forward those that might be valid (according to your threat model and public documentation).
  • Those that have a security@<pmc>.apache.org and handle report directly (and receive the highest number of reports). We help them with some book keeping.

If you prefer to receive the reports directly, you can open an INFRA ticket to create security@beam.apache.org: see https://cwiki.apache.org/confluence/spaces/SECURITY/pages/303794800/Getting+help+handling+security+reports

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @Abacn for label website.
Backup reviewer: shunping (if the main reviewer is unresponsive, you can escalate to them by tagging their username)

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@Abacn Abacn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

At a moment thought it was AI hallucinating in security model PR, checked history this existed back in #10581

@damccorm

damccorm commented Nov 4, 2026

Copy link
Copy Markdown
Contributor Author

Hi @damccorm,

I think you should remove private@beam.apache.org. In the ASF there are currently two kinds of PMCs:

  • Those that use security@apache.org as security contact (numerical majority). We triage their reports and forward those that might be valid (according to your threat model and public documentation).
  • Those that have a security@<pmc>.apache.org and handle report directly (and receive the highest number of reports). We help them with some book keeping.

If you prefer to receive the reports directly, you can open an INFRA ticket to create security@beam.apache.org: see https://cwiki.apache.org/confluence/spaces/SECURITY/pages/303794800/Getting+help+handling+security+reports

Thanks, updated

@damccorm
damccorm merged commit 79c6459 into master Nov 4, 2026
7 checks passed
@damccorm
damccorm deleted the damccorm-patch-2 branch November 4, 2026 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants