On Tue, Jun 20, 2017 at 9:39 AM Emilian Bold <[email protected]> wrote:
> I do. The previous API Review had some logic to it. I don't believe we > can do without it entirely. > Or at all! I agree with much of what you suggest, but I'm interested to turn that around - why do you believe things need to change now / what aspects are not going to meet Apache compliance? My point was that I don't see the point in changing processes that have worked for the project for years right now, unless it's something where our hand is forced. Surely better to establish a regular review of processes (quarterly, post-releases, ?) and then evolve things where need be? IMO this is the wrong time to be changing too much. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
