So to be clear, if I translate that google doc to markup and submit a PR, you will merge it?
If we're just using "spip" label, that's probably fine, but we still need shared filters for open and closed SPIPs so the page can link to them. I do not believe I have jira permissions to share filters, I just attempted to edit one of mine and do not see an add shares field. On Fri, Mar 10, 2017 at 10:54 AM, Sean Owen <so...@cloudera.com> wrote: > Sure, that seems OK to me. I can merge anything like that. > I think anyone can make a new label in JIRA; I don't know if even the admins > can make a new issue type unfortunately. We may just have to mention a > convention involving title and label or something. > > On Fri, Mar 10, 2017 at 4:52 PM Cody Koeninger <c...@koeninger.org> wrote: >> >> I think it ought to be its own page, linked from the more / community >> menu dropdowns. >> >> We also need the jira tag, and for the page to clearly link to filters >> that show proposed / completed SPIPs >> >> On Fri, Mar 10, 2017 at 3:39 AM, Sean Owen <so...@cloudera.com> wrote: >> > Alrighty, if nobody is objecting, and nobody calls for a VOTE, then, >> > let's >> > say this document is the SPIP 1.0 process. >> > >> > I think the next step is just to translate the text to some suitable >> > location. I suggest adding it to >> > https://github.com/apache/spark-website/blob/asf-site/contributing.md >> > >> > On Thu, Mar 9, 2017 at 4:55 PM Sean Owen <so...@cloudera.com> wrote: >> >> >> >> I think a VOTE is over-thinking it, and is rarely used, but, can't >> >> hurt. >> >> Nah, anyone can call a vote. This really isn't that formal. We just >> >> want to >> >> declare and document consensus. >> >> >> >> I think SPIP is just a remix of existing process anyway, and don't >> >> think >> >> it will actually do much anyway, which is why I am sanguine about the >> >> whole >> >> thing. >> >> >> >> To bring this to a conclusion, I will just put the contents of the doc >> >> in >> >> an email tomorrow for a VOTE. Raise any objections now. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
