Skip to content

Latest commit

 

History

History
33 lines (25 loc) · 2.86 KB

proposal_process.md

File metadata and controls

33 lines (25 loc) · 2.86 KB

Zowe Sub-Project Proposal Process

This document is based on the CNCF Project Proposal Process v1.1.

Introduction

This governance policy sets forth the proposal process for sub-projects to be accepted into Zowe. The process is the same for both existing projects which seek to move into Zowe, and new projects to be formed within Zowe. Zowe Leadership Committee (ZLC) will review all proposals in a timely manner.

Sub-Project Proposal Requirements

Projects must be proposed via a Zowe Leadership Committee (ZLC) issue to https://github.com/zowe/zlc/issues with the "enhancement" label. Project proposals submitted to the ZLC must provide the following information to the best of your ability:

  • Name of project (must be unique within Zowe)
  • Project description (what it does, why it is valuable, origin and history)
  • Statement on alignment with Zowe mission
  • Sponsor from ZLC (sponsor helps mentor projects)
  • License and contribution guidelines (Zowe project requires code contributions to Zowe are to be made under the Eclipse Public License 2.0 (EPL-2.0) and all non-code contributions are to be made under the Creative Commons Attribution 4.0 International license (CC-BY-4.0) unless otherwise approved by the Open Mainframe Project Governing Board, having each committer agree to the DCO
  • Review the Zowe License and Copyright Guidence
  • Source control (GitHub by default)
  • External dependencies (including licenses)
  • Initial committers (how long working on project)
  • Infrastructure requests (CI / OMP Cluster)
  • Communication channels (Slack, irc, mailing lists)
  • Issue tracker (GitHub by default)
  • Prefered maturity level (see Zowe Graduation Criteria below)

Project Acceptance Process

  • Projects are required to schedule and present their proposal at a ZLC meeting. You can check the meeting schedules in the [Zowe Development Calendar].(https://lists.openmainframeproject.org/g/zowe-dev/calendar)
  • Projects get accepted via a 2/3 supermajority vote of the ZLC.
  • All projects must adopt the OMP Code of Conduct.
  • All projects agree to transfer any relevant trademarks to ZLC and to assist in filing for any relevant unregistered ones. This assignment will be reversed if the project does not remain in the ZLC, as described below. Note that no patent or copyright assignment is necessary because the Eclipse Public License 2.0 (EPL-2.0) provides sufficient protections for other developers and users.
  • All projects start at the Incubation stage by default unless the ZLC approves otherwise.