]>
Commit | Line | Data |
---|---|---|
1 | .. _governance: | |
2 | ||
3 | ============ | |
4 | Governance | |
5 | ============ | |
6 | ||
7 | The Ceph open source community is guided by a few different groups. | |
8 | ||
9 | Key principles | |
10 | ============== | |
11 | ||
12 | * Decision-making is consensus-driven by those who participate. | |
13 | * Leadership roles are defined primarily by responsibility, not prestige or seniority. | |
14 | * It is normal and healthy for these roles to be passed on to others | |
15 | * Everyone's role is ultimately to serve the users and participation | |
16 | is voluntary. | |
17 | ||
18 | Bodies | |
19 | ------ | |
20 | ||
21 | Ceph Executive Council | |
22 | ====================== | |
23 | ||
24 | Responsibilities | |
25 | ---------------- | |
26 | ||
27 | * Arbiter in cases where decisions cannot be reached by consensus | |
28 | * Distribute key responsibilities amongst themselves or others | |
29 | * Point of contact for the project | |
30 | * Representatives for Ceph foundation board meetings | |
31 | * Ensure things get done | |
32 | ||
33 | Membership | |
34 | ---------- | |
35 | ||
36 | * 3 people | |
37 | * Elected by the steering committee | |
38 | * Candidates self-nominate or are nominated by other members | |
39 | * Discussion of how roles/responsibilities may be delegated | |
40 | * Ranked-choice vote by the steering committee | |
41 | * 2 year terms, with one member being elected in even years, and the | |
42 | other two in odd years | |
43 | * Members may resign at any time, and the steering committee may vote | |
44 | to appoint a replacement for the rest of their term | |
45 | * members must involve >1 employer | |
46 | ||
47 | Current Members | |
48 | ^^^^^^^^^^^^^^^ | |
49 | ||
50 | * Dan van der Ster <daniel.vanderster@cern.ch> | |
51 | * Josh Durgin <jdurgin@redhat.com> | |
52 | * Neha Ojha <nojha@redhat.com> | |
53 | ||
54 | .. _csc: | |
55 | ||
56 | Ceph Steering Committee | |
57 | ======================= | |
58 | ||
59 | Responsibilities | |
60 | ---------------- | |
61 | ||
62 | * Elect executive council | |
63 | * Amend governance model (by majority vote) | |
64 | * Meet regularly to discuss and decide on tactical and strategic projects | |
65 | and improvements | |
66 | ||
67 | Membership | |
68 | ---------- | |
69 | ||
70 | * Developers, users, community members | |
71 | * Voting members can be nominated and added/removed by existing | |
72 | members (2/3 majority) | |
73 | * Anyone may attend steering committee meetings as a non-voting participant | |
74 | * Existing Ceph Leadership Team members are grandfathered in | |
75 | * Membership reflected by an email list and on the Ceph website and | |
76 | docs | |
77 | ||
78 | Current Members | |
79 | ^^^^^^^^^^^^^^^ | |
80 | ||
81 | * Adam King <adking@redhat.com> | |
82 | * Casey Bodley <cbodley@redhat.com> | |
83 | * Dan van der Ster <daniel.vanderster@cern.ch> | |
84 | * David Orman <ormandj@iland.com> | |
85 | * Ernesto Puerta <epuerta@redhat.com> | |
86 | * Gregory Farnum <gfarnum@redhat.com> | |
87 | * Haomai Wang <haomai@xsky.com> | |
88 | * Ilya Dryomov <idryomov@redhat.com> | |
89 | * Igor Fedotov <igor.fedotov@croit.io> | |
90 | * Jeff Layton <jlayton@redhat.com> | |
91 | * Josh Durgin <jdurgin@redhat.com> | |
92 | * João Eduardo Luis <joao@suse.de> | |
93 | * Ken Dreyer <kdreyer@redhat.com> | |
94 | * Mark Nelson <mnelson@redhat.com> | |
95 | * Matt Benjamin <mbenjami@redhat.com> | |
96 | * Mike Perez <miperez@redhat.com> | |
97 | * Myoungwon Oh <myoungwon.oh@samsung.com> | |
98 | * Neha Ojha <nojha@redhat.com> | |
99 | * Patrick Donnelly <pdonnell@redhat.com> | |
100 | * Sam Just <sjust@redhat.com> | |
101 | * Vikhyat Umrao <vikhyat@redhat.com> | |
102 | * Xie Xingguo <xie.xingguo@zte.com.cn> | |
103 | * Yehuda Sadeh <yehuda@redhat.com> | |
104 | * Yingxin Cheng <yingxin.cheng@intel.com> | |
105 | * Yuri Weinstein <yweinste@redhat.com> | |
106 | * Zac Dover <zac.dover@gmail.com> | |
107 | ||
108 | .. _ctl: | |
109 | ||
110 | Component Team Leads | |
111 | ==================== | |
112 | ||
113 | Responsibilities | |
114 | ---------------- | |
115 | ||
116 | * Manage a `component team`_ in Ceph | |
117 | * Ensure PRs are reviewed and merged | |
118 | * Ensure severe bug fixes are backported | |
119 | * Run standups | |
120 | * Bug triage, scrubs | |
121 | * etc. | |
122 | ||
123 | Team leads are selected by the executive council, generally based on | |
124 | the recommendation by team members and outgoing lead. Periodic | |
125 | rotation of lead responsibility among team members is encouraged. | |
126 | ||
127 | The Ceph Foundation | |
128 | ------------------- | |
129 | ||
130 | The Ceph Foundation is organized as a directed fund under the Linux | |
131 | Foundation and is tasked with supporting the Ceph project community | |
132 | and ecosystem. It has no direct control over the technical direction | |
133 | of the Ceph open source project beyond offering feedback and input | |
134 | into the collaborative development process. | |
135 | ||
136 | For more information, see :ref:`foundation`. | |
137 | ||
138 | .. _component team: https://ceph.io/en/community/team/ |