Stepping down as Page Speed mentor

[Phil Sorber]

I have not been able to commit the amount of time and energy needed to
fulfill my obligations as mentor to the Page Speed podling, and thus I am
stepping down as a mentor. Hopefully someone else will be able to help them
to graduation.

Thanks.

Re: [VOTE] Graduate Traffic Control to a top level project

[Phil Sorber]

+1

Thanks.

On Fri, Apr 20, 2018 at 7:20 PM Matt Sicker <boa...@gmail.com> wrote:

> +1
>
> It would be cool if the project site didn't look like it was from the year
> 2000. ;)
>
> On 20 April 2018 at 13:02, Dave Neuman <neu...@apache.org> wrote:
>
> > Hello IPMC,
> > The Traffic Control PMC would like to call a vote to graduate from the
> > incubator to a top level Apache project!  The traffic control community
> has
> > voted to graduate [1], voted on our resolution [2], and opened a thread
> to
> > discuss our resolution on this list [3].
> >
> > Traffic Control entered the incubator on July 12, 2016.  Since then we
> have
> > announced 4 releases, nominated 4 new committers, organized 4 summits,
> had
> > more than 8,000 commits from 63 different contributors, and -- most
> > importantly -- we have grown and diversified our community.  Apache
> Traffic
> > Control is a healthy project that is already acting like an Apache top
> > level project, and we are ready to take the next step.
> >
> > I would like to ask that you please take a moment to vote on our
> > resolution.  Please respond with one of the following:
> >
> > [ ] +1 Graduate Traffic Control from the incubator
> > [ ] +0 No Opinion
> > [ ] -1 Do not graduate Traffic Control from the incubator (please
> provide a
> > reason)
> >
> > The vote is open for a minimum of 72 hours and will need at least 3 more
> +1
> > votes than -1 votes from IPMC members to succeed.
> >
> > Please do not hesitate to let us know if you have any questions.
> >
> > Thanks,
> > Dave
> >
> > [1]
> > https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
> > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> > [2]
> > https://lists.apache.org/thread.html/53c51f3eab45525c4e6c1bc5207265
> > 9c751fd9c59001006791e4b0e3@%3Cdev.trafficcontrol.apache.org%3E
> > [3]
> > https://lists.apache.org/thread.html/837b7bfd090d84632fe1f314484c32
> > f18cddf5030b21289879753403@%3Cgeneral.incubator.apache.org%3E
> >
> >
> >
> > ---
> >
> > Establish the Apache Traffic Control Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to building, monitoring, configuring, and provisioning a large
> > scale content delivery network (CDN)..
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Traffic Control Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > building, monitoring, configuring, and provisioning a large scale
> > content delivery network (CDN).; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> > and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache Traffic
> > Control Project, and to have primary responsibility for management of
> > the projects within the scope of responsibility of the Apache Traffic
> > Control Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache Traffic Control
> > Project:
> >
> >  * Dan Kirkwood   <dang...@apache.org>
> >  * David Neuman   <neu...@apache.org>
> >  * Dewayne Richardson <dewr...@apache.org>
> >  * Eric Covener   <cove...@apache.org>
> >  * Eric Friedrich <fri...@apache.org>
> >  * Hank Beatty<hbea...@apache.org>
> >  * Jan van Doorn  <j...@apache.org>
> >  * Jeff Elsloo<els...@apache.org>
> >  * Jeremy Mitchell<mitchell...@apache.org>
> >  * Leif Hedstrom  <zw...@apache.org>
> >  * Mark Torluemke <mtorlue...@apache.org>
> >  * Phil Sorber<sor...@apache.org>
> >  * Steve Malenfant<smalenf...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dav

Re: [DISCUSS] Resolution to graduate Traffic Control to a top level project

[Phil Sorber]

Speaking with my mentor hat on, I think this looks good. Hopefully this thread 
is quiet because everyone agrees?

Thanks.

On 2018/04/12 21:59:00, Dave Neuman <neu...@apache.org> wrote: 
> Hello IPMC,
> Per the graduation guidelines, the Traffic Control community would like to
> start a DISCUSS thread on graduating to a top level project.  We have
> discussed internally on private, taken a vote to draft a resolution [1],
> and voted on the resolution [2].  The next step in the process is to submit
> our resolution here for feedback.  Please take a moment to review our
> resolution and let you know what feedback you have.
> 
> Thanks in advance,
> Dave
> 
> [1]
> https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/53c51f3eab45525c4e6c1bc52072659c751fd9c59001006791e4b0e3@%3Cdev.trafficcontrol.apache.org%3E
> 
> 
> Resolution:
> 
> Establish the Apache Traffic Control Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to building, monitoring, configuring, and provisioning a large
> scale content delivery network (CDN)..
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Traffic Control Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
> 
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> responsible for the creation and maintenance of software related to
> building, monitoring, configuring, and provisioning a large scale
> content delivery network (CDN).; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Traffic
> Control Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache Traffic
> Control Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Traffic Control
> Project:
> 
>  * Dan Kirkwood   <dang...@apache.org>
>  * David Neuman   <neu...@apache.org>
>  * Dewayne Richardson <dewr...@apache.org>
>  * Eric Covener   <cove...@apache.org>
>  * Eric Friedrich <fri...@apache.org>
>  * Hank Beatty<hbea...@apache.org>
>  * Jan van Doorn  <j...@apache.org>
>  * Jeff Elsloo<els...@apache.org>
>  * Jeremy Mitchell<mitchell...@apache.org>
>  * Leif Hedstrom  <zw...@apache.org>
>  * Mark Torluemke <mtorlue...@apache.org>
>  * Phil Sorber<sor...@apache.org>
>  * Steve Malenfant<smalenf...@apache.org>
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> to the office of Vice President, Apache Traffic Control, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
> 
> RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> tasked with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Traffic Control
> Project; and be it further
> 
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Traffic Control podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Traffic Control podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
> 

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

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

[Phil Sorber]

+1 (binding). After having fought with docker for a bit I was able to build
packages. Sig and hashes check out as well. We should work on getting all
our GPG keys signed by each other next summit, but that is not a show
stopper in my opinion.

Thanks!

On Tue, Jan 16, 2018 at 11:45 AM Leif Hedstrom  wrote:

> +1 (binding). Tested the build, RPMs successfully built, and double
> checked the RAT report.
>
> Cheers
>
> — Leif
>
> > On Jan 10, 2018, at 18:04, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > +1 (binding)
> >
> > I checked:
> > - incubating in name
> > - hashes and signatures good
> > - DISCLAIMER exists
> > - LICENSE good and NOTICE OK (see below)
> > - no unexpected binary files
> > - All ALv2 source files have ASF headers
> >
> > For the NOTICE don’t forget to update the year to be the current one and
> there’s no need to list information about the fonts inside it.
> >
> > Thanks,
> > Justin
> > -
> > 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
>
>

Re: [PROPOSAL] PageSpeed

[Phil Sorber]

I would be interested in helping out in a mentor role.

Thanks.

On Mon, Sep 25, 2017, 14:29 Leif Hedstrom  wrote:

>
> > On Sep 20, 2017, at 4:44 AM, Otto van der Schaaf 
> wrote:
> >
> > Dear Apache Incubator Community,
> >
> > We are excited to share our proposal for discussion and feedback for
> > entering Apache Incubation.
> > PageSpeed represents a series of open source technologies to help make
> the
> > web faster by rewriting web pages to reduce latency and bandwidth.
> >
> > Our proposal can be found at
> > https://wiki.apache.org/incubator/PageSpeedProposal and is also included
> > below.
>
> Ping? Any more thoughts on this, or should we take this to a [VOTE] ?
>
> We might want one more mentor if anyone is interested?
>
> Cheers,
>
> — leif
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Podlings & Gitbox Usage

[Phil Sorber]

+1

On Fri, Jul 28, 2017 at 11:00 AM aditi hilbert  wrote:

> +1
> The Apache Mynewt community loves it.
>
> thanks,
> aditi
>
> > On Jul 28, 2017, at 8:48 AM, John D. Ament 
> wrote:
> >
> > All,
> >
> > As many are aware, Infra has been rolling out a new service that allows
> > projects to leverage git repositories dually hosted on github and ASF git
> > repositories, commonly known as gitbox.  This effectively allows a
> project
> > to commit directly to Github and have those commits reflect back on the
> ASF
> > side.
> >
> > This has been especially useful to a number of projects, since the github
> > interface gives many options for managing repositories.  I've recently
> also
> > asked infra to open it up to allow any IPMC member to request a gitbox
> > repository for any approved podling that is using gitbox.  Podlings I
> think
> > have found this useful, since many of them come from a github background.
> > They like using the tool and having it available for all to use.
> >
> > So with that said, I want to propose some broad incubator wide policies
> for
> > gitbox.  I'd like to propose that gitbox usage is approved for all
> > podlings, there is nothing to inhibit a podling to request a gitbox
> > repository and as long as a podling feels the need to use gitbox, like
> they
> > would any other tool that we can integrate with, they should be free to
> use
> > it without any additional approvals required.
> >
> > So please let me know your thoughts.  If I don't hear any -1's I plan to
> > submit an infra ticket early next week to enable the access for all
> > approved podlings.  Please note that your first conversion may need some
> > lead time with infra.
> >
> > Regards,
> >
> > John
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: ZeroMQ licensing in Apache MXNet

[Phil Sorber]

What about nanomsg? It's supposed to be a functional replacement for
ZeroMQ, has C++ bindings available and is MIT licensed.

http://nanomsg.org/documentation-zeromq.html

On Fri, Jul 7, 2017 at 8:02 AM Felix Cheung  wrote:

> I think the header is required at compile time but zeromq is optional at
> runtime.
>
>
> On Fri, Jul 7, 2017 at 1:54 AM Greg Stein  wrote:
>
> > If it is optional at compile-time, then a header file is very allowable.
> As
> > long as MXNet can be compiled without ZeroMQ on the box, then I see no
> > issue at all.
> >
> > On Thu, Jul 6, 2017 at 3:51 PM, Felix Cheung 
> > wrote:
> >
> > > Isn't the release binaries going to contain bits from zeromq because of
> > > #include though?
> > >
> > > That header file is still going to be LGPL 3.0 licensed right?
> > >
> > >
> > > On Thu, Jul 6, 2017 at 12:45 PM John D. Ament 
> > > wrote:
> > >
> > > > Mu,
> > > >
> > > > So what happens when ZeroMQ is not available, do you fall back to
> > > something
> > > > else?
> > > >
> > > > I'm inclined to say that this is allowable, knowing that its an
> > optional
> > > > dynamically linked dependency that has an alternative.  Assuming it
> has
> > > an
> > > > alternative.
> > > >
> > > > I would strongly encourage podlings to try to leverage what the ASF
> > > > provides, we ship a number of messaging systems that may be better
> > from a
> > > > licensing stand point - ActiveMQ, RocketMQ, Pulsar.
> > > >
> > > > John
> > > >
> > > > On Thu, Jul 6, 2017 at 3:27 PM Mu Li  wrote:
> > > >
> > > > > MXNet's backend is written in C++, which is not able to use the
> > > > > java interface.
> > > > >
> > > > > On Thu, Jul 6, 2017 at 12:25 PM, Luciano Resende <
> > luckbr1...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Are you guys able to use this (which is what we use in Apache
> > Toree)?
> > > > > >
> > > > > > https://github.com/zeromq/jeromq
> > > > > >
> > > > > > Which has been successfully relicensed?
> > > > > > https://github.com/zeromq/jeromq/blob/master/LICENSE
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 5, 2017 at 11:23 PM, Henri Yandell <
> bay...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > One of the items that is on the list to do before releasing
> > Apache
> > > > > MXNet
> > > > > > is
> > > > > > > removing ZeroMQ from the codebase/dependencies.
> > > > > > >
> > > > > > > ZeroMQ is licensed under the LGPL 3.0 with an exception for
> > static
> > > > > > > compiling.
> > > > > > >
> > > > > > > They have long been interested in relicensing to MPL 2.0, but
> > > haven't
> > > > > > made
> > > > > > > much progress, though they did relicense JeroMQ (Java
> > > > > > > wrapper/implementaiton) last year.
> > > > > > >
> > > > > > > In the last few months they've made a lot of progress towards
> > > > > > relicensing:
> > > > > > > https://github.com/zeromq/libzmq/tree/master/RELICENSE
> > > > > > >
> > > > > > > I'd like to ask on legal-discuss@ for an exception (one year?)
> > to
> > > > > > continue
> > > > > > > using ZeroMQ, with prominent documentation, in MXNet given the
> > > trend
> > > > > > > towards MPL 2.0.
> > > > > > >
> > > > > > > Any concerns before I do so?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Hen
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > > http://twitter.com/lresende1975
> > > > > > http://lresende.blogspot.com/
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

[Phil Sorber]

Checksums match.

GPG sig verifies, but is untrusted:
$ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
gpg: assuming signed data in `apache-trafficcontrol-2.0.0-incubating.tar.gz'
gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
9AB7BDD5
gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
fri...@apache.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5

No signatures:
$ gpg --list-sigs 9AB7BDD5
pub   4096R/9AB7BDD5 2017-04-25
uid  Eric Friedrich (CODE SIGNING KEY) 
sig 39AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
fri...@apache.org>
sub   4096R/F445ABB1 2017-04-25
sig  9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
fri...@apache.org>

I won't -1 on that, but we should try to have every RM make sure their keys
are trusted. I've already spoken with Eric about this.

Build also works, with one caveat. You have to set selinux to unenforcing,
otherwise you fail from permissions errors. You can do this with
`setenforce 0` as root. I won't -1 for this either, but we should add that
to the build documentation.

-rw-r--r--. 1 phil phil  51M Jun 30 15:12
traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 910K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 858K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  22K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil  21K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 142K Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  17M Jun 30 15:12
traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 417K Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm

+1 binding.

Thanks!

On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean 
wrote:

> Hi,
>
> > The build instructions will be put in place once the release is done
> > -- catch-22.
>
> Yep another reason for including them in the release IMO.
>
> > Would Jira issues for the copyright and build instruction issues be
> sufficient?
>
> Yes. Changing my vote to +1 binding.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Traffic Control 1.8.1-incubating (RC0)

[Phil Sorber]

+1 binding.

Agree with statements made up-thread.

Built all artifacts using docker.

-rw-r--r--. 1 root root  986K Jun 13 00:13 build-traffic_monitor.log
-rw-r--r--. 1 root root  130K Jun 13 00:12 build-traffic_ops.log
-rw-r--r--. 1 root root  205K Jun 13 00:13 build-traffic_portal.log
-rw-r--r--. 1 root root 1019K Jun 13 00:13 build-traffic_router.log
-rw-r--r--. 1 root root   18K Jun 13 00:12 build-traffic_stats.log
-rw-r--r--. 1 root root   51M Jun 13 00:13
traffic_monitor-1.8.1-4642.cc56e763.el7.x86_64.rpm
-rw-r--r--. 1 root root  810K Jun 13 00:12
traffic_ops-1.8.1-4642.cc56e763.el7.src.rpm
-rw-r--r--. 1 root root  5.1M Jun 13 00:12
traffic_ops-1.8.1-4642.cc56e763.el7.x86_64.rpm
-rw-r--r--. 1 root root   22K Jun 13 00:12
traffic_ops_ort-1.8.1-4642.cc56e763.el7.src.rpm
-rw-r--r--. 1 root root   21K Jun 13 00:12
traffic_ops_ort-1.8.1-4642.cc56e763.el7.x86_64.rpm
-rw-r--r--. 1 root root  143K Jun 13 00:13
traffic_portal-1.8.1-4642.cc56e763.el7.src.rpm
-rw-r--r--. 1 root root  3.6M Jun 13 00:13
traffic_portal-1.8.1-4642.cc56e763.el7.x86_64.rpm
-rw-r--r--. 1 root root   19M Jun 13 00:13
traffic_router-1.8.1-4642.cc56e763.el7.x86_64.rpm
-rw-r--r--. 1 root root   38K Jun 13 00:12
traffic_stats-1.8.1-4642.cc56e763.el7.src.rpm
-rw-r--r--. 1 root root  5.0M Jun 13 00:12
traffic_stats-1.8.1-4642.cc56e763.el7.x86_64.rpm

Thanks.

On Sat, Jun 10, 2017 at 6:48 PM Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - incubating in release name
> - signatures and hashes good
> - disclaimer exists
> - In NOTICE there no need to list the fonts
> - LICENSE is good
> - Source files have apache headers
> - No unexpected binaries files
> - Didn’t build a that requires docker
>
> For completeness you may want to include these Apache licensed [3] font
> files in LICENSE. [1][2]
>
> Thanks,
> Justin
>
> 1.
> trafficcontrol-incubating-1.8.1/docs/source/_themes/sphinx_rtd_theme/static/fonts/RobotoSlab-Bold.ttf
> 2.
> trafficcontrol-incubating-1.8.1/docs/source/_themes/sphinx_rtd_theme/static/fonts/RobotoSlab-Regular.ttf
> 3. https://fonts.google.com/specimen/Roboto+Slab
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar into the Apache Incubator

[Phil Sorber]

+1 (binding)

On Wed, May 17, 2017 at 8:21 AM Jim Jagielski  wrote:

> Make it so! +1! (binding)
>
> > On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >
> > Hi All,
> >
> > As the champion for Pulsar, I would like to start a VOTE to bring the
> > project in as Apache incubator podling.
> >
> > The ASF voting rules are described:
> >
> >   https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for which
> > only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Pulsar into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >   https://wiki.apache.org/incubator/PulsarProposal
> >
> > -Bryan
> >
> >
> > = Pulsar Proposal =
> >
> > == Abstract ==
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at-least-once delivery of messages, automatic cursor
> management for
> > subscribers, and cross-datacenter replication.
> >
> > == Proposal ==
> >
> > Pub-sub messaging is a very common design pattern that is increasingly
> found
> > in distributed systems powering Internet applications. These applications
> > provide real-time services, and need publish-latencies of 5ms on average
> and
> > no more than 15ms at the 99th percentile. At Internet scale, these
> > applications require a messaging system with ordering, strong
> durability, and
> > delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> > of a production environment, the messages have to be committed on
> multiple
> > disks or nodes.
> >
> > Pulsar has been developed at Yahoo to address these specific
> requirements by
> > providing a hosted service supporting millions of topics for multiple
> tenants.
> > The current incarnation of Pulsar has been open-sourced under Apache
> license
> > in September 2016 and it is the direct evolution of systems that were
> > developed at Yahoo since 2011.
> >
> > We believe there is currently no other system that provides a
> multi-tenant
> > hosted messaging platform capable of supporting a huge number of topics
> while
> > maintaining strict guarantees for durability, ordering and low latency.
> > Current solutions would require to run multiple individual clusters with
> > additional operational work and capacity overhead.
> >
> > Since the open sourcing of Pulsar, the development has been done
> exclusively
> > on the public Github repository and two major releases were shipped
> (1.15 and
> > 1.16), along with multiple minor ones. Several other companies have
> expressed
> > interest in the project and its future direction.
> >
> > == Rationale ==
> >
> > Pulsar is a platform that is built on top of several other Apache
> projects. In
> > particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> > is used for coordination and metadata storage. Pulsar is also
> interoperable
> > out of the box with Apache Storm, to provide an easy to use stream
> processing
> > solution.
> >
> > We want to establish a community outside the scope of initial core
> developers
> > at Yahoo and we believe that the Apache Foundation is a great fit and
> long-
> > term home for Pulsar, as it provides an established process for
> community-
> > driven development and decision making by consensus. This is exactly the
> model
> > we want to adopt for future Pulsar development.
> >
> > == Initial Goals ==
> >
> > The initial goals will be to move the existing codebase to Apache and
> > integrate with the Apache development process. Furthermore, we plan for
> > incremental development, and releases along with the Apache guidelines.
> >
> > == Current Status ==
> >
> > Pulsar has been in service at large scale for more than 2 years at
> Yahoo. In
> > this time around 60 different applications were integrated with Pulsar.
> Other
> > companies are evaluating it as well and have been contributing code to
> the
> > project.
> >
> > === Meritocracy ===
> >
> > We value meritocracy and we understand that it is the basis to form an
> open
> > community that encourages multiple companies and individuals to
> contribute and
> > get invested in the project future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> all
> > contributors.
> >
> > === Community ===
> >
> > We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> > that a reliable hosted pub-sub messaging platform represent a very
> important
> > building block for web-scale distributed applications. We believe that
> many
> > companies can benefit by applying the same model and that bringing
> Pulsar to
> > 

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC11)

[Phil Sorber]

Checksums and signature validate. Builds. +1.

On Mon, Feb 27, 2017 at 9:44 AM Dan Kirkwood  wrote:

> Sorry -- I used the same template as the previous RC..  A couple of
> the descriptions of links above are not accurate,  but the content is
> correct:
>
> The updated documentation can be found here:
> http://trafficcontrol.incubator.apache.org
>
> The source distribution along with checksums and signature (using the
> dang...@apache.org key) is here:
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11/
>
>
>
> On Tue, Feb 21, 2017 at 9:06 AM, Dan Kirkwood  wrote:
> > Hello Incubator PMC,
> >
> > The Apache Traffic Control community has voted on and approved a
> > proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> > kindly request that the Incubator PMC members review and vote on this
> > incubator release.
> >
> > The VOTE RESULT is here:
> >
> >
> https://lists.apache.org/thread.html/dc3ba61d2834579a6e7237df08d828b61011a6cb087e1948be70c78a@%3Cdev.trafficcontrol.apache.org%3E
> >
> > The draft release notes (along with links to artifacts,
> > signatures/checksums, and updated documentation) can be found here:
> >
> > http://trafficcontrol.incubator.apache.org/downloads/
> >
> > The git tag for the repository is "RELEASE-1.8.0-RC11":
> >
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC11
> >
> > The source distribution (also linked in the release notes) is here:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11/
> >
> > Build instructions are included in the BUILD.md file which is included
> > in the source artifact.
> >
> > Artifacts have been signed with the "dang...@apache.org" key listed in:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
> >
> > Please review and vote:
> >
> > [  ] +1 Approve the release
> > [  ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> >
> > - Dan
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Phil Sorber]

+1 (binding)

On Wed, Feb 8, 2017 at 9:28 AM Dan Kirkwood  wrote:

> Minor correction to the previous email -- the artifacts for RC9 are
> located here
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/
> .
>
> Please review this RC and vote..
>
>
>
> The Apache Traffic Control community has voted on and approved a
> proposal to release Apache Traffic Control 1.8.0-incubating. We now
> kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
>
> https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E
>
> The draft release notes can be found here:
> http://trafficcontrol.incubator.apache.org
>
> The git tag for the repository is "RELEASE-1.8.0-RC9":
>
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9
>
> The source distribution is here:
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/
>
> Build instructions are included in the BUILD.md file which is included
> in the source artifact.
>
> Artifacts have been signed with the "dang...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> Please review and vote:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Dan
>
> On Thu, Feb 2, 2017 at 12:38 PM, Dan Kirkwood  wrote:
> > Hello Incubator PMC,
> >
> > The Apache Traffic Control community has voted on and approved a
> > proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> > kindly request that the Incubator PMC members review and vote on this
> > incubator release.
> >
> > The VOTE RESULT is here:
> >
> >
> https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E
> >
> > The draft release notes (along with links to artifacts,
> > signatures/checksums, and updated documentation) can be found here:
> >
> > http://trafficcontrol.incubator.apache.org/downloads/
> >
> > The git tag for the repository is "RELEASE-1.8.0-RC9":
> >
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9
> >
> > The source distribution (also linked in the release notes) is here:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/
> >
> > Build instructions are included in the BUILD.md file which is
> > included in the source artifact.
> >
> > Artifacts have been signed with the "dang...@apache.org" key listed in:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
> >
> > Please review and vote:
> >
> > [  ] +1 Approve the release
> > [  ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> >
> > - Dan
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Policy Question: GA for GitHub for Podlings

[Phil Sorber]

Reading the other thread on this it seems it has not yet. Let me know if
any external to infra help is wanted.

Thanks.

On Mon, Nov 7, 2016, 16:29 Phil Sorber <sor...@apache.org> wrote:

> I am +1 on both as well. My understanding is that there was an LDAP
> hurdle. Has that been resolved?
>
> On Mon, Nov 7, 2016, 15:24 Chris Mattmann <mattm...@apache.org> wrote:
>
> Hi,
>
> As some of you may have seen the OpenWhisk podling being discussed now has
> requested to use GitHub as its primary master. Greg Stein our ASF Infra
> Admin
> has OK’ed this for OpenWhisk iff the IPMC is OK with it.
>
> I ask now:
>
> 1. Is the IPMC OK with this for OpenWhisk?
> 2. Is the IPMC OK with this in general availability for Podlings?
>
> I am +1 on both (IPMC hat on).
>
> Thanks.
>
> Cheers,
> Chris
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Policy Question: GA for GitHub for Podlings

[Phil Sorber]

I am +1 on both as well. My understanding is that there was an LDAP hurdle.
Has that been resolved?

On Mon, Nov 7, 2016, 15:24 Chris Mattmann  wrote:

> Hi,
>
> As some of you may have seen the OpenWhisk podling being discussed now has
> requested to use GitHub as its primary master. Greg Stein our ASF Infra
> Admin
> has OK’ed this for OpenWhisk iff the IPMC is OK with it.
>
> I ask now:
>
> 1. Is the IPMC OK with this for OpenWhisk?
> 2. Is the IPMC OK with this in general availability for Podlings?
>
> I am +1 on both (IPMC hat on).
>
> Thanks.
>
> Cheers,
> Chris
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Traffic Control Incubator Code Grant next steps

[Phil Sorber]

Great, thanks!

On Wed, Oct 5, 2016 at 11:33 PM Craig Russell <craig.russ...@oracle.com>
wrote:

> Hi Phil,
>
>
> > On Oct 5, 2016, at 9:51 AM, Phil Sorber <sor...@apache.org> wrote:
> >
> > So we now have CCLA's on file from all contributing corps as well as
> ICLA's from all individual contributors. Have we satisfied the requirements
> to make a release from the incubator or are there still additional steps
> like an IP Clearance vote?
>
> There is no separate IP clearance vote needed for incubator releases. If
> the code is ready to go, prepare a release and follow the incubator vote
> procedure. The cover page for the project should be updated with the IP
> clearance. You can put it in the Copyright section.
>
> > I've seen those threads, but they look like code grants to existing
> projects so it wasn't clear if that was required or not.
>
> IP clearance is part of the normal incubating process, and there is a
> separate, special IP clearance process for non-incubating projects.
>
> Craig
> >
> > Thanks.
>
> Craig L Russell
> c...@apache.org
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Traffic Control Incubator Code Grant next steps

[Phil Sorber]

So we now have CCLA's on file from all contributing corps as well as ICLA's
from all individual contributors. Have we satisfied the requirements to
make a release from the incubator or are there still additional steps like
an IP Clearance vote? I've seen those threads, but they look like code
grants to existing projects so it wasn't clear if that was required or not.

Thanks.

wiki write access for PhilSorber

[Phil Sorber]

Hi all, can you grant karma to "PhilSorber" to edit the incubator
wiki?

Thanks.

Re: [VOTE] Accept Traffic Control into the Apache Incubator

[Phil Sorber]

ackage 'Crypt::OpenSSL::Random'
>   *  CPAN package 'Net::DNS::SEC::Private'
>   *  CPAN package 'LWP::Protocol::https'
>   *  CPAN package 'Net::CIDR'
>   *  CPAN package 'Data::Validate::IP'
>
> == Cryptography ==
>
> There is no cryptographic code in Traffic Control. We leverage OpenSSL for
> all our cryptography needs.
>
> == Required Resources ==
>
> === Mailing lists ===
>
> We currently use "google groups" to communicate, but we would like to move
> that
> to ASF maintained mailing lists.
>
> Current groups / mailing lists:
>  * https://groups.google.com/forum/#!forum/traffic_control
>  * https://groups.google.com/forum/#!forum/traffic_control-announce
>  * https://groups.google.com/forum/#!forum/traffic_control-discuss
>
> Proposed ASF maintained lists:
>  * priv...@traffic-control.incubator.apache.org (moderated subscriptions)
>  * d...@traffic-control.incubator.apache.org
>  * comm...@traffic-control.incubator.apache.org
>  * notificati...@traffic-control.incubator.apache.org
>  * us...@traffic-control.incubator.apache.org
>
> === Subversion Directory ===
>
> We do not use SVN for source code revision control.
>
> === Git Repository ===
>
> We would like to use git-wip (git://git.apache.org/traffic_control.git).
>
>
> === Issue Tracking ===
>
> JIRA.
>
> === Other Resources ===
>
> We have automated tests and continuous integration configurations we would
> like
> to move away from Comcast.
>
> == Initial Committers ==
>
>  * Dan Kirkwood (dangogh at gmail.com)
>  * David Neuman (david.neuman64 at gmail.com)
>  * Dewayne Richardson (dewrich at gmail.com)
>  * Eric Friedrich (eric.friedrich84 at gmail.com)
>  * Hank Beatty (Hank.Beatty at cox.com)
>  * Jackie Heitzer (jackieheitzer at gmail.com)
>  * Jan van Doorn (jvd at knutsel.com)
>  * Jeff Elsloo (jeff.elsloo at gmail.com)
>  * Jeremy Mitchell (mitchell852 at gmail.com)
>  * Mark Torluemke (mark at torluemke.net)
>  * Steve Malenfant (steve.malenfant at cox.com)
>
> == Affiliations ==
>
>  * Comcast Cable: Dan Kirkwood, David Neuman, Dewayne Richardson, Jackie
> Heitzer,
>  Jan van Doorn, Jeff Elsloo, Jeremy Mitchell, Mark Torluemke
>
>  * Cox Communications: Hank Beatty, Steve Malenfant
>
>  * Cisco: Eric Friedrich
>
> == Sponsors ==
>
> === Champion ===
>
>  * Leif Hedstrom (zwoop at apache.org)
>
> === Nominated Mentors ===
>
>  * Phil Sorber (sorber at apache.org)
>  * Eric Covener (covener at apache.org)
>  * Daniel Gruno (humbedooh at apache.org)
>  * J. Aaron Farr (farra at apache.org)
>
> === Sponsoring Entity ===
>
> We request the Apache Incubator to sponsor this project.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>