├── CODE_OF_CONDUCT.md ├── SECURITY.md ├── README.md ├── REPOSITORIES.md └── MEETING.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Prometheus Community Code of Conduct 2 | 3 | Prometheus follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md). 4 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Reporting a security issue 2 | 3 | The Prometheus security policy, including how to report vulnerabilities, can be 4 | found here: 5 | 6 | 7 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Prometheus Community 2 | 3 | The [prometheus-community organization](https://github.com/prometheus-community) collects resources and projects outside of, but associated with, the [Prometheus project](https://prometheus.io). 4 | 5 | ## Prometheus & The Ecosystem Community Meeting 6 | 7 | See [MEETING.md](MEETING.md) for information on the Prometheus & The Ecosystem Community Meeting. 8 | 9 | ## Community Repositories 10 | 11 | See [REPOSITORIES.md](REPOSITORIES.md) for information on the creation and management of repositories in this organization. 12 | -------------------------------------------------------------------------------- /REPOSITORIES.md: -------------------------------------------------------------------------------- 1 | # Community Repositories 2 | 3 | The [prometheus-community organization](https://github.com/prometheus-community) collects projects associated with [Prometheus](https://prometheus.io) that are not part of the [prometheus organization](https://github.com/prometheus) itself. 4 | 5 | Support for community projects is best-effort on the part of the Prometheus project. 6 | Each project must have a sponsor from the [Prometheus team](https://prometheus.io/governance/#team-members). 7 | 8 | ## For community members 9 | 10 | To propose adding a new repository to the prometheus-community organization, [open an issue on this repository](https://github.com/prometheus-community/community/issues). 11 | 12 | ## For sponsors 13 | 14 | ### Importing an existing repository 15 | 16 | 1. Comment on the issue that you are willing to sponsor this repository. 17 | 1. Create a [team](https://github.com/orgs/prometheus-community/teams) and add the maintainers for the new repository, unless there is already an appropriate team. 18 | 1. Transfer the repository. 19 | * If you have owner rights on both sides: 20 | 1. Transfer the repository directly. 21 | * If you do not have owner rights on the original repository: 22 | 1. Ask the owner of the existing repository to initiate the transfer into the prometheus-community organization. 23 | 1. Accept the transfer. 24 | 1. Add a `MAINTAINERS.md` listing the active maintainers, and yourself as the sponsor. 25 | 1. Subscribe to notifications for the repository. 26 | 27 | ### Creating a new repository 28 | 29 | 1. Comment on the issue that you are willing to sponsor this repository. 30 | 1. Create a [team](https://github.com/orgs/prometheus-community/teams) and add the maintainers for the new repository, unless there is already an appropriate team. 31 | 1. Create the repository. 32 | 1. In the repository Settings -> Collaborators and Teams, add the team that should manage the repository, as Admin. 33 | 1. Add a `MAINTAINERS.md` listing the active maintainers, and yourself as the sponsor. 34 | 1. Subscribe to notifications for the repository. 35 | -------------------------------------------------------------------------------- /MEETING.md: -------------------------------------------------------------------------------- 1 | # Prometheus & The Ecosystem Community Meeting 2 | 3 | We have PUBLIC and RECORDED monthly meeting every first Wednesday of the month, on odd months 9:00 am UTC([Time zone converter](https://www.thetimezoneconverter.com/?t=9%3A00%20am&tz=UTC%20(Coordinated%20Universal%20Time)&)), on even months 5:00 pm UTC([Time zone converter](https://www.thetimezoneconverter.com/?t=5%3A00%20pm&tz=UTC%20(Coordinated%20Universal%20Time)&)). 4 | 5 | See it on the web at [calendar.google.com](https://calendar.google.com/calendar/embed?src=o4g18inl0mghikksvgtd6nspms%40group.calendar.google.com), or paste this [iCal url](https://calendar.google.com/calendar/ical/o4g18inl0mghikksvgtd6nspms%40group.calendar.google.com/public/basic.ics) into any [iCal client](https://en.wikipedia.org/wiki/ICalendar). Do NOT copy the meetings over to a your personal calendar, you will miss meeting updates. Instead use your client's calendaring feature to say you are attending the meeting so that any changes made to meetings will be reflected on your personal calendar. 6 | 7 | All meetings are archived on the [Youtube Channel](https://www.youtube.com/channel/UC4pLFely0-Odea4B2NL1nWA). 8 | 9 | Quick links: 10 | 11 | - [Agenda document](https://bit.ly/prometheus-community-agenda) 12 | - [9 AM UTC Zoom meeting link](https://zoom.us/j/639056489) 13 | - [5 PM UTC Zoom meeting link](https://zoom.us/j/906107777) 14 | 15 | ## Purpose 16 | 17 | The Prometheus & The Ecosystem community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates. 18 | It also provides a forum for discussion of project-level concerns that might need a wider audience. 19 | 20 | ## Code Of Conduct 21 | 22 | The meeting follows the [Prometheus Code of Conduct](https://github.com/prometheus/prometheus/blob/main/CODE_OF_CONDUCT.md). If you notice a violation of the Code of Conduct, reach out to Mishi Choudhary at [mishi@linux.com](mailto:mishi@linux.com). 23 | 24 | ## Meeting Agenda 25 | 26 | If you have a topic you'd like to present or would like to see discussed, 27 | please propose a specific date on the [Prometheus & The Ecosystem Community Meeting Agenda](https://bit.ly/prometheus-community-agenda). 28 | 29 | General speaking the meeting is structured as follows: 30 | 31 | - Introduction by Host (~3 minutes) 32 | - Prometheus Updates & Announcements (~10 minutes) 33 | - (Optional) Ecosystem Updates & Announcements (~10 minutes) 34 | - Questions (~5 minutes) 35 | 36 | ## Updates & Announcements 37 | 38 | The first 10 minutes of a meeting are dedicated to Prometheus Updates & Announcements. The next 10 minutes are dedicated to Ecosystem Updates & Announcements. These announcements are noted at the top of the community document. There is a hard stop of the announcements at 10 minutes, with up to 5 more minutes for questions. 39 | 40 | If you want to announce something during the time allocated for announcements, contact the organizers. They will get back to you. 41 | 42 | Announcements submissions MUST follow the requirements listed below. 43 | 44 | ### Requirements 45 | 46 | This meeting has a large number of attendees. 47 | Out of respect for their time, we ask that you be fully prepared for your announcement. Make sure slides are clear if applicable, and the link to them is posted in the meeting agenda. 48 | 49 | - Your announcement should provide clear, valuable information to the community without being commercial in nature. Typical sales pitches are not permitted, and could potentially alienate your audience. 50 | - You are required to show up 10 minutes before the meeting to verify your audio and screensharing capabilities with the hosts. If you cannot make and keep this commitment, you will not be allowed to proceed with your announcement until such time you can. 51 | - You also required to commit to being available the week before your announcement date in case there is an issue with that week's announcement. 52 | - The use of a headset or other high-quality audio equipment is strongly encouraged. Typing on a laptop while using the system microphone is distracting, so please insulate your microphone from key noises. 53 | - Ensure you are presenting from a quiet environment. 54 | - If you run out of time while performing your announcement, you may ask the audience if they would like a follow-up at a subsequent meeting. If there is enthusiastic support, the community team will help schedule a continuation. 55 | 56 | ## Archives 57 | 58 | The document gets slow as we add notes, so it is archived regularly into another document. 59 | 60 | --------------------------------------------------------------------------------