justinmclean commented on code in PR #18:
URL: https://github.com/apache/comdev/pull/18#discussion_r3349109884
##########
mcp/next-committer/PROMPT.md:
##########
@@ -0,0 +1,201 @@
+# Next Committer Candidates — AI Prompt
+
+Use this prompt (or adapt it) with your MCP-capable AI assistant to generate
+a "Next Committer Candidates" report for your Apache project.
+
+## Prerequisites
+
+Your AI tool must have access to two MCP servers:
+
+1. **ponymail-mcp** — provides `search_list`, `get_email`, `get_thread`,
`get_mbox`
+2. **apache-projects-mcp** — provides `get_committee`, `get_group_members`,
`get_person`, `search_people`, `get_releases`, `get_repositories`
+
+Additionally, the AI tool needs the ability to fetch URLs (for GitHub API
access).
+
+## The Prompt
+
+Copy and paste the following into your AI assistant, replacing `{PROJECT}` with
+your Apache project ID (e.g., `iceberg`, `spark`, `tinkerpop`):
+
+---
+
+```
+You are an Apache committer pipeline analyst. Generate a "Next Committer
+Candidates" report for Apache {PROJECT} using ONLY public data.
+
+## Data Sources — PUBLIC ONLY
+
+This report uses ONLY publicly available data:
+- Apache PonyMail (public mailing list archives)
+- GitHub public API (contributor stats, merged PRs)
+- Apache Projects LDAP (public committee/committer rosters, release history)
+
+Do NOT include any internal company data, proprietary information, or
+vendor/employer affiliations. Focus exclusively on open source contributions.
+
+## Step 1: Get current committers, PMC, and recent promotions (DO THIS FIRST)
+
+- Use get_committee("{PROJECT}") — this returns the full PMC roster WITH join
+ dates. Record join dates to identify recent promotions (last 12 months).
+- Use get_group_members("{PROJECT}") for committers.
+- Use get_group_members("{PROJECT}-pmc") for PMC members.
+- Store these lists. Every person you encounter MUST be checked against them
+ before being placed in a section.
+
+## Step 2: Get release history (PMC candidate signal)
+
+- Use get_releases("{PROJECT}") to get recent releases.
+- Note release managers — managing a release is strong evidence for PMC
+ readiness.
Review Comment:
While it is possible for a committer to be a release manager, in practice,
this is extremely rare.
--
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]
