On Sun, Oct 9, 2016 at 5:19 PM Cody Koeninger <c...@koeninger.org> wrote:
> Regarding name, if the SIP overlap is a concern, we can pick a different > name. > > My tongue in cheek suggestion would be > > Spark Lightweight Improvement process (SPARKLI) > If others share my minor concern about the SIP name, I propose Spark Enhancement Proposal (SEP), taking inspiration from the Python Enhancement Proposal name. So if we're going to number proposals like other projects do, they'd be numbered SEP-1, SEP-2, etc. This avoids the naming conflict with Scala SIPs. Another way to avoid a conflict is to stick with "Spark Improvement Proposal" but use SPIP as the acronym. So SPIP-1, SPIP-2, etc. Anyway, it's not a big deal. I just wanted to raise this point. Nick
