You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,11 +69,9 @@ When adding new scheduled meetings to this list:
69
69
70
70
| Date & time | Agenda
71
71
| - | -
72
-
| 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
73
-
| 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
74
-
| 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
75
-
| 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
76
-
| 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
72
+
| 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
73
+
| 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
74
+
| 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
These are actions that need to be performed by a Dapr project maintainer to give access to a new community manager.
4
+
5
+
The following information is needed from the new community manager:
6
+
7
+
- Full name
8
+
- Company name
9
+
- Email address
10
+
- GitHub username
11
+
- Discord username
12
+
13
+
### Update the Dapr Maintainers & Community Managers doc
14
+
15
+
Add the community manager to the [_Dapr Maintainers & Community Managers_ document](https://docs.google.com/document/d/1FRTKgEih_lWlTM5e5ZeTSwPxIwvWyWZhtWr8KCx8CXo) on the Dapr Google Drive.
16
+
17
+
### Update the Maintainers.md
18
+
19
+
Add the community manager to the [MAINTAINERS.md](MAINTAINERS.md) file.
- Create a PR to add the community manager to the project-maintainers.csv file.
35
+
36
+
The format of the entry should be:
37
+
38
+
```csv
39
+
,,<Full name>,<Company>,<GitHub username>,
40
+
```
41
+
42
+
1. An email need to be sent to _[email protected]_ with the name and email of the new community manager.
43
+
44
+
### 1Password
45
+
46
+
The community manager requires access to these logins in 1Password:
47
+
48
+
- Twitter
49
+
- Google
50
+
- Zoom (CNCF)
51
+
52
+
- Send an invite to the new Community Manager to join the Dapr 1Password account:
53
+
- In the 1Password menu go to Invitations -> Invite by email.
54
+
55
+
### GitHub access
56
+
57
+
The community manager requires maintainer access to the [community](https://github.com/dapr/community) and [blog](https://github.com/dapr/blog) repositories.
58
+
59
+
Add the community manager to these Dapr org teams on GitHub:
60
+
61
+
- maintainers-community
62
+
- maintainers-blog
63
+
64
+
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.
65
+
66
+
### Discord
67
+
68
+
The community manager requires access to perform management and moderation tasks on the Dapr Discord server.
69
+
70
+
-[Invite](https://bit.ly/dapr-discord) the community manager to the Dapr Discord server.
71
+
- Add the community manager to the _Community Manager_, _release observers_, and _maintainers_ roles on Discord:
72
+
73
+
- In Discord go to Server Settings -> Roles -> [Role] -> Manage Members -> Add Member.
74
+
75
+
- Add the community manager to the _Community Sync_ DM group on Discord.
## Community Manager Onboarding (for community managers)
2
+
3
+
This document contains information about the tools and processes that are used by the Dapr community managers.
4
+
5
+
Community managers are encouraged to update this file to improve the onboarding process.
6
+
7
+
### 1Password
8
+
9
+
Dapr uses 1Password that contains credentials for the various accounts that are used by the Dapr team members.
10
+
11
+
The community manager will receive an email from on of the project maintainers with an invite to join the Dapr 1Password account.
12
+
13
+
### Planning community calls
14
+
15
+
For planning and managing community calls, the community manager adds issues and edit them in the [community repo](https://github.com/dapr/community).
16
+
17
+
Once new community calls have been planned, update the community repo [README.md](README.md) with the new dates.
18
+
19
+
### Hosting community calls
20
+
21
+
Zoom is used for the Dapr community calls which are hosted by the community manager.
22
+
23
+
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.
24
+
25
+
Zoom credentials can be found in the Dapr 1password account.
26
+
27
+
### Discord
28
+
29
+
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.
30
+
31
+
In case the community manager want to invite people to the Dapr Discord server, use this [invite link](https://bit.ly/dapr-discord).
32
+
33
+
The _Community Sync_ DM group is used by community managers to discuss moderation and management tasks, and to plan community calls.
34
+
35
+
### Twitter
36
+
37
+
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).
38
+
39
+
The Dapr Twitter credentials can be found in the Dapr 1Password account.
40
+
41
+
### YouTube
42
+
43
+
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.
44
+
45
+
Example Dapr Community Call video description:
46
+
47
+
```
48
+
Slides: (link to Google slides (read-only))
49
+
50
+
Claim the Dapr Community supporter badge: https://bit.ly/dapr-supporter
51
+
Join the Dapr Discord: http://bit.ly/dapr-discord
52
+
53
+
Blog posts:
54
+
(list blog posts here)
55
+
56
+
Videos:
57
+
(list blog posts here)
58
+
59
+
0:00 Intro
60
+
2:00 Session 1: Topic
61
+
20:00 Session 2: Topic
62
+
40:00 Community show & tell
63
+
```
64
+
65
+
The Dapr Google credentials can be found in the Dapr 1Password account.
66
+
67
+
### Google Drive
68
+
69
+
Google Drive is used for storing the Dapr community call slides.
70
+
71
+
- A new slide deck is created for each community call. Copy the most recent deck and rename it.
72
+
- Update the deck with the new date, host name and the agenda.
73
+
- Share the deck (with edit rights) with the speakers and in the _Community Sync_ Discord group.
74
+
75
+
The Dapr Google credentials can be found in the Dapr 1Password account.
| <imgwidth="30px"src="https://github.com/yaron2.png"> | Yaron Schneider | Diagrid |[@yaron2](https://github.com/yaron2)| 1st Dec 2023 | Nov 30th 2025|
79
-
| <imgwidth="30px"src="https://github.com/msfussell.png"> | Mark Fussell | Diagrid |[@msfussell](https://github.com/msfussell)| 1st Dec 2023 | Nov 30th 2025|
80
-
| <imgwidth="30px"src="https://github.com/daxiang0.png"> | Loong Dai | Intel |[@daxiang0](https://github.com/daxiang0)| 1st Dec 2023 | Nov 30th 2025|
81
-
| <imgwidth="30px"src="https://github.com/cvictory.png"> | Victory Cao| Alibaba |[@cvictory](https://github.com/cvictory)| 1st Dec 2023 | Nov 30th 2025|
82
-
| <imgwidth="30px"src="https://github.com/olitomlinson.png"> | Oli Tomlinson | Dotmatics |[@olitomlinson](https://github.com/olitomlinson)| 1st Dec 2023 | Nov 30th 2025|
83
-
| <imgwidth="30px"src="https://github.com/johnewart.png"> | John Ewart | Microsoft |[@johnewart](https://github.com/johnewart)| 1st Dec 2023 | Nov 30th 2025 |
84
-
| <imgwidth="30px"src="https://github.com/paulyuk.png"> | Paul Yuknewicz |Microsoft |[@paulyuk](https://github.com/paulyuk)| 1st Dec 2023 | Nov 30th 2025|
78
+
| <imgwidth="30px"src="https://github.com/yaron2.png"> | Yaron Schneider | Diagrid |[@yaron2](https://github.com/yaron2)| 1st Dec 2023 | Nov 30th 2025 |
79
+
| <imgwidth="30px"src="https://github.com/msfussell.png"> | Mark Fussell | Diagrid |[@msfussell](https://github.com/msfussell)| 1st Dec 2023 | Nov 30th 2025 |
80
+
| <imgwidth="30px"src="https://github.com/daxiang0.png"> | Loong Dai | Intel |[@daxiang0](https://github.com/daxiang0)| 1st Dec 2023 | Nov 30th 2025 |
81
+
| <imgwidth="30px"src="https://github.com/jaczhao.png"> | Qingjie Zhao| Alibaba |[@jackzhao](https://github.com/jaczhao)| 1st Dec 2023 | Nov 30th 2025 |
82
+
| <imgwidth="30px"src="https://github.com/olitomlinson.png"> | Oli Tomlinson | Dotmatics |[@olitomlinson](https://github.com/olitomlinson)| 1st Dec 2023 | Nov 30th 2025 |
83
+
| <imgwidth="30px"src="https://github.com/johnewart.png"> | John Ewart | Microsoft |[@johnewart](https://github.com/johnewart)| 1st Dec 2023 | Nov 30th 2025 |
84
+
| <imgwidth="30px"src="https://github.com/paulyuk.png"> | Paul Yuknewicz | Microsoft |[@paulyuk](https://github.com/paulyuk)| 1st Dec 2023 | Nov 30th 2025 |
85
85
86
86
## Emeritus members
87
87
The following emeritus members are recognized for their previous role on the STC.
0 commit comments