Thank you so much Craig and it feels good to work to gain your
support.
Cheers and have a fantastic weekend.
Cheers,
Chris
-Original Message-
From: Craig L Russell
Reply-To: "general@incubator.apache.org"
Date: Friday, February 7, 2014 2:28 PM
To: "general@incubator.apache.org"
Subj
I'm happy to see that my concerns about Spark are being actively addressed in a
professional non-confrontational manner.
The mismatch between committers and proposed PMC members has been resolved. I
guess the only missing bit is updating the graduation resolution.
The use of git for pull reques
Ah looks like the missing PR title only happen for the emails
describing comments from the Github pull requests.
- Henry
On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra wrote:
> Hi Jake,
>
> Looks like all the emails from the PR has the same subject:
> "[GitHub] incubator-spark pull request:"
>
>
We had a bit of a snafu on adding PR titles to the subject lines, but
it's been taken care of now.
With regards,
Daniel.
On 02/07/2014 09:57 PM, Henry Saputra wrote:
> Ah looks like the missing PR title only happen for the emails
> describing comments from the Github pull requests.
>
> - Henry
>
Hi Jake,
Looks like all the emails from the PR has the same subject:
"[GitHub] incubator-spark pull request:"
Is there a way to get the Title of the pull request included in the
Subject line?
Thanks,
Henry
On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell wrote:
> I just wanted to follow up on my
That is great news! Thanks Jake and Daniel.
-- Joyce
On Fri, Feb 7, 2014 at 8:51 AM, Henry Saputra wrote:
> W00t! Looks like it is working :)
>
> Thanks Jake and Daniel.
>
> - Henry
>
> On Friday, February 7, 2014, Jake Farrell wrote:
>
> > I just wanted to follow up on my previous comments a
W00t! Looks like it is working :)
Thanks Jake and Daniel.
- Henry
On Friday, February 7, 2014, Jake Farrell wrote:
> I just wanted to follow up on my previous comments about the Github
> webhooks not posting comments, Daniel Gruno and I have been debugging the
> Github webhooks we had in place
I just wanted to follow up on my previous comments about the Github
webhooks not posting comments, Daniel Gruno and I have been debugging the
Github webhooks we had in place to send pull request notifications and we
have fixed it so comments for issues and pull requests will now go to the
dev@ list
Thanks Bertrand, for your feedback and as I have mentioned, we filed
the account requests, and have explained from the community perspective
the issues at hand (Matei has done so grandly in the last day and
don't have time now to look up the exact thread pointer but look
for some replies by Matei o
Hi Chris,
On Fri, Feb 7, 2014 at 4:20 PM, Chris Mattmann wrote:
>... Bertrand, you originally VOTEd +1 until Craig mentioned his concerns
> about accounts not having been filed. Matei and others immediately
> stepped up (including myself), and explained the situation, and
> filed the accounts. Se
Hi Bertrand,
(changing this to DISCUSS thread to avoid continuing hijacking
the VOTE thread)
Of Spark's IPMC direct mentorship, 5 of the 7 mentors
have all VOTEd for its graduation:
Chris Mattmann
Andrew Hart
Henry Saputra
Roman Shaposhnik
Suresh Marru
Still waiting on +1s from:
Paul Ramirez
Hi Marvin,
On Fri, Feb 7, 2014 at 7:07 AM, Marvin Humphrey wrote:
> On Wed, Feb 5, 2014 at 3:20 AM, Bertrand Delacretaz
> wrote:
...
>> Cautious congrats here, as the board still has to accept this
>> recommendation.
...
> You know, I thought about this before posting then went ahead anyway. I
+1
Agree with Ted here. I would write more but his input is succinct and
right on.
--Paul Ramirez
On 2/6/14 9:32 PM, "Ted Dunning" wrote:
>+1 (binding)
>
>These wrinkles are not as big as they appear. For instance, the issue
>with some committers not noticing that their accounts were live is
On Fri, Feb 7, 2014 at 4:05 AM, David Nalley wrote:
> ...The part that disturbs me is that after the vote passed in the
> community, and came to the IPMC a mentor is still having to remind
> folks that things like strategy and roadmap discussions need to happen
> on the mailing list...
Yes - cons
Thanks for describing this, Andrew. We’ll do it as well.
Matei
On Feb 6, 2014, at 1:24 PM, Andrew Phillips wrote:
>> The other option would be to somehow subscribe dev@ through the standard
>> GitHub watcher framework by making it the notification address
>
>
> jclouds does that for the jcl
15 matches
Mail list logo
