Increasing inclusiveness at the community group meetings

@dtig, @jgravelle-google and I had a discussion this morning about the CG meetings. We all agreed that they are working well, but it may be difficult for folks to speak up if they have questions or comments, since the meetings are very technical and require a lot of context.

We were thinking of ways to improve this, and a few ideas popped up:

• Take some time during the meeting to remind people that we value all input.
• Add an agenda item to some meetings allowing people to ask questions, rather than any particular topic.
• Provide an easier environment for this type of discussion: a mailing list, slack, discord, etc.
• Provide other avenues where new people can contribute, such as a "good-first-bug" list, improving documentation, writing examples and tests, etc.

Any thoughts or other ideas?

Start by reviewing the meeting-inclusiveness discussion and its proposed options: meeting reminders, question-focused agenda time, community channels, and new contributor pathways. Done means the group reaches agreement on a concrete approach and records the resulting next steps; no files or tests are identified in the issue.