Hi folks!

Thanks for all the feedback and on the additional mentor; I think the proposal 
is ready to go to a vote now.

Presuming folks don't have any last minute questions, I'll post it later today.

-busbey

On 2017-05-23 19:52 (-0500), Kostas Sakellis <kos...@cloudera.com> wrote: 
> Thank you John for the feedback.
> 
> On Mon, May 22, 2017 at 12:30 PM, Sean Busbey <bus...@apache.org> wrote:
> 
> > On 2017-05-21 09:46 (-0500), "John D. Ament" <johndam...@apache.org>
> > wrote:
> > >
> > > On Fri, May 19, 2017 at 7:45 PM Sean Busbey <bus...@apache.org> wrote:
> > > >
> > > > == Reliance on salaried Developers ==
> > > >
> > > > The existing contributors to the Livy project have been made by
> > salaried
> > > > engineers from Cloudera, Microsoft and Hortonworks. Since there are
> > three
> > > > major organisations involved, the risk of reliance on a single group of
> > > > salaried developers is mitigated. The Livy user base is diverse, with
> > users
> > > > from across the globe, including users from academic settings. We aim
> > to
> > > > further diversify the Livy user and contributor base.
> > > >
> > >
> > > There's a disconnect between this paragraph and the initial committers
> > > list. Specifically, no one from Microsoft is represented (as best as I
> > can
> > > tell).
> >
> > Ah, this lack of clarity is my fault as an editor. One of the initial
> > committers was recently employed by Microsoft but is now in the
> > process of changing employers. Another person formally affiliated with
> > both the project and Microsoft has decided not to continue
> > participating.
> >
> > I could rephrase this to talk about the contributions made to date as
> > being from individuals then in the employ of three major companies.
> > Then call out the initial committer list as from two of those and one
> > unaffiliated. Would that read clearer?
> >
> 
> I modified this section in the proposal to read: "The contributions to the
> Livy project to date have been made by salaried engineers from Cloudera,
> Microsoft and Hortonworks. One of the individuals on the initial committer
> list has since left Microsoft and is currently unaffiliated. The remaining
> contributors are from Cloudera and Hortonworks. Since there are at least
> two major organizations involved, the risk of reliance on a single group of
> salaried developers is mitigated. The Livy user base is diverse, with users
> from across the globe, including users from academic settings. We aim to
> further diversify the Livy user and contributor base."
> 
> 
> >
> > > > Cloudera currently owns the domain name: http://livy.io/ which will be
> > > > transferred to the ASF and redirected to the official page during
> > > > incubation.
> > > >
> > > >
> > >
> > > I'm assuming that the incoming project is aware that we expect the main
> > dev
> > > landing page to be livy.incubator.apache.org . We will want to track
> > this
> > > as a project specific item.
> >
> >
> > Yep, once all the docs are moved over to ASF infrastructure we can
> > just have the current domain act as a redirect. Should I call this out
> > in the proposal?
> >
> > I modified the proposal to say: "Cloudera currently owns the domain name:
> http://livy.io/. Once all the documentation has moved over to ASF
> infrastructure, the main landing page will become livy.incubator.apache.org
> and the old domain will just act as a redirect."
> 
> 
> >
> > > > == Git Repository ==
> > > >
> > > > git://git.apache.org/livy
> > > >
> > >
> > > Just to confirm - it'll be incubator-livy, not just livy.
> >
> > right right. I'll correct this when making the other edits.
> >
> > Added the correction to the proposal
> 
> 
> >
> > > > == Issue Tracking ==
> > > >
> > > > We would like to import our current JIRA project into the ASF JIRA,
> > such
> > > > that our historical commit message and code comments continue to
> > reference
> > > > the appropriate bug numbers.
> > > >
> > >
> > > I would recommend reaching out to infra to see if the import is possible
> > > before voting on the project. Otherwise you'll need to list out an la
> >
> > Sure I can reach out. I've seen this done a few times, so I consider
> > it low risk. The end of your line appears to have been lost, what's
> > the "Otherwise..." ?
> >
> > > > = Sponsors =
> > > > == Champion ==
> > > >
> > > > * Sean Busbey (bus...@apache.org)
> > > >
> > > > == Nominated Mentors ==
> > > >
> > > > * Bikas Saha (bi...@apache.org)
> > > > * Brock Noland (br...@phdata.io)
> > >
> > >
> > > A couple of points:
> > >
> > > - Sean, while the champion and mentor roles are separate, we do hope that
> > > all champions will continue on as a mentor. If this is your intention
> > > please add yourself.
> >
> > After having to withdraw from mentoring a couple of podlings at the
> > end of last year I am conservative about what my volunteer time looks
> > like right now. I'm certain I can spare the time to help the Livy
> > community get introduced to the incubator. I'm not certain beyond
> > that, so I am not listed as a formal mentor.
> >
> > >  - All mentors must be on the IPMC. Foundation membership isn't a
> > > requirement, however most people use membership to get access to the
> > IPMC.
> > > If Bikas wants to be a mentor, he'll need to join the IPMC otherwise
> > you'll
> > > need to find 2 mentors.
> >
> > I was pretty sure Bikas had already done this step. I'll chase this
> > down and find the disconnect.
> >
> > > - Do the proposed mentors have a relationship to the incoming project,
> > e.g.
> > > do they care if it succeeds from a corporate interest standpoint?
> >
> > I'll let the mentors answer for themselves here, as I won't presume to
> > know their specific motivations for volunteering.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to