Project Workflow

2015-05-12 Thread Michael Joyce
Hi folks, Since this has been brought up a few times on various tickets I thought now would be a good time to go over our project workflow and make sure it's working for us. A general overview of the workflow that we use is available at [1]. A brief overview is that: - ALL changes are push

Re: Project Workflow

2015-05-12 Thread Mattmann, Chris A (3980)
++ -Original Message- From: Michael Joyce Reply-To: "dev@climate.apache.org" Date: Tuesday, May 12, 2015 at 8:55 AM To: "dev@climate.apache.org" Subject: Project Workflow >Hi folks, > >Since this has b

Re: Project Workflow

2015-05-12 Thread Ramirez, Paul M (398M)
ate: Tuesday, May 12, 2015 at 8:55 AM To: "dev@climate.apache.org<mailto:dev@climate.apache.org>" mailto:dev@climate.apache.org>> Subject: Project Workflow Hi folks, Since this has been brought up a few times on various tickets I thought now would be a good time to go over our p

Re: Project Workflow

2015-05-12 Thread Lee, Kyo (329C-Caltech)
, CA 90089 USA >++ > > > > > > >-Original Message- >From: Michael Joyce >Reply-To: "dev@climate.apache.org" >Date: Tuesday, May 12, 2015 at 8:55 AM >To: "dev@climate.apach

Re: Project Workflow

2015-05-12 Thread Michael Joyce
++++++ > > > > > > > -Original Message- > From: Michael Joyce mailto:jo...@apache.org>> > Reply-To: "dev@climate.apache.org<mailto:dev@climate.apache.org>" < > dev@climate.apache.org&

Re: Project Workflow

2015-05-12 Thread Mattmann, Chris A (3980)
unset.usc.edu/~mattmann/ >> ++ >> Adjunct Associate Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> +

Re: Project Workflow

2015-05-12 Thread Lewis John Mcgibbney
Hi Jimmy, On Tue, May 12, 2015 at 10:39 AM, wrote: > Since this has been brought up a few times on various tickets I thought now > would be a good time to go over our project workflow and make sure it's > working for us. > Excellent idea! > > A general overview of the

Re: Project Workflow

2015-05-12 Thread Lewis John Mcgibbney
Hi Chris, Responses inline On Tue, May 12, 2015 at 10:39 AM, wrote: > > I don’t think we should dictate everything be code reviewed. 72 hours seems pretty permissive to me. I would comment that I see it as a different case where comments are provided and not addressed. I also don't think that

Re: Project Workflow

2015-05-12 Thread Lewis John Mcgibbney
Hi Kyo, On Tue, May 12, 2015 at 3:05 PM, wrote: > > This debate just wastes my time. > ! Why ! > I am not simply talking about the advantages or disadvantages. Advantages or disadvantages of what? The Workflow? > The old one > has serious problems. The old what? The Workflow? It is if t

Re: Project Workflow

2015-05-12 Thread Mattmann, Chris A (3980)
++ -Original Message- From: Michael Joyce Reply-To: "dev@climate.apache.org" Date: Tuesday, May 12, 2015 at 11:49 AM To: "dev@climate.apache.org" Subject: Re: Project Workflow >Pre-email note - 'you' is used here to collectively refer to a nonexistent

Re: Project Workflow

2015-05-12 Thread Mattmann, Chris A (3980)
Lewis, I’m honestly not sure what you are talking about, and to be honest, waiting 72 hours before committing everything is not a project I’d ever want to be on. Like I said - if I care about a review, or want something to be seen by someone, fine, I can choose to ask for it. It shouldn’t be *impo

Re: Project Workflow

2015-05-12 Thread Loikith, Paul C (329C-Caltech)
t;Instrument Software and Science Data Systems Section (398) >NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >Office: 168-519, Mailstop: 168-527 >Email: chris.a.mattm...@nasa.gov >WWW: http://sunset.usc.edu/~mattmann/ >++++++++

Re: Project Workflow

2015-05-12 Thread Lewis John Mcgibbney
Hi Chris, Please see replies inline On Tue, May 12, 2015 at 6:10 PM, wrote: > > I’m honestly not sure what you are talking about, Not even one wee bit ;) maybe some of my replies will bridge the gap between you not being sure about what I am talking about Vs disagreeing with what I am trying t

Re: Project Workflow

2015-05-12 Thread Mattmann, Chris A (3980)
Lewis, -Original Message- From: Lewis John Mcgibbney Reply-To: "dev@climate.apache.org" Date: Tuesday, May 12, 2015 at 8:29 PM To: "dev@climate.apache.org" Subject: Re: Project Workflow >Hi Chris, >Please see replies inline > >On Tue, May 12, 2015

Re: Project Workflow

2015-05-12 Thread Michael Joyce
Thank you for the great responses Lewis. You put into words what I haven't seemed to be able to type out today. Few comments below (it's really mostly just me typing +100 to be honest though) -- Jimmy On Tue, May 12, 2015 at 8:29 PM, Lewis John Mcgibbney < lewis.mcgibb...@gmail.com> wrote:

Re: Project Workflow

2015-05-12 Thread Cameron Goodale
Wow! There sure is a lot of passion and fire in this thread, so let me put on my asbestos small clothes and wade into the pool. Dear Kyo, When you say that this discussion is a waste of your time it makes me sad. Sure sitting here the last 20 minutes reading this thread could be seen as a waste

Re: Project Workflow

2015-05-12 Thread Lewis John Mcgibbney
Hi Chris, I'm aware that I'm not responding to your previous reply exactly but my reaponse is still on this overall thread so that's OK. This thread seems to have, rather drastically turned into a bit of a pissibg match on one hand and borderline argument on the other. Which is uncharacteristic and

Re: Project Workflow

2015-05-12 Thread Michael Joyce
m...@jpl.nasa.gov> wrote: > Lewis, > > -Original Message- > > From: Lewis John Mcgibbney > Reply-To: "dev@climate.apache.org" > Date: Tuesday, May 12, 2015 at 8:29 PM > To: "dev@climate.apache.org" > Subject: Re: Project Workflow > >

Re: Project Workflow

2015-05-12 Thread Lee, Kyo (329C-Caltech)
Hi Mike, Yes, I won¹t hesitate to ask your help. Thank you as always. Hi Cam and everyone, I would like to clarify that the time wasting discussion is not about the project workflow at all. I am sorry, but I have been too busy to read any email thread on the workflow. The discussion in my

Re: Project Workflow

2015-05-13 Thread Lee, Kyo (329C-Caltech)
Dear all, Finally I read all of this thread. Now I am writing to express my sincere apologies for my words and failure to control my anger. I realized that some of my behavior inappropriate and disrespectful. I hope that you will allow me the opportunity to express my apology again in person this

Re: Project Workflow

2015-05-13 Thread Cameron Goodale
Good Morning Kyo, I am sorry for your frustration in this matter, and I appreciate you sticking it out with us. I'll let the git professionals answer the code related stuff and I'll handle the acronyms. CTR - Commit then review ( doing code review after it has been committed) RTC - Review then

Re: Project Workflow

2015-05-13 Thread Mattmann, Chris A (3980)
(329C-Caltech)" Reply-To: "dev@climate.apache.org" Date: Tuesday, May 12, 2015 at 11:32 PM To: "dev@climate.apache.org" Subject: Re: Project Workflow >Hi Mike, > >Yes, I won¹t hesitate to ask your help. Thank you as always. > >Hi Cam and everyone, >

Re: Project Workflow

2015-05-13 Thread Andrew Hart
When talking about project workflow, I think it makes sense to look at it in terms of value. Those of us with a technical background see value in a stable code base, consistent architecture, predictable release cycle, etc. Those of us with a scientific background see value in scientific

Re: Project Workflow

2015-05-13 Thread Lee, Kyo (329C-Caltech)
t; > > > >-Original Message- >From: , "Kyo (329C-Caltech)" >Reply-To: "dev@climate.apache.org" >Date: Tuesday, May 12, 2015 at 11:32 PM >To: "dev@climate.apache.org" >Subject: Re: Project Workflow > >>Hi Mike, >> >>Ye