Re: [VOTE] Retire ODF Toolkit

[Sergio Fernández]

+1

It'd be good to state the intention of the podling to continue under the
TDF (The Document Foundation) umbrella or the project is going to die
completely.

On Fri, Nov 16, 2018, 20:54 Dave Fisher  The ODF Toolkit community has VOTEd to Retire.
>
> The thread:
> https://lists.apache.org/thread.html/6de81dc33cb8311a38e38b927bfa1df7290c47ba7e7b39311cd06ce6@%3Codf-dev.incubator.apache.org%3E
>
> The results:
> https://lists.apache.org/thread.html/d4b4b33470a7bc3e70dc6192527168bb5907810045df5453c784cc93@%3Codf-dev.incubator.apache.org%3E
>
> Note that of the 6 VOTES there were 5 from IPMC members including the
> current Mentor and two original Mentors.
>
> This Vote will continue with the IPMC votes at 5 +1 and will be open for
> the next week.
>
> [ ] +1 - Retire ODF Toolkit.
> [ ] -1 - Do not retire ODF Toolkit. I intend to become a Mentor and try to
> make the community happen.
>
> Regards,
> Dave
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Approaching Apache's 200th top level project and more than 300 projects have gone through the incubator

[Sergio Fernández]

very cool!

On Fri, Nov 2, 2018, 23:48 Justin Mclean  Hi,
>
> It looks like the next project to graduate after Griffin will be the ASF’s
> 200th top level project!
>
> We’ll also recently passed the 300th project to go through the incubator.
> [1]
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog and apigateway 0.9.0 [RC1]

[Sergio Fernández]

+1 (binding)

So far I've checked:

- incubating suffix and disclaimer
- signatures and checksums
- LICENSE files
- Apache License headers
- No binaries distributed
- No unexpected binary files

As well as Justin, I have one minor comment that doesn't block the release:
some JavaScript files do use an incorrect (shorter) version of the Apache
License header. I know the JS build stack may not support that. But if
there is no automatic add/check in the build, the project has to audit
those manually on regular basis.

I'm very happy to see this podling I used to mentor moving forward :-)

On Mon, Sep 10, 2018, 08:15 Vincent S Hou  wrote:

> Dear IPMC members,
>
> This is a call for vote to release Apache OpenWhisk (Incubating):
> OpenWhisk catalog and apigateway 0.9.0 [RC1].
>
> The  Apache OpenWhisk community has voted on and approved a proposal to
> release Apache OpenWhisk (Incubating): catalog and apigateway, Version
> 0.9.0.
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> Apache OpenWhisk Catalog maintains the package catalogs of openwhisk. In
> OpenWhisk, the catalog of packages gives you an easy way to enhance your
> app with useful capabilities, and to access external services in the
> ecosystem.
> Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty
> and NGINX.
>
> OpenWhisk Catalog and apigateway vote thread:
>
> https://lists.apache.org/thread.html/87b2d4006c3502a6cc402ea54f940ddb5ae9dcae958779d60a75d875@%3Cdev.openwhisk.apache.org%3E
>
> OpenWhisk Catalog and apigateway vote result thread:
>
> https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
>
> This release comprises of source code distribution only.
>
>
> For OpenWhisk Catalog:
> The source code artifact of OpenWhisk Catalog can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk catalog is:
> openwhisk-catalog-0.9.0-incubating-sources.tar.gz:
> 3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD
> 010EFE8B
>  4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk catalog can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc
>
>
> For OpenWhisk Apigateway:
> The source code artifact of OpenWhisk Apigateway can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk apigateway is:
> openwhisk-apigateway-0.9.0-incubating-sources.tar.gz:
> F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E
> EAA0EFA5
>  AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk apigateway can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc
>
>
> KEYS file is available at:
> https://www.apache.org/dist/incubator/openwhisk/KEYS
> This key has been validated here:
> http://pgp.mit.edu/pks/lookup?search=houshengbo=index
>
> This is the first time that Apache OpenWhisk: Catalog and Apigateway
> request for a release, so there is no file of CHANGELOG.
>
> The documentation on how to verify the artifacts can be found at:
>
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
>
> We are currently using the tool called openwhisk-release(
> https://github.com/apache/incubator-openwhisk-release) to release all the
> modules of OpenWhisk. The instruction for release managers can be found at:
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
> This tool
> supports  both manual and automated modes to package the source code, sign
> the artifacts and upload the artifacts into Apache SVN repositories.
>
> 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
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes 

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

[Sergio Fernández]

+1 (binding)

On Wed, Sep 12, 2018, 08:40 Dave Fisher  wrote:

> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: [VOTE] Apache MXNet (incubating) 1.3.0 release RC0

[Sergio Fernández]

+1 (binding)

So far I've checked:
* signatures and digests (md5 checksums can be removed)
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* LICENSE & NOTICE files look good
* no binary files in the source release
* clean build (osx 10.12.6)

I'd like to state this is a just a legal binding vote, which is what we
check at this stage. Functionally speaking the podling is responsible of
the good state of every release. I remark that because from the dev@ vote I
can't see that feeling represented unanimously by the community.


On Fri, Sep 7, 2018, 11:36 Roshani Nagmote 
wrote:

> Hi all,
>
> This is a call for releasing Apache MXNet (incubating) 1.3.0, release
> candidate RC0.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
>
> *
> https://lists.apache.org/thread.html/8ad6f14811be465cdf663d6962980fd95e12193626292631a21ec6f1@%3Cdev.mxnet.apache.org%3E
> <
> https://lists.apache.org/thread.html/8ad6f14811be465cdf663d6962980fd95e12193626292631a21ec6f1@%3Cdev.mxnet.apache.org%3E
> >*
>
> Results thread:
>
> *
> https://lists.apache.org/thread.html/8dad26e9a485180a3dd36f2b54de24395b626a57b5e847bc99dda0e9@%3Cdev.mxnet.apache.org%3E
> <
> https://lists.apache.org/thread.html/8dad26e9a485180a3dd36f2b54de24395b626a57b5e847bc99dda0e9@%3Cdev.mxnet.apache.org%3E
> >*
>
> The source tarball, including signatures, digests etc. can be found at:
>
> *https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.0.rc0/
> *
>
> The release tag can be found here:
>
> *https://github.com/apache/incubator-mxnet/releases/tag/1.3.0.rc0
> *
>
> The release hash is b3be92f4a48bce62a5a8424271871c2f81c8f7f1 and can be
> found here:
>
> *
> https://github.com/apache/incubator-mxnet/commit/b3be92f4a48bce62a5a8424271871c2f81c8f7f1
> <
> https://github.com/apache/incubator-mxnet/commit/b3be92f4a48bce62a5a8424271871c2f81c8f7f1
> >*
>
> Release artifacts are signed with the following key:
>
> CB91 64C7 6A80 3D86 1DE1  6E5B 9105 2D92 2E28 A38F
>
>
> KEYS file available:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> The vote will end on Tuesday, September 11th, 11:30am PDT or until the
> necessary number of votes is reached.
>
> [ ] +1 Release this package as 1.3.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Roshani
>

Re: [CANCELLED][VOTE] Apache MXNet (incubating) 1.2.1 release RC0

[Sergio Fernández]

Exactly, 1.2.2 addressing the warning issue. Specially since 1.3.0 is being
already discussed at dev@. Anyway, the podling can learn from these things.

On Tue, Jul 3, 2018, 00:34 Justin Mclean  wrote:

> Hi,
>
> > Agree with Dave: incubating releases are not cheap…
>
> Also agree. Seems to me like something that could be improved on in a
> later release - release early and often! [1]
>
> Thanks,
> Justin
>
> 1. https://en.wikipedia.org/wiki/Release_early,_release_often
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [CANCELLED][VOTE] Apache MXNet (incubating) 1.2.1 release RC0

[Sergio Fernández]

Agree with Dave: incubating releases are not cheap...

On Mon, Jul 2, 2018, 20:02 Anirudh  wrote:

> Hi Dave,
>
> Thank you for your inputs. To give more context, the reason we are doing
> the release is to fix a backwards incompatible change with the save_params
> API. This issue impacted some of our users and the warning message in RC0
> showed an alternative API for one use case but not the other when
> save_params was called. We are fixing it to provide a warning message for
> both use cases, so that users may not end up replacing save_params with the
> wrong API.
> My sincere apologies to the mentors, for creating additional work.
>
> Anirudh
>
> On Mon, Jul 2, 2018, 6:44 PM Dave Fisher  wrote:
>
> > Mentors all - Releases are not cheap and we are all volunteers.
> >
> > Can we teach Release Managers to have a little more judgement about when
> > to pull a release?
> >
> > It seems to be too risk adverse to cancel this vote due to a warning
> > message.
> >
> > My 2 cents.
> >
> > Regards,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On Jul 2, 2018, at 5:45 PM, Anirudh  wrote:
> > >
> > > Hi,
> > >
> > > We are cancelling this vote because we need to improve the warning
> > message
> > > when users use a deprecated API: `save_params`. We will address the
> issue
> > > and send out a new release for another vote.
> > >
> > > Thanks,
> > >
> > > Anirudh
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Apache MXNet (incubating) 1.2.1 release RC0

[Sergio Fernández]

+1 (binding)

So far I've checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* LICENSE & NOTICE files look good
* no binary files in the source release
* clean build (osx 10.12.6)

Some minor details I'd like to comment:
* I don't understand what's the purposed of CODEOWNERS file in the source
release
* I've noticed the patch release is not included in the README's changelog.

On Fri, Jun 22, 2018 at 12:16 PM Anirudh  wrote:

> Hi all,
>
> This is a call for releasing Apache MXNet (incubating) 1.2.1, release
> candidate RC0.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/52a6487bc1389d8865ccc0e42ade49
> edde02c061090389616c8088d5@%3Cdev.mxnet.apache.org%3E
>
> Results thread:
>
> https://lists.apache.org/thread.html/1d833bc94897132590950668eaff7d
> 7e253894e2c274b1223ef733e1@%3Cdev.mxnet.apache.org%3E
>
> The source tarball, including signatures, digests etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.2.1.rc0/
>
> The release tag can be found here:
>
> https://github.com/apache/incubator-mxnet/releases/tag/1.2.1.rc0
>
> 
> The release hash is daa957c9c811b1abd09b98e8fb5ff2c06cad9ad8 and can be
> found here:
>
> https://github.com/apache/incubator-mxnet/commit/
> daa957c9c811b1abd09b98e8fb5ff2c06cad9ad8
>
> Release artifacts are signed with the following key:
>
>
> 0D04 3D0F 92CA 7333 22A8  D131 9067 CC8E AF55 CD6D
>
>
> KEYS file available:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> The vote will end at Tuesday June 26th, 12:15 PDT.
>
> [ ] +1 Release this package as 1.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Anirudh
>

Re: [VOTE] Retire the Slider podling

[Sergio Fernández]

+1

On Sun, May 20, 2018, 10:59 Billie Rinaldi  wrote:

> After a long period of low activity, the Slider PPMC has recently decided
> upon retirement [1]. Please vote on whether we should retire the Slider
> podling. Here is my +1 (binding).
>
> [ ] +1 Retire Slider
> [ ] +0 No opinion
> [ ] -1 Do not retire Slider because ...
>
> This vote will remain open for 72 hours.
>
> [1]: https://s.apache.org/V8SB
>

Re: [VOTE] Apache MXNet (incubating) 1.2.0 release RC3

[Sergio Fernández]

+1 (binding)

So far I've checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* LICENSE & NOTICE files look good despite the many third-party code (CC-BY
files from RC2 are gone)
* no binary files in the source release
* clean build



On Tue, May 15, 2018 at 12:16 PM, Anirudh Subramanian <
anirudh2...@apache.org> wrote:

> Hi all,
>
> This is a call for releasing Apache MXNet (incubating) 1.2.0, release
> candidate RC3.
> As suggested by Justin and Henri, we have removed the two category b
> license files: DevGuide.md from the release source tarball.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/fee7800da4b701cb62d6dd7c1b43ef
> d44c94a3a386f3adb48f343d6e@%3Cdev.mxnet.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/0a43205e47a02a528873e16fe0e578
> 9dfcfebc8a8539f17bbcde2062@%3Cdev.mxnet.apache.org%3E
>
> The source tarball, including signatures, digests etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.2.0.rc3/
>
> The release tag can be found here:
> https://github.com/apache/incubator-mxnet/releases/tag/1.2.0.rc3
>
> 
> The release hash is 297c64fd2ee404612aa3ecc880b940fb2538039c and can be
> found here:
> https://github.com/apache/incubator-mxnet/commit/
> 297c64fd2ee404612aa3ecc880b940fb2538039c
>
>  297c64fd2ee404612aa3ecc880b940fb2538039c>
> Release artifacts are signed with the following key:
> 0D04 3D0F 92CA 7333 22A8  D131 9067 CC8E AF55 CD6D
>
> KEYS file available:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> For information on the contents of the release see:
>
> https://cwiki.apache.org/confluence/display/MXNET/
> Apache+MXNet+%28incubating%29+1.2.0+Release+Notes
>
> The vote will end at 1:00 PM on Friday, May 18th, PDT.
>
> [ ] +1 Release this package as 1.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
>
> Anirudh
>

Re: [VOTE] Resolution to graduate Apache FreeMarker to TLP

[Sergio Fernández]

My +1 (binding).

It has been an interesting journey. Now the project deserves more as TLP.

On Feb 19, 2018 02:45, "Jacopo Cappellato" <jaco...@apache.org> wrote:

> Hi all,
>
> The FreeMarker community has discussed [1] and voted [2] positively on
> graduating to a top level project (TLP). The resolution for the graduation
> has been proposed and discussed in this list [3].
> Information about FreeMarker can be found in the status page [4],
> in the project maturity model [5] and in the website [6].
>
> I am now calling a VOTE to ask the IPMC to recommend the resolution to the
> ASF Board:
> the proposed resolution can be found at the bottom of this email.
> The vote will be open for 72 hours.
>
> [ ] +1 recommend to the Board the resolution to graduate Apache FreeMarker
> to a TLP
> [ ] +0 no opinion
> [ ] -1 don't graduate Apache FreeMarker to a TLP (please specify a reason)
>
> Thanks,
> Jacopo Cappellato
>
> References:
> [1] Community graduation discussion: https://s.apache.org/gYMw
> [2] Community graduation vote: https://s.apache.org/MNdd
> [3] Incubator resolution discussion: https://s.apache.org/xdI3
> [4] Project status page:
> http://incubator.apache.org/projects/freemarker.html
> [5] Project maturity model: https://s.apache.org/ixlR
> [6] Freemarker website: https://freemarker.apache.org/
>
> The proposed Resolution of the Apache FreeMarker project:
>
> --
>
> Establish the Apache FreeMarker 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 template engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache FreeMarker Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache FreeMarker Project be and hereby is
> responsible for the creation and maintenance of software
> related to a template engine, and be it further
>
> RESOLVED, that the office of "Vice President, Apache FreeMarker" 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 FreeMarker Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache FreeMarker 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 FreeMarker Project:
>
>   * Dániel Dékány   <ddek...@apache.org>
>   * David E. Jones<jone...@apache.org>
>   * Jacopo Cappellato   <jaco...@apache.org>
>   * Jacques Le Roux <jler...@apache.org>
>   * Nan Lei <nan...@apache.org>
>   * Sergio Fernández<wik...@apache.org>
>   * Woonsan Ko  <woon...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány
> be appointed to the office of Vice President, Apache FreeMarker,
> 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 Apache FreeMarker Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator FreeMarker podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator FreeMarker podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
> --
>

Re: [VOTE] Apache MXNet (incubating) 1.1.0 release RC1

[Sergio Fernández]

My +1 (binding). So far I've checked:

* incubating suffix
* incubator DISCLAIMER exists
* signatures and checksums match
* LICENSE& NOTICE file look good enough, although it may require a further
review
* no binary files included in the source release
* release builds

Glad to see the good progress on the different LICENSE files. I think it'd
be good to assist the podling on a more extensive analysis for the upcoming
releases.


On Tue, Feb 13, 2018 at 11:37 PM, YiZhi Liu  wrote:

> Hi all,
>
> As we have updated the LICENSE file which caused the failure vote for
> Apache MXNet (incubating) 1.1.0.RC0, this is a call for a releasing
> Apache MXNet (incubating) 1.1.0, release candidate 1.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/500fb648e8629249b904d9fc56e773
> 7c5312dfe54c17d4d5d06468a8@%3Cdev.mxnet.apache.org%3E
>
> Result thread:
> https://lists.apache.org/thread.html/afaf45dda45da60692476c56a268b9
> 5dd0663bb193f8c77ac372631a@%3Cdev.mxnet.apache.org%3E
>
> PR which fixes the license:
> https://github.com/apache/incubator-mxnet/pull/9701
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.1.0.rc1/
>
> The tag to be voted upon is 1.1.0.rc0:
> https://github.com/apache/incubator-mxnet/releases/tag/1.1.0.rc1
>
> The release hash is 07a83a0325a3d782513a04f47d711710972cb144:
> https://github.com/apache/incubator-mxnet/commit/
> 07a83a0325a3d782513a04f47d711710972cb144
>
> Release artifacts are signed with the following key:
> F42C 1A6E 634C 105E 8D98  5105 CA75 1254 E97B 9FE4
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/
> Apache+MXNet+%28incubating%29+1.1.0+Release+Notes
>
> The vote will end at 11:35 pm on Friday, Feb 16th, PST.
>
> [ ] +1 Release this package as 1.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> --
> Yizhi Liu
> DMLC member
> Amazon Web Services
> Vancouver, Canada
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire iota

[Sergio Fernández]

+1 (binding)

On Feb 4, 2018 14:44, "Justin Mclean"  wrote:

> Hi,
>
> This is a call to vote for the retirement of the Iota podling.
>
> The podling has discussed retirement [1], has not made a single release
> and there's been little activity on it’s mailing list [2] and repos [3] in
> recent time.
>
> [ ] +1 to retire
> [ ] +/- 0 to retire
> [ ] -1 don't retire because...
>
> Thanks,
> Justin
>
> 1. https://lists.apache.org/thread.html/f762acf82cf0bf7609ec036551c6b4
> 969cd0c45a565d28fc5b01a017@%3Cdev.iota.apache.org%3E
> 2. https://lists.apache.org/list.html?d...@iota.apache.org:lte=3M:
> 3. https://github.com/apache/incubator-iota
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Who should I contact to talk about GSoC 2018?

[Sergio Fernández]

ComDev: d...@community.apache.org

On Jan 16, 2018 00:14, "吴晟 Sheng Wu"  wrote:

> Hi All,
>
>
> Several students reach me, ask me about GSoC 2018. Who should I ask?
>
>
> Thanks.
>
>
> --
> Sheng Wu
> Apache SkyWalking creator and PPMC member

Re: [VOTE] Release Apache Taverna Server 3.1.0-incubating RC3

[Sergio Fernández]

+1 (binding)

So far I've checked:

* Source releases match with source repo
* Signatures and digests
* Headers, LICENSE files.
* Build on a clean env OpenJDK 1.8.0_144, Maven 3.5.0, Debian amd64)

I've noticed some minor issues at L files, as I think Justin already
pointed out, that should be addressed in the next release.


On Jan 13, 2018 16:23, "Stian Soiland-Reyes"  wrote:

The Apache Taverna IPMC has voted +3 to release
Apache Taverna Server 3.1.0-incubating.

This vote carries over +1 binding vote from IPMC members.

Vote thread:
https://lists.apache.org/thread.html/5cde355f427de0ff7be6800
2c578387ef7116573d197a6cafc1ad94b@%3Cdev.taverna.apache.org%3E

Taverna Server allows remote execution of Apache Taverna workflows, exposed
as
REST Web APIs and WSDL Web Services. This release is based on Apache Taverna
Command-line 3.1.0.


Release candidates to be voted over are available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/sou
rce/taverna-parent-3-incubating-RC3/

https://dist.apache.org/repos/dist/dev/incubator/taverna/sou
rce/taverna-server-3.1.0-RC3/


SHA-1 checksums:
6d779941bec29d327e22d2a76ec1069d82c4c28d  apache-taverna-parent-3-incuba
ting-source-release.zip
4aebfdeecb78645365cab868878dc85c34f04ecc  apache-taverna-server-3.1.0-in
cubating-source-release.zip


MD5 checksums:
11b15c0065541645976658387e4c5030  apache-taverna-parent-3-incuba
ting-source-release.zip
a1ed882e11b2e5a7af58486800f5e8aa  apache-taverna-server-3.1.0-in
cubating-source-release.zip


Build the release candidate *in the above order* using:

mvn clean install


The release candidates correspond to the following git commits:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-
maven-parent.git;a=commit;h=adecb277e6179ee3f8cbd099b0bffe7aa3e38223
https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-
server.git;a=commit;h=77884cbcc96a065671d920766931819b60f40b53



Release candidates are signed with a GPG key available at:
https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS


A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachetaverna-1018



Please vote on releasing these packages as:

Apache Taverna Maven Parent 3-incubating
Apache Taverna Server 3.1.0-incubating

The vote is open for at least 72 hours and passes if a majority of at least
three +1 Apache Incubator IPMC votes are cast.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...


--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718


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

Re: [VOTE] Accept ECharts for Apache Incubation

[Sergio Fernández]

+1 (binding)

On Jan 12, 2018 14:13, "Kevin A. McGrail"  wrote:

> Hi All,
>
> I would like to start a VOTE & I vote +1 to bring the ECharts project in
> as an Apache incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [ ] +1 Accept ECharts into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept ECharts into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
> https://wiki.apache.org/incubator/EChartsProposal
>
> Regards,
> KAM
>
>
> ECharts Proposal
>
> Abstract
>
> ECharts is a charting and data visualization library written in JavaScript.
>
> Proposal
>
> ECharts provides a powerful, interactive charting and data visualization
> library and framework for web browser, mobile App and backend usage.
>
> Background
>
> A primary goal of data visualization is to communicate information clearly
> and efficiently via statistical graphics, plots and other graphics.
>
> Numerical data may be presented in dots, lines, or bars, to visually
> communicate a quantitative message. Effective visualization helps users to
> analyze data .It makes complex data more readable, understandable.[1]
>
> Now data visualization concerns mainly about presentation and propagation
> in web, ECharts uses JavaScript as its basic programing language. It brings
> great compatibility across multiple platforms, not only in web browsers,
> but also in mobile Apps via embedded web engine or in backend environment
> via the techniques of headless browser.
>
> Rationale
>
> ECharts encapsulates the underlying data transformation, control flow,
> visual encoding and rendering, receiving the visualization requirements
> with declarative language, and produces interactive charts and components.
> We will highlight the features below to illustrate the power that ECharts
> already has, and our concerns and our visions:
>
> User Diversity:
>
> ECharts expects that its users are not only web developers, but also
> people with lesser programing skills. So ECharts enables users to describe
> data and settings with declarative language, which lowers the barrier but
> without losing the power, and benefit to transfer and store.
>
> Configurable Interactions:
>
> ECharts has provided plenty of interactions and aims at providing more.
> Both human interactions and the interactions with upper program are
> supported and can be configurable.
>
> Large Data:
>
> Although the browser environment and JavaScript bring some performance
> limits in visualizing large data or performing animations, ECharts have
> been adopting various optimization techniques to rise the upper limit of
> the amount of data that it can process, and keep improving the fluency of
> interactions and animations.
>
> Cross-Platform:
>
> The underlying render engine of ECharts can be switched between
> HTMLCanvas, SVG, or VML, which provides good compatibility and brings
> opportunities to optimize performance according to different platform and
> usage scenarios. Besides, ECharts can also works in backend environment via
> headless techniques.
>
> ECharts can be created using headless browsers to pregenerate reports on
> more powerful machines for better performance on resource-limited devices
>
> Extension and Customization:
>
> ECharts provides extension mechanisms to make new types of chart and
> components, adopt other layout algorithms, or even adopt other render
> techniques. Various developers have contributed different types of
> extensions based on ECharts.[2]
>
> Current Status
>
> ECharts has been an open source project on GitHub[3] since 2013. Currently
> it has more than 20k stars, more than 50k monthly downloads[4] in NPM, and
> is one of the most popular repositories in topic of data visualization
> category in GitHub.[5] And it has been used in many products of Baidu and
> other companies such as Alibaba, Tencent, Netease, XinHua News
> Agency,National Bureau of Statistics of China, Sina, State Grid Corporation
> of China, Lenovo, Ctrip etc.
>
> Meritocracy
>
> The ECharts project already operates on meritocratic principles. It was
> originally created by Lin Zhifeng in 2013,adding developers worldwide and
> has accepted multiple major patches from a diverse set of contributors.
>
> We will follow ASF meritocratic principles to encourage more developers to
> contribute in this project. We know that only active and committed
> developers from a diverse set of backgrounds can make ECharts a successful
> project. We are also improving the project documentation and code to help
> new developers to get started quickly.
>
> Community
>
> ECharts has been building an active community for the last four years.
> 

Re: [VOTE] Retire Wave

[Sergio Fernández]

+1 (binding)

On Jan 8, 2018 19:57, "John D. Ament"  wrote:

> All,
>
> This is a call to vote for the retirement of the Wave podling.
>
> The podling has positively voted to retire [1].  I now call upon the IPMC
> to confirm this retirement.
>
> [ ] +1 to retire
> [ ] +/- 0 to retire
> [ ] -1 don't retire because...
>
> The podling is working on a migration plan, it seems they will move the
> code to github somewhere, and will work on it as seen fit there.
>
> John
>
> [1]:
> https://lists.apache.org/thread.html/fe4b7a240facbebeded29d7d9d8c73
> 3c0e5e624f07b7a110887c2f16@%3Cwave-dev.incubator.apache.org%3E
>

Re: [VOTE] Accept PLC4X into the Apache Incubator

[Sergio Fernández]

+1 (binding)

On Dec 14, 2017 15:19, "Justin Mclean"  wrote:

> Hi All,
>
> I would like to start a VOTE to propose the PLC4X project as a podling
> into the Apache incubator.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html  foundation/voting.html>
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept PLC4X into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept PLC4X into the Apache Incubator because ...
>
> The proposal is listed below, but you can view it on the wiki:
> https://wiki.apache.org/incubator/PLC4XProposal
>
> = PLC4XProposal =
>
> == Abstract ==
>
> PLC4X is intended to become a set of libraries for communicating with
> industrial programmable logic controllers (PLCs) using a variety of
> protocols
> but with a shared API.
>
> For the most used of these protocols, PLC4X will provide implementations of
> drivers. Each protocol driver is hereby provided by an individual artifact.
>
> In a first step, we are concentrating on Java but will be hoping to be
> able to
> port implementation to C and other languages.
>
> == Background ==
>
> Industrial machines have been controlled by PLCs for more than 30 years. In
> simpler pieces of machinery these may operate autonomously, in more complex
> ones several to hundreds of these industrial computers communicate with
> each
> other.
>
> == Rationale ==
>
> Currently software for communicating with PLCs is mainly proprietary
> software
> and a whole ecosystem of closed-source solutions exist. Usually this
> software
> is very expensive and licensing implies a lot of restrictions on its usage.
> There is a small set of open-source libraries available, but unfortunately
> most
> of these are GPL licensed and hereby disqualify themselves from commercial
> use.
> Most of these are direct ports from C/C++ implementations and therefore
> inherit
> their API. Usually these are implemented blocking socket operations and
> have
> great problems with concurrency. Also, the APIs of these tools differ
> quite a
> lot, so porting a software from communicating with one type of PLC to
> another
> sometimes requires re-writing a great part of the software.
>
> There are multiple rationales behind this project:
>
>  1. By providing libraries with Apache license, it will be possible to
> create
> commercial applications which access PLCs
>  2. By providing a universal API for different protocols, it reduces the
> vendor
> lock-in when creating software
>  3. Most of the proprietary commercial solutions are based on Windows
> systems,
> especially the Siemens solutions, sometimes require maintaining un-patched
> versions of older Windows version in order to run, this is a huge security
> risk
> (See Stuxnet)
>  4. Most of the proprietary commercial solutions don't scale. Running them
> in
> public/private clouds and/or in containers is completely out of the
> question.
>
> As a result of above, it would be possible to start writing secure,
> scalable
> and reliable software using the full stack of open-source solutions and
> hereby
> open a complete new market for developers. In order to make this even
> easier,
> we are planning on directly providing adapters and examples for using PLC4X
> together with other Apache frameworks.
>
> == Initial Goals ==
>
> Develop a universal API for accessing industrial programmable logic
> controllers
> in a protocol-agnostic way. Also implement Java versions of drivers for the
> most prominent protocols: S7, Modbus and OPC-UA - but not limited to
> those. On
> the side of the adapters, for existing OS solutions, we are currently
> working
> on adapters for: Apache Edgent (incubating), Apache Camel and eventually
> even
> Apache Brooklyn.
>
> Also, we will be providing a Scala wrapper to ease integration of PLC4X in
> Scala based systems with an API Scala developers should easily adopt.
>
> As soon as a C version exists, we are planning on providing an Apache
> Mynewt
> adapter as we see great benefits on this combination.
>
> == Current Status ==
>
> === Meritocracy ===
>
> PLC4X was initially created by Christofer Dutz. He is an Apache Member and
> also
> involved in a variety of Apache and Non-Apache Open-Source projects. Being
> PMC
> of the Apache Flex, Apache Kibble and the Apache Travel Assistance he
> definitely knows how Apache works and is a strong advocate of the Apache
> Way.
> He is also currently helping the Apache Edgent project as member of the
> PPMC.
> However, the team working on PLC4X also includes a diverse set of
> additional
> Apache Committers and Members as well as people, that are not yet
> affiliated
> with any Apache project. The team working on PLC4X are both working for
> codecentric as well as other entities, such as commercial companies as
> 

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

[Sergio Fernández]

+1 (binding)

So far I've successfully checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* clean build (Java 1.8.0_151, Debian amd64)


On Mon, Dec 11, 2017 at 6:52 PM, Nozomi Kurihara 
wrote:

> This is the fourth release candidate for Apache Pulsar, version
> 1.21.0-incubating.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management
> for subscribers, and cross-datacenter replication.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Fixed issues:
> https://github.com/apache/incubator-pulsar/milestone/10?closed=1
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-1.21.0-incubating-candidate-3/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1005/
>
> The tag to be voted upon:
> v1.21.0-incubating-candidate-3
> https://github.com/apache/incubator-pulsar/releases/tag/
> v1.21.0-incubating-candidate-3
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Link to the voting thread from the dev@pulsar mailing list:
> https://lists.apache.org/thread.html/51c0737bcfee37073017291adb6453
> c27f9562dc9905f8eccdc78abe@%3Cdev.pulsar.apache.org%3E
>
> Please download the the source package, and follow the README to build and
> run the Pulsar standalone service.
>
> This vote will stay open for at least 72 hours (around December 15th 2017,
> 10:00 GMT).
>
> Regards,
> Nozomi
>

Re: [VOTE] Graduate the Apache Trafodion Project from Incubator to a TLP

[Sergio Fernández]

+1 (binding)

On Nov 28, 2017 12:01, "Pierre Smits"  wrote:

> Hi all,
>
> The Trafodion community started an initial discussion graduating from the
> Incubator (see [1]) and had a consensus that the project is good to
> graduate. The community proceeded to draft the graduation resolution,
> discussed it [2], and voted on it [3]. The community vote passed with 42 +1
> votes (40 advisory, 2 binding votes), no -1 votes or  +0 (abstains) votes.
>
> The discussion on the graduation of the Apache Trafodion project and the
> proposed draft resolution proceeded to the general mailing list of the
> Apache Incubator project [4], and advice was provided about some wording in
> the draft resolution. The proposed changes to that draft are incorporated
> into the graduation resolution shown below. I would now like to call for a
> recommendation vote to present the Board of The Apache Software Foundation
> with the resolution solution to graduate from incubation and establish
> Apache Trafodion as a top-level project.
>
> Apache Trafodion entered incubation in May 2015. Since then the project has
> produced several releases and has grown the community, the committer pool
> and the PPMC. For each release source artefacts have been voted on and made
> available to the public on the Apache Distribution Network. Given all the
> feedback provided in various discussions about our progress and graduation,
> we feel confident that the project is ready to graduate from incubation.
>
> Please vote on whether to graduate Apache Trafodion from incubation and
> recommend the graduation resolution below to the ASF Board.
>
> [  ] +1 Graduate the Apache Trafodion Project from the Incubator
> [  ] +0 Abstain
> [  ] -1 Don't graduate the Apache Trafodion Project from the Incubator
> because...
>
> This vote will be open for at least 72 hours. Thanks to all Trafodion
> Mentors, all Trafodion Contributors for their support and contributions and
> all in the Apache Incubator Project who took the time to provide their
> insights and support.
>
> The full text of the resolution from [5] is below. The resolution will
> be submitted
> to the Board of Directors of The Apache Software Foundation for their
> consideration upon approval by the Apache Incubator PMC members.
>
> [1] [DISCUSSION] Graduation of The (incubating) Apache Trafodion Project
>  3ad86ff21839e98e0ae68520e3@%3Cdev.trafodion.apache.org%3E>
> [2] [VOTE] Graduate from Incubator and become a top-level project
>  03a1585d398d7820b26be9a255@%3Cdev.trafodion.apache.org%3E>
> [3]  [RESULT][VOTE] Graduate from Incubator and become a top-level project
>  56302cf98fe212909fefb8e76f@%3Cdev.trafodion.apache.org%3E>
> [4] [DISCUSS] Resolution to graduate the incubating Apache Trafodion
> Project
>  69b9e08b6e4cc69fafdc21531e@%3Cgeneral.incubator.apache.org%3E>
>
>
> Best Regards,
>
> Pierre Smits
>
> -
>
> Establish the Apache Trafodion 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 webscale SQL-on-Hadoop solution enabling transactional or
>
> operational workloads.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache Trafodion Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache Trafodion Project be and hereby is responsible
>
> for the creation and maintenance of software related to a webscale
>
> SQL-on-Hadoop solution enabling transactional or operational workloads;
>
> and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache Trafodion" 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 Trafodion
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache Trafodion
>
> 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 Trafodion
>
> Project:
>
>
>  * Amanda K Moran 
>
>  * Dave Birdsall  
>
>  * Gunnar Tapper  
>
>  * Ming Liu   
>
>  * Pierre Smits   
>
>  * Roberta Marton 
>
>  * Selva Govindarajan 
>

Re: [VOTE] Accept SkyWalking into the Apache Incubator

[Sergio Fernández]

+1

On Dec 4, 2017 03:17, "mck"  wrote:

>
> After some discussion on the SkyWalking proposal, I'd like to raise the
> vote on accepting SkyWalking into into the Apache Incubator.
>
> https://lists.apache.org/thread.html/b4e7205e77fe382b4cd096fb6da28b
> 70053e0722b3dd7ae8ac389f8a@%3Cgeneral.incubator.apache.org%3E
>
>
> A vote for accepting a new Apache Incubator podling is a majority vote
> for which only Incubator PMC member votes are binding.
> Votes from other people are also welcome as an indication of peoples
> enthusiasm (or lack thereof).
>
> Please do not use this VOTE thread for discussions. If needed, start a
> new thread instead.
>
> This vote will run for at least 72 hours.
> Please VOTE as follows:
>[] +1 Accept SkyWalking
>[] +0 Abstain
>[] -1 Do not accept Skywalking, because ...
>
>
> The proposal below is also on the wiki:
> https://wiki.apache.org/incubator/SkyWalkingProposal
>
>
> = Abstract =
> Skywalking is an APM (application performance monitor), especially for
> microservice, Cloud Native and container-based architecture systems.
> Also known as a distributed tracing system. It provides an automatic way
> to instrument applications: no need to change any of the source code of
> the target application; and an collector with an very high efficiency
> streaming module.
>
> = Proposal =
> The goal of this proposal is to bring the existing
> [[https://github.com/OpenSkywalking/skywalking|Skywalking]] codebase and
> existing developers and community into the Apache Software Foundation
> (ASF) in order to build a global, diverse and self-governed open source
> community in APM field.
>
> This project started in Open Source on GitHub about more than 2 years
> ago. Beginning with a small SDK and collector. So far the
> [[https://github.com/OpenSkywalking/Organization|OpenSkywalking]]
> governs the project through the PMC and Committer Team.
>
> OpenSkywalking is submitting this proposal to donate the Skywalking
> sources code and  associated artifacts (documentation, web site content,
> wiki, etc.) to the Apache Software Foundation Incubator under the Apache
> License, Version 2.0. These artifacts are currently available on GitHub
> at https://github.com/OpenSkywalking and include:
>  * Skywalking: The java sniffer(agent) for collecting data, and
>  collector for analysing and persistence.
>  * Skywalking-UI: The web UI for skywalking APM
>
> ''Voted on submitting the proposal to the Incubator.
> [[https://github.com/OpenSkywalking/Organization/issues/11|Check
> here]]''
>
> = Background =
> Mircro-service, Cloud Native and container-based architecture system are
> becoming more and more popular, so the traditional monitoring, like
> application loggings, can provide less information because of the
> distributed isolates the relations. Based on the
> [[https://research.google.com/pubs/pub36356.html|Google Dapper paper]],
> many tracing systems born. The OpenSkywalking organisation was created
> with  Skywalking made based on tracing, but not just tracing, it adds
> additional value by reducing the sniffer (agent) cost, analysis and
> visualization.
>
> In 2015, Skywalking project started, when service-oriented architecture
> became popular. At first, skywalking provided a very simple SDK, and
> collected data into a HBASE cluster. After we opened on the GitHub, the
> community gives the feedbacks about how difficult to maintain a HBase
> cluster, even harder than the applications under monitored. So, in 2.x
> 2016, skywalking provided a self-designed storage, and update the SDK to
> a javaagent with supporting auto-instrumentation. Then since 2017, more
> and more contributors joined, we set up the PMC team and committer team.
> Skywalking evolved to an APM, and more and more features provided since
> then.
>
> = Rationale =
> Skywalking includes these primary parts:
>  1. Provide an anto-instrument sniffer, which is based on Javaagent and
>  collects events and traces happened inside JVM, with little CPU/Memory
>  cost.
>  1. An extendable `tracing data protocol suit` with gRPC and HTTP
>  implementations, is compatible for other language agent or SDK.
>  1. Provide Collector, which accepts the `tracing data protocol suit`,
>  and does the analysis and aggregation inside for detecting the
>  relationships among applications and services, generating the metrics,
>  and altering.
>  1. Provided our own UI, which visualizes the topological graph of
>  related applications and services, trace stack, metrics and alerting.
>
> Also, Skywalking team is passionate about community cooperations.
> Skywalking is a supported tracer and member of
> [[OpenTracing|http://opentracing.io]]. Also we take part in the
> [[https://github.com/TraceContext/tracecontext-spec|TraceContext
> Specs]], which is about `tracing context propagation format`. The
> founder of the project, Sheng Wu, is the member of these organizations,
>
> There is a strong need for an open, easy-to-use APM 

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC1

[Sergio Fernández]

+1 (binding)

Most of the minor issues I've seen so far are already reported by Justin.
So let's address them for the next release. Good luck at NIPS!



On Nov 30, 2017 4:45 PM, "Chris Olivier"  wrote:

Hello All,


This is a call for releasing Apache MXNet (incubating) 1.0.0, release
candidate 1.


Apache MXNet community has voted and approved the release.


*Vote thread:*

https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E


*Result thread:*

https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E


*The source tarball, including signatures, digests, etc. can be found at:*

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc1/



*The release tag can be found here: *

https://github.com/apache/incubator-mxnet/tree/1.0.0.rc1



*The release hash is *25720d0e3c29232a37e2650f3ba3a2454f9367bb* and can be
found here:*





*Release artifacts are signed with the following key:*

16DD B2E2 FE0C 3925 CB13  38D7 21F3 F9AB C622 DF82



*KEY files are available here:*

https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS



*For information about the contents of this release, see:*





The vote will be open for at least 72 hours.


[ ] +1 Release this package as 1.0.0

[ ] +0 no opinion

[ ] -1 Do not release this package because...


Thanks,


-Chris Olivier

cjolivie...@apache.org

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC0

[Sergio Fernández]

Generally speaking, I follow these key aspects:

* Don't put anything in NOTICE for the sake of an MIT or a 3-clause BSD
licensed dependency.
* For an ALv2 dependency, follow the instructions in the licensing howto:
http://www.apache.org/dev/licensing-howto.html
* For all other licenses, either guess or ask.

The changes introduced by Meghna Baijal (PR #8873 and #/8876) address some
issues. What I still don't see handled correctly is the inclusion of a
binary file within the source release. Please, address that, and cast a
vote for a RC2.


On Wed, Nov 29, 2017 at 7:54 PM, John D. Ament 
wrote:

> On Wed, Nov 29, 2017 at 7:52 PM Hen  wrote:
>
> > On Wed, Nov 29, 2017 at 3:18 PM, Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > >> - A number of source file are missing license headers e.g. [15][16]
> > [18]
> > > >> [19] and many others
> > > >>
> > > >
> > > > Many of these are not Apache MXNet files but from dependencies. I'll
> > > > suggest on dev@ that these submodules be moved into a third-party/
> > > > directory.
> > >
> > > Having that clearly identified would certainly make the release a lot
> > > easier to review.
> > >
> > > > Why would it be? We only have to include the LICENSE from TVM, we
> don't
> > > > need to name them.
> > >
> > > In general all bundled software need to be added. [1]
> > >
> > > > If TVM want to be identified, they should add a NOTICE file.
> > >
> > > Licenses of permissively bundled software go in LICENSE with a few
> > > exceptions. [2] Apache licensed (v2) doesn't have to me listed [3] but
> is
> > > useful to list and you're listing other Apache licensed software in
> > LICENSE
> > > so it seemed odd to omit it.
> > >
> > > Again I suggest you run rat over the release and see if you can fix up
> > > what it finds. An annotated rat exclusion file would also be a lot of
> > help.
> > > Just try not to make the exclusions too wide as you may miss something.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> > > 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> > > 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> >
> >
> > Fair enough.
> >
> > My argument would be that it's Apache v2, so its LICENSE is in the MXNet
> > package already, but if it's out of sorts with other items already being
> > listed then that's a weak argument :)
> >
>
> Well, but it's a valid point.  the more correct thing to do is not to list
> those files, and just make it clear that every thing's Apache Licensed
> unless listed specifically.
>
>
> >
> > Hen
> >
>

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC0

[Sergio Fernández]

I correct myself, this is not the first incubating release.
My bad, I couldn't find traces of previous incubating releases to download
from the podling site.
I'll go back to check if previous VOTEs had similar issues.
So all my comments on 1.0.0-RC0 still remain valid though.

On Mon, Nov 27, 2017 at 7:37 PM, Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> * Incubator DISCLAIMER included.
> * LICENSE file contains information that should go in the NOTICE.
> * Build worked fine on my desktop (Ubuntu 17.10, GCC 7.2.0).
>
> * I'd put the install instruction somewhere more prominent
> than docs/install/index.md, and probably more CLI-friendly text document.
> Actually I was confused by the very different instruction from
> http://mxnet.apache.org/install/index.html So always take into account
> usability of your source release.
> * The KEYS file are not correctly linked in the VOTE email. They weren't
> that hard to find at https://dist.apache.org/rep
> os/dist/dev/incubator/mxnet/KEYS, but should be properly linked..
>
> Event thoughmy vote for this RC1 is -1 (binding), because:
>
> * Binary nnvm/tvm/apps/android_rpc/gradle/wrapper/gradle-wrapper.jar is
> distributed without NOTICE.
> * Files' header contain, after the normative ASF license header, confusing
> copyright information that should be cleaned to avoid confusions.
>
> Anyway, congratulations for such big milestone. Based on my experience,
> the first incubating release is always difficult. So, if you need some more
> mentor power, I could jump into dev@mxnet to help your with the upcoming
> RCs.
>
> Cheers,
>
>
> On Mon, Nov 27, 2017 at 4:48 PM, Dave Fisher <dave2w...@comcast.net>
> wrote:
>
>> Hi -
>>
>> > On Nov 27, 2017, at 4:26 PM, Chris Olivier <cjolivie...@apache.org>
>> wrote:
>> >
>> > Hello All,
>> >
>> >
>> > This is a call for releasing Apache MXNet (incubating) 1.0.0, release
>> > candidate 0.
>> >
>> >
>> > Apache MXNet community has voted and approved the release.
>> >
>> >
>> > *Vote thread:*
>> >
>> > https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
>> > 7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
>> >
>> >
>> > *Result thread:*
>> >
>> > https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
>> > ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E
>> >
>>
>> It looks like the true results are:
>>
>> IPMC Binding (mentor): 1
>> Sebastian
>>
>> PPMC “Binding”: 3
>> Chris Oliver
>> Indhu Bharanthi
>> Haibin Lin
>>
>> Contributors: 2
>>
>> There is already one IPMC vote and you are looking for two more.
>>
>> Regards,
>> Dave
>>
>> >
>> > *The source tarball, including signatures, digests, etc. can be found
>> at:*
>> >
>> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc0/
>> >
>> >
>> >
>> > *The release tag can be found here: *
>> >
>> > https://github.com/apache/incubator-mxnet/tree/1.0.0.rc0
>> >
>> >
>> >
>> > *The release hash is *862629d056fe57e0afcf987f7708967bbe29e606* and
>> can be
>> > found here:*
>> >
>> > <https://github.com/apache/incubator-mxnet/commit/
>> > 862629d056fe57e0afcf987f7708967bbe29e606>
>> >
>> >
>> >
>> > *Release artifacts are signed with the following key:*
>> >
>> > 69FF E8D6 1051 FFE7 E61B 02C2 80FD 81D7 703D F31B
>> >
>> >
>> >
>> > *KEY files are available here:*
>> >
>> > <https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc0/>
>> >
>> >
>> >
>> > *For information about the contents of this release, see:*
>> >
>> > <https://cwiki.apache.org/confluence/display/MXNET/
>> > Apache+MXNet+%28incubating%29+1.0+Release+Notes>
>> >
>> >
>> >
>> > The vote will be open for at least 72 hours.
>> >
>> >
>> > [ ] +1 Release this package as 1.0.0
>> >
>> > [ ] +0 no opinion
>> >
>> > [ ] -1 Do not release this package because...
>> >
>> >
>> > Thanks,
>> >
>> >
>> > Chris Olivier
>>
>>
>

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC0

[Sergio Fernández]

Hi,

* Incubator DISCLAIMER included.
* LICENSE file contains information that should go in the NOTICE.
* Build worked fine on my desktop (Ubuntu 17.10, GCC 7.2.0).

* I'd put the install instruction somewhere more prominent
than docs/install/index.md, and probably more CLI-friendly text document.
Actually I was confused by the very different instruction from
http://mxnet.apache.org/install/index.html So always take into account
usability of your source release.
* The KEYS file are not correctly linked in the VOTE email. They weren't
that hard to find at https://dist.apache.org/repos/dist/dev/incubator/
mxnet/KEYS, but should be properly linked..

Event thoughmy vote for this RC1 is -1 (binding), because:

* Binary nnvm/tvm/apps/android_rpc/gradle/wrapper/gradle-wrapper.jar is
distributed without NOTICE.
* Files' header contain, after the normative ASF license header, confusing
copyright information that should be cleaned to avoid confusions.

Anyway, congratulations for such big milestone. Based on my experience, the
first incubating release is always difficult. So, if you need some more
mentor power, I could jump into dev@mxnet to help your with the upcoming
RCs.

Cheers,


On Mon, Nov 27, 2017 at 4:48 PM, Dave Fisher  wrote:

> Hi -
>
> > On Nov 27, 2017, at 4:26 PM, Chris Olivier 
> wrote:
> >
> > Hello All,
> >
> >
> > This is a call for releasing Apache MXNet (incubating) 1.0.0, release
> > candidate 0.
> >
> >
> > Apache MXNet community has voted and approved the release.
> >
> >
> > *Vote thread:*
> >
> > https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
> > 7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
> >
> >
> > *Result thread:*
> >
> > https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
> > ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E
> >
>
> It looks like the true results are:
>
> IPMC Binding (mentor): 1
> Sebastian
>
> PPMC “Binding”: 3
> Chris Oliver
> Indhu Bharanthi
> Haibin Lin
>
> Contributors: 2
>
> There is already one IPMC vote and you are looking for two more.
>
> Regards,
> Dave
>
> >
> > *The source tarball, including signatures, digests, etc. can be found
> at:*
> >
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc0/
> >
> >
> >
> > *The release tag can be found here: *
> >
> > https://github.com/apache/incubator-mxnet/tree/1.0.0.rc0
> >
> >
> >
> > *The release hash is *862629d056fe57e0afcf987f7708967bbe29e606* and can
> be
> > found here:*
> >
> >  > 862629d056fe57e0afcf987f7708967bbe29e606>
> >
> >
> >
> > *Release artifacts are signed with the following key:*
> >
> > 69FF E8D6 1051 FFE7 E61B 02C2 80FD 81D7 703D F31B
> >
> >
> >
> > *KEY files are available here:*
> >
> > 
> >
> >
> >
> > *For information about the contents of this release, see:*
> >
> >  > Apache+MXNet+%28incubating%29+1.0+Release+Notes>
> >
> >
> >
> > The vote will be open for at least 72 hours.
> >
> >
> > [ ] +1 Release this package as 1.0.0
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 Do not release this package because...
> >
> >
> > Thanks,
> >
> >
> > Chris Olivier
>
>

Re: [VOTE] Release Apache FreeMarker 2.3.27 (incubating)

[Sergio Fernández]

+1 (binding)

On Oct 30, 2017 13:49, "Daniel Dekany"  wrote:

> Can someone from the IPMC take a look at this release? We are missing
> 1 binding vote. Thank you!
>
>
> Tuesday, October 24, 2017, 3:00:19 PM, Woonsan Ko wrote:
>
> > Hi all,
> >
> > Apache FreeMarker (incubating) is a template engine, i.e. a generic
> > tool to generate text output based on templates. FreeMarker is
> > implemented in Java as a class library for programmers.
> >
> > The Apache FreeMarker community has voted on and approved a proposal
> > to release Apache FreeMarker 2.3.27-incubating.
> >
> > PPMC Vote Call:
> > https://lists.apache.org/thread.html/7c25fe06137217a1a6f90bb27a620c
> 1ff2fa10231705d2b327d09d34@%3Cdev.freemarker.apache.org%3E
> >
> > PPMC Vote Result:
> > https://lists.apache.org/thread.html/ff230e650c73e4941120190c95af08
> 80d9510bd41be36fba4ea59e39@%3Cdev.freemarker.apache.org%3E
> >
> > PPMC Vote Summary:
> > 2 binding (IPMC member) +1 votes
> > 2 non-binding PPMC member +1 votes
> > 1 non-binding Committer +1 votes
> >
> > Release Notes:
> > http://freemarker.org/builds/2.3.27-voting/documentation/_
> html/versions_2_3_27.html
> >
> > Before proceed, you should know that FreeMarker 2.3.x, for a long
> > time, always releases a normal and a "gae" variant on the same time,
> > which are technically two independent source trees (Git branches). The
> > "gae" variant contains a few small modification in the Java source
> > code to be Google App Engine compliant, and has freemarker-gae as the
> > Maven artifact name. Otherwise the normal and the "gae" branches are
> > identical. Hence, they are voted on together.
> >
> > The commits to be voted upon are:
> > - Normal (non-gae) variant:
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=8e501b8ab83fb7d312791a4907ca94ef8acaf3e5
> >   Commit hash: 8e501b8ab83fb7d312791a4907ca94ef8acaf3e5
> > - "gae" variant:
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=cf2ae45d174d07a38d096958a44977cb79b1a68d
> >   Commit hash: cf2ae45d174d07a38d096958a44977cb79b1a68d
> >
> > The artifacts to be voted upon are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.27-incubating/source/
> > where the source release artifacts are:
> > - Normal (non-gae) variant:
> > apache-freemarker-2.3.27-incubating-src.tar.gz
> > - "gae" variant:
> > apache-freemarker-gae-2.3.27-incubating-src.tar.gz
> >
> > See the README inside them for build instructions!
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/woonsan.asc
> >
> > Note that for convenience, we also provide binaries:
> > https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.27-incubating/binaries/
> > and Maven artifacts in the ASF staging repositories:
> > -
> > https://repository.apache.org/content/repositories/staging/
> org/freemarker/freemarker/2.3.27-incubating/
> > -
> > https://repository.apache.org/content/repositories/staging/
> org/freemarker/freemarker-gae/2.3.27-incubating/
> >
> > We request the permission of the IPMC to publish the above release as
> > Apache FreeMarker 2.3.27-incubating. Please try out the package and
> > vote.
> >
> > The vote is open for a minimum of 72 hours or until the necessary
> > number of votes (3 binding +1s) is reached.
> >
> > [ ] +1 Release this package as Apache FreeMarker 2.3.27-incubating
> > [ ] 0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Please add "(binding)" if your vote is binding.
> >
> >
> > Woonsan Ko
> > on behalf of Apache FreeMarker Podling Project Management Committee
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache SystemML project from Incubator

[Sergio Fernández]

+1 (binding)

On May 11, 2017 02:40, "Luciano Resende"  wrote:

> Following the previous discussion, please vote on the draft resolution
> which establishes Apache SystemML as a new top-level project at the Apache
> Software Foundation, as follows:
>
> [ ] +1, Graduate Apache SystemML from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache SystemML from the Incubator (provide details)
>
> The full text of the resolution is bellow.
>
> If approved by the Apache Incubator PMC members, the proposed resolution
> will be submitted to the Board of Directors for their consideration.
>
> Thanks !
>
> 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 declarative,
> large-scale machine learning that compiles to hybrid runtime
> execution plans ranging from single node, in-memory computations,
> to distributed computations such as on Apache Hadoop MapReduce or
> Apache Spark.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SystemML Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SystemML Project be and hereby is
> responsible for the creation and maintenance of software related to
> declarative, large-scale machine learning; and be it further
>
> RESOLVED, that the office of "Vice President, Apache SystemML" 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
> SystemML Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache SystemML
> 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 SystemML
> project:
>
> * Alexandre V Evfimievski   
> * Arvind Surve  
> * Berthold Reinwald 
> * DB Tsai   
> * Deron Eriksson
> * Faraz Makari  
> * Felix Schueler
> * Fred Reiss
> * Glenn Weidner 
> * Henry Saputra 
> * Holden Karau  
> * Joseph Bradley
> * Luciano Resende   
> * Matthias Boehm
> * Nakul Jindal  
> * Mike Dusenberry   
> * Niketan Pansare   
> * Patrick Wendell   
> * Prithviraj Sen
> * Reynold Xin   
> * Rich Bowen
> * Shirish Tatikonda 
> * Xiangrui Meng 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Deron Eriksson be
> appointed
> to the office of Vice President, Apache SystemML, 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 SystemML 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 SystemML
> Project; and be it further
>
> RESOLVED, that the Apache SystemML Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> SystemML podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> SystemML podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: Publishing npm modules

[Sergio Fernández]

INFRA-12886 might be relevant, since Nexus 3.x also comes with npm support.

On Tue, Apr 11, 2017 at 5:04 PM, John D. Ament 
wrote:

> On Tue, Apr 11, 2017 at 10:00 AM Niclas Hedhman 
> wrote:
>
> > Hi,
> >
> > does anyone have any information on policy/process for uploading npm
> > modules to global registry https://registry.npmjs.org/
>
>
> You may want to check with the Cordova team, see what they've come up.
>
>
> >
> >
> > This is for convenience and should be similar to publishing to Maven
> > Central, but I would like to know if there is anything explicit about it.
> >
> > Cheers
> > --
> > Niclas Hedhman, Software Developer
> > http://polygene.apache.org - New Energy for Java
> >
>

Re: [VOTE] Release Apache FreeMarker 2.3.26 (incubating)

[Sergio Fernández]

Repeating the vote I already did at dev@freemarker:

+1 (binding)

So far I've checked:

* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* build sources in a clean environment (Ant 1.9.6, OpenJDK 1.8.0_91 64-Bit,
Debian amd64), all tests passed



On Mon, Mar 20, 2017 at 11:51 PM, Daniel Dekany <ddek...@apache.org> wrote:

> Hi all,
>
> Apache FreeMarker (incubating) is a template engine, i.e. a generic
> tool to generate text output based on templates. FreeMarker is
> implemented in Java as a class library for programmers.
>
> The Apache FreeMarker community has voted on and approved a proposal
> to release Apache FreeMarker 2.3.26-incubating.
>
> PPMC Vote Call:
> https://lists.apache.org/thread.html/a33860d7196ccdc5ec19c4ca00d152
> b95784d743995f89ad4e9acedb@%3Cdev.freemarker.apache.org%3E
>
> PPMC Vote Result:
> https://lists.apache.org/thread.html/2bf7dfa720510cf5484e0b345e6b31
> bc8c8a6933b5073d2c87902473@%3Cdev.freemarker.apache.org%3E
>
> PPMC Vote Summary:
> 2 binding (IPMC member) +1 votes
> 2 non-binding PPMC member +1 votes
> 1 non-binding Commiter +1 votes
>
> Release Notes:
> http://freemarker.org/builds/2.3.26-voting/documentation/_
> html/versions_2_3_26.html
>
> Before proceed, you should know that FreeMarker 2.3.x, for a long
> time, always releases a normal and a "gae" variant on the same time,
> which are technically two independent source trees (Git branches). The
> "gae" variant contains a few small modification in the Java source
> code to be Google App Engine compliant, and has freemarker-gae as the
> Maven artifact name. Otherwise the normal and the "gae" branches are
> identical. Hence, they are voted on together.
>
> The commits to be voted upon are:
> - Normal (non-gae) variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=876fffcfaf66bd212b02a931fdd2c69f6e0c297e
>   Commit hash: 876fffcfaf66bd212b02a931fdd2c69f6e0c297e
> - "gae" variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=43564859db4bec23e161c6fa5a32882e8bd9e40a
>   Commit hash: 43564859db4bec23e161c6fa5a32882e8bd9e40a
>
> The artifacts to be voted upon are located here:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.26-incubating/source/
> where the source release artifacts are:
> - Normal (non-gae) variant:
>   apache-freemarker-2.3.26-incubating-src.tar.gz
> - "gae" variant:
>   apache-freemarker-gae-2.3.26-incubating-src.tar.gz
>
> See the README inside them for build instructions!
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/ddekany.asc
>
> Note that for convenience, we also provide binaries:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.26-incubating/binaries/
> and Maven artifacts in the ASF staging repository:
> https://repository.apache.org/content/repositories/staging/
> org/freemarker/freemarker/2.3.26-incubating/
>
> We request the permission of the IPMC to publish the above release as
> Apache FreeMarker 2.3.26-incubating. Please try out the package and
> vote.
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache FreeMarker 2.3.26-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
> --
> Thanks,
>  Daniel Dekany
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Machine Learning in METRON

[Sergio Fernández]

Hi,

you can find the documentation at
http://metron.incubator.apache.org/documentation/

You should better reach the folks directly at
us...@metron.incubator.apache.org (subscribed sending fist a mail to
users-subscr...@metron.incubator.apache.org).

Cheers,

On Feb 17, 2017 10:13, "Savakh S"  wrote:

> Hello,
>
> I saw METRON can do machine learning analysis but I didn't find this
> feature when I installed the product. Could you please explain me more
> about ML in METRON ?
>
> Many thanks.
>
> BR
>

Re: [VOTE] Apache SystemML 0.12.0-incubating (RC2)

[Sergio Fernández]

+1 (binding)

So far I've successfully checked:
* signatures and digests
* source releases file layouts
* no binaries found at the source distribution
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* clean build

I guess it's not blocking, but the NOTICE says "2015-2016", and we're
already in 2017 ;-)

On Thu, Feb 2, 2017 at 11:39 PM, Arvind Surve <ac...@yahoo.com.invalid>
wrote:

> Please vote on releasing the following candidate as Apache SystemML
> version 0.12.0-incubating !
>
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.12.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see http://systemml.apache.
> org/
>
> The tag to be voted on is v0.12.0-incubating-rc2 (
> d96a17f64cef7f251d9592679ecdee7ac17feb04)
>
> https://github.com/apache/incubator-systemml/commit/
> d96a17f64cef7f251d9592679ecdee7ac17feb04
>
> The release artifacts can be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> 12.0-incubating-rc2/
>
> The maven release artifacts, including signatures, digests, etc. can
> be found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1013/
>
> PPMC Vote Mail Threadhttps://www.mail-archive.com/dev@systemml.
> incubator.apache.org/msg01321.html
>
> PPMC Vote Results Mailhttps://www.mail-archive.com/dev@systemml.incubator.
> apache.org/msg01349.html
>
>
>
>  -- Arvind Surve Spark Technology Center
> http://www.spark.tc/




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Guacamole 0.9.11-incubating (RC1)

[Sergio Fernández]

+1 (binding)

On Thu, Jan 26, 2017 at 10:18 PM, Mike Jumper <mike.jum...@guac-dev.org>
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.11-incubating.
>
> We now kindly request that the Incubator PMC members review and vote on
> this incubator release.
>
> The VOTE RESULT is here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> guacamole-dev/201701.mbox/%3CCALKeL-PA3VO0kgetj15aVTp%
> 3D5uD2G3s88Hf6Hi_ozp507R9OFg%40mail.gmail.com%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://guacamole.incubator.apache.org/releases/0.9.11-incubating/
>
> The git tag for all relevant repositories is "0.9.11-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.11-incubating-RC1
>
> Build instructions are included in the manual, which is part of the updated
> documentation referenced above. For convenience:
>
> http://guacamole.incubator.apache.org/doc/0.9.11-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-ext can be found in the following staging
> repository (guacamole-common and guacamole-common-js are unchanged from the
> previous release):
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1005
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.11-incubating-RC1/
>
> Artifacts have been signed with the "mjum...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS
>
> Please review and vote:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Mike
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept OpenWhisk into the Apache Incubator

[Sergio Fernández]

+1 (binding)

On Nov 22, 2016 21:44, "Bertrand Delacretaz"  wrote:

> Le 17 nov. 2016 16:23, "Sam Ruby"  a écrit :
> >
> > Now that the discussion thread on the OpenWhisk Proposal has died
> > down, please take a moment to vote on accepting OpenWhisk into the
> > Apache Incubator
>
> +1, binding.
> - Bertrand
>

Re: [VOTE] Graduate Apache Geode (incubating)

[Sergio Fernández]

+1

good luck, guys!

On Sun, Nov 6, 2016 at 11:42 PM, John D. Ament <johndam...@apache.org>
wrote:

> +1
>
> On Nov 6, 2016 15:58, "Roman Shaposhnik" <ro...@shaposhnik.org> wrote:
>
> > Hi!
> >
> > after a very positive discussion in the Geode community
> > and at the IPMC level:
> > http://markmail.org/message/z4prj62hr7rn6cu6
> > I'd like to bring the following resolution for a formal vote.
> >
> > Please vote on the resolution pasted below to graduate
> > Apache Geode from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Geode from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> > Roman (on behalf of the Apache Geode PPMC).
> >
> > Resolution:
> >
> > Establish the Apache Geode 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 data management platform that provides
> > real-time, consistent access to data-intensive applications
> > throughout widely distributed cloud architectures.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Geode Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Geode Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a data management platform that provides real-time,
> > consistent access to data-intensive applications throughout
> > widely distributed cloud architectures.
> >
> > RESOLVED, that the office of "Vice President, Apache Geode" 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 Geode Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Geode 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 Geode Project:
> >
> > * Anilkumar Gingade <aging...@apache.org>
> > * Anthony Baker <aba...@apache.org>
> > * Ashvin Agrawal <ash...@apache.org>
> > * Avinash Dongre <adon...@apache.org>
> > * Barry Oglesby < bogle...@apache.org>
> > * Bruce Schuchardt <bschucha...@apache.org>
> > * Dan Smith <upthewatersp...@apache.org>
> > * Darrel Schneider <dschnei...@apache.org>
> > * Dave Barnes <dbar...@apache.org>
> > * Eric Shu <esh...@apache.org>
> > * Greg Chase <gregch...@apache.org>
> > * Hitesh Khamesra <hiteshkhame...@apache.org>
> > * Jason Huynh <jasonhu...@apache.org>
> > * Jens Deppe <jensde...@apache.org>
> > * Jianxia Chen <jche...@apache.org>
> > * Jinmei Liao <jinmeil...@apache.org>
> > * John Blum <jxb...@apache.org>
> > * Karen Miller <kmil...@apache.org>
> > * Konstantin Boudnik <c...@apache.org>
> > * Kirk Lund <kl...@apache.org>
> > * Mark Bretl <mbr...@apache.org>
> > * Nabarun Nag <n...@apache.org>
> > * Niall Pemberton <nia...@apache.org>
> > * Nitin Lamba <nla...@apache.org>
> > * Roman Shaposhnik <r...@apache.org>
> > * Sai Boorlagadda <sai_boorlaga...@apache.org>
> > * Swapnil Bawaskar <sbawas...@apache.org>
> > * Udo Kohlmeyer <u...@apache.org>
> > * William Markito <mark...@apache.org>
> > * Xiaojian Zhou <zho...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> > be appointed to the office of Vice President, Apache Geode, 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 Geode PMC be and hereby is
> > tasked with the creation of

Re: [DISCUSS] OpenWhisk Proposal

[Sergio Fernández]

Perfect, already added to the wiki.
Thanks, Felix.

On Fri, Nov 4, 2016 at 4:05 PM, Felix Meschberger <fmesc...@adobe.com>
wrote:

> Hi Sergio
>
> Pleased to meet you and thanks for offering to become a mentor. That helps.
>
> Feel free to add yourself to the proposal
>
> Thanks
> Felix
>
> Am 04.11.2016 um 15:57 schrieb Sergio Fernández <wik...@apache.org wik...@apache.org>>:
>
> Hi Felix,
>
> most of the ASF project have successfully manage to keep using GitHub for
> PRs, having the master git repository in ASF-controlled infrastructure. In
> the end it doesn't represent that big break on the common workflows. But
> definitely something the podling could try to address during incubation.
>
> I'd be happy to jump-in the proposal and help as mentor.
>
> Cheers,
>
>
> On Fri, Nov 4, 2016 at 3:48 PM, Felix Meschberger <fmesc...@adobe.com
> <mailto:fmesc...@adobe.com>>
> wrote:
>
> Hi John
>
> My understanding is, that we are well aware of this concern, which others
> have mentioned as well.
>
> Also Greg noted in the proposal:
>
> gstein sez: the podling can only graduate within an approved repository
> system. The IPMC may have a differing opinion, but from an Infra
> perspective: the OpenWhisk podling can continue with their usage of a
> GitHub repository, but faces a clear obstacle: GitHub "as master [as
> allowed by the Foundation]" must be approved and working before the
> graduation, or they must migrate their primary to the Foundation's Git
> repository (at git-wip) before they graduate.
>
> I think this sounds like a good compromise to work on and the poddling
> intends to work actively with Infra to see that we can stay in GitHub. If
> that is not possible, we byte the bullet accordingly.
>
> In addition, also according to Greg:
>
> We require that anybody committing to a GitHub repository authenticates
> with BOTH: GitHub, and the ASF. No commits without that multiple
> authentication. (this is based on our current experiments with Whimsy and
> Traffic Server; same rules would apply to this podling)
>
> The original discussion took place after the initial submission, see [1]
>
> Does that help ?
>
> Regards
> Felix
>
> [1] https://lists.apache.org/thread.html/1c22a29b69e944ee725278aae05bd4
> 1dea80d10d0d204c26eb4cb24c@%3Cgeneral.incubator.apache.org ttp://3Cgeneral.incubator.apache.org>%3E
>
> Am 04.11.2016 um 15:20 schrieb John D. Ament <johndam...@apache.org
> <mailto:johndam...@apache.org>>:
>
> I raised the concern over using github as the primary repo.  This is
> still
> unresolved, as I understood it.
>
> John
>
> On Fri, Nov 4, 2016 at 9:36 AM Felix Meschberger <fmesc...@adobe.com
> <mailto:fmesc...@adobe.com>>
> wrote:
>
> Hi all
>
> I have made some additions to the OpenWhisk Proposal [1]:
>
> - restructured the API Gateway references: It is expected
>  that the API Gateway will be refactored with additional
>  code donated by IBM during incubation.
> - added a note on the API Gateway’s dependency on OpenSSL
> - added a note on Trademarks IBM is currently pursuing and
>  intends to transfer to ASF
> - fixed some typos
>
> With these changes and no discussions over the course of the recent
> weeks,
> I would propose we could could vote for OpenWhisk to become an
> incubating
> project over the course of next weeks.
>
> Of course we are still open to welcome interested people to become
> initial
> committers to OpenWhisk Servlerless Runtime and API Gateway !
>
> WDYT ?
>
> Regards
> Felix
>
> [1] https://wiki.apache.org/incubator/OpenWhiskProposal
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org general-h...@incubator.apache.org>
>
>
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co<mailto:sergio.fernan...@redlink.co>
> w: http://redlink.co<http://redlink.co/>
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [DISCUSS] OpenWhisk Proposal

[Sergio Fernández]

Hi Felix,

most of the ASF project have successfully manage to keep using GitHub for
PRs, having the master git repository in ASF-controlled infrastructure. In
the end it doesn't represent that big break on the common workflows. But
definitely something the podling could try to address during incubation.

I'd be happy to jump-in the proposal and help as mentor.

Cheers,


On Fri, Nov 4, 2016 at 3:48 PM, Felix Meschberger <fmesc...@adobe.com>
wrote:

> Hi John
>
> My understanding is, that we are well aware of this concern, which others
> have mentioned as well.
>
> Also Greg noted in the proposal:
>
> > gstein sez: the podling can only graduate within an approved repository
> system. The IPMC may have a differing opinion, but from an Infra
> perspective: the OpenWhisk podling can continue with their usage of a
> GitHub repository, but faces a clear obstacle: GitHub "as master [as
> allowed by the Foundation]" must be approved and working before the
> graduation, or they must migrate their primary to the Foundation's Git
> repository (at git-wip) before they graduate.
>
> I think this sounds like a good compromise to work on and the poddling
> intends to work actively with Infra to see that we can stay in GitHub. If
> that is not possible, we byte the bullet accordingly.
>
> In addition, also according to Greg:
>
> > We require that anybody committing to a GitHub repository authenticates
> with BOTH: GitHub, and the ASF. No commits without that multiple
> authentication. (this is based on our current experiments with Whimsy and
> Traffic Server; same rules would apply to this podling)
>
> The original discussion took place after the initial submission, see [1]
>
> Does that help ?
>
> Regards
> Felix
>
> [1] https://lists.apache.org/thread.html/1c22a29b69e944ee725278aae05bd4
> 1dea80d10d0d204c26eb4cb24c@%3Cgeneral.incubator.apache.org%3E
>
> > Am 04.11.2016 um 15:20 schrieb John D. Ament <johndam...@apache.org>:
> >
> > I raised the concern over using github as the primary repo.  This is
> still
> > unresolved, as I understood it.
> >
> > John
> >
> > On Fri, Nov 4, 2016 at 9:36 AM Felix Meschberger <fmesc...@adobe.com>
> wrote:
> >
> >> Hi all
> >>
> >> I have made some additions to the OpenWhisk Proposal [1]:
> >>
> >> - restructured the API Gateway references: It is expected
> >>   that the API Gateway will be refactored with additional
> >>   code donated by IBM during incubation.
> >> - added a note on the API Gateway’s dependency on OpenSSL
> >> - added a note on Trademarks IBM is currently pursuing and
> >>   intends to transfer to ASF
> >> - fixed some typos
> >>
> >> With these changes and no discussions over the course of the recent
> weeks,
> >> I would propose we could could vote for OpenWhisk to become an
> incubating
> >> project over the course of next weeks.
> >>
> >> Of course we are still open to welcome interested people to become
> initial
> >> committers to OpenWhisk Servlerless Runtime and API Gateway !
> >>
> >> WDYT ?
> >>
> >> Regards
> >> Felix
> >>
> >> [1] https://wiki.apache.org/incubator/OpenWhiskProposal
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Apache Beam release 0.3.0-incubating

[Sergio Fernández]

(repeating my vote on dev@beam https://s.apache.org/AYPs )

+1 (binding)

So far I've successfully checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* clean build (Java 1.8.0_91, Scala, 2.11.7, SBT 0.13.9, Debian amd64)


Couple of minor issues I've seen it'd be great to have fixed in upcoming
releases:
* MongoDbIOTest fails (addr already in use) when a Mongo service is locally
running. I'd say the port should be random in the test suite. Reported
as BEAM-856.
* How did you generated the checksums? Because both SHA1/MD5 can't be
automatically checked because "no properly formatted SHA1/MD5 checksum
lines found". Reported as BEAM-841.

Cheers,



On Fri, Oct 28, 2016 at 10:49 AM, Aljoscha Krettek <aljos...@apache.org>
wrote:

> Hi everyone,
> Please review and vote on the release candidate #1 for the Apache Beam
> version 0.3.0-incubating, as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> [2],
> * all artifacts to be deployed to the Maven Central Repository [3],
> * source code tag "v0.3.0-incubating-RC1" [4],
> * website pull request listing the release and publishing the API reference
> manual [5].
>
> The Apache Beam community has unanimously approved this release [6].
>
> As customary, the vote will be open for at least 72 hours. It is adopted by
> a majority approval with at least three PMC affirmative votes. If approved,
> we will proceed with the release.
>
> Thanks!
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319527=12338051
> [2] https://dist.apache.org/repos/dist/dev/incubator/beam/0.3.0-
> incubating/
> [3]
> https://repository.apache.org/content/repositories/staging/
> org/apache/beam/
> [4]
> https://git-wip-us.apache.org/repos/asf?p=incubator-beam.git;a=tag;h=
> 5d86ff7f04862444c266142b0d5acecb5a6b7144
> [5] https://github.com/apache/incubator-beam-site/pull/52
> [6]
> https://lists.apache.org/thread.html/b3736acb5edcea247a5a6a64c09eca
> cab794461bf1ea628152faeb82@%3Cdev.beam.apache.org%3E
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Rya (Incubating) version 3.2.10 RC3

[Sergio Fernández]

+1 (binding)

So far I've successfully checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* clean build (Java 1.8.0_91, Maven 3.3.9, Debian amd64)



On Tue, Oct 25, 2016 at 10:00 PM, Aaron D. Mihalik <aaron.miha...@gmail.com>
wrote:

> The Apache Rya community has voted and approved the proposed release of
> Apache Rya 3.2.10 (Incubating) RC3.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
> supports SPARQL queries. Rya is a scalable RDF data management system built
> on top of Apache Accumulo®. Rya uses novel storage methods, indexing
> schemes, and query processing techniques that scale to billions of triples
> across multiple nodes. Rya provides fast and easy access to the data
> through SPARQL, a conventional query mechanism for RDF data. More
> information can be found at http://rya.incubator.apache.org/
>
> [VOTE] Thread:
> https://lists.apache.org/thread.html/01d692717b2ee088253fa96c427593
> 09a2a4d2aaf9867905bc473fa7@%3Cdev.rya.apache.org%3E
>
> [VOTE] [RESULT] Thread:
> https://lists.apache.org/thread.html/e58e7456987d74f11a0698fd5d4dde
> 436bd83016baa269c149f03511@%3Cdev.rya.apache.org%3E
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.10-rc3/
>
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1004/org/apache/rya/rya-project/3.2.10-incubating/
>
>
> The Git tag is rya-incubating-3.2.10-rc3
>
> The Git commit ID is 66d8b7f060bddeeb7c50cb0918f98ce3b265c564
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> 66d8b7f060bddeeb7c50cb0918f98ce3b265c564
>
>
> Checksums of rya-project-3.2.10-incubating-source-release.zip:
> SHA1: 4468f55b9f381e9103ca1e2e9c25b30e1cad4ed0
> MD5: a28d9a146857576903ff4fc3f7dae908
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mihalik.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12334209=Html=12319020
>
> The vote will be open for 72 hours and closes at Fri Oct 28 16:00 EDT 2016.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
>
> Then please vote:
> [ ] +1 Release this package as rya-project-3.2.10-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> --Aaron
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC6

[Sergio Fernández]

Sure Do Yung, keep it open until someone else has time to check the release
candidate.

Actually the right wording for the vote is that it "will be open for a
minimum of 72 hours" ;-)


On Tue, Oct 18, 2016 at 3:26 PM, DO YUNG YOON <sho...@gmail.com> wrote:

> Dear IPMC,
>
> Since there wasn't sufficient votes, I am asking if it is possible to
> extend vote period for another 72 hours or until we get sufficient
> votes(correct me if there is other proper way to extend vote).
>
> Would highly appreciate any feedback to this release candidate.
>
> Regards,
> DOYUNG YOON.
>
>
> On Mon, Oct 17, 2016 at 4:02 PM Sergio Fernández <wik...@apache.org>
> wrote:
>
> > Folks, more votes?
> > The first release is very important for every podling, and we still need
> > one additional binding vote.
> > Thanks.
> >
> > On Sat, Oct 15, 2016 at 3:30 AM, Justin Mclean <jus...@classsoftware.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > +1 binding
> > >
> > > I checked:
> > > - name contains incubating
> > > - signatures and hashes good
> > > - LICENSE and NOTICE correct
> > > - DISCLAIMER exists
> > > - all source code has Apache headers
> > > - no binary files in release
> > > - can compile from source
> > >
> > > Good to see simple build instructions in the README. A nice simple
> > release
> > > to check thanks for that.
> > >
> > > I did notice this in DEVELOPMENT.md, "The toll will write a report in
> > case
> > > it finds any issue.” and first misread that as “troll” :-) I assume you
> > > mean tool?
> > >
> > > Also just a minor branding issue you may also want to add some
> trademark
> > > attributions [1] to your incubator page [2]. I also notice a prominent
> > > button to github mirror without and equally prominent button/link to
> the
> > > actual Apache git repo, you may want to consider changing that.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://www.apache.org/foundation/marks/faq/#attribution
> > > 2. http://s2graph.incubator.apache.org
> > > -----
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925 <+43%20660%202747925>
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC6

[Sergio Fernández]

Folks, more votes?
The first release is very important for every podling, and we still need
one additional binding vote.
Thanks.

On Sat, Oct 15, 2016 at 3:30 AM, Justin Mclean <jus...@classsoftware.com>
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - name contains incubating
> - signatures and hashes good
> - LICENSE and NOTICE correct
> - DISCLAIMER exists
> - all source code has Apache headers
> - no binary files in release
> - can compile from source
>
> Good to see simple build instructions in the README. A nice simple release
> to check thanks for that.
>
> I did notice this in DEVELOPMENT.md, "The toll will write a report in case
> it finds any issue.” and first misread that as “troll” :-) I assume you
> mean tool?
>
> Also just a minor branding issue you may also want to add some trademark
> attributions [1] to your incubator page [2]. I also notice a prominent
> button to github mirror without and equally prominent button/link to the
> actual Apache git repo, you may want to consider changing that.
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/foundation/marks/faq/#attribution
> 2. http://s2graph.incubator.apache.org
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept NetBeans into the Apache Incubator

[Sergio Fernández]

milian Bold* (various plugins from Joseki Bold SRL)
>  11. Hermien Pellissier (documentation, testing)
>  12. Ivar Grimstad (JPA Modeler and MVC tooling)
>  13. Josh Juneau (documentation, testing, MVC tooling)
>  14. Kirk Pepperdine (jClarity)
>  15. Johan Vos (Gluon plugin from Gluon)
>  16. Jose Pereda (Gluon plugin from Gluon)
>  17. John Kostaras (documentation, testing)
>  18. Liang Ding (Chinese translator)
>  19. Mark Stephens (JavaFX PDF viewer plugin from IDR Solutions)
>  20. Martijn Verburg (jClarity)
>  21. Michael Nascimento Santos (Improving CEO, working on refactoring
> tools)
>  22. Michael Mueller
>  23. Michel Graciano (tests, documentation)
>  24. Tushar Joshi (various plugins, documentation, testing)
>  25. *Wade Chandler* (Independent, working on Groovy support)
>  26. Zoran Sevarac (plugins for teaching/education)
>
>  * Individual contributors from NetBeans plugin developers.
>   1. Georgia Ingham (JavaFX PDF viewer plugin from IDR Solutions)
>   2. *Emmanuel Hugonnet* (WildFly plugin from Red Hat)
>   3. Shai Almog (Codename One plugin from Codename One)
>   4. Steve Hannah (Codename One plugin from Codename One)
>   5. Attila Kelemen (independent Gradle plugin)
>   6. Denis Anisimov (Vaadin plugin from Vaadin)
>   7. Gaurav Gupta (independent JPA Modeler plugin)
>   8. Junichi Yamamoto (PHP-related plugins)
>   9. Bruno Flavio (Groovy/Grails-related code)
>  10. Leonardo Loch Zanivan (JSHint)
>  11. Mattias Blaesing (various plugins)
>
>  * Miscellaneous
>   1. Anuradha Gunasekara (Maven tools)
>   2. Steve Millidge (Payara Services)
>   3. Andrew Pielage (Payara Services)
>   4. Gui Chulin (translation)
>   5. Yi Zhao (translation)
>   6. Liyuan Li (translation)
>   7. CunHui Lin (translation)
>   8. Lei Cao (translation)
>
> == Sponsors ==
>
> === Champion ===
>
>  * Bertrand Delacretaz
>
> === Mentors ===
>
>  * Bertrand Delacretaz
>  * Emmanuel Lécharny
>  * Ate Douma
>  * Mark Struberg
>  * Jim Jagielski
>  * Daniel Gruno
>
> === Sponsoring Entity ===
>  * The Apache Incubator
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Request to join Apache Streams (Incubating) as Mentor

[Sergio Fernández]

OK. Just try to properly report all this in your next cycle (including
links to each important discussion/vote mail) to have it properly tracked.

All the best for the podling.

On Mon, Sep 26, 2016 at 2:37 PM, Ate Douma <a...@douma.nu> wrote:

> On 2016-09-26 09:42, Sergio Fernández wrote:
>
>> How this vote relates with the other thread about retiring Apache Streams
>> to the attic?
>>
>> https://lists.apache.org/thread.html/077e46f67271c2e2e2d406b
>> 8b1f8cf9ae633a71bccffefdfd206d0b4@%3Cgeneral.incubator.apache.org%3E
>>
>> I'm a bit confused... maybe I missed some mails.
>>
> I guess so :-)
>
> There has been new feedback and input which potentially might bring this
> podling back on its feet.
> And the offer from Suneel to become mentor for Apache Streams is part of
> that.
>
> For these reasons I've cancelled the vote for retirement, for now.
>
> Concerning the process for assigning Suneel as mentor, can we assume lazy
> consensus and just 'make it so' in a few days, if nobody objects?
>
> Thanks, Ate
>
>
>
>>
>> On Sun, Sep 25, 2016 at 12:25 PM, Ate Douma <a...@douma.nu> wrote:
>>
>> I'm happy to add and have Suneel join me as mentor for Apache Streams.
>>>
>>> I can't find anything about this: Is there any formal process or voting
>>> needed
>>> before I make this so?
>>>
>>> Ate
>>>
>>> On 2016-09-23 19:51, Suneel Marthi wrote:
>>>
>>> 
>>>>
>>>>
>>>>
>>> -
>>> 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
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Request to join Apache Streams (Incubating) as Mentor

[Sergio Fernández]

How this vote relates with the other thread about retiring Apache Streams
to the attic?

https://lists.apache.org/thread.html/077e46f67271c2e2e2d406b8b1f8cf9ae633a71bccffefdfd206d0b4@%3Cgeneral.incubator.apache.org%3E

I'm a bit confused... maybe I missed some mails.


On Sun, Sep 25, 2016 at 12:25 PM, Ate Douma <a...@douma.nu> wrote:

> I'm happy to add and have Suneel join me as mentor for Apache Streams.
>
> I can't find anything about this: Is there any formal process or voting
> needed
> before I make this so?
>
> Ate
>
> On 2016-09-23 19:51, Suneel Marthi wrote:
>
>> 
>>
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Is the incubator full?

[Sergio Fernández]

Hi,

On Wed, Aug 24, 2016 at 11:41 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Tue, Aug 23, 2016 at 7:26 AM, John D. Ament <johndam...@apache.org>
> wrote:
> > I'm wondering if the Apache Incubator is full right now?
>

Very interesting question I wouldn't say full, because volunteering is
hard to allocate in slots. But John is right, we're operating in the limits
of our capacity.

It seems that this question gets asked about once a year. The consensus
> always seems to be that this may not be the right question to ask. It is
> sort of like asking whether Hadoop has too many lines of Java. On a more
> serious note, I think that the takeaway from each of these threads over
> the years has been that the right question to ask is whether we're
> providing
> podlings with support they need to emerge as TLPs ASAP. I think that should
> be the focus of IPMC. A maniacal focus on getting the projects out either
> as
> TLPs or to the Attic should, indeed, be a constant priority for us. I know
> I'm
> in the minority when I say this, but I think this should be one of the few
> areas
> where IPMC and/or IPMC Chair gets to drive the inquiry as opposed to
> mentors
> doing it. Wave sitting in the Incubator since 2010 is clearly NOT in
> anybody's
> best interest.
>

Can we say if a podling stays incubating for a time (5 years?) is in a
heavy risk of leaving the incubator? I know each podling has different
timing; but I'l pretty sure we could find some common-sense milestones.

> So I wonder, is the incubator full? Has capacity plateaued and we should
> > discourage projects from joining?  Are there projects that we should
> > strongly encourage to graduate?
>
> I think you may be seeing signs of self-throttling. Basically if the
> new proposal
> comes in and there's nobody interested in mentoring it -- well the project
> won't
> go in.


Well, that just 1% of the work. Every body could easily volunteer for
mentoring; most os the work at that phase is done by the champion. But what
really requires time is actually mentoring the podling. My feeling is (I
have no figures) that is most of our current podling we have just 1-2
active mentors. That would be another way to look to that detail.


> In terms of reviewing releases -- Justin truly deserves a
> medal, but aside from his awesome efforts.


Absolutely! I have to pay him a Rebujito in Sevilla in Autumn ;-)

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Apache Annotator

[Sergio Fernández]

+1 (binding)

On Thu, Aug 11, 2016 at 9:49 PM, Brian McCallister <bri...@skife.org> wrote:

> +1 from me!
>
> On Thu, Aug 11, 2016 at 11:23 AM Daniel Gruno <humbed...@apache.org>
> wrote:
>
> > Obviously a binding +1 from me :)
> >
> > With regards,
> > Daniel.
> >
> > On 08/08/2016 09:41 PM, Benjamin Young wrote:
> > > Hi all!
> > >
> > > Thanks for everyone who's contributed to the discussion around the
> > Apache Annotator proposal:
> > > https://wiki.apache.org/incubator/AnnotatorProposal
> > >
> > > From what our Champion tells me, we're now ready to go to a vote!
> > >
> > > We have a long and eager list of contributors, a key focus around
> > existing code and completed W3C standards for annotation, and a growing
> > world of annotation-centric tools on and off the Web (including NLP and
> > machine learning).
> > >
> > > I'd also like to say a quick "thanks" to our Champion to our Mentors
> for
> > their input and help along the way.
> > >
> > > Cheers!
> > > Benjamin
> > > --
> > > http://bigbluehat.com/
> > > http://linkedin.com/in/benjaminyoung
> > >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Beam, version 0.2.0-incubating

[Sergio Fernández]

On Tue, Aug 2, 2016 at 7:37 PM, Dan Halperin <dhalp...@google.com.invalid>
wrote:
>
> Apparently I thoroughly fat-fingered my initial mail and sent to
> APACHE.INCUBATOR.org instead of the correct domain.
>

wow, I didn't realize about the mistake either...

Sergio, would you mind re-sending your response to the correct list?
>

Sure, here it goes:

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers, build sources in a clean environment
(Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Airflow podling name search

[Sergio Fernández]

Don't worry Chris, unless you have something really urgent blocked by the
name search, Shane Curcuru (VP for Brand Management) would eventually
handle your request.

On Tue, Jul 26, 2016 at 5:03 AM, Chris Riccomini <criccom...@apache.org>
wrote:

> Hey all,
>
> Could someone please have a look at:
>
>   https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-110
>
> Has been open for 2 weeks with no activity.
>
> Thanks!
> Chris
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Pony Mail (Incubating) 0.9.RC2 as 0.9

[Sergio Fernández]

On Wed, Jul 20, 2016 at 9:03 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
>
> > Looks like they're using the hosted version in the site:
> > https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js
>
> If it not bundled then there's no need to mention it in LICENSE.
>

Exactly. Just wanted to clarify where the runtime dependency came from.

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Pony Mail (Incubating) 0.9.RC2 as 0.9

[Sergio Fernández]

Justin,

On Wed, Jul 20, 2016 at 7:25 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
>
> Looks like the the source bundles may be missing jQuery? It’s mentioned in
> license and needed by bootstrap but I don't see it bundled.
>

Looks like they're using the hosted version in the site:
https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Pony Mail (Incubating) 0.9.RC2 as 0.9

[Sergio Fernández]

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers, absence of unexpected binaries.

Since the sources are a complex and there is no build need, I'd recommend
to added a test suite to verify the sources (lua or python) can actually be
interpreted.

Another thing I'd recommend to improve is the tarball: currently it expands
to just "ponymail" as directory, while I could expect "apache-ponymail" or
"apache-pony-mail", or even better "apache-pony-mail-0.9.RC2-incubating".

Congratulations guys for your first incubating release!


On Sun, Jul 17, 2016 at 11:08 AM, Daniel Gruno <humbed...@apache.org> wrote:

> Hello IPMC and lurkers,
> This is a vote to release Apache Pony Mail (Incubating) 0.9.RC2 as 0.9.
>
> Podling vote thread is at:
>
> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c03d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>
> The release artefact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/ponymail/
> Specifically, this is a vote on
>
> https://dist.apache.org/repos/dist/dev/incubator/ponymail/apache-pony-mail-0.9.RC2-incubating.tar.gz
>
> The git hash for the current 0.9.RC2 head is:
> 116797982cec1e483349ed48a397e0b0cdad5b1d
>
> Signing keys etc can be found in the same dir as the RC (
> https://dist.apache.org/repos/dist/dev/incubator/ponymail/KEYS )
>
> Change-log for 0.9 can be found at:
>
> https://git1-us-west.apache.org/repos/asf?p=incubator-ponymail.git;a=blob;f=CHANGELOG.md
>
> With regards,
> Daniel.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating

[Sergio Fernández]

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers, build sources in a clean environment
(Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).


On Thu, Jul 14, 2016 at 4:11 PM, Michael Wu <mchl@gmail.com> wrote:

> Hi all,
>
> This is the incubator release of Apache Eagle, version 0.4.0-incubating.
> Highlighted changes in this release are as the following:
>   * JBDC Metadata Storage Extension
>   * Topology management in remote mode including start/stop/status
> operations
>   * Auditlogparser for MapR's audit log
>   * Oozie auditlog integration for Oozie security monitoring
>   * Add applicaiton "maprFSAuditLog"
>   * Refactor bin/eagle-sandbox-starter.sh to make it easier to use
>
> Thanks to everyone who has contributed to this release.
>
> Here's the release note:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/$BRANCH_NAME
> >
>
> The artifacts to be voted on are located at:
>
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/
> <
> https://dist.apache.org/repos/dist/dev/incubator/eagle/$ARTIFACT_DIRECTORY/
> >
>
> The commit to be voted upon:
>
> https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715
> <https://github.com/apache/incubator-eagle/commit/$COMMIT_SHA>
>
> Release tag is:
>
> https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3
> <https://github.com/apache/incubator-eagle/releases/tag/$TAG_NAME>
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/mw.asc
> <http://people.apache.org/keys/committer/$NAME.asc>
>
> The hashes of the artifacts are as follows:
> apache-eagle-0.4.0-incubating-src-rc3.tar.gz.md5:
> 5781048a2fc2b3dcfe5e30a09be86d25
> apache-eagle-0.4.0-incubating-src-rc3.tar.gz.sha1:
> a98b565604b3921a4ea5c53e30479427b227e1e2
>
> A vote on releasing this package has already passed in Apache Eagle PPMC[1]
> including +1 votes from our PPPMC (Julian Hyde, Hao Chen, Edward Zhang,
> Qinwen Zhao).
>
> Please vote on releasing this package as: Apache Eagle 0.4.0-incubating.
>
> The vote is open for the next 72 hours.
>
> [ ] +1 Approve
> [ ]  0 No opinion
> [ ] -1 Disapprove (and reason ...)
>
>
> Thanks,
> Michael
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE]: Graduate Apache Kudu from the incubator

[Sergio Fernández]

+1 (binding)
good luck, guys!

On Fri, Jul 8, 2016 at 3:58 AM, John D. Ament <johndam...@apache.org> wrote:

> +1
>
> On Tue, Jul 5, 2016 at 3:04 PM Jake Farrell <jfarr...@apache.org> wrote:
>
> > This thread is to start a vote on the graduation resolution Apache Kudu
> has
> > approved on the dev list with 12 positive votes (11 PPMC, 1 community (6
> > from IPMC members))
> >
> > Status page: http://incubator.apache.org/projects/kudu.html
> > Graduation discussion: https://s.apache.org/T8Uj
> > Graduation vote: https://s.apache.org/5hpx
> >
> > Apache Kudu has been apart of the Incubator since December 2015 and in
> that
> > time has
> >
> > * Had 5 successful IPMC approved releases
> > * Expanded the PPMC with new members
> > * A successful community vote to graduate with 12 positive votes
> >
> > I would like to get the voting started with my own +1
> >
> > The following 6 IPMC members voted during the community vote on the
> > dev@kudu
> > list and asked that their vote be carried forward:
> >
> > - Binglin Chang
> > - Chris Mattmann
> > - Jake Farrell
> > - Michael Stack
> > - Todd Lipcon
> > - Jacques Nadeau
> >
> > Please vote
> >
> > [ ] +1 Graduate Apache Kudu as a TLP
> > [ ] +0
> > [ ] -1 Don't graduate Apache Kudu as a TLP because…
> >
> > Voting will end in 72 hours, i.e. 15:00 UTC on 2016-07-08
> > http://www.timeanddate.com/countdown/to?iso=20160708T15
> >
> > -Jake
> >
> >
> >
> > Resolution:
> >
> > Establish the Apache Kudu 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 distributed columnar storage engine
> > built for the Apache Hadoop ecosystem.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Kudu Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Kudu Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a distributed columnar storage engine built
> > for the Apache Hadoop ecosystem.
> >
> > RESOLVED, that the office of "Vice President, Apache Kudu" 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 Kudu Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Kudu 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 Kudu Project:
> >
> >   * Adar Dembo <a...@apache.org>
> >   * Binglin Chang <bch...@apache.org>
> >   * Chris Mattman <mattm...@apache.org>
> >   * Dan Burkert <danburk...@apache.org>
> >   * David Alves <dral...@apache.org>
> >   * Jake Farrell <jfarr...@apache.org>
> >   * Jarek Jarcec Cecho <jar...@apache.org>
> >   * Jean-Daniel Cryans <jdcry...@apache.org>
> >   * Julien Le Dem <jul...@apache.org>
> >   * Michael Stack <st...@apache.org>
> >   * Mike Percy <mpe...@apache.org>
> >   * Misty Stanley-Jones <mi...@apache.org>
> >   * Todd Lipcon <t...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Todd Lipcon
> > be appointed to the office of Vice President, Apache Kudu, 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 Kudu 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 Kudu Project; and be it further
> >
> > RESOLVED, that the Apache Kudu Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Kudu podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator Kudu podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [DISCUSS] Incubator Logo & Branding

[Sergio Fernández]

+1

The big thing here is to make easier for new podlings to follow the
guidelines. What about creating a checklist and/or adding this branding
details to the tasks in status template?

The logo is a bit more trickier, but the disclaimer should be something
easy to monitor...


On Sat, Jul 2, 2016 at 5:16 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> +1
>
> Regards
> JB
>
>
> On 07/02/2016 04:06 AM, John D. Ament wrote:
>
>> All,
>>
>> As a follow up to the current discussions happening, I wanted to get
>> opinions from the IPMC on whether or not the Incubator logo should be
>> included in podling websites.
>>
>> Take https://wiki.apache.org/incubator/BrandingAuditJune2016 as a summary
>> of podling status.
>>
>> 29 podlings presently show the Incubator Logo.  1 podling uses a custom
>> version of the logo.  This means we're just above 50% matching.  The
>> branding guide indicates that this is a should, which essentially means
>> that unless there's some strong reason to not include, it is to be
>> included
>> on the website.
>>
>> I believe the usage of the Incubator logo comes from including parent
>> project logos on sub-project websites, where podlings are essentially
>> sub-projects, but I can't find anything confirming this.
>>
>> If we are to require the logo to be present, we must spell out the URL to
>> the logo to use.  This may be a variety of logos, include transparency
>> effects, with and without borders, but we should guide projects on where
>> to
>> find them.
>>
>> John
>>
>>
> --
> 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
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Apache Kudu (incubating) 0.9.1 RC1

[Sergio Fernández]

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers, build from sources (CMake 3.5.1, GCC
5.3.1, Debian amd64).

The  thirdparty/patches folder looks  a bit weird for me: what license do
they have? is the release already patched? So some clarification would be
welcomed.

Around the release, for not strictly affected, I'd like to point three more
thing about the podling itself:

* Although redirections are correctly handled, I'd remove all getkudu.io
links in the documentation to use the new canonical domain kudu.apache.org

* I noticed you incubating releases are not clearly marked (version suffix)
at http://kudu.apache.org/releases/ until you actually retrieve the file.
I'd say it's something to remark, to know what releases happened before
incubation, what during and what afterwards.

* The podling status page http://incubator.apache.org/projects/kudu.html
requires some work (I went there just to check the releases issue mentioned
before).

Cheers,


On Tue, Jun 28, 2016 at 6:12 PM, John D. Ament <johndam...@apache.org>
wrote:

> +1
>
> On Mon, Jun 27, 2016 at 11:10 AM Todd Lipcon <t...@apache.org> wrote:
>
> > Hi,
> >
> > The PPMC vote to release Apache Kudu (incubating) 0.9.1 RC1 passed and
> > I'm now submitting this to the IPMC.
> >
> > Vote thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201606.mbox/%3CCADY20s6%3D%2BnKNgvx%3DG_pKupQGiH%2B9ToS53LqExBwWM6vLp-ns9A%40mail.gmail.com%3E
> >
> > Result:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201606.mbox/%3CCADY20s6gXTnV_vGqX1GrwecegdcFuEs9ovA2KPykkT524PaA3w%40mail.gmail.com%3E
> >
> > On the podling vote, one +1 (mine) is from an IPMC member, so carries
> over
> > into this vote.
> >
> > This is a source-only release. The artifacts were staged here:
> > https://dist.apache.org/repos/dist/dev/incubator/kudu/0.9.1-RC1/
> >
> > It was built from this tag:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=095b481e308ad954cfe36ff7f91751f43eaf6aa1
> >
> > The release notes can be found here (some links will only work when this
> > version is released):
> >
> >
> https://github.com/apache/incubator-kudu/blob/master/docs/release_notes.adoc#rn_0.9.1
> >
> > KEYS file:
> > http://www.apache.org/dist/incubator/kudu/KEYS
> >
> > Please try the release and vote; vote will be open for at least 72 hours.
> >
> > Thanks,
> > -Todd
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Worked LICENSE and NOTICE example

[Sergio Fernández]

Hi,

On Thu, Jun 23, 2016 at 8:49 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
>
> You can’t have a dependancy (other than optional) on or include non
> permissive licenses like LGPL. Even if it’s an optional dependancy nothing
> would go in NOTICE as it’s not bundled.
>

Right, non-bundled licenses does not need to be noticed.

I could make an example with Category B licenses (weak copy left) as I’ve
> not covered that yet.
>

Indeed, a example with Category B may be useful.

Thanks!


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Worked LICENSE and NOTICE example

[Sergio Fernández]

Great idea, Justin!

What about including an example in the NOTICE about the inclusion of a
non-permissive 3rd party license (e.g., LGPL)?

I can make a PR in case you find it relevant.

On Thu, Jun 23, 2016 at 2:16 AM, Justin Mclean <jus...@classsoftware.com>
wrote:

> Hi,
>
> At the last ApacheCon I was discussing with Marvin about some of the
> issues around assembling license and notice files. One of the ideas we come
> up with was to have some worked examples.
>
> So here is a small example I put together of a fictional Apache project
> using Bootstrap. Code is on github [1] and the checkins show each step
> needed to bring LICENSE and NOTICE into complicance. I’ve also made a short
> (4 minutes) screen cast of the process here [2].
>
> Feedback, spelling errors, legal corrections/queries etc etc all welcome.
> Do people think this is useful and would they like to see more examples?
>
> Thanks,
> Justin
>
> 1. https://github.com/justinmclean/ApacheWombat
> 2. https://vimeo.com/171210141
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

[Sergio Fernández]

On Mon, Jun 20, 2016 at 1:49 PM, Justin Mclean 
wrote:
>
> > license text should go in the LICENSE files, while NOTICE should just
> > contain a brief enumeration with some details (file/s, copyright holder,
> > license name and original source) about the third-party source components
> > included.
>
> Agree but just to make clear NOTICE should usually not include copyright
> info about permissive 3rd party licenses. NOTICE should include copyright
> notices that have been removed [1] and required notices [2] but nothing
> more. [3]
>

Correct.

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

[Sergio Fernández]

0159a5a4e8
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-commandline.git;a=commit;h=2db7d9f823e895d33ef2107ebfe5d70ed20e1fc7
>
>
> Release candidates are signed with a GPG key available at:
>   https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachetaverna-1015/
>
>
> The changelog for this release is available from JIRA:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332249
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332250
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332251
>
>
>
> Please vote on releasing these packages as:
>
>   Apache Taverna Engine 3.1.0-incubating
>   Apache Taverna Common Activities 2.1.0-incubating
>   Apache Taverna Command-line Tool 3.1.0-incubating
>
>
> The vote is open for at least 72 hours and passes if a majority of at
> least three +1 Apache Incubator IPMC votes are cast.
>
>
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
>
> Anyone can participate in testing and voting, not just IPMC members,
> please feel free to try out the release candidate and provide your
> votes!
>
> How to review a release candidate? https://s.apache.org/review-release
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept SensSoft into the Apache Incubator WAS Re: [VOTE] Accept

[Sergio Fernández]

t; > > across a few full-time staff that have been with the project for at
> > least 2
> > > years. Core personnel can be found on our website:
> > > http://www.draper.com/softwareasasensor
> > >
> > > == Alignment ==
> > > The Software as a Sensor™ Project is currently Copyright (c) 2015, 2016
> > The
> > > Charles Stark Draper Laboratory, Inc. All rights reserved and licensed
> > > under Apache v2.0.
> > >
> > > == Known Risks ==
> > >
> > > === Orphaned products ===
> > > There are currently no orphaned products. Each component of The
> Software
> > as
> > > a Sensor™ Project has roughly 1-2 dedicated staff, and there is
> > substantial
> > > collaboration between projects.
> > >
> > > === Inexperience with Open Source ===
> > > Draper has a number of open source software projects available through
> > > www.github.com/draperlaboratory.
> > >
> > > == Relationships with Other Apache Products ==
> > > Software as a Sensor™ Project does not currently have any dependences
> on
> > > Apache Products. We are also interested in coordinating with other
> > projects
> > > including Usergrid, and others involving data processing at large
> scales,
> > > time-series analysis and ETL processes.
> > >
> > > == Developers ==
> > > The Software as a Sensor™ Project is primarily funded through contract
> > > work. There are currently no “dedicated” developers, however, the same
> > core
> > > team does work will continue work on the project across different
> > contracts
> > > that support different features. We do intend to maintain a core set of
> > key
> > > personnel engaged in community development and maintenance—in the
> future
> > > this may mean dedicated developers funded internally to support the
> > > project, however, the project is tied to business development strategy
> to
> > > maintain funding into various facets of the project.
> > >
> > > == Documentation ==
> > > Documentation is available through Github; each repository under the
> > > Software as a Sensor™ Project has documentation available through
> wiki’s
> > > attached to the repositories.
> > >
> > > == Initial Source ==
> > > Current source resides at Github:
> > >  * https://github.com/draperlaboratory/user-ale (User ALE)
> > >  * https://github.com/draperlaboratory/distill (Distill)
> > >  * https://github.com/draperlaboratory/stout (STOUT and Extensions)
> > >  * https://github.com/draperlaboratory/
> > >
> > > == External Dependencies ==
> > > Each component of the Software as a Sensor™ Project has its own
> > > dependencies. Documentation will be available for integrating them.
> > >
> > > === User ALE ===
> > >  * Elasticsearch: https://www.elastic.co/
> > >  * Logstash: https://www.elastic.co/products/logstash
> > >  * Kibana (optional): https://www.elastic.co/products/kibana
> > > === STOUT ===
> > >  * Django: https://www.djangoproject.com/
> > >* django-axes
> > >* django-custom-user
> > >* django-extensions
> > >  * Elasticsearch: https://www.elastic.co/
> > >  * Gunicorn: http://gunicorn.org/
> > >  * MySQL-python: https://pypi.python.org/pypi/MySQL-python
> > >  * Numpy: http://www.numpy.org/
> > >  * Pandas: http://pandas.pydata.org/
> > >  * psycopg2: http://initd.org/psycopg/
> > >  * pycrypto: https://www.dlitz.net/software/pycrypto/
> > >  * pymongo: https://api.mongodb.org/python/current/
> > >  * python-dateutil: https://labix.org/python-dateutil
> > >  * pytz: https://pypi.python.org/pypi/pytz/
> > >  * requests: http://docs.python-requests.org/en/master/
> > >  * six: https://pypi.python.org/pypi/six
> > >  * urllib3: https://pypi.python.org/pypi/urllib3
> > >  * mongoDB: https://www.mongodb.org/
> > >  * R (optional): https://www.r-project.org/
> > > === Distill ===
> > >  * Flask: http://flask.pocoo.org/
> > >  * Elasticsearch-dsl: https://github.com/elastic/elasticsearch-dsl-py
> > >  * graph-tool: https://git.skewed.de/count0/graph-tool
> > >  * OpenMp: http://openmp.org/wp/
> > >  * pandas: http://pandas.pydata.org/
> > >  * numpy: http://www.numpy.org/
> > >  * scipy: http://www.numpy.org/
> > > === Portal ===
> > >  * Django: https://www.djangoproject.com/
> > >  * React: https://facebook.github.io/react/
> > >  * D3.js: https://d3js.org/
> > >
> > > === GNU GPL 2 ===
> > >
> > >
> > > === LGPL 2.1 ===
> > >
> > >
> > > === Apache 2.0 ===
> > >
> > >
> > > === GNU GPL ===
> > >
> > >
> > > == Required Resources ==
> > >  * Mailing Lists
> > >* priv...@senssoft.incubator.apache.org
> > >* d...@senssoft.incubator.apache.org
> > >* comm...@senssoft.incubator.apache.org
> > >
> > >  * Git Repos
> > >* https://git-wip-us.apache.org/repos/asf/User-ALE.git
> > >* https://git-wip-us.apache.org/repos/asf/STOUT.git
> > >* https://git-wip-us.apache.org/repos/asf/DISTILL.git
> > >* https://git-wip-us.apache.org/repos/asf/TAP.git
> > >
> > >  * Issue Tracking
> > >* JIRA SensSoft (SENSSOFT)
> > >
> > >  * Continuous Integration
> > >* Jenkins builds on https://builds.apache.org/
> > >
> > >  * Web
> > >* http://SoftwareasaSensor.incubator.apache.org/
> > >* wiki at http://cwiki.apache.org
> > >
> > > == Initial Committers ==
> > > The following is a list of the planned initial Apache committers (the
> > > active subset of the committers for the current repository on Github).
> > >
> > >  * Joshua Poore (jpo...@draper.com)
> > >  * Laura Mariano (lmari...@draper.com)
> > >  * Clayton Gimenez (cgime...@draper.com)
> > >  * Alex Ford (af...@draper.com)
> > >  * Steve York (sy...@draper.com)
> > >  * Fei Sun (f...@draper.com)
> > >  * Michelle Beard (mbe...@draper.com)
> > >  * Robert Foley (rfo...@draper.com)
> > >  * Kyle Finley (kfin...@draper.com)
> > >  * Lewis John McGibbney (lewi...@apache.org)
> > >
> > > == Affiliations ==
> > >  * Draper
> > >* Joshua Poore (jpo...@draper.com)
> > >* Laura Mariano (lmari...@draper.com)
> > >* Clayton Gimenez (cgime...@draper.com)
> > >* Alex Ford (af...@draper.com)
> > >* Steve York (sy...@draper.com)
> > >* Fei Sun (f...@draper.com)
> > >* Michelle Beard (mbe...@draper.com)
> > >* Robert Foley (rfo...@draper.com)
> > >* Kyle Finley (kfin...@draper.com)
> > >
> > >  * NASA JPL
> > >* Lewis John McGibbney (lewi...@apache.org)
> > >
> > > == Sponsors ==
> > >
> > > === Champion ===
> > >  * Lewis McGibbney (NASA/JPL)
> > >
> > > === Nominated Mentors ===
> > >  * Paul Ramirez (NASA/JPL)
> > >  * Lewis John McGibbney (NASA/JPL)
> > >  * Chris Mattmann (NASA/JPL)
> > >
> > > == Sponsoring Entity ==
> > > The Apache Incubator
> > >
> > > == References ==
> > >
> > > Mariano, L. J., Poore, J. C., Krum, D. M., Schwartz, J. L., Coskren, W.
> > D.,
> > > & Jones, E. M. (2015). Modeling Strategic Use of Human Computer
> > Interfaces
> > > with Novel Hidden Markov Models. [Methods]. Frontiers in Psychology, 6.
> > > doi: 10.3389/fpsyg.2015.00919
> > > Poore, J., Webb, A., Cunha, M., Mariano, L., Chapell, D., Coskren, M.,
> &
> > > Schwartz, J. (2016). Operationalizing Engagement with Multimedia as
> User
> > > Coherence with Context. IEEE Transactions on Affective Computing,
> PP(99),
> > > 1-1. doi: 10.1109/taffc.2015.2512867
> > >
> > >
> > >
> > > --
> > > Lewis
> > >
> >
> >
> >
> > --
> > *Lewis*
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Beam, version 0.1.0-incubating

[Sergio Fernández]

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers (two test files from the Project
Gutenberg don't have it) build sources in a clean environment (Maven 3.3.9,
OpenJDK 1.8.0_91 64-Bit, Debian amd64).

The issue with the "Project Gutenberg license" needs to be clarified, as
Justin already pointed it out. Although license looks to affect only test
resources, this may need legal@apache check.

Good work, guys! Happy to sea Bean moving forward.



On Sun, Jun 12, 2016 at 1:54 AM, Davor Bonaci <da...@google.com.invalid>
wrote:

> Hi everyone,
> Here's the first vote for the first release of Apache Beam -- version
> 0.1.0-incubating!
>
> The complete staging area is available for your review, which includes:
> * the official Apache source release to be deployed to dist.apache.org
> [1],
> and
> * all artifacts to be deployed to the Maven Central Repository [2].
>
> This corresponds to the tag "v0.1.0-incubating-RC3" in source control, [3].
>
> The Apache Beam community has unanimously approved this release, [4], [5],
> [6].
>
> Please vote as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> As customary, the vote will be open for at least 72 hours. It is adopted by
> a majority approval with at least three PMC affirmative votes. If approved,
> we will proceed with the release.
>
> Thanks,
> Davor
>
> [1]
> https://dist.apache.org/repos/dist/dev/incubator/beam/0.1.0-incubating/RC3/
> [2] https://repository.apache.org/content/repositories/orgapachebeam-1002/
> [3] https://github.com/apache/incubator-beam/tree/v0.1.0-incubating-RC3
> [4]
>
> https://lists.apache.org/thread.html/68bf80b386dde080126b51ddf3497c6801015903a705411d435d64a1@%3Cdev.beam.apache.org%3E
> [5]
>
> https://lists.apache.org/thread.html/32c991987e0abf2a09cd8afad472cf02e482af02ac35418ee8731940@%3Cdev.beam.apache.org%3E
> [6]
>
> https://lists.apache.org/thread.html/e6ffcba94ef4514e8cf5c6fed39100ee359b954c4876d3275b1bc33a@%3Cdev.beam.apache.org%3E
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Looking for mentors

[Sergio Fernández]

(Off-topic) At some point we may need to discuss our incubation capacity...
People present cool proposal and they get vote just because that, without
checking our available resources.

On Thu, Jun 9, 2016 at 3:38 AM, John D. Ament <johndam...@apache.org> wrote:

> All,
>
> Speaking on behalf of the to-be-proposed Juneau project, I wanted to reach
> out to the broader community to see interest in getting mentors setup for
> this project.
>
> You can find the proposal here:
> http://wiki.apache.org/incubator/JuneauProposal
>
> John
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Joe Witt joins the Incubator PMC

[Sergio Fernández]

Welcome, Joe!

On Tue, Jun 7, 2016 at 4:03 AM, Joe Witt <joe.w...@gmail.com> wrote:

> Thank you all.  Very happy to be able to help and give back to new
> communities forming in the incubator.  I know I benefited greatly from
> the mentors we had during incubation and definitely feel like I need
> to return the favor.
>
> I can definitely not be as awesome as Justin is with licensing/release
> review diligence but I can sure try to help take the edge off!
>
> On Mon, Jun 6, 2016 at 9:53 PM, Martin Gainty <mgai...@hotmail.com> wrote:
> > Welcome Joseph!
> >
> > Martin
> >
> >
> >
> >> From: mar...@rectangular.com
> >> Date: Mon, 6 Jun 2016 12:48:35 -0700
> >> Subject: Joe Witt joins the Incubator PMC
> >> To: general@incubator.apache.org
> >>
> >> Greets,
> >>
> >> I'm pleased to announce that Apache Member Joe Witt has joined the
> >> Incubator PMC!
> >>
> >> Joe is a core contributor to Apache NiFi, and is currently the
> >> project's PMC Chair.  Joe knows the Incubator from NiFi's trip through
> >> it -- we look forward to him returning to contribute as a member of
> >> the IPMC!
> >>
> >> Marvin Humphrey, on behalf of the IPMC
> >>
> >> -
> >> 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
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Fwd: Podling Report Reminder - June 2016

[Sergio Fernández]

On Thu, Jun 2, 2016 at 10:25 AM, Nick Burch <apa...@gagravarr.org> wrote:

> On Thu, 2 Jun 2016, Sergio Fernández wrote:
>
>> Can anybody give karma to GaryGregory for editing the incubator wiki?
>> Thanks.
>>
>
> Karma granted, happy editing!


Thanks, Nick!


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Fwd: Podling Report Reminder - June 2016

[Sergio Fernández]

Can anybody give karma to GaryGregory for editing the incubator wiki?
Thanks.


-- Forwarded message --
From: Gary Gregory <garydgreg...@gmail.com>
Date: Thu, Jun 2, 2016 at 9:21 AM
Subject: Re: Podling Report Reminder - June 2016
To: d...@commonsrdf.incubator.apache.org


Crud, I cannot seem to edit the Wiki. I am logged on the wiki as
"GaryGregory" Do I karma?

Gary

On Wed, Jun 1, 2016 at 4:44 PM, <johndam...@apache.org> wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 1st).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/June2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [PROPOSAL] Apache Annotator

[Sergio Fernández]

Hi Benjamin,

looks promising! Very interesting stuff.

I'd be willing to mentor it, but I'm already in my limit with two podlings.

For the proposal at https://wiki.apache.org/incubator/AnnotatorProposal
your should remove the hints from the template (e.g., "A short descriptive
summary of the project...") to improve readability.

Cheers,


On Tue, May 31, 2016 at 10:41 PM, Benjamin Young <byo...@bigbluehat.com>
wrote:

> Yeah. A bit of both, actually. ;)
>
> JSON-LD is the new bridge builder / peace-maker in this space.
>
> There's an RDF-based data model "underneath" but the expression of it can
> be treated as "plain JSON" for those who don't do RDF.
>
> For instance, I have the beginnings of the Web Annotation Protocol built
> on Apache CouchDB:
> https://github.com/BigBlueHat/ldp-on-couchdb
>
> The Web Annotation Protocol is based on LDP BasicContainers--which really
> just (re)defined GET, POST, PUT, and DELETE + Link headers for finding your
> way around:
> https://www.w3.org/TR/annotation-protocol/
>
> Anyhow, it's getting uptake from folks who have little to no interest in
> RDF or graphs as well as folks who depend heavily on RDF and graphs--which
> is about the best scenario we can hope for these days. :)
>
> Thanks for the thoughts, Nick!
> Benjamin
>
> -Original Message-
> From: Nick Kew [mailto:n...@apache.org]
> Sent: Tuesday, May 31, 2016 4:36 PM
> To: general@incubator.apache.org
> Subject: Re: [PROPOSAL] Apache Annotator
>
> On Tue, 2016-05-31 at 18:13 +, Benjamin Young wrote:
> > Yeah. Lots has happened in the intervening 14 years. :)
>
> :)
>
> Thanks for the reply.  I kind-of thought it might've done, but (having
> followed your first link and found only javascript that had nothing to say
> on the subject) I was looking for ...
> well, I guess your reply and the links in it.
>
> Lots more reading to do, but I see it's moved from RDF and pie-in-the-sky
> to JSON and some more realistic expectations.
>
> --
> Nick Kew
>
>
> -----
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[ANNOUNCE] Apache CommonsRDF 0.2.0-incubating released

[Sergio Fernández]

The Apache CommonsRDF team is proud to announce the latest release of
Apache CommonsRDF 0.2.0.

Apache Commons RDF aims to provide a common library for RDF 1.1 that could
be implemented by systems on the Java Virtual Machine (e.g., Apache Jena or
Eclipse RDF4J). The main motivation behind this simple library is revise an
historical incompatibility issue. This library does not pretend to be a
generic API wrapping those libraries, but a set of interfaces for the RDF
1.1 concepts that can be used to expose common RDF 1.1 concepts using
common Java interfaces.

More details can be found at https://commonsrdf.incubator.apache.org/

Version 0.2.0 represent the evolution of the API towards providing a common
RDF library.

Further details can be found in the release notes:
https://s.apache.org/0.2.0-incubating

Binary and source archives are available from:
http://commonsrdf.incubator.apache.org/download.html

User guide:
http://commonsrdf.incubator.apache.org/userguide.html

Maven artifacts have also been made available on repository.apache.org and
Maven Central.

Thanks on behalf of the CommonsRDF PPMC.

Disclaimer: Apache Commons RDF is an effort undergoing incubation at The
Apache Software Foundation (ASF) sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept CarbonData into the Apache Incubator

[Sergio Fernández]

itial Source ==
>
> https://github.com/HuaweiBigData/carbondata.git
>
> == External Dependencies ==
>
> All external dependencies are licensed under an Apache 2.0 license or
> Apache-compatible license. As we grow the Carbondata community we will
> configure our build process to require and validate all contributions
> and dependencies are licensed under the Apache 2.0 license or are under
> an Apache-compatible license.
>
>  * Apache Spark
>  * Apache Hadoop
>  * Apache Maven
>  * Apache Commons
>  * Apache Log4j
>  * Apache Thrift
>  * Apache Zookeeper
>  * Scala
>  * Snappy
>  * Kettle (Pentaho)
>  * Eigenbase
>  * Fastutil
>  * GSON
>  * Jmockit
>  * Junit
>
> == Required Resources ==
>
> === Mailing lists ===
>
>  * priv...@carbondata.incubator.apache.org (moderated subscriptions)
>  * comm...@carbondata.incubator.apache.org
>  * d...@carbondata.incubator.apache.org
>  * iss...@carbondata.incubator.apache.org
>
> === Git Repository ===
>
>  * https://git-wip-us.apache.org/repos/asf/incubator-carbondata.git
>
> === Issue Tracking ===
>
>  * JIRA Project CarbonData (CarbonData)
>
> === Initial Committers ===
>
>  * Liang Chenliang
>  * Jean-Baptiste Onofré
>  * Henry Saputra
>  * Uma Maheswara Rao G
>  * Jenny MA
>  * Jacky Likun
>  * Vimal Das Kammath
>  * Jarray Qiuheng
>
> === Affiliations ===
>
>  * Huawei: Liang Chenliang
>  * Talend: Jean-Baptiste Onofré
>  * Ebay: Henry Saputra
>  * Intel: Uma Maheswara Rao G
>
> === Sponsors ===
>
> === Champion ===
>
>  * Jean-Baptiste Onofré - Apache Member
>
> === Mentors ===
>
>  * Henry Saputra (eBay)
>  * Jean-Baptiste Onofré (Talend)
>  * Uma Maheswara Rao G (Intel)
>
> === Sponsoring Entity ===
>
> The Apache Incubator
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[ANNOUNCE] Apache CommonsRDF 0.2.0-incubating released

[Sergio Fernández]

The Apache CommonsRDF team is proud to announce the latest release of Apache
CommonsRDF 0.2.0.

Apache BroCommons RDF aims to provide a common library for RDF 1.1 that
could be implemented by systems on the Java Virtual Machine. More details
can be found at https://commonsrdf.incubator.apache.org/

Version 0.2.0 represent the evolution of the API towards providing a common
RDF library. Further details can be found in the release notes:
https://s.apache.org/0.2.0-incubating

Binary and source archives are available from:
http://commonsrdf.incubator.apache.org/download.html

User guide:
http://commonsrdf.incubator.apache.org/userguide.html

Maven artifacts have also been made available on repository.apache.org and
Maven Central.

Thanks on behalf of the CmmonsRDF PPMC.

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Sergio Fernández]

ithub.com/PredictionIO/PredictionIO/issues
> .
>   We will migrate to Apache JIRA.
>
>   JIRA PREDICTIONIO
>   https://issues.apache.org/jira/browse/PREDICTIONIO
>
> Other Resources
>
>   TravisCI for builds and test running.
>
>   PredictionIO's documentation, included in the code repo (docs/manual
>   directory), is built with Middleman and publicly hosted at
>   https://docs.prediction.io
>
>   A blog to drive adoption and excitement at https://blog.prediction.io
>
> Initial Committers
>
>   Pat Ferrell
>   Tamas Jambor
>   Justin Yip
>   Xusen Yin
>   Lee Moon Soo
>   Donald Szeto
>   Kenneth Chan
>   Tom Chan
>   Simon Chan
>   Marco Vivero
>   Matthew Tovbin
>   Yevgeny Khodorkovsky
>   Felipe Oliveira
>   Vitaly Gordon
>   Alex Merritt
>
> Affiliations
>
>   Pat Ferrell - ActionML
>   Tamas Jambor - Channel4
>   Justin Yip - independent
>   Xusen Yin - USC
>   Lee Moon Soo - NFLabs
>   Donald Szeto - Salesforce
>   Kenneth Chan - Salesforce
>   Tom Chan - Salesforce
>   Simon Chan - Salesforce
>   Marco Vivero - Salesforce
>   Matthew Tovbin - Salesforce
>   Yevgeny Khodorkovsky - Salesforce
>   Felipe Oliveira - Salesforce
>   Vitaly Gordon - Salesforce
>   Alex Merritt - ActionML
>
> Sponsors
>
> Champion
>
>   Andrew Purtell 
>
> Nominated Mentors
>
>   Andrew Purtell 
>   James Taylor 
>   Lars Hofhansl 
>   Suneel Marthi 
>   Xiangrui Meng 
>   Luciano Resende 
>
> Sponsoring Entity
>
>   Apache Incubator PMC
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[RESULT] [VOTE] Release Apache CommonsRDF 0.2.0-incubating based on RC3

[Sergio Fernández]

Hi,

after being open for more than 72 hours, the vote for releasing RC3 as
Apache CommonsRDF 0.2.0-incubating
https://lists.apache.org/thread.html/Zgvi38zfo1yumzk has passed 5 +1s (4
binding) and 1 -0, detailed as follows:

+1s:
Stian Soiland-Reyes
Sergio Fernández
John D. Ament
Lewis John Mcgibbney
Justin Mclean

-0
Gary Gregory

I'll prepare the release and announce it when the sources and maven
binaries will be properly mirrored.

Thanks everybody who has helped in getting out this incubating release.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[Sergio Fernández]

eve these would
> be orphaned or, should they become orphaned, that it would impact the
> development of the project.
>
> Inexperience with Open Source:
> Most of the current committers are already ASF members and
> committers, we do not believe there to be any concerns around OSS
> inexperience.
>
> Homogenous Developers:
> While the current mix of people involved in the project spans
> several continents with a wide variety of skills and experience, a long
> standing relation with the ASF applies to all committers (even the
> non-ASF people in this proposal are intimately familiar with the ASF),
> and we believe there to be a very homogeneous culture in terms of
> development, IP and release processes.
>
> Reliance on Salaried Developers:
> While two of the committers in this project are salaried
> developers with regards to Pony, the project was founded outside of
> corporate interests, and is primarily driven by people either working
> for or with ties to non-profit
>
> organisations.
> We see no issues regarding possible strong-arming or otherwise
> skewing project focus, nor do we believe that absence of salaries would
> deter people from committing to this project.
>
> Relationships with Other Apache Products:
> Pony Mail uses at least Apache HTTPd with mod_lua as its
> end-user facing delivery mechanism. Many of the commiters are also
> involved with this PMC.
>
> Pony also utilises ElasticSearch which is based on Lucene.
>
> Documentation
>
> Documentation will initially be in the source tree, and be part of
> the initial code inclusion.
>
> Initial Source
>
> The initial source was written under the Apache License v/2.0 from
> the beginning, and is available at:
>
> https://github.com/Quenda/ponymail
>
> Source and Intellectual Property Submission Plan
>
> We know of no legal encumberments in the way of transfer of source
> to Apache. Portions of the software (sans dependencies) is already owned
> by the ASF, other portions privately, but it will be granted to the ASF
> in its entirety.
>
> External Dependencies:
>
> ElasticSearch backend (Apache License v/2.0)
> Apache HTTP Server front-end with mod_lua loaded (Apache License
> v/2.0 for httpd, MIT for Lua)
> Python 3.x for importing/archiving (PSF License)
> Lua 5.1 or 5.2 + lua-cjson (MIT License, lua-cjson is optional)
> Bootstrap/JQuery (MIT License)
>
> Cryptography Pony employs no cryptography other than what TLS-enabled
> web sites served by HTTPd might use.
>
> Required Resources:
>
> Mailing lists:It would be rude not too, given this project should
> archive them.
>
> Subversion Directory:Nope
>
> Git Repositories:
> - incubator-ponymail.git - incubator-ponymail-site.git
>
> Issue Tracking: JIRA or GitHub Issues
>
> Other Resources: Dev stack, PoC Stack, HipChat Channel
>
> Initial Committers
>
> Daniel Gruno < humbed...@apache.org >
>
> Tony Stevenson < pct...@apache.org >
>
> Richard Bowen < rbo...@apache.org >
>
> Ulises Beresi < ulises.cerv...@gmail.com >
>
> David P Kendal < apa...@dpk.io >
>
> Francesco Chicchiriccò - < ilgro...@apache.org >
>
> Sam Ruby < ru...@apache.org >
>
> Shane Curcuru < curc...@apache.org >
>
> Jim Jagielski < j...@apache.org >
>
> Affiliations
>
> Daniel Gruno - Quenda IvS
> Tony Stevenson - pctony ltd, VocalIQ Ltd
> Richard Bowen - Redhat, inc.
>     Ulises Beresi - Datastax, inc.
> David P Kendal - Quenda IvS
> Francesco Chicchiriccò - Tirasa S.r.l.
> Sam Ruby - IBM
> Shane Curcuru - IBM(?)
> Jim Jagielski - Capital One
>
> Sponsors
>
> Champion:
>
> Suneel Marthi < smar...@apache.org >
>
> Nominated Mentors:
>
> Andrew Bayer < aba...@apache.org >
>
> John D. Ament < johndam...@apache.org >
>
> Sponsoring Entity:
> The Apache Software Foundation
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache CommonsRDF 0.2.0-incubating RC3

[Sergio Fernández]

On Fri, May 20, 2016 at 4:26 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
>
> > @Justin is this the equivalent of a PPMC throwing you a freebie? :-)
>
> They didn't need to be added to my “owe me a beer” list :-)
>

Because the beer has been already paid in Vancouver ;-)

Thanks, Justin for checking the rc.

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[VOTE] Release Apache CommonsRDF 0.2.0-incubating RC3

[Sergio Fernández]

Hi,

I am pleased to post a RC3 for CommonsRDF (Incubating) 0.2.0-incubating for
a public VOTE.

CommonsRDF 0.2.0-incubating RC3 is available for review at:
https://dist.apache.org/repos/dist/dev/incubator/commonsrdf/0.2.0-incubating/

Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1168/

Details of changes since 0.1.0-incubating are in the release notes:
https://s.apache.org/0.2.0-incubating

The source code tagged with 0.2.0-incubating-RC3 refers to
commit 433ffd9da203a86dfceba95765dbf90dc039ef24

RC3 has been built with Maven 3.3.3 and OpenJDK 1.8.0_66-internal on Debian
64 bits.

KEYS: https://www.apache.org/dist/incubator/commonsrdf/KEYS

The vote at d...@commonsrdf.incubator.apache.org
https://lists.apache.org/thread.html/Z715psnjorf47kz has 3 +4s (Stian
Soiland-Reyes, Sergio Fernández, John D. Ament, Lewis John Mcgibbney) and 1
-0 (Gary Gregory).

Please review the release candidate and vote.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

This vote will close no sooner that 72 hours from now.

Thanks to everyone that contributed to this development drive and also
anyone able to review.

Best

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Throwing my hat in the ring

[Sergio Fernández]

Welcome to Incubator, Daniel!
Was great to meet you in Vancouver!
On May 14, 2016 6:18 PM,  wrote:

> Hi, all;
> I've been having a lot of great F2F talks the past few days at the con and
> Marvin has talked me into throwing my hat in the ring to help with the
> incubator project. So, yeah - I'm game to help where I can (and by sending
> this email, it kinda forces me to follow through).
>
> AIUI, I'm able to be an informal mentor for any podlings of interest (hey,
> there Guacamole!) so I'll just kinda poke around with that for a while, but
> I'll also keep an eye out here for other stuff that comes up.
>
> I've been soaking up documentation while airport hopping to get a better
> idea of what goes on and what I can do specifically, but unfortunately
> haven't had a chance to read the archives for this list.
>
> --
> Daniel Ruggeri
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire Concerted

[Sergio Fernández]

+1 (binding)
Sad, but something quite expected.
So a lesson to learn for future similar cases.

On Wed, Apr 20, 2016 at 1:32 AM, Julian Hyde <jh...@apache.org> wrote:

> Following a discussion[1], the Concerted community has voted to retire the
> project from incubation[2]. Per the retirement guide[3], the next step is
> an IPMC vote for retirement.
>
> This is a vote of the IPMC to confirm the decision to retire the podling.
>
> [ ] +1 to retire Concerted from the Incubator
> [ ] -1 to keep Concerted in the Incubator
>
> This vote will be held open for at least 72 hours.
>
> Here is my vote:
>
> [x] +1 retire Concerted
>
> Julian Hyde
>
>
>
> [1] https://s.apache.org/concerted-retire-discuss
>
> [2] https://s.apache.org/concerted-retire-vote
>
> [3] http://incubator.apache.org/guides/retirement.html
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Graduate TinkerPop from Incubator

[Sergio Fernández]

+1 (binding)

On Tue, Apr 5, 2016 at 1:11 PM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> The Apache TinkerPop community has discussed graduation to a top level
> project and achieved consensus:
>
> https://s.apache.org/PKhX
>
> Please vote on the resolution that follows to graduate Apache TinkerPop
> from incubator to top level project. This vote will be open for at least 72
> hours.
>
> Thanks,
>
> Stephen Mallette on behalf of the Apache TinkerPop PPMC
>
> ==
> X. Establish the Apache TinkerPop 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 graph computing framework for graph
> databases and graph analytic systems
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache TinkerPop Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache TinkerPop Project be and hereby is
> responsible for the creation and maintenance of software
> related to a graph computing framework for graph databases
> and graph analytic systems.
>
> RESOLVED, that the office of "Vice President, Apache TinkerPop" 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 TinkerPop Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache TinkerPop 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 TinkerPop Project Management Committee:
>
> * Daniel Gruno <humbed...@apache.org>
> * Daniel Kuppitz <dkupp...@apache.org>
> * James Thornton <esp...@apache.org>
> * Hadrian Zbarcea <hadr...@apache.org>
> * Marko Rodriguez <ok...@apache.org>
> * Stephen Mallette <spmalle...@apache.org>
> * Ted Wilmes <twil...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen Mallette
> be appointed to the office of Vice President, Apache TinkerPop, 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 TinkerPop 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 TinkerPop Project; and be it further
>
> RESOLVED, that the Apache TinkerPop Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator TinkePop podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator TinkerPop podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Graduate Johnzon from the Incubator

[Sergio Fernández]

+1 (binding)

On Sat, Apr 2, 2016 at 12:40 PM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> +1 non-binding
> On 1 Apr 2016 20:49, "Hendrik Dev" <hendrikde...@gmail.com> wrote:
>
> > The Apache Johnzon community has discussed and voted on graduation to
> > a top level project. The vote passed with 8 +1 votes (5 from the PPMC)
> > and no 0 or -1 votes.
> >
> > Incubation Status:
> > http://incubator.apache.org/projects/johnzon.html
> > Maturity Assessment:
> > https://s.apache.org/d88S
> > Discussions:
> > https://s.apache.org/5vxO
> > https://s.apache.org/8VkX
> > Vote:
> > https://s.apache.org/suuK
> > (http://markmail.org/message/mawumtfqokgye5xn)
> > Result:
> > https://s.apache.org/Erd0
> > (http://markmail.org/message/qmqvk56ccqkq2gob)
> >
> > Please vote on the resolution pasted below to graduate Apache Johnzon
> > from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Johnzon from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Johnzon from the Incubator because ...
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> >
> > Hendrik Saly on behalf of the Apache Johnzon PPMC
> >
> > Apache Johnzon top-level project resolution:
> > 
> >
> > 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 JSR-353 compliant JSON parsing and a
> > set of useful modules to help with the usage of JSR-353
> > as well as JSR successors (like JSR-374) or related JSRs
> > (like JSR-367).
> >
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Johnzon Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Johnzon Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to JSR-353 compliant JSON parsing and a
> > set of useful modules to help with the usage of JSR-353
> > as well as JSR successors (like JSR-374) or related JSRs
> > (like JSR-367); and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Johnzon" 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 Johnzon Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Johnzon 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 Johnzon Project:
> >
> > * Justin Mclean 
> > * Romain Manni-Bucau 
> > * Jean-Louis Monteiro 
> > * Mark Struberg 
> > * Hendrik Saly 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hendrik Saly (salyh)
> > be appointed to the office of Vice President, Apache Johnzon, 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 Johnzon 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 Johnzon Project; and be it further
> >
> > RESOLVED, that the Apache Johnzon Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Johnzon podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator Johnzon podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
> > --
> > Hendrik Saly (salyh, hendrikdev22)
> > @hendrikdev22
> > PGP: 0x22D7F6EC
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Airflow into the Incubator

[Sergio Fernández]

leviewer=file-view-default|filechunkio
> > > (MIT)]]
> > > * [[
> >
> https://bitbucket.org/tarek/flake8/src/a209fb69350c572c9b2d7b4b09c7657be153be5e/LICENSE?fileviewer=file-view-default|flake8
> > > (MIT)]]
> > > * [[https://github.com/mitsuhiko/flask/blob/master/LICENSE|flask
> (BSD)]]
> > > * [[
> >
> https://github.com/flask-admin/flask-admin/blob/master/LICENSE|flask-admin
> > > (BSD)]]
> > > * [[
> > https://github.com/thadeusb/flask-cache/blob/master/LICENSE|flask-cache
> > > (BSD)]]
> > > * [[
> >
> https://github.com/maxcountryman/flask-login/blob/master/LICENSE|flask-login
> > > (MIT)]]
> > > * [[https://github.com/mher/flower/blob/master/LICENSE|flower (BSD)]]
> > > * [[
> >
> https://github.com/PythonCharmers/python-future/blob/master/LICENSE.txt|future
> > > (MIT)]]
> > > * [[https://github.com/benoitc/gunicorn/blob/master/LICENSE|gunicorn
> > (MIT)]]
> > > * [[
> >
> https://github.com/youngwookim/hive-thrift-py/blob/master/setup.py|hive-thrift-py
> > > (Apache 2.0)]]
> > > * [[https://github.com/ipython/ipython/blob/master/COPYING.rst|ipython
> > (BSD)]]
> > > * [[https://github.com/mitsuhiko/jinja2/blob/master/LICENSE|jinja2
> > (BSD)]]
> > > * [[
> >
> https://github.com/waylan/Python-Markdown/blob/master/LICENSE.md|markdown
> > > (BSD)]]
> > > * [[https://github.com/pydata/pandas/blob/master/LICENSE|pandas
> (BSD)]]
> > > * [[https://pypi.python.org/pypi/Pygments|pygments (BSD)]]
> > > * pyhive
> > > * pydruid
> > > * PyOpenSSL
> > > * PySmbClient
> > > * python-dateutil
> > > * redis
> > > * requests
> > > * setproctitle
> > > * statsd
> > > * sphinx
> > > * sphinx-argparse
> > > * sphinx_rtd_theme
> > > * Sphinx-PyPI-upload
> > > * sqlalchemy (MIT)
> > > * thrift
> > > * jaydebeapi
> > > * mysqlclient
> > > * unicodecsv
> > > * slackclient
> > > * ldap3
> > > * Flask-WTF
> > > * lxml
> > > * [[
> https://github.com/bgamble/pykerberos/blob/master/LICENSE|pykerberos
> > > (Apache 2.0)]]
> > > * [[https://github.com/pyca/bcrypt/blob/master/LICENSE|bcrypt (Apache
> > 2.0)]]
> > > * [[
> >
> https://github.com/maxcountryman/flask-bcrypt/blob/master/LICENSE|flask-bcrypt
> > > (BSD)]]
> > > * [[https://github.com/testing-cabal/mock/blob/master/LICENSE.txt|mock
> > (BSD)]]
> > > * [[https://github.com/mtth/hdfs/blob/master/LICENSE|hdfs (MIT)]]
> > >
> > > == Cryptography ==
> > >
> > > None
> > >
> > > == Required Resources ==
> > >
> > > === Mailing Lists ===
> > >
> > > * priv...@airflow.incubator.apache.org (moderated)
> > > * d...@airflow.incubator.apache.org
> > > * comm...@airflow.incubator.apache.org
> > >
> > > === Subversion Directory ===
> > >
> > > Git is the preferred source control system: git://
> git.apache.org/Airflow
> > >
> > > === Issue Tracking ===
> > >
> > > JIRA Airflow (Airflow)
> > >
> > > === Other Resources ===
> > >
> > > The existing code already has unit tests, so we would like a Travis
> > > instance to run them whenever a new patch is submitted. This can be
> > > added after project creation.
> > >
> > > == Initial Committers ==
> > >
> > > * Maxime Beauchemin
> > > * Siddharth Anand
> > > * Chris Riccomini
> > > * Bolke de Bruin
> > > * Arthur Wiedmer
> > > * Dan Davydov
> > > * Jeremiah Lowin
> > > * Patrick Leo Tardif
> > >
> > > == Affiliations ==
> > >
> > > * Maxime Beauchemin (Airbnb)
> > > * Siddharth Anand (Agari)
> > > * Chris Riccomini (WePay)
> > > * Bolke de Bruin (ING)
> > > * Arthur Wiedmer (Airbnb)
> > > * Dan Davydov (Airbnb)
> > > * Jeremiah Lowin (Kokino)
> > > * Patrick Leo Tardif (Airbnb)
> > >
> > > == Sponsors ==
> > >
> > > === Champion ===
> > >
> > > Chris Riccomini (WePay, Apache Samza PMC)
> > >
> > > === Nominated Mentors ===
> > >
> > > * Chris Nauroth (HortonWorks, Apache Hadoop Committer/PMC Member,
> > > Apache ZooKeeper Committer, Apache Software Foundation Member)
> > > * Hitesh Shah (HortonWorks, Apache Hadoop Committer/PMC Member,
> > > Apache Ambari Committer/PMC Member, Apache Tez Committer/PMC Member,
> > > Apache Software Foundation Member)
> > > * Jakob Homan (OfferUp, Apache Hadoop Committer/PMC Member, Apache
> > > Kafka Committer/PMC Member, Apache Samza Committer/PMC Member, Apache
> > > Giraph Committer/PMC Member,  Apache Software Foundation Member)
> > >
> > > === Sponsoring Entity ===
> > >
> > > We are requesting the Incubator to sponsor this project.
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] TinkerPop 3.1.1-incubating Release

[Sergio Fernández]

+1 (binding)

So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and
disclaimer, NOTICE and LICENSE files, build sources in a clean environment
(openjdk8, debian 64bits).

Aligned with Justin, this new release addresses my main concerns
in 3.1.0-incubating, where ALv2 software is not anymore in your LICENSE
file, but the NOTICE didn't receive all the expected notices. Nothing
blocking, just something to keep improving.



On Thu, Feb 11, 2016 at 5:01 PM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> Hello,
>
> We are happy to announce that TinkerPop 3.1.1-incubating is ready for
> release.
>
> The release artifacts can be found at this location:
>
> https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.1.1-incubating/
>
> The source distribution is provided by:
> apache-tinkerpop-3.1.1-incubating-src.zip
>
> Two binary distributions are provided for user convenience:
> apache-gremlin-console-3.1.1-incubating-bin.zip
> apache-gremlin-server-3.1.1-incubating-bin.zip
>
> The GPG key used to sign the release artifacts is available at:
> https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/KEYS
>
> The online docs can be found here:
> http://tinkerpop.apache.org/docs/3.1.1-incubating/reference/ (user docs)
> http://tinkerpop.apache.org/docs/3.1.1-incubating/upgrade/ (upgrade docs)
> http://tinkerpop.apache.org/javadocs/3.1.1-incubating/core/ (core javadoc)
> http://tinkerpop.apache.org/javadocs/3.1.1-incubating/full/ (full javadoc)
>
> The tag in Apache Git can be found here:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=d225c4609c02a0e0ea62214e055c6f8eb37b63d0
>
> The release notes are available here:
>
> https://github.com/apache/incubator-tinkerpop/blob/tp31/CHANGELOG.asciidoc#tinkerpop-311-release-date-february-8-2016
>
> Finally, the dev@tinkerpop [VOTE] thread can be found at this location:
>
> https://pony-poc.apache.org/thread.html/Zc5152tqpdz7adz
>
> Result summary: +12 (5 binding, 7 non-binding), 0 (0), -1 (0)
>
> The [VOTE] will be open for the next 72 hours --- closing Sunday (February
> 14, 2016) at 11AM EST.
>
> Thanks,
>
> Stephen
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: New ASF visual identity

[Sergio Fernández]

+1

On Wed, Feb 3, 2016 at 8:40 PM, Sravya Tirukkovalur <sra...@cloudera.com>
wrote:

> +1
>
> On Wed, Feb 3, 2016 at 10:51 AM, <markus.ge...@live.de> wrote:
>
> >
> >
> > +1
> >
> >
> > Best,
> >
> >
> > Markus
> >
> >
> > .:: YAGNI likes a DRY KISS ::.
> >
> >
> >
> >
> >
> >
> > On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" <
> > mar...@rectangular.com> wrote:
> >
> >
> >
> >
> >
> > Greets,
> >
> > The ASF has a new look:
> >
> >
> >
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
> > https://www.apache.org/foundation/press/kit/
> >
> > The main Incubator website needs to be updated with the new visual
> > identity, as do podling websites.
> >
> > I volunteer to create a drop-in replacement for the egg logo:
> >
> > http://incubator.apache.org/images/egg-logo.png
> >
> > I expect to take the same approach as the last time the graphic was
> > updated a few years back[1]: keep the black border and keep the same
> > pixel dimensions, so that existing podling web pages can simply switch
> > in the new file without needing to adapt their designs.
> >
> > Please note: the intent of this undertaking is to keep the Incubator up
> > to date and in sync with the efforts of our marketing team. It is not
> > to rework the Incubator's visual identity, so I hope that we can avoid a
> > lengthy bikeshed painting debate.
> >
> > Marvin Humphrey
> >
> > [1] https://issues.apache.org/jira/browse/INCUBATOR-112
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Sravya Tirukkovalur
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Beam into the Apache Incubator

[Sergio Fernández]

gle.com]
>  * Davor Bonaci[da...@google.com]
>  * Frances Perry   [f...@google.com]
>  * James Malone[jamesmal...@google.com]
>  * Jean-Baptiste Onofré[jbono...@apache.org]
>  * Josh Wills  [jwi...@apache.org]
>  * Kostas Tzoumas  [kos...@data-artisans.com]
>  * Kenneth Knowles [k...@google.com]
>  * Luke Cwik   [lc...@google.com]
>  * Maximilian Michels  [m...@apache.org]
>  * Stephan Ewen[step...@data-artisans.com]
>  * Tom White   [t...@cloudera.com]
>  * Tyler Akidau[taki...@google.com]
>  * Robert Bradshaw [rober...@google.com]
>
> == Additional Interested Contributors ==
>
>  * Debo Dutta  [dedu...@cisco.com]
>  * Henry Saputra   [hsapu...@apache.org]
>  * Taylor Goetz[ptgo...@gmail.com]
>  * James Carman[ja...@carmanconsulting.com]
>  * Joe Witt[joew...@apache.org]
>  * Vaibhav Gumashta[vgumas...@hortonworks.com]
>  * Prasanth Jayachandran   [pjayachand...@hortonworks.com]
>  * Johan Edstrom   [seij...@gmail.com]
>  * Hugo Louro  [hmclo...@gmail.com]
>  * Krzysztof Sobkowiak [krzys.sobkow...@gmail.com]
>  * Jeff Genender   [jgenen...@apache.org]
>  * Edward J. Yoon  [edward.y...@samsung.com]
>  * Hao Chen[h...@apache.org]
>  * Byung-Gon Chun  [bgc...@gmail.com]
>  * Charitha Elvitigala [charit...@apache.org]
>  * Alexander Bezzubov  [b...@apache.org]
>  * Tsuyoshi Ozawa  [oz...@apache.org]
>  * Mayank Bansal   [maban...@gmail.com]
>  * Supun Kamburugamuve [su...@apache.org]
>  * Matthias Wessendorf [mat...@apache.org]
>  * Felix Cheung[felixche...@apache.org]
>  * Ajay Yadava [ajay.ya...@inmobi.com]
>  * Liang Chen  [chenliang...@huawei.com]
>  * Renaud Richardet[renaud (at) apache (dot) org]
>  * Bakey Pan   [bakey1...@gmail.com]
>  * Andreas Neumann [a...@apache.org]
>  * Suresh Marru[sma...@apache.org]
>  * Hadrian Zbarcea [hzbar...@gmail.com]
>
> == Affiliations ==
>
> The initial committers are from six organizations. Google developed
> Dataflow and the Dataflow SDK, data Artisans developed the Flink runner,
> and Cloudera (Labs) developed the Spark runner.
>
>  * Cloudera
>   * Tom White
>  * Data Artisans
>   * Aljoscha Krettek
>   * Kostas Tzoumas
>   * Maximilian Michels
>   * Stephan Ewen
>  * Google
>   * Ben Chambers
>   * Dan Halperin
>   * Davor Bonaci
>   * Frances Perry
>   * James Malone
>   * Kenneth Knowles
>   * Luke Cwik
>   * Tyler Akidau
>   * Robert Bradshaw
>  * PayPal
>   * Amit Sela
>  * Slack
>   * Josh Wills
>  * Talend
>   * Jean-Baptiste Onofré
>
> == Sponsors ==
>
> === Champion ===
>
>  * Jean-Baptiste Onofre [jbono...@apache.org]
>
> === Nominated Mentors ===
>
>  * Jean-Baptiste Onofre   [jbono...@apache.org]
>  * Jim Jagielski  [j...@apache.org]
>  * Venkatesh Seetharam[venkat...@apache.org]
>  * Bertrand Delacretaz[bdelacre...@apache.org]
>  * Ted Dunning[tdunn...@apache.org]
>
> === Sponsoring Entity ===
>
> The Apache Incubator
> 
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache FreeMarker 2.3.24-rc01 (incubating)

[Sergio Fernández]

Once I had time to check this new attempt, I vote +1 (binding) to
release Apache FreeMarker 2.3.24-rc01.


On Fri, Jan 22, 2016 at 9:13 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
>
> I'd also suggest that you name each release candidate in order e.g rc1,
> rc2, rc3 etc etc rather than naming them all rc1. There's less chance of
> confusion and people voting on the wrong release candidate that way.


Justin, Podling has decided to keep their old method having RCs out for a
while for integration testing. Because RCs will be public and announce,
they have to be voted as a regular release. For for this podling what
normally is a RCs are called "attempts". That's was the source I vote -1,
because FMPOV that was not properly handled in the process. Something to
improve, for sure.


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Websites at podling.apache.org

[Sergio Fernández]

+1

On Fri, Dec 4, 2015 at 4:33 AM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Tue, Dec 1, 2015 at 2:02 AM, Sergio Fernández <wik...@apache.org>
> wrote:
> > Well, the transition is not that hard if:
> >
> > a) during incubation podling.a.o redirects (302/307) to podling.i.a.o
> >
> > b) after graduation podling.i.a.o redirects (301) to podling.a.o
> >
> > right?
>
> Discussion has quieted down.  I plan to claim lazy consensus in a
> couple of days and address this situation by opening an INFRA Jira
> requesting that redirects be installed per above. I'll post the link
> to that issue in this thread.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Websites at podling.apache.org

[Sergio Fernández]

Yes, INFRA arguments are completely valid. But rather than the DNS
resolution of the domains, I think Marvin was asking how domains are
handled at the HTTP level.
Niall

Thanks for digging up the reference

I knew INFRA had made the change for a reason but couldn't remember the
reasoning

Rob

On 01/12/2015 16:18, "Niall Pemberton"  wrote:

>On Tue, Dec 1, 2015 at 4:46 AM, Marvin Humphrey 
>wrote:
>
>> Greets,
>>
>> It seems that podling websites are available at both these URL patterns:
>>
>>   http://podling.incubator.apache.org
>>   http://podling.apache.org
>>
>> See for example:
>>
>>   http://systemml.apache.org/
>>   http://systemml.incubator.apache.org/
>>   http://mynewt.apache.org/
>>   http://mynewt.incubator.apache.org/
>>
>> I believe that resolving podling.apache.org is a mistake based on the
>> following pages:
>>
>>   http://incubator.apache.org/guides/sites
>>   http://incubator.apache.org/guides/branding
>>
>>
>See http://markmail.org/message/l4khtbfgq7b72hsw
>
>Niall
>
>
>> Shall we ask Infra to install 302 redirects?
>>
>> Marvin Humphrey
>>
>> -
>> 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: Websites at podling.apache.org

[Sergio Fernández]

Well, the transition is not that hard if:

a) during incubation podling.a.o redirects (302/307) to podling.i.a.o

b) after graduation podling.i.a.o redirects (301) to podling.a.o

right?


On Tue, Dec 1, 2015 at 10:44 AM, Rob Vesse <rve...@dotnetrdf.org> wrote:

> I seem to remember that INFRA used to do redirects but decided to stop
> doing them because it made the transition to TLP easier for podlings post
> graduation because their "final" URL was active from as soon as they start
> (assuming they don't name change during incubation)
>
> Pretty much any of the current crop of podlings can be resolved via
> podling.apache.org AFAICT
>
> e.g.
>
> http://eagle.apache.org
>
> This does look to be at odds with the branding requirements but provided
> that the podling is following other requirements e.g. clear use of
> Incubating in the name, incubation disclaimer etc I don't see that the
> IPMC necessarily needs to continue enforcing the subdomain requirement?
>
> Rob
>
> On 01/12/2015 07:21, "Sergio Fernández" <sergio.fernan...@redlink.co>
> wrote:
>
> >They used to have a redirects. But you' re right, looks like not
> >anymore...
> >So we should ask INFRA to get a 307 resolving the TLP domains.
> >
> >On Tue, Dec 1, 2015 at 5:46 AM, Marvin Humphrey <mar...@rectangular.com>
> >wrote:
> >
> >> Greets,
> >>
> >> It seems that podling websites are available at both these URL patterns:
> >>
> >>   http://podling.incubator.apache.org
> >>   http://podling.apache.org
> >>
> >> See for example:
> >>
> >>   http://systemml.apache.org/
> >>   http://systemml.incubator.apache.org/
> >>   http://mynewt.apache.org/
> >>   http://mynewt.incubator.apache.org/
> >>
> >> I believe that resolving podling.apache.org is a mistake based on the
> >> following pages:
> >>
> >>   http://incubator.apache.org/guides/sites
> >>   http://incubator.apache.org/guides/branding
> >>
> >> Shall we ask Infra to install 302 redirects?
> >>
> >> Marvin Humphrey
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> >
> >--
> >Sergio Fernández
> >Partner Technology Manager
> >Redlink GmbH
> >m: +43 6602747925
> >e: sergio.fernan...@redlink.co
> >w: http://redlink.co
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Websites at podling.apache.org

[Sergio Fernández]

They used to have a redirects. But you' re right, looks like not anymore...
So we should ask INFRA to get a 307 resolving the TLP domains.

On Tue, Dec 1, 2015 at 5:46 AM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> Greets,
>
> It seems that podling websites are available at both these URL patterns:
>
>   http://podling.incubator.apache.org
>   http://podling.apache.org
>
> See for example:
>
>   http://systemml.apache.org/
>   http://systemml.incubator.apache.org/
>   http://mynewt.apache.org/
>   http://mynewt.incubator.apache.org/
>
> I believe that resolving podling.apache.org is a mistake based on the
> following pages:
>
>   http://incubator.apache.org/guides/sites
>   http://incubator.apache.org/guides/branding
>
> Shall we ask Infra to install 302 redirects?
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept S2Graph into Apache Incubation

[Sergio Fernández]

sing to enter incubation at Apache in order to help
> >efforts to diversify the committer-base, not so much to capitalize on
> >the Apache brand. The S2Graph project is in production use already
> >inside Kakao, but is not expected to be a Kakao product for external
> >customers. As such, the S2Graph project is not seeking to use the
> >Apache brand as a marketing tool.
> >
> >== Documentation ==
> >Information about S2Graph can be found at
> >https://github.com/kakao/s2graph. The following links provide more
> >information about S2Graph in open source:
> > * S2Graph web site: https://steamshon.gitbooks.io/s2graph-book/content/
> > * Codebase at Github: https://github.com/kakao/s2graph
> > * Issue Tracking: https://github.com/kakao/s2graph/issues
> > * User community: https://groups.google.com/forum/#!forum/s2graph
> >
> >== Initial Source ==
> >
> >The S2Graph codebase is currently hosted on Github:
> >https://github.com/kakao/s2graph.
> >
> >=== Source and Intellectual Property Submission Plan ===
> >
> >Currently, the S2Graph codebase is distributed under the Apache 2.0
> >License.
> >
> >== External Dependencies ==
> >
> >Beyond relying on Apache HBase, S2Graph has the following external
> >dependencies:
> > * Asynchbase (BSD)
> > * Play Framework (Apache 2.0 license)
> > * Scala (http://www.scala-lang.org/license.html)
> > * Spark (Apache 2.0 license)
> > * Kafka (Apache 2.0 license)
> >
> >== Required Resources ==
> >
> >=== Mailing list ===
> >
> >We will migrate our mailing lists to the following:
> > * us...@s2graph.incubator.apache.org
> > * d...@s2graph.incubator.apache.org
> > * priv...@s2graph.incubator.apache.org
> > * comm...@s2graph.incubator.apache.org
> >
> >=== Source control ===
> >
> >The S2Graph team would like to use Git for source code control, due to
> >our current use of Git. We request a writeable Git repo for S2Graph,
> >and mirroring to be set up to Github through INFRA.
> >
> >=== Issue Tracking ===
> >
> >S2Graph currently uses the github issue tracking system associated
> >with its github repo (https://github.com/kakao/s2graph/issues). We
> >will migrate to the Apache JIRA
> >(http://issues.apache.org/jira/browse/S2Graph).
> >
> >=== Other Resources ===
> >
> > * Jenkins/Hudson for builds and test running.
> > * Wiki for documentation purposes.
> > * Blog to improve project dissemination.
> >
> >== Initial Committers ==
> >
> > * Doyung Yoon 
> > * Daewon Jeong 
> > * Jaesang Kim 
> > * Hwansung Yu 
> > * Min-Seok Kim 
> > * Chul Kang 
> > * Luke Han 
> > * Alexander Bezzubov 
> >
> >== Affiliations ==
> >
> > * Doyung Yoon, Kakao
> > * Daewon Jeong, Kakao
> > * Jaesang Kim, Kakao
> > * Hwansung Yu, Kakao
> > * Min-Seok Kim, Kakao
> > * Chul Kang, Kakao,
> > * Luke Han, Ebay Inc.
> > * Alexander Bezzubov, NFLabs
> >
> >== Sponsors ==
> >
> >=== Champion ===
> >Hyunsik Choi
> >
> >=== Nominated Mentors ===
> > * Andrew Purtell - Apache Member, Salesforce
> > * Sergio Fernández - Apache Member, Redlink
> > * Hyunsik Choi - Apache Member, Gruter Inc.
> > * Seetharam Venkatesh - IPMC, Hortonworks Inc.
> >
> >=== Sponsoring Entity ===
> >
> > * The Apache Incubator
> >
> >-
> >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
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] TinkerPop 3.1.0-incubating Release

[Sergio Fernández]

+1 (binding)

So far I've checked in the source release: signatures and digests, source
releases file layouts, matched git tags and commit ids, incubator suffix
and disclaimer, build sources in a clean environment (oracle java
8u66+8u65arm-1~webupd8~1 on debian 64bits).

I think Justin already spotted something similar, anyway I want to assert
two minor comments about the LICENSE file:

* There is no need to include ALv2 software in your LICENSE file.
* Most of the stuff there should actually go in the NOTICE file.



On Fri, Nov 20, 2015 at 10:54 AM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> Hello,
> We are happy to announce that TinkerPop 3.1.0-incubating is ready for
> release.
>
> The release artifacts can be found at this location:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.1.0-incubating/
>
> The source distribution is provided by:
> apache-tinkerpop-3.1.0-incubating-src.zip
>
> Two binary distributions are provided for user convenience:
> apache-gremlin-console-3.1.0-incubating-bin.zip
> apache-gremlin-server-3.1.0-incubating-bin.zip
>
> The GPG key used to sign the release artifacts is available at:
> https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/KEYS
>
> The online docs can be found here:
> http://tinkerpop.incubator.apache.org/docs/3.1.0-incubating/ (user
> docs)
>
>
> http://tinkerpop.incubator.apache.org/docs/3.1.0-incubating/upgrade.html#_tinkerpop_3_1_0
> (upgrade docs)
> http://tinkerpop.incubator.apache.org/javadocs/3.1.0-incubating/core/
> (core javadoc)
> http://tinkerpop.incubator.apache.org/javadocs/3.1.0-incubating/full/
> (full javadoc)
>
> The tag in Apache Git can be found here:
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=310d0cda0c5ac83f47d173aaa4cf2ec51a47e636
>
> The release notes are available here:
>
>
> https://github.com/apache/incubator-tinkerpop/blob/3.1.0-incubating/CHANGELOG.asciidoc#tinkerpop-310-release-date-november-16-2015
>
> Finally, the dev@tinkerpop [VOTE] thread can be found at this location:
>
> https://pony-poc.apache.org/thread.html/Zea70rxds8l66xj
>
> Result summary: +14 (4 binding, 10 non-binding), 0 (0), -1 (0)
>
> The [VOTE] will be open for the next 72 hours --- closing Monday (November
> 23, 2015) at 5:00am EST.
>
> Thanks,
>
> Stephen
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Retire Corinthia

[Sergio Fernández]

+1 (binding)
On Nov 16, 2015 03:01, "Marvin Humphrey"  wrote:

> Greetings,
>
> The Corinthia community has voted to retire:
>
>   http://s.apache.org/odN
>
> This is a vote of the IPMC to confirm the decision to retire the podling.
>
> [ ] +1 to retire Corinthia from the Incubator
> [ ] -1 to keep Corinthia in the Incubator
>
> This vote will be held open for at least 72 hours.
>
> Should this vote pass, I have volunteered to assist Corinthia with
> retirement,
> as I am assisting Droids and Kalumet.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Apache Metrics, Not Apache Humans

[Sergio Fernández]

Marko, the metrics approach has been discussed in the past, for instance
http://markmail.org/message/ubx3utli3bnltv75 So far my feeling is that the
ASF prefer to deliver of people to build an opinion of projects rather than
based them on pure statistical metrics. But I'd be happy to see something
like that.
Hi,

I was talking with Daniel Gruno and wrote the following ideas to him. Note
that these are just ideas and not based on any real momentary issue or
concern -- though a more general concern about how Apache should evolve.

Apache should NOT use a binary "podling" / "top-level" model. All projects
should simply have a "health score" and that health score is derived from
measurables. Because of Apache Infrastructure's centralized server model
(email lists, version control, distributions, homepages, etc.), it  has the
ability to gather metrics such as, for example, the distribution of pushes
to the repository, the branch factor of the mailing list, the centrality of
the project in the Central Maven repository dependency graph, the number of
non-sequisters (dead-end conversations) in the email chain, the length of
discussions in JIRA, etc. etc. Which metrics are important? Who care --
just make up things to glean from the wealth of information you already
have access to. Watch...

Next, the Apache members subjectively say which projects they think are
"good" (healthy). This can even be a global vote including everyone in the
world and (should be) dynamic over time as projects evolve with time.
Either way, lets say, the ranking says Apache Hadoop, Apache Solr, Apache
Commons, etc. are the (collective subjective's) "best" Apache projects.
Now, there should exist a multi-dimensional projection of the
aforementioned gleaned statistics what will have Hadoop, Solr, Commons,
etc. close to one another in metric-space (clustered). Likewise, low
ranking projects should be close to one another in this space and far from
Hadoop, Solr, Commons, etc. Find that projection and that is your "healthy
metric space."

>From here, all Apache projects have a computed "healthy" score(s) and when
users go to download, lets say, Lucene, they go: "Cool. This is a healthy
project." (it has a HEALTH.txt file distributed with it, lets say). What
that means is that Lucene, at that release was in the "healthy" cluster of
the metric space. This model has various benefits:

1. There is no need to have philosophical arguments (not grounded
in measurables) about what rules a project should follow (bounded by law).
- Perhaps a project that is exclusive, but is X is still in
the "healthy" subspace.
- Perhaps having bad documentation is a "unhealthy" even
though Apache doesn't care about documentation.
- Perhaps too much discussion causes a project to become
"unhealthy."
- Perhaps … who knows? … let the statistics do the talking.
-  Apache becomes a breeding ground for different models of
open source (bounded by law), not just "The Apache Way."
- And these models are measurable! Let us study the
act of open source.
2. "Top-level" projects can fall from grace.
- Currently, all "top-level" projects are "equal." This
should by dynamic as the mighty do fall.
- It is possible for what are now "podlings" to be
"healthy" as they simply are coming into Apache.
- "The student is the master."
- Hadoop 1.2.1 might be the healthiest version of Hadoop
(as I tend to believe). "Hadoop" is not a thing eternal.
3. Less work for people.
- No more VOTEing on graduation.
- No more amorphous aesthetic arguments about "The Apache
Way."
- No more long winded contradictory documentation about how
things should be done (bounded by law).

The Apache Way should be about metrics, not about philosophy as different
paths lead to the same mountain top <--- See! Is that random Buddhist
saying that everyone just "believes" even true? :) Get the human out of the
loop!

Thanks for reading,
Marko.

http://markorodriguez.com

P.S. The same should hold true for educational degrees. I graduate and now
forever I'm an expert in computers? Medical doctors too! A 90 year old
doctor can do surgery on me?!?!… Binary graduation is not "real." Metrics,
metrics, metrics --- we live in a world where this is possible. For every
"thing" good comes and goes, up and down…

Re: [DISCUSS] S2Graph Incubator Proposal

[Sergio Fernández]

Definitely the first priority for S2Graph incubation would be to grow the
real community out of Kakao.

On Thu, Nov 12, 2015 at 2:47 AM, Hyunsik Choi <hyun...@apache.org> wrote:

> Hi Luke,
>
> Thank you for your interest in S2Graph project. If you don't mind,
> we'd like to add you to the initial committer list. I think that your
> experience and skills about HBase would be very helpful to S2Graph
> project.
>
> Best regards,
> Hyunsik
>
> On Mon, Nov 9, 2015 at 6:58 PM, Luke Han <luke...@gmail.com> wrote:
> > I'm very interesting about this project, would love to help but I'm not
> > IPMC member.
> >
> > Please let me know if there's anything I could help on.
> >
> > Thanks.
> >
> >
> > Best Regards!
> > -
> >
> > Luke Han
> >
> > On Tue, Nov 10, 2015 at 9:03 AM, Hyunsik Choi <hyun...@apache.org>
> wrote:
> >
> >> Hi Seetharam,
> >>
> >> Thank you for your volunteering! I've added your name to the mentor
> list.
> >>
> >> I also updated the initial committer list and affiliations via google
> >> search.
> >> If I wrote wrong affiliations, please let me know.
> >>
> >> Best regards,
> >> Hyunsik
> >>
> >>
> >> On Mon, Nov 9, 2015 at 4:21 PM, Seetharam Venkatesh
> >> <venkat...@innerzeal.com> wrote:
> >> > Hi Hyunsik,
> >> >
> >> > If you are still looking for mentors, let me volunteer as one.
> >> >
> >> > Thanks!
> >> >
> >> > On Mon, Nov 9, 2015 at 3:45 PM Hyunsik Choi <hyun...@apache.org>
> wrote:
> >> >
> >> >> Thank you all guys  I just put you names on the nominated mentor
> list.
> >> >>
> >> >> @Andrew,
> >> >>
> >> >> I agree with you. S2Graph already has good relationships with other
> >> >> ASF projects, such as HBase and Spark,  In addition, they have a plan
> >> >> to expand its relationship to Apache incubator TinkerPop, which is a
> >> >> graph computing framework. I'm looking forward to their combinations.
> >> >>
> >> >> @Sergio,
> >> >>
> >> >> Thank you for attending the talk and joining the S2Graph mentors.
> That
> >> >> was Doyung Yoon, one of the S2Graph creators. He had a talk at the
> >> >> last ApacheCon.
> >> >>
> >> >> On Mon, Nov 9, 2015 at 11:58 AM, Sergio Fernández <wik...@apache.org
> >
> >> >> wrote:
> >> >> > Hi Hyunsik, I attended your talk at the last ApacheCon, and I
> think S2
> >> >> has
> >> >> > quite some potential. So if you need a mentor, count me in!
> >> >> >
> >> >> > On Mon, Nov 9, 2015 at 7:54 PM, Hyunsik Choi <hyun...@apache.org>
> >> wrote:
> >> >> >
> >> >> >> This project is looking for mentors. Anyone can help? We are also
> >> >> >> looking forward to any feedback.
> >> >> >>
> >> >> >> Also, I attached the proposal here. I forgot it.
> >> >> >>
> >> >> >> 
> >> >> >>
> >> >> >> = S2Graph Proposal =
> >> >> >>
> >> >> >> == Abstract ==
> >> >> >> S2Graph is a distributed and scalable OLTP graph database built on
> >> >> >> HBase to support fast traversal on extremely large graph.
> >> >> >>
> >> >> >> Here are additional materials to introduce S2Graph.
> >> >> >>  * HBaseCon 2015 -
> >> >> http://www.slideshare.net/HBaseCon/use-cases-session-5
> >> >> >>  * Apache: Big Data 2015 -
> >> >> >>
> >> http://schd.ws/hosted_files/apachebigdata2015/06/s2graph_apache_con.pdf
> >> >> >>
> >> >> >> == Proposal ==
> >> >> >> S2Graph is to provide a scalable distributed graph database engine
> >> >> >> over key/value storage such as HBase. S2Graph provide fully
> >> >> >> ashynchronous API to manupulate data as property graph model and
> fast
> >> >> >> breadth first search query on graph.
> >> >> >>
> >> >> >> == Background ==
> >> >> >> S2Graph initially started as an internal project at Kakao.com t

Re: [DISCUSS] S2Graph Incubator Proposal

[Sergio Fernández]

 would like to use Git for source control, due to our
> current use of Git. We request a writeable Git repo for S2Graph, and
> mirroring to be set up to Github through INFRA.
>
> === Issue Tracking ===
>
> S2Graph currently uses the github issue tracking system associated
> with its github repo: https://github.com/kakao/s2graph/issues. We will
> migrate to the Apache JIRA:
> http://issues.apache.org/jira/browse/S2Graph
>
> === Other Resources ===
>
> Jenkins/Hudson for builds and test running.
> Wiki for documentation purposes
> Blog to improve project dissemination
>
> == Initial Committers ==
>
>  * Doyung Yoon 
>  * Daewon Jeong 
>  * Jaesang Kim 
>  * Hwansung Yu 
>  * Min-Seok Kim 
>  * Chul Kang 
>
> == Affiliations ==
>
> The initial committers are from one organizations: Kakao.
>  * Doyung Yoon, Kakao
>  * Daewon Jeong, Kakao
>  * Jaesang Kim, Kakao
>  * Hwansung Yu, Kakao
>  * Min-Seok Kim, Kakao
>  * Chul Kang, Kakao
>
> == Sponsors ==
>
> === Champion ===
> Hyunsik Choi
>
> === Nominated Mentors ===
>
> === Sponsoring Entity ===
>
>  * The Apache Incubator
>
> On Fri, Nov 6, 2015 at 4:05 PM, Hyunsik Choi <hyun...@apache.org> wrote:
> > Hi Seetharam,
> >
> > Thank you for a good question. That seem to be a frequent question to
> > this project.
> >
> > Here is the answer to your question.
> >
> https://steamshon.gitbooks.io/s2graph-book/content/what_is_different_to_titan.html
> >
> > I hope that this link is helpful to your understanding.
> >
> > Best regards,
> > Hyunsik
> >
> >
> >
> > On Fri, Nov 6, 2015 at 3:07 PM, Seetharam Venkatesh
> > <venkat...@innerzeal.com> wrote:
> >> Hi Hyunsik,
> >>
> >> The proposal looks interesting and want to know how is this different
> from
> >> existing solutions in the same space such as Titan, etc.
> >>
> >> Thanks!
> >> Venkatesh
> >>
> >>
> >> On Fri, Nov 6, 2015 at 1:36 PM Hyunsik Choi <hyun...@apache.org> wrote:
> >>
> >>> Hi folks,
> >>>
> >>> We would like to start a discussion on S2Graph as an incubation
> project.
> >>>
> >>> S2Graph is a distributed and scalable OLTP graph database built on
> >>> HBase. It provides interactive queries for vertex/edge/sub-graphs on
> >>> extremely large graph data sets as well as insertion and update
> >>> operations.
> >>>
> >>> S2Graph was already introduced in Apache BigData and HBaseCon this
> year.
> >>>
> >>> The proposal is available at :
> >>> https://wiki.apache.org/incubator/S2GraphProposal
> >>>
> >>> We are looking forward to any feedback. In addition, we are looking
> >>> for volunteers as mentors.
> >>>
> >>> Best regards,
> >>> Hyunsik
> >>>
> >>> -
> >>> 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
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Graduate Groovy from the Incubator

[Sergio Fernández]

+1 (binding)

good luck, guys!

On Wed, Oct 28, 2015 at 9:26 PM, Konstantin Boudnik <c...@apache.org> wrote:

> Following discussions [1] about its current status, the Groovy community
> has voted [2] to graduate from the Incubator. The vote passed [3] with 12
> +1s
> total, 5 are binding:
>
> Guillaume Laforge
> Cédric Champeau
> Paul King
> Jochen Theodorou
> Pascal Schumacher
> Emmanuel Lécharny (binding)
> Bertrand Delacretaz (binding)
> Andrew Bayer (binding)
> Jim Jagielski (binding)
> Konstantin Boudnik (binding)
> Russel Winder
> Guillaume Alleon
>
> The Groovy community has:
> * completed all required paperwork:
> https://incubator.apache.org/projects/groovy.html
> * completed multiple releases (2.4.4, 2.4.5, 2.4.6 is in the works)
> * completed the name check procedure:
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-88
> * addressed 50+ JIRAs:
> http://is.gd/1tACON
> * voted in multiple new committers/PPMC members
>
> Therefore, I'm calling a VOTE to graduate Groovy with the following Board
> resolution. The VOTE will run for at least 72 hours, ending
> Saturday, October 31st 8 PM PST.
>
> [ ] +1 Graduate Apache Groovy from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Groovy from the Incubator because ...
>
> Regards,
> Cos
>
> [1] http://is.gd/DX41lO
> [2] http://is.gd/pPweq3
> [3] http://is.gd/VTLiqO
>
>  Apache Groovy graduation resolution draft
>
> Establish the Apache Groovy Top-Level 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 evolution
> and maintenance of the Groovy programming language,
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Groovy Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Groovy Project be and hereby is responsible
> for the evolution and maintenance of the Groovy programming language;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache Groovy" 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 Groovy
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Groovy
> 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 Groovy Project
> PMC:
>
> Cédric Champeau <cedric.champ...@gmail.com>
> Paul King <pa...@asert.com.au>
> Guillaume Laforge <glafo...@gmail.com>
> Pascal Schumacher <pascalschumac...@gmx.net>
> Jochen Theodorou <blackd...@gmx.org>
> Andrew Bayer <andrew.ba...@gmail.com>
> Konstantin Boudnik <c...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Guillaume Laforge be
> appointed to the office of Vice President, Apache Groovy, 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 Apache Groovy Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Groovy
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Groovy podling encumbered upon the Apache Incubator Project are
> hereafter discharged.
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] TinkerPop 3.0.2-incubating Release

[Sergio Fernández]

+1 (binding)

On Mon, Oct 26, 2015 at 3:47 PM, Rich Bowen <rbo...@rcbowen.com> wrote:

> +1, binding, mentor
> On Oct 23, 2015 9:07 PM, "Stephen Mallette" <spmalle...@gmail.com> wrote:
>
> > Hello,
> > We are happy to announce that TinkerPop 3.0.2-incubating is ready for
> > release.
> >
> > The release artifacts can be found at this location:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.0.2-incubating/
> >
> > The source distribution is provided by:
> > apache-tinkerpop-3.0.2-incubating-source-release.zip
> >
> > Two binary distributions are provided for user convenience:
> > apache-gremlin-console-3.0.2-incubating-distribution.zip
> > apache-gremlin-server-3.0.2-incubating-distribution.zip
> >
> > The GPG key used to sign the release artifacts is available at:
> > https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/KEYS
> >
> > The online docs can be found here:
> > http://tinkerpop.incubator.apache.org/docs/3.0.2-incubating/ (user
> > docs)
> >
> >
> http://tinkerpop.incubator.apache.org/docs/3.0.2-incubating/upgrade.html#_tinkerpop_3_0_2
> > (upgrade docs)
> >
> http://tinkerpop.incubator.apache.org/javadocs/3.0.2-incubating/core/
> > (core javadoc)
> >
> http://tinkerpop.incubator.apache.org/javadocs/3.0.2-incubating/full/
> > (full javadoc)
> >
> > The tag in Apache Git can be found here:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=8e9af13d6beb184a137067caa0445157351435ab
> >
> > The release notes are available here:
> >
> >
> https://github.com/apache/incubator-tinkerpop/blob/3.0.2-incubating/CHANGELOG.asciidoc#tinkerpop-302-release-date-october-19-2015
> >
> > Finally, the dev@tinkerpop [VOTE] thread can be found at this location:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201510.mbox/%3CCAA-H439qBNzu1gO7P0m%2BeUQ4OZyPU9Ya2D1icTEftd3fpzNvrA%40mail.gmail.com%3E
> >
> > Result summary: +14 (4 binding, 10 non-binding), 0 (0), -1 (0)
> >
> > The [VOTE] will be open for the next 72 hours --- closing Monday
> > (October 26, 2015) at 8am EST.
> >
> > Thanks,
> >
> > Stephen
> >
> > P.S. Hopefully we were able to get LICENSE/NOTICE solid on this
> > release.  Justin Mclean I hope you get a chance to verify and vote as
> > you usually seem to do.
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Concerted into the Apache Incubator

[Sergio Fernández]

aphy =
>
> N/A
>
> = Required Resources =
> == Mailling List ==
>  *priv...@concerted.incubator.apache.org (moderated subscriptions)
>  *comm...@concerted.incubator.apache.org
>  *d...@concerted.incubator.apache.org
>  *iss...@concerted.incubator.apache.org
>
> == Git Repository ==
>
> https://git-wip-us.apache.org/repos/asf/incubator-concerted.git
>
> == Issue Tracking ==
> Jira Concerted (CONCERTED)
>
> == Other Resources ==
>  * Continuous Integration
>   * Jenkins
>  * Wiki
>   * cwiki.apache.org/confluence/display/CONCERTED
>
> = Initial Committers =
>  * Roman Shaposhnik 
>  * Daniel Dai 
>  * Jake Farrell 
>  * Lars Hofhansl 
>  * Julian Hyde 
>  * Chris Nauroth 
>  * Pavel Stehule 
>  * Amrish 
>  * Nupur S 
>  * Atri Sharma 
>  * Nishith Singhal 
>  * Michael Down 
>  * Vijayakumar Ramdoss 
>  * Wang Albert 
>  * Hans-Jurgen Schonig 
>  * Kris Popat 
>  * Ayrton Gomesz 
>
> = Affiliations =
>  * Roman Shaposhnik (Pivotal)
>  * Daniel Dai (HortonWorks)
>  * Jake Farrell (Acquia)
>  * Lars Hofhansl (Salesforce)
>  * Julian Hyde (HortonWorks)
>  * Chris Nauroth (HortonWorks)
>  * Pavel Stehule (GoodData)
>  * Amrish (Ingenium Data Systems)
>  * Nupur S (Ingenium Data Systems)
>  * Atri Sharma (Barclays)
>  * Nishith Singhal (Wipro)
>  * Michael Down (Barclays)
>  * Vijayakumar Ramdoss (EMC)
>  * Wang Albert (Lehigh University)
>  * Hans- Jurgen Schonig (CyberTec)
>  * Kris Popat (CETIS LLP)
>  * Ayrton Gomesz (IQLabs)
>
> The nominated mentors are employees of HortonWorks, Acquia, and Salesforce.
>
>  * Daniel Dai (HortonWorks)
>  * Jake Farrell (Acquia)
>  * Lars Hofhansl (Salesforce)
>  * Julian Hyde (HortonWorks)
>  * Chris Nauroth (HortonWorks)
>
> = Sponsors =
>
> == Champion ==
>
>  * Roman Shaposhnik (rvs AT apache DOT org)
>
> == Nominated Mentors ==
>
>  * Daniel Dai 
>  * Jake Farrell 
>  * Lars Hofhansl 
>  * Julian Hyde 
>  * Chris Nauroth 
>
> == Sponsoring Entity ==
> Apache Incubator
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Concerted Proposal

[Sergio Fernández]

I just wanted to state the fact that mentoring is not expected to take an
active role in technical questions. Moreover arguing that "bootstrapping
the existing code base and community into ASF will generate much more
interest" clearly shows an excessive fascination with the Apache brand. In
the end you have to take into account that been a podling introduces quite
some overhead, which personally I don't find healthy in such very early
stage.

But well, looks the proposal has enough support, so my opinion is just
that, an individual opinion. Go ahead with the proposal, and all the best!


On Mon, Oct 5, 2015 at 10:51 AM, <nup...@ingeniumsys.com> wrote:

> As a member of Concerted community, I believe that acceptance into ASF
> Incubator is beneficial for Concerted especially in terms of community
> support. Being an independent project on github really does not help when
> we want to build a healthy community of people interested in Concerted and
> aiming to take Concerted to ultimate goal we have i.e. being the primary in
> memory support framework for big data engines. I really feel that
> bootstrapping the existing code base and community into ASF will generate
> much more interest, visibility and allow the community to be regulated in a
> much better manner.
>
> Also, I agree with Atri on the fact that since our eventual goal is to be
> supporting existing big data projects, working with them early on is a
> great way to improve our roadmap and get contributions from those projects.
>
> As a person who has been revamping Concerted code base for a while now, I
> believe that the existing code base is a great place to pick up the main
> development of Concerted.
>
> Nupur
>
>
> On 05/10/2015 02:09 PM, Atri Sharma wrote:
>
>> While I do not disagree with the fact that the code base can evolve at
>> github, the situation here is a bit different. Preliminary though it is,
>> Concerted does have an existing code base. The bigger question is having
>> the code base evolve at a higher frequency with a wider community.
>>
>> I think that if Concerted becomes a part of ASF Incubator, it has a much
>> higher chance of evolving into a wider product with a much better
>> alignment
>> with the existing Apache big data ecosystem. Concerted provides the
>> ability
>> to DIY big data in memory support engines, with a high degree of custom
>> building for each user project.
>>
>> The reason why Concerted is proposed to become part of ASF Incubator is
>> that Concerted is a small project right now, with a roadmap and a set of
>> developers. Getting into ASF allows the Concerted project to have much
>> better visibility with existing big data projects, which will then allow
>> Concerted to be developed with more goals in mind. Please note that
>> eventual goal of Concerted is to be supporting existing big data engines
>> with on demand custom in memory support. Since the primary target is
>> Apache
>> big data space, I think it makes sense to be bootstrapping into ASF early
>> on.
>>
>> Second, ASF will allow Concerted to have better community support and
>> management. As mentioned earlier, visibility and integration with other
>> ASF
>> projects will allow those projects to contribute to Concerted if they want
>> to mold it. Also, being a part of ASF anyways helps build community and
>> manage it in a much better manner.
>>
>> I think Roman put it aptly when he mentioned Apache Drill. I think Apache
>> Drill came to ASF Incubator with a goal and a community, and Concerted
>> comes with the same goal. We already have a small community of active
>> people, and who are excited at prospect of joining the Incubator.
>>
>> Please also note that Concerted does not aim to become a large project
>> like
>> Apache Spark (although that might change with time). Community current
>> aims
>> are to become a lightweight in memory support engine building framework,
>> with a small but well managed community and code base. So, the existing
>> code base might actually be a great starting point for us to be
>> bootstrapped into ASF Incubator, build community and build the existing
>> framework into a much more mature project dedicated at supporting ASF big
>> data projects.
>>
>> Thoughts?
>>
>> Regards,
>>
>> Atri
>>
>> On Mon, Oct 5, 2015 at 1:39 PM, Sergio Fernández <wik...@apache.org>
>> wrote:
>>
>> Well, I think what we should ask ourselves is if this is actually the role
>>> of ASF incubation. FMPOV the project will evolve much easier at github,
>>> and
>>> once the code base

Re: Concerted Proposal

[Sergio Fernández]

Well, I think what we should ask ourselves is if this is actually the role
of ASF incubation. FMPOV the project will evolve much easier at github, and
once the code base becomes a reality we can help mentoring the project in
the Apache way. But this is just my personal opinion.

On Mon, Oct 5, 2015 at 8:18 AM, Ted Dunning <ted.dunn...@gmail.com> wrote:

> It looks like there is plenty of mentor-power left on the project. I don't
> see why one mentor dropping out from a good and large group is a problem.
>
> On Sun, Oct 4, 2015 at 8:08 AM, Roman Shaposhnik <r...@apache.org> wrote:
>
> > Hi!
> >
> > as some of you know, Atri and I have been
> > discussing his Concerted Proposal lately:
> >https://wiki.apache.org/incubator/ConcertedProposal
> >
> > At this point I can no longer offer my mentorship
> > services (I ended up quite overloaded as it is)
> > and I feel it is only fair to Atri if I ask for help here.
> >
> > Consider this thread a pre-DICUSS. Concerted isn't
> > what most of the Incubator proposals are these days.
> > It is much more about promise of technology rather
> > than something that exists today. In this it reminds
> > me of Drill a great deal when it just got proposed -- mostly
> > and idea. Not much of an existing code base or product.
> >
> > So I guess what I'm asking is an IPMC opinion on
> > how to proceed with this given the mentor situation
> > and the state of technology.
> >
> > Please help by chiming in.
> >
> > Thanks,
> > Roman.
> >
> > ---------
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache Groovy 2.4.5-incubating

[Sergio Fernández]

+1 (binding)

On Sun, Sep 20, 2015 at 12:20 PM, Cédric Champeau <cchamp...@apache.org>
wrote:

> Hi all!
>
> The Apache Groovy PPMC has successfully voted the release of Apache Groovy
> 2.4.5-incubating [1], with 4 "+1" binding votes, one "+1" non binding and
> no 0/-1 votes. We are now asking the IPMC to vote it too.
>
> This release was done in a particular context, at the SpringOne2GX
> conference. Following a very successful BOF session, we followed up with a
> release initiation party to share the knowledge about how to perform a
> release! We anticipate this will make it easier for more of us to be
> involved with releases in the future. It's worth noting that the release
> was performed with the presence of Baruch Sadogursky from JFrog
> (Artifactory/Bintray) that we use, and he could already suggest some nice
> improvements in our release process that we're going to improve for the
> upcoming releases.
>
> Vote on dev list:
>
> http://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201509.mbox/%3CCADQzvmkCoEUFXfmSR%2B71K%2BEmSYHAjkFWa1HH76LEcPDLMNSYZQ%40mail.gmail.com%3E
> Result of vote on dev list:
>
> http://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201509.mbox/%3CCADQzvm%3DDzF-6T46crzuOBizG2wq0xPArfuz%3DQio_OwgQxEHEcw%40mail.gmail.com%3E
>
> This release fixes documentation issues, a potential memory leak when
> loading the Groovy runtime from different classloaders, some JSON fixes and
> improvements and numerous small bug fixes.
>
> The changelog for this release can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12332749
>
> Tag:
>
> https://git1-us-west.apache.org/repos/asf?p=incubator-groovy.git;a=commit;h=13934972b400d40600c994377308b26978fcc325
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/groovy/
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/groovy/KEYS
> Vote is open for at least 72 hours. Artifacts will be moved to dist as soon
> as the vote passes.
>
> [ ] +1, release Apache Groovy 2.4.5-incubating
> [ ] 0, I don't care
> [ ] -1, because...
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache htrace-4.0.0-incubating

[Sergio Fernández]

+1 (binding)

On Thu, Sep 10, 2015 at 1:45 AM, Colin P. McCabe <cmcc...@apache.org> wrote:

> Apache HTrace (incubating), has voted to release the below referenced
> Apache HTrace 4.0.0-incubating release candidate.
>
> Dear IPMC, please vote on our second release candidate as an Apache
> Incubator project.
>
> The source tarball, hashes, and signing are here:
> http://people.apache.org/~cmccabe/htrace/releases/4.0.0/rc0/
>
> Related maven artifacts are posted here:
> https://repository.apache.org/content/repositories/orgapachehtrace-1017
>
> The tag for the RC is here:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=commit;h=8cf1e01967f2ad10f7c6d5d099b724c520613a7d
>
> The KEYS file with the key used signing is available here:
> https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
>
> 60 issues were resolved in this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315924=12333022
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache HTrace 4.0.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> best,
> Colin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Release Apache NiFi 0.2.0-incubating

[Sergio Fernández]

+1 (binding), where so far I've checked:

* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* build sources in a clean environment (openjdk7, maven 3, debian 64bits)

As Justin commented, is preferable to use the distribution area for both rc
and releases, nothing blocker anyway.

Good luck for the next release as TLP!


On Mon, Jul 13, 2015 at 3:44 PM, Matt Gilman matt.c.gil...@gmail.com
wrote:

 Hello

 The Apache NiFi PPMC has voted to release Apache NiFi 0.2.0-incubating. The
 vote was based on the release candidate and thread described below. We now
 request the IPMC to vote on this release.

 Here is the PPMC voting result:
 0 +1 (IPMC binding) - IPMC we need your help to reach the requisite 3
 binding votes.
 4 +1 (PPMC non-binding)
 3 +1 (non-binding)
 0  0
 0 -1

 Here is the PPMC vote thread: http://s.apache.org/BcG

 The source zip, including signatures, digests, etc. can be found at:
 https://repository.apache.org/content/repositories/orgapachenifi-1057/

 The Git tag is nifi-0.2.0-incubating-RC1
 The Git commit ID is e4f51eac9d1b9eabbb091a9f2c3eb1fee453cfc6

 https://git1-us-west.apache.org/repos/asf/incubator-nifi/repo?p=incubator-nifi.git;a=commit;h=e4f51eac9d1b9eabbb091a9f2c3eb1fee453cfc6

 Checksums of nifi-0.2.0-incubating-source-release.zip:
 MD5: 22301dc8d9006f73b0fb7aef395e6b92
 SHA1: 1ed4c892d98c059865610fcb5140093c5b4e

 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/mcgilman.asc

 KEYS file available here:
 https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS

 110 issues were closed/resolved for this release:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12332286

 The vote will be open for 72 hours.
 Please download the release candidate and evaluate the necessary items
 including checking hashes, signatures, build from source, and test.  Then
 please vote:

 [ ] +1 Release this package as nifi-0.2.0-incubating
 [ ] +0 no opinion
 [ ] -1 Do not release this package because...




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co