├── funding-request └── ceph-foundation-funding-request-template.md └── README.md /funding-request/ceph-foundation-funding-request-template.md: -------------------------------------------------------------------------------- 1 | # Ceph Foundation Funding Request Form 2 | 3 | Thank you for your interest in securing funding from the Ceph Foundation. To ensure that we evaluate your request appropriately, please fill out the details below and email it to governing-board@lists.cephfoundation.org 4 | 5 | ## Applicant Information 6 | 7 | 1. **Full Name**: *[Insert Name]* 8 | 2. **Email Address**: *[Insert Email]* 9 | 3. **Organization** (if applicable): *[Insert Name]* 10 | 11 | ## Project Information 12 | 13 | 4. **Project Name**: *[Insert Project Name]* 14 | 5. **Brief Description of the Project**: 15 | *[Provide a brief summary of the project and its goals]* 16 | 6. **How does this project benefit the Ceph community/project?** 17 | *[Explain the impact and significance for the Ceph community, including any long-term benefits or contributions to the ecosystem]* 18 | 7. **Project Start and End Dates**: 19 | **Start Date**: *[Insert Date]* 20 | **End Date**: *[Insert Date]* 21 | 8. **Total Funding Requested**: 22 | *[Insert amount in USD]* 23 | 9. **Budget Breakdown**: 24 | *[Provide a detailed breakdown of how the requested funds will be used, including key expenses like development, events, materials, etc.]* 25 | 10. **Is the full funding amount needed all at once, or can it be phased out over time?** 26 | - Full funding required all at once 27 | - Phased funding (please provide details below) 28 | 11. **If phased, please describe the funding phases and the milestones associated with each**: 29 | *[Provide details of how the funding can be divided, including phases and expected outcomes per phase.]* 30 | 12. **Is this a one-time cost or a recurring cost?** 31 | - One-time cost 32 | - Recurring cost (please provide details below) 33 | 13. **If recurring, please specify the frequency and duration of the recurring costs** (e.g. monthly, annually, etc.): 34 | *[Provide details about how often the costs will recur and any expected changes overtime.]* 35 | 36 | ## Project Impact and Alignment 37 | 38 | 13. **How does this project align with the Ceph Foundation’s mission and values?** 39 | *[Describe how your project supports the vision, goals, or initiatives of the Ceph Foundation, such as promoting open-source development, community engagement, or advancing Ceph technology.]* 40 | 14. **What measurable outcomes do you expect from this project?** 41 | *[Outline what success looks like for this project and how outcomes will be measured. This could include things like community growth, code contributions, new features, etc.]* 42 | 15. **How will the progress of this project be shared with the Ceph community, and how will its impact be tracked?** 43 | *[Explain how the project’s progress will be shared (e.g., through blogs, presentations, reports) and describe the methods you will use to track its impact, such as metrics, feedback loops, or specific milestones.]* 44 | 45 | ## Additional Information 46 | 47 | 16. **Any other information you would like the Ceph Foundation to consider when evaluating your funding request?** 48 | *[Provide any additional context or details you think are important for the decision-making process.]* 49 | 50 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Repository Template and Usage Guide 2 | 3 | ## Summary 4 | 5 | This repository is designed to serve as a template for all Ceph committees. 6 | 7 | ## Repository Naming Convention 8 | 9 | To maintain a clear and organized naming system, repositories should follow this convention: 10 | 11 | {topic}-committee 12 | 13 | For example: 14 | * outreach-committee 15 | * hardware-committee 16 | * governance-committee 17 | 18 | This naming convention helps identify the purpose and scope of the repository at a glance. 19 | 20 | ## Required Contents 21 | 22 | Every committee repository must include the following files: 23 | 24 | ### 1. README.md 25 | 26 | The README.md file serves as the repository’s introduction and documentation. It should include: 27 | 28 | * The goal of the committee. 29 | * The desired outcomes the committee aims to achieve. 30 | * A list of members involved in the committee, including their roles (e.g., chair). 31 | 32 | An example template can be found at the bottom of this README 33 | 34 | 35 | ### 2. LICENSE 36 | 37 | The LICENSE.md file specifies the repository’s licensing terms. Apache 2.0 is recommended. 38 | 39 | ## Objectives & Key Results (OKRs) 40 | 41 | While not mandatory, we encourage committees to define and commit to achievable OKRs. These OKRs should follow an 42 | annual cycle and be documented in a file named YYYY-OKRs.md. A template is provided below. 43 | 44 | ## Visibility 45 | 46 | We encourage committees to keep their repositories public. However there might be valid reasons for a repository 47 | needing to be private, when in doubt please ask the board. 48 | 49 | ## Issues and Github Projects 50 | 51 | Committees are encouraged to leverage Github issues and projects to organize and track their work. 52 | 53 | 54 | ## README.md Template 55 | 56 | ``` 57 | # [Committee Name] 58 | 59 | ## Goal 60 | 61 | [A committee’s goal should be a clear, actionable, and purpose-driven statement that aligns with 62 | Ceph's broader mission. It should outline the committee’s desired outcome or contribution. For example: 63 | 64 | To ensure the Ceph community can efficiently build, test, and release software by addressing the 65 | bottlenecks in the current build environment, enhancing lab capacity, and diversifying infrastructure 66 | to reduce single points of failure. ] 67 | 68 | ## Desired Outcomes 69 | 70 | [Broadly What the committee aims to achieve. For example: 71 | 72 | 1. Increased Build Capacity 73 | 2. Diversified Infrastructure 74 | 3. Optimized Resource Utilization 75 | ] 76 | 77 | ## Committee Members 78 | 79 | [A list of who is on the committee and their roles if applicable] 80 | 81 | * [First Name, Last Name (@githubid) - Role] 82 | 83 | ``` 84 | 85 | ## YYYY-OKRs.md Template 86 | 87 | ``` 88 | OKR Template 89 | This template provides a structured way to outline Objectives and Key Results (OKRs) broken down by quarters. 90 | 91 | ## Q1: [Year] 92 | 93 | ### Objective 1: [State the high-level goal you want to achieve this quarter.] 94 | 95 | ### Key Results: 96 | 97 | [KR 1: Specific measurable result tied to the objective.] 98 | [KR 2: Specific measurable result tied to the objective.] 99 | [KR 3: Specific measurable result tied to the objective.] 100 | 101 | ``` 102 | --------------------------------------------------------------------------------