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):
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 [ draft proposal needed ]
For reference and from Incubator proposal (see https://wiki.apache.org/incubator/OpenWhiskProposal):
Background
Serverless computing is the evolutionary next stage in Cloud computing carrying further the abstraction offered to software developers using Container-based operating system virtualization. The Serverless paradigm enables programmers to just “write” functional code and not worry about having to configure any aspect of a server needed for execution. Such Serverless functions are single purpose and stateless that respond to event-driven data sources and can be scaled on-demand.
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.
OpenWhisk's containerized design tenants not only allows it to be hosted in various IaaS, PaaS Clouds platforms that support Docker containers, but also achieves the high expectation of the Serverless computing experience by masking all aspects of traditional resource specification and configuration from the end user simplifying and accelerating Cloud application development. In order to enable HTTP requests as a source of events, and thus the creation of Serverless microservices that expose REST APIs, OpenWhisk includes an API Gateway that performs tasks like security, request routing, throttling, and logging.
Rationale
Serverless computing is in the very early stages of the technology adoption curve and has great promise in enabling new paradigms in event-driven application development, but current implementation efforts are fractured as most are tied to specific Cloud platforms and services. Having an open implementation of a Serverless platform, such as OpenWhisk, available and governed by an open community like Apache could accelerate growth of this technology, as well as encourage dialog and interoperability.
Having the ASF accept and incubate OpenWhisk would provide a clear signal to developers interested in Serverless and its future that they are welcome to participate and contribute in its development, growth and governance.
In addition, there are numerous projects already at the ASF that would provide a natural fit to the API-centric, event-driven programming model that OpenWhisk sees as integral to a Serverless future. In fact, any project that includes a service that can produce or consume actionable events could become an integration point with OpenWhisk-enabled functions. Apache projects that manage programming languages and (micro) service runtimes could become part of the OpenWhisk set of supported runtime environments for functions. Device and API gateways would provide natural event sources that could utilize OpenWhisk functions to process, store and analyze vast amounts of information immediately unlocking the potential of fast-growing computing fields offered in spaces as IoT, analytics, cognitive, mobile and more.
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 ${PROJECT} Project be and hereby is responsible for the creation and maintenance of software
related to ${DESCRIPTION-AND-SCOPE};
[ draft description and scope 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 Committer names here: (NOTE: initially. I moved all PPMC names here, but would recommend a discussion by PPMC to resolve on a final list)
- Format: <first/last name> <apache email address>
nauerz andreasnauerz Andreas Nauerz
bbrowning Benjamin M. Browning
bwmcadams bwmcadams Brendan McAdams
csantanapr csantanapr Carlos Santana
cziegeler cziegeler Carsten Ziegeler
chetanm chetanmeh Chetan Mehrotra
cbickel cbickel Christian Bickel
dgrove dgrove-oss Dave Grove
lz1982 (*) lzbj David ZL Liu
style95 style95 Dominic Kim
dragos ddragosd Dragos Dascalita Haut
edwardyoon edwardyoon Edward J. Yoon
dubeejw (*) dubee James Dubee
jamesthomas (*) jthomas James Thomas
jeremiaswerner jeremiaswerner Jeremias Werner
mdeuser (*) mdeuser Mark Deuser
markusthoemmes markusthoemmes Markus Thömmes
mrutkowski mrutkows Matt Rutkowski
tardieu tardieu Olivier Tardieu
pcastro paulcastro Paul Castro
perry (*) perryibm Perry S Cheng
psuter Philippe Suter
rabbah rabbah Rodric Rabbah
sjfink sjfink Stephen Fink
slange (*) sven-lange-last Sven Lange-Last
tonyffrench tonyffrench Tony Ffrench
tysonnorris tysonnorris Tyson Norris
houshengbo houshengbo Vincent Hou
daisyguo daisy-ycguo Ying Chung Guo
]
NOW, THEREFORE, BE IT FURTHER RESOLVED, that
[ Name of VP nominee ]
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.