mirror of https://github.com/dapr/community.git
Merge branch 'dapr:master' into Featuremaintainer
This commit is contained in:
commit
a28131ef1d
|
@ -141,7 +141,7 @@ for repo in my_repos:
|
|||
issue.html_url, age_str, humanize.naturaldelta(time_to_triage)))
|
||||
bugs.append(bug)
|
||||
|
||||
average_days_to_triage = (total_time_to_triage / triaged_count).total_seconds() / ONE_DAY.total_seconds()
|
||||
average_days_to_triage = (total_time_to_triage / triaged_count).total_seconds() / ONE_DAY.total_seconds() if triaged_count != 0 else 30
|
||||
expected_average_days_to_triage = (expected_total_time_to_triage / total_count).total_seconds() / ONE_DAY.total_seconds()
|
||||
triaged_under_5_days_ratio = triaged_under_5_days_count / total_count
|
||||
|
||||
|
|
|
@ -59,8 +59,7 @@ In order to de-risk potential misuse of power or suspicion of leaked credentials
|
|||
|
||||
| Name | GitHub Handle | Discord Handle | Company | Status | Timezone | Term Start | Term End |
|
||||
| - | - | - | - | - | - | - | -
|
||||
| Artur Souza | [@artursouza](https://github.com/artursouza) | artursouza#5141 | Diagrid | Active | PST | Jan 16th, 2023 | Jun 15th, 2023
|
||||
|
||||
| Artur Souza | [@artursouza](https://github.com/artursouza) | artursouza | Diagrid | Active | PST | Dec 1st, 2023 | Dec 1st, 2025
|
||||
|
||||
### Statuses
|
||||
* Active: has full access and can perform administrator duties.
|
||||
|
|
|
@ -17,11 +17,19 @@ A community manager has the following responsibilities:
|
|||
* Organize and monitor Discord channels.
|
||||
* Ensure community rules are being followed.
|
||||
* Help new Discord users find the right channels & answers.
|
||||
* Announce new Dapr releases and events.
|
||||
* Review issues & pull requests in the community repository.
|
||||
* Review and publish Dapr blog posts submitted by the community.
|
||||
* Report on community health, growth trends, and top issues to maintainers and STC.
|
||||
* Propose new partnerships with other adjacent communities to STC and manage them.
|
||||
* Manage community analytics tools, including Google Analytics, CommonRoom.io and Scarf.sh.
|
||||
* Manage the [@daprdev](https://twitter.com/daprdev) Twitter account.
|
||||
* Manage the [@daprdev](https://twitter.com/daprdev) Twitter account:
|
||||
* Asking the community for community call topics.
|
||||
* Announcing community calls (one day before and one hour before the call).
|
||||
* Announcing that the recording of the community call is available on YouTube.
|
||||
* Announcing new Dapr releases.
|
||||
* Announcing new Dapr blog posts or CNCF case studies.
|
||||
* Reposting relevant Dapr tweets from the community.
|
||||
* Manage the [@daprdev](https://www.youtube.com/@daprdev) YouTube account.
|
||||
|
||||
### Duties that require STC approval
|
||||
|
@ -50,8 +58,10 @@ The following community managers have been approved by the STC:
|
|||
|
||||
| Name | GitHub Handle | Discord Handle | Company | Status | Timezone | Term Start | Term End |
|
||||
| - | - | - | - | - | - | - | -
|
||||
| Marc Duiker | [@marcduiker](https://github.com/marcduiker) | MarcDuiker#2929 | Diagrid | Active | UTC+1/CET | Feb 15th, 2023 | Feb 15th, 2024
|
||||
| Nyemade Uversky | [@nyemade-uversky](https://github.com/nyemade-uversky) | nuversky#2099 | Microsoft | Inactive | PST | Feb 15th, 2023 | Feb 15th, 2024
|
||||
| Annu Singh | [@AnnuCode](https://github.com/annucode) | annusingh | Nirmata | Active | UTC+5.30/IST | Jan 1st, 2024 | Jan 1st, 2025
|
||||
| Cecil Phillip | [@cecilphillip](https://github.com/cecilphillip) | cecilphillip | Stripe | Active | UTC-5/EST | Jan 1st, 2024 | Jan 1st, 2025
|
||||
| Marc Duiker | [@marcduiker](https://github.com/marcduiker) | marcduiker | Diagrid | Active | UTC+1/CET | Feb 15th, 2023 | Feb 15th, 2024
|
||||
| Nyemade Uversky | [@nyemade-uversky](https://github.com/nyemade-uversky) | nuversky#2099 | Microsoft | Inactive | UTC-8/PST | Feb 15th, 2023 | Feb 15th, 2024
|
||||
|
||||
### Statuses
|
||||
* Active: Currently an active community manager.
|
||||
|
|
|
@ -4,8 +4,10 @@ This is the list of maintainers for all Dapr repositories, in alphabetical order
|
|||
|
||||
- Alessandro Segala (Microsoft) [@ItalyPaleAle](https://github.com/ItalyPaleAle)
|
||||
- Amulya Varote (Microsoft) [@amulyavarote](https://github.com/amulyavarote)
|
||||
- Annu Singh (Nirmata) [@annucode](https://github.com/annucode) (non voting)
|
||||
- Artur Souza (Diagrid) [@artursouza](https://github.com/artursouza)
|
||||
- Bernd Verst (Microsoft) [@berndverst](https://github.com/berndverst)
|
||||
- Cecil Phillip (Stripe) [cecilphillip](https://github.com/cecilphillip) (non voting)
|
||||
- Hannah Hunter (Microsoft) [@hhunter-ms](https://github.com/hhunter-ms)
|
||||
- Hal Spang (Microsoft) [@halspang](https://github.com/halspang)
|
||||
- Long Dai (Intel) [@daixiang0](https://github.com/daixiang0)
|
||||
|
@ -13,7 +15,6 @@ This is the list of maintainers for all Dapr repositories, in alphabetical order
|
|||
- Mark Fussell (Diagrid) [@msfussell](https://github.com/msfussell)
|
||||
- Mukundan Sundararajan (Microsoft) [@mukundansundar](https://github.com/mukundansundar)
|
||||
- Nick Greenfield (Microsoft) [@greenie-msft](https://github.com/greenie-msft)
|
||||
- Nyemade Uversky (Microsoft) [@nyemade-uversky](https://github.com/nyemade-uversky) (non voting)
|
||||
- Paul Yuknewicz (Microsoft) [@paulyuk](https://github.com/paulyuk)
|
||||
- Rob Landers (Automattic) [@withinboredom](https://github.com/withinboredom)
|
||||
- Ryan Nowak (Microsoft) [@rynowak](https://github.com/rynowak)
|
||||
|
|
|
@ -69,11 +69,9 @@ When adding new scheduled meetings to this list:
|
|||
|
||||
| Date & time | Agenda
|
||||
| - | -
|
||||
| Wednesday September 20<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230920T09&p1=234&msg=Dapr+Community+Call) | dapr/community#341
|
||||
| Wednesday October 4<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231004T09&p1=234&msg=Dapr+Community+Call) | dapr/community#342
|
||||
| Wednesday October 18<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231018T09&p1=234&msg=Dapr+Community+Call) | dapr/community#343
|
||||
| Wednesday November 1<sup>st</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231101T09&p1=234&msg=Dapr+Community+Call) | dapr/community#344
|
||||
| Wednesday November 15<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231115T09&p1=234&msg=Dapr+Community+Call) | dapr/community#345
|
||||
| Wednesday January 10<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240110T09&p1=234&msg=Dapr+Community+Call) | dapr/community#375
|
||||
| Wednesday January 24<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240124T09&p1=234&msg=Dapr+Community+Call) | dapr/community#376
|
||||
| Wednesday February 7<sup>th</sup> 9:00am Pacific Time (PST) - [See it in your local time and add to your calendar](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240207T09&p1=234&msg=Dapr+Community+Call) | dapr/community#377
|
||||
|
||||
#### China Community Meetings
|
||||
|
||||
|
|
|
@ -0,0 +1,75 @@
|
|||
## Community Manager Onboarding (for maintainers)
|
||||
|
||||
These are actions that need to be performed by a Dapr project maintainer to give access to a new community manager.
|
||||
|
||||
The following information is needed from the new community manager:
|
||||
|
||||
- Full name
|
||||
- Company name
|
||||
- Email address
|
||||
- GitHub username
|
||||
- Discord username
|
||||
|
||||
### Update the Dapr Maintainers & Community Managers doc
|
||||
|
||||
Add the community manager to the [_Dapr Maintainers & Community Managers_ document](https://docs.google.com/document/d/1FRTKgEih_lWlTM5e5ZeTSwPxIwvWyWZhtWr8KCx8CXo) on the Dapr Google Drive.
|
||||
|
||||
### Update the Maintainers.md
|
||||
|
||||
Add the community manager to the [MAINTAINERS.md](MAINTAINERS.md) file.
|
||||
|
||||
The format should be:
|
||||
|
||||
```
|
||||
<First name> <Last name> (<Company>) <GitHub username> (non voting)
|
||||
```
|
||||
|
||||
### Update the CNCF project-maintainers.csv
|
||||
|
||||
In order to get access to the CNCF service desk and receive emails from CNCF, two actions need to be done:
|
||||
|
||||
1. The community manager needs to be added to the [project-maintainers.csv](
|
||||
https://github.com/cncf/foundation/blob/main/project-maintainers.csv).
|
||||
|
||||
- Create a PR to add the community manager to the project-maintainers.csv file.
|
||||
|
||||
The format of the entry should be:
|
||||
|
||||
```csv
|
||||
,,<Full name>,<Company>,<GitHub username>,
|
||||
```
|
||||
|
||||
1. An email need to be sent to _cncf-maintainer-changes@cncf.io_ with the name and email of the new community manager.
|
||||
|
||||
### 1Password
|
||||
|
||||
The community manager requires access to these logins in 1Password:
|
||||
|
||||
- Twitter
|
||||
- Google
|
||||
- Zoom (CNCF)
|
||||
|
||||
- Send an invite to the new Community Manager to join the Dapr 1Password account:
|
||||
- In the 1Password menu go to Invitations -> Invite by email.
|
||||
|
||||
### GitHub access
|
||||
|
||||
The community manager requires maintainer access to the [community](https://github.com/dapr/community) and [blog](https://github.com/dapr/blog) repositories.
|
||||
|
||||
Add the community manager to these Dapr org teams on GitHub:
|
||||
|
||||
- maintainers-community
|
||||
- maintainers-blog
|
||||
|
||||
The community manager is mostly likely not a member of the Dapr org on GitHub. By adding them to the above org teams they will receive an invite to join the Dapr org.
|
||||
|
||||
### Discord
|
||||
|
||||
The community manager requires access to perform management and moderation tasks on the Dapr Discord server.
|
||||
|
||||
- [Invite](https://bit.ly/dapr-discord) the community manager to the Dapr Discord server.
|
||||
- Add the community manager to the _Community Manager_, _release observers_, and _maintainers_ roles on Discord:
|
||||
|
||||
- In Discord go to Server Settings -> Roles -> [Role] -> Manage Members -> Add Member.
|
||||
|
||||
- Add the community manager to the _Community Sync_ DM group on Discord.
|
|
@ -0,0 +1,75 @@
|
|||
## Community Manager Onboarding (for community managers)
|
||||
|
||||
This document contains information about the tools and processes that are used by the Dapr community managers.
|
||||
|
||||
Community managers are encouraged to update this file to improve the onboarding process.
|
||||
|
||||
### 1Password
|
||||
|
||||
Dapr uses 1Password that contains credentials for the various accounts that are used by the Dapr team members.
|
||||
|
||||
The community manager will receive an email from on of the project maintainers with an invite to join the Dapr 1Password account.
|
||||
|
||||
### Planning community calls
|
||||
|
||||
For planning and managing community calls, the community manager adds issues and edit them in the [community repo](https://github.com/dapr/community).
|
||||
|
||||
Once new community calls have been planned, update the community repo [README.md](README.md) with the new dates.
|
||||
|
||||
### Hosting community calls
|
||||
|
||||
Zoom is used for the Dapr community calls which are hosted by the community manager.
|
||||
|
||||
Join the call 15 minutes before the start of the call and have the other speakers join early as well so they can test their audio and screen sharing.
|
||||
|
||||
Zoom credentials can be found in the Dapr 1password account.
|
||||
|
||||
### Discord
|
||||
|
||||
The Dapr Discord server is used for community discussions and Q&A. The responsibility of the community manager is to manage and moderate the Discord server.
|
||||
|
||||
In case the community manager want to invite people to the Dapr Discord server, use this [invite link](https://bit.ly/dapr-discord).
|
||||
|
||||
The _Community Sync_ DM group is used by community managers to discuss moderation and management tasks, and to plan community calls.
|
||||
|
||||
### Twitter
|
||||
|
||||
The [Dapr Twitter](https://twitter.com/daprdev) account is used for posting important updates and reposting relevant tweets from the community. See the list of [community manager responsibilities](COMMUNITY-MANAGER.md#responsibilities).
|
||||
|
||||
The Dapr Twitter credentials can be found in the Dapr 1Password account.
|
||||
|
||||
### YouTube
|
||||
|
||||
The community call recordings are published to [YouTube](https://www.youtube.com/@daprdev). Links are added to the video description, and video chapters are added for easy navigation.
|
||||
|
||||
Example Dapr Community Call video description:
|
||||
|
||||
```
|
||||
Slides: (link to Google slides (read-only))
|
||||
|
||||
Claim the Dapr Community supporter badge: https://bit.ly/dapr-supporter
|
||||
Join the Dapr Discord: http://bit.ly/dapr-discord
|
||||
|
||||
Blog posts:
|
||||
(list blog posts here)
|
||||
|
||||
Videos:
|
||||
(list blog posts here)
|
||||
|
||||
0:00 Intro
|
||||
2:00 Session 1: Topic
|
||||
20:00 Session 2: Topic
|
||||
40:00 Community show & tell
|
||||
```
|
||||
|
||||
The Dapr Google credentials can be found in the Dapr 1Password account.
|
||||
|
||||
### Google Drive
|
||||
|
||||
Google Drive is used for storing the Dapr community call slides.
|
||||
|
||||
- A new slide deck is created for each community call. Copy the most recent deck and rename it.
|
||||
- Update the deck with the new date, host name and the agenda.
|
||||
- Share the deck (with edit rights) with the speakers and in the _Community Sync_ Discord group.
|
||||
|
||||
The Dapr Google credentials can be found in the Dapr 1Password account.
|
|
@ -75,23 +75,21 @@ The current membership of the STC is:
|
|||
|
||||
| | Member | Organization | Profile | Term Start | Term End |
|
||||
| -------------------------------------------------------------- | ---------------- | ------------ | ---------------------------------------------------- | ---------- | --------
|
||||
| <img width="30px" src="https://github.com/yaron2.png"> | Yaron Schneider | Diagrid | [@yaron2](https://github.com/yaron2) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/msfussell.png"> | Mark Fussell | Diagrid | [@msfussell](https://github.com/msfussell) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/daxiang0.png"> | Loong Dai | Intel | [@daxiang0](https://github.com/daxiang0) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/cvictory.png"> | Victory Cao | Alibaba | [@cvictory](https://github.com/cvictory) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/olitomlinson.png"> | Oli Tomlinson | Dotmatics | [@olitomlinson](https://github.com/olitomlinson) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/johnewart.png"> | John Ewart | Microsoft | [@johnewart](https://github.com/johnewart) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/paulyuk.png"> | Paul Yuknewicz | Microsoft | [@paulyuk](https://github.com/paulyuk) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/yaron2.png"> | Yaron Schneider | Diagrid | [@yaron2](https://github.com/yaron2) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/msfussell.png"> | Mark Fussell | Diagrid | [@msfussell](https://github.com/msfussell) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/daxiang0.png"> | Loong Dai | Intel | [@daxiang0](https://github.com/daxiang0) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/jaczhao.png"> | Qingjie Zhao | Alibaba | [@jackzhao](https://github.com/jaczhao) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/olitomlinson.png"> | Oli Tomlinson | Dotmatics | [@olitomlinson](https://github.com/olitomlinson) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/johnewart.png"> | John Ewart | Microsoft | [@johnewart](https://github.com/johnewart) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
| <img width="30px" src="https://github.com/paulyuk.png"> | Paul Yuknewicz | Microsoft | [@paulyuk](https://github.com/paulyuk) | 1st Dec 2023 | Nov 30th 2025 |
|
||||
|
||||
## Emeritus members
|
||||
The following emeritus members are recognized for their previous role on the STC.
|
||||
|
||||
| | Member | Organization | Profile |
|
||||
| -------------------------------------------------------------- | ---------------- | ------------ | --------------------------------------------------|
|
||||
|
|
||||
| <img width="30px" src="https://github.com/jaczhao.png"> | Qingjie Zhao | Alibaba | [@jackzhao](https://github.com/jaczhao) |
|
||||
| <img width="30px" src="https://github.com/forrest-zhao.png"> | Forrest Zhao | Intel | [@forrest-zhao](https://github.com/forrest-zhao) |
|
||||
|
||||
| -------------------------------------------------------------- | ---------------- | ------------ | -------------------------------------------------|
|
||||
| <img width="30px" src="https://github.com/cvictory.png"> | Victory Cao | Alibaba | [@cvictory](https://github.com/cvictory) |
|
||||
| <img width="30px" src="https://github.com/forrest-zhao.png"> | Forrest Zhao | Intel | [@forrest-zhao](https://github.com/forrest-zhao) |
|
||||
|
||||
## Decision process
|
||||
|
||||
|
|
Loading…
Reference in New Issue