Big +1 If you don't mind a personal anecdote, in fact at work I was recently pointedly asked how the pay is over at the Foundation. (Smile)
On Saturday, October 10, 2015, Patrick Hunt <ph...@apache.org> wrote: > 10x to what Chris said, put much better than I could. > > We all wear multiple hats, can't tell you the number of times I've worn my > Apache hat in the office, in some cases to my own detriment there. If I > weren't associated with the project at Apache that representation would be > missing. So really it cuts both ways. > > Patrick > > > On Sat, Oct 10, 2015 at 7:49 AM, Mattmann, Chris A (3980) < > chris.a.mattm...@jpl.nasa.gov <javascript:;>> wrote: > > > So here’s my elaboration. > > > > The proposal below would have prevented me from ever helping > > projects to the ASF and convincing them that it may be a good > > home for them. I’ve always had financial ties to a project’s > > Incubation status. In many cases, projects being at the ASF, > > and my involvement in them has assisted my mission of doing > > scientific research and helping win proposals and so forth for > > NASA and other agencies. > > > > Further, I’ve many times been at the same institution in which > > the project has originated from before the ASF. > > > > I think I’ve done a good job on the projects I’ve helped to > > bring here and they have been successful too and have overall > > benefitted the ASF. > > > > This rings to me very similar to Roy’s email circa 2012 I believe > > in which in the Incubator we tried to force the diversity requirement > > as a graduation requirement, and Roy succinctly explained that we > > can’t punish e.g., a podling for having people all from the same > > institution. That would punish that institution for hiring folks > > for open source who work on code at the ASF. Diversity is always > > a strong property of a podling as I feel it makes it more resilient > > but it’s not a hard requirement. I feel the same thing in this thread. > > > > Cheers, > > Chris > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Chris Mattmann, Ph.D. > > Chief Architect > > 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 <javascript:;> > > WWW: http://sunset.usc.edu/~mattmann/ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Adjunct Associate Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > > > > > > -----Original Message----- > > From: jpluser <chris.a.mattm...@jpl.nasa.gov <javascript:;>> > > Reply-To: "general@incubator.apache.org <javascript:;>" < > general@incubator.apache.org <javascript:;>> > > Date: Friday, October 9, 2015 at 5:14 PM > > To: "general@incubator.apache.org <javascript:;>" < > general@incubator.apache.org <javascript:;>> > > Subject: Re: [DISCUSS] Mentor neutrality policy > > > > >I do not agree with this proposal I will elaborate more later > > > > > >Sent from my iPhone > > > > > >> On Oct 9, 2015, at 8:07 AM, Daniel Gruno <humbed...@apache.org > <javascript:;>> wrote: > > >> > > >> Hi Incubator folks, > > >> > > >> I would like to propose we adopt a mentor neutrality policy for > > >> incubating podlings: > > >> > > >> - A mentor must not be financially tied to the project or its > incubation > > >> status. > > >> - A mentor must not have a vested interest in incubating, graduating > or > > >> dismantling a podling that goes beyond the general Apache mission > > >> - A mentor must not be affiliated with the entity granting the code > > >> (company or original project community) > > >> > > >> Furthermore, I would like to see this extended to votes on graduating > or > > >> retiring podlings, so that only people with no organizational (aparty > > >> from the ASF) or financial ties to the project (or the companies > behind > > >> it) can cast a binding vote on graduation or retirement. > > >> > > >> This would essentially mean: > > >> > > >> - If you work for a company (or are hired as consultant/advisor) that > is > > >> entering a project into incubation, you cannot mentor it nor vote > > >> for/against its incubation, graduation or retirement. > > >> - If you are a in the original community behind the project, you > cannot > > >> mentor it nor vote for/against it. > > >> > > >> I believe this would create a neutral mentorship whose sole mission is > > >> to guide podlings with the interests of the ASF in mind. > > >> > > >> > > >> Please do discuss this. If there is (mostly) positive feedback, I > would > > >> like to, at some point, have a vote on including this in the Incubator > > >> policy. I realize this would cut down on the number of potential > > >> mentors, and I would ask that more people step up to the challenge of > > >> mentoring if adopted. > > >> > > >> With regards, > > >> Daniel > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > <javascript:;> > > >> For additional commands, e-mail: general-h...@incubator.apache.org > <javascript:;> > > >> > > > > > >--------------------------------------------------------------------- > > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > <javascript:;> > > >For additional commands, e-mail: general-h...@incubator.apache.org > <javascript:;> > > > > > > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
