INSTRUCTIONS FOR USE: Make a copy of this template to draft your charter in collaboration with others or privately. The OASIS Project Administrator project-admin@oasis-open.org is available to answer questions and offer suggestions.
If you’d like to participate in this Open Project (OP), please contact join@oasis-open.org. Details on Open Project sponsorship are here.
This is a draft proposal. It has not been submitted to or accepted by OASIS. This charter must be finalized by its proposers and submission requirements must be met before it can be considered for formation as an official OASIS Open Project. Contact the Open Projects Administrator for details on this.
| Open Project Charter | Section description. Column will be removed when the draft is ready. |
|---|---|
| 1. Open Project Name Proposed name and abbreviation> |
Enter your Project's complete name here. Your project name must be unique. Do an online search to ensure there isn't an existing project or product with the same or similar name. Don't include any non-OASIS trademarks or other protected terms. |
| 2. Statement of Purpose Describe the technical and business problem(s) you want to address here. |
Explain why the work is necessary. Identify the specific problems you want to address. Describe your proposed solution in a way that will be clear to someone only moderately versed in the subject. Bring as much foresight as you can to your scope but don't let it constrain the work. This description can be edited as your project evolves. You may want to describe specific deliverables and/or your proposed timeline in this section. |
| 3. Business Benefits Enter a description of your stakeholders and the benefits they will gain here. |
Who will benefit from this work? Who are the key stakeholders? Provide as much detail as you can about the value of your Project to potential participants and to adopters. Ideally, list all the categories of stakeholders (types of organizations, vertical industries, professional titles) and explain how each will benefit. Help potential participants make the case to their management for why they should be part of this work. Convince potential adopters they should monitor if not engage with your Project. |
| 4. Normative Scope Enter a description of what is in and out of scope for your project here. |
Provide detail on the work you intend to do to achieve your stated purpose. Clarify what work will be the focus of the project as well as any work the project will explicitly not undertake. |
| 5.Milestones and Deliverabels Use this section to outline the actions, deliverables, or decisions points needed to achieve the objective(s) |
Explain the initial set of decisions or deliverables you think the project will need to make in order to start working towards the goal. This list does not have to be final and can change as the project progresses. Having an initial roadmap will help the project plan its early work with the goal of seeing progress early in the project. |
| 6. Relationship to Other Projects Enter a list of related projects here. |
How does your Project build on or relate to other open source activities or standards? List all related projects and describe how your approach differs from or complements each one. Don't hesitate to reference other work. Even if your Project is truly groundbreaking, potential participants will want to know where it fits in the current landscape. Use this opportunity to demonstrate your awareness, clarify your differentiators, and attract support from developers involved in related efforts. If you plan to form liaison relationships with other groups, you may note that here too. OASIS staff will use this information to connect your Project with participants experienced in this space. |
| 7. Repositories and Licenses Choose one of these licenses for each repository: - Apache License 2.0 - https://www.apache.org/licenses/LICENSE-2.0 - Eclipse Public License 1.0 - https://www.eclipse.org/legal/epl-v10.html - Eclipse Public License 2.0 - https://www.eclipse.org/legal/epl-2.0/ - 3-Clause BSD License - https://opensource.org/licenses/BSD-3-Clause - Attribution 2.0 Generic (CC BY 2.0) - https://creativecommons.org/licenses/by/2.0/legalcode - Attribution 4.0 International (CC BY 4.0) - https://creativecommons.org/licenses/by/4.0/legalcode - MIT License - https://opensource.org/licenses/MIT - CC-0 - https://creativecommons.org/publicdomain/zero/1.0/legalcode Not sure which licenses to choose? OASIS staff can offer assistance to help you determine what's right for your Project. |
List initial repositor(ies) you would like to set up with the preferred licenses for each. Provide names or descriptions of any initial repositories you expect to use for developing project assets. Specify preferred licenses for submissions and distributions. Each repository listed may have its own license. The licenses offer different patent guarantees, reuse rights, and requirements with which implementers will need to comply. |
| 8. Initial Contributions from Existing Work Identify any existing projects, specifications, or repositories that may be contributed to the project here. |
If you plan to contribute existing specifications, repositories, or documentation to your Project, provide those details - including links - in this section. Any type of prior work can be contributed, such as code, JSON schemas, and UML files. Be sure to note the license under which each contribution was developed. If you do not plan to base your work on any initial contributions, you can note that in this section. |
When you are ready to submit this charter, please notify OASIS. The Open Projects Administrator will ensure it is complete and meets all requirements.
For more information, please see: