Ceph User Committee¶
The Ceph user community has grown to a point where we want to meet and exchange our experience.
Not just online during the Ceph Developer Summit or during international conferences such as the
OpenStack summit or the Linux Foundation conferences. But also during loosely organized local meetups.
Part of the user committee mission would be to organize these meetings.
As more Ceph production environments are set up, the user committee could also reach out to interview
the organizations and publish the use cases to inspire others.
The evolution of the Ceph software is currently relying mostly on the ability of Inktank to
take into account the needs of their customers. The user committee could publish the desired future features and roadmap.
It could be things like erasure code or tiering ( which are scheduled for Firefly ) because they have market value in addition to being
generaly useful. It could also be features that have only marginal market value but matter to the general
public such as a fully functional and 100% Free Software Ceph production environment.
- Cloudapt, Mike Dawson <email@example.com>
- Free Software Foundation France,<firstname.lastname@example.org>
- Université de Nantes,<Yann.Dupont@univ-nantes.fr>
- Crédit Mutuel Arkea,<email@example.com>
- Deutsche Telekom AG, Danny Al-Gaaf,<firstname.lastname@example.org>
- Joseph R Gruher <email@example.com>
- Sean Noonan <firstname.lastname@example.org>
- Lincoln Bryant <email@example.com>
- Warren Wang <firstname.lastname@example.org>
- Matt Lehner <email@example.com>
- James Pearce <firstname.lastname@example.org> - London
- ACOnet/VIX - Kurt Bauer <email@example.com>
- Peter Matulis <firstname.lastname@example.org>
- Edward Hope-Morley <email@example.com>
- Andrew Woodward <firstname.lastname@example.org>
- Stephane Neveu <email@example.com>
- Joao Eduardo Luis <firstname.lastname@example.org>
- Haomai Wang <email@example.com>
- Heinlein Support GmbH, Robert Sander <firstname.lastname@example.org>
- christopher liljenstolpe <email@example.com>
- eNovance, Sébastien Han <firstname.lastname@example.org>
- Ubisoft, Christian Lachance <email@example.com>
- Inktank, Mark Nelson <firstname.lastname@example.org>
- Aaron Ten Clay <email@example.com>
- jiangang duan <firstname.lastname@example.org>
- Li Wang <email@example.com>
- Acaleph, Paul Gadi <firstname.lastname@example.org>
- SWITCH, Jens-Christian Fischer, <email@example.com>
- Eric Eastman <firstname.lastname@example.org>
- Faidon Liambotis <email@example.com>
- Arne Wiebalck <firstname.lastname@example.org>
- Dan van der Ster <email@example.com>
- Guillaume Moutier <firstname.lastname@example.org>
- Orange, Ghislain Chevalier <email@example.com>
The idea emerged from a conversation during the OpenStack summit and was discussed on the ceph user mailing list. There has been enough interest to move forward. The mission statement is going to be discussed before the CDS, based on the detailed description below. The CDS session is going to be a kind of light general assembly where interested parties could confirm their involvement to act according to the mission statement.
Detailed Description¶The User Committee is an independant group of Ceph users who elects a board of their peers to represent and defend their interests in accordance to the following mission statement:
- Organize meetups, events, booth, talks... : Meeting in person is a useful way to exchange experience and tips, to discover new ways to use Ceph. The User Committee helps with the logistic. It is also responsible for maintaining a calendar of upcoming events.
- Collect use cases and user stories : A diverse collection of existing use cases is a precious source of inspiration. The User Committe approaches users and conduct interviews. A well articulated user story that describes how Ceph could be used in the future is an effective way for developers to figure out what should be included in the roadmap. The User Committee will organize user stories published in a wiki and sort them according to their popularity.
- Focus on the Free and Open Source ecosystem : Ceph is included in proprietary solutions used by a growing number of companies to run successfull commercial activities. Their ecosystem is not in the scope of the User Committee. The User Committee focus on the Open standards, formats, Free and Open Source software that can be assembled with Ceph and allow users to freely use, modify, distribute and study.
- Maintain Community Infrastructure
- Website : Although some parts of ceph.com are maintained by Ceph developers ( such as http://ceph.com/docs/ ) the User Committee is expected to maintain http://ceph.com/
- Social Media : Determine how the community will interact with twitter/facebook/google+
- Wiki : A complete IA overhaul and data cleanup would be great, but at the very least the Ceph community should help maintain the press page and event info here.
- Aggregate Information : Should we create a "firstname.lastname@example.org" list/alias so that people have an easy way to contribute information to be replicated on social media/website/etc?
- IRC Channel Ops : Right now Ops are Inktank employees and +v are community support volunteers. User committee should help w/ Op to maintain ban list and topic
- Mailing List : Right now Inktank moderates and manages all of the ceph lists. Should the community be involved in helping to moderate
- Organize events :
at least three meetups+ one booth ( Loic )
- Publish use cases : at least one ( Loic )
- Publish user stories : ( ??? )
- Reach consensus on the mission statement ( Loic )
- Recruit active members of the User Committee ( ??? )
- Announce the existence of the User Committee after the CDS ( Loic )
- Organize the first election ( ??? )