6.4 Community Roles and Promotion
Roles and Promotion Mechanism in the Koupleless Community
The roles in the Koupleless community are based on the organization model of Apache open-source projects, with each component (SOFAArk, Arklet, ModuleController, ArkCtl) having its own set of roles. The roles, from lowest to highest, are Contributor, Committer, PMC (Project Management Committee), and Maintainer
| Role | Responsibilities and Permissions | Promotion Mechanism to Higher Roles |
|---|---|---|
| Contributor | All students who provide Issues, answer Issues, operate externally, submit documentation content, or submit any code are Contributors of the corresponding component. Contributors have the permission to submit Issues, reply to Issues, submit content to the official website or documentation, submit code (excluding code review), and publish articles externally. | When a Contributor has merged enough code or documentation content, they can be promoted to Committer by a vote of PMC members of the component. When a Contributor has answered enough Issues or participated in enough operational activities, they can also be voted as a Committer by PMC members. |
| Committer | All students who actively answer Issues, operate externally, submit documentation content, or submit code have the potential to be voted as Committers by PMC members based on their activity level. Committers additionally have responsibilities and permissions for code review, technical proposal review, and Contributor cultivation. | Committers who have shown long-term active involvement or outstanding contributions can be promoted to PMC members of the corresponding component by a vote of PMC members. |
| PMC | Students who make sustained contributions and are particularly active in the corresponding component have the opportunity to be promoted to PMC members. PMC members additionally have responsibilities and permissions for RoadMap formulation, technical proposal and code review, Issue and iteration management, Contributor and Committer cultivation, etc. | |
| Maintainer | Maintainers have additional permissions for key management and repository management. Apart from this, they have equivalent responsibilities and permissions as PMC members in other aspects. |
Community Role Member List
SOFAArk
Maintainer
yuanyuancin
lvjing2
PMC (Project Management Comittee)
glmapper
Committer
zjulbj5
gaosaroma
QilongZhang133
straybirdzls13
caojie0911
Contributor
lylingzhen10
khotyn
FlyAbner (260+ commits, nominated for Comitter?)
alaneuler
sususama
ujjboy
JoeKerouac
Lunarscave
HzjNeverStop
AiWu4Damon
vchangpengfei
HuangDayu
shenchao45
DalianRollingKing
nobodyiam
lanicc
azhsmesos
wuqian0808
KangZhiDong
suntao4019
huangyunbin
jiangyunpeng
michalyao
rootsongjc
Zwl0113
tofdragon
lishiguang4
hionwi
343585776
g-stream
zkitcast
davidzj
zyclove
WindSearcher
lovejin52022
smalljunHw
vchangpengfei
sq1015
xwh1108
yuanChina
blysin
yuwenkai666
hadoop835
gitYupan
thirdparty-core
Estom
jijuanwang
DCLe-DA
linkoog
springcoco
zhaowwwjian
xingcici
ixufeng
jnan806
lizhi12q
kongqq
wangxiaotao00
Due to space limitations, Contributors who submitted issues before 23 are not listed here. We also thank everyone for their use and consultation of SOFAArk.
Arklet
Maintainer
yuanyuancin
lvjing2
PMC (Project Management Committee)
TomorJM
Committer
None
Contributor
glmapper
Lunarscave
lylingzhen
ModuleController
Maintainer
CodeNoobKing
PMC (Project Management Committee)
None
Committer
None
Contributor
liu-657667
Charlie17Li
lylingzhen
Arkctl
Maintainer
yuanyuancin
lvjing2
PMC (Project Management Committee)
None
Committer
None
Contributor
None
Feedback
Was this page helpful?
Welcome propose feedback to community!
Welcome propose feedback to community, or improve this document directly.。