-
Notifications
You must be signed in to change notification settings - Fork 481
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2763 from nateynateynate/opensearchcon/2024/europ…
…e/sessions/how-to-become-an-opensearch-project-repo-maintainer Welcome to the conference DB! Glad you can come!
- Loading branch information
Showing
2 changed files
with
64 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
63 changes: 63 additions & 0 deletions
63
...con_sessions/2024-europe-how-to-become-an-opensearch-project-repo-maintainer.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
--- | ||
# | ||
# The expected filename format is ${conference_id}-${url-encoded-session-title}.md | ||
# For example the "Community Inclusion" session from the 2023 conference in North America the title is "2023-north-america-community-inclusion.html" | ||
# | ||
session_time: "time TBD" | ||
|
||
session_room: "a room yet to be determined." | ||
|
||
# Conference session speaker short name that maps to a short_name value | ||
# in the community members collection. | ||
primary_presenter: 'dblock' | ||
|
||
# Conference session speaker full name. | ||
speaker_name_full: 'Daniel Doubrovkine' | ||
|
||
# Conference session title. | ||
speaker_talk_title: 'How to become an OpenSearch Project repo maintainer' | ||
|
||
# Page level 1 header title. | ||
primary_title: 'How to become an OpenSearch Project repo maintainer' | ||
|
||
# Page document title displayed in the browser title bar. | ||
title: 'OpenSearchCon 2024 Session: How to become an OpenSearch Project repo maintainer' | ||
|
||
breadcrumbs: | ||
icon: community | ||
items: | ||
- title: OpenSearchCon | ||
url: /events/opensearchcon/index.html | ||
- title: 2024 | ||
url: /events/opensearchcon/2024/index.html | ||
- title: North America | ||
url: /events/opensearchcon/2024/europe/index.html | ||
- title: Session Summaries | ||
url: /events/opensearchcon/2024/europe/sessions/index.html | ||
# Session date / time | ||
# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm)) | ||
|
||
|
||
# Session topic track. | ||
session_track: "Community" | ||
|
||
# URL permalink for the session. | ||
permalink: '/events/opensearchcon/sessions/how-to-become-an-opensearch-project-repo-maintainer.html' | ||
|
||
# ID of the YouTube video of the session to embed in the page. | ||
# This is to be added after the conference and after the session recordings | ||
# are uploaded to YouTube. | ||
#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID' | ||
|
||
# Conference ID. | ||
# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'. | ||
conference_id: '2024-europe' | ||
|
||
# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any). | ||
presenters: | ||
- dblock | ||
|
||
--- | ||
As of March 2024, 113 GitHub repos in opensearch-project have 231 maintainers. What is their story? What are their responsibilities? In this session you will hear about the journeys of a couple of most active community maintainers, and learn about how to become a maintainer yourself. | ||
|
||
Maintainers are active and visible members of the OpenSearch community, and have maintain-level permissions on a repository. With great power comes a lot of responsibilities: maintainers write code, but also use those privileges to serve the community, uphold the code of conduct, review pull requests, triage issues, provide feedback, and so much more. Ready to volunteer for more work and become a maintainer, but don't know how? This talk is for you. |