Hi!
after an enthusiastic discussion with the community:
https://lists.apache.org/thread.html/3fe85fb22cd1fd2c4e4a2370c03a453448a1ea12735d1e136cae6e79@%3Cdev.servicecomb.apache.org%3E
culminating with a positive vote:
https://lists.apache.org/thread.html/53f73695f8b504d1ed52e837cff9b8877e98c8a9c
Hi -
No objections from me. I do ask you let the IPMC know in your podling report if
this results in any controversy from the creators of any autoclosed pull
requests.
Regards,
Dave
Sent from my iPhone
> On Sep 19, 2018, at 6:48 PM, Sid Anand wrote:
>
> Thanks Greg and Ismael!
> -s
>
>> On
Thanks Greg and Ismael!
-s
On Wed, Sep 19, 2018 at 6:39 PM Greg Stein wrote:
> Hello all,
>
> The confusion here was "write access to the repository" (not allowed)
> versus "write access to Pull Requests" (allowed). It took the Beam folks
> some research to determine that GitHub *does* different
Hello all,
The confusion here was "write access to the repository" (not allowed)
versus "write access to Pull Requests" (allowed). It took the Beam folks
some research to determine that GitHub *does* differentiate between these
two write capabilities (historically, GitHub has not been very granula
Hi, JB,
The proposal on wiki has been Updated.
Add JB and Kevin as mentors.
But we still look for champion, can someone help?
Thanks
在 2018/9/19 下午1:53， "Jean-Baptiste Onofré" 写入:
>Hi,
>
>sure. I think we can update the wiki with the proposal.
>
>Thoughts ?
>
>Regards
>JB
>
>On 19/09/2018
Ismael,
Thanks for this pointer. I've re-opened my INFRA ticket and referenced your
Apache Beam one. Super helpful.. if we get it enabled, please collect a
beer from anyone in the Apache Airflow community!
-s
On Wed, Sep 19, 2018 at 7:39 AM Ismaël Mejía wrote:
> While I agree that autoclosing P
Hi,
Sorry for removing your report I’ll fix it.
Thanks,.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
The October 2018 Incubator report [1] timeline is as follows:
Wed October 03 -- Podling reports due by end of day
Sun October 07 -- Shepherd reviews due by end of day
Sun October 07 -- Summary due by end of day
Tue October 09 -- Mentor signoff due by end of day
Wed October
Hello all,
The Apache MXNet (incubating) Community announces the availability of
Apache MXNet (incubating) 1.3.0!
Release blog post:
https://blogs.apache.org/mxnet/entry/announcing-apache-mxnet-incubating-1
https://medium.com/apache-mxnet/announcing-apache-mxnet-1-3-0-484ea78c22ad
Apache MXNet (
Thanks to all who voted.
The release has PASSED with the following IPMC votes:
+1 Jim Jagielski (binding)
+1 Justin Mclean (binding)
+1 Olivier Lamy (binding)
+1 Jean-Baptiste Onofré (binding)
I will proceed to publish the release and send ANNOUNCE.
On behalf of Apache Gobblin, thank you!
Reg
Hi,
So we’ve over the 50% mark, so those who has responded a number have indicated
that they will put more effort into mentoring and stay on, 7 people so far will
continue as mentors, 19 have asked to step down.
We had every one of the gearpump mentors ask to step down, but given the
project i
HI,
> This is not correct. The vote must run for at least 72 hours regardless of
> when the number of votes is reached.
Correct the vote doesn’t end when it get the required number of votes. I guess
you could possibly close it early if the entire PPMC/IPMC voted on it but I
can’t see that happ
Hi Craig,
Sure thing. I will change that statement, but normally I wait for at least a
week to collect the votes for all the openwhisk modules.
Could you, by the way, verify the artifacts for this vote mail thread?
Thanks.
Best wishes.
Vincent Hou (侯胜博)
Advisory Software Engineer, OpenWhisk Con
On Wed, Sep 19, 2018 at 5:18 PM Craig Russell wrote:
>...The vote must run for at least 72 hours regardless of when the number of
>votes is reached...
Indeed, the goal is to allow people who are not working full-time on a
project to have a look if they want.
-Bertrand
-
On Tue, Sep 18, 2018 at 6:28 PM Vincent S Hou wrote:
> This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk
> python, php and swift runtimes 1.12.0 [RC1]
+1 for the release of the artifacts listed below with their sha512 digests.
Checked signature, digests, LICENSE, D
On Tue, Sep 18, 2018 at 6:11 PM Vincent S Hou wrote:
> ...This is a call for vote to release Apache OpenWhisk (Incubating):
> OpenWhisk nodejs, java and docker runtimes 1.12.0
+1 for the release of the artifacts listed below with their sha512 digests.
Checked signature, digests, LICENSE, DISCLA
Hi Vincent,
> On Sep 18, 2018, at 9:28 AM, Vincent S Hou wrote:
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
This is not correct. The vote must run for at least 72 hours regardless of when
the number of votes is reached.
Regards,
Craig
C
Hi Alex,
Without going into history let's discuss the current guidance:
http://www.apache.org/licenses/#provenance
If you want to cite historical references that conflict with this, we can have
that discussion.
Establishing provenance is one of the primary tasks of a project in incubation.
In
Hi Jim,
I saw you actually vote on this mail thread for python, php and swift runtimes
twice.
Did you mean to vote on the mail thread for nodejs, java and docker runtimes?
Thanks.
Best wishes.
Vincent Hou (侯胜博)
Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
Not
Thanks everyone. The vote passes with 9 +1s and we will move on with
retirement.
Manu
On Tue, Sep 18, 2018 at 9:34 AM Willem Jiang wrote:
> +1.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Sep 16, 2018 at 5:32 PM Manu Zhang
> wrote:
> >
> > Hi mentors,
> >
> > The Ge
While I agree that autoclosing PRs can be unwelcoming. I don't see
clearly the argument of INFRA in the ticket.
> The policy of no-write-access for bots is a requirement by the foundation
> legal team. We cannot allow write access to repos without an ICLA.
Labeling and closing the PR in github d
+1 (binding)
> On Sep 18, 2018, at 12:28 PM, Vincent S Hou wrote:
>
> Dear IPMC members,
>
> This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk
> python, php and swift runtimes 1.12.0 [RC1].
>
> The Apache OpenWhisk community has voted on and approved a proposal to
>
Ok，I will update the wiki
But we are still looking for volunteer to be champion，
Anyone can help？
在 2018/9/19 下午1:53， "Jean-Baptiste Onofré" 写入:
>Hi,
>
>sure. I think we can update the wiki with the proposal.
>
>Thoughts ?
>
>Regards
>JB
>
>On 19/09/2018 04:34, Tan,Zhongyi wrote:
>> Hi，JB，
>>
Hi, Von Gosling
In a short time, the core develop team of brpc are still focusing on
adopting brpc to satisfy scenarios where performance of communication and
thread scheduling do really matter, such as HPC, search backend and
distributed storage. There is some work that we can do:
1. Merge rdma
24 matches
Mail list logo
