docs: clarify security guidance#2961
Open
He-Pin wants to merge 1 commit into
Open
Conversation
Motivation: The security announcements page should use Apache Pekko-specific reporting guidance and keep readers on the Apache Pekko security announcements page for project security information. Modification: Clarify that issues affecting Apache Pekko and its predecessor project should be reported to the Apache Pekko team first, describe responsible disclosure coordination with affected upstream maintainers, and update the security-related documentation link to the Apache Pekko security announcements page. Result: The security documentation now avoids predecessor project branding in authored text, links to the Apache Pekko security announcements page, and better matches the Apache Pekko reporting process. Tests: - git diff --check / passed - sbt docs/paradox / passed with existing duplicate-anchor warnings in release notes only References: Upstream commit: akka/akka-core@fe097c3, which is now Apache licensed Refs #31927 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
He-Pin
force-pushed
the
port-fe097c3-security-announcements
branch
from
be5ce49 to
eccad3b
Compare
pjfanning
reviewed
May 9, 2026
|
|
||
| Ideally, any issues affecting Apache Pekko and Akka should be reported to Apache team first. We will share the | ||
| report with the Lightbend Akka team. | ||
| Ideally, any issues affecting Apache Pekko and its predecessor project should be reported to the Apache Pekko team |
Member
There was a problem hiding this comment.
I don't see why we shouldn't name Akka here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.