Foundation » History » Version 1
Jessica Mack, 05/25/2015 11:30 PM
1 | 1 | Jessica Mack | h1. Foundation |
---|---|---|---|
2 | |||
3 | _This is a brainstorming document and is subject to the outcome of the Red Hat acquisition of Inktank (and the Ceph IP). There are some very good arguments to be made for single-vendor Open Source projects, and those discussions have yet to occur as a part of the merger._ |
||
4 | |||
5 | Housing the Ceph project within a Foundation setting would ensure that the community is empowered to make good technical decisions and coordinate efforts across the industry. Below is a rough outline of what the goals and responsibilities of a Ceph Foundation might look like. |
||
6 | |||
7 | h3. Responsibilities: |
||
8 | |||
9 | * Project Governance |
||
10 | * Development process and release management |
||
11 | * Developer, user, and ecosystem community management |
||
12 | * Centralized clearinghouse for engineering work |
||
13 | * Brand management (PR, marketing, trademark) |
||
14 | * Event management (Ceph days, CDS, meetups, etc) |
||
15 | * Legal affairs |
||
16 | |||
17 | h3. Protecting |
||
18 | |||
19 | * The Ceph software by ensuring it remains freely available by facilitating the open development process |
||
20 | * The trademark |
||
21 | * The core values of the Ceph community, such as: |
||
22 | * Respecting and appreciating the individuals and organizations who contribute in various ways, including testing, documenting, translating, integrating, extending, educating, financing, training, supporting, facilitating, evangelizing, designing, and art making. |
||
23 | * Respecting the meritocracy which guides decision making. |
||
24 | * Encouraging economic opportunity in the Ceph ecosystem. |
||
25 | |||
26 | h3. Empowering |
||
27 | |||
28 | * Developers to write great code without overly painful process or tools in a way that takes care of the legal issues |
||
29 | * Developers by training them to become better Free Software contributors |
||
30 | * Developers by providing access to a set of reference platforms, including for large-scale testing |
||
31 | * Users to have access to great software and provide feedback and input on the direction |
||
32 | * Community members of all sorts to organize events, information, discussions and other activities and resources |
||
33 | * Companies to build a powerful and profitable ecosystem and marketplace around the software that creates new business opportunities and feeds the long-term health of Ceph |
||
34 | * Users, by educating them on the best uses for the Ceph software |
||
35 | |||
36 | h3. Promoting |
||
37 | |||
38 | * The software produced |
||
39 | * The developers producing it |
||
40 | * The users using it |
||
41 | * The marketplace of businesses built with or around the software |
||
42 | |||
43 | |||
44 | If there was a Ceph Foundation, it should: |
||
45 | * Provide resources for developers |
||
46 | ** Teuthology instances |
||
47 | ** Package build farms |
||
48 | ** Shared hardware test lab |
||
49 | *** for running teuthology QA |
||
50 | *** for vendors to contirube hardware for testing and eval |
||
51 | ** ... |
||
52 | |||
53 | * Organize Ceph Developer Summits |
||
54 | ** Define the roadmap |
||
55 | ** Discuss feature implementation details |
||
56 | ** ... |
||
57 | |||
58 | * Decide the governance |
||
59 | ** Development workflow (reviews, merge rights etc.) |
||
60 | ** Release cycle |
||
61 | ** What is part of Ceph what is not |
||
62 | ** Own the Ceph trademark and thus logos |
||
63 | ** Host the Ceph website and repository |
||
64 | ** ... |