Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PROPOSAL] OpenSearch Operations & Project Health meeting format #187

Closed
krisfreedain opened this issue Feb 2, 2024 · 5 comments
Closed
Labels
discuss Issues calling for discussion process

Comments

@krisfreedain
Copy link
Member

krisfreedain commented Feb 2, 2024

The OpenSearch team within Amazon have been holding internal maintainer meetings on holistic project needs. To increase transparency and community ownership, this meeting needs to be in the public.

Overview:

Strengthen the OpenSearch project by addressing maintenance and health opportunities that can enable more contributions.

Scope: Health is a broad spectrum that includes security, developer experience, maintainer experience, quality and usability standards, documentation, community wellness and safety.

Agenda setting:

  • This is a bi-weekly meeting with topics nominated publicly or spilled from the previous meeting.
  • If you have a topic you would like discussed, propose it for addition to the next week’s agenda by doing [TBD].
  • At the end, if there is time, we can discuss other topics.

Proposals:

Anything to add to the Agenda setting?

Agenda building:

Where do we collaborate on building the agendas

Proposals:

  1. Forum threads.
    1. Pro: Easily accessible, public, can admins and moderators can edit original thread, already in-practice with Community Meetings & multiple triage meetings
    2. Con: outside of Github (if this is an issue)
  2. Community repo Issues
    1. Pro: Keeps central to GitHub, public, easily accessible
    2. Con: Maintainer rights required to edit Issues, whereas forum moderator rights are easier to grant

Tech:

Do we use Chime or Zoom?

Proposals:

  • Zoom: fairly standard. Great moderation tools. Licensing requirements are restrictive and require a named license holder.
  • Chime: not as common. Good moderation tools. Allows anyone with “moderator code“ to act as host to each meeting.

Any other suggestions you have?

We look forward to your input on this.
thanks - wbeckler & krisfreedain

@wbeckler wbeckler added discuss Issues calling for discussion process and removed untriaged labels Feb 2, 2024
@reta
Copy link

reta commented Feb 2, 2024

Thanks a lot @krisfreedain for summing it up!

Personally, I think we should start with Zoom and:

  • Forum thread (per meeting)
  • Keep the one single Github issue with references to the forum to all past (and upcoming) meetings

Yes, it would be 2 places but I think forum is more friendly from wider collaboration (internal + external).

@apasun
Copy link

apasun commented Feb 14, 2024

Zoom has been great with regular community meetings. Thank you doing this Kris!

@peternied
Copy link
Member

@krisfreedain Any updates, is there a schedule for these meetings?

@krisfreedain
Copy link
Member Author

Thank you all for the input. We'll work to get this scheduled ASAP

@krisfreedain
Copy link
Member Author

Coming back to close this one out. We're running this meeting on a bi-weekly schedule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issues calling for discussion process
Projects
None yet
Development

No branches or pull requests

5 participants