rabbah commented on a change in pull request #4818: Define processes for 
enhancement proposals
URL: https://github.com/apache/openwhisk/pull/4818#discussion_r378933788

 File path: proposals/POEM-1-proposal-for-openwhisk-enhancements.md
 @@ -0,0 +1,65 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#     http://www.apache.org/licenses/LICENSE-2.0
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# See the License for the specific language governing permissions and
+# limitations under the License.
+# Title
+Process for introducing an OpenWhisk Enhancement (POEM)
+## Status
+* Current state: Draft
+* Author: @style95
+## Summary
+Introduce a process for suggesting and implementing a substantive OpenWhisk 
Enhancement (POEM).
+A developer or group of developers working together to propose and implement a 
major new feature or functionality, a new subsystem, or a breaking change 
should follow the process described herein and open a proposal for 
consideration under this directory.
+## Motivation
+As the project grows, more and more issues are getting complex and require 
multiple parties and an extended period of time to develop them.
+We can incubate, manage, and elaborate new ideas in OpenWhisk with a standard 
way and a well-tracked artifact.
+It would enhance the discoverability of proposals and help community members 
to involve in the project better.
+## Proposed changes
+### Procedures
+1. Create a pull request to describe your proposal with [this 
template](./POEM-N-template.md). The initial state of a proposal should be 
+2. [Create a corresponding issue]((/issues/new?template=proposal.md)) to 
propose a new change based on [this 
template](../github/ISSUE_TEMPLATE/proposal.md). It is mainly used to track 
discussion history.
+3. Discuss the proposals with any channels(issue comments, mailing list, 
Slack, etc) to form a consensus and update your proposal based on comments as 
much as needed.
+4. When members form a rough consensus for the proposal. The proposal owner 
can request a vote via the dev mailing list.
+5. The voting process follows the [Apache Voting 
guideline](https://www.apache.org/foundation/voting.html). The PR can be merged 
with the _"In-progress"_ state if the voting is successfully closed without any 
+6. The implementation begins as the proposal is filed into the repo and any 
volunteer can join the implementation ideally.
+7. If the proposal is not accepted or no consensus is formed, the PR is merged 
with the state, _"Abandoned"_.
+8. When implementation is included in the master branch, it is supposed to 
update the state of the proposal to _"Completed"_ as well. A corresponding 
issue is closed at this point.
+### Note
+* Committers and PMCs are supposed to label issues with an appropriate label 
to track its status.
+* There are 4 labels(`draft`, `in-progress`, `completed`, and `abandoned`) to 
specify the state of a proposal and one special label(`proposal`) to 
differentiate proposals from other issues.
+### Proposal Lifecycle
+A proposal is supposed to be in one of the following states:
 Review comment:
   A proposal may be in one of the following states:

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to