Skip to content

Commit 0cb2636

Browse files
committed
doc/governance: revert d7c144c
Revert the commit (manually, by restoring the file by hand to the state it was in prior to d7c144c) to the state that it was in before I added the Executive Council Responsibilities document to governance.rst. This document cannot be edited at will, but must be voted on by the Leadership Team. Signed-off-by: Zac Dover <[email protected]>
1 parent d7c144c commit 0cb2636

File tree

1 file changed

+7
-49
lines changed

1 file changed

+7
-49
lines changed

doc/governance.rst

Lines changed: 7 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -21,57 +21,15 @@ Bodies
2121
Ceph Executive Council
2222
======================
2323

24-
.. _exec-council-responsibilities:
25-
26-
Ceph Executive Council Responsibilities
27-
---------------------------------------
28-
29-
- Spokesperson
30-
31-
- welcome/keynote for cephalocon
32-
33-
- maintaining slides and presenting about the project
24+
Responsibilities
25+
----------------
3426

35-
- Community focal point (user interaction, conference talks, mailing list,
36-
etc)
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
3732

38-
- Community
39-
40-
- managing community manager
41-
42-
- LF Program Manager person, Social Media person
43-
44-
- liase with the ambassadors
45-
46-
- make sure ceph events happen, successfully: cephalocon, ceph days, cds, user/dev, cdm
47-
48-
- coordinating with LF
49-
50-
- creating program committee
51-
52-
- recordings on youtube
53-
54-
- getting sponsors for events
55-
56-
- communications, schedule, venue decisions
57-
58-
- coordinate blog posts
59-
60-
61-
- Ceph Foundation
62-
63-
- ensure foundation is healthy: financials, operations
64-
65-
- represent the CLT on the Board
66-
67-
- present project status regularly (yearly)
68-
69-
- collect member ideas / feedback
70-
71-
- ensure members feel valued
72-
73-
- guide the members how to support the project (events, testing, marketing, hardware, ...)
74-
7533
Membership
7634
----------
7735

0 commit comments

Comments
 (0)