+1 for keeping the policy in writing. Are we looking at the Traffic Server's API policy as a starting point for discussion?
On Tue, Mar 13, 2018 at 10:12 AM, Greg Mann <g...@mesosphere.io> wrote: > Hi all, > As BenM mentioned in a recent email, we discussed our process for review of > API changes in the recent API working group meeting [1]. James Peach was > also kind enough to share with me Apache Traffic Server's API review > policy, which they have formalized [2]. > > I like the idea of putting our review policy in writing, as this increases > transparency and helps to communicate the policy to new contributors. If > others in the project are amenable to this idea, I could propose a draft > policy and present it to the mailing list for review. > > What do folks think about this? > > Cheers, > Greg > > [1] > https://docs.google.com/document/d/1JrF7pA6gcBZ6iyeP5YgDG62ifn0cZ > IBWw1f_Ler6fLM/edit > [2] https://cwiki.apache.org/confluence/display/TS/API+Review+Process > -- Cheers, Zhitao Li
