Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: <9C73A06F-1CE9-42B5-99B1-4DADEBFDB995@gmail.com>
References: <B9C259FA-118F-4433-87A3-967BF6BA79A6@gmail.com>
 <5ADA0D81-AFC4-4C13-ABCD-9464C27723C7@oracle.com>
 <9BA99E04-68AF-4023-AC3C-F4F52FB2414D@gmail.com>
 <BFAACF49-4CB3-487C-8A0F-6D20CCE0B503@oracle.com>
 <9C73A06F-1CE9-42B5-99B1-4DADEBFDB995@gmail.com>
From: David Nalley <david@gnsa.us>
Date: Thu, 6 Feb 2014 04:22:47 -0500
Message-ID: 
 <CAKprHVach1LVLGiWj-k24dc9UkkRaardbaONm14LKqzfRG38_Q@mail.gmail.com>
Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator
To: general@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

>
> If you look at the GitHub code reviews (https://github.com/apache/incubator-spark/pulls), you'll see that lots of people are contributing to reviewing. But I agree that the new committer onboarding process should include having them do a test commit.
>

Matei:

Reviews being done on github causes me a bit of concern. Generally
dev@ should be the nexus for a project, and most of the projects that
have github in the workflow ensure that pull requests get sent to dev@
so the discussions, reviews, and patches themselves are seen and
archived there.

I see that one of your mentors brought up similar concerns about this
(as well as where discussions on strategy or roadmap happen) yesterday
on dev@ - that doesn't leave me with warm fuzzy assurance that the
project groks the Apache way.

--David

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