dapr
/
community
mirror of https://github.com/dapr/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update COMMUNITY-MANAGER.md 

Clarify responsibilities

Signed-off-by: Marc Duiker <marcduiker@users.noreply.github.com>
This commit is contained in:
Marc Duiker 2023-12-21 12:06:10 +01:00 committed by GitHub
parent 99b83105ea
commit 2fc22c5568
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 24 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
COMMUNITY-MANAGER.md
View File

@ -2,43 +2,50 @@
## Charter
Community managers are responsible for managing many aspects of the Dapr community. The role is to engage and promote the Dapr community and have someone that the community can reach out to for guidance or to raise a concern. This document outlines a list of duties that a community manager can perform.
Community managers are responsible for managing many aspects of the Dapr community. The goal is to achieve and maintain a healthy and growing Dapr community where everyone feels welcome and is encouraged to share knowledge and learn from each other. This document outlines the responsibilities of a community manager and the process involved in becoming one.
### Duties
### Responsibilities
A community manager can perform the following duties:
A community manager has the following responsibilities:
* Manage the Discord community including organizing and monitoring the Discord channels, establishing community rules, and aiding on the overall health of the Discord community.
* Manage the Dapr community calls:
* Participate in the rotating schedule to host the call.
* Find speakers to present Dapr related sessions.
* Collect community content to highlight during the _show and tell_ section.
* Publish the community call recording to the Dapr YouTube channel.
* Manage the Discord community:
* Organize and monitor Discord channels.
* Ensure community rules are being followed.
* Help new Discord users find the right channels & answers.
* Review and publish Dapr blog posts submitted by the community.
* Plan, manage and host Dapr community calls.
* Plan, prepare sharable content, and ensure overall health of Dapr community meetups.
* Report out regularly on community health, growth trends, and top issues to maintainers and STC.
* Can propose new partnerships with other adjacent communities to STC and then manage them.
* Manage community analytics tools including Google Analytics, CommonRoom.io and Scarf.sh.
* 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://www.youtube.com/@daprdev) YouTube account.
### Duties that require STC approval
* Add new analytics tools
## Process to become a Community Manager
## Process to become a community manager
Self-nominate via a [new issue in the community repository](https://github.com/dapr/community/issues/new) stating why you want to be an community manager, or alternatively contact an STC member. A community manager needs approval from 3 or more STC members.
Self-nominate via a [new issue in the community repository](https://github.com/dapr/community/issues/new) stating why you want to be an community manager, or alternatively, contact an STC member. A community manager needs approval from three or more STC members.
Once a community manager is approved they are added to the [MAINTAINERS.md](./MAINTAINERS.md) file including a non-voting statement to indicate the community manager does not have voting rights as the regular maintainers do.
Once a community manager is approved, they are added to the [MAINTAINERS.md](./MAINTAINERS.md) file, including a non-voting statement to indicate the community manager does not have voting rights as the regular maintainers do.
## Limits and Expiration
The community manager role expires 12 months from the date it was approved. Reapproval is then required. To minimize the number of people to coordinate between, there can a maximum of 3 active community manager.
The community manager role expires 12 months from the date it was approved. Reapproval is then required. To minimize the number of people to coordinate between, there is a maximum of three active community managers.
## Removal
The community manager role is removed in case of the following:
* Expiration of the 12 months term.
* STC votes with simple majority to remove Community Manager.
The community manager role is removed in the following cases:
* Expiration of the 12-month term.
* STC votes with a simple majority to remove the community manager.
* The community manager can ask to have themselves removed from the role.
## Current Community Managers
## Current community managers
The following community managers have been approved by the STC:
| Name | GitHub Handle | Discord Handle | Company | Status | Timezone | Term Start | Term End |