]> git.proxmox.com Git - ceph.git/blob - ceph/doc/governance.rst
update sources to ceph Nautilus 14.2.1
[ceph.git] / ceph / doc / governance.rst
1 .. _governance:
2
3 ============
4 Governance
5 ============
6
7 The Ceph open source community is guided by a few different groups.
8
9 Project Leader
10 --------------
11
12 The Ceph project is currently led by Sage Weil <sage@redhat.com>. The
13 project leader is responsible for guiding the overall direction of the
14 project and ensuring that the developer and user communities are
15 healthy.
16
17
18 Committers
19 ----------
20
21 Committers are project contributors who have write access to the central
22 Ceph code repositories, currently hosted on GitHub. This group of developers
23 is collectively empowered to make changes to the Ceph source code.
24
25 Generally speaking, no individual should make a change in isolation:
26 all code contributions go through a collaborative review process (and
27 undergo testing) before being merged. The specifics of this process
28 are dynamic and evolving over time.
29
30 New committers are added to the project (or committers removed from
31 the project) at the discretion of the Ceph Leadership Team (below).
32 The criteria for becoming a contributor include a consistent level of
33 quality and engagement in the project over time.
34
35
36 Ceph Leadership Team
37 --------------------
38
39 The Ceph Leadership Team (CLT) is a collection of component leads and
40 other core developers who collectively make technical decisions for
41 the project. These decisions are generally made by consensus,
42 although voting may be used if necessary.
43
44 The CLT meets weekly via video chat to discuss any pending issues or
45 decisions. Minutes for the CLT meetings are published at
46 `https://pad.ceph.com/p/clt-weekly-minutes <https://pad.ceph.com/p/clt-weekly-minutes>`_.
47
48 Committers are added to or removed from the CLT at the discretion of
49 the CLT itself.
50
51 Current CLT members are:
52
53 * Ahbishek Lekshmanan <abhishek@suse.com>
54 * Alfredo Deza <adeza@redhat.com>
55 * Gregory Farnum <gfarnum@redhat.com>
56 * Haomai Wang <haomai@xsky.com>
57 * Jason Dillaman <dillaman@redhat.com>
58 * Josh Durgin <jdurgin@redhat.com>
59 * Joao Eduardo Luis <joao@suse.de>
60 * Ken Dreyer <kdreyer@redhat.com>
61 * Lenz Grimmer <lgrimmer@suse.com>
62 * Matt Benjamin <mbenjami@redhat.com>
63 * Myoungwon Oh <omwmw@sk.com>
64 * Neha Ojha <nojha@redhat.com>
65 * Sage Weil <sage@redhat.com>
66 * Sebastian Wagner <swagner@suse.com>
67 * Xie Xingguo <xie.xingguo@zte.com.cn>
68 * Yehuda Sadeh <yehuda@redhat.com>
69 * Zack Cerza <zcerza@redhat.com>
70
71 Component Leads
72 ---------------
73
74 Each major subcomponent of the Ceph project has a lead engineer who is
75 responsible for guiding and coordinating development. The leads are
76 nominated or appointed at the discretion of the project leader or the
77 CLT. Leads responsibilities include:
78
79 * guiding the (usually) daily "stand-up" coordination calls over video chat
80 * building the development roadmap for each release cycle
81 * coordinating development activity between contributors
82 * ensuring that contributions are reviewed
83 * ensuring that different proposed changes do not conflict
84 * ensuring that testing remains robust (new features include tests, changes do not break tests, etc.)
85
86 All component leads are included on the CLT. They are expected to
87 report progress and status updates to the rest of the leadership team
88 and to help facilitate any cross-component coordination of
89 development.
90
91 The Ceph Foundation
92 -------------------
93
94 The Ceph Foundation is organized as a directed fund under the Linux
95 Foundation and is tasked with supporting the Ceph project community
96 and ecosystem. It has no direct control over the technical direction
97 of the Ceph open source project beyond offering feedback and input
98 into the collaborative development process.
99
100 For more information, see `https://ceph.com/foundation
101 <https://ceph.com/foundation>`_.
102