incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: Trafodion podling needs more mentors
Date Tue, 21 Jun 2016 01:25:21 GMT
Dave,

Thanks for clarifying.  I'm glad its these two items, as I would have been
worried if there were others.

1. Ideally, the PPMC should be able to vet the release.  You're pretty
close, but you want to get to the day where you have 0 issues found during
an incubating release.  Realistically, that's why the PPMC vote is a
recommendation vote to the IPMC and the IPMC has final say.  Part of the
maturity assessment says whether or not you can vet your own releases, so
that when it gets to this list its less deep digging and more "Yes, they
got this."

Your most recent release had an odd quirk about it, probably been there for
a while and no one noticed. That's why we include the incubating disclaimer
on the release.

2. This is a temporary problem.  If you're ever in a situation where you
need someone added, and St.Ack's not around, just send an email to
private@i.a.o and someone will give you a hand.  When you graduate, your VP
will be the one handling these requests.

John

On Mon, Jun 20, 2016 at 9:02 PM Dave Birdsall <dave.birdsall@esgyn.com>
wrote:

> At the moment, mainly two things:
>
> 1. Release validation
> 2. Occasional administrative items associated with adding new committers
> and/or podling PMC members
>
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: Monday, June 20, 2016 5:43 PM
> To: general@incubator.apache.org
> Subject: Re: Trafodion podling needs more mentors
>
> Also, could you please expound on what you are reliant on St.Ack on?
>
> On Mon, Jun 20, 2016 at 8:34 PM Roman Shaposhnik <roman@shaposhnik.org>
> wrote:
>
> > Help me understand, why is this a mentor issue and not IPMC one?
> >
> > Thanks,
> > Roman.
> >
> > On Fri, Jun 17, 2016 at 6:38 PM, Atanu Mishra <atanu.mishra@esgyn.com>
> > wrote:
> > > Response below.
> > >
> > > On Fri, Jun 17, 2016 at 4:58 PM, Roman Shaposhnik
> > > <roman@shaposhnik.org>
> > > wrote:
> > >
> > >> On Wed, Jun 15, 2016 at 4:05 PM, John D. Ament
> > >> <johndament@apache.org>
> > >> wrote:
> > >> > Dave,
> > >> >
> > >> > For some reason, I feel like I commented on that thread as well,
> > >> > but
> > >> don't
> > >> > see it, so I'm either thinking of something else or its inlined
> > somewhere
> > >> > that I didn't see (e.g. the emails back and forth with Pierre).
> > >> >
> > >> > The question to always ask with company alliances is if someone
> > >> > would contribute to the project if they weren't paid by $dayjob to
> do
> > >> > so.
> > The
> > >> > beauty of the Apache Way is by focusing on individuals, this
> > >> > problem becomes more apparent.  Of the new contributors you added
> > >> > that work
> > for
> > >> > Esgyn, which of them would realistically contribute to Trafodion
> > >> > if
> > they
> > >> > weren't employed by Esgyn?  Likewise, if Esgyn stopped building a
> > product
> > >> > on top of Trafodion, would those contributors remain?
> > >> >
> > >> > In addition, with such tight company affiliation, does the PMC
> > represent
> > >> a
> > >> > reasonable cross section so that they can assert their iP claims?
> > >> > For example, based on looking at the usage of Trafodion vs Apache
> > Trafodion
> > >> on
> > >> > https://esgyn.com/ would the PMC send an email to some
> > representative of
> > >> > Esgyn asking them to correct the branding errors? (To be clear, a
> > cursory
> > >> > look around the website only gives me one minor error, nothing
> > >> > crazy
> > like
> > >> > we've seen with other projects, you've done a great job keeping
> > branding
> > >> in
> > >> > line with guidelines on both the ASF site and here)
> > >> >
> > >> > These are the reasons, at least from my POV, why community
> > >> > diversity
> > is
> > >> > important.  To be honest, I don't see any of the typical warning
> > signs I
> > >> > see with company backed ASF projects that I see here.  Its clear
> > >> > that
> > its
> > >> > ASF developed first.  I see great communication and collaboration
> > >> > via
> > >> email
> > >> > (heck, I wish my $dayjob communicated this well via email).
> > >> >
> > >> > So to answer your question, no, I don't think Trafodion needs
> > >> > more mentors.  Maybe you need some help with the graduation
> > >> > process, but
> > from
> > >> my
> > >> > POV you seem like TLP material to me.
> > >>
> > >> +1 to the above. I honestly still don't understand what is the
> > >> +problem
> > >> with Trafodion
> > >> (if any) that piling mentors up would be a good solution to.
> > >>
> > >
> > > An extract from the original email should help answer that question.
> > > We are very dependent on one mentor (St.Ack) at the moment.
> > >
> > >> We have done two releases now, learning many lessons from that
> > > experience.
> > >> But we need more help checking out our release candidates. Our
> > >> current mentors have been pressed for time. (We started with five,
> > >> two have
> > since
> > >> resigned due to other obligations.)
> > >
> > > Atanu
> > >
> > > --
> > > __________
> > > *Atanu Mishra*
> > > *Esgyn Corporation*
> > > Milpitas, CA 95035
> > > m: +1.408.219.9765
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message