Skip to content

Community-Meeting-Guidelines.md

Latest commit

 

History

History
79 lines (61 loc) · 3.45 KB

Community-Meeting-Guidelines.md

File metadata and controls

79 lines (61 loc) · 3.45 KB

Important:

Do not follow this process if you think you have discovered a vulnerability. Instead, please use the VMT process.

Community Meeting Guidelines

The Kata Containers community collected a list of good practices for you to follow when raising issues and adding topics to the meeting agenda, to ensure an efficient meeting with productive conversations.

Use a GitHub issue first

For a project like Kata Containers, with contributors spanning across so many different time zones, asynchronous discussions and reviews are the preferred communication media.

If you hit unexpected behavior that you think might be a bug, please just go ahead and report it as a GitHub issue.

If you have an improvement or new feature idea that you would like to get feedback on before starting to implement it, the best way to share that with the community for consideration is also through GH issues.

Advantages of using GH issues:

  • More inclusive to folks in all time zones who might not be able to attend (all of) the community calls, so you will get more visibility to your idea
  • It gives more time for folks to think through your proposal and give more meaningful feedback
  • The Architecture Committee (AC) and the community will have the opportunity to better follow the conversation and keep history

If your idea/proposal takes an extended amount of time (2 weeks or longer) for the community to discuss and the AC to weigh in on, you can follow these two steps:

  1. Bring up your GH issue in the #kata-dev Slack channel in the Kata Slack workspace.
  2. Propose it as a discussion topic for an upcoming weekly community call.

Exceptions

Topics like the below examples do not need an associated PR or GH issue:

  • Announcements
  • Presentations
  • Call for reviews of articles, blog posts, etc.

Proposing an agenda item for the community call

When you are ready to propose a new agenda item, you can do the on the etherpad that the community uses to put together the agenda for upcoming calls and take notes.

When adding a new agenda item, please also add the following information:

  • Short summary of your topic and your name in brackets
  • GH Issue or PR link, if you have it
  • Useful additional information
    • Highlight and details of your topic that will help people to catch up to the topic faster during the meeting
    • The question(s) you would like to get answers to
    • The challenge or issue that is blocking you from progressing forward in the topic area that you are working on

How to set expectations for agenda topics on the community call

When adding a topic to the agenda, one should have clearly defined expectations: "What do I want to get from the community and the AC with that discussion?".

For instance:

  • Are you looking for a possible solution to a problem exposed through GitHub or the mailing list?
  • Are you looking for a resolution of a conflict in a pull request?
  • Are you looking for a "go/no go" from the community in order to start working on something?
  • Are you looking for technical feedback and guidelines on a pending technical proposal?

Answering those questions and clearly stating the expectations upfront will help with steering the Community Call discussions in the right direction.