Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Latest commit

 

History

History
12 lines (6 loc) · 1.89 KB

ISSUE_TEMPLATE.md

File metadata and controls

12 lines (6 loc) · 1.89 KB

ATTENTION! If you would like to submit an KIP and it has already been written as a draft (see the template for an example), please submit it as a Pull Request.

If you are considering a proposal but would like to get some feedback on the idea before submitting 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 KIP-1:

Each KIP must have a champion - someone who writes the KIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The KIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is KIP-able. Posting to the the Protocol Discussion forum or opening an Issue is the best way to go about this.

Vetting an idea publicly before going as far as writing a KIP is meant to save the potential author time. Asking the Klaytn 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 Klaytn is used.

Once the champion has asked the Klaytn community as to whether an idea has any chance of acceptance, a draft KIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft KIP to make properly formatted, of high quality, and to address initial concerns about the proposal.