Thank you for the good suggestion. I will try to follow the process and define some procedures for our proposal.
Currently, we are sharing proposals via Confluence(cwiki). IMHO, we may need a new repo to deal with such things only. 2019년 7월 26일 (금) 오전 12:39, Matt Sicker <boa...@gmail.com>님이 작성: > I like this! It would make a great starting point, and we might not > even need to get more advanced any time soon. Good find! > > On Thu, 25 Jul 2019 at 02:00, Bertrand Delacretaz > <bdelacre...@apache.org> wrote: > > > > Hi, > > > > On Thu, Jul 18, 2019 at 8:36 PM Matt Sicker <boa...@gmail.com> wrote: > > > ...This is one of the situations where having some sort of proposal > > > process can help align the various people and technical considerations > > > a bit easier than mailing lists and PRs. There are numerous other > > > communities with similar proposal processes (e.g., SIPs for Scala, > > > KIPs for Kafka, JEPs and JSRs for Java, etc.).... > > > > One lightweight example is https://github.com/apache/cordova-discuss , > > with the process described at [1], basically: > > > > -Create an issue to define the rough shape of a proposal > > -If there's consensus, create a Markdown document with the proposal > > -Refine the proposal with pull requests > > -Set a state on each proposal: draft, implementing, done, canceled etc. > > > > What I like about it is that it captures the history of each proposal > > in a single place, with a minimal process. > > > > -Bertrand > > > > [1] > https://github.com/apache/cordova-discuss/blob/master/proposals/README.md > > > > -- > Matt Sicker <boa...@gmail.com> >
