Re: Updating XML status pages

[John D. Ament]

Yes, as mentioned at
https://incubator.apache.org/guides/website.html#building they're built
daily, otherwise you can manually trigger in Jenkins.

On Mon, Jul 17, 2017 at 4:15 PM Jim Apple  wrote:

> http://incubator.apache.org/guides/website.html says:
>
> "Podling status files are maintained in SVN, and you should continue to
> maintain them at
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/";
>
> Are those updated XML files ever published automatically? As of a few
> months ago, we had to use https://cms.apache.org/incubator/publish?diff=1
>

Re: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

On Mon, Jul 17, 2017 at 10:29 AM sebb  wrote:

> On 17 July 2017 at 02:54, John D. Ament  wrote:
> > On Sun, Jul 16, 2017 at 7:34 PM sebb  wrote:
> >
> >> On 16 July 2017 at 23:25, John D. Ament  wrote:
> >> > On Sun, Jul 16, 2017 at 5:32 PM sebb  wrote:
> >> >
> >> >> On 16 July 2017 at 21:22, John D. Ament 
> wrote:
> >> >> > Sebb,
> >> >> >
> >> >> > I have no particular issue with including the file, and I'm not
> sure
> >> why
> >> >> > you think I or anyone else would.  This is not the canonical path
> for
> >> >> > podlings.xml though, and may be out of date.  My recommendation is
> to
> >> do
> >> >> a
> >> >> > 302 to the right location, so that consumers are always getting the
> >> >> latest
> >> >> > but I know not all tools can follow 302's.  If there are tools out
> >> there
> >> >> > that need it, and you want to make those tools get it from this
> >> >> location, I
> >> >> > have no issue with you committing your proposed change to the
> website
> >> >> > repo.  I would recommend that we also include the .dtd and .xsl
> files
> >> as
> >> >> > well.
> >> >>
> >> >> A redirect (or 3) may be sufficient.
> >> >> What definitely needs to be avoided is a 404.
> >> >>
> >> >
> >> > Infra have updated the scripts on eos to point to SVN.
> >>
> >> It's either not working or has not yet been deployed:
> >>
> >> $ curl -I http://incubator.apache.org/podlings.xml
> >> HTTP/1.1 404 Not Found
> >> Date: Sun, 16 Jul 2017 23:27:40 GMT
> >> Server: Apache/2.4.18 (Ubuntu)
> >> Content-Type: text/html; charset=iso-8859-1
> >>
> >>
> > That is correct.  As I mentioned before, please feel free to commit a
> > change.
>
> I updated .htaccess.; that built OK.
> I then triggered a build of the Jenkins job; that also built OK.
>
> It looks like the .htaccess file is not being picked up from SVN.
> Instead it seems to be copied from the assets/ directory in Git.
>
> As already mentioned, I don't have karma to update that.
>
>
Please review - https://incubator.apache.org/guides/website.html

I'd like to understand why you think you don't have karma to update that.
All incubator committers have write access to this repo.

John


> ==
>
> If the .htaccess file in SVN is no longer relevant, this should be
> noted in comments in the file.
> However I think it would be better to edit the build_site.sh file to
> pick up the correct file from SVN, and drop the one under assets/
>
> Note: I don't have time to fix this now.
>
> >
> >> >
> >> > If you know of other tools, please speak up.
> >>
> >> >>
> >> >> > John
> >> >> >
> >> >> > On Sun, Jul 16, 2017 at 8:02 AM sebb  wrote:
> >> >> >
> >> >> >> On 16 July 2017 at 11:47, John D. Ament 
> >> wrote:
> >> >> >> > Each of those services should be reading the file from SVN
> >> locations,
> >> >> >> e.g.
> >> >> >> >
> >> >> >>
> >> >>
> >>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
> >> >> >>
> >> >> >> Perhaps they should, but the fact is that the URL
> >> >> >>
> >> >> >> http://incubator.apache.org/podlings.xml
> >> >> >>
> >> >> >> used to work. And I'm fairly sure it used to be advertised
> somewhere.
> >> >> >>
> >> >> >> It's trivial to fix, so why not fix it?
> >> >> >>
> >> >> >> > You can see it being done correctly in whimsy here:
> >> >> >> >
> >> >> >>
> >> >>
> >>
> https://github.com/apache/whimsy/blob/ed8acc34dff71ef811b2e11312866c2d1f971b67/www/incubator/moderators.cgi
> >> >> >> > (though
> >> >> >> > the link in the README is wrong)
> >> >> >> >
> >> >> >> > John
> >> >> >> >
> >> >> >> > On Sun, Jul 16, 2017 at 4:49 AM sebb  wrote:
> >> >> >> >
> >>

Re: Help please

[John D. Ament]

Specifically you'd want to follow the proposal guide [1], find a champion.
That probably means you're sharing an abstract of your proposal here on
list if you don't know someone personally at the ASF.

[1]: https://incubator.apache.org/guides/proposal.html


On Mon, Jul 17, 2017 at 2:52 AM Harrison & Wells 
wrote:

> Thanks guys!
>
> On Mon, Jul 17, 2017 at 12:19 PM, Greg Stein  wrote:
>
> > general@ is just fine...
> >
> > On Mon, Jul 17, 2017 at 1:47 AM, Harrison & Wells <
> rahul29112...@gmail.com
> > >
> > wrote:
> >
> > > Guys, I need your help.If I wanted to send a proposal to the incubator
> > > committee, whom do I send it to? The general mailing list?Or is there a
> > > special one?It's quite confusing.
> > > Thanks!
> > >
> >
>

Re: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

On Sun, Jul 16, 2017 at 7:34 PM sebb  wrote:

> On 16 July 2017 at 23:25, John D. Ament  wrote:
> > On Sun, Jul 16, 2017 at 5:32 PM sebb  wrote:
> >
> >> On 16 July 2017 at 21:22, John D. Ament  wrote:
> >> > Sebb,
> >> >
> >> > I have no particular issue with including the file, and I'm not sure
> why
> >> > you think I or anyone else would.  This is not the canonical path for
> >> > podlings.xml though, and may be out of date.  My recommendation is to
> do
> >> a
> >> > 302 to the right location, so that consumers are always getting the
> >> latest
> >> > but I know not all tools can follow 302's.  If there are tools out
> there
> >> > that need it, and you want to make those tools get it from this
> >> location, I
> >> > have no issue with you committing your proposed change to the website
> >> > repo.  I would recommend that we also include the .dtd and .xsl files
> as
> >> > well.
> >>
> >> A redirect (or 3) may be sufficient.
> >> What definitely needs to be avoided is a 404.
> >>
> >
> > Infra have updated the scripts on eos to point to SVN.
>
> It's either not working or has not yet been deployed:
>
> $ curl -I http://incubator.apache.org/podlings.xml
> HTTP/1.1 404 Not Found
> Date: Sun, 16 Jul 2017 23:27:40 GMT
> Server: Apache/2.4.18 (Ubuntu)
> Content-Type: text/html; charset=iso-8859-1
>
>
That is correct.  As I mentioned before, please feel free to commit a
change.


> >
> > If you know of other tools, please speak up.
>
> >>
> >> > John
> >> >
> >> > On Sun, Jul 16, 2017 at 8:02 AM sebb  wrote:
> >> >
> >> >> On 16 July 2017 at 11:47, John D. Ament 
> wrote:
> >> >> > Each of those services should be reading the file from SVN
> locations,
> >> >> e.g.
> >> >> >
> >> >>
> >>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
> >> >>
> >> >> Perhaps they should, but the fact is that the URL
> >> >>
> >> >> http://incubator.apache.org/podlings.xml
> >> >>
> >> >> used to work. And I'm fairly sure it used to be advertised somewhere.
> >> >>
> >> >> It's trivial to fix, so why not fix it?
> >> >>
> >> >> > You can see it being done correctly in whimsy here:
> >> >> >
> >> >>
> >>
> https://github.com/apache/whimsy/blob/ed8acc34dff71ef811b2e11312866c2d1f971b67/www/incubator/moderators.cgi
> >> >> > (though
> >> >> > the link in the README is wrong)
> >> >> >
> >> >> > John
> >> >> >
> >> >> > On Sun, Jul 16, 2017 at 4:49 AM sebb  wrote:
> >> >> >
> >> >> >> The podlings.xml file used to be available from
> >> >> >>
> >> >> >> http://incubator.apache.org/podlings.xml
> >> >> >>
> >> >> >> Also the related .dtd and .xsl were there.
> >> >> >>
> >> >> >> These URLs need to be restored as 3rd parties (such as Whimsy) use
> >> them.
> >> >> >>
> >> >> >>
> >> >> >> On 13 July 2017 at 02:50, John D. Ament 
> >> wrote:
> >> >> >> > All,
> >> >> >> >
> >> >> >> > The website has been migrated.  Apologies for any spam on the
> cvs
> >> list
> >> >> >> > while we were committing things.
> >> >> >> >
> >> >> >> > Please feel free to review the website guide for how to use the
> new
> >> >> >> website
> >> >> >> > - https://incubator.apache.org/guides/website.html .
> >> >> >> >
> >> >> >> > I'll begin content editing within a few days.
> >> >> >> >
> >> >> >> > John
> >> >> >> >
> >> >> >> > On Mon, Jul 10, 2017 at 12:51 PM John D. Ament <
> >> johndam...@apache.org
> >> >> >
> >> >> >> > wrote:
> >> >> >> >
> >> >> >> >> All,
> >> >> >> >>
> >> >> >> >> Just as a heads up we will be migrating to the new Incubator
> >> website
> >> >> >> >> Wednesday night, 9pm Eastern.  I expect during this time some
> >> links
> >> >> may
> >> >> >> >> break and other stuff not work quite right.  Please be patient
> and
> >> >> shout
> >> >> >> >> out when you see something.
> >> >> >> >>
> >> >> >> >> John
> >> >> >> >>
> >> >> >>
> >> >> >>
> -
> >> >> >> 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
> >> >>
> >> >>
> >>
> >> -
> >> 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: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

On Sun, Jul 16, 2017 at 5:32 PM sebb  wrote:

> On 16 July 2017 at 21:22, John D. Ament  wrote:
> > Sebb,
> >
> > I have no particular issue with including the file, and I'm not sure why
> > you think I or anyone else would.  This is not the canonical path for
> > podlings.xml though, and may be out of date.  My recommendation is to do
> a
> > 302 to the right location, so that consumers are always getting the
> latest
> > but I know not all tools can follow 302's.  If there are tools out there
> > that need it, and you want to make those tools get it from this
> location, I
> > have no issue with you committing your proposed change to the website
> > repo.  I would recommend that we also include the .dtd and .xsl files as
> > well.
>
> A redirect (or 3) may be sufficient.
> What definitely needs to be avoided is a 404.
>

Infra have updated the scripts on eos to point to SVN.  If you know of
other tools, please speak up.


>
> > John
> >
> > On Sun, Jul 16, 2017 at 8:02 AM sebb  wrote:
> >
> >> On 16 July 2017 at 11:47, John D. Ament  wrote:
> >> > Each of those services should be reading the file from SVN locations,
> >> e.g.
> >> >
> >>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
> >>
> >> Perhaps they should, but the fact is that the URL
> >>
> >> http://incubator.apache.org/podlings.xml
> >>
> >> used to work. And I'm fairly sure it used to be advertised somewhere.
> >>
> >> It's trivial to fix, so why not fix it?
> >>
> >> > You can see it being done correctly in whimsy here:
> >> >
> >>
> https://github.com/apache/whimsy/blob/ed8acc34dff71ef811b2e11312866c2d1f971b67/www/incubator/moderators.cgi
> >> > (though
> >> > the link in the README is wrong)
> >> >
> >> > John
> >> >
> >> > On Sun, Jul 16, 2017 at 4:49 AM sebb  wrote:
> >> >
> >> >> The podlings.xml file used to be available from
> >> >>
> >> >> http://incubator.apache.org/podlings.xml
> >> >>
> >> >> Also the related .dtd and .xsl were there.
> >> >>
> >> >> These URLs need to be restored as 3rd parties (such as Whimsy) use
> them.
> >> >>
> >> >>
> >> >> On 13 July 2017 at 02:50, John D. Ament 
> wrote:
> >> >> > All,
> >> >> >
> >> >> > The website has been migrated.  Apologies for any spam on the cvs
> list
> >> >> > while we were committing things.
> >> >> >
> >> >> > Please feel free to review the website guide for how to use the new
> >> >> website
> >> >> > - https://incubator.apache.org/guides/website.html .
> >> >> >
> >> >> > I'll begin content editing within a few days.
> >> >> >
> >> >> > John
> >> >> >
> >> >> > On Mon, Jul 10, 2017 at 12:51 PM John D. Ament <
> johndam...@apache.org
> >> >
> >> >> > wrote:
> >> >> >
> >> >> >> All,
> >> >> >>
> >> >> >> Just as a heads up we will be migrating to the new Incubator
> website
> >> >> >> Wednesday night, 9pm Eastern.  I expect during this time some
> links
> >> may
> >> >> >> break and other stuff not work quite right.  Please be patient and
> >> shout
> >> >> >> out when you see something.
> >> >> >>
> >> >> >> John
> >> >> >>
> >> >>
> >> >> -
> >> >> 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
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

Sebb,

I have no particular issue with including the file, and I'm not sure why
you think I or anyone else would.  This is not the canonical path for
podlings.xml though, and may be out of date.  My recommendation is to do a
302 to the right location, so that consumers are always getting the latest
but I know not all tools can follow 302's.  If there are tools out there
that need it, and you want to make those tools get it from this location, I
have no issue with you committing your proposed change to the website
repo.  I would recommend that we also include the .dtd and .xsl files as
well.

John

On Sun, Jul 16, 2017 at 8:02 AM sebb  wrote:

> On 16 July 2017 at 11:47, John D. Ament  wrote:
> > Each of those services should be reading the file from SVN locations,
> e.g.
> >
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>
> Perhaps they should, but the fact is that the URL
>
> http://incubator.apache.org/podlings.xml
>
> used to work. And I'm fairly sure it used to be advertised somewhere.
>
> It's trivial to fix, so why not fix it?
>
> > You can see it being done correctly in whimsy here:
> >
> https://github.com/apache/whimsy/blob/ed8acc34dff71ef811b2e11312866c2d1f971b67/www/incubator/moderators.cgi
> > (though
> > the link in the README is wrong)
> >
> > John
> >
> > On Sun, Jul 16, 2017 at 4:49 AM sebb  wrote:
> >
> >> The podlings.xml file used to be available from
> >>
> >> http://incubator.apache.org/podlings.xml
> >>
> >> Also the related .dtd and .xsl were there.
> >>
> >> These URLs need to be restored as 3rd parties (such as Whimsy) use them.
> >>
> >>
> >> On 13 July 2017 at 02:50, John D. Ament  wrote:
> >> > All,
> >> >
> >> > The website has been migrated.  Apologies for any spam on the cvs list
> >> > while we were committing things.
> >> >
> >> > Please feel free to review the website guide for how to use the new
> >> website
> >> > - https://incubator.apache.org/guides/website.html .
> >> >
> >> > I'll begin content editing within a few days.
> >> >
> >> > John
> >> >
> >> > On Mon, Jul 10, 2017 at 12:51 PM John D. Ament  >
> >> > wrote:
> >> >
> >> >> All,
> >> >>
> >> >> Just as a heads up we will be migrating to the new Incubator website
> >> >> Wednesday night, 9pm Eastern.  I expect during this time some links
> may
> >> >> break and other stuff not work quite right.  Please be patient and
> shout
> >> >> out when you see something.
> >> >>
> >> >> John
> >> >>
> >>
> >> -
> >> 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: Mainlinglist archive down?

[John D. Ament]

Did you try lists.apache.org ?

John

On Sun, Jul 16, 2017 at 2:57 PM Oliver B. Fischer 
wrote:

> Hi,
>
> is the archive of our mailing lists down?
> (http://mail-archives.apache.org/mod_mbox/) I get only a while page.
>
> Does anyone knows more?
>
> Oliver
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251 <+49%2030%2044793251>
> M +49 178 7903538 <+49%20178%207903538>
> E o.b.fisc...@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fisc...@jabber.org
> X http://xing.to/obf
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

Each of those services should be reading the file from SVN locations, e.g.
http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml

You can see it being done correctly in whimsy here:
https://github.com/apache/whimsy/blob/ed8acc34dff71ef811b2e11312866c2d1f971b67/www/incubator/moderators.cgi
(though
the link in the README is wrong)

John

On Sun, Jul 16, 2017 at 4:49 AM sebb  wrote:

> The podlings.xml file used to be available from
>
> http://incubator.apache.org/podlings.xml
>
> Also the related .dtd and .xsl were there.
>
> These URLs need to be restored as 3rd parties (such as Whimsy) use them.
>
>
> On 13 July 2017 at 02:50, John D. Ament  wrote:
> > All,
> >
> > The website has been migrated.  Apologies for any spam on the cvs list
> > while we were committing things.
> >
> > Please feel free to review the website guide for how to use the new
> website
> > - https://incubator.apache.org/guides/website.html .
> >
> > I'll begin content editing within a few days.
> >
> > John
> >
> > On Mon, Jul 10, 2017 at 12:51 PM John D. Ament 
> > wrote:
> >
> >> All,
> >>
> >> Just as a heads up we will be migrating to the new Incubator website
> >> Wednesday night, 9pm Eastern.  I expect during this time some links may
> >> break and other stuff not work quite right.  Please be patient and shout
> >> out when you see something.
> >>
> >> John
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

HORN retirement question

[John D. Ament]

All,

For podlings so far, its been easy to decide how to retire them.  They've
had releases and/or naming completed so we keep the source code around.

HORN has neither a release nor naming.

Should we delete the source repos or mark them as read only?

John

Re: svn commit: r1801913 - /incubator/public/trunk/content/projects/mxnet.xml

[John D. Ament]

As long as you are correctly maintaining roster in whimsy, you don't need
to update the project status with roster as well.

John

On Fri, Jul 14, 2017 at 4:07 AM  wrote:

> Author: bayard
> Date: Fri Jul 14 08:07:11 2017
> New Revision: 1801913
>
> URL: http://svn.apache.org/viewvc?rev=1801913&view=rev
> Log:
> Adding 3 missing committers
>
> Modified:
> incubator/public/trunk/content/projects/mxnet.xml
>
> Modified: incubator/public/trunk/content/projects/mxnet.xml
> URL:
> http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/mxnet.xml?rev=1801913&r1=1801912&r2=1801913&view=diff
>
> ==
> --- incubator/public/trunk/content/projects/mxnet.xml [utf-8] (original)
> +++ incubator/public/trunk/content/projects/mxnet.xml [utf-8] Fri Jul 14
> 08:07:11 2017
> @@ -215,6 +215,21 @@
>lxn2
>Ly Nguyen
>  
> +
> +  .
> +  yajiedesign
> +  Shiwen Hu
> +
> +
> +  .
> +  jianzhangzju
> +  Jian Zhang
> +
> +
> +  .
> +  terrychen
> +  Terry Chen
> +
>
>  
>  
>
>
>
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
>
>

Re: Hawq trademarks?

[John D. Ament]

Ted,

Was this for the hawq list or the incubator list?  It appears that there is
an open PNS https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-83

John

On Thu, Jul 13, 2017 at 4:46 PM Ted Dunning  wrote:

> We had a recent problem with Madlib graduating due to lack of progress on
> trademark assignment.
>
> I suspect that Hawq will find itself in the same situation as it gets
> closer to graduation.
>
> What is the situation with the Hawq trademark? Has the transfer process
> been started?
>
> http://www.trademarkia.com/hawq-86117685.html
>

[RESULT] Retire HORN

[John D. Ament]

With 5 binding +1's and 1 non-binding +1 the vote to retire HORN passes.
I'll take care of the next steps.

On Mon, Jul 10, 2017 at 1:39 AM Raphael Bircher 
wrote:

> +1 (binding)
>
> Am .07.2017, 14:53 Uhr, schrieb John D. Ament :
>
> > All,
> >
> > After a few discussions on list, its been agreed to retire the HORN
> > podling.
> >
> > - The podling recently voted to retire [1]
> > - Back in April I asked for their status, where a public discussion
> > occurred with others stating they had no time for the project.
> > - Recently started a discussion, where it was agreed [3]
> >
> > At this point, I am asking the IPMC to vote to retire HORN.
> >
> > [ ] +1 to retire
> > [ ] -1 don't retire because...
> >
> > Here is my own +1.
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/9cec83d3a648c7746f5df0936798b4e533fe74ded7bc4eead8611d30@%3Cdev.horn.apache.org%3E
> > [2]:
> >
> https://lists.apache.org/thread.html/200eba59f8de9e0df220ef7c3d1c65e877d2cc8f480d6e89279fd810@%3Cdev.horn.apache.org%3E
> > [3]:
> >
> https://lists.apache.org/list.html?d...@horn.apache.org:gte=1d:discuss%20retire%20horn
>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] publish ariatosca 0.1.1

[John D. Ament]

+1 release contents look good, signatures fine.

Minor nit: don't send to both general@ and dev@.  It confuses the vote.

On Thu, Jul 13, 2017 at 10:33 AM Ran Ziv  wrote:

> The ariatosca community voted on and has approved a proposal to release
> ariatosca 0.1.1.
> Pursuant to the Releases section of the Incubation Policy and with the
> endorsement of our mentors, we would now like to request the permission of
> the Incubator PMC to publish the tarball on Apache's /dist/release.
>
>
> Proposal:
> https://lists.apache.org/thread.html/b0571ee44c5f5bb325cc7f4
> 9e475e3219c5ca89d78d22a3ac203a77c@%3Cdev.ariatosca.apache.org%3E
>
>
> Vote result:
>
> https://lists.apache.org/thread.html/a2271fa86a2d0d9926a53c165b9a8a50218d12ca01a651bdd0af5122@%3Cdev.ariatosca.apache.org%3E
>
>
> Release candidate package may be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.1-incubating/
> The "source" directory contains the actual source snapshot as required per
> an Apache release.
> the "sdist" and "bdist" directories are Pythonic source and binary
> distributions, to be uploaded on PyPI upon a successful vote.
>
> See more information about the package in the original proposal thread.
>
>
>
> Please vote by Sunday, July 16th, at 14:00 UTC.
>
>
> Thanks,
> Ran
>

Re: [NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

All,

The website has been migrated.  Apologies for any spam on the cvs list
while we were committing things.

Please feel free to review the website guide for how to use the new website
- https://incubator.apache.org/guides/website.html .

I'll begin content editing within a few days.

John

On Mon, Jul 10, 2017 at 12:51 PM John D. Ament 
wrote:

> All,
>
> Just as a heads up we will be migrating to the new Incubator website
> Wednesday night, 9pm Eastern.  I expect during this time some links may
> break and other stuff not work quite right.  Please be patient and shout
> out when you see something.
>
> John
>

Re: [VOTE] Recommend Apache Fluo graduation as TLP to Board

[John D. Ament]

+1

On Mon, Jul 10, 2017 at 4:44 PM Christopher  wrote:

> Hello IPMC,
>
> The recent DISCUSS thread on the topic of Fluo's graduation has been open
> for at least 72 hours, and I believe all questions have been answered and
> issues addressed at this point.
>
> With the discussion having settled down, I would now like to call for a
> recommendation VOTE to present the ASF board with the following resolution
> to graduate from incubation and establish Apache Fluo as a top-level
> project (TLP).
>
> Incubator DISCUSS thread:
>
> https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E
> Fluo PPMC DISCUSS thread:
>
> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
> Fluo PPMC internal VOTE thread:
>
> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
> Fluo Podling Status page: https://incubator.apache.org/projects/fluo
>
> Please vote on whether to recommend the following graduation resolution to
> the ASF Board.
>
> [  ]  +1, In favor of recommending the following graduation resolution to
> the ASF Board to establish Apache Fluo as a TLP
> [  ]  +0, Neither opposed to, nor in favor of, recommending the following
> graduation resolution to the Board
> [  ]  -1, Opposed to recommending the following graduation resolution to
> the Board
>
> This VOTE will be open for at least 72 hours.
>
> ***Resolution:
>
> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Fluo Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
> the creation and maintenance of software related to the storage and
> incremental processing of large data sets; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Fluo 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 Fluo Project:
>
> * Billie Rinaldi 
> * Chris McTague 
> * Christopher Tubbs 
> * Corey J. Nolet 
> * Drew Farris 
> * Josh Elser 
> * Keith Turner 
> * Mike Walch 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
> to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
> further
>
> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Fluo podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: Re: [RESULT][VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[John D. Ament]

Also, please note that I did not cast a vote on this release.  I agreed
with Roman's sentiments on needed proper NOTICE/LICENSE/DISCLAIMER for the
RPMs, but did not get a chance to review the release contents.

John

On Tue, Jul 11, 2017 at 3:48 AM Ruilong Huo  wrote:

> Thanks Julian for the clarification!
>
> Checked that: 1) Roman Shaposhnik; 2) John D. Ament; 3) Justin Mclean; 4)
> Alan Gates, are all PMC member of incubator.
> I have sent another email with their IPMC vote as binding vote for Apache
> HAWQ 2.2.0.0-incubating release.
>
>
> Best regards,
> Ruilong Huo
>
>
> At 2017-07-11 12:21:13, "Julian Hyde"  wrote:
> >Ruilong (and others),
> >
> >If in doubt, look people up at https://people.apache.org/phonebook.html <
> https://people.apache.org/phonebook.html>. If a voter’s page has “PMC
> member of … incubator” then their vote is binding.
> >
> >E.g. https://people.apache.org/phonebook.html?uid=jmclean <
> https://people.apache.org/phonebook.html?uid=jmclean>
> >
> >Julian
> >
> >
> >> On Jul 10, 2017, at 8:50 PM, Justin Mclean 
> wrote:
> >>
> >> Hi,
> >>
> >>> There was only one explicit +1 binding vote from you and others are
> just +1. So I thought they were non-binding vote:)
> >>
> >> In which case (if they were non binding votes) the vote would not of
> passed as you need 3 +1 binding votes and more +1’s than -1’s to pass.
> >>
> >> Thanks,
> >> Justin
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
>

[NOTICE] Migrating to the new Incubator Website Wednesday night

[John D. Ament]

All,

Just as a heads up we will be migrating to the new Incubator website
Wednesday night, 9pm Eastern.  I expect during this time some links may
break and other stuff not work quite right.  Please be patient and shout
out when you see something.

John

Re: [VOTE] Graduate Apache Streams project from Incubator

[John D. Ament]

+1

On Mon, Jul 10, 2017 at 11:28 AM sblackmon  wrote:

>
> In concert with the discussion started last week [1], please vote on the
> draft resolution which establishes Apache Streams as a new top-level
> project at the Apache Software Foundation, as follows:
>
> [ ] +1, Graduate Apache Streams from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache Streams from the Incubator (provide details)
>
> The full text of the resolution is below.
>
> If approved by the Apache Incubator PMC members, the proposed resolution
> will be submitted to the Board of Directors for their consideration.
>
> Thanks !
>
> [1]
> https://lists.apache.org/thread.html/60d676ad7b190323f8479bccff8ae996f98bf5fcd0d0ff4d54b71006@
> 
>
> Establish the Apache Streams 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 interoperability of online profiles and activity feeds.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Streams Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Streams Project be and hereby is responsible for
> the creation and maintenance of software related to interoperability of
> online profiles and activity feeds; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Streams" 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 Streams Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Streams 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 Streams Project:
>
>  * Stephen D Blackmon   
>  * Robert Baker Douglas 
>  * Ate Douma
>  * Ryan Edward Ebanks   
>  * Matt Franklin
>  * Joey Frazee  
>  * Trevor Grant 
>  * Suneel Marthi
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen D Blackmon be
> appointed to the office of Vice President, Apache Streams, 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 Streams 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 Streams Project; and be it further
>
> RESOLVED, that the Apache Streams Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Streams podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Streams 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
>
>

[DRAFT] Incubator PMC Board Report - July 2017

[John D. Ament]

 SQL
   engine that can run native to the container cloud platform).

   Release information:

   1) Release page:

https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release

   2) Issues/tasks fixed (80):
  https://issues.apache.org/jira/issues/?filter=12339844

2. Per project mentor guidance, the Apache Incubator logo has
   been applied to the project's website (http://hawq.incubator.apache.org/)
   and wiki (
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+Home).

3. Per project mentor guidance, an incubator project logo was
   created and voted on. It has been applied to the projet's wiki:
   https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+Home

4. To encourage more doc contributions, a discussions took place
   on dev/user mail lists to recommend moving the HAWQ doc
   repository (https://github.com/apache/incubator-hawq-docs
   master branch) into the HAWQ source
   repository (https://github.com/apache/incubator-hawq).

5. Project mail list activity:

   Between Sat Apr 01 2017 and Fri Jun 30 2017:

   d...@hawq.apache.org
 337 emails sent
 147 topics started
 87  participants

   u...@hawq.apache.org
 78  emails sent
 24  topics started
 35  participants

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-02-28, Apache HAWQ 2.1.0.0

When were the last committers or PPMC members elected?

  Podling committers (1) added:
Xiang Sheng (https://github.com/stanlyxiang), May 16, 2017

Signed-off-by:

  [X](hawq) Alan Gates
 Comments:
  [ ](hawq) Konstantin Boudnik
 Comments:
  [ ](hawq) Justin Erenkrantz
 Comments:
  [ ](hawq) Thejas Nair
 Comments:
  [ ](hawq) Roman Shaposhnik
 Comments:

IPMC/Shepherd notes:



Juneau

Apache Juneau is a toolkit for marshalling POJOs to a wide variety of
content
types using a common framework, and for creating sophisticated self-
documenting REST interfaces and microservices using VERY little code.

Juneau has been incubating since 2016-06-24.

Three most important issues to address in the move towards graduation:

  1. Build up community with non-IBM and non-Salesforce contributors.
  2. Solicit user feedback/usage
  3. Grow awareness of the project

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None.

How has the community developed since the last report?

  The Juneau community continues collaborating with the Apache Streams
  team and have come up with significant new enhancements from the
  effort.

How has the project developed since the last report?

  6.2.0 major release delivered on Apr 28, 2017.
  6.3.0 major release delivered on Jun 28, 2017.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-06-28

When were the last committers or PPMC members elected?

  - Initial committers only.

Signed-off-by:

  [X](juneau) Craig Russell
 Comments: I'm ambivalent about the use of Slack as a communications
channel. While it's great for just-in-time discussion, it's not visible to
the dev list (the digests are of no value). Juneau is mostly a one-man show
and I'm hopeful that others will join the project.
  [ ](juneau) Jochen Wiedmann
 Comments:
  [X](juneau) John D. Ament
 Comments:  The podling is struggling a bit with community growth and
public communication.  While we've opened up Slack as a communication
channel and it has led to some external contribution, we need to figure out
how to get more communication happening on list and how to get more outside
contributors.

IPMC/Shepherd notes:




Livy

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important issues to address in the move towards graduation:

N/A

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

N/A

How has the community developed since the last report?

The community is working on moving the project to Apache.

How has the project developed since the last report?

N/A

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

N/A

Signed-off-by:

  [ ](livy) Bikas 

[VOTE] Retire HORN

[John D. Ament]

All,

After a few discussions on list, its been agreed to retire the HORN
podling.

- The podling recently voted to retire [1]
- Back in April I asked for their status, where a public discussion
occurred with others stating they had no time for the project.
- Recently started a discussion, where it was agreed [3]

At this point, I am asking the IPMC to vote to retire HORN.

[ ] +1 to retire
[ ] -1 don't retire because...

Here is my own +1.

[1]:
https://lists.apache.org/thread.html/9cec83d3a648c7746f5df0936798b4e533fe74ded7bc4eead8611d30@%3Cdev.horn.apache.org%3E
[2]:
https://lists.apache.org/thread.html/200eba59f8de9e0df220ef7c3d1c65e877d2cc8f480d6e89279fd810@%3Cdev.horn.apache.org%3E
[3]:
https://lists.apache.org/list.html?d...@horn.apache.org:gte=1d:discuss%20retire%20horn

Re: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

Will the podling be progressing on a vote in time for the next board report
(7/19)? Please make sure you draft your proposal.  You can take a sample
draft from https://whimsy.apache.org/roster/ppmc/fluo (it's all the way at
the bottom)

On Thu, Jul 6, 2017 at 10:55 AM Josh Elser  wrote:

> Thanks, John. Consider this mentor +1 then.
>
> On 7/5/17 7:03 PM, John D. Ament wrote:
> > For what it's worth, I have no concerns with Fluo's graduation based on
> the
> > conversation here.
> >
> > John
> >
> > On Wed, Jul 5, 2017 at 7:02 PM Josh Elser  wrote:
> >
> >>
> >>
> >> On 7/5/17 1:51 PM, Dave Fisher wrote:
> >>> Hi Josh,
> >>>
> >>> I have some questions:
> >>>
> >>>> On Jul 5, 2017, at 10:18 AM, Josh Elser  wrote:
> >>>>
> >>>> As a mentor, I consciously avoided an explicit "+1" until we got some
> >> IPMC discussion. Let me expand:
> >>>>
> >>>> The current members of Fluo are great, get the Apache Way, and are
> >> self-sufficient. I have no concerns over them operating as a TLP -- I
> think
> >> they are ready. However, they have only added a single committer and I
> see
> >> none in the pipeline -- Fluo is defined by the current committers.
> >>>
> >>> (1) Seems to be a niche project as you state below which is just within
> >> the range of 5 contributors. Am I wrong?
> >>
> >> Yup, that sounds about right. I'm notice three of them being the most
> >> active, but I tend to not watch that closely.
> >>
> >>>> My hesitation is balancing the Incubators goal of "pushing podlings to
> >> graduate" and ensuring adequate diversity in the podling. This is
> >> especially difficult for Fluo as they're "niche on niche" (it's a
> difficult
> >> dist-sys problem/software, and not many people use the tech they're
> >> building on top of given my view of the world).
> >>>>
> >>>> I realize that this discussion could easily spiral out of control,
> >> turning into some meta-discussion about Incubator goals. I want to avoid
> >> that.
> >>>>
> >>>> I'm looking for some feelings from other IPMC folks about how to
> >> approach the Fluo podling given their specific circumstances. If other
> >> people are also hesitant, I would also be interested in suggestions
> about
> >> what we would concretely change (because I don't know what to suggest
> that
> >> "fix" the diversity issue for them that isn't changing the core of their
> >> project). If people aren't worried, I'm happy to give an explicit +1.
> >>>
> >>> (2) Has any consideration been given to becoming a project within
> >> Accumulo? Or are the goals of Fluo distinct from and not wholly
> dependent
> >> on Accumulo?
> >>>
> >>> (3) Corollary - it seems a large number of Fluo Initial Committers were
> >> also Accumulo PMC. (I not intentionally rehashing any prior
> conversation.)
> >>>
> >>
> >> Will leave Christopher's response to (thoroughly) answer this ;)
> >>
> >> -
> >> 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: Edit Access to incubator wiki

[John D. Ament]

Added, happy editing!

On Sat, Jul 8, 2017 at 8:55 PM Francis Liu  wrote:

> Hi,
> Can I please get access to edit the incubator wiki. Need to it sign-off on
> pulsar podling report.
> username: FrancisLiu
>
> Thanks,Francis
>
>

Re: ZeroMQ licensing in Apache MXNet

[John D. Ament]

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 
> 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 
> 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 Airflow 1.8.2 (incubating)

[John D. Ament]

And to answer the question why this only came up now.  I'm mentoring the
Aria Tosca project, and looking at their release pointed out some of these
issues, so only then I came to find out the differences about this.  Thanks
to Ran, I understand better now.

John

On Thu, Jul 6, 2017 at 1:38 PM Bolke de Bruin  wrote:

> Thanks alot. That does indeed help, and might be a structure we will start
> using ourselves.
>
> Cheers
> Bolke
>
> Sent from my iPhone
>
> > On 6 Jul 2017, at 17:34, Ran Ziv  wrote:
> >
> > Hi,
> >
> > I'm not 100% sure this is relevant, but regarding sdist vs source
> tarball,
> > we just had a similar issue in the apache-ariatosca project when the
> > release candidate package I had brought up to a vote contained a Pythonic
> > sdist rather than a source code tarball.
> > We ended up creating three different packages:
> > a tarball ("source") - containing a snapshot of the source code
> (including
> > e.g. doc-generating files, but without the generated doc pages)
> > an sdist - containing examples, generated documentation, and source code
> > with a setup.py etc.
> > and a bdist - basically the package's wheel (but updated to contain the
> > LICENSE, NOTICE and DISCLAIMER files) i.e. compiled code.
> >
> > The tarball goes as the canonical Apache release, and the sdist and bdist
> > packages go on PyPI.
> >
> > You can see the structure here if you're interested:
> >
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
> >
> >
> > Sorry if this wasn't relevant for your scenario.
> >
> >
> >
> >
> >
> >> On Thu, Jul 6, 2017 at 5:00 PM, Bolke de Bruin 
> wrote:
> >>
> >> Protovis became d3, which is BSD licensed. D3’s examples contain the
> same
> >> code. The author (Mike Bostock) is the same in both cases. I have just
> send
> >> him an email, I hope he responds.
> >>
> >> Cheers
> >> Bolke
> >>
> >>
> >>> On 6 Jul 2017, at 15:08, Justin Mclean 
> wrote:
> >>>
> >>> HI,
> >>>
>  [20] “nv.d3.js” originates from http://nvd3.org 
> and
> >> its license states it is Apache License 2,
> https://github.com/novus/nvd3/
> >> blob/master/LICENSE.md  >> nvd3/blob/master/LICENSE.md> . And as far as I understand it it should
> >> not need to be licensed to the ASF to be using the APL2?
> >>>
> >>> Which is fine but if you look a litter closer you see in the file this
> >> comment:
> >>>
> >>> // Chart design based on the recommendations of Stephen Few.
> >> Implementation
> >>> // based on the work of Clint Ivy, Jamie Love, and Jason Davies.
> >>> // http://projects.instantcognition.com/protovis/bulletchart/
> >>>
> >>> Going to that URL it’s unclear how that code is licensed.
> >>>
> >>> Doing a google search show similar code that is GPL licensed.
> >>>
> >>> 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
> >>
> >>
>
> -
> 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

[John D. Ament]

Hen,

Can you give some more info about how MXnet uses ZeroMQ?  Is it an optional
dependency or required?  Are you actually bundling ZeroMQ in your release
(source or binary)?

John

On Thu, Jul 6, 2017 at 2:23 AM Henri Yandell  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
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

It looks like the header issues are tracked as
https://issues.apache.org/jira/browse/ARIA-300

Thanks Tal!

John

On Wed, Jul 5, 2017 at 10:11 PM Tal Liron  wrote:

> +1 non-binding.
>
> Justin, most of the YAML files do have the header, it seems that only our
> examples don't. I will make a note to add them.
>
> On Wed, Jul 5, 2017 at 8:02 PM, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > +1 binding
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes good
> > - disclaimer exists
> > - LICENSE and NOTICE good
> > - no unexpected binaries
> > - All source file have ASF headers (would be nice if the yaml files has
> > ASF headers)
> >
> > I did run into an issue compiling but probably my setup. Is OSX a
> > supported platform I note a TODO in the readme?
> >
> >  Running setup.py install for apache-ariatosca ... error
> >Complete output from command /usr/bin/python -u -c "import setuptools,
> >
> tokenize;__file__='/private/tmp/pip-RmQ4kh-build/setup.py';f=getattr(tokenize,
> > 'open', open)(__file__);code=f.read().replace('\r\n',
> > '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record
> > /tmp/pip-7e9Nfb-record/install-record.txt
> --single-version-externally-managed
> > --compile:
> >Traceback (most recent call last):
> >  File "", line 1, in 
> >  File "/Library/Python/2.7/site-packages/setuptools/__init__.py",
> > line 12, in 
> >import setuptools.version
> >  File "/Library/Python/2.7/site-packages/setuptools/version.py", line
> > 1, in 
> >import pkg_resources
> >  File "/Library/Python/2.7/site-packages/pkg_resources/__init__.py",
> > line 72, in 
> >import packaging.requirements
> >  File "/Library/Python/2.7/site-packages/packaging/requirements.py",
> > line 59, in 
> >MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
> >TypeError: __call__() takes exactly 2 arguments (1 given)
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Tal Liron, Senior Solutions Architect 
> --
> M: +1-312-375-8299 <(312)%20375-8299> http://cloudify.co @cloudifysource
> 
> 
> 
> 
>

Re: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

For what it's worth, I have no concerns with Fluo's graduation based on the
conversation here.

John

On Wed, Jul 5, 2017 at 7:02 PM Josh Elser  wrote:

>
>
> On 7/5/17 1:51 PM, Dave Fisher wrote:
> > Hi Josh,
> >
> > I have some questions:
> >
> >> On Jul 5, 2017, at 10:18 AM, Josh Elser  wrote:
> >>
> >> As a mentor, I consciously avoided an explicit "+1" until we got some
> IPMC discussion. Let me expand:
> >>
> >> The current members of Fluo are great, get the Apache Way, and are
> self-sufficient. I have no concerns over them operating as a TLP -- I think
> they are ready. However, they have only added a single committer and I see
> none in the pipeline -- Fluo is defined by the current committers.
> >
> > (1) Seems to be a niche project as you state below which is just within
> the range of 5 contributors. Am I wrong?
>
> Yup, that sounds about right. I'm notice three of them being the most
> active, but I tend to not watch that closely.
>
> >> My hesitation is balancing the Incubators goal of "pushing podlings to
> graduate" and ensuring adequate diversity in the podling. This is
> especially difficult for Fluo as they're "niche on niche" (it's a difficult
> dist-sys problem/software, and not many people use the tech they're
> building on top of given my view of the world).
> >>
> >> I realize that this discussion could easily spiral out of control,
> turning into some meta-discussion about Incubator goals. I want to avoid
> that.
> >>
> >> I'm looking for some feelings from other IPMC folks about how to
> approach the Fluo podling given their specific circumstances. If other
> people are also hesitant, I would also be interested in suggestions about
> what we would concretely change (because I don't know what to suggest that
> "fix" the diversity issue for them that isn't changing the core of their
> project). If people aren't worried, I'm happy to give an explicit +1.
> >
> > (2) Has any consideration been given to becoming a project within
> Accumulo? Or are the goals of Fluo distinct from and not wholly dependent
> on Accumulo?
> >
> > (3) Corollary - it seems a large number of Fluo Initial Committers were
> also Accumulo PMC. (I not intentionally rehashing any prior conversation.)
> >
>
> Will leave Christopher's response to (thoroughly) answer this ;)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

It seems the discussion has died down.  I'm going to plan to finalize the
last few parts, make the jenkins job also build the legacy bits and move to
the new site sometime next week.

I'll drop a mail when I have the last of it staged and ready to go.

John

On Sat, Jun 24, 2017 at 10:27 AM John D. Ament 
wrote:

> On Thu, Jun 22, 2017 at 12:50 PM Patrick Hunt  wrote:
>
>> On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament 
>> wrote:
>>
>> > All,
>> >
>> > I'd like to start the process to move forward on a new incubator
>> website.
>> > Based on discussions in the past on list, I wanted to do the following:
>> >
>> > - Roll out a new technology stack + repository
>> > - Leave content in place, while we work later on content enhancements
>> >
>> > For right now, I'm planning to leave the existing /projects and
>> > /ip-clearance in place.  My hope is that we may not need them in the
>> > future.
>> >
>> > The website staging area can be seen here:
>> > https://incubator.apache.org/ngtest/
>> > The git repository for the site can be seen here:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
>> > shortlog;h=refs/heads/jbake-site
>> > (with
>> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
>> >
>> > I'd like to get some final feedback on the layout and colors (not the
>> > content).  I want to start tracking content enhancements in JIRA to help
>> > come up with a backlog of areas of improvement for our incubator guides.
>> >
>> >
>> I'm very familiar with the old layout, so this may be coloring my
>> feedback.
>> However I find the new layout to be less usable than previous. In
>> particular the drop downs lack structure. I think it would be better to
>> focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
>> docs, or "graduating a podingling" etc... - basically focus around the
>> lifecycle of podling rather than a big long list of "guides". Additionally
>> it's hard to find things with the new layout, I used to use the browser
>> "search" feature to narrow down to a particular doc. Now I need to click
>> on
>> each of the drop downs to find the content I'm looking for. Additionally
>> things like wiki/faq/etc... - can't find them at all.
>>
>>
> Hi Patrick,
>
> Thanks for the input.  I've started to add it to the new version, let me
> know your thoughts.  There's still a few areas to tweak, but definitely
> keep it coming.
>
> I have to still add a link to google search.
>
> John
>
>
>> Patrick
>>
>>
>> > John
>> >
>>
>

Re: [RESULT][VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[John D. Ament]

Flavio,

I'll update podlings.xml and projects/distributedlog.xml for you.

John

On Sat, Jul 1, 2017 at 10:39 AM Flavio Junqueira  wrote:

> The vote passes with the following:
>
> - 3 +1 binding votes:
> * Flavio Junqueira
> * Henry Saputra
> * John D. Ament
> - 6 +1 non-binding votes:
> * David Rusek
> * Sijie Guo
> * Jia Zhai
> * Von Gosling
> * Leigh Stewart
> * Xinyu Zhou
> - No -1 vote
>
> Thank you all for participating.
>
> -Flavio
>
> > On 01 Jul 2017, at 16:19, Flavio Junqueira  wrote:
> >
> > +1 (binding)
> >
> >> On 01 Jul 2017, at 09:26, Henry Saputra 
> wrote:
> >>
> >> +1 (binding)
> >>
> >> On Thu, Jun 29, 2017 at 7:23 PM Xinyu Zhou  wrote:
> >>
> >>> +1
> >>>
> >>> Regards,
> >>> yukon
> >>>
> >>>
> >>>
> >>> On Fri, Jun 30, 2017 at 3:49am, Leigh Stewart <
> >>> lstew...@twitter.com.invalid [lstew...@twitter.com.invalid] > wrote:
> >>> +1
> >>>
> >>> On Jun 29, 2017 12:55 AM, "Von Gosling"  wrote:
> >>>
> >>>> +1
> >>>>
> >>>> Best Regards,
> >>>> Von Gosling
> >>>>
> >>>>
> >>>>> 在 2017年6月29日，13:42，Sijie Guo  写道：
> >>>>>
> >>>>> +1
> >>>>>
> >>>>> On Wed, Jun 28, 2017 at 8:25 AM, John D. Ament <
> johndam...@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>> I have no idea why this is copying both public and private lists.
> >>>>>>
> >>>>>> I'm +1 to graduate.
> >>>>>>
> >>>>>> On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira 
> >>>> wrote:
> >>>>>>
> >>>>>>> The Apache DistributedLog community has voted to graduate the
> project
> >>>> and
> >>>>>>> make it a subproject of Apache BookKeeper. The Apache BookKeeper
> PMC
> >>>> has
> >>>>>>> also voted to accept DistributedLog as a subproject. The links to
> the
> >>>>>> vote
> >>>>>>> threads are the following:
> >>>>>>>
> >>>>>>> DistributedLog PPMC vote:
> >>>>>>>
> >>>>>>> https://mail-search.apache.org/members/private-arch/
> >>>>>> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> >>>>>> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >>>>>>> <
> >>>>>>> https://mail-search.apache.org/members/private-arch/
> >>>>>> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> >>>>>> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >>>>>>>>
> >>>>>>>
> >>>>>>> https://mail-search.apache.org/members/private-arch/
> >>>>>> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-
> >>>> 9eUYycHJvpCo5=
> >>>>>> ts87rzhpsm096r...@mail.gmail.com%3e
> >>>>>>> <
> >>>>>>> https://mail-search.apache.org/members/private-arch/
> >>>>>> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-
> >>>> 9eUYycHJvpCo5=
> >>>>>> ts87rzhpsm096r...@mail.gmail.com%3e
> >>>>>>>>
> >>>>>>>
> >>>>>>> DistributedLog Community vote:
> >>>>>>>
> >>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
> >>>>>> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> >>>>>> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >>>>>>> <
> >>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
> >>>>>> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> >>>>>> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >>>>>>>>
> >>>>>>>
> >>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
> >>>>>> distributedlog-dev/201706.mbox/%3cCAO2yDya-=
> >>>> 0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
> >>>>>> TQg

Re: [DISCUSS] Gradute Streams as TLP

[John D. Ament]

So I just went back through the archives.  I think I share Dave's concerns
about notifying.  It looks like the incubator list was the first place the
proposed resolution was shared.  Would be good to put in front of the
private@streams list make sure no one has any concerns with it.

John

On Wed, Jul 5, 2017 at 4:26 PM Dave Fisher  wrote:

> Thanks for clarifying. Does this list correspond to those who have
> participated with commits and project work in the last 6 months or year who
> are PPMC members or committers? Will you continue to allow all current
> committers to have commit rights once you go to TLP?
>
> My concern is anyone losing merit even if it has been a few years. People
> come and go. Sometimes people come back after being absent for a couple of
> years. One aspect at Apache is that merit does not expire.
>
> (I am part of OpenOffice where we went from a huge PPMC to a large PMC on
> graduation so I feel what you are doing is legitimate.)
>
> Regards,
> Dave
>
> On Jul 5, 2017, at 1:19 PM, sblackmon  wrote:
>
> As the PPMC member encouraged to draft the resolution, that was the
> condition I decided to apply, after running it by a few others from the
> community out-of-band.  There was no email thread on the topic, so using
> the definition that decisions must be made on the list, this wasn’t a group
> decision, it was an action by me.
>
> Sorry for the confusion.
>
> Steve
>
> On July 5, 2017 at 2:45:50 PM, Dave Fisher (dave2w...@comcast.net) wrote:
>
> Hi Steve,
>
> Where was that decision made? I don’t see that recently in Pony Mail
> archives. I don’t see anything wrong with decision I just don’t see any
> record of it. Please let us know when it was made and how it was recorded.
>
>
> Regards,
> Dave
>
> > On Jul 5, 2017, at 12:33 PM, sblackmon  wrote:
> >
> > John,
> >
> > We decided to propose only PPMC members who voted +1 to the graduation
> resolution for the PMC. If that left out anyone harboring a latent plan to
> re-engage with the project community, and they let us know on dev@streams,
> we’d be happy to add their names onto the resolution.
> >
> > Steve
> >
> > On July 5, 2017 at 2:12:53 PM, John D. Ament (johndam...@apache.org)
> wrote:
> >
> > Hi Steve,
> >
> > Thanks for drafting this. I see there's a big difference between the
> > listed PPMC and the proposed PMC. I'm assuming you've reached out to
> those
> > excluded and confirmed they're not interested in Streams any longer?
> >
> > John
> >
> > On Wed, Jul 5, 2017 at 2:48 PM sblackmon  wrote:
> >
> >> Hello,
> >>
> >> The Streams PPMC has discussed [1] and voted [2] to graduate to TLP.
> >>
> >> In preparation for an IPMC vote on the matter, we’ve updated our project
>
> >> status xml [3] and corresponding whimsy podlingStatus [4], completed an
>
> >> Apache Maturity Model Assessment [5], and drafted a proposed charter
> [6].
> >>
> >> We’d appreciate any feedback you can provide at this stage to help
> ensure
> >> the project has all bases covered to become a successful Apache TLP.
> >>
> >> Thank you for your consideration.
> >>
> >> [1]
> >>
> https://lists.apache.org/thread.html/64738d9382b094bb52a733e7d44f5497eecc04fae4255366abc0270b@
> >> 
> >> [2]
> >>
> >>
> https://lists.apache.org/thread.html/cd17d49769b85a8cda14cd16624032c0ddb02e8e707545082c5fc893@
>
> >> 
> >> [3]
> >> http://incubator.apache.org/projects/streams.html
> >> [4]
> >> https://whimsy.apache.org/roster/ppmc/streams#podlingStatus
> >> [5]
> >>
> >>
> https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
>
> >> [6]
> >> https://cwiki.apache.org/confluence/display/STREAMS/Proposed+Charter
> >>
> >>
> >>
> >>
> >>
>
>
>

Re: [VOTE]: Apache HAWQ 2.2.0.0-incubating Release

[John D. Ament]

On Wed, Jul 5, 2017 at 5:05 PM Roman Shaposhnik 
wrote:

> On Sat, Jul 1, 2017 at 6:37 PM, Ruilong Huo  wrote:
> > Hi IPMC member,
> >
> >
> > The PPMC vote for the Apache HAWQ 2.2.0.0-incubating release has passed.
> We kindly request that the IPMC now vote on the release.
> >
> >
> > The PPMC vote thread is located here:
> >
> https://lists.apache.org/thread.html/ee0b81127e75eb2562e91b0a44d56b24165c6284a7a46dc03eeb7d6d@%3Cdev.hawq.apache.org%3E
> >
> >
> > The artifacts can be downloaded here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.2.0.0-incubating.RC3/
> >
> >
> > The artifacts have been signed with Key : 1B8B6872
> >
> >
> > All JIRAs completed for this release are tagged with 'FixVersion =
> 2.2.0.0-incubating'. You can view them here:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318826&version=12339641
> >
> >
> > Please vote accordingly:
> > [ ] +1, accept as the official Apache HAWQ 2.2.0.0-incubating release
> > [ ] -1, do not accept as the official Apache HAWQ 2.2.0.0-incubating
> release because...
>
> I'm +1 on the release with one caveat: it seems that pxf RPMs don't
> deliver LICENSE/NOTICE/DISCLAIMER.
> inside of the RPMs. Normally that would be enough for me to cast a -1,
> but it seems that the JARs inside
> of the RPMs (and these RPMs deliver JARs only) actually bundle the
> required files.
>
>

> My take it is that we shouldn't hold a release for that -- but I'll
> let the rest of IPMC chime in.
>

I agree with what you said, assuming there's a JIRA tracking fixing it.  I
think the LICENSE/NOTICE should be in the RPMs and should be valid, instead
of just in the JARs.

BTW its a little odd that you only provide RPMs.  Do you also plan to
support DEBs?  What about install on macOS/Windows?


>
> The rest looks really good:
>* checked sigs and hashes
>* compared source tarball to the git tag
>* checked for license headers in the source
>* installed the RPMs
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Gradute Streams as TLP

[John D. Ament]

Hi Steve,

Thanks for drafting this.  I see there's a big difference between the
listed PPMC and the proposed PMC.  I'm assuming you've reached out to those
excluded and confirmed they're not interested in Streams any longer?

John

On Wed, Jul 5, 2017 at 2:48 PM sblackmon  wrote:

> Hello,
>
> The Streams PPMC has discussed [1] and voted [2] to graduate to TLP.
>
> In preparation for an IPMC vote on the matter, we’ve updated our project
> status xml [3] and corresponding whimsy podlingStatus [4], completed an
> Apache Maturity Model Assessment [5], and drafted a proposed charter [6].
>
> We’d appreciate any feedback you can provide at this stage to help ensure
> the project has all bases covered to become a successful Apache TLP.
>
> Thank you for your consideration.
>
> [1]
> https://lists.apache.org/thread.html/64738d9382b094bb52a733e7d44f5497eecc04fae4255366abc0270b@
> 
> [2]
>
> https://lists.apache.org/thread.html/cd17d49769b85a8cda14cd16624032c0ddb02e8e707545082c5fc893@
> 
> [3]
> http://incubator.apache.org/projects/streams.html
> [4]
> https://whimsy.apache.org/roster/ppmc/streams#podlingStatus
> [5]
>
> https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
> [6]
> https://cwiki.apache.org/confluence/display/STREAMS/Proposed+Charter
>
>
>
>
>

Re: Write access to Incubator Wiki

[John D. Ament]

Done happy editing!

On Jul 5, 2017 11:32 AM, "Dave Neuman"  wrote:

> Hello,
> Can you please grant write access for my user (neuman) to the Incubator
> wiki page (https://wiki.apache.org/incubator/July2017)?  I need it to
> upload the July report for the Traffic Control project.
>
> Thanks in advance!
>
> Dave
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

Copying my +1 from the dev list.

- Builds from source
- Signed
- Clearly separated source, sdist and bdist files

John

On Wed, Jul 5, 2017 at 9:52 AM Ran Ziv  wrote:

> The ariatosca community voted on and has approved a proposal to release
> ariatosca 0.1.0.
> Pursuant to the Releases section of the Incubation Policy and with the
> endorsement of two of our mentors we would now like to request the
> permission of the Incubator PMC to publish the tarball Apache's
> /dist/release.
>
>
> Proposal:
>
> https://lists.apache.org/thread.html/ab4979e21893389a97f57d0b1823608a0933f27fcc4e7e0805cbc583@%3Cdev.ariatosca.apache.org%3E
>
>
> Vote result:
>
> https://lists.apache.org/thread.html/24420783e5bb09db4246819d31c9b7806edc57013e0838ec4790c06b@%3Cdev.ariatosca.apache.org%3E
>
>
> Release candidate package may be found at:
> *
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
> <
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
> >*
> The "source" directory contains the actual source snapshot as required per
> an Apache release.
> the "sdist" and "bdist" directories are Pythonic source and binary
> distributions, to be uploaded on PyPI upon a successful vote.
>
> See more information about the package in the original proposal thread.
>
>
>
> Please vote by Saturday, July 8th, at 14:00 UTC.
>
>
> Thanks,
> Ran
>

Re: [VOTE] Release Apache Airflow 1.8.2 (incubating)

[John D. Ament]

Hi,

I have a few questions about the release contents.

I ran RAT, and found many unapproved files.  Are you maybe missing a few
things from your rat excludes?  https://paste.apache.org/jBql is the report
I got (ignore rat-output, it's the file I was piping to).  Note that there
is no rat-excludes file in the distribution yet there is one in the git
repo.  Also, I cannot follow the instructions in the email to run rat which
points to "sh scripts/ci/check-license.sh" which doesn't exist in the
release.

In addition, comparing the release contents to your git repository, are you
sure this is your source release and not your bdist (in pypi terms)?  While
its good to have the convenience binary around, we're looking to review and
approve the source release for compliance.  I've been working with the
AriaTosca podling, we've come up with a process to create the source
release, sdist and bdist that would be distributed via pypi.

John



On Mon, Jul 3, 2017 at 6:56 PM Maxime Beauchemin 
wrote:

> Hello Incubator PMC’ers,
>
> The Apache Airflow community has voted and approved the proposal to release
> Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 2. We
> now kindly request the Incubator PMC members to review and vote on this
> incubator release. If the vote is successful we will rename release
> candidate 2 to final.
>
> Airflow is a platform to programmatically author, schedule and monitor
> workflows. Use airflow to author workflows as directed acyclic graphs
> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of
> workers while following the specified dependencies. Rich command line
> utilities make performing complex surgeries on DAGs a snap. The rich user
> interface makes it easy to visualize pipelines running in production,
> monitor progress, and troubleshoot issues when needed. When workflows are
> defined as code, they become more maintainable, versionable, testable, and
> collaborative.
>
> The Apache Airflow-1.8.2-incubating release candidate is now available with
> the following artifacts for a project vote:
>
> * [VOTE] Thread:*
> *
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
> >*
>
> TODO
>
> *The release candidate(s) to be voted on is available at:*
> https://dist.apache.org/repos/dist/dev/incubator/airflow/ or
> *
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
> >*
>
> *Git branch*
> https://github.com/apache/incubator-airflow/tree/v1-8-test or
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-test
>
> *Git tag*
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
> >*
>
> *PGP signature*
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.asc
>
> *MD5/SHA Hashes*
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.md5
>
> https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.sha
>
> *Keys to verify the signature of the release artifacts are available at:*
> https://dist.apache.org/repos/dist/release/incubator/airflow/
>
> * RAT License checks*
>
> RAT is executed as part of the CI process (e.g.
> https://travis-ci.org/apache/incubator-airflow/builds/226568140) but can
> also be run manually by issuing “sh scripts/ci/check-license.sh” from the
> top level.
>
> Source code is always included, i.e. there is no binary release.
> Compilation and installation will happen by standard Python practices, e.g.
> pip install <> or python setup.py install.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Members please be sure to indicate "(Binding)" with your vote which will
> help in tallying the vote(s).
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> *Here is my +1 (non-binding)*
>
> Cheers,
>
> Max
>

Re: Guidance on copyrights in sample code.

[John D. Ament]

On Mon, Jul 3, 2017 at 6:28 PM Ted Dunning  wrote:

> That's confusing. Here are some questions and thoughts.
>
> A) 2001?
>
> B) the only Apache foundation is the Apache software foundation. What did
> you mean by foobar?
>
> C) you don't need a copyright notice on code included in the documentation.
> Save that for the copy of the sample code that you put into a separate
> file.
>
>
That's actually why I asked James to pose the question on the general
list.  I wasn't particularly sure if he found the right file, based on the
comments made by Justin and was hoping Justin could speak up to explain why
it is or isn't an issue, and if there's a way to include a sample atom that
wouldn't get flagged.  I had posed on the list "1955 - 1971, Fake Atom
Enterprises" which obviously would be an invalid copyright used only for
demonstration purposes.  (for those unfamiliar, US Copyright law started in
1976, entities prior to that date wouldn't have been valid).


>
> On Jul 3, 2017 2:38 PM, "James Bognar"  wrote:
>
> > Need some quick guidance.
> >
> > On the release vote for Juneau 6.3.0, Justin Mclean made this note...
> > "There's a number of "Copyright (c) 2016, Apache Foundation” in the
> > documentation you may want to update the year."
> >
> > I tracked it down to sample code where the copyright statement itself was
> > sample code.  (i.e. showing how to create an ATOM feed with an embedded
> > copyright statement).
> >
> > Can I change it to the following so that it's not flagged in the future?
> >
> > "Copyright (c) 2001, Apache Foobar Foundation”
> >
> > Or better ideas?
> >
>

[RESULT] Retire Sirona (was Re: [VOTE] Retire Sirona)

[John D. Ament]

All,

The vote to retire Sirona passes with 7 +1's to retire (6 from IPMC
members).

I'll move forward on getting the infra tickets in and various other
paperwork post holiday.

John

On Sat, Jul 1, 2017 at 12:48 AM Jean-Baptiste Onofré 
wrote:

> +1
>
> Regards
> JB
>
> On 06/26/2017 06:50 PM, John D. Ament wrote:
> > All,
> >
> > This is a call to vote the Sirona podling.
> >
> > A vote was called for on the dev list for Sirona [1], of which one mentor
> > commented and that's all.
> >
> > Sirona at this point is behind 6 months on reports, has shown little
> > activity since joining the incubator.  Its not clear there are 3 PPMCs
> > available for a vote if need be.  Based on the prior discussions ([2] &
> > [3]) and these items, I'd like to call for a vote and unilateral decision
> > by the IPMC to retire Sirona.
> >
> > [ ] +1 to retire Sirona
> > [ ] -1 don't retire Sirona because...
> >
> > Here is my +1.
> >
> > John
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/673daa1452150ed5ef0df4aa77f587dbac6e5a4a63670c6bf4809b17@%3Cdev.sirona.apache.org%3E
> > [2]:
> >
> https://lists.apache.org/thread.html/0a70d486680f0339bfcb4baae23c2540095fda90ca83eb414104a6fd@%3Cgeneral.incubator.apache.org%3E
> > [3]:
> >
> https://lists.apache.org/thread.html/438298290de9a3573b5e315b12e77191b27f8d91b50cf9f97e90cba8@%3Cgeneral.incubator.apache.org%3E
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

Oh hmm did a bit more digging.

Looks like you did add someone, but I guess due to timing it was missed in
the last board report? Then nevermind, ignore my 2nd bullet point.

John

On Mon, Jul 3, 2017 at 4:15 PM John D. Ament  wrote:

> Hi Christopher,
>
> Thanks for the heads up.  A few nits on my part, but overall I would be
> happy to see Fluo graduate.  When reading my notes, please also consult the
> graduation guide at [1].
>
> - The discussion and vote should have happened on your public dev list,
> not private.  It's good that at least discussion happened publicly, and the
> actual vote isn't required so it's not a big deal.
> - I don't see any sign that you added new committers or PPMC members since
> incubating.  See also [2].  I don't see that as a show stopper, as it looks
> like a diverse group.
> - Of the proposed PMC, how many are actively committing to Fluo?  Was
> there an ask at any point to see who was still interested?
> - Only one mentor voted on the graduation.  Would be great to see if the
> other mentors are equally on board.
>
> John
>
> [1]: http://incubator.apache.org/guides/graduation.html#toplevel
> [2]: https://whimsy.apache.org/board/minutes/Fluo
>
>
> On Mon, Jul 3, 2017 at 2:12 PM Christopher  wrote:
>
>> Greetings Incubator,
>>
>> The Fluo podling has decided to pursue graduation to a TLP. The result of
>> the internal PPMC vote is at [1] (apologies that it occurred on our
>> private
>> list instead of on our dev list; the discuss thread [2] which preceded it
>> did occur on the dev list). Our podling status page has recently been
>> updated and can be found here[3].
>>
>> Below, you can view the proposed TLP resolution which we'd like to present
>> to the board with the support of the IPMC, after sufficient discussion
>> here
>> and subsequent IPMC vote.
>>
>> [1]:
>>
>> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
>> [2]:
>>
>> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
>> [3]: https://incubator.apache.org/projects/fluo
>>
>> **
>> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Fluo Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>>
>> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
>> the creation and maintenance of software related to the storage and
>> incremental processing of large data sets; and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
>> have primary responsibility for management of the projects within the
>> scope of responsibility of the Apache Fluo 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 Fluo Project:
>>
>> * Billie Rinaldi 
>> * Chris McTague 
>> * Christopher Tubbs 
>> * Corey J. Nolet 
>> * Drew Farris 
>> * Josh Elser 
>> * Keith Turner 
>> * Mike Walch 
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
>> to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
>> further
>>
>> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
>> migration and rationalization of the Apache Incubator Fluo podling; and
>> be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>>
>

Re: [DISCUSS] Fluo graduation as TLP

[John D. Ament]

Hi Christopher,

Thanks for the heads up.  A few nits on my part, but overall I would be
happy to see Fluo graduate.  When reading my notes, please also consult the
graduation guide at [1].

- The discussion and vote should have happened on your public dev list, not
private.  It's good that at least discussion happened publicly, and the
actual vote isn't required so it's not a big deal.
- I don't see any sign that you added new committers or PPMC members since
incubating.  See also [2].  I don't see that as a show stopper, as it looks
like a diverse group.
- Of the proposed PMC, how many are actively committing to Fluo?  Was there
an ask at any point to see who was still interested?
- Only one mentor voted on the graduation.  Would be great to see if the
other mentors are equally on board.

John

[1]: http://incubator.apache.org/guides/graduation.html#toplevel
[2]: https://whimsy.apache.org/board/minutes/Fluo

On Mon, Jul 3, 2017 at 2:12 PM Christopher  wrote:

> Greetings Incubator,
>
> The Fluo podling has decided to pursue graduation to a TLP. The result of
> the internal PPMC vote is at [1] (apologies that it occurred on our private
> list instead of on our dev list; the discuss thread [2] which preceded it
> did occur on the dev list). Our podling status page has recently been
> updated and can be found here[3].
>
> Below, you can view the proposed TLP resolution which we'd like to present
> to the board with the support of the IPMC, after sufficient discussion here
> and subsequent IPMC vote.
>
> [1]:
>
> https://lists.apache.org/thread.html/04a9de260fcd14b184ae7a8b725e348e13ee4ad10e3057a6a404732c@%3Cprivate.fluo.apache.org%3E
> [2]:
>
> https://lists.apache.org/thread.html/3164d77ea18c3e36ce215ab4a07b2cb80cf9c49c2503ef5d1defbdde@%3Cdev.fluo.apache.org%3E
> [3]: https://incubator.apache.org/projects/fluo
>
> **
> Establish the Apache Fluo 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 the storage and incremental processing of large data sets.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Fluo Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Fluo Project be and hereby is responsible for
> the creation and maintenance of software related to the storage and
> incremental processing of large data sets; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Fluo" 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 Fluo Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Fluo 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 Fluo Project:
>
> * Billie Rinaldi 
> * Chris McTague 
> * Christopher Tubbs 
> * Corey J. Nolet 
> * Drew Farris 
> * Josh Elser 
> * Keith Turner 
> * Mike Walch 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
> to the office of Vice President, Apache Fluo, 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 Fluo 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 Fluo Project; and be it
> further
>
> RESOLVED, that the Apache Fluo Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Fluo podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Fluo podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: Edit access to wiki for Rya project report

[John D. Ament]

Added, but just to confirm wiki is a separate registration and is not
necessarily your ASF user id.

On Mon, Jul 3, 2017 at 2:04 PM David Lotts  wrote:

> Can someone give me edit access to the wiki for incubator reports?
> I'd like to submit one for Rya. Username is:
>
> dlotts
>
> Thanks,
> david lotts.
>

Re: Edit Access to the Wiki

[John D. Ament]

Added.

FWIW, there was a "David Fisher" account listed as well.  It wasn't
properly bracketed, so it wouldn't have worked.  I can fix that one if you
want, or just ignore it.

On Mon, Jul 3, 2017 at 2:13 PM Dave Fisher  wrote:

> Hi -
>
> I lost track of my prior MoinMoin Wiki account and created a new one.
>
> Please grant DavidFisher access to Edit the Incubator Wiki.
>
> (My old one seems to be named "c-67-180-51-144” in the logs.)
>
> Thanks and Regards,
> Dave
>

Re: svn commit: r1800695 - /incubator/public/trunk/content/podlings.xml

[John D. Ament]

Julien,

Does Heron intend to report this month (July)?

John

On Mon, Jul 3, 2017 at 12:09 PM  wrote:

> Author: julien
> Date: Mon Jul  3 16:09:08 2017
> New Revision: 1800695
>
> URL: http://svn.apache.org/viewvc?rev=1800695&view=rev
> Log:
> creating Heron podling
>
> Modified:
> incubator/public/trunk/content/podlings.xml
>
> Modified: incubator/public/trunk/content/podlings.xml
> URL:
> http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1800695&r1=1800694&r2=1800695&view=diff
>
> ==
> --- incubator/public/trunk/content/podlings.xml [utf-8] (original)
> +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Jul  3
> 16:09:08 2017
> @@ -1032,6 +1032,17 @@ and a set of useful extensions for this
>  Davanum Srinivas
>  
>  
> + sponsor="Incubator" startdate="2017-06-23">
> +A real-time, distributed, fault-tolerant stream
> processing engine.
> +
> +Julien Le Dem
> +
> +Jake Farrell
> +Jacques Nadeau
> +Julien Le Dem
> +P. Taylor Goetz
> +
> +
>   startdate="2009-11-05" enddate="2012-02-11">
>  HISE
>  Retired due to inactivity.
>
>
>
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
>
>

Re: Wiki Access

[John D. Ament]

Added, happy editing!

On Mon, Jul 3, 2017 at 3:30 AM Nikolai Stoilov 
wrote:

> Hello,
>
> I'd like to request write access to the Incubator wiki, so I can add the
> report for Milagro.
>
> My wiki ID is nstoilov
>
>
> Thanks,
>
> Nikolai Stoilov
> --
> Nikolai Stoilov
> NOC/Support Team Lead
> MIRACL
>

Re: vote to go to a TLP? (was: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper)

[John D. Ament]

On Sat, Jul 1, 2017 at 5:33 AM Stian Soiland-Reyes  wrote:

> IPMC formally owns "Apache DistributedLog" until graduation. BookKeeper -
> or any project anywhere - would of course legally be allowed to fork the
> code under a different name. Graduation is more about the community
> practices, not so much the code.
>
>
No we don't.  It's actually not clear who owns the name "DistributedLog"
right now.  Shane may be able to answer that, but all marks are owned by
the ASF as a whole, the individual PMCs are responsible for enforcing the
naming used.



> Realistically IPMC won't block any such graduation into an existing ASF
> project who is accepting, but it should not be automatic, e.g. IPMC should
> oversee to ensure the new (sub)community is working in an Apache Way, that
> contributions are recognised and releases are IP clean.
>

Yep.  I would be shouting out if their last release was in bad shape, but
that isn't an issue.



>
>
> On 1 Jul 2017 9:01 am, "Greg Stein"  wrote:
>
> On Wed, Jun 28, 2017 at 10:25 AM, John D. Ament 
> wrote:
>
> > I have no idea why this is copying both public and private lists.
> >
>
> And I have no idea why this is a vote for the IPMC to conduct.
>

I agree.  The sub-project graduation has an extra vote that's not really
required.  I feel a [NOTICE] is enough pre-vote and post vote.  We can add
comments like "make sure you do a PNS!" and "Your releases are a pain, make
them better in the future" but for all intents and purposes, this is BK's
problem.

However, with that said, they are following the currently written guide.
Others are free to make changes to the guide.


>
> Can't Apache BookKeeper just move the code over, add some committers and
> PMC members, and carry on?
>
> Like... what? The IPMC will tell BK "you can't do that" ??
>
> Cheers,
> -g
>

Re: Copying private and public lists on VOTE thread (was: Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper)

[John D. Ament]

On Thu, Jun 29, 2017 at 4:50 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Jun 28, 2017 at 8:56 PM, Flavio Junqueira  wrote:
> > ...1- We suggest to only send to general, and not copy anyone else, or
> at least not copy any private list...
>
> That's my favorite way by far, send the actual message to a single
> list and if needed send *pointers* to that message to other lists.
>
> Like "FYI, a VOTE about xyz is going on on d...@foobarinator.apache.org".
>

Yep, and that matches what is stated on the incubator [1] guide.

[1]: http://incubator.apache.org/guides/graduation.html#tlp-resolution



>
> -Bertrand
>
> -
> 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 2.0.0 incubating (RC6)

[John D. Ament]

On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood  wrote:

> Thanks John and Justin..Eric's out for a few days,  but I can work
> on getting some of these things addressed.
>
> The build instructions will be put in place once the release is done
> -- catch-22..  but I should be able to add a reference to the local
> rst file as well.   Would Jira issues for the copyright and build
> instruction issues be sufficient?  Or would you prefer to see another
> RC to address those?
>
> The `./pkg` is the simplest way to build.   If you give that a `-v`,
> it will spill all the output to stdout so you can see where it's
> erroring out.   We are able to build it,  so not sure where the issue
> lies with building the traffic_portal.
>

Is there a log to look at the failure?

Either way I'm fine with releasing as is, so +1.


>
> -dan
>
> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament 
> wrote:
> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean 
> > wrote:
> >
> >> Hi,
> >>
> >> +0 binding as I can’t build from source and no instructions provided.
> >>
> >
> > I struggled with this a bit as well.  The BUILD.md indicates:
> >
> > See the build instructions at ./docs/source/development/building.rst or
> at
> >
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> >
> > That URL doesn't work, but the rst file indicates running pkg does the
> > build.
> >
> > However, when I run pkg, I get the following:
> >
> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
> > ☺  ./pkg
> >
> >
> >
> > Building traffic_portal_build.
> > Building traffic_router_build.
> > Building traffic_monitor_build.
> > Building source.
> > Building traffic_ops_build.
> > Building traffic_stats_build.
> > Failed to build traffic_portal_build.
> >
> >
> >>
> >> I will change to +1 when I can compile/ you raise a JIRA to add
> >> instructions on how to build.
> >>
> >> I checked:
> >> - signatures and hashes good
> >> - DISCLAIMER exists
> >> - LICENSE good
> >> - NOTICE OK . You can remove the information about the fonts in there
> it’s
> >> not needed.
> >> - No unexpected binary files
> >> - All source files have headers (there's a few script files and other
> >> files that could also have headers)
> >> - can't build from source
> >>
> >> when running the build.sh script it eventually fails with this error
> >>
> >> cp: ./build/*.spec: No such file or directory
> >> Could not copy spec files: 1
> >> traffic_stats failed:
> >> The following subdirectories had errors:
> >>traffic_monitor
> >>traffic_monitor_golang
> >>traffic_ops
> >>traffic_portal
> >>traffic_router
> >>traffic_stats
> >>
> >> Has perhaps something not been included in the release or is my
> >> environment not set up correctly?
> >>
> >> It would be nice to include the build instructions in the build itself.
> I
> >> believe this has come up before. By providing a URL it means that the
> >> content of that URL may change for future releases and people would be
> >> unable to build this release. In fact the URL in the documentation is
> >> incorrect [1] and currently 404s which is less than helpful.
> >>
> >> There a few file still copyright comcast I assume these need to be
> >> removed? [2][3][4][5][6]
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> >>
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> >> 2.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> >> 3.
> >>
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> >> 4.
> >>
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> github.com/jheitz200/test_helper/http.go
> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> github.com/jheitz200/test_helper/test.go
> >>
> >>
> >>
> >> -
> >> 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: Copying private and public lists on VOTE thread (was: Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper)

[John D. Ament]

On Wed, Jun 28, 2017 at 12:27 PM Flavio Junqueira  wrote:

>
> > On 28 Jun 2017, at 17:25, John D. Ament  wrote:
> >
> > I have no idea why this is copying both public and private lists.
> >
>
> I wanted to make sure that everyone on those lists saw the thread as the
> people on those lists participated in the vote process. Perhaps I should
> have added them bcc instead.
>


My concern is from this page:
https://www.apache.org/foundation/mailinglists.html

Specifically: "Be sure not to take emails from private discussions or
mailing lists into a public forum"


>
> Thanks for voting.
>
> -Flavio
>
> > I'm +1 to graduate.
> >
> > On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira  wrote:
> >
> >> The Apache DistributedLog community has voted to graduate the project
> and
> >> make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has
> >> also voted to accept DistributedLog as a subproject. The links to the
> vote
> >> threads are the following:
> >>
> >> DistributedLog PPMC vote:
> >>
> >>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3ccao2ydyy3nzjtb934g-aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >> <
> >>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3ccao2ydyy3nzjtb934g-aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >>>
> >>
> >>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=ts87rzhpsm096r...@mail.gmail.com%3e
> >> <
> >>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=ts87rzhpsm096r...@mail.gmail.com%3e
> >>>
> >>
> >> DistributedLog Community vote:
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3ccao2ydyzzinfghjxqmvehxdaulkwdt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3ccao2ydyzzinfghjxqmvehxdaulkwdt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >>>
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+TQgqwJs=c...@mail.gmail.com%3e
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+TQgqwJs=c...@mail.gmail.com%3e
> >>>
> >>
> >> BookKeeper PMC vote:
> >>
> >>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3e
> >> <
> >>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3e
> >>>
> >>
> >>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=W=c09qk2...@mail.gmail.com%3e
> >> <
> >>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=W=c09qk2...@mail.gmail.com%3e
> >>>
> >>
> >> This message is to start an IPMC vote. Please vote on the following:
> >>
> >> [ ] +1 Graduate Apache DistributedLog from the Incubator.
> >> [ ] +0 No opinion
> >> [ ] -1 Don't graduate Apache DistributedLog from the Incubator (please
> >> provide
> >> the reason)
> >>
> >> This VOTE will be opened for the next 72 hours.
> >>
> >> -Flavio
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[John D. Ament]

I have no idea why this is copying both public and private lists.

I'm +1 to graduate.

On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira  wrote:

> The Apache DistributedLog community has voted to graduate the project and
> make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has
> also voted to accept DistributedLog as a subproject. The links to the vote
> threads are the following:
>
> DistributedLog PPMC vote:
>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3ccao2ydyy3nzjtb934g-aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> <
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3ccao2ydyy3nzjtb934g-aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >
>
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=ts87rzhpsm096r...@mail.gmail.com%3e
> <
> https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=ts87rzhpsm096r...@mail.gmail.com%3e
> >
>
> DistributedLog Community vote:
>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3ccao2ydyzzinfghjxqmvehxdaulkwdt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3ccao2ydyzzinfghjxqmvehxdaulkwdt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >
>
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+TQgqwJs=c...@mail.gmail.com%3e
> <
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+TQgqwJs=c...@mail.gmail.com%3e
> >
>
> BookKeeper PMC vote:
>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3e
> <
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3e
> >
>
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=W=c09qk2...@mail.gmail.com%3e
> <
> https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=W=c09qk2...@mail.gmail.com%3e
> >
>
> This message is to start an IPMC vote. Please vote on the following:
>
> [ ] +1 Graduate Apache DistributedLog from the Incubator.
> [ ] +0 No opinion
> [ ] -1 Don't graduate Apache DistributedLog from the Incubator (please
> provide
> the reason)
>
> This VOTE will be opened for the next 72 hours.
>
> -Flavio

Re: Seeking interested parties for a messaging components podling

[John D. Ament]

You've been added.

On Wed, Jun 28, 2017 at 8:06 AM Michael André Pearce <
michael.andre.pea...@me.com> wrote:

> @John,
>
> I have created username: MichaelAndrePearce (so original)
>
> Could I be enabled to edit the wiki
>
> Cheers
> Mike
>
> Sent from my iPhone
>
> > On 26 Jun 2017, at 21:47, Clebert Suconic 
> wrote:
> >
> > @John: do I need special auth to change the WIKI you created? I can't
> > figure out how to make a change.
> >
> >> On Mon, Jun 26, 2017 at 6:16 AM, John D. Ament 
> wrote:
> >> All,
> >>
> >> I've dropped in the proposal template to
> >> https://wiki.apache.org/incubator/MessagingComponentsProposal - we can
> >> rename it later if we come up with a better name.  I'd encourage those
> >> interested in the project to start to form out this proposal so we can
> >> start to shape the who, the why and the what.  If you need access to the
> >> incubator wiki, first register then email on here asking to gain access.
> >> Include your username.
> >>
> >> John
> >>
> >>> On Sun, Jun 25, 2017 at 9:17 PM Von Gosling 
> wrote:
> >>>
> >>> Hi john,
> >>>
> >>> I am very interested in participate in such a podling personally. as
> for
> >>> RocketMQ community, imo, we will start a thread to discussion this
> idea :-)
> >>>
> >>> Best Regards,
> >>> Von Gosling
> >>>
> >>>
> >>>> 在 2017年6月24日，22:17，John D. Ament  写道：
> >>>>
> >>>> Hi Von Gosling,
> >>>>
> >>>> So I just want to check, is this an indication that there may be
> interest
> >>>> from the RocketMQ community to participate in such a podling?
> >>>>
> >>>> John
> >>>>
> >>>> On Fri, Jun 23, 2017 at 9:35 PM Von Gosling 
> >>> wrote:
> >>>>
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>>
> >>>>> I am not sure your mention is Apache RocketMQ. In RocketMQ, jms
> >>>>> integration is just a adaptor, while not fully support JMS 1.1 and
> JMS
> >>> 2.0
> >>>>> specification.
> >>>>>
> >>>>> IMO, that’s a good idea. if we messaging engines can collaborate to
> some
> >>>>> common components, such as benchmark, common api specification, wire
> >>>>> protocol bridge and so on.
> >>>>>
> >>>>> Indeed, we have drafted some api specification(OpenMessaging) about
> >>>>> messaging and streaming fields[1], welcome any idea about it :-)
> >>>>>
> >>>>>
> >>>>> [1] https://openmessaging.github.io/ <
> https://openmessaging.github.io/>
> >>>>>
> >>>>> Best Regards,
> >>>>> Von Gosling
> >>>>>
> >>>>>
> >>>>>> 在 2017年6月24日，05:25，Michael André Pearce <
> michael.andre.pea...@me.com>
> >>>>> 写道：
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> As already been discussing in the Artemis mailing lists have some
> areas
> >>>>> we would like to contribute/commit in particular already looking at:
> >>>>>>
> >>>>>> JMSObject Custom serdes wrapper (with and avro serdes as initial
> >>>>> provided)
> >>>>>> Generic JMS Client side persistence
> >>>>>>
> >>>>>>
> >>>>>> Cheers
> >>>>>> Mike
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On 2017-06-22 04:39 (+0100), Atri Sharma wrote:
> >>>>>>> I would love to contribute.>
> >>>>>>>
> >>>>>>> On Jun 22, 2017 8:05 AM, "John D. Ament" wrote:>
> >>>>>>>
> >>>>>>>> All,>
> >>>>>>>>>
> >>>>>>>> There's an ongoing discussion on the ActiveMQ dev list [1] to
> spin up
> >>>>> a>
> >>>>>>>> project focused on core, reusable messaging components. The
> feeling
> >>> is>
> >>>>>>>> that this is outside the realm of Activ

Re: Granting access to Jenkins

[John D. Ament]

Thanks Andy.  I was just about to see if my karma now kicked in.

John

On Wed, Jun 28, 2017 at 6:04 AM Andy Seaborne  wrote:

> Done
>
> On 28/06/17 10:26, Henri Yandell wrote:
> > Could a PMC Chair type person grant access to Jenkins for Ly please
> (login
> > lxn2)?
> >
> >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount
> >
> > I gave it a shot, but I don't believe I have the correct permissions.
> >
> > Thank you,
> >
> > Hen
> >
>
> -
> 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 2.0.0 incubating (RC6)

[John D. Ament]

On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean 
wrote:

> Hi,
>
> +0 binding as I can’t build from source and no instructions provided.
>

I struggled with this a bit as well.  The BUILD.md indicates:

See the build instructions at ./docs/source/development/building.rst or at
http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html

That URL doesn't work, but the rst file indicates running pkg does the
build.

However, when I run pkg, I get the following:

~/Desktop/apache-trafficcontrol-2.0.0-incubating
☺  ./pkg



Building traffic_portal_build.
Building traffic_router_build.
Building traffic_monitor_build.
Building source.
Building traffic_ops_build.
Building traffic_stats_build.
Failed to build traffic_portal_build.


>
> I will change to +1 when I can compile/ you raise a JIRA to add
> instructions on how to build.
>
> I checked:
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE good
> - NOTICE OK . You can remove the information about the fonts in there it’s
> not needed.
> - No unexpected binary files
> - All source files have headers (there's a few script files and other
> files that could also have headers)
> - can't build from source
>
> when running the build.sh script it eventually fails with this error
>
> cp: ./build/*.spec: No such file or directory
> Could not copy spec files: 1
> traffic_stats failed:
> The following subdirectories had errors:
>traffic_monitor
>traffic_monitor_golang
>traffic_ops
>traffic_portal
>traffic_router
>traffic_stats
>
> Has perhaps something not been included in the release or is my
> environment not set up correctly?
>
> It would be nice to include the build instructions in the build itself. I
> believe this has come up before. By providing a URL it means that the
> content of that URL may change for future releases and people would be
> unable to build this release. In fact the URL in the documentation is
> incorrect [1] and currently 404s which is less than helpful.
>
> There a few file still copyright comcast I assume these need to be
> removed? [2][3][4][5][6]
>
> Thanks,
> Justin
>
> 1.
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> 3.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> 4.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> github.com/jheitz200/test_helper/http.go
> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> github.com/jheitz200/test_helper/test.go
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Gearpump (incubating) 0.8.4-RC1

[John D. Ament]

Hi,

I notice that your source license includes jquery, bootstrap but I can't
find those in your source release.

In your bin release, all of your license entries look
like licenses/LICENSE-[project].txt. but they should be valid paths.

John


On Tue, Jun 27, 2017 at 1:47 AM Karol Brejna  wrote:

> IPMC Community,
>
> The PPMC vote to release Apache Gearpump (incubating) 0.8.4-RC1 has passed.
> We would like to now submit this release candidate to the IPMC.
>
> The PPMC vote thread is here:
>
> https://lists.apache.org/thread.html/d04e30eec251c8f33f319e98d24a5cd2d3cc62455276d49719057c3f@%3Cdev.gearpump.apache.org%3E
>
> The source and binary tarballs, including signatures, digests, etc.
> can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/
>
> Release artifacts are signed with the key with fingerprint:
> 3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291
>
> The KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
>
> The tag to be voted upon is:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1
>
> The release hash is:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290
>
> For information about the contents of this release see:
> https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225
> Most changes are driven by Apache Beam integration.
>
>
> This vote will be open for at least 72 hours (Thursday, June 29, 2017
> at 11:00 PM PDT).
>
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, run the
> binary artifacts in the binary release and test.
> Please vote:
>
> [ ] +1 Release this package as gearpump-0.8.4
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thanks,
> Karol
>
> -
> 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 2.0.0 incubating (RC6)

[John D. Ament]

Hi Eric,

I see that a lot changed in the project as a part of this release.
Specifically I'm concerned about the over eager rat excludes.

- The Apache License v2 is not a software only license.  It also applies to
documentation, etc.  So feel free to add the header to .md files
- Minified files should include proper license headers
- Copyright dates should be ranges, so 2016-2017 or 2016,2017 are both
fine.

I'll continue to dig into the release tarball if you can comment on these
items (I'm not asking you to cut a new release, I'm asking for you to
comment on these only)

John

On Wed, Jun 21, 2017 at 5:05 PM Eric Friedrich  wrote:

> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a proposal
> to release Apache Traffic Control 2.0.0. We now kindly request that the
> Incubator PMC members review and vote on this incubator release.
>
>
> Changes since 1.8.1:
>
>
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC6
>
>
> This corresponds to git:
>
> Repo: https://github.com/apache/incubator-trafficcontrol
>
> Hash: 85d14ebe2a4ac71236f86f70349481d2b3dc784b
>
> Tag: RELEASE-2.0.0-RC6
>
> Which can be verified with the following:git tag -v RELEASE-2.0.0-RC6
>
>
> My code signing key is available from the following locations:
>
> http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
>
> The source .tar.gz file, pgp signature (.asc signed with my key from
> above), md5 and sha512 checksums are provided here:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC6
>
>
> Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/
>
>
> Build instructions are included in the BUILD.md file which is included in
> the source artifact.
>
>
> This vote will be open for at least 72 hours. Please review and vote:
>
> [ ] +1 Approve the release
>
> [ ] -1 Don't approve the release (please provide specific comments)
>
>
> We’ve taken IPMC feedback to change following since the recent 1.8.1 vote:
>
> - Modify release artifact filename to
> apache-trafficcontrol-2.0.0-incubating.tar.gz
>
> - Fix font licenses in LICENSE and NOTICE
>
>
> Thanks,
>
> Eric Friedrich 
>

Incubator PMC Board Report - Initial Reminder - July 2017

[John D. Ament]

July 2017 Incubator report timeline:

https://wiki.apache.org/incubator/July2017

Wed July 05 -- Podling reports due by end of day
Sun July 09 -- Shepherd reviews due by end of day
Sun July 09 -- Summary due by end of day
Tue July 11 -- Mentor signoff due by end of day
Wed July 12 -- Report submitted to Board
Wed July 19 -- Board meeting


I'll be traveling through the end of the US holiday, but think I have
report reminders working.

John

Re: couple issues with graduation doc

[John D. Ament]

On Mon, Jun 26, 2017 at 11:08 PM Greg Stein  wrote:

> On Mon, Jun 26, 2017 at 9:55 PM, John D. Ament 
> wrote:
>
> > Greg,
> >
> > On Mon, Jun 26, 2017 at 6:04 PM Greg Stein  wrote:
> >
> > > Hey all,
> > >
> > > There appears to be some confusion around graduation because the
> current
> > > doc[1] isn't very clear on the steps the new TLP needs to take.
> > >
> > > A big one is that the right INFRA tickets aren't being filed because
> > there
> > > isn't a pointer to the graduation servicedesk[2].
> > >
> >
> > From your POV, who is actually supposed to submit those tickets and when?
> > I had assumed the "Congratulations on your new role" email was the
> trigger
> > point, but that none of this should be done until a director presses the
> > button.
> >
>
> I would suggest anyone from the newly-graduated PMC should submit those
> tickets. We can easily de-dup if the PMC didn't deconflict on who would
> take point.
>
> The email you note is sent by the Secretary. Nominally, the Secretary also
> "presses the button" that informs Infra that X and Y have graduated, but
> that automated plumbing is a bit broken at the moment. No biggy, as Infra
> is always at the meetings, so we know who graduated (or not).
>
>
Hmm it seems like that's kind of a biggie.  Right now, there's no mention
to the graduated project they graduated outside of what secretary sends.
Seems like there should be something automated to notify the new PMC that
they are in fact a PMC.


> We do not expect the Secretary or Infra to file the graduation tickets.
> That is and has always been left to the community and its decision of
> timing.
>

Agreed.


>
> (a separate matter is de-incubation, which is out of our hands, and I would
> suggest is up to the IPMC to set policy, even against the timing wishes of
> the new TLP)
>

Unincubate never happens.  I've taken care of the last 6, either by
repeatedly emailing the TLPs or doing it myself.  I'm inclined to make
unincubate (via status file and podlings.xml) a chair responsibility.


>
> > A small one is that it talks about updating www.a.o front page with
> > > obsolete language about templates/blocks/projects.mdtext.
> > >
> > >
> > What page is that?
> >
>
> Same page [1].
>
> More specifically:
> http://incubator.apache.org/guides/graduation.html#transfer ... item 3.2.
>

So, that whole block just goes?  3.1.2 seems not needed either.  It seems
like a lot of those sections are irrelevant since podlings are effectively
TLPs with double host names (podling.a.o and podling.i.a.o).  None of that
stuff moves.

I do think we need a section on how to create the TLP request ticket.


>
> And I just realized that item 6 is wrong, as we just went through this
> today for another TLP. Infra will "svn mv" the dev/release areas from
> dist/incubator/ to dist/${TLP}/ ... so no cleanup is needed since it is
> moved.
>
> > Could somebody fix up the doc?
>

I created https://issues.apache.org/jira/browse/INCUBATOR-202 to track.
I'm not going to do any more maintenance on the current website, planning
to instead cut over to the new one and make enhancements there.


> > >
> > > Thanks,
> > > -g
> > >
> > > [1]
> > >
> http://incubator.apache.org/guides/graduation.html#life-after-graduation
> > > [2] https://issues.apache.org/jira/servicedesk/customer/
> > portal/1/group/12
> > >
> >
>
> Cheers,
> -g
>

[jira] [Created] (INCUBATOR-202) Graduation steps guide enhancements

[John D. Ament (JIRA)]

John D. Ament created INCUBATOR-202:
---

 Summary: Graduation steps guide enhancements
 Key: INCUBATOR-202
 URL: https://issues.apache.org/jira/browse/INCUBATOR-202
 Project: Incubator
  Issue Type: Improvement
Reporter: John D. Ament


Related to this section:

- Clarify that anyone from the new PMC can create the infra tickets.  This 
should happen after its clear that the resolution was accepted.
- Direct users to use Service Desk for ticket creation
- Most of 3.1 needs to be removed, as TLPs don't have incubator.a.o domains
- All of 3.2 can be removed
- Section 6, infra does a move so just create a ticket.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Re: couple issues with graduation doc

[John D. Ament]

Greg,

On Mon, Jun 26, 2017 at 6:04 PM Greg Stein  wrote:

> Hey all,
>
> There appears to be some confusion around graduation because the current
> doc[1] isn't very clear on the steps the new TLP needs to take.
>
> A big one is that the right INFRA tickets aren't being filed because there
> isn't a pointer to the graduation servicedesk[2].
>

>From your POV, who is actually supposed to submit those tickets and when?
I had assumed the "Congratulations on your new role" email was the trigger
point, but that none of this should be done until a director presses the
button.


>
> A small one is that it talks about updating www.a.o front page with
> obsolete language about templates/blocks/projects.mdtext.
>
>
What page is that?


> Could somebody fix up the doc?
>
> Thanks,
> -g
>
> [1]
> http://incubator.apache.org/guides/graduation.html#life-after-graduation
> [2] https://issues.apache.org/jira/servicedesk/customer/portal/1/group/12
>

[VOTE] Retire Sirona

[John D. Ament]

All,

This is a call to vote the Sirona podling.

A vote was called for on the dev list for Sirona [1], of which one mentor
commented and that's all.

Sirona at this point is behind 6 months on reports, has shown little
activity since joining the incubator.  Its not clear there are 3 PPMCs
available for a vote if need be.  Based on the prior discussions ([2] &
[3]) and these items, I'd like to call for a vote and unilateral decision
by the IPMC to retire Sirona.

[ ] +1 to retire Sirona
[ ] -1 don't retire Sirona because...

Here is my +1.

John

[1]:
https://lists.apache.org/thread.html/673daa1452150ed5ef0df4aa77f587dbac6e5a4a63670c6bf4809b17@%3Cdev.sirona.apache.org%3E
[2]:
https://lists.apache.org/thread.html/0a70d486680f0339bfcb4baae23c2540095fda90ca83eb414104a6fd@%3Cgeneral.incubator.apache.org%3E
[3]:
https://lists.apache.org/thread.html/438298290de9a3573b5e315b12e77191b27f8d91b50cf9f97e90cba8@%3Cgeneral.incubator.apache.org%3E

Re: Seeking interested parties for a messaging components podling

[John D. Ament]

All,

I've dropped in the proposal template to
https://wiki.apache.org/incubator/MessagingComponentsProposal - we can
rename it later if we come up with a better name.  I'd encourage those
interested in the project to start to form out this proposal so we can
start to shape the who, the why and the what.  If you need access to the
incubator wiki, first register then email on here asking to gain access.
Include your username.

John

On Sun, Jun 25, 2017 at 9:17 PM Von Gosling  wrote:

> Hi john,
>
> I am very interested in participate in such a podling personally. as for
> RocketMQ community, imo, we will start a thread to discussion this idea :-)
>
> Best Regards,
> Von Gosling
>
>
> > 在 2017年6月24日，22:17，John D. Ament  写道：
> >
> > Hi Von Gosling,
> >
> > So I just want to check, is this an indication that there may be interest
> > from the RocketMQ community to participate in such a podling?
> >
> > John
> >
> > On Fri, Jun 23, 2017 at 9:35 PM Von Gosling 
> wrote:
> >
> >>
> >> Hi,
> >>
> >>
> >> I am not sure your mention is Apache RocketMQ. In RocketMQ, jms
> >> integration is just a adaptor, while not fully support JMS 1.1 and JMS
> 2.0
> >> specification.
> >>
> >> IMO, that’s a good idea. if we messaging engines can collaborate to some
> >> common components, such as benchmark, common api specification, wire
> >> protocol bridge and so on.
> >>
> >> Indeed, we have drafted some api specification(OpenMessaging) about
> >> messaging and streaming fields[1], welcome any idea about it :-)
> >>
> >>
> >> [1] https://openmessaging.github.io/ <https://openmessaging.github.io/>
> >>
> >> Best Regards,
> >> Von Gosling
> >>
> >>
> >>> 在 2017年6月24日，05:25，Michael André Pearce 
> >> 写道：
> >>>
> >>> Hi,
> >>>
> >>> As already been discussing in the Artemis mailing lists have some areas
> >> we would like to contribute/commit in particular already looking at:
> >>>
> >>> JMSObject Custom serdes wrapper (with and avro serdes as initial
> >> provided)
> >>> Generic JMS Client side persistence
> >>>
> >>>
> >>> Cheers
> >>> Mike
> >>>
> >>>
> >>>
> >>> On 2017-06-22 04:39 (+0100), Atri Sharma wrote:
> >>>> I would love to contribute.>
> >>>>
> >>>> On Jun 22, 2017 8:05 AM, "John D. Ament" wrote:>
> >>>>
> >>>>> All,>
> >>>>>>
> >>>>> There's an ongoing discussion on the ActiveMQ dev list [1] to spin up
> >> a>
> >>>>> project focused on core, reusable messaging components. The feeling
> is>
> >>>>> that this is outside the realm of ActiveMQ for various reasons and
> >> could be>
> >>>>> leveraged by various messaging platforms, potentially even building
> >> out>
> >>>>> some reusability and core protocol support along the ways.>
> >>>>>>
> >>>>> Knowing that we have some messaging experience within the incubator,
> I>
> >>>>> wanted to prod around a bit to see if there was anyone else
> interested
> >> in a>
> >>>>> project like this.>
> >>>>>>
> >>>>> John>
> >>>>>>
> >>>>> PS - when I say interested parties, it could be>
> >>>>> champions/mentors/contributors or heck even possible TLP sponsors.>
> >>>>>>
> >>>>> [1]:>
> >>>>> https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c37>
> >>>>> 3e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E>
> >>>>>>
> >>>>
> >>>
> >>>
> >>> Sent from my iPad
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> <mailto:general-unsubscr...@incubator.apache.org>
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >> <mailto: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: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

On Thu, Jun 22, 2017 at 12:50 PM Patrick Hunt  wrote:

> On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament 
> wrote:
>
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
> >
> > - Roll out a new technology stack + repository
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> > future.
> >
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> > The git repository for the site can be seen here:
> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> > shortlog;h=refs/heads/jbake-site
> > (with
> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
> >
> > I'd like to get some final feedback on the layout and colors (not the
> > content).  I want to start tracking content enhancements in JIRA to help
> > come up with a backlog of areas of improvement for our incubator guides.
> >
> >
> I'm very familiar with the old layout, so this may be coloring my feedback.
> However I find the new layout to be less usable than previous. In
> particular the drop downs lack structure. I think it would be better to
> focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
> docs, or "graduating a podingling" etc... - basically focus around the
> lifecycle of podling rather than a big long list of "guides". Additionally
> it's hard to find things with the new layout, I used to use the browser
> "search" feature to narrow down to a particular doc. Now I need to click on
> each of the drop downs to find the content I'm looking for. Additionally
> things like wiki/faq/etc... - can't find them at all.
>
>
Hi Patrick,

Thanks for the input.  I've started to add it to the new version, let me
know your thoughts.  There's still a few areas to tweak, but definitely
keep it coming.

I have to still add a link to google search.

John


> Patrick
>
>
> > John
> >
>

Re: Seeking interested parties for a messaging components podling

[John D. Ament]

Hi Von Gosling,

So I just want to check, is this an indication that there may be interest
from the RocketMQ community to participate in such a podling?

John

On Fri, Jun 23, 2017 at 9:35 PM Von Gosling  wrote:

>
> Hi,
>
>
> I am not sure your mention is Apache RocketMQ. In RocketMQ, jms
> integration is just a adaptor, while not fully support JMS 1.1 and JMS 2.0
> specification.
>
> IMO, that’s a good idea. if we messaging engines can collaborate to some
> common components, such as benchmark, common api specification, wire
> protocol bridge and so on.
>
> Indeed, we have drafted some api specification(OpenMessaging) about
> messaging and streaming fields[1], welcome any idea about it :-)
>
>
> [1] https://openmessaging.github.io/ <https://openmessaging.github.io/>
>
> Best Regards,
> Von Gosling
>
>
> > 在 2017年6月24日，05:25，Michael André Pearce 
> 写道：
> >
> > Hi,
> >
> > As already been discussing in the Artemis mailing lists have some areas
> we would like to contribute/commit in particular already looking at:
> >
> > JMSObject Custom serdes wrapper (with and avro serdes as initial
> provided)
> > Generic JMS Client side persistence
> >
> >
> > Cheers
> > Mike
> >
> >
> >
> > On 2017-06-22 04:39 (+0100), Atri Sharma wrote:
> >> I would love to contribute.>
> >>
> >> On Jun 22, 2017 8:05 AM, "John D. Ament" wrote:>
> >>
> >>> All,>
> >>>>
> >>> There's an ongoing discussion on the ActiveMQ dev list [1] to spin up
> a>
> >>> project focused on core, reusable messaging components. The feeling is>
> >>> that this is outside the realm of ActiveMQ for various reasons and
> could be>
> >>> leveraged by various messaging platforms, potentially even building
> out>
> >>> some reusability and core protocol support along the ways.>
> >>>>
> >>> Knowing that we have some messaging experience within the incubator, I>
> >>> wanted to prod around a bit to see if there was anyone else interested
> in a>
> >>> project like this.>
> >>>>
> >>> John>
> >>>>
> >>> PS - when I say interested parties, it could be>
> >>> champions/mentors/contributors or heck even possible TLP sponsors.>
> >>>>
> >>> [1]:>
> >>> https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c37>
> >>> 3e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E>
> >>>>
> >>
> >
> >
> > Sent from my iPad
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> <mailto:general-unsubscr...@incubator.apache.org>
> > For additional commands, e-mail: general-h...@incubator.apache.org
> <mailto:general-h...@incubator.apache.org>
>

[NOTICE] Clutch is moving

[John D. Ament]

All,

In preparation for moving to the new website, I'm cleaning up anything that
is important that may be hosted directly in /.  Since I plan to cut the new
website over piece by piece, I need to get those critical components into
their own directories.  clutch appears to be the only outlier, and is now
incubator.apache.org/clutch instead of incubator.apache.org/clutch.html

John

Re: [RESULT][VOTE] Heron to enter Apache Incubator

[John D. Ament]

On Fri, Jun 23, 2017 at 5:10 PM Bill Graham  wrote:

> Dear Incubator members,
>
> This vote has passed with the following result:
>
> 24 [+1] votes (8 binding, 16 non-binding)
>
> Binding Votes:
> 
>
> Julien Le Dem
> Raphael Bircher
> Jake Farrell
> Jacques Nadeau
> Julian Hyde
> Chris Douglas
> John Ament
> P. Taylor Goetz
>
> Non-binding Votes:
> 
>
> Debo Dutta
> William Markito Oliveira
> Roy Lenferink
> Sijie Guo
> Sanjeev Kulkarni
> Chris Aniszczyk
> Supun Kamburugamuva
> Jia Zhai
> Karthi Ramasamy
> Ashvin A
> Ashish
> Nabarun Nag
> Pierre Smits
> Byung-Gon Chun
> Bill Graham
> Van Gosling
>
> Vote thread:
> https://lists.apache.org/thread.html/767b502a7cb698cc509c5f79835db6
> 1effc89cb80baec46a52359554@%3Cgeneral.incubator.apache.org%3E
>
> I will start the process for getting the SGA submitted.
>

Sounds good.  I'll be curious to see how the SGA notes the existing code
from other projects (which should be excluded).  Its a general curiosity of
mine.

Meanwhile, your mentors will want to get your mailing lists setup so people
can start migrating there.  I see no reason for you to request repositories
outside of a website before then.


>
> thanks,
> Bill
>

Re: [VOTE] Heron to enter Apache Incubator

[John D. Ament]

Based on the additional comments, I'm OK with this continuing graduation.
I would like the proposed podling to undertake a specific task to ensure
its clear what is different between Storm and Heron, to avoid any
unexpected competition or user confusion.

John

On Fri, Jun 23, 2017 at 12:32 PM Julien Le Dem 
wrote:

> Hi Edward,
>
> A better comparison is SQL. Heron provides an implementation of the Storm
> topology api just like a query engine would implement SQL.
> It is a statement to the Storm API that it became a reference for
> streaming. This is the shared component and I agree that both projects
> should collaborate around it.
>
> The proposal already has a statement of cooperation: *"We believe that
> having Heron at Apache will help further the growth of the streaming
> compute community, as well as encourage cooperation and developer cross
> pollination with other Apache projects."*
> If Heron started at Twitter it has now contributors from more companies. In
> particular Microsoft which has been presenting this work in conferences.
> Joining the incubator is also about growing the community. Diversity is a
> goal but not a requirement to enter the incubator. Many successful projects
> have started with a little diversity and grown.
> Heron is its own project, different form Storm both in the programming
> language used and the deployment approach.
>
> This is not a new situation, the Apache foundation has Thrift and Avro,
> Parquet and ORC to name a few competing projects that address similar needs
> with a different approach each with their own strengths and weaknesses.
>
> Your concerns are valid and should be addressed during incubation (ensuring
> cross project collaboration, building more diversity, ...)
>
> On Fri, Jun 23, 2017 at 6:54 AM, Edward Capriolo 
> wrote:
>
> > "The only overlap is that Heron supports the Storm user API for ease of
> > migration."
> >
> > It sounds possible possible that storm could be one user facing API with
> > two back ends inside one project.
> >
> > "Accumulo vs HBase" I do not think Accumulo and HBase is a valid
> comparison
> > one did not start out to emulate or be compatible with the other.
> >
> > In any case the largest issue I see is community. The proposed Heron
> > committer list is mostly a single company. Storm has already established
> a
> > community
> > with diverse committers. Also in terms of adoption, suppose you are a
> Storm
> > user do you run Heron side by side? Suppose your a vendor that packages
> > Hadoop and friends do you ship
> > both? Suppose you provide a no-sql database do you manage (test,
> document)
> > a connector for Heron and Storm? In my experience it is not trivial to
> keep
> > something working for example AbcBolt across Storm versions now that
> matrix
> > would double.
> >
> > I wish their was a stronger statement of cooperation in the proposal, for
> > example, "We with to establish a middle ground repo with shared
> components
> > etc". If nothing is shared other than a mentor or PMC your could run
> > into "software
> > X is the fasted way to run your storm bolts and spouts because of our
> > special sauce software Y does not have" and "software x is 2.2 years
> behind
> > the api of software Y they only implement and test 10% of the spouts we
> > support"
> >
> >
> > On Fri, Jun 23, 2017 at 8:08 AM, John D. Ament 
> > wrote:
> >
> > > Bill,
> > >
> > > Would I be correct in understanding that Heron implements the same
> > protocol
> > > as Storm, but the actual implementation is different?
> > >
> > > John
> > >
> > > On Fri, Jun 23, 2017 at 1:36 AM Bill Graham 
> > wrote:
> > >
> > > > It's grossly inaccurate to refer to Heron as a Storm fork. There are
> > > about
> > > > 132k lines of code in the Heron codebase (plus 166k of codegen), of
> > which
> > > > about 7k are to implement the Apache Storm API bindings to the Heron
> > API.
> > > >
> > > > The Rationale section of the proposal discusses the Heron
> architecture,
> > > > which is a complete rewrite with little in common with Storm. The
> only
> > > > overlap is that Heron supports the Storm user API for ease of
> > migration.
> > > >
> > > > The value of having multiple projects to solve a common need is that
> > each
> > > > can foster innovation, collaboration and exchange of ideas in
> d

Re: [VOTE] Heron to enter Apache Incubator

[John D. Ament]

Bill,

Would I be correct in understanding that Heron implements the same protocol
as Storm, but the actual implementation is different?

John

On Fri, Jun 23, 2017 at 1:36 AM Bill Graham  wrote:

> It's grossly inaccurate to refer to Heron as a Storm fork. There are about
> 132k lines of code in the Heron codebase (plus 166k of codegen), of which
> about 7k are to implement the Apache Storm API bindings to the Heron API.
>
> The Rationale section of the proposal discusses the Heron architecture,
> which is a complete rewrite with little in common with Storm. The only
> overlap is that Heron supports the Storm user API for ease of migration.
>
> The value of having multiple projects to solve a common need is that each
> can foster innovation, collaboration and exchange of ideas in different
> ways. This is not a new concept to Apache. You can look at the incubator
> discussions around Accumulo vs HBase (two implementations of the BigTable
> paper) for example, to see how two different approaches to a shared problem
> can be a good thing.
>
> thanks,
> Bill
>
> On Thu, Jun 22, 2017 at 6:45 PM, Von Gosling 
> wrote:
>
> > Hi,
> >
> > I will give +1(Non-binding), but,
> >
> > I have the similar question about so many streaming framework in the
> > apache, how to develop community for themselves.
> >
> >
> >
> >
> > Best Regards,
> > Von Gosling
> >
> >
> >
> > 在 2017年6月23日，08:51，Edward Capriolo  写道：
> >
> > I believe heron and storm should be merged back together. I do not see
> the
> > value of storm and a storm fork in the asf.
> >
> > On Thursday, June 22, 2017, Bill Graham  wrote:
> >
> > Thanks Taylor for relaying these sentiments, especially the part about
> the
> > Heron website which is indeed poorly worded (I suspect this could have
> been
> > the result of internal docs being open-sourced). I've opened this pull
> > request to update the language regarding Storm:
> >
> > https://github.com/twitter/heron/pull/1979
> >
> > On Thu, Jun 22, 2017 at 12:21 PM, P. Taylor Goetz  > > wrote:
> >
> > The Apache Storm PMC had a discussion regarding the Heron proposal. In
> >
> > the
> >
> > spirit of openness I wanted to bring some of the sentiments expressed in
> > that discussion back to this list. Please note that I am paraphrasing
> >
> > from
> >
> > that discussion and attempting to relay opinions of the collective PMC,
> >
> > not
> >
> > necessarily that of any individual.
> >
> > * There is a general disappointment that the Heron community chose not to
> > engage with the Storm community and instead chose a separate path.
> > * A majority of the PMC supports Heron’s incubation, though some felt it
> > would result in unnecessary duplication of effort.
> > * A majority of the PMC supports the two projects working closely
> > together. A number of PMC members suggested the two projects merge in
> >
> > some
> >
> > way.
> > * Many PMC members took issue some of the marketing language on the Heron
> > website, particularly Heron being billed as “the direct successor to
> >
> > Apache
> >
> > Storm” and the prominent “Upgrade from Storm” links.  The main concern
> >
> > here
> >
> > was such phrasing has somewhat of a hostile tone and undermines the
> >
> > desire
> >
> > for better collaboration, as well as confusing users.
> >
> > One of my goals as a proposed mentor for Heron and a Storm PMC member is
> > to address some of these concerns and encourage collaboration. As I
> > mentioned to the Storm PMC on that thread, if there are ongoing concerns
> > from either the Storm PMC or the Heron PPMC about me acting as a mentor,
> >
> > I
> >
> > would be willing to step down.
> >
> > +1 (binding)
> >
> > -Taylor
> >
> > On Jun 16, 2017, at 4:41 PM, Bill Graham  >
> > > wrote:
> >
> >
> > Hi,
> >
> > Based on the discussion on the incubator mailing list[1] I would like
> >
> > to
> >
> > call a vote to add Heron to the Apache Incubator.
> >
> > The full proposal is available below, and is also available on the
> >
> > Apache
> >
> > Incubator wiki at:
> >   https://wiki.apache.org/incubator/HeronProposal
> >
> > Please vote:
> > [ ] +1, bring Heron into Incubator
> > [ ] -1, do not bring Heron into Incubator, because...
> >
> > The vote will open for 7 days until Friday June 23 at 14:00 PT.
> >
> > Thank you
> >
> > 1 -
> > https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7
> >
> > 786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
> >
> >
> >
> >
> > = Heron Proposal =
> >
> > = Abstract =
> > Heron is a real-time, distributed, fault-tolerant stream processing
> >
> > engine
> >
> > initially developed by Twitter.
> >
> > = Proposal =
> >
> > Heron is a real-time stream processing engine built for high
> >
> > performance,
> >
> > ease of manageability, performance predictability and developer
> > productivity[1]. We wish to develop a community around Heron to
> >
> > increase
> >
> > contributions and see Heron thrive in an open forum.
> >
> > = Background =
> >
> > Heron provide

Re: [VOTE] Heron to enter Apache Incubator

[John D. Ament]

All,

I'm requesting that the community holds on closing this vote for a few
extra days to address concerns raised by the Storm community and others.

Please don't interpret this as a -1, but do interpret it as a need for some
extra due dilligence due to code usage from Apache Storm within Heron.

John

On Sun, Jun 18, 2017 at 6:35 AM John D. Ament  wrote:

> +1, however a few things to note about the proposal (and follow up will be
> required when bringing Heron in):
>
> - There is no ASF 2.0 license (missed when putting together the proposal)
> - The IP section doesn't mention anything about a SGA being sent, is your
> intention to not send an SGA?
> - The NOTICE for the repo indicates there is some source code from Yahoo!.
>
> - The contents of https://github.com/twitter/heron/tree/master/third_party 
> seems
> to be mostly binary files, and you'll need to clean that up for your first
> release.
> - Your 3rd party section mentions everything is ASF 2.0, however this
> includes glog and similar tools that include an odd buildchain license that
> is actually GPL, we'll need to get clearance if this is actually compliant
> or not.  Some of the contents in third_party are missing license headers.
>
> John
>
>
> On Fri, Jun 16, 2017 at 4:41 PM Bill Graham  wrote:
>
>> Hi,
>>
>> Based on the discussion on the incubator mailing list[1] I would like to
>> call a vote to add Heron to the Apache Incubator.
>>
>> The full proposal is available below, and is also available on the Apache
>> Incubator wiki at:
>> https://wiki.apache.org/incubator/HeronProposal
>>
>> Please vote:
>>   [ ] +1, bring Heron into Incubator
>>   [ ] -1, do not bring Heron into Incubator, because...
>>
>> The vote will open for 7 days until Friday June 23 at 14:00 PT.
>>
>> Thank you
>>
>> 1 -
>>
>> https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
>>
>>
>>
>> = Heron Proposal =
>>
>> = Abstract =
>> Heron is a real-time, distributed, fault-tolerant stream processing engine
>> initially developed by Twitter.
>>
>> = Proposal =
>>
>> Heron is a real-time stream processing engine built for high performance,
>> ease of manageability, performance predictability and developer
>> productivity[1]. We wish to develop a community around Heron to increase
>> contributions and see Heron thrive in an open forum.
>>
>> = Background =
>>
>> Heron provides the ability for developers to compose directed acyclic
>> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
>> submit the topology to execute on a pluggable job scheduling system (e.g.,
>> Apache Aurora, YARN, Marathon, etc). Users can employ either the native
>> Heron API or the Apache Storm API to develop the topology. Heron supports
>> the Storm API for ease of migration, but beyond that Heron’s architecture
>> differs considerably from Storm’s.
>>
>> Users submit a topology to the scheduler using the Heron client, which
>> uses
>> the Heron binary libraries to deploy all daemons required to run and
>> manage
>> the topology. The topology therefore has no reliance on centrally managed
>> Heron services, only on a generic job scheduling system, which lends
>> itself
>> well to be run on top of Apache Aurora/Mesos or Apache Hadoop/YARN (among
>> others).
>>
>> The scheduler runs each topology as a job consisting of multiple
>> containers. One of the containers runs the topology master, responsible
>> for
>> managing the topology. The remaining containers each runs a stream manager
>> responsible for data routing, a metrics manager that collects and reports
>> various metrics and a number of processes called Heron instances which run
>> the user-defined logic on the stream of tuples. Parallelism is achieved
>> via
>> process-based isolation of Heron instances, which provides predictable
>> performance while simplifying debugging. The containers are allocated and
>> managed by the scheduler framework based on resource availability of nodes
>> in the cluster. The metadata for the topology, such as the physical plan
>> and execution details, are stored in the pluggable Heron State Manager
>> (e.g. Apache ZooKeeper).
>>
>> = Rationale =
>>
>> Heron is a general-purpose, modular and extensible platform that can be
>> leveraged to support common, real-time analytics use cases. There is an
>> increasing demand for open-source, scalable real-time analytics systems.

Re: [VOTE] Release Apache Juneau 6.3.0-incubating-RC1

[John D. Ament]

Copying my +1 from dev list.

John

On Thu, Jun 22, 2017 at 9:44 AM James Bognar  wrote:

> The Apache Juneau Incubator PPMC has voted +3 to release Apache Juneau
> 6.3.0-incubating RC1. This vote carries over +1 binding vote from IPMC
> members.
>
> John D. Ament
>
> Incubator PMC members please review and vote on this incubator release.
> Apache Juneau is...
>
>- A toolkit for marshalling POJOs to a wide variety of content types
>using a common framework.
>- A REST server API for creating self-documenting REST interfaces using
>POJOs.
>- A REST client API for interacting with REST interfaces using POJOs.
>- A REST microservice API that combines all the features above for
>creating lightweight standalone REST interfaces that start up in
>milliseconds.
>
>
> Please see original [VOTE] thread:
>
> https://lists.apache.org/thread.html/21d28dd4d82279df6cc53e64561276a4f076783a0199b82ba99e4ecb@%3Cdev.juneau.apache.org%3E
>
> We've introduced some significant new enhancements to support new use cases
> in Apache Streams. The full list of changes can be viewed here:
> http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#6.3.0
>
> The binaries are available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/juneau/binaries/juneau-6.3.0-incubating-RC1/
>
> The release candidate to be voted over is available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/juneau/source/juneau-6.3.0-incubating-RC1/
>
> Build the release candidate using:
> mvn clean install
>
> Note:  You may get a Rat failure on a generated DEPENDENCIES file.  This
> can be ignored and will be fixed in 6.3.1.
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachejuneau-1012/
>
> Please vote on releasing these packages as:
> Apache Juneau 6.3.0-incubating
>
> This vote will be open until 27-June-2017 1:00pm GMT.
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>

[RESULT] (was Re: [VOTE] Retire the Blur Podling)

[John D. Ament]

With 5 +1 binding and 1 +1 the vote to retire Blur has passed, in addition
to the 3 binding votes on the dev list.  I'll begin the process in coming
days.

John

On Sun, Jun 18, 2017 at 12:30 PM John D. Ament 
wrote:

> All,
>
> This is a call to vote to retire the Blur podling.  Blur has been
> incubating for nearly 5 years and has not grown a community.  It is
> mutually felt that it is time to retire Blur.  There was a successful vote
> on the podling's dev list at [1].  I'm now calling for the Incubator vote
> on the same subject.
>
> [ ] +1 to retire Blur
> [ ] -1 Don't retire Blur because...
>
> Here is my own +1
>
> John
>
> [1]:
> https://lists.apache.org/thread.html/d6e8050a0f94fd9871e69a529d50690c639c9aa0f5d27ef8b52109c1@%3Cblur-dev.incubator.apache.org%3E
>

Seeking interested parties for a messaging components podling

[John D. Ament]

All,

There's an ongoing discussion on the ActiveMQ dev list [1] to spin up a
project focused on core, reusable messaging components.  The feeling is
that this is outside the realm of ActiveMQ for various reasons and could be
leveraged by various messaging platforms, potentially even building out
some reusability and core protocol support along the ways.

Knowing that we have some messaging experience within the incubator, I
wanted to prod around a bit to see if there was anyone else interested in a
project like this.

John

PS - when I say interested parties, it could be
champions/mentors/contributors or heck even possible TLP sponsors.

[1]:
https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c373e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E

Re: [VOTE] Apache Fluo Recipes 1.1.0-incubating (rc1)

[John D. Ament]

+1 to release.

On Mon, Jun 19, 2017 at 1:49 PM Keith Turner  wrote:

> Dear IPMC,
>
> Please vote for the following release candidate of Apache Fluo Recipes
> 1.1.0-incubating.
>
> PPMC vote threads:
>
> https://lists.apache.org/thread.html/4c99f51ef5302506f518d692ff9d65a188027aadc93ba648a75682df@%3Cdev.fluo.apache.org%3E
>
> https://lists.apache.org/thread.html/4db5c8ed71d070506f26509890d0e1bdba921570f569b236acce94f9@%3Cdev.fluo.apache.org%3E
>
> Staged dist artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo-recipes/1.1.0-incubating-rc1/
>
> Staged Maven repository:
> https://repository.apache.org/content/repositories/orgapachefluo-1018
>
> Signing KEYS:
> https://www.apache.org/dist/incubator/fluo/KEYS
> (fingerprint for this release: CF72CA07C8BC86A1C862765F9AACFB56352ACF76)
>
> Git repo:
> https://gitbox.apache.org/repos/asf/incubator-fluo-recipes
> (branch: 1.1.0-incubating-rc1,
> commit: 4769fa9a3a43af030de318c0423a7cae5c5eb4fe)
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Thanks,
> The Apache Fluo Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Looking for GPG key signers in Boston area

[John D. Ament]

Is there a guide you're getting that from?  When I look at [1] it seems we
trust the public registries, so nothing else should be needed.

John

[1]: https://www.apache.org/info/verification.html


On Mon, Jun 19, 2017 at 1:28 PM Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:

> Thanks John-
>   My key is already listed there and is present in the KEYS file as well.
>
> Doesn’t the key also need to be verified by others at Apache to be
> considered valid?
>
> —Eric
>
> > On Jun 19, 2017, at 1:12 PM, John D. Ament 
> wrote:
> >
> > I think all you have to do is upload it via https://pgp.mit.edu/
> ...
> >
> > John
> >
> > On Mon, Jun 19, 2017 at 1:11 PM Eric Friedrich (efriedri) <
> > efrie...@cisco.com> wrote:
> >
> >> Apologies for this slightly unorthodox use of the mailer.
> >>
> >> I’m in the process of preparing a release for the Traffic Control
> podling.
> >> As the RM, I have to use my GPG key to sign the release.
> >>
> >> However, my GPG key is not yet tied into the web of trust and we cannot
> >> pass the vote because of this.
> >>
> >> Is there anyone in the Boston area (preferably South or metro-west) that
> >> would be willing to meet and verify my key ownership?
> >>
> >> Thanks!
> >> Eric
> >>
> >>
>
>

Re: Looking for GPG key signers in Boston area

[John D. Ament]

I think all you have to do is upload it via https://pgp.mit.edu/ ...

John

On Mon, Jun 19, 2017 at 1:11 PM Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:

> Apologies for this slightly unorthodox use of the mailer.
>
> I’m in the process of preparing a release for the Traffic Control podling.
> As the RM, I have to use my GPG key to sign the release.
>
> However, my GPG key is not yet tied into the web of trust and we cannot
> pass the vote because of this.
>
> Is there anyone in the Boston area (preferably South or metro-west) that
> would be willing to meet and verify my key ownership?
>
> Thanks!
> Eric
>
>

Re: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Sat, Jun 17, 2017 at 2:35 PM, John D. Ament 
> wrote:
> > ...The git repository for the site can be seen here:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
> ...
>
> Just one detail, I'm also working on converting the Sling site to
> JBake [1] and like the Tamaya podling website did I have included
> JBake in a ./bin folder to make it easier for everybody to use the
> same version.
>
>
I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
buildbot slaves are coming next.  Not sure if that's of interest to you.
The Tamaya guys are who introduced me to JBake.


> -Bertrand
>
> [1] https://issues.apache.org/jira/browse/SLING-6955 - repo will be at
> https://git-wip-us.apache.org/repos/asf?p=sling-sling-site.git soon
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Retire the Blur Podling

[John D. Ament]

All,

This is a call to vote to retire the Blur podling.  Blur has been
incubating for nearly 5 years and has not grown a community.  It is
mutually felt that it is time to retire Blur.  There was a successful vote
on the podling's dev list at [1].  I'm now calling for the Incubator vote
on the same subject.

[ ] +1 to retire Blur
[ ] -1 Don't retire Blur because...

Here is my own +1

John

[1]:
https://lists.apache.org/thread.html/d6e8050a0f94fd9871e69a529d50690c639c9aa0f5d27ef8b52109c1@%3Cblur-dev.incubator.apache.org%3E

Re: [VOTE] Heron to enter Apache Incubator

[John D. Ament]

+1, however a few things to note about the proposal (and follow up will be
required when bringing Heron in):

- There is no ASF 2.0 license (missed when putting together the proposal)
- The IP section doesn't mention anything about a SGA being sent, is your
intention to not send an SGA?
- The NOTICE for the repo indicates there is some source code from Yahoo!.
- The contents of
https://github.com/twitter/heron/tree/master/third_party seems
to be mostly binary files, and you'll need to clean that up for your first
release.
- Your 3rd party section mentions everything is ASF 2.0, however this
includes glog and similar tools that include an odd buildchain license that
is actually GPL, we'll need to get clearance if this is actually compliant
or not.  Some of the contents in third_party are missing license headers.

John

On Fri, Jun 16, 2017 at 4:41 PM Bill Graham  wrote:

> Hi,
>
> Based on the discussion on the incubator mailing list[1] I would like to
> call a vote to add Heron to the Apache Incubator.
>
> The full proposal is available below, and is also available on the Apache
> Incubator wiki at:
> https://wiki.apache.org/incubator/HeronProposal
>
> Please vote:
>   [ ] +1, bring Heron into Incubator
>   [ ] -1, do not bring Heron into Incubator, because...
>
> The vote will open for 7 days until Friday June 23 at 14:00 PT.
>
> Thank you
>
> 1 -
>
> https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
>
>
>
> = Heron Proposal =
>
> = Abstract =
> Heron is a real-time, distributed, fault-tolerant stream processing engine
> initially developed by Twitter.
>
> = Proposal =
>
> Heron is a real-time stream processing engine built for high performance,
> ease of manageability, performance predictability and developer
> productivity[1]. We wish to develop a community around Heron to increase
> contributions and see Heron thrive in an open forum.
>
> = Background =
>
> Heron provides the ability for developers to compose directed acyclic
> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
> submit the topology to execute on a pluggable job scheduling system (e.g.,
> Apache Aurora, YARN, Marathon, etc). Users can employ either the native
> Heron API or the Apache Storm API to develop the topology. Heron supports
> the Storm API for ease of migration, but beyond that Heron’s architecture
> differs considerably from Storm’s.
>
> Users submit a topology to the scheduler using the Heron client, which uses
> the Heron binary libraries to deploy all daemons required to run and manage
> the topology. The topology therefore has no reliance on centrally managed
> Heron services, only on a generic job scheduling system, which lends itself
> well to be run on top of Apache Aurora/Mesos or Apache Hadoop/YARN (among
> others).
>
> The scheduler runs each topology as a job consisting of multiple
> containers. One of the containers runs the topology master, responsible for
> managing the topology. The remaining containers each runs a stream manager
> responsible for data routing, a metrics manager that collects and reports
> various metrics and a number of processes called Heron instances which run
> the user-defined logic on the stream of tuples. Parallelism is achieved via
> process-based isolation of Heron instances, which provides predictable
> performance while simplifying debugging. The containers are allocated and
> managed by the scheduler framework based on resource availability of nodes
> in the cluster. The metadata for the topology, such as the physical plan
> and execution details, are stored in the pluggable Heron State Manager
> (e.g. Apache ZooKeeper).
>
> = Rationale =
>
> Heron is a general-purpose, modular and extensible platform that can be
> leveraged to support common, real-time analytics use cases. There is an
> increasing demand for open-source, scalable real-time analytics systems. We
> believe that Heron can be leveraged by other organizations to build
> streaming applications that can benefit from its robustness, high
> performance, adaptability to cloud environments and ease of use. Moreover,
> we hope that open-sourcing Heron will help to further evolve the technology
> as the project attracts contributors with diverse backgrounds and areas of
> expertise.
>
> We believe the Apache foundation is a great fit as the long-term home for
> Heron, as it provides an established process for community-driven
> development and decision making by consensus. This is exactly the model we
> want for future Heron development.
>
> = Initial Goals =
>
>  * Move the existing codebase, website, documentation, and mailing lists to
> Apache-hosted infrastructure.
>  * Integrate with the Apache development process.
>  * Ensure all dependencies are compliant with Apache License version 2.0.
>  * Incrementally develop and release per Apache guidelines.
>
> = Current Status =
>
> Heron is a stable project used in production

Re: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

On Sat, Jun 17, 2017 at 3:51 PM Pierre Smits  wrote:

> From a UX point of view I would move the 'About The Apache Software
> Foundation' to below the lists of codlings.
>

Hmmm ok.  I'm not sure the text is relevant, and i'm not sure how much
people will scroll through the list of podlings (I included it to simply
mirror existing behavior).  I do think the whole header area needs a bit
more work.


>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Sat, Jun 17, 2017 at 9:05 PM, Raphael Bircher  >
> wrote:
>
> > Hi John
> >
> > Am .06.2017, 14:35 Uhr, schrieb John D. Ament :
> >
> > All,
> >>
> >> I'd like to start the process to move forward on a new incubator
> website.
> >> Based on discussions in the past on list, I wanted to do the following:
> >>
> >> - Roll out a new technology stack + repository
> >> - Leave content in place, while we work later on content enhancements
> >>
> >> For right now, I'm planning to leave the existing /projects and
> >> /ip-clearance in place.  My hope is that we may not need them in the
> >> future.
> >>
> >> The website staging area can be seen here:
> >> https://incubator.apache.org/ngtest/
> >>
> > 1) When you think to add the navigation?
> > 2) The code part has a syntax heightlighting. witch is not so nice if you
> > have a simple text file. (a template for a E-mail for example.
> >
> > Regards, Raphael
> >
> >
> > --
> > My introduction https://youtu.be/Ln4vly5sxYU
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

On Sat, Jun 17, 2017 at 3:05 PM Raphael Bircher 
wrote:

> Hi John
>
> Am .06.2017, 14:35 Uhr, schrieb John D. Ament :
>
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
> >
> > - Roll out a new technology stack + repository
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> > future.
> >
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> 1) When you think to add the navigation?
>

Which navigation?  There's a header on top, similar to the top level www.


> 2) The code part has a syntax heightlighting. witch is not so nice if you
> have a simple text file. (a template for a E-mail for example.
>

Yeah, hm.  I think that's because I'm using asciidoctor's [source] instead
of [literal] but will check.



>
> Regards, Raphael
>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

On Sat, Jun 17, 2017 at 8:53 AM sebb  wrote:

> On 17 June 2017 at 13:35, John D. Ament  wrote:
> > All,
> >
> > I'd like to start the process to move forward on a new incubator website.
> > Based on discussions in the past on list, I wanted to do the following:
>
> I missed those, so some of my comments may be unnecessary ...
>

Your input is never unnecessary Sebb :-)


>
> > - Roll out a new technology stack + repository
>
> Is this going to be documented somewhere?
>

Yes, I think it'll be useful to include a README (a new norm?) on how it
works + create the equivalent of
https://incubator.apache.org/ngtest/guides/website.html for the new git
repo + jbake, plus docs on how the jenkins job works (over CMS)


>
> > - Leave content in place, while we work later on content enhancements
> >
> > For right now, I'm planning to leave the existing /projects and
> > /ip-clearance in place.  My hope is that we may not need them in the
> future.
>
> /projects files are currently referenced from lots of places.
>

ACK.  I have no intention of dropping /projects anytime soon, at least not
until Whimsy can handle all of these use cases.


>
> This includes retired podling website urls which redirect to the
> relevant projects/podling.html file.
> These are set up as permanent redirects in .htaccess files.
>

I'm wondering if this can just show a 404 page after a while?  For TLPs we
show an attic notice, but podlings may have never gotten through a release.


>
> The list of graduated and retired projects needs to be accessible.
>

While we provide this service today, I'm wondering what the use case is for
it?  Is it just to see that after they've graduated they had everything
done?


>
> > The website staging area can be seen here:
> > https://incubator.apache.org/ngtest/
> > The git repository for the site can be seen here:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
> > (with
> > github mirror at https://github.com/apache/incubator/tree/jbake-site )
> >
> > I'd like to get some final feedback on the layout and colors (not the
> > content).
>
> The layout and colours seem fine to me, but I was happy with the
> present layout (which was redone not that long ago?)
>

It has to be ~ 6 years, at least, the incubator website looks the same as
when I first got here.


>
> All existing (major) URLs should continue to work to avoid
> invalidating bookmarks.
>

Sure, I'm assuming you'd be OK with a .htaccess doing redirects?  Just note
at some point we will be moving content around.


>
> > I want to start tracking content enhancements in JIRA to help
> > come up with a backlog of areas of improvement for our incubator guides.
> >
> > John
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DISCUSS] Migrating to the New Incubator Website

[John D. Ament]

All,

I'd like to start the process to move forward on a new incubator website.
Based on discussions in the past on list, I wanted to do the following:

- Roll out a new technology stack + repository
- Leave content in place, while we work later on content enhancements

For right now, I'm planning to leave the existing /projects and
/ip-clearance in place.  My hope is that we may not need them in the future.

The website staging area can be seen here:
https://incubator.apache.org/ngtest/
The git repository for the site can be seen here:
https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=shortlog;h=refs/heads/jbake-site
(with
github mirror at https://github.com/apache/incubator/tree/jbake-site )

I'd like to get some final feedback on the layout and colors (not the
content).  I want to start tracking content enhancements in JIRA to help
come up with a backlog of areas of improvement for our incubator guides.

John

[FINAL DRAFT] Incubator PMC Board Report - June 2016

[John D. Ament]

All,

Below is the final draft of the board report.  I plan to submit it in the
morning (eastern).

IPMC Members specifically, please review the report, any podlings you are a
mentor of, and whether or not you have signed off on their reports.  This
month is especially big on single sign off podlings, which is a concern of
mine.

Incubator PMC report for June 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

At the end of May, there were 60 podlings incubating.  Podlings executed
six releases this month.  The incubator brought in one new podling, and the
board has motions to graduate three podlings from the incubator.  One IPMC
member stepped down while two new IPMC members joined.

Many reports below were signed off by a single mentor.  The Incubator PMC
shall begin to plan for a way to address this.

* Community

  New IPMC members:

  - Bikas Saha
  - Bob Paulin

  People who left the IPMC:

  - Par Niclas Hedhman

* New Podlings

  - Superset

* Podlings that failed to report, expected next month

  - MRQL - No on list discussion in past 3 months, limited discussions
prior to that.
  - Myriad - Discussing retirement
  - Sirona - Likely to be retired or moved as a sub-project by next report

* Graduations

  The board has motions for the following:

  - Atlas
  - HORN
  - MADlib
  - Mynewt

* Releases

  The following releases entered distribution during the month of
  May:

  - 2017-05-01 Apache Trafodion 2.1.0
  - 2017-05-04 Apache Mnemonic 0.7.0-incubating
  - 2017-05-09 Apache Airflow 1.8.1
  - 2017-05-09 Apache MADlib 1.11
  - 2017-05-17 Apache Ratis 0.1.0-alpha
  - 2017-05-30 Apache Tephra 0.12.0

* Infrastructure

  - The Incubator has begun to migrate podling maintenance into Whimsy

* Miscellaneous

  - The IPMC has elected a new chair, hopefully accepted at this month's
board meeting.


--
   Table of Contents
AriaTosca
Atlas
Gearpump
Gobblin
Griffin
Hivemall
HTrace
iota
Joshua
Mnemonic
Omid
OpenWhisk
Pony Mail
Quickstep
SAMOA
Singa
Slider
Spot
Streams
Superset
Tamaya
Taverna
Tephra
Toree
Trafodion
Wave

--


AriaTosca

ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.

AriaTosca has been incubating since 2016-08-27.

Three most important issues to address in the move towards graduation:

  1. Grow the community and enroll new committers.
  2. Have frequent Release cycles to be compliant with the Apache Way.
  3. Move the website to apache.org

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 The project is ready for its first release as far as the code is
concerned; We're working on updating the README and ensuring compatibility
with ASF's regulations regarding creating releases.
On the latter issue, we've come across a few possible problems, that are
being discussed on the project's mailing list.
For more information, see the threads "ARIA dependencies License issues"
and "A few questions about creating a release" on the mailing list archive.


How has the community developed since the last report?

 * All project communication takes now place on either the mailing list or
ASF's Slack, and is open for everybody.
 * Increased chatter on the mailing list including new subscribers who ask
questions, make suggestions and are likely to become contributors
themselves in the near future.

How has the project developed since the last report?

 1. ARIA now has a CLI, making it usable as a stand alone tool as well as a
library.
 2. Usage examples have been added
 3. End-to-End tests now run on a daily basis (as well as on CIs for every
commit)
 4. 93 JIRA issues have been resolved since the last report

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  No release yet.

When were the last committers or PPMC members elected?

Project is still functioning with the initial set of committers.

Signed-off-by:

  [X](ariatosca) Suneel Marthi
 Comments:
  [X](ariatosca) John D. Ament
 Comments:  The project continues to struggle in adopting the Apache
Way.  It's clear most of them want to do it, but need to work on getting
focused to make it happen.
  [ ](ariatosca) Jakob Homan
 Comments:


Atlas

 Apache Atlas is a scalable and extensible set of core foundational
governance
 services that enables enterprises to effectively and efficiently meet their
 compliance requirements w

Re: Edit access request for incubator wiki

[John D. Ament]

Bill,

You've been added.  Happy editing!

On Fri, Jun 16, 2017 at 2:35 PM Bill Graham  wrote:

> Hi,
>
> Can I please have edit permission to https://wiki.apache.org/incubator
> /ProjectProposals. My wiki login is BillGraham.
>
> thanks,
> Bill
> --
> Sent from Gmail Mobile
>

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

On Thu, Jun 15, 2017 at 3:50 PM Jim Apple  wrote:

> Thank you for the responses.
>
> >> 5. Make sure the Whimsy page applies to all projects. For instance,
> >> Impala releases are source tarballs, so if "Binary Distribution
> >> Licensing" means something about a non-source-tarball release
> >> artefact, it's not meaningful for Impala.
> >>
> >
> > Hmm that's interesting.  The ASF only releases source code.  However, the
> > second check is that your resulting binary is also compliant.
>
> The "your resulting binary" is for projects that distribute
> convenience binaries?
>

No - but either way Impala is probably in the clear.

The resulting binary is an issue if:

- You use statically linked libraries (e.g. they get embedded in the binary)
- You do provide a distribution style binary that includes them in the
package (e.g. a rpm or deb or tar or zip)

As an example, ActiveMQ Artemis depends on an optional extension for
libaio.  libaio is LGPL licensed.  This binary is OK because it is
optional, the user has to do something to enable it.  But do note they ship
it as a convenience.


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

Re: Clarification/typo on release votes (Re: [VOTE] Release Apache Tamaya 0.3-incubating)

[John D. Ament]

Gah, this is what I was trying to convey.  But I don't think it's still
100% correct.

You need a minimum of 3 +1's
Your net positive votes must be 3 (e.g. if you have a -1 and 5 total votes,
the other 4 votes must be +1's)
You need more +1's than -1's

I'm not sure what is written better.

(trying to be more anal than Josh, but just to make sure everyone agrees)

John

On Thu, Jun 15, 2017 at 8:54 PM Josh Elser  wrote:

> On 6/15/17 1:11 PM, Oliver B. Fischer wrote:
> >
> > Please note:
> > This vote is a "majority approval" with a minimum of three +1 votes and
> > no -1’s (see [4]).
>
> Just wanted to point out that your description of majority approval is
> wrong. You need at least 3 +1's and more +1's than -1's. -1's are not
> vetos in this case :)
>
> (since I had to be anal about it and correct you, let me take a look at
> your RC too :P)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Tamaya 0.3-incubating

[John D. Ament]

Copying my +1 from the dev list.

On Thu, Jun 15, 2017 at 4:11 PM Oliver B. Fischer 
wrote:

> Dear all,
>
> The Apache Tamaya team would like to release version 0.3-incubating of
> Apache Tamaya.
>
> The new release is a major milestone of the project with the following
> new key features:
>
>   *
>
> Review & Verify OSGi Support
>
>   *
>
> Remove dependency on DropWizard in favour of Tomcat Embedded
>
>   *
>
> Remove dependency on Jersey
>
>   *
>
> Add possibility to configure non annotated classes/interfaces
>
>   *
>
> Support also XML based property files
>
>   *
>
> Improve resource loading in OSGi
>
>   *
>
> Integrate Pitest in Tamaya Core and the Extensions
>
>   *
>
> Add converters for File and Path
>
>   *
>
> Add statistics function about Configuration Usage
>
>   *
>
> Add support for adding of main argument parameters as configuration
>
>   *
>
> Lots of smaller fixes
>
> The artifacts are deployed to [1].
>
> The tag is available at [2].
>
> The full release notes are available at [3].
>
> The project vote has been passed with
>
> 4 binding +1 votes (pmc):
>
> 0 non-binding +1
>
> 0 -1 vote
>
> The vote thread can be found at
>
> https://s.apache.org/aNgu
>
> Please take a look at the artifacts and vote!
>
> Please note:
> This vote is a "majority approval" with a minimum of three +1 votes and
> no -1’s (see [4]).
>
> 
> [ ] +1 for community members who have reviewed the bits
> [ ] +0
> [ ] -1 for fatal flaws that should cause these bits not to be
> released, and why..
> 
>
> [1] https://s.apache.org/Sp3k
>
> [2] https://s.apache.org/uwD2
>
> [3] https://s.apache.org/hbyu
>
> [4] http://www.apache.org/foundation/voting.html#ReleaseVotes
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251 <+49%2030%2044793251>
> M +49 178 7903538 <+49%20178%207903538>
> E o.b.fisc...@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fisc...@jabber.org
> X http://xing.to/obf
>
>

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

Jim,

Thanks for the input!

On Thu, Jun 15, 2017 at 1:22 PM Jim Apple  wrote:

> Here are some suggestions:
>
> 1. Only make this the reporting structure for new podlings.
> Grandfather in old podlings to the old structure, since they may
> already have workflows built around it. Impala does.
>

So far, this is an experiment only.  No one is required to fill it out yet.


>
> 2. Provide a clear description of the meaning and formatting of each
> field in comments on the YAML file itself.
>

At some point, the yaml files will be there in spirit only and the actual
entry will be done via this screen.  There would need to be a read only
version available as well.


>
> 3. Provide guidance on how long it takes from SVN checkin to whimsy
> render change.
>
> 4. Use git, not SVN
>
> 5. Make sure the Whimsy page applies to all projects. For instance,
> Impala releases are source tarballs, so if "Binary Distribution
> Licensing" means something about a non-source-tarball release
> artefact, it's not meaningful for Impala.
>

Hmm that's interesting.  The ASF only releases source code.  However, the
second check is that your resulting binary is also compliant.


>
> 6. Give the fields on the whimsy page names that correspond,
> one-to-one, with the YAML fields.
>

It isn't 1:1, specifically, because some of the information is either/or in
nature.


>
> 7. Give the Whimsy page headers more specific meanings. "Confirmation
> of ASF Copyright Headers on Source Code on" could mean confirmation by
> any number of people or committees. Which one is meant by this phrase?
> If it's the IPMC, and the first approved release is what is meant by
> this, change the name to "First Apache release" or something.
>
>
Agreed.


> 8. Provide the ability to lookup the information required to fill out
> the status page. How can a podling find out when the SGA was received?
> Please remember that podling personnel can change during incubation.
>

True, but podlings should also have access to mail archives which includes
the SGA that was filed.  Worst case, ask your mentor, or even better, when
secretary receives it they set this value.


>
> On Tue, Jun 13, 2017 at 6:04 PM, John D. Ament 
> wrote:
> > Jim,
> >
> > For your specific cases, if all you want is to remove red text:
> >
> > - for :sga: enter the date in -MM-DD format of when the ASF Secretary
> > acknowledged your SGA.  Based on the records I have its 2016-03-15
> > - For the :asfCopyright: and :distributionRights: attributes, I would use
> > 2017-01-20 as that's the day of the results of 2.8 which was the first
> > release to have no issues during review.
> >
> > But please do continue to provide input, want to make sure we're building
> > something useful, not a pain.
> >
> > HTH,
> >
> > John
> >
> > On Tue, Jun 13, 2017 at 8:52 PM Jim Apple  wrote:
> >
> >> I'm confused. The message to podlings@ said "If you're not sure what
> >> to fill out, feel free to reach out."
> >>
> >> It sounds like there is no set way yet to fill it out.
> >>
> >> What can I do to get the bolded, red, inaccurate scare messages off of
> >> our whimsy page?
> >>
> >> On Tue, Jun 13, 2017 at 5:30 PM, John D. Ament 
> >> wrote:
> >> > Good points Dave.  To be honest, since this is a prototype I don't
> have
> >> > answers any more than "If you think it should do that, we can make it
> do
> >> > that"
> >> >
> >> > What I did have in mind:
> >> >
> >> > ---
> >> > :issueTracker: jira|github|bugzilla
> >> > :wiki: if using confluence, their space key
> >> > :jira: if using jira, their issue key (though I suppose this can be
> >> > multiple)
> >> > :proposal: link to the proposal page.
> >> > :asfCopyright: the date that we confirmed ASF copyright headers on the
> >> > source code (e.g. the first time a source release passed without any
> >> issues)
> >> > :distributionRights: the date that we confirmed the resulting binary
> >> > satisfied our release policies (e.g. the first time a release
> included a
> >> > binary without any issues)
> >> > :ipClearance: a link to the IP Clearance page for this podling.  I
> guess
> >> > this can be multiple?
> >> > :sga: date in which a SGA was received
> >> > :website: http://impala.incubator.apache.org
> >> > :graduationDate: to be filled in when the podling graduate

Re: [VOTE]: Release Apache RocketMQ 4.1.0(incubating)(RC1)

[John D. Ament]

+1 to release

On Tue, Jun 13, 2017 at 10:02 PM dongeforever <1018815...@qq.com> wrote:

> Hello Incubator PMC,
>
>
> The Apache RocketMQ community has voted and approved the proposal to
> release Apache RocketMQ 4.1.0 (incubating). We now kindly request the IPMC
> review and vote on this incubator release.
>
>
> Apache RocketMQ is a distributed messaging and streaming platform with low
> latency, high performance and reliability, trillion-level capacity and
> flexible scalability.
>
>
>
>
> [VOTE] Thread:
>
> https://lists.apache.org/thread.html/c81e7329d1e47425a50a11e863257a2798bf17c52e9573e0020c42d0@%3Cdev.rocketmq.apache.org%3E
>
>
> [RESULT][VOTE] Thread:
>
> https://lists.apache.org/thread.html/626e93ad0ed4c1df6a5ee5b7466b1ab4f4b10f3e6ec72cac11157368@%3Cdev.rocketmq.apache.org%3E
>
>
> The artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/4.1.0-incubating-rc1/
>
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacherocketmq-1005
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-rocketmq/tree/rocketmq-all-4.1.0-incubating
>
>
> Hash for the release tag:
> 308598865addb9a857d432c9607478642541093c
>
>
> Release Notes:
> https://rocketmq.apache.org/release-notes-4.1.0-incubating/
>
>
> The artifacts have been signed with Key : 133C87CA, which can be found in
> the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS
>
>
>
>
>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
>
> Please vote accordingly:
>
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Thanks,
> The Apache RocketMQ Team

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

Jim,

For your specific cases, if all you want is to remove red text:

- for :sga: enter the date in -MM-DD format of when the ASF Secretary
acknowledged your SGA.  Based on the records I have its 2016-03-15
- For the :asfCopyright: and :distributionRights: attributes, I would use
2017-01-20 as that's the day of the results of 2.8 which was the first
release to have no issues during review.

But please do continue to provide input, want to make sure we're building
something useful, not a pain.

HTH,

John

On Tue, Jun 13, 2017 at 8:52 PM Jim Apple  wrote:

> I'm confused. The message to podlings@ said "If you're not sure what
> to fill out, feel free to reach out."
>
> It sounds like there is no set way yet to fill it out.
>
> What can I do to get the bolded, red, inaccurate scare messages off of
> our whimsy page?
>
> On Tue, Jun 13, 2017 at 5:30 PM, John D. Ament 
> wrote:
> > Good points Dave.  To be honest, since this is a prototype I don't have
> > answers any more than "If you think it should do that, we can make it do
> > that"
> >
> > What I did have in mind:
> >
> > ---
> > :issueTracker: jira|github|bugzilla
> > :wiki: if using confluence, their space key
> > :jira: if using jira, their issue key (though I suppose this can be
> > multiple)
> > :proposal: link to the proposal page.
> > :asfCopyright: the date that we confirmed ASF copyright headers on the
> > source code (e.g. the first time a source release passed without any
> issues)
> > :distributionRights: the date that we confirmed the resulting binary
> > satisfied our release policies (e.g. the first time a release included a
> > binary without any issues)
> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
> > this can be multiple?
> > :sga: date in which a SGA was received
> > :website: http://impala.incubator.apache.org
> > :graduationDate: to be filled in when the podling graduates
> > :resolution: tlp|subproject , if subproject the TLP should be in here
> > somehwere.  We may want to track as "sponsor."
> >
> > I can draft this up on a wiki page to gain more input.  What do you think
> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
> > work through it?  I had a few more questions in line.
> >
> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher 
> wrote:
> >
> >> Hi John -
> >>
> >> These are excellent questions. I see each of these as being tuples of
> >> various kinds.
> >>
> >> For example :sga: could have multiple grants each of which has a date
> and
> >> a file name to refer to in the foundation records.
> >>
> >>
> > We don't usually expose the file name to people outside members, so I'm
> not
> > sure this would be useful.  Multiple dates are also not common.
> >
> >
> >> The path to the source repository is missing completely.
> >>
> >
> > Which source repository?  The podlings?  I have a prototype for gitbox
> > podlings and think I can make it work for ASF git as well.  For SVN, we
> can
> > assume default or have a list of values.
> >
> >
> >>
> >> Some of these items could be transitory. For example distributionRights
> >> may be confirmed but then something is added which negates those rights
> >> until the issue is cleared up.
> >>
> >>
> > +1
> >
> >
> >> I wonder if it makes sense to provide links to email threads and/or Wiki
> >> pages with the details?
> >>
> >> Regards,
> >> Dave
> >>
> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
> >> >
> >> > What format of data is expected in the fields? Impala's new status
> >> > page SVN config file
> >> > <
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >> >
> >> > is:
> >> >
> >> > ---
> >> > :issueTracker: jira
> >> > :wiki: IMPALA
> >> > :jira: IMPALA
> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> >> > :asfCopyright:
> >> > :distributionRights:
> >> > :ipClearance:
> >> > :sga:
> >> > :website: http://impala.incubator.apache.org
> >> > :graduationDate:
> >> > :resolution:
> >> >
> >> > I do not know how to fill out asfCopyright, distributionRights,
> >> > ipClearance, or sga. Note 

Re: [DRAFT] What the new Status Pages potentially look like

[John D. Ament]

Good points Dave.  To be honest, since this is a prototype I don't have
answers any more than "If you think it should do that, we can make it do
that"

What I did have in mind:

---
:issueTracker: jira|github|bugzilla
:wiki: if using confluence, their space key
:jira: if using jira, their issue key (though I suppose this can be
multiple)
:proposal: link to the proposal page.
:asfCopyright: the date that we confirmed ASF copyright headers on the
source code (e.g. the first time a source release passed without any issues)
:distributionRights: the date that we confirmed the resulting binary
satisfied our release policies (e.g. the first time a release included a
binary without any issues)
:ipClearance: a link to the IP Clearance page for this podling.  I guess
this can be multiple?
:sga: date in which a SGA was received
:website: http://impala.incubator.apache.org
:graduationDate: to be filled in when the podling graduates
:resolution: tlp|subproject , if subproject the TLP should be in here
somehwere.  We may want to track as "sponsor."

I can draft this up on a wiki page to gain more input.  What do you think
about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
work through it?  I had a few more questions in line.

On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher  wrote:

> Hi John -
>
> These are excellent questions. I see each of these as being tuples of
> various kinds.
>
> For example :sga: could have multiple grants each of which has a date and
> a file name to refer to in the foundation records.
>
>
We don't usually expose the file name to people outside members, so I'm not
sure this would be useful.  Multiple dates are also not common.


> The path to the source repository is missing completely.
>

Which source repository?  The podlings?  I have a prototype for gitbox
podlings and think I can make it work for ASF git as well.  For SVN, we can
assume default or have a list of values.


>
> Some of these items could be transitory. For example distributionRights
> may be confirmed but then something is added which negates those rights
> until the issue is cleared up.
>
>
+1


> I wonder if it makes sense to provide links to email threads and/or Wiki
> pages with the details?
>
> Regards,
> Dave
>
> > On Jun 13, 2017, at 8:22 AM, Jim Apple  wrote:
> >
> > What format of data is expected in the fields? Impala's new status
> > page SVN config file
> > <
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >
> > is:
> >
> > ---
> > :issueTracker: jira
> > :wiki: IMPALA
> > :jira: IMPALA
> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> > :asfCopyright:
> > :distributionRights:
> > :ipClearance:
> > :sga:
> > :website: http://impala.incubator.apache.org
> > :graduationDate:
> > :resolution:
> >
> > I do not know how to fill out asfCopyright, distributionRights,
> > ipClearance, or sga. Note that I believe I understand what these
> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> >
> > I also don't know which one(s) correspond to the bold red "No Release
> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
> > has had a couple of ASF releases.
> >
> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament 
> wrote:
> >> All,
> >>
> >> We're piloting a new format for the podling status pages.  Specifically,
> >> the current status page leaves a lot to be desired - it's basically
> crafted
> >> html, there's no structure and its hard to find missing items.  The end
> >> goal is to have a web form editable in Whimsy, but until we get more
> input
> >> on what the content looks like I don't want to make changes like that.
> I'm
> >> asking at this point for podlings to take a look at the status output,
> >> potentially update their own content, and see if they like the output.
> >>
> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
> (authentication
> >> is via your ASF committer username/password) and find your podling,
> you'll
> >> see your current roster as well as your current status information.
> >>
> >> The status pages can be found in SVN at this directory
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> >>
> >> Some more information can be found at
> >>
> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
> >>
> >> If you're not sure what to fill out, feel free to reach out.
> >>
> >> John
>
>

Re: [Incubator Wiki] Update of "June2017" by johndament

[John D. Ament]

I added a note about the IPMC chair vote.

On Jun 11, 2017 10:28 PM, "Justin Mclean"  wrote:

> Hi,
>
> Silly comment? Can you expand a little?
>
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DRAFT] Incubator PMC Board Report - June 2017

[John D. Ament]

All,

Below is the present draft of our board report.  Four podlings are missing
sign off (CC'd) and it needs some reflowing.  I removed 3 non-reporting
podlings.

Remember that you can update the report on the wiki at
https://wiki.apache.org/incubator/June2017 (aka don't reply asking me to
make a change :-)

Incubator PMC report for June 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

At the end of May, there were 60 podlings incubating.  Podlings executed
six releases this month.  The incubator brought in one new podling, and the
board has motions to graduate three podlings from the incubator.  One IPMC
member stepped down while two new IPMC members joined.

* Community

  New IPMC members:

  - Bikas Saha
  - Bob Paulin

  People who left the IPMC:

  - Par Niclas Hedhman

* New Podlings

  - Superset

* Podlings that failed to report, expected next month

  - MRQL - No on list discussion in past 3 months, limited discussions
prior to that.
  - Myriad - Discussing retirement
  - Sirona - Likely to be retired or moved as a sub-project by next report

* Graduations

  The board has motions for the following:

  - Atlas
  - MADlib
  - Mynewt

* Releases

  The following releases entered distribution during the month of
  May:

  - 2017-05-01 Apache Trafodion 2.1.0
  - 2017-05-04 Apache Mnemonic 0.7.0-incubating
  - 2017-05-09 Apache Airflow 1.8.1
  - 2017-05-09 Apache MADlib 1.10.0
  - 2017-05-17 Apache Ratis 0.1.0-alpha
  - 2017-05-30 Apache Tephra 0.12.0

* IP Clearance



* Legal / Trademarks



* Infrastructure

  - The Incubator has begun to migrate podling maintenance into Whimsy

* Miscellaneous

  - The IPMC has elected a new chair, hopefully accepted at this month's
board meeting.

--
   Table of Contents
AriaTosca
Atlas
Gearpump
Gobblin
Griffin
Hivemall
HORN
HTrace
iota
Joshua
Mnemonic
Omid
OpenWhisk
Pony Mail
Quickstep
SAMOA
Singa
Slider
Spot
Streams
Superset
Tamaya
Taverna
Tephra
Toree
Trafodion
Wave

--


AriaTosca

ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.

AriaTosca has been incubating since 2016-08-27.

Three most important issues to address in the move towards graduation:

  1. Grow the community and enroll new committers.
  2. Have frequent Release cycles to be compliant with the Apache Way.
  3. Move the website to apache.org

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 The project is ready for its first release as far as the code is
concerned; We're working on updating the README and ensuring compatibility
with ASF's regulations regarding creating releases.
On the latter issue, we've come across a few possible problems, that are
being discussed on the project's mailing list.
For more information, see the threads "ARIA dependencies License issues"
and "A few questions about creating a release" on the mailing list archive.


How has the community developed since the last report?

 * All project communication takes now place on either the mailing list or
ASF's Slack, and is open for everybody.
 * Increased chatter on the mailing list including new subscribers who ask
questions, make suggestions and are likely to become contributors
themselves in the near future.

How has the project developed since the last report?

 1. ARIA now has a CLI, making it usable as a stand alone tool as well as a
library.
 2. Usage examples have been added
 3. End-to-End tests now run on a daily basis (as well as on CIs for every
commit)
 4. 93 JIRA issues have been resolved since the last report

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  No release yet.

When were the last committers or PPMC members elected?

Project is still functioning with the initial set of committers.

Signed-off-by:

  [X](ariatosca) Suneel Marthi
 Comments:
  [X](ariatosca) John D. Ament
 Comments:  The project continues to struggle in adopting the Apache
Way.  It's clear most of them want to do it, but need to work on getting
focused to make it happen.
  [ ](ariatosca) Jakob Homan
 Comments:

IPMC/Shepherd notes:




Atlas

 Apache Atlas is a scalable and extensible set of core foundational
governance
 services that enables enterprises to effectively and efficiently meet their
 compliance requirements within Hadoop and allows integration with the
complete
 enterprise data ec

Re: Updating PPMC rosters via whimsy

[John D. Ament]

Alright, we'll have to look, I was hoping it was something obvious but
everything about your setup looks correct.  And I should have known which
podling you were on - I think we even met at ACNA.

John

On Sun, Jun 11, 2017 at 12:31 PM Adina Crainiceanu  wrote:

> John,
>
> I'm a committer and PPMC member for Rya
>
> Adina
>
> On Sun, Jun 11, 2017 at 12:23 PM, John D. Ament 
> wrote:
>
> > Adina,
> >
> > What podling are you on?
> >
> > John
> >
> > On Sun, Jun 11, 2017 at 10:50 AM Adina Crainiceanu 
> wrote:
> >
> > > I just wanted to mention that in the "Incubator committers that are not
> > on
> > > the IPMC and are not listed as a committer of any podling" I noticed
> > > multiple names (myself included - Adina Crainiceanu), who are
> committers
> > on
> > > active podlings and are still included in the list. For example, I am a
> > > committer and PPMC member for Apache Rya (incubating). Not sure how the
> > > list was generated, but not only committers of already graduated
> podlings
> > > are on the list, but also committers of active podlings. Maybe because
> > > those people are part of the PPMC of a podling and therefore they are
> > > implicit committers, but somehow they were not considered committers
> for
> > > the purpose of generating the list.  (I believe that the assumption
> that
> > > all PPMC members are commiters is/should be true)
> > >
> > > On Sun, Jun 11, 2017 at 10:21 AM, Sam Ruby 
> > wrote:
> > >
> > > > On Sun, Jun 11, 2017 at 7:58 AM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > > > On Sun, Jun 11, 2017 at 5:58 AM sebb  wrote:
> > > > >
> > > > >> On 11 June 2017 at 00:18, Sam Ruby 
> wrote:
> > > > >> > On Fri, May 26, 2017 at 6:10 PM, Sam Ruby <
> ru...@intertwingly.net
> > >
> > > > >> wrote:
> > > > >> >>
> > > > >> >> For that reason, I'd like to make a simplifying assumption:
> that
> > > all
> > > > >> mentors
> > > > >> >> are PPMC members, and all PPMC members are committers.
> > > > >> >
> > > > >> > Existing records that violate one or more assumptions:
> > > > >> > https://whimsy.apache.org/incubator/podling-crosscheck
> > > > >>
> > > > >> "Podling Committers that are not Incubator committers"
> > > > >> AFAIK, that should not happen.
> > > > >> Probably mostly existing ASF committers being added to podlings
> > > > directly.
> > > > >> New committers should be added to Incubator + podling by the
> > existing
> > > > >> processes.
> > > > >> I think it would make sense to just add them to the Incubator
> > > > >> committer list so they have the appropriate karma.
> > > > >>
> > > > >>
> > > > > Agreed.  I appreciate the concise report.  We should plan to add
> > these
> > > > > individuals.
> > > >
> > > > You should be able to add them from the ppmc page.
> > > >
> > > > >> "Incubator committers that are not on the IPMC and are not listed
> > as a
> > > > >> committer of any podling"
> > > > >> Most likely they were on podlings that are no longer active.
> > > > >> I don't think any cleanup of the list is done when podlings exit
> > > > >> incubation, so this list will continue growing.
> > > > >> Does that matter?
> > > > >>
> > > > > I was thinking about this.  I think I mis-stated the behavior of
> > adding
> > > > > someone to the PPMC.  There is no requirement to remove them from
> > > > > incubator.  That's actually how I got started, my podling already
> > > > graduated
> > > > > but I still had my incubator commit bit.
> > > >
> > > > Some of that list is because not all of the podling rosters have been
> > > > updated.
> > > >
> > > > But if the plan is to have a monotonically increasing list of people
> > > > who ever were associated with a podling at any point in the past, it
> > > > may make sense to change things so that all committers have access to
> > > > inc

Re: Updating PPMC rosters via whimsy

[John D. Ament]

Adina,

What podling are you on?

John

On Sun, Jun 11, 2017 at 10:50 AM Adina Crainiceanu  wrote:

> I just wanted to mention that in the "Incubator committers that are not on
> the IPMC and are not listed as a committer of any podling" I noticed
> multiple names (myself included - Adina Crainiceanu), who are committers on
> active podlings and are still included in the list. For example, I am a
> committer and PPMC member for Apache Rya (incubating). Not sure how the
> list was generated, but not only committers of already graduated podlings
> are on the list, but also committers of active podlings. Maybe because
> those people are part of the PPMC of a podling and therefore they are
> implicit committers, but somehow they were not considered committers for
> the purpose of generating the list.  (I believe that the assumption that
> all PPMC members are commiters is/should be true)
>
> On Sun, Jun 11, 2017 at 10:21 AM, Sam Ruby  wrote:
>
> > On Sun, Jun 11, 2017 at 7:58 AM, John D. Ament 
> > wrote:
> > > On Sun, Jun 11, 2017 at 5:58 AM sebb  wrote:
> > >
> > >> On 11 June 2017 at 00:18, Sam Ruby  wrote:
> > >> > On Fri, May 26, 2017 at 6:10 PM, Sam Ruby 
> > >> wrote:
> > >> >>
> > >> >> For that reason, I'd like to make a simplifying assumption: that
> all
> > >> mentors
> > >> >> are PPMC members, and all PPMC members are committers.
> > >> >
> > >> > Existing records that violate one or more assumptions:
> > >> > https://whimsy.apache.org/incubator/podling-crosscheck
> > >>
> > >> "Podling Committers that are not Incubator committers"
> > >> AFAIK, that should not happen.
> > >> Probably mostly existing ASF committers being added to podlings
> > directly.
> > >> New committers should be added to Incubator + podling by the existing
> > >> processes.
> > >> I think it would make sense to just add them to the Incubator
> > >> committer list so they have the appropriate karma.
> > >>
> > >>
> > > Agreed.  I appreciate the concise report.  We should plan to add these
> > > individuals.
> >
> > You should be able to add them from the ppmc page.
> >
> > >> "Incubator committers that are not on the IPMC and are not listed as a
> > >> committer of any podling"
> > >> Most likely they were on podlings that are no longer active.
> > >> I don't think any cleanup of the list is done when podlings exit
> > >> incubation, so this list will continue growing.
> > >> Does that matter?
> > >>
> > > I was thinking about this.  I think I mis-stated the behavior of adding
> > > someone to the PPMC.  There is no requirement to remove them from
> > > incubator.  That's actually how I got started, my podling already
> > graduated
> > > but I still had my incubator commit bit.
> >
> > Some of that list is because not all of the podling rosters have been
> > updated.
> >
> > But if the plan is to have a monotonically increasing list of people
> > who ever were associated with a podling at any point in the past, it
> > may make sense to change things so that all committers have access to
> > incubator resources and do away with this list.
> >
> > > The list that does worry me is the list of mentors not on the IPMC.  I
> > feel
> > > like that requires a bit more research to find out what happened but
> > unless
> > > those people are members they're probably going to be removed from
> their
> > > mentor roles.  What do others think?
> >
> > The individuals should probably be evaluated separately.  As Sebb
> > points out, most are ASF members, and therefore are one ask away from
> > being added to the IPMC:
> > http://incubator.apache.org/guides/pmc.html#joining
> >
> > - Sam Ruby
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Dr. Adina Crainiceanu
> Associate Professor, Computer Science Department
> United States Naval Academy
> 410-293-6822 <(410)%20293-6822>
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

Re: [VOTE] Apache HTrace 4.3.0 incubating release (rc3)

[John D. Ament]

Hi,

The issue of what to include in a WAR file recently came up.  I noticed
that your release includes a WAR file so figured I'd check it.  I found the
following:

- Includes a LICENSE, NOTICE.
- LICENSE does not mention the bundled backbone, jquery, underscore,
moment, npm.js libraries.
- No other dependencies found (no JAR files) so nothing else probably needs
to get included.

If you can raise a JIRA to cover these, I can vote a +1 with changes
required for next release.

John

On Fri, Jun 2, 2017 at 4:11 PM Mike Drob  wrote:

> Hi IPMC,
>
> Please consider the release of Apache HTrace 4.3.0 Incubating
>
>
>
> Project [VOTE]:
>
>
> https://lists.apache.org/thread.html/6e60ba2574a853da59c3a150f18cd9bbd52051785380a7cc837b583e@%3Cdev.htrace.apache.org%3E
>
> Project [RESULT][VOTE]:
>
>
> https://lists.apache.org/thread.html/fb2a68fcd9c80d9db4a483794112aecde486ca263384dec0bad38c34@%3Cdev.htrace.apache.org%3E
>
> Artifacts staged at:
>
> http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/
>
> Staging maven repository at:
>
> https://repository.apache.org/content/repositories/orgapachehtrace-1029
>
> Source tree:
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=2ca8767b38c83f0d2f46ce7f91373d9df69f7fb8;hb=a47398aea8d65fb544faba150beb49bb7654cb49
>
>
> Please download and evaluate the release candidate.
>
> This vote will remain open for minimum 5 days
>
> [ ] +1 Approve the release
>
> [ ] +0 No opinion
>
> [ ] -1 Do not approve the release because ...
>
>
> Thanks,
>
> Mike
>

Re: [VOTE] Impala 2.9.0 release candidate 1

[John D. Ament]

+1

On Thu, Jun 8, 2017 at 5:23 PM Taras Bobrovytsky 
wrote:

> Impala 2.9.0 release candidate 1 has passed a PPMC vote; this email is
> a call for an IPMC vote.
>
> The PPMC vote thread is:
> https://lists.apache.org/thread.html/f913ab0376f997fedd9a018715ce4b
> 3e88da67226e26751ea0e1f105@%3Cdev.impala.apache.org%3E
> http://mail-archives.apache.org/mod_mbox/impala-dev/201706.mbox/%
> 3CCAAXWMB7EAUnMnshPaCWC3i69C-rdduA-URyFw%3DZ4GHaVD6jxwA%40mail.gmail.com%3E
> 
>
> The vote result thread is:
> https://lists.apache.org/thread.html/877a75e7905b41b87df9901c2eae77
> b0331ccb8638905422bea06bb4@%3Cdev.impala.apache.org%3E
>
> The artifacts for testing are at
> .
> That is git tag 2.9.0-rc1, tree hash
> 93a1ac914dab21c4e08c630178aa6f8235f2d6f6, visible at
>  93a1ac914dab21c4e08c630178aa6f8235f2d6f6
> 
> >.
>
> The KEYS are at  impala/KEYS 
> >.
>
> To run RAT, follow the instructions in bin/check-rat-report.py. To
> build, follow the instructions in bin/bootstrap_build.sh.
>
> This vote will be open for at least 72 hours, or until the necessary
> number of votes (3 +1) is reached.
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>

Re: [VOTE] Apache Fluo 1.1.0-incubating (rc1)

[John D. Ament]

+1

On Tue, Jun 6, 2017 at 4:15 PM Keith Turner  wrote:

> Dear IPMC,
>
> Please vote for the following release candidate of Apache Fluo
> 1.1.0-incubating.
>
> PPMC vote thread:
>
> https://lists.apache.org/thread.html/c815b7a22fab10281ab2d4e88418a47a5903ba85327058bb727c7ccd@%3Cdev.fluo.apache.org%3E
>
> https://lists.apache.org/thread.html/99508ef4a2b782b82494e4250713c1d0917b75cf7149bec64455bea2@%3Cdev.fluo.apache.org%3E
>
> Staged dist artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo/1.1.0-incubating-rc1/
>
> Staged Maven repository:
> https://repository.apache.org/content/repositories/orgapachefluo-1017/
>
> Signing KEYS:
> https://www.apache.org/dist/incubator/fluo/KEYS
> (fingerprint for this release: CF72CA07C8BC86A1C862765F9AACFB56352ACF76)
>
> Git repo:
> https://gitbox.apache.org/repos/asf/incubator-fluo
> (branch: 1.1.0-incubating-rc1,
> commit: ad8ee492e2f435405f98d825781098c55186f4fb)
>
> This vote will end on Fri Jun  9 20:30:00 UTC 2017
> (Fri Jun  9 16:30:00 EDT 2017 / Fri Jun  9 13:30:00 PDT 2017)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Updating PPMC rosters via whimsy

[John D. Ament]

On Sun, Jun 11, 2017 at 5:58 AM sebb  wrote:

> On 11 June 2017 at 00:18, Sam Ruby  wrote:
> > On Fri, May 26, 2017 at 6:10 PM, Sam Ruby 
> wrote:
> >>
> >> For that reason, I'd like to make a simplifying assumption: that all
> mentors
> >> are PPMC members, and all PPMC members are committers.
> >
> > Existing records that violate one or more assumptions:
> > https://whimsy.apache.org/incubator/podling-crosscheck
>
> "Podling Committers that are not Incubator committers"
> AFAIK, that should not happen.
> Probably mostly existing ASF committers being added to podlings directly.
> New committers should be added to Incubator + podling by the existing
> processes.
> I think it would make sense to just add them to the Incubator
> committer list so they have the appropriate karma.
>
>
Agreed.  I appreciate the concise report.  We should plan to add these
individuals.


> "Incubator committers that are not on the IPMC and are not listed as a
> committer of any podling"
> Most likely they were on podlings that are no longer active.
> I don't think any cleanup of the list is done when podlings exit
> incubation, so this list will continue growing.
> Does that matter?
>
>
I was thinking about this.  I think I mis-stated the behavior of adding
someone to the PPMC.  There is no requirement to remove them from
incubator.  That's actually how I got started, my podling already graduated
but I still had my incubator commit bit.

The list that does worry me is the list of mentors not on the IPMC.  I feel
like that requires a bit more research to find out what happened but unless
those people are members they're probably going to be removed from their
mentor roles.  What do others think?


> > - Sam Ruby
> >
> > -
> > 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: [DRAFT] What the new Status info looks like

[John D. Ament]

On Sat, Jun 10, 2017 at 12:27 PM Ted Dunning  wrote:

> One more thought is that it would be nice to be able to see when the
> different committers, mentors and such were added to the project. The date
> of the last addition would be nice.
>
> If this data is pulled from a non-canonical source of user data, it would
> be good if the page cross-checked against canonical sources like LDAP to
> verify consistency.
>

It's pulling this information from LDAP so I suspect we can get it.


>
>
>
> On Sat, Jun 10, 2017 at 5:20 PM, John D. Ament 
> wrote:
>
> > I've put together a few podling status pages based on where some podlings
> > are, to demonstrate what it could look like.
> >
> > Juneau: https://whimsy.apache.org/roster/ppmc/juneau
> > AriaTosca: https://whimsy.apache.org/roster/ppmc/ariatosca
> > OpenWhisk: https://whimsy.apache.org/roster/ppmc/openwhisk
> >
> > These are just a couple of examples.  Some things I still feel are
> missing:
> >
> > - List of repositories.  For github it's easy, we can just link to a
> > search.  Can't say the same for ASF hosted (yet)
> > - Migration.  Haven't decided what I want to support, but the yaml files
> > are out there in
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > if
> > anyone wants to edit theirs
> > - Anything missing?
> > - Do we need public access, or is committer access OK?
> >
>

Re: [DRAFT] What the new Status info looks like

[John D. Ament]

On Sat, Jun 10, 2017 at 12:24 PM Ted Dunning  wrote:

> There are few usability issues.
>
> For the actions on a particular row, the double click is highly
> unconventional. That is evidenced by the fact that you have to tell people
> how to do it. I would suggest having a pull down on each row or use the
> standard sort of select,act style of interface where each row can be
> selected and there are several action buttons at top or bottom.
>
> I also find that the + buttons don't work. Instead of allowing me to add
> something, the inexplicably turn into search boxes. It isn't clear what is
> being searched since the box appears after all the other data. It would
> make more sense if the + were slightly outside the content list and
> clicking it caused a number of text entries to appear that allow me to
> enter required information.
>
>
Agreed on both parts.  The roster tool side of this needs a bit of UX.
I've created https://issues.apache.org/jira/browse/WHIMSY-99 for the roster
tool.


> I also find that the podling proposal link look like a content header
> because it is s close to the green explanation for how to add things.
> Removing the usage documentation (because it should be superfluous if the
> UI is properly discoverable) would allow this link to make more sense, but
> I would still want a separation from textual content and the list of
> people.
>
>
Agreed.  That was my first attempt to put something in, I wasn't sure where
it was going to go, and completely forgot about it until you mentioned it
now.

I'm thinking to add a bit to Podling Status to indicate the start date
(established) and proposal link.


>
>
> On Sat, Jun 10, 2017 at 5:20 PM, John D. Ament 
> wrote:
>
> > I've put together a few podling status pages based on where some podlings
> > are, to demonstrate what it could look like.
> >
> > Juneau: https://whimsy.apache.org/roster/ppmc/juneau
> > AriaTosca: https://whimsy.apache.org/roster/ppmc/ariatosca
> > OpenWhisk: https://whimsy.apache.org/roster/ppmc/openwhisk
> >
> > These are just a couple of examples.  Some things I still feel are
> missing:
> >
> > - List of repositories.  For github it's easy, we can just link to a
> > search.  Can't say the same for ASF hosted (yet)
> > - Migration.  Haven't decided what I want to support, but the yaml files
> > are out there in
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> > if
> > anyone wants to edit theirs
> > - Anything missing?
> > - Do we need public access, or is committer access OK?
> >
>

Re: [RESULT][VOTE] Graduate Apache MADlib podling

[John D. Ament]

Please don't forget to get this resolution up on the board's agenda.

John

On Tue, May 30, 2017 at 10:40 PM FENG, Xixuan (Aaron) 
wrote:

> With 5 +1 binding votes, 2 +1 non-bidning votes and 0 votes
> of any other kind this vote PASSES. Thanks to everyone who
> voted. The voting tally can be seen below:
>
> +1 binding:
> John D. Ament
> Jim Jagielski
> P. Taylor Goetz
> Roman Shaposhnik
> Konstantin Boudnik
>
> +1 non-binding:
> Pierre Smits
> Gregory Chase
>
> Thanks!
>
> --
> FENG, Xixuan (Aaron)
>
> Recruit Institute of Technology
> http://www.recruit.ai/
>
> Recruit Holdings
> http://www.recruit-rgf.com/
>
> Tel. +81-70-1402-6921 <+81%2070-1402-6921> <+81%2070-1402-6921>
> http://www.recruit.ai/aaron-feng
>
>
> On Wed, May 31, 2017 at 10:14 AM, Gregory Chase  wrote:
>
> > +1 (loiterer)
> >
> > On Tue, May 30, 2017 at 6:09 PM, Konstantin Boudnik 
> > wrote:
> >
> > > +1 [binding]
> > >
> > > On Sat, May 27, 2017 at 04:56PM, FENG, Xixuan (Aaron) wrote:
> > > > Greetings IPMC!
> > > >
> > > > The discussion seems to have died down, so I'm calling the
> > > > vote:  I propose that we graduate Apache MADlib from the Incubator.
> > > > The full text of the proposal is below.  The discuss thread can be
> > found
> > > > here:
> > > > https://lists.apache.org/thread.html/535f9871636f6e10c13e47
> > f1ec6e41
> > > > 5eca7f666e1580d8b762d8a42d@%3Cgeneral.incubator.apache.org%3E
> > > >
> > > > Please vote on the resolution:
> > > >
> > > > [ ] +1 Graduate Apache MADlib from the Incubator.
> > > > [ ] +0 No opinion
> > > > [ ] -1 Don't graduate Apache MADlib from the Incubator (please
> provide
> > > > the reason)
> > > >
> > > > This VOTE will be opened for the next 72 hours.
> > > >
> > > > Thanks to all Mentors and Apache MADlib Project members for their
> > > > support and contributions.
> > > >
> > > > Thanks,
> > > > Aaron.
> > > >
> > > > Resolution:
> > > >
> > > > Establish the Apache MADlib 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 a scalable, Big Data, SQL-driven machine
> > > > learning framework for Data Scientists.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > Committee (PMC), to be known as the "Apache MADlib Project",
> > > > be and hereby is established pursuant to Bylaws of the
> > > > Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache MADlib Project be and hereby is
> > > > responsible for the creation and maintenance of software
> > > > related to a scalable, Big Data, SQL-driven machine
> > > > learning framework for Data Scientists.
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache MADlib" 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 MADlib Project, and to have primary responsibility
> > > > for management of the projects within the scope of
> > > > responsibility of the Apache MADlib 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 MADlib Project:
> > > >
> > > > Sarah Aerni 
> > > > Greg Chase 
> > > > Aaron Feng 
> > > > Rahul Iyer 
> > > > Jim Jagielski 
> > > > Nandish Jayaram 
> > > > Anirudh Kondaveeti 
> > > > Orhan Kışlal 
> > > > Frank McQuillan 
> > > > Srivatsan R 
> > > > Rashmi Raghu 
> > > > Roman Shaposhnik 
> > > > Atri Sharma 
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Aaron Feng
> > > > 

[DRAFT] What the new Status info looks like

[John D. Ament]

I've put together a few podling status pages based on where some podlings
are, to demonstrate what it could look like.

Juneau: https://whimsy.apache.org/roster/ppmc/juneau
AriaTosca: https://whimsy.apache.org/roster/ppmc/ariatosca
OpenWhisk: https://whimsy.apache.org/roster/ppmc/openwhisk

These are just a couple of examples.  Some things I still feel are missing:

- List of repositories.  For github it's easy, we can just link to a
search.  Can't say the same for ASF hosted (yet)
- Migration.  Haven't decided what I want to support, but the yaml files
are out there in
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/ if
anyone wants to edit theirs
- Anything missing?
- Do we need public access, or is committer access OK?