mirror of https://github.com/dapr/community.git
Merge pull request #568 from dapr/update-issue-templates
Update issue templates + new maintainer onboarding
This commit is contained in:
commit
ca8109704a
|
@ -3,7 +3,7 @@ name: Community Call Agenda Issue
|
|||
about: Create a new community call agenda
|
||||
title: '<date>, Community Call Agenda'
|
||||
assignees: ''
|
||||
label: 'community call'
|
||||
label: ["community call"]
|
||||
---
|
||||
|
||||
## 📞 Dapr Community Call Live Stream
|
||||
|
|
|
@ -0,0 +1,37 @@
|
|||
---
|
||||
name: Maintainer Onboarding Request
|
||||
about: Request to onboard a maintainer for one or more Dapr repositories
|
||||
title: 'REQUEST: Onboard <new-maintainer-GH-handle> as maintainer'
|
||||
labels: area/github-membership
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### GitHub Username
|
||||
|
||||
<new-maintainer-GH-handle>
|
||||
|
||||
### STC decision
|
||||
|
||||
_Link to the GitHub issue that contains the STC decision about onboarding the new maintainer._
|
||||
|
||||
### GitHub repositories
|
||||
|
||||
_List the repositories the member will have maintainer access._
|
||||
|
||||
- <repository_name>
|
||||
- <repository_name>
|
||||
|
||||
### Checklist for repo maintainers
|
||||
|
||||
- [ ] Add new maintainer to _maintainers-<repo>_ GitHub team.
|
||||
|
||||
### Checklist for _dapr/community_ maintainer
|
||||
|
||||
- [ ] Add maintainer to [MAINTAINERS.md](https://github.com/dapr/community/blob/master/MAINTAINERS.md).
|
||||
- [ ] Add maintainer to [CNCF project-maintainers.csv](https://github.com/cncf/foundation/blob/main/project-maintainers.csv).
|
||||
- [ ] Add maintainer to _Dapr Maintainers & Community Managers_ doc on Google Drive.
|
||||
- [ ] Invite maintainer to Dapr 1Password.
|
||||
- [ ] Add maintainer to _Maintainers_ Vault in 1Password.
|
||||
- [ ] Add maintainer to _maintainers_ role on Discord.
|
||||
- [ ] Add maintainer to [CNCF Dapr Maintainers](https://lists.cncf.io/g/cncf-dapr-maintainers/) email list via [CNCF Service Desk](https://cncfservicedesk.atlassian.net/servicedesk/customer/portals).
|
|
@ -22,9 +22,15 @@ _List the repositories you would like to be removed from as a maintainer._
|
|||
- <repository_name>
|
||||
- <repository_name>
|
||||
|
||||
### Checklist for repo maintainers
|
||||
|
||||
- [ ] Remove maintainer from _maintainers-<repo>_ GitHub team.
|
||||
|
||||
### Checklist for _dapr/community_ maintainer
|
||||
|
||||
- [ ] Remove maintainer from [MAINTAINERS.md](https://github.com/dapr/community/blob/master/MAINTAINERS.md).
|
||||
- [ ] Remove maintainer from [CNCF project-maintainers.csv](https://github.com/cncf/foundation/blob/main/project-maintainers.csv).
|
||||
- [ ] Remove maintainer from _Dapr Maintainers & Community Managers_ doc on Google Drive.
|
||||
- [ ] Remove maintainer from _Maintainers_ Vault in 1Password.
|
||||
- [ ] Remove maintainer from _maintainers_ role on Discord.
|
||||
- [ ] Remove maintainer from [CNCF Dapr Maintainers](https://lists.cncf.io/g/cncf-dapr-maintainers/) email list via [CNCF Service Desk](https://cncfservicedesk.atlassian.net/servicedesk/customer/portals).
|
||||
|
|
|
@ -39,15 +39,11 @@ https://github.com/cncf/foundation/blob/main/project-maintainers.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.
|
||||
2. Create a ticket at the [CNCF Service Desk](https://cncfservicedesk.atlassian.net/servicedesk/customer/portals), select the Program Management category and submit the name and email of the new community manager.
|
||||
|
||||
### 1Password
|
||||
|
||||
The community manager requires access to these logins in 1Password:
|
||||
|
||||
- Twitter
|
||||
- Google
|
||||
- Zoom (CNCF)
|
||||
The community manager requires access to the Community Outreach vault in 1Password.
|
||||
|
||||
- Send an invite to the new Community Manager to join the Dapr 1Password account:
|
||||
- In the 1Password menu go to Invitations -> Invite by email.
|
||||
|
|
Loading…
Reference in New Issue