From 5a1037d48641b9b11ecb5c3b535a91cfaa2deb2f Mon Sep 17 00:00:00 2001 From: cdetrio Date: Wed, 25 Jan 2017 10:17:44 +0100 Subject: [PATCH 1/2] create ISSUE_TEMPLATE.md --- ISSUE_TEMPLATE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 ISSUE_TEMPLATE.md diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md new file mode 100644 index 0000000000000..46111ce72773d --- /dev/null +++ b/ISSUE_TEMPLATE.md @@ -0,0 +1,11 @@ +ATTENTION! If you would like to submit an EIP and it has already been written as a draft (see the [template](https://github.com/ethereum/EIPs/blob/master/eip-X.md) for an example), please submit it as a [Pull Request](https://github.com/ethereum/EIPs/pulls). + +If you are considering a proposal but you would like to get some feedback on the rough idea before writing a draft, then continue opening an Issue as a thread for discussion. + +Keep in mind the following guidelines from [EIP-1](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.mediawiki): + +> Each EIP must have a champion -- someone who writes the EIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The EIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is EIP-able. Asking in the [EIPs gitter room](https://gitter.im/ethereum/EIPs) or opening an Issue is the best way to go about this. + +> Vetting an idea publicly before going as far as writing a EIP is meant to save the potential author time. Asking the Ethereum community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Ethereum is used. + +> Once the champion has asked the Ethereum community as to whether an idea has any chance of acceptance, a draft EIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft EIP to make properly formatted, of high quality, and to address initial concerns about the proposal. From 986d6d66c2748d1cb63a93f812f78e0b90e4d7a6 Mon Sep 17 00:00:00 2001 From: cdetrio Date: Wed, 25 Jan 2017 16:59:25 +0100 Subject: [PATCH 2/2] update ISSUE_TEMPLATE.md --- ISSUE_TEMPLATE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md index 46111ce72773d..bef04dbc34bac 100644 --- a/ISSUE_TEMPLATE.md +++ b/ISSUE_TEMPLATE.md @@ -1,6 +1,6 @@ ATTENTION! If you would like to submit an EIP and it has already been written as a draft (see the [template](https://github.com/ethereum/EIPs/blob/master/eip-X.md) for an example), please submit it as a [Pull Request](https://github.com/ethereum/EIPs/pulls). -If you are considering a proposal but you would like to get some feedback on the rough idea before writing a draft, then continue opening an Issue as a thread for discussion. +If you are considering a proposal but you would like to get some feedback on the rough idea before writing a draft, then continue opening an Issue as a thread for discussion. Note that the more clearly and completely you state your idea the higher the quality of the feedback you are likely to receive. Keep in mind the following guidelines from [EIP-1](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.mediawiki):