Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

I incorporated the feedbacks here and updated the SPIP page: https://github.com/apache/spark-website/pull/156 The new version is live now: https://spark.apache.org/improvement-proposals.html On Fri, Aug 31, 2018 at 4:35 PM Ryan Blue wrote: > +1 > > I think this is a great suggestion. I agree

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

+1 I think this is a great suggestion. I agree a bit with Sean, but I think it is really about mapping these questions into some of the existing structure. These are a great way to think about projects, but they're general and it would help to rephrase them for a software project, like Matei's

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

+1 One could argue that the litany of the questions are really a double-click on the essence: why, what, how. The three interrogatives ought to be the essence and distillation of any proposal or technical exposition. Cheers Jules Sent from my iPhone Pardon the dumb thumb typos :) > On Aug

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

I like this as well. Regarding “cost”, I think the equivalent concept for us is impact on the rest of the project (say maintenance cost down the line or whatever). This could be captured in the “risks” too, but it’s a slightly different concept. We should probably just clarify what we mean with

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

+1 to Sean's comment On Fri, Aug 31, 2018 at 2:48 PM, Reynold Xin wrote: > Yup all good points. One way I've done it in the past is to have an appendix > section for design sketch, as an expansion to the question "- What is new in > your approach and why do you think it will be successful?" > >

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

Yup all good points. One way I've done it in the past is to have an appendix section for design sketch, as an expansion to the question "- What is new in your approach and why do you think it will be successful?" On Fri, Aug 31, 2018 at 12:47 PM Marcelo Vanzin wrote: > I like the questions

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

I like the questions (aside maybe from the cost one which perhaps does not matter much here), especially since they encourage explaining things in a more plain language than generally used by specs. But I don't think we can ignore design aspects; it's been my observation that a good portion of

Re: [discuss] replacing SPIP template with Heilmeier's Catechism?

Looks good. From the existing template at https://spark.apache.org/improvement-proposals.html I might keep points about design sketch, API, and non goals. And we don't need a cost section. On Fri, Aug 31, 2018, 1:23 PM Reynold Xin wrote: > I helped craft the current SPIP template >

[discuss] replacing SPIP template with Heilmeier's Catechism?

I helped craft the current SPIP template last year. I was recently (re-)introduced to the Heilmeier Catechism, a set of questions DARPA developed to evaluate proposals. The set of questions are: - What are you trying to do? Articulate your