This is an automated email from the ASF dual-hosted git repository.

style95 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk.git


The following commit(s) were added to refs/heads/master by this push:
     new dab68ec  Fix broken links. (#4832)
dab68ec is described below

commit dab68ece3e24a426a844ccdb992c176b9d06b8fa
Author: Dominic Kim <[email protected]>
AuthorDate: Wed Feb 26 09:42:20 2020 +0900

    Fix broken links. (#4832)
---
 proposals/POEM-1-proposal-for-openwhisk-enhancements.md | 2 +-
 proposals/README.md                                     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/POEM-1-proposal-for-openwhisk-enhancements.md 
b/proposals/POEM-1-proposal-for-openwhisk-enhancements.md
index 7cdcf00..cfed8c3 100644
--- a/proposals/POEM-1-proposal-for-openwhisk-enhancements.md
+++ b/proposals/POEM-1-proposal-for-openwhisk-enhancements.md
@@ -39,7 +39,7 @@ The goals are to enhance the discoverability of proposals, 
and to help community
 
 ### 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 
_"Draft"_.
-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.
+2. [Create a corresponding 
issue](https://github.com/apache/openwhisk/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 using to form a consensus and update your proposal 
based on comments as needed. It is important to be inclusive, and to notify the 
OpenWhisk community of meaningful changes using the Apache [`dev` 
list](https://openwhisk.apache.org/community.html) for this project. Other 
forms of communication such as Slack are OK but any meaningful results should 
be documented in issues and the `dev` list.
 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 
veto.
diff --git a/proposals/README.md b/proposals/README.md
index 0c3b57a..b633d8d 100644
--- a/proposals/README.md
+++ b/proposals/README.md
@@ -26,7 +26,7 @@ You can find the full details in 
[POEM-1](./POEM-1-proposal-for-openwhisk-enhanc
 
 ## Quickstart to propose a new change.
 1. Copy the [POEM template](./POEM-N-template.md) and open a pull request.
-2. [Create a corresponding issue](/issues/new?template=proposal.md) with the 
prefix, `[Proposal]` in the title.
+2. [Create a corresponding 
issue](https://github.com/apache/openwhisk/issues/new?template=proposal.md) 
with the prefix, `[Proposal]` in the title.
 3. Follow the process outlined in the 
[POEM-1](./POEM-1-proposal-for-openwhisk-enhancements.md).
 
 ## When should I open a proposal?

Reply via email to