Most Apache projects already have someone who does community work -- answering newcomer questions, triaging good-first-issues, showing up at conferences. The problem isn't that these people don't exist; it's that they're invisible, unsupported, and unconnected to each other. The Project Ambassador proposal is about finding those people and giving them tools and a peer network.
We ask projects "Who's your community person?" and then support whoever they name -- with a metrics dashboard for their project, templates for contributor onboarding, a Good First Issues aggregator, and a weekly office hour where ambassadors from different projects share what's working. Ambassadors report to their own PMC, not to ComDev. We recruit, equip, connect, and recognize -- we don't assign or manage. Full proposal: https://github.com/apache/comdev-working-groups/blob/main/proposed/ambassadors.md Includes the toolkit we'd provide, a graduation outreach process for recruiting ambassadors from newly-graduated projects, and email templates. Feedback welcome -- particularly on whether this matches what your project actually needs, or whether it's Yet Another Thing nobody asked for. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
