There were, I think, 8 or 9 of us there. And it was largely social, but we also did useful things.
Attendees discussed several topics: - We reviewed the published proposal at https://github.com/apache/comdev-working-groups/blob/main/proposed/ambassadors.md - The program starts as a peer knowledge-exchange venue -- a place for project community champions to compare notes and share solutions. Not external evangelism or a formal liaison structure, at least initially. - "Ambassador" means the person a project already treats as its community champion -- visible community leads who show up to events and do the work. ComDev identifies and supports them; it doesn't appoint them. - The Speaker Travel Program in the proposal is distinct from the existing Travel Assistance Committee (TAC). The proposed model: donor-funded pool, volunteer/merit-driven selection (same vendor-neutrality rules as TAC). Funding comes from donors; outreach and selection stays volunteer-led. This runs as its own program, structurally parallel to TAC, not folded into it. - The metrics dashboard referenced in the proposal is already running at https://boxofclue.com/comdev-metrics/ -- externally hosted for now, with a request to move it onto ComDev infrastructure. - Next step: outreach to pilot projects begins (Airflow, Cassandra, CloudStack, plus 5 recent Incubator graduations). - A new effort or working group was proposed: organizing ComDev's community-facing documentation and policies (community.apache.org content, program policy pages, and related artifacts). Three co-owners were assigned. Scope is not yet broken down -- this was the kickoff, not a plan. --- Next office hours: same time next week. Agenda items welcome on-list. However, I should note that I won’t be available for next week’s meeting, as I’ll be traveling. So if someone wants to pick this up and make it happen, I’d be much obliged. If not, then I’ll see y’all at the next one. —Rich --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
