apache / apache/shardingsphere-on-cloud

[Schedule] Community Duty

Open
#103 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
88
Forks
33
PR merge metrics
No merged PRs in 30d

Description

## Why?
Hello everyone, in order to better operate the ShardingSphere community and allow issues and PRs in the community to be dealt with in a timely manner, we plan to arrange a community duty schedule.

## Who can be on duty?
Apache ShardingSphere community members, all persons interested in ShardingSphere.

## What needs to be done on duty?
Please refer to the duty guide: https://shardingsphere.apache.org/community/en/involved/committer/responsibilities/
It doesn't matter if you don't have permission to operate the ShardingSphere repository, you just need to reply or mention relevant people in the issue or PR, and community members will tag the issue/PR, assign people, merge code, etc.

## How to participate on duty?
Please choose your preferred date of duty by yourself.
If you have permission to edit the current discussion directly, please edit the schedule directly to add your duty wishes date. If you don't have permission, you can leave a message about your willingness to be on duty date in the current discussion, and a community member will assist you in completing the registration.

## Schedule
| Start Date | End Date | Person | Remark |
| ---- | --- | --- | --- |
| 2022/10/24 | 2022/10/30 | @mlycore | |
| 2022/10/31 | 2022/11/6 | @windghoul | |
| 2022/11/7 | 2022/11/13 |@xuanyuan300 | |
| 2022/11/14 | 2022/11/20 |@wbtlb | |
| 2022/11/21 | 2022/11/27 | @mlycore| |
| 2022/11/28 | 2022/12/4 | @windghoul | |
| 2022/12/5 | 2022/12/11 |@xuanyuan300 | |
| 2022/12/12 | 2022/12/18 |@wbtlb | |
| 2022/12/19 | 2022/12/25 |@mlycore | |
| 2022/12/26 | 2023/1/1 |@windghoul | |
| 2023/1/2 | 2023/1/8 | @xuanyuan300| |
| 2023/1/9 | 2023/1/15 |@wbtlb | |
| 2023/1/16 | 2023/1/22 |@mlycore | |
| 2023/1/23 | 2023/1/29 |@windghoul | |
| 2023/1/30 | 2023/2/5 |@xuanyuan300 | |
| 2023/2/6 | 2023/2/12 |@wbtlb | |
| 2023/2/13 | 2023/2/19 |@mlycore | |
| 2023/2/20 | 2023/2/26 |@xuanyuan300 | |
| 2023/2/27 | 2023/3/5 |@wbtlb | |
| 2023/3/6 | 2023/3/12 |@mlycore | |
| 2023/3/13 | 2023/3/19 |@xuanyuan300 | |
| 2023/3/20 | 2023/3/26 |@wbtlb | |
| 2023/3/27 | 2023/4/2 |@mlycore | |
| 2023/4/2 | 2023/4/9 |@xuanyuan300 | |
| 2023/4/10 | 2023/4/16 |@wbtlb | |
| 2023/4/17 | 2023/4/23 |@Xu-wentao | |
| 2023/4/24 | 2023/4/30 |@mlycore | |

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.