I agree with Ted that these minor issues can be ironed out especially if
the community is open to constructive criticism as these folks are. IMHO
the health of the community is much more important than minor insignificant
shortcomings. Social development is changing many things and causing
incongru
+1 (binding)
--Andrew
On 2/6/14 10:51 PM, Sebastian Schelter wrote:
+1 (binding)
Fully agree with Ted's view on the Spark community.
On 02/07/2014 06:32 AM, Ted Dunning wrote:
+1 (binding)
These wrinkles are not as big as they appear. For instance, the
issue with some committers not notic
+1 (binding)
Fully agree with Ted's view on the Spark community.
On 02/07/2014 06:32 AM, 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 actually due to a
better submissi
On Wed, Feb 5, 2014 at 3:20 AM, Bertrand Delacretaz
wrote:
> On Tue, Feb 4, 2014 at 3:02 AM, Marvin Humphrey
> wrote:
>> ...Congratulations to Roman Shaposhnik! The Incubator PMC has voted to
>> recommend Roman as our next Chair in a resolution to the Board next
>> week
>
> Cautious congrat
On Thu, Feb 6, 2014 at 7:05 PM, 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. That's a pretty
HI David Nalley,
Thank you for your comment and concern, really appreciate it.
As Patrick had mentioned in his reply, this is not a persistent problem.
The reminder I sent was about particular topic which could be
interpreted as design or roadmap topic rather than review for a patch.
Rather than
+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 actually due to a
better submission and review process than most tlp's exhibit.
The spark community has more of the apache spirit in it than mos
Hey All - chiming in as an active Spark committer.
> 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. That's a pretty f
Hi Everyone,
The Apache Knox Incubating podling has VOTEd to graduate from the
Incubator.
The community VOTE has passed below with the provided tallies. The
graduation
resolution draft is pasted below. We welcome your VOTE'ing on Knox's
graduation
from the Incubator.
I will leave this VOTE open f
Begin forwarded message:
> From: Shawn McKinney
> Date: February 6, 2014 8:47:54 AM PST
> To: priv...@incubator.apache.org
> Subject: Regarding the Apache incubator project named Sentry
> Reply-To: priv...@incubator.apache.org
>
> Hello,
>
> This mail is to inform you that we have been using
>
> Hope this helps to ease your concern about Spark podling readiness to
> become TLP.
>
I am a bit conflicted. Part of me is inclined to join Craig, Sebb, and
Bertand and issue a -1. At the same time, there exist many +1s here
from folks that I respect and trust, including the mentors of the
po
On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian
wrote:
> Hi IPMC members,
>
> Olingo is waiting to get a third vote for our current release candidate. We
> would really appreciate if someone could have a look at this.
Is it time to enroll Olingo as in our release voting experiment? Or if anyone
> 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 jclouds-mirror user (which is the one that
periodically mirrors the ASF Git repos which are the source of truth to
GitHub). See
I like the idea of sending these to the dev list. I’m going to open an INFRA
ticket for it.
While it seems that the current web hook only sends events when a pull request
is opened or closed, GitHub *can* email watchers for comments as well. I’m
watching the project on GitHub and I get an email
lgtm.
Craig
On Feb 6, 2014, at 11:21 AM, Stack wrote:
> Please check this IP-Clearance form
>
> http://incubator.staging.apache.org/ip-clearance/phoenix.html
>
> It is for a software grant for Apache Phoenix from Salesforce.
>
> Salesforce were the original sponsors of the Phoenix project and
Please check this IP-Clearance form
http://incubator.staging.apache.org/ip-clearance/phoenix.html
It is for a software grant for Apache Phoenix from Salesforce.
Salesforce were the original sponsors of the Phoenix project and
have donated the code to ASF.
Thanks,
St.Ack
Jake, yep thanks for suggesting moving this to another thread :)
In a few days I plan on tallying the VOTEs from the Spark VOTE thread
which at current count is overwhelmingly passing.
I'll keep it open through at least Monday and then in time to add
it to the agenda for the Feb 2014 meeting of t
FYI, we have an on-going thread for the git/github discussion here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201402.mbox/%3CCAEWfVJ%3D_wtDRTNEz4ojvUBf50_VdLDUhiQ15q5rfvFi5eh76uw%40mail.gmail.com%3E
For Phoenix, we'll likely mimic what JClouds is doing, but I live Lar's
ideas as a
I agree with Marvin. In addition I find it odd to rely in two sources of truth
(and two sets of infrastructure, etc) as far as code goes just so we do code
reviews on GitHub.
Anybody who wants to commit now needs to have both the Github repo and the
Apache repo cloned; you can merge a pull reque
Matei
multiple TLPs using it as their main reviewing system? Outside of JClouds I
am unaware of any others using it currently.
I think this is a good discussion to have, but we should start another
thread with it so as to not hijack the Apache Spark graduation thread with
it.
-Jake
On Thu, Feb
On 02/06/2014 07:34 PM, Michael Joyce wrote:
> Let's try this again Marvin since you're jumping to the wrong conclusions
> here.
>
> If people are concerned about work on Github not being automatically
> mirrored to ASF mailing lists that's an Infra problem. They should go talk
> to them to help g
Let's try this again Marvin since you're jumping to the wrong conclusions
here.
If people are concerned about work on Github not being automatically
mirrored to ASF mailing lists that's an Infra problem. They should go talk
to them to help get it addressed, which includes the possibility of
contri
Once the mirror is setup and synced to github (24hr window for this
potentially to occur) then one of the Github Apache org admins can setup
the webhook. The project just needs to put in an infra ticket asking for it
-Jake
On Thu, Feb 6, 2014 at 1:06 PM, Henry Saputra wrote:
> HI Marvin,
>
> T
HI Marvin,
The automatic email to dev@ list for github mirror PR, does it happen
for all ASF github mirrors or each podling need to do some setup to
make it work?
- Henry
On Thu, Feb 6, 2014 at 9:53 AM, Marvin Humphrey wrote:
> On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce wrote:
>> How is do
The webhooks are in place to send pr notifications from github to the
dev@lists, the problem is that comments do not get sent only the
actions of
opening and closing of the pr are sent.
-Jake
On Thu, Feb 6, 2014 at 12:08 PM, Michael Joyce wrote:
> How is doing a review on Github any different
On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce wrote:
> How is doing a review on Github any different than doing a review on Review
> Board?
One is captured to Apache controlled channels and the other is not.
> If there's concern that work on Github isn't being adequately mirrored on
> the mailin
This got me to thinking.
If git is the working tool of the team, and actions from the git site are
automatically forwarded to dev, how about putting release votes on git?
Could an action item be created in git by the release manager to release, say,
version 3.4.5 of the code? Voting could be do
Having developer/committer comments from a github review automatically show up
on dev@ lists will ease my concern that the git activities somehow avoid the
"if it isn't on the mail lists, it didn't happen" requirement.
Craig
On Feb 6, 2014, at 9:08 AM, Michael Joyce wrote:
> How is doing a rev
How is doing a review on Github any different than doing a review on Review
Board? If there's concern that work on Github isn't being adequately
mirrored on the mailing lists then that sounds like an Infra problem to me.
There are plenty of hooks [1] that makes this easy to do and, if I'm not
mista
Hi IPMC members,
Olingo is waiting to get a third vote for our current release candidate. We
would really appreciate if someone could have a look at this.
Thanks & Best Regards,
Christian
-Original Message-
From: Dave Brondsema [mailto:d...@brondsema.net]
Sent: Dienstag, 4. Februar 20
>
> 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 gi
31 matches
Mail list logo
