projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| 11fdf7f2 TL |
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 | ||
| 9f95a23c TL |
36 | .. _clt: |
| 37 | ||
| 11fdf7f2 TL |
38 | Ceph Leadership Team |
| 39 | -------------------- | |
| 40 | ||
| 41 | The Ceph Leadership Team (CLT) is a collection of component leads and | |
| 42 | other core developers who collectively make technical decisions for | |
| 43 | the project. These decisions are generally made by consensus, | |
| 44 | although voting may be used if necessary. | |
| 45 | ||
| 46 | The CLT meets weekly via video chat to discuss any pending issues or | |
| 47 | decisions. Minutes for the CLT meetings are published at | |
| 48 | `https://pad.ceph.com/p/clt-weekly-minutes <https://pad.ceph.com/p/clt-weekly-minutes>`_. | |
| 49 | ||
| 50 | Committers are added to or removed from the CLT at the discretion of | |
| 51 | the CLT itself. | |
| 52 | ||
| 53 | Current CLT members are: | |
| 54 | ||
| 9f95a23c | 55 | * Casey Bodley <cbodley@redhat.com> |
| 20effc67 TL |
56 | * Dan van der Ster <daniel.vanderster@cern.ch> |
| 57 | * David Galloway <dgallowa@redhat.com> | |
| 58 | * David Orman <ormandj@iland.com> | |
| f67539c2 | 59 | * Ernesto Puerta <epuerta@redhat.com> |
| 11fdf7f2 TL |
60 | * Gregory Farnum <gfarnum@redhat.com> |
| 61 | * Haomai Wang <haomai@xsky.com> | |
| 20effc67 TL |
62 | * Ilya Dryomov <idryomov@redhat.com> |
| 63 | * Igor Fedotov <igor.fedotov@croit.io> | |
| 64 | * Jeff Layton <jlayton@redhat.com> | |
| 11fdf7f2 | 65 | * Josh Durgin <jdurgin@redhat.com> |
| f67539c2 | 66 | * João Eduardo Luis <joao@suse.de> |
| 11fdf7f2 | 67 | * Ken Dreyer <kdreyer@redhat.com> |
| 20effc67 | 68 | * Mark Nelson <mnelson@redhat.com> |
| 11fdf7f2 | 69 | * Matt Benjamin <mbenjami@redhat.com> |
| 20effc67 TL |
70 | * Mike Perez <miperez@redhat.com> |
| 71 | * Myoungwon Oh <myoungwon.oh@samsung.com> | |
| 11fdf7f2 | 72 | * Neha Ojha <nojha@redhat.com> |
| f67539c2 | 73 | * Patrick Donnelly <pdonnell@redhat.com> |
| 11fdf7f2 | 74 | * Sage Weil <sage@redhat.com> |
| 20effc67 TL |
75 | * Sam Just <sjust@redhat.com> |
| 76 | * Sebastian Wagner <sewagner@redhat.com> | |
| 11fdf7f2 TL |
77 | * Xie Xingguo <xie.xingguo@zte.com.cn> |
| 78 | * Yehuda Sadeh <yehuda@redhat.com> | |
| 20effc67 TL |
79 | * Yuri Weinstein <yweinste@redhat.com> |
| 80 | * Zac Dover <zac.dover@gmail.com> | |
| 11fdf7f2 TL |
81 | |
| 82 | Component Leads | |
| 83 | --------------- | |
| 84 | ||
| 85 | Each major subcomponent of the Ceph project has a lead engineer who is | |
| 86 | responsible for guiding and coordinating development. The leads are | |
| 87 | nominated or appointed at the discretion of the project leader or the | |
| 88 | CLT. Leads responsibilities include: | |
| 89 | ||
| 90 | * guiding the (usually) daily "stand-up" coordination calls over video chat | |
| 91 | * building the development roadmap for each release cycle | |
| 92 | * coordinating development activity between contributors | |
| 93 | * ensuring that contributions are reviewed | |
| 94 | * ensuring that different proposed changes do not conflict | |
| 95 | * ensuring that testing remains robust (new features include tests, changes do not break tests, etc.) | |
| 96 | ||
| 97 | All component leads are included on the CLT. They are expected to | |
| 98 | report progress and status updates to the rest of the leadership team | |
| 99 | and to help facilitate any cross-component coordination of | |
| 100 | development. | |
| 101 | ||
| 102 | The Ceph Foundation | |
| 103 | ------------------- | |
| 104 | ||
| 105 | The Ceph Foundation is organized as a directed fund under the Linux | |
| 106 | Foundation and is tasked with supporting the Ceph project community | |
| 107 | and ecosystem. It has no direct control over the technical direction | |
| 108 | of the Ceph open source project beyond offering feedback and input | |
| 109 | into the collaborative development process. | |
| 110 | ||
| 9f95a23c | 111 | For more information, see :ref:`foundation`. |
| 11fdf7f2 | 112 |