A requirement for Apache Top-Level projects. For more information see "Preparing a Charter" topic as part of the "Guide to Successful Graduation" found here:
Template: https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt
Example charters:
Harmony (see section E. Establish the Apache Harmony project in the October 2006 Board minutes)
OFBiz (see section B. Establish Apache Open for Business Project in the December 2006 Board minutes)
Cayenne (see section C. Establish Apache Cayenne Project in the December 2006 Board minutes)
It appears (but needs to be verified) that once Resolution is drafted (at that stage of grad. process) it can be submitted (along with the name of the chair nominee) from our project Whimsey page here (near bottom):
However, the official page indicates an email to the board is needed (following IPMC VOTE):
- ... the resolution should be submitted at least 72 hours before that meeting. A calendar for meetings is available. Business for the Board should be submitted by a post to the board mailing list. Posting from an Apache address is recommended. Mixing public and private lists on a post is not recommended.
Be aware that our Whimsey page has the following WARNINGs that I am not sure how to address (since we have releases, and ASF licenses etc.)
Licensing
- No Software Grant and No IP Clearance Filed
- No Release Yet/Missing ASF Copyright Headers on Source Code
- No Release Yet/Binary has licensing issues
Proposed Charter for the Apache OpenWhisk project:
The mission of Apache OpenWhisk is to provide a complete Serverless, or Function-as-a-Service, platform along with an ecosystem of curated functional packages, client SDKs and integration tooling.
For reference and from Incubator proposal (see https://wiki.apache.org/incubator/OpenWhiskProposal):
Background
The OpenWhisk project offers a truly open, highly scalable, performant distributed Serverless platform leveraging other open technologies along with a robust programming model, catalog of service and event provider integrations and developer tooling. Specifically, every architectural component service of the OpenWhisk platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API Gateway, etc.) all is designed to be run and scaled as a Docker container. In addition, OpenWhisk uniquely leverages aspects of Docker engine to manage, load balance and scale supported OpenWhisk runtime environments (e.g., JavaScript, Python, Swift, Java, etc.), that run Serverless functional code within Invoker compute instances, using Docker containers.
Initial Goals
OpenWhisk is an open source community project which seeks to adopt the Apache way through the course of the incubator process and foster collaborative development in the Serverless space.
Currently, the OpenWhisk project's source repository is in GitHub using its associated project tooling, but we believe the open Apache processes, democratic project governance, along with its rich developer community and natural integrations with existing projects provide the ideal fit for the technology to grow.
Serverless will only reach its full potential and avoid fragmentation if it is grown in an environment that Apache can offer.
Proposed Resolution for the Apache OpenWhisk project for the ASF Board:
X. Establish the Apache OpenWhisk Project
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the public, related to ${DESCRIPTION-AND-SCOPE}.
[ draft ${DESCRIPTION-AND-SCOPE} text here ].
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache OpenWhisk Project",
be and hereby is established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache OpenWhisk Project be and hereby is responsible for the creation and maintenance of software
related to ${DESCRIPTION-AND-SCOPE};
[ draft ${DESCRIPTION-AND-SCOPE} reference text here ];
and be it further
RESOLVED, that the office of "Vice President, Apache OpenWhisk" be and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair of the Apache OpenWhisk Project, and to have primary responsibility
for management of the projects within the scope of responsibility of the Apache OpenWhisk Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the
Apache OpenWhisk Project:
[ Add list of Initial PMC names here: (NOTE: the PPMC is currently discussing (via a DISCUSS thread in private) the finalized membership to bring forward on the resolution)
TBD
]
NOW, THEREFORE, BE IT FURTHER RESOLVED, that
[ Name of VP/Chair nominee ] (NOTE: Need to discuss/nominate on PPMC mailing list to bring forward on the resolution)
be appointed to the office of Vice President, Apache OpenWhisk, to serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache OpenWhisk PMC be and hereby is tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the Apache OpenWhisk Project; and be it further
RESOLVED, that the Apache OpenWhisk Project be and hereby is tasked with the migration and rationalization of the Apache
Incubator OpenWhisk podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenWhisk podling encumbered upon the Apache Incubator
Project are hereafter discharged.