[2023 Q2 Developer Activities]: Call For Participation！

[ilixiaocui]

Contributions are welcomed!

Since Curve's open source, it has received extensive attention from the industry. Contributions are welcomed!

BTW, it's better to file a PR for every single function.

For more details, please refer to our dev guideline.

• https://ask.opencurve.io/t/topic/142

---

We have provided some topics:

1、Cloud native deployment (Languages: Go), mentor: @caoxianfei1

Func	Issue	Assigne	PR	Progress
Feature optimization	opencurve/curve-operator#24	@anurnomeru	opencurve/curve-operator#49	Done
Stand-alone deployment	opencurve/curve-operator#25	@caoxianfei1	opencurve/curve-operator#52	Done
Monitor deployment	opencurve/curve-operator#26	@caoxianfei1	opencurve/curve-operator#64	Done
$\color{#FF0000} Hard$ Disk discovery	opencurve/curve-operator#27	@xzt1590
Code clean	opencurve/curve-operator#28	@hezhizhen	opencurve/curve-operator#38	Done
$\color{#FF0000} Hard$ Update cluster	opencurve/curve-operator#29
Formating progress show	opencurve/curve-operator#30

2、New tool support (Languages: Go), mentor: @Cyber-SiKu

Func	Issue	Assigne	PR	Progress
transfer-leader	#2022	@Xinlong-Chen	2452	Done
do-snapshot	#2023	@Xinlong-Chen	2454	Done
clean-recycle	#2032	@lng2020	2351	Done
chunkserver-list	#2036	@Sindweller	2386	Done
$\color{#FF0000} Hard$ chunkserver-status	#2344	@TheR1sing3un		Done
client-status	#2345	@Xinlong-Chen	2446	Done
snapshot-clone-status	#2346	@Xinlong-Chen	2442	Done
$\color{#FF0000} Hard$ copysets-status	#2347	@tobehardest		Done
do-snapshot-all	#2352	@iiiuwioajdks
$\color{#FF0000} Hard$ check-chunkserver	#2353	@lng2020
$\color{#FF0000} Hard$ check-copyset	#2354	@baytan0720	2435	Done
check-server	#2355	@pengpengSir	2463
list-may-broken-vol	#2356	@baytan0720	2518	Done
set-copyset-availflag	#2357	@baytan0720	2455	Done
rapid-leader-schedule	#2359	@montaguelhz		Done
set-scan-state	#2360	@montaguelhz	2465	Done
scan-state	#2361	@lianzhanbiao	2481	Done
clean up code about peer/configs	#2451

3、Modification of code logic (Languages: C++), mentor: @ilixiaocui @wuhongsong

Func	Issue	Assigne	PR	Progress
[curve] optimize some metric style	#2319	@Xinlong-Chen	#2417	Done
[build] Upgrade Image	#2305	@DuckdanB
[curve] add libfmt to WORKSPACE	#2291	@Tangruilin	#2367
[monitor] Use tdengine as the data engine for promethues	#2027	@KeeProMise
[curvefs] Can metaserver's raft snapshot implementation be asynchronous	#1617	@Ziy1-Tan
[compile] Clean up warnings in code compilation	#1264	@MizukiCry	#2383	Done
[curvefs] When the fs mount is mounted multiple times with different enableSumInDir switches, the xattr information recorded in the metadata will be inaccurate	#2094	@bit-dance	#2491	Done
[curvefs] cancel the warm-up task in the warm-up queue	#2019	@Tom-CaoZH
[curvefs] change the data organization format	#2380	@201341	#2420	Done
[curvefs] add qos for curve-fuse	#2225	@UniverseParticle	#2424	Done
[curvefs] make background curve-fuse metric correct	#2391
[curvebs] optimize curvebs rapid leader schedule	#2388	@JadeFlute0127
[curvebs] Add Tracing Feature for Curve	#2229	@UniverseParticle
[ut]ut.sh run in build-debian9	#2181
[curvefs] UmountFs will cause deadlock	#2308	@Xinlong-Chen
[curvefs] Async read need	#2070	@Ziy1-Tan	#2421	Done

4、Perfection of Curveadm (Languages: Go), memtor: @Wine93

Func	Issue	Assigne	PR	Progress
smarter core_pattern	opencurve/curveadm#178
incremental formatting	opencurve/curveadm#189
sharing database	opencurve/curveadm#206
service log	opencurve/curveadm#197	@fengshunli	opencurve/curveadm#230
map prompt	opencurve/curveadm#177	@mfordjody	opencurve/curveadm#222
replica	opencurve/curveadm#146
support deploy minio-s3-gateway	opencurve/curveadm#218

see also: curveadm develop activities issue

[zhanghuidinah]

Developer Activities Registration Steps:

• Step 1: Select the issue you want to participate in and comment (up to three contestants may choose the same issue, but only one will be merged; the first merged PR wins)

• Step 2: Note [Issue ID + GitHub ID] and add the community assistant
  

• Step 3: The community assistant will invite you to the Developer Activities Group, where online meetings will be held occasionally (as needed) to answer questions and provide assistance.

• Step 4: Submit the PR for the corresponding issue before June 3rd.

开发者活动参赛流程

• 第一步：选中想参与 issue 并 comment (同一个issue最多允许有三个参赛者选择，但最终只有一个合入；公平竞争，PR 先合入者先得～)

• 第二步：备注【Issue ID + GitHub ID】添加社区小助手
  

• 第三步：社区小助手邀请至开发者活动群，群中会不定期(按需)线上会议，为大家答疑解惑。

• 第四步：在6月3日之前提交对应 issue 的 PR；

[caoxianfei1]

Close it because Q2 developer activitiy finished.