mirror of
https://github.com/ceph/ceph
synced 2025-02-19 17:08:05 +00:00
doc/governance: revert d7c144c0d7
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 <zac.dover@proton.me>
This commit is contained in:
parent
d7c144c0d7
commit
0cb2636f1a
@ -21,57 +21,15 @@ Bodies
|
||||
Ceph Executive Council
|
||||
======================
|
||||
|
||||
.. _exec-council-responsibilities:
|
||||
Responsibilities
|
||||
----------------
|
||||
|
||||
Ceph Executive Council Responsibilities
|
||||
---------------------------------------
|
||||
|
||||
- Spokesperson
|
||||
|
||||
- welcome/keynote for cephalocon
|
||||
|
||||
- maintaining slides and presenting about the project
|
||||
|
||||
- Community focal point (user interaction, conference talks, mailing list,
|
||||
etc)
|
||||
* Arbiter in cases where decisions cannot be reached by consensus
|
||||
* Distribute key responsibilities amongst themselves or others
|
||||
* Point of contact for the project
|
||||
* Representatives for Ceph foundation board meetings
|
||||
* Ensure things get done
|
||||
|
||||
- Community
|
||||
|
||||
- managing community manager
|
||||
|
||||
- LF Program Manager person, Social Media person
|
||||
|
||||
- liase with the ambassadors
|
||||
|
||||
- make sure ceph events happen, successfully: cephalocon, ceph days, cds, user/dev, cdm
|
||||
|
||||
- coordinating with LF
|
||||
|
||||
- creating program committee
|
||||
|
||||
- recordings on youtube
|
||||
|
||||
- getting sponsors for events
|
||||
|
||||
- communications, schedule, venue decisions
|
||||
|
||||
- coordinate blog posts
|
||||
|
||||
|
||||
- Ceph Foundation
|
||||
|
||||
- ensure foundation is healthy: financials, operations
|
||||
|
||||
- represent the CLT on the Board
|
||||
|
||||
- present project status regularly (yearly)
|
||||
|
||||
- collect member ideas / feedback
|
||||
|
||||
- ensure members feel valued
|
||||
|
||||
- guide the members how to support the project (events, testing, marketing, hardware, ...)
|
||||
|
||||
Membership
|
||||
----------
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user