potiuk commented on PR #3478: URL: https://github.com/apache/pekko/pull/3478#issuecomment-5444530329
Thanks @pjfanning — this is exactly what the draft was for, and considerably more than I hoped for. Thirteen rulings, and the provenance moves from 40 documented / 0 maintainer / 14 inferred to 43 / 48 / 3. Two of your commits correct me rather than extend me, and both are fair: `191e00d` drops a scope ruling about app-bound sockets that I inferred and shouldn't have, and `02066b0` restores the upstream-coordination wording in `SECURITY.md` that I had paraphrased — I should have preserved that verbatim rather than reworded it. **On merge order** — your branch fast-forwarded cleanly from this one, so I've pushed it here. All 19 of your commits are now on this PR with your authorship intact; no rebase, no force push, nothing resolved by hand. That leaves a single PR against `apache/pekko` carrying the full history, so pjfanning/incubator-pekko#59 can be closed whenever suits you. If you'd rather it went the other way round — yours opened against `apache/pekko` and this one closed — that's equally fine and I'll close this. It's your document now; I only wanted to avoid ending up with two. I also pushed one small follow-up commit (`9ed2a94`): the header still read `Status: DRAFT — awaiting Pekko PMC review. Not yet maintainer-ratified`, which stopped being true once you answered the questions. A triager citing §9 to close a report shouldn't be citing a document that calls itself unratified. It now reads "Reviewed by the Apache Pekko PMC, 2026-08-27" and names the one item still open. Two lines; no ruling, citation or disposition touched. That open item is the last loose end: §2's module in/out split is still the ASF Security team's proposal rather than a maintainer call, as Q6 notes. Not blocking — worth a line from you at some point so the document has no inferred claims left at all. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
