Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[Justin Mclean]

HI,

+1 binding

I checked: 
- artefact has incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE correct
- No unexpected binaries in source
- All source file have Apache headers
- Can compile from source

Thanks,
Justin

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

RE: [VOTE] Graduate REEF

[Ross Gardler]

+1


-Original Message-
From: Chris Douglas [mailto:cdoug...@apache.org] 
Sent: Monday, November 9, 2015 1:47 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Graduate REEF

+1 -C

On Mon, Nov 9, 2015 at 1:14 PM, Markus Weimer  wrote:
> This is the vote to decide if Apache REEF should graduate from the 
> Incubator. Please see the proposed resolution below.
>
> This proposal was discussed [0] and voted upon [1] by the REEF 
> community and has been discussed [2] on this list.
>
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache REEF from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache REEF from the Incubator because ...
>
> Thanks,
>
> Markus
>
> [0]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationdiscussion=01%7c01%7cRoss.Gardler%40micros
> oft.com%7c2e6348917e55482e1c7a08d2e94f66ae%7c72f988bf86f141af91ab2d7cd
> 011db47%7c1=FdjxiP5MGog%2fxYQI68swmKF3JZtkZt3dHa1TW8NM5qM%3d
> [1]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationppmsvoteresult=01%7c01%7cRoss.Gardler%40mi
> crosoft.com%7c2e6348917e55482e1c7a08d2e94f66ae%7c72f988bf86f141af91ab2
> d7cd011db47%7c1=uZ%2bpPsxnrf9voUVLJBzyKIb56hd3qOyf0Qr0dwJ6kXQ%3d
> [2]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationdiscussionongeneral=01%7c01%7cRoss.Gardler
> %40microsoft.com%7c2e6348917e55482e1c7a08d2e94f66ae%7c72f988bf86f141af
> 91ab2d7cd011db47%7c1=X%2f%2bpf6TfJkxgqAON1HZFEj7t3wsCiY7H5fyZM0V
> EeSI%3d
>
> 
> X. Establish the Apache REEF 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 application development on top of
> resource managers.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache REEF Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache REEF Project be and hereby is
> responsible for the creation and maintenance of a software
> framework for application development on top of resource
> managers; and be it further
>
> RESOLVED, that the office of "Vice President, Apache REEF"
> 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 REEF Project, and to have primary
> responsibility for management of the projects within the scope
> of responsibility of the Apache REEF 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 REEF Project Management Committee:
>
> * Markus Weimer 
> * Byung-Gon Chun 
> * Yunseong Lee 
> * Brian Cho 
> * Beysim Sezgin 
> * Yingda Chen 
> * Julia Wang 
> * Andrew Chung 
> * Youngseok Yang 
> * Gyewon Lee 
> * Taegeon Um 
> * Joo Seong Jeong 
> * Geon-Woo Kim 
> * Mariia Mykhailova 
> * Shravan M Narayanamurthy 
> * Dongjoon Hyun 
> * Sergiy Matusevych 
> * Tyson Condie 
> * Chris Mattman 
> * Chris Douglas 
> * Boris Shulman 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
> appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
> is tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache REEF Project; and be it further
>
> RESOLVED, that the initial Apache REEF Project be and hereby
> is tasked with the migration 

Re: [VOTE] Graduate REEF

[Jakob Homan]

+1 (binding).

On 9 November 2015 at 13:14, Markus Weimer  wrote:
> This is the vote to decide if Apache REEF should graduate from
> the Incubator. Please see the proposed resolution below.
>
> This proposal was discussed [0] and voted upon [1] by the REEF community
> and has been discussed [2] on this list.
>
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache REEF from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache REEF from the Incubator because ...
>
> Thanks,
>
> Markus
>
> [0]: http://s.apache.org/reefgraduationdiscussion
> [1]: http://s.apache.org/reefgraduationppmsvoteresult
> [2]: http://s.apache.org/reefgraduationdiscussionongeneral
>
> 
> X. Establish the Apache REEF 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 application development on top of
> resource managers.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache REEF Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache REEF Project be and hereby is
> responsible for the creation and maintenance of a software
> framework for application development on top of resource
> managers; and be it further
>
> RESOLVED, that the office of "Vice President, Apache REEF"
> 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 REEF Project, and to have primary
> responsibility for management of the projects within the scope
> of responsibility of the Apache REEF 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 REEF Project Management Committee:
>
> * Markus Weimer 
> * Byung-Gon Chun 
> * Yunseong Lee 
> * Brian Cho 
> * Beysim Sezgin 
> * Yingda Chen 
> * Julia Wang 
> * Andrew Chung 
> * Youngseok Yang 
> * Gyewon Lee 
> * Taegeon Um 
> * Joo Seong Jeong 
> * Geon-Woo Kim 
> * Mariia Mykhailova 
> * Shravan M Narayanamurthy 
> * Dongjoon Hyun 
> * Sergiy Matusevych 
> * Tyson Condie 
> * Chris Mattman 
> * Chris Douglas 
> * Boris Shulman 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
> appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
> is tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache REEF Project; and be it further
>
> RESOLVED, that the initial Apache REEF Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator REEF podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator REEF podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Graduate REEF

[Chris Douglas]

+1 -C

On Mon, Nov 9, 2015 at 1:14 PM, Markus Weimer  wrote:
> This is the vote to decide if Apache REEF should graduate from
> the Incubator. Please see the proposed resolution below.
>
> This proposal was discussed [0] and voted upon [1] by the REEF community
> and has been discussed [2] on this list.
>
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache REEF from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache REEF from the Incubator because ...
>
> Thanks,
>
> Markus
>
> [0]: http://s.apache.org/reefgraduationdiscussion
> [1]: http://s.apache.org/reefgraduationppmsvoteresult
> [2]: http://s.apache.org/reefgraduationdiscussionongeneral
>
> 
> X. Establish the Apache REEF 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 application development on top of
> resource managers.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache REEF Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache REEF Project be and hereby is
> responsible for the creation and maintenance of a software
> framework for application development on top of resource
> managers; and be it further
>
> RESOLVED, that the office of "Vice President, Apache REEF"
> 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 REEF Project, and to have primary
> responsibility for management of the projects within the scope
> of responsibility of the Apache REEF 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 REEF Project Management Committee:
>
> * Markus Weimer 
> * Byung-Gon Chun 
> * Yunseong Lee 
> * Brian Cho 
> * Beysim Sezgin 
> * Yingda Chen 
> * Julia Wang 
> * Andrew Chung 
> * Youngseok Yang 
> * Gyewon Lee 
> * Taegeon Um 
> * Joo Seong Jeong 
> * Geon-Woo Kim 
> * Mariia Mykhailova 
> * Shravan M Narayanamurthy 
> * Dongjoon Hyun 
> * Sergiy Matusevych 
> * Tyson Condie 
> * Chris Mattman 
> * Chris Douglas 
> * Boris Shulman 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
> appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
> is tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache REEF Project; and be it further
>
> RESOLVED, that the initial Apache REEF Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator REEF podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator REEF podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[Henry Saputra]

- Signature files look good
- Hash files look good
- LICENSE file looks good
- NOTICE file looks good
- DISCLAIMER files exists
- Source compiled successfully
- NO 3rd party executables in source artifact
- Source files has correct Apache header

+1 (binding)

On Sat, Nov 7, 2015 at 4:46 PM, ShaoFeng Shi  wrote:
> Hi all,
>
> The Apache Kylin community has voted on and approved a proposal to release
> Apache Kylin 1.1.1-incubating. This release only includes license cleanup,
> no Java code change; For more information please check KYLIN-999.
>
> Proposal:
> http://s.apache.org/kylin-1.1.1-vote_rc1
>
> Vote result:
> 7 binding +1 votes
> 9 non-binding +1 votes
> No -1 votes
> http://s.apache.org/kylin-1.1.1-result_rc1
>
>
> The commit to be voted upon:
> https://github.com/apache/incubator-kylin/commit/708ea38d7f764048e67e8e1ee8a13955983d12ba
>
> Its hash is 708ea38d7f764048e67e8e1ee8a13955983d12ba.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1.1-incubating-rc1/
>
> The hashes of the artifacts are as follows:
> apache-kylin-1.1.1-incubating-src.tar.gz.md5
> ff942b2eba870b04552bc8c8dace5517
> apache-kylin-1.1.1-incubating-src.tar.gz.sha1
> cc8990ba7821b02f4bf6da5f870b30a915881535
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachekylin-1013/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/shaofengshi.asc
>
> Pursuant to the Releases section of the Incubation Policy and with
> the endorsement of our mentors we would now like to request
> the permission of the Incubator PMC to publish the release. The vote
> is open for 72 hours, or until the necessary number of votes (3 +1)
> is reached.
>
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
>
> Shaofeng Shi, on behalf of Apache Kylin PPMC
> shaofeng...@apache.org

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

[VOTE] Graduate REEF

[Markus Weimer]

This is the vote to decide if Apache REEF should graduate from
the Incubator. Please see the proposed resolution below.

This proposal was discussed [0] and voted upon [1] by the REEF community
and has been discussed [2] on this list.

This vote is open for at least 72 hours.

[ ] +1 Graduate Apache REEF from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache REEF from the Incubator because ...

Thanks,

Markus

[0]: http://s.apache.org/reefgraduationdiscussion
[1]: http://s.apache.org/reefgraduationppmsvoteresult
[2]: http://s.apache.org/reefgraduationdiscussionongeneral


X. Establish the Apache REEF 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 application development on top of
resource managers.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache REEF Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache REEF Project be and hereby is
responsible for the creation and maintenance of a software
framework for application development on top of resource
managers; and be it further

RESOLVED, that the office of "Vice President, Apache REEF"
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 REEF Project, and to have primary
responsibility for management of the projects within the scope
of responsibility of the Apache REEF 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 REEF Project Management Committee:

* Markus Weimer 
* Byung-Gon Chun 
* Yunseong Lee 
* Brian Cho 
* Beysim Sezgin 
* Yingda Chen 
* Julia Wang 
* Andrew Chung 
* Youngseok Yang 
* Gyewon Lee 
* Taegeon Um 
* Joo Seong Jeong 
* Geon-Woo Kim 
* Mariia Mykhailova 
* Shravan M Narayanamurthy 
* Dongjoon Hyun 
* Sergiy Matusevych 
* Tyson Condie 
* Chris Mattman 
* Chris Douglas 
* Boris Shulman 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
is tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache REEF Project; and be it further

RESOLVED, that the initial Apache REEF Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator REEF podling; and be it further

RESOLVED, that all responsibility pertaining to the Apache
Incubator REEF podling encumbered upon the Apache Incubator
PMC are hereafter discharged.

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

Re: [VOTE] Graduate REEF

[Hitesh Shah]

+1 (binding)

— Hitesh 

On Nov 9, 2015, at 1:14 PM, Markus Weimer  wrote:

> This is the vote to decide if Apache REEF should graduate from
> the Incubator. Please see the proposed resolution below.
> 
> This proposal was discussed [0] and voted upon [1] by the REEF community
> and has been discussed [2] on this list.
> 
> This vote is open for at least 72 hours.
> 
> [ ] +1 Graduate Apache REEF from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache REEF from the Incubator because ...
> 
> Thanks,
> 
> Markus
> 
> [0]: http://s.apache.org/reefgraduationdiscussion
> [1]: http://s.apache.org/reefgraduationppmsvoteresult
> [2]: http://s.apache.org/reefgraduationdiscussionongeneral
> 
> 
> X. Establish the Apache REEF 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 application development on top of
>resource managers.
> 
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache REEF Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
> 
>RESOLVED, that the Apache REEF Project be and hereby is
>responsible for the creation and maintenance of a software
>framework for application development on top of resource
>managers; and be it further
> 
>RESOLVED, that the office of "Vice President, Apache REEF"
>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 REEF Project, and to have primary
>responsibility for management of the projects within the scope
>of responsibility of the Apache REEF 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 REEF Project Management Committee:
> 
>* Markus Weimer 
>* Byung-Gon Chun 
>* Yunseong Lee 
>* Brian Cho 
>* Beysim Sezgin 
>* Yingda Chen 
>* Julia Wang 
>* Andrew Chung 
>* Youngseok Yang 
>* Gyewon Lee 
>* Taegeon Um 
>* Joo Seong Jeong 
>* Geon-Woo Kim 
>* Mariia Mykhailova 
>* Shravan M Narayanamurthy 
>* Dongjoon Hyun 
>* Sergiy Matusevych 
>* Tyson Condie 
>* Chris Mattman 
>* Chris Douglas 
>* Boris Shulman 
> 
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
>appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
>is tasked with the creation of a set of bylaws intended to
>encourage open development and increased participation in the
>Apache REEF Project; and be it further
> 
>RESOLVED, that the initial Apache REEF Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator REEF podling; and be it further
> 
>RESOLVED, that all responsibility pertaining to the Apache
>Incubator REEF podling encumbered upon the Apache Incubator
>PMC are hereafter discharged.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

RE: [VOTE] Graduate REEF

[Julia Wang (QIUHE)]

+1

Julia

-Original Message-
From: Chris Douglas [mailto:cdoug...@apache.org] 
Sent: Monday, November 9, 2015 1:47 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Graduate REEF

+1 -C

On Mon, Nov 9, 2015 at 1:14 PM, Markus Weimer  wrote:
> This is the vote to decide if Apache REEF should graduate from the 
> Incubator. Please see the proposed resolution below.
>
> This proposal was discussed [0] and voted upon [1] by the REEF 
> community and has been discussed [2] on this list.
>
> This vote is open for at least 72 hours.
>
> [ ] +1 Graduate Apache REEF from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache REEF from the Incubator because ...
>
> Thanks,
>
> Markus
>
> [0]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationdiscussion=01%7c01%7cQiuhe.Wang%40microsof
> t.com%7cdbcd052826ca4852f41a08d2e94f66b3%7c72f988bf86f141af91ab2d7cd01
> 1db47%7c1=j9Uulpdhr%2fEDpH3296StoEZF84u6tMkg56mZBIzBsN0%3d
> [1]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationppmsvoteresult=01%7c01%7cQiuhe.Wang%40micr
> osoft.com%7cdbcd052826ca4852f41a08d2e94f66b3%7c72f988bf86f141af91ab2d7
> cd011db47%7c1=%2fkz%2fvT3C5uOScvi2wUsxK9y8ECYr4cFaq43I0iABGNQ%3d
> [2]: 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apac
> he.org%2freefgraduationdiscussionongeneral=01%7c01%7cQiuhe.Wang%4
> 0microsoft.com%7cdbcd052826ca4852f41a08d2e94f66b3%7c72f988bf86f141af91
> ab2d7cd011db47%7c1=V5Gn9h3Tblc0qz93EFvSn7JWIhwKyTfdV8r7B2LiC3k%3
> d
>
> 
> X. Establish the Apache REEF 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 application development on top of
> resource managers.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache REEF Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache REEF Project be and hereby is
> responsible for the creation and maintenance of a software
> framework for application development on top of resource
> managers; and be it further
>
> RESOLVED, that the office of "Vice President, Apache REEF"
> 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 REEF Project, and to have primary
> responsibility for management of the projects within the scope
> of responsibility of the Apache REEF 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 REEF Project Management Committee:
>
> * Markus Weimer 
> * Byung-Gon Chun 
> * Yunseong Lee 
> * Brian Cho 
> * Beysim Sezgin 
> * Yingda Chen 
> * Julia Wang 
> * Andrew Chung 
> * Youngseok Yang 
> * Gyewon Lee 
> * Taegeon Um 
> * Joo Seong Jeong 
> * Geon-Woo Kim 
> * Mariia Mykhailova 
> * Shravan M Narayanamurthy 
> * Dongjoon Hyun 
> * Sergiy Matusevych 
> * Tyson Condie 
> * Chris Mattman 
> * Chris Douglas 
> * Boris Shulman 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Markus Weimer be
> appointed to the office of Vice President, Apache REEF, 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 REEF Project be and hereby
> is tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache REEF Project; and be it further
>
> RESOLVED, that the initial Apache REEF Project be and hereby
> is tasked with the migration 

[DISCUSS] OpenMiracl for Incubation

[Nick Kew]

I should like to propose that we consider OpenMiracl for incubation.

OpenMiracl is software for distributed cryptography, building
on the existing MIRACL library and tools.  Among the
big problems it helps solve are Identity and Trust, and it
crucially serves to eliminate single points of failure.

OpenMiracl seeks incubation at Apache to help it transition
from a single-company open source project to full open development.
This move is prompted by increasing outside corporate interest,
and will take place concurrently with an IETF standards process
for the M-Pin protocol underlying much of OpenMiracl.

I'll attach the full draft proposal here, and upload to the
wiki once I've sorted access there.

-- 
Nick Kew
# Project Proposal: OpenMiracl


## Abstract

OpenMiracl is a distributed cryptosystem for cloud computing. Its purpose is to provide an open source alternative to proprietary key management and certificate backed cryptosystems used for secure communication and authentication. The adoption of OpenMiracl will create a secure, free, open source alternative to monolithic certificate authorities and eliminate single points of failure.

### Background

The Cloud Computing industry is using 40-year-old cryptographic algorithms and infrastructure, invented for a different era when client-server computing was the dominant paradigm. At the heart of it, is the continued reliance on outdated, and problematic, monolithic cryptographic trust hierarchies such as commercial certificate authorities.

A number of factors are aligning to make this the right time to bring forth an alternative to the Internet's continued reliance on PKI.

The Cloud Infrastructure as a Service (IaaS) industry as a whole encounters friction bringing the largest customers in regulated industries onto their platforms because issues of cryptographic trust, data residency, and data governance prevent total adoption among regulated industries.

DevOps teams tasked with running an IaaS provider's datacenter automation encounter challenges scaling and automating data center operations when confronted with the complexities of running encryption, certificate and key management infrastructures built for a client-server era.

Enterprises in regulated industries find challenges to transform entirely into digital businesses because the economics of cloud computing are unavailable to them.

Despite the astounding growth of cloud infrastructure as a service platforms over the last few years, full adoption by organizations with stringent data security requirements won’t be achieved until these fundamental capability issues get resolved.

Lastly, the Internet as a whole is suffering from an erosion of trust following incidents with commercial certificate authorities industry, i.e., compromised root keys, and failures in due diligence issuing real domain certificates.

Indeed, mass surveillance, a lack of easy end-user encryption, a growing demand for key escrow under legal oversight, and general certificate authority security concerns create the question:
How appropriate is the continued dependency on PKI when the goal is to advance the benefits of cloud computing across the technology landscape?

NetCraft is the industry standard for monitoring Active TLS certificates. In May 2015, they stated that “Although the global [TLS] ecosystem is competitive, it is dominated by a handful of major CAs — three certificate authorities (Symantec, Comodo, GoDaddy) account for three-quarters of all issued [TLS] certificates on public-facing web servers.” 


The Internet Security Research Group's (ISRG) "Let's Encrypt" initiative aims to make Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates available for free in an automated fashion. This a step in the right direction, in that it removes the risk of profit before ethics. The real issue, which is one entity acts as a monolithic trust hierarchy, is not addressed. The monolithic trust hierarchy is a fundamental design flaw within PKI itself.

The rate of attacks against certificate authorities seems to be [increasing](http://wiki.cacert.org/Risk/History) as the obvious single point of compromise design inherent to PKI is becoming a more popular route to carry out attacks.

## Proposal


OpenMiracl is an open source, pairing-based cryptographic platform to solve key management, secure communications, data governance and compliance issues that are challening Cloud Provider's and their customers.

It does this without the need for certificate authorities, putting into place a new category of service providers called Distributed Trust Authorities (D-TA's).

The M-Pin protocol, and its existing open-source MIRACL implementation on which OpenMiracl will build, are already in use by Experian, NTT, Odin, Gov.UK and are being rolled out at scale for zero password multi-factor authentication and certificate-less HTTPS / secure channel.

It is proposed that OpenMiracl enter incubation at Apache.  At the same 

Re: Releases during incubation?

[Greg Stein]

Yup. Subversion 1.6.9 was released while we were incubating.

Further: Subversion 1.6.x had patch releases for three years (given our
support rules), after we became Apache Subversion. 1.7.0 was our first
Apache release, occurring about 18 months after we became a TLP. We
distinguished them by name (Subversion vs Apache Subversion), and by
release channel/host (tigris.org vs apache.org). The same people happened
to work on both releases, but we made sure to distinguish non-Foundation
releases.

On Mon, Nov 9, 2015 at 7:22 PM, Joe Schaefer  wrote:

> Subversion cut a release while in incubation on their old system.
> Shouldn't pose a problem for others.
>
> On Mon, Nov 9, 2015 at 8:03 PM, Todd Lipcon  wrote:
>
> > Hey folks,
> >
> > Hopefully quick policy question here:
> >
> > Once a project is under proposal for incubation, what is the foundation
> > policy on that project making releases outside of Apache from its current
> > home?
> >
> > For example, suppose there's an open source project FooBar, with a public
> > release FooBar 1.0.0 in use by various people out in the world. FooBar is
> > then proposed to the incubator. During the discussion/voting timeframe,
> > someone discovers a bug in FooBar 1.0.0, and the team would like to
> release
> > FooBar 1.0.1 from the project's current home (eg github). Would this be
> an
> > issue?
> >
> > More controversial variant:
> >
> > How about early during the incubation period, while the project is still
> in
> > the process of transitioning the necessary infrastructure, etc, into the
> > ASF repositories? Assuming that the project is making good faith efforts
> > towards making a release compatible with ASF guidelines, would it be
> > allowed to make "external" releases during this initial period of
> > incubation, for the purposes of bug fixes?
> >
> > Thanks
> > Todd
> >
>

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Justin Mclean]

Hi,

> Are you referring to the screenshots under war/static/? Those are
> untouched since the migration from Google, so fall under the license
> from them.

Not the screen shots no but the photos found in here:
./src/org/waveprotocol/wave/client/editor/harness/public/pics/

Do you have the authors permission to use and distribute them?

> These icons are from the Tango Desktop Project, which licenses them
> into the public domain, who are mentioned in THANKS. I can mention
> this explicitly in THANKS if preferable?

In that case should be added to LICENSE. Only minor issue, certainly nothing to 
hold up this release.

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

Re: IP clearance for properly licensed code

[Alex Harui]

And I believe the “external” or “third-party” code should not be listed in
the SGA’s Exhibit A since those files are not being submitted to the ASF.

There is some documentation on how to handle third-party code.  I think
one doc is [1] which has links to other places.

HTH,
-Alex

[1] http://www.apache.org/legal/src-headers.html

On 11/9/15, 6:58 PM, "Rob Vesse"  wrote:

>You are quite right
>
>Apache projects can incorporate code under suitable licenses provided that
>they properly attribute it in their NOTICE and LICENSE files.  Exact
>requirements will depend on the license under which the external source
>code is incorporated.
>
>For a simple case like this it would most likely just require placing some
>text like the following into the LICENSE file:
>
>---
>The following code/components are under a Foo License
>
>[Foo License text]
>---
>
>Essentially all copyright owners of the code original to the incoming
>project need to provide CLAs and/or SGAs as appropriate and any external
>code incorporated into the code base needs to be under Apache compatible
>licenses and appropriately attributed
>
>Rob
>
>On 09/11/2015 18:11, "Todd Lipcon" t...@apache.org> wrote:
>
>>Hi all,
>>
>>Another hopefully simple question:
>>
>>The Mentor guide contains the following text:
>>
>>>
>>> Existing codebases need to be imported through the standard IP
>>>clearance
>>> process. This means that a Software Grant Agreement (SGA
>>> ) or Contributor License
>>> Agreement (CLA ) need to be
>>> submitted for all copyright owners. This process may take a while so it
>>>is
>>> best to start as soon as the podling is accepted.
>>
>>
>>How does this rule apply to sections of code that are released publicly
>>under a suitable license (eg Apache/BSD/MIT) but were originally written
>>from a different context? For example, I am working on an incubation
>>proposal for a project that includes portions of code copied from the
>>Chromium open source project, which is released under a BSD license but
>>holds a copyright notice by "The Chromium Authors". It's unlikely that
>>these authors would submit the appropriate paperwork to the ASF.
>>
>>Assuming that the imported project retains the notice of the original
>>copyright, and the commits which import the code suitably track the
>>provenance of the code, my understanding is this is acceptable under the
>>licenses and foundation policy. However, the text in the mentor guide
>>seems
>>to indicate otherwise.
>>
>>Thanks
>>Todd
>
>
>
>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[Jian Zhong]

+1 non-binding
md5 passed
no license issue
mvn test passed

On Tue, Nov 10, 2015 at 10:57 AM, Luke Han  wrote:

> Forwarding my vote from dev@:
>
> +1 non-binding
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Tue, Nov 10, 2015 at 6:00 AM, Henry Saputra 
> wrote:
>
> > - Signature files look good
> > - Hash files look good
> > - LICENSE file looks good
> > - NOTICE file looks good
> > - DISCLAIMER files exists
> > - Source compiled successfully
> > - NO 3rd party executables in source artifact
> > - Source files has correct Apache header
> >
> > +1 (binding)
> >
> > On Sat, Nov 7, 2015 at 4:46 PM, ShaoFeng Shi 
> > wrote:
> > > Hi all,
> > >
> > > The Apache Kylin community has voted on and approved a proposal to
> > release
> > > Apache Kylin 1.1.1-incubating. This release only includes license
> > cleanup,
> > > no Java code change; For more information please check KYLIN-999.
> > >
> > > Proposal:
> > > http://s.apache.org/kylin-1.1.1-vote_rc1
> > >
> > > Vote result:
> > > 7 binding +1 votes
> > > 9 non-binding +1 votes
> > > No -1 votes
> > > http://s.apache.org/kylin-1.1.1-result_rc1
> > >
> > >
> > > The commit to be voted upon:
> > >
> >
> https://github.com/apache/incubator-kylin/commit/708ea38d7f764048e67e8e1ee8a13955983d12ba
> > >
> > > Its hash is 708ea38d7f764048e67e8e1ee8a13955983d12ba.
> > >
> > > The artifacts to be voted on are located here:
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1.1-incubating-rc1/
> > >
> > > The hashes of the artifacts are as follows:
> > > apache-kylin-1.1.1-incubating-src.tar.gz.md5
> > > ff942b2eba870b04552bc8c8dace5517
> > > apache-kylin-1.1.1-incubating-src.tar.gz.sha1
> > > cc8990ba7821b02f4bf6da5f870b30a915881535
> > >
> > > A staged Maven repository is available for review at:
> > >
> https://repository.apache.org/content/repositories/orgapachekylin-1013/
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/shaofengshi.asc
> > >
> > > Pursuant to the Releases section of the Incubation Policy and with
> > > the endorsement of our mentors we would now like to request
> > > the permission of the Incubator PMC to publish the release. The vote
> > > is open for 72 hours, or until the necessary number of votes (3 +1)
> > > is reached.
> > >
> > > [ ] +1 Release this package
> > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > > Shaofeng Shi, on behalf of Apache Kylin PPMC
> > > shaofeng...@apache.org
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] OpenMiracl for Incubation

[Nick Kew]

On Tue, 2015-11-10 at 01:33 +, Nick Kew wrote:

> [chop]

I need to declare my own interest here.

I first approached Certivox in search of solutions to the
problems of online identity, and made some suggestions.
They welcomed my interest, and I am now undertaking
development work for them on a consultancy basis.

-- 
Nick Kew


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

Re: Wiki access

[Marvin Humphrey]

On Mon, Nov 9, 2015 at 5:47 PM, Nick Kew  wrote:
> I have a incubator-wiki account "niq", but no current
> write access.  Can someone with the relevant karma
> please enable me?

Done.

Marvin Humphrey

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

Re: [DISCUSS] S2Graph Incubator Proposal

[Luke Han]

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  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
>  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  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 
> >> 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 
> 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 to
> >> >> efficiently store user relation and user activities as one large
> graph
> >> >> and provide unified query to traverse graph. It was open sourced on
> >> >> Github about a 3 months ago in June 2015.
> >> >>
> >> >> Over time S2Graph, together with HBase as storage tier, has begun to
> >> >> be adapted into various applications, such as messaging, social
> feeds,
> >> >> realtime recommendations at Kakao.
> >> >>
> >> >> Users can benefit from S2Graph`s generalized high level API instead
> of
> >> >> low-level key/value API for graph abstraction, just like Phoenix
> >> >> provide SQL layer over HBase.
> >> >>
> >> >> == Rationale ==
> >> >> Graph data(highly interconnected data) is very abundant and important
> >> >> these days.
> >> >> When users have a multitude of relationships, each with complex
> >> >> properties associated with them, graph model is more intuitive and
> >> >> efficient than tabular format(RDBMS).
> >> >> There are many ASF projects that provide SQL layer, but there is no
> >> >> ASF projects that provide scalable graph layer on existing hadoop
> echo
> >> >> system.
> >> >> When graph data grows to trillion edge scale, the process of
> >> >> traversing takes a long time and costly. However, with the benefit of
> >> >> HBase`s scalable architecture, S2Graph can traverse large graph in
> >> >> breadth first search manner efficiently.
> >> >>
> >> >> S2Graph also interoperates with several existing Apache
> >> >> projects(HBase, Spark) to provide way to merge real time events and
> >> >> batch processed data using property graph data model.
> >> >>
> >> >> Many developers are running their own domain specific API servers to
> >> >> serve their data products, but graph model is general and S2Graph API
> >> >> fully support traverse on graph, so it can be used as scalable
> general
> >> >> purpose API serving layer for various domains.
> >> >> As long as data can be modeled as graph, then users can avoid tedious
> >> >> work for developing customized API servers by using S2Graph.
> >> >>
> >> >> == Initial Goals ==
> >> >> The initial goals will be to move the existing codebase to Apache and
> 

Re: IP clearance for properly licensed code

[Rob Vesse]

You are quite right

Apache projects can incorporate code under suitable licenses provided that
they properly attribute it in their NOTICE and LICENSE files.  Exact
requirements will depend on the license under which the external source
code is incorporated.

For a simple case like this it would most likely just require placing some
text like the following into the LICENSE file:

---
The following code/components are under a Foo License

[Foo License text]
---

Essentially all copyright owners of the code original to the incoming
project need to provide CLAs and/or SGAs as appropriate and any external
code incorporated into the code base needs to be under Apache compatible
licenses and appropriately attributed

Rob

On 09/11/2015 18:11, "Todd Lipcon"  wrote:

>Hi all,
>
>Another hopefully simple question:
>
>The Mentor guide contains the following text:
>
>>
>> Existing codebases need to be imported through the standard IP clearance
>> process. This means that a Software Grant Agreement (SGA
>> ) or Contributor License
>> Agreement (CLA ) need to be
>> submitted for all copyright owners. This process may take a while so it
>>is
>> best to start as soon as the podling is accepted.
>
>
>How does this rule apply to sections of code that are released publicly
>under a suitable license (eg Apache/BSD/MIT) but were originally written
>from a different context? For example, I am working on an incubation
>proposal for a project that includes portions of code copied from the
>Chromium open source project, which is released under a BSD license but
>holds a copyright notice by "The Chromium Authors". It's unlikely that
>these authors would submit the appropriate paperwork to the ASF.
>
>Assuming that the imported project retains the notice of the original
>copyright, and the commits which import the code suitably track the
>provenance of the code, my understanding is this is acceptable under the
>licenses and foundation policy. However, the text in the mentor guide
>seems
>to indicate otherwise.
>
>Thanks
>Todd





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

Draft report November 2015 -- please review

[Marvin Humphrey]

Incubator PMC report for November 2015

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

There are 47 podlings currently undergoing incubation.

With 702 messages to general@incubator, October was one of the heaviest
months for email traffic in a long time.

Podlings nearing graduation received extra scrutiny this month, presumably
as an indirect result of various recent proposals to rework graduation to
include more structured review.  Such evaluations of podling readiness,
while illuminating, put stress on the Mentors and contributors to the
podling under the microscope and raise the overall tension in the
Incubator.

Another topic of discussion was disengaged Mentors.  An initiative to engage
Mentors privately when podlings do not report for two months or more yielded
positive results, with some Mentors reaffirming their commitment and others
officially moving on.

* Community

  New IPMC members:

  - Tom Barber (magicaltrout)
  - Patrick Wendell (pwendell)
  - Reynold Xin (rxin)
  - Phil Sorber (sorber)
  - Julien Le Dem (julien)
  - Jacques Nadeau (jacques)

  No one left the IPMC this month, but a handful of Mentors have stepped
  down from their posts with various podlings.  Most of the resignations
  were from Mentors who had become inactive, so the Incubator's rolls have
  become a bit more accurate.

* New Podlings

  - Eagle
  - Mynewt
  - Concerted
  - SystemML

* Graduations

  The board has motions for the following:

  - Brooklyn
  - Groovy

* Releases

  The following releases were made since the last Incubator report:

  - 2015-10-05 Apache Johnzon 0.9.2-incubating
  - 2015-10-07 Apache Singa 0.1.0
  - 2015-10-14 Apache AsterixDB 0.8.7-incubating
  - 2015-10-14 Apache REEF 0.13.0-incubating
  - 2015-10-23 Apache Kylin 1.1-incubating
  - 2015-10-28 Apache TinkerPop 3.0.2-incubating
  - 2015-10-30 Apache Apex v3.2.0-incubating
  - 2015-10-31 Apache Slider 0.81.1-incubating

* IP Clearance

  - Taobao (China) Software Co., Ltd and several individuals donated Alibaba
JStorm, "A fork of Apache Storm with Clojure code replaced with Java,
and several other improvements".

  A discussion calling into question what responsibilities -- if any -- the
  Incubator should have with regards to IP Clearance eventually went quiet,
  leaving the status quo intact.

* Miscellaneous

  - Droids has retired.
  - Kalumet has retired.
  - The Corinthia community is voting on retirement.

 Summary of podling reports 

* Still getting started at the Incubator

  - Concerted
  - Mynewt
  - Rya

* Not yet ready to graduate

  No release:

  - Climate Model Diagnostic Analyzer
  - Cotton
  - MADlib
  - DataFu
  - HAWQ
  - HORN

  Community growth:

  - Apex
  - Blur
  - Slider
  - Tamaya
  - TinkerPop
  - Twill

* Ready to graduate

  - AsterixDB
  - Kylin
  - REEF

* Did not report, expected next month

  - Ripple (5 months late)
  - Sirona
  - Unomi

--
   Table of Contents
Apex
AsterixDB
Blur
Climate Model Diagnostic Analyzer
Concerted
Cotton
DataFu
HAWQ
HORN
Kylin
MADlib
Mynewt
REEF
Ripple
Rya
Sirona
Slider
Tamaya
TinkerPop
Twill
Unomi

--


Apex

Apex is an enterprise grade native YARN big data-in-motion platform that
unifies stream processing as well as batch processing.

Apex has been incubating since 2015-08-17.

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

  1. Release Apex-Core, and Apex-Malhar on ongoing basis.
  2. Grow contributors beyond the initial set.
  3. Move to using Apache JIRA

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

  The project is still using the original Atlassian instance of JIRA.
  INFRA-10144 has tracked the Apache JIRA migration request since August.

How has the community developed since the last report?

  The community is very engaged with the development of the project. There
  have been 788 messages on dev@ for October.

  The community has been active building meetup groups in various locations:
  http://s.apache.org/jKT

  - Number of meetups: 6 in total so far: 4 in USA cities and 2 in Indian
cities
  - Total members in worldwide Apache Apex meetups: 495
  - Events: 1 in Oct; 4 scheduled in Nov: CapitalOne presentation in
Chicago; DataTorrent presentation in Pune; GE presentation in San Ramon;
PubMatic presentation in San Jose;

  Future: Planning to start meetups in more cities, and be able to organize
  2-3 events a month.

How has the project developed since the last report?

  The first release under incubation passed voting. Apex (Core)
  3.2.0-incubating was released 2015-10-30.  The community is currently
  discussing roadmap for upcoming releases.

  Various metrics are as follows:
  

Re: [DISCUSS] S2Graph Incubator Proposal

[Hyunsik Choi]

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 to
efficiently store user relation and user activities as one large graph
and provide unified query to traverse graph. It was open sourced on
Github about a 3 months ago in June 2015.

Over time S2Graph, together with HBase as storage tier, has begun to
be adapted into various applications, such as messaging, social feeds,
realtime recommendations at Kakao.

Users can benefit from S2Graph`s generalized high level API instead of
low-level key/value API for graph abstraction, just like Phoenix
provide SQL layer over HBase.

== Rationale ==
Graph data(highly interconnected data) is very abundant and important
these days.
When users have a multitude of relationships, each with complex
properties associated with them, graph model is more intuitive and
efficient than tabular format(RDBMS).
There are many ASF projects that provide SQL layer, but there is no
ASF projects that provide scalable graph layer on existing hadoop echo
system.
When graph data grows to trillion edge scale, the process of
traversing takes a long time and costly. However, with the benefit of
HBase`s scalable architecture, S2Graph can traverse large graph in
breadth first search manner efficiently.

S2Graph also interoperates with several existing Apache
projects(HBase, Spark) to provide way to merge real time events and
batch processed data using property graph data model.

Many developers are running their own domain specific API servers to
serve their data products, but graph model is general and S2Graph API
fully support traverse on graph, so it can be used as scalable general
purpose API serving layer for various domains.
As long as data can be modeled as graph, then users can avoid tedious
work for developing customized API servers by using S2Graph.

== Initial Goals ==
The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Once this is
accomplished, we plan for incremental development and releases that
follow the Apache guidelines.

== Current Status ==

=== Meritocracy ===
S2Graph operated on meritocratic principles from the get go.
Currently, all the discussions pertaining to S2Graph development are
public on Github. The current incubation
proposal includes the major code contributors to S2Graph. Several
additional people have worked on the S2graph codebase for industry use
cases and would be interested in becoming committers. We are starting
with a small committer group and we plan to add additional committers
following an open merit-based decision process during the incubation
phase.

=== Community ===
We have already begun building a community but at this time the
community consists only of S2Graph developers – all Kakao employees –
and prospective users.
S2Graph seeks to develop developer and user communities during incubation.

=== Core Developers ===
S2Graph is currently being designed and developed by 2 engineers from
Kakao. - Doyung Yoon, Deawon Jeong.

=== Alignment ===
Our proposed S2Graph effort aligns closely with Apache HBase. The
HBase project perimeter is denoted by a simple byte-array based
Create, Read, Update, Delete and Scan APIs with no current plans to
extend beyond this bounds.

S2Graph complements this with a higher level API for property graph model.

S2Graph was designed to offer scalable distributed graph database skin
over HBase from the beginning in order to provide property graph model
and breadth first search, and continue to focus on providing graph
model.

== Known Risks ==
=== Orphaned Products ===
The core developers of S2Graph team plan to work full time on this
project. There is very little risk of S2Graph getting orphaned since
at least one large company (Kakao) is extensively using it in their
production HBase clusters. For example, currently there are 20+ use
cases with more than 1+Trillion edges and 140 million breadth first
search query requests per minute using S2Graph in production.
We plan to extend and diversify this community further through Apache.

=== Inexperience with Open Source ===
The core developers are all active users and followers of open source.

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ian Dunlop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I did try to use the CLI to build it but ran into java issues since
windows seems determined to use java 8 and i can only get java 7 to
run inside eclipse. Getting windows to use an older version of java
seems like a fairly difficult or poorly documented task nowadays.
Suggestions welcome (though as noted earlier they may belong a a
different list).

Cheers,

Ian

On 08/11/15 19:41, John D. Ament wrote:
> Typically speaking, releases should compile.  If there are steps
> required to make it compile they should be shared. On Nov 8, 2015
> 14:33, "Upayavira"  wrote:
> 
>> Ian,
>> 
>> Please bear in mind that this release vote is to validate the
>> legal aspects of the release, not its technical merits. Technical
>> merits can be resolved in subsequent releases.
>> 
>> Upayavira
>> 
>> On Fri, Nov 6, 2015, at 02:51 PM, Ian Dunlop wrote:
> Hello,
> 
> I'll give it at 0 the moment since I encountered a build issue. I 
> downloaded the src zip and imported the code into Eclipse Mars
> (4.50) with jdk 1.7.0_79 & ANT 1.9.4 but found the following
> issues:
> 
> 1) BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:28:
> Cannot find 
> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path}
> imported from C:\Users\idunlop\workspace\waveinabox\build.xml
> 
> Resolved by commenting out
> 
> 
> 
>  
> 
> and tried again
> 
> 2)
> 
> BUILD FAILED Target "define-gxpc" does not exist in the project
> "waveinabox". It is used from target "gen-gxp".
> 
> Resolved by removing define-gxpc from
> 
>  depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp"> 
>  destdir="${gen.dir}/gxp" target="org.waveprotocol.box.server.gxp"
> />  
> 
> 3)
> 
> BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:120:
> Problem: failed to create task or type buildproto Cause: The name
> is undefined. Action: Check the spelling. Action: Check that any
> custom tasks/types have been declared. Action: Check that any
> / declarations have taken place.
> 
> At that point I figured it best to report the issues here:
> 
> Is there a procedure for building in eclipse, am I missing an ant 
> setting somewhere?
> 
> So, apart fromn the compile issue everything else looks good:
> 
> signatures are good artifact/hashes good DISCLAIMER OK LICENCE OK 
> NOTICE OK
> 
> Cheers,
> 
> Ian
> 
> 
> 
> On 04/11/2015 07:14, Justin Mclean wrote:
> Hi,
> 
> +1 binding.
> 
> Could you please fix the LICENCE Appendix in the next
> release. The text should be "Copyright [] [name of
> copyright owner]” not "Copyright 2013 The Apache Software
> Foundation”.
> 
> I checked: - artefact has incubating in name - signatures
> and hashes good - DISCLAIMER exists - LICENSE  has minor
> issue with the copyright in the appendix. Not required but
> it could also use the sort form in LICENSE [1] particularly
> as you bundle the software LICENSE files. - NOTICE good. -
> All source files have Apache headers - No unexpected binary
> file in source release (but see below) - can compile from
> source - test pass
> 
> I notice there’s a couple of photographs in the source
> release, I assume you have permission from the person who
> took them to use these? IF so you may want to put that in
> the LICENSE.
> 
> There's a number of binary file without extensions in 
> /thumbnail_patterns/ but they all look to be PNGs is this
> the case? Where did these images come from?
> 
> I had a quick look at the binary release and the LICENCE
> and NOTICE appear comprehensive. I didn;t do a though
> check. I did notice that the year is incorrect in the
> NOTICE file and LICENSE appendix has the same issue.  It’s
> actually wrong here as non ASF Apache licensed software is
> mentioned. There no need to mean Apache licensed software
> in the LICENCE but no harm is done by donning so. [2]
> 
> Thanks, Justin
> 
> 1.
> http://www.apache.org/dev/licensing-howto.html#permissive-deps
>
> 
2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> 
> 
> 
> --
- ---
>
>
>
> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail:
> general-h...@incubator.apache.org
> 
> 
>>> 
>>> 
- -
>>>
>>> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail:
>>> general-h...@incubator.apache.org
>>> 
>> 
>> -
>>
>> 
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail:
>> general-h...@incubator.apache.org
>> 
>> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Re: Project Website Template

[Julian Hyde]

> On Nov 7, 2015, at 6:40 PM, Luciano Resende  wrote:
> 
> On Sat, Nov 7, 2015 at 7:35 PM, Julian Hyde  wrote:
> 
>> I also think it would be useful to provide a template for maven/java based
>> projects. There would be a pom.xml, module/pom.xml and
>> module/org/apache/foo/Foo.java, and just enough content in the pom.xml to
>> be able to make a release by typing “mvn release:prepare … mvn
>> release:perform”. If anyone is interested I’ll do it.
> 
> I believe this is already available if your "parent pom" inherit from
> "apache pom".
> See: http://svn.apache.org/repos/asf/maven/pom/tags/apache-17/

In my experience you need a lot more in a pom than to just inherit from the 
apache pom. For example you need to configure maven-assembly-plugin to generate 
a artifacts called apache-foo-x.y-src rather than foo-x.y-src, and use 
checksum-maven-plugin to generate md5 and sha-1 checksums. Most projects will 
probably also want checkstyle, to generate a git.properties file containing the 
commit id, and set up some RAT exclusions.

Julian


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

Re: [DISCUSS] S2Graph Incubator Proposal

[Andrew Purtell]

If you are looking for mentors let me volunteer as one.

I think S2Graph has the potential to be a good addition to the Apache
family given its relationships and dependencies with other Apache projects
from the outset.



On Mon, Nov 9, 2015 at 10:54 AM, Hyunsik Choi  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 to
> efficiently store user relation and user activities as one large graph
> and provide unified query to traverse graph. It was open sourced on
> Github about a 3 months ago in June 2015.
>
> Over time S2Graph, together with HBase as storage tier, has begun to
> be adapted into various applications, such as messaging, social feeds,
> realtime recommendations at Kakao.
>
> Users can benefit from S2Graph`s generalized high level API instead of
> low-level key/value API for graph abstraction, just like Phoenix
> provide SQL layer over HBase.
>
> == Rationale ==
> Graph data(highly interconnected data) is very abundant and important
> these days.
> When users have a multitude of relationships, each with complex
> properties associated with them, graph model is more intuitive and
> efficient than tabular format(RDBMS).
> There are many ASF projects that provide SQL layer, but there is no
> ASF projects that provide scalable graph layer on existing hadoop echo
> system.
> When graph data grows to trillion edge scale, the process of
> traversing takes a long time and costly. However, with the benefit of
> HBase`s scalable architecture, S2Graph can traverse large graph in
> breadth first search manner efficiently.
>
> S2Graph also interoperates with several existing Apache
> projects(HBase, Spark) to provide way to merge real time events and
> batch processed data using property graph data model.
>
> Many developers are running their own domain specific API servers to
> serve their data products, but graph model is general and S2Graph API
> fully support traverse on graph, so it can be used as scalable general
> purpose API serving layer for various domains.
> As long as data can be modeled as graph, then users can avoid tedious
> work for developing customized API servers by using S2Graph.
>
> == Initial Goals ==
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is
> accomplished, we plan for incremental development and releases that
> follow the Apache guidelines.
>
> == Current Status ==
>
> === Meritocracy ===
> S2Graph operated on meritocratic principles from the get go.
> Currently, all the discussions pertaining to S2Graph development are
> public on Github. The current incubation
> proposal includes the major code contributors to S2Graph. Several
> additional people have worked on the S2graph codebase for industry use
> cases and would be interested in becoming committers. We are starting
> with a small committer group and we plan to add additional committers
> following an open merit-based decision process during the incubation
> phase.
>
> === Community ===
> We have already begun building a community but at this time the
> community consists only of S2Graph developers – all Kakao employees –
> and prospective users.
> S2Graph seeks to develop developer and user communities during incubation.
>
> === Core Developers ===
> S2Graph is currently being designed and developed by 2 engineers from
> Kakao. - Doyung Yoon, Deawon Jeong.
>
> === Alignment ===
> Our proposed S2Graph effort aligns closely with Apache HBase. The
> HBase project perimeter is denoted by a simple byte-array based
> Create, Read, Update, Delete and Scan APIs with no current plans to
> extend beyond this bounds.
>
> S2Graph complements this with a higher level API for property graph model.
>
> S2Graph was designed to offer scalable distributed graph database skin
> over HBase from the beginning in order to provide property graph model
> and breadth first search, and continue to focus on providing graph
> model.
>
> == Known Risks ==
> === Orphaned Products ===
> The core developers of S2Graph team plan to work full time on this
> project. There is very 

Re: [DISCUSS] S2Graph Incubator Proposal

[Sergio Fernández]

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  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 to
> efficiently store user relation and user activities as one large graph
> and provide unified query to traverse graph. It was open sourced on
> Github about a 3 months ago in June 2015.
>
> Over time S2Graph, together with HBase as storage tier, has begun to
> be adapted into various applications, such as messaging, social feeds,
> realtime recommendations at Kakao.
>
> Users can benefit from S2Graph`s generalized high level API instead of
> low-level key/value API for graph abstraction, just like Phoenix
> provide SQL layer over HBase.
>
> == Rationale ==
> Graph data(highly interconnected data) is very abundant and important
> these days.
> When users have a multitude of relationships, each with complex
> properties associated with them, graph model is more intuitive and
> efficient than tabular format(RDBMS).
> There are many ASF projects that provide SQL layer, but there is no
> ASF projects that provide scalable graph layer on existing hadoop echo
> system.
> When graph data grows to trillion edge scale, the process of
> traversing takes a long time and costly. However, with the benefit of
> HBase`s scalable architecture, S2Graph can traverse large graph in
> breadth first search manner efficiently.
>
> S2Graph also interoperates with several existing Apache
> projects(HBase, Spark) to provide way to merge real time events and
> batch processed data using property graph data model.
>
> Many developers are running their own domain specific API servers to
> serve their data products, but graph model is general and S2Graph API
> fully support traverse on graph, so it can be used as scalable general
> purpose API serving layer for various domains.
> As long as data can be modeled as graph, then users can avoid tedious
> work for developing customized API servers by using S2Graph.
>
> == Initial Goals ==
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is
> accomplished, we plan for incremental development and releases that
> follow the Apache guidelines.
>
> == Current Status ==
>
> === Meritocracy ===
> S2Graph operated on meritocratic principles from the get go.
> Currently, all the discussions pertaining to S2Graph development are
> public on Github. The current incubation
> proposal includes the major code contributors to S2Graph. Several
> additional people have worked on the S2graph codebase for industry use
> cases and would be interested in becoming committers. We are starting
> with a small committer group and we plan to add additional committers
> following an open merit-based decision process during the incubation
> phase.
>
> === Community ===
> We have already begun building a community but at this time the
> community consists only of S2Graph developers – all Kakao employees –
> and prospective users.
> S2Graph seeks to develop developer and user communities during incubation.
>
> === Core Developers ===
> S2Graph is currently being designed and developed by 2 engineers from
> Kakao. - Doyung Yoon, Deawon Jeong.
>
> === Alignment ===
> Our proposed S2Graph effort aligns closely with Apache HBase. The
> HBase project perimeter is denoted by a simple byte-array based
> Create, Read, Update, Delete and Scan APIs with no current plans to
> extend beyond this bounds.
>
> S2Graph complements this with a higher level API for property graph model.
>
> S2Graph was designed to offer scalable distributed graph database skin
> over HBase from the beginning in order to provide property graph model
> and breadth first search, and continue to focus on providing graph
> model.
>
> == Known Risks ==
> === Orphaned Products ===
> The core developers of S2Graph team plan to work full time on this
> project. There is very little risk of S2Graph getting orphaned since
> at least one large company (Kakao) is 

IP clearance for properly licensed code

[Todd Lipcon]

Hi all,

Another hopefully simple question:

The Mentor guide contains the following text:

>
> Existing codebases need to be imported through the standard IP clearance
> process. This means that a Software Grant Agreement (SGA
> ) or Contributor License
> Agreement (CLA ) need to be
> submitted for all copyright owners. This process may take a while so it is
> best to start as soon as the podling is accepted.


How does this rule apply to sections of code that are released publicly
under a suitable license (eg Apache/BSD/MIT) but were originally written
from a different context? For example, I am working on an incubation
proposal for a project that includes portions of code copied from the
Chromium open source project, which is released under a BSD license but
holds a copyright notice by "The Chromium Authors". It's unlikely that
these authors would submit the appropriate paperwork to the ASF.

Assuming that the imported project retains the notice of the original
copyright, and the commits which import the code suitably track the
provenance of the code, my understanding is this is acceptable under the
licenses and foundation policy. However, the text in the mentor guide seems
to indicate otherwise.

Thanks
Todd

Re: Releases during incubation?

[Todd Lipcon]

Thanks, Joe!

-Todd

On Mon, Nov 9, 2015 at 5:22 PM, Joe Schaefer  wrote:

> Subversion cut a release while in incubation on their old system.
> Shouldn't pose a problem for others.
>
> On Mon, Nov 9, 2015 at 8:03 PM, Todd Lipcon  wrote:
>
> > Hey folks,
> >
> > Hopefully quick policy question here:
> >
> > Once a project is under proposal for incubation, what is the foundation
> > policy on that project making releases outside of Apache from its current
> > home?
> >
> > For example, suppose there's an open source project FooBar, with a public
> > release FooBar 1.0.0 in use by various people out in the world. FooBar is
> > then proposed to the incubator. During the discussion/voting timeframe,
> > someone discovers a bug in FooBar 1.0.0, and the team would like to
> release
> > FooBar 1.0.1 from the project's current home (eg github). Would this be
> an
> > issue?
> >
> > More controversial variant:
> >
> > How about early during the incubation period, while the project is still
> in
> > the process of transitioning the necessary infrastructure, etc, into the
> > ASF repositories? Assuming that the project is making good faith efforts
> > towards making a release compatible with ASF guidelines, would it be
> > allowed to make "external" releases during this initial period of
> > incubation, for the purposes of bug fixes?
> >
> > Thanks
> > Todd
> >
>

Wiki access

[Nick Kew]

I have a incubator-wiki account "niq", but no current
write access.  Can someone with the relevant karma
please enable me?

Thanks,

-- 
Nick Kew


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

Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[Luke Han]

Forwarding my vote from dev@:

+1 non-binding


Best Regards!
-

Luke Han

On Tue, Nov 10, 2015 at 6:00 AM, Henry Saputra 
wrote:

> - Signature files look good
> - Hash files look good
> - LICENSE file looks good
> - NOTICE file looks good
> - DISCLAIMER files exists
> - Source compiled successfully
> - NO 3rd party executables in source artifact
> - Source files has correct Apache header
>
> +1 (binding)
>
> On Sat, Nov 7, 2015 at 4:46 PM, ShaoFeng Shi 
> wrote:
> > Hi all,
> >
> > The Apache Kylin community has voted on and approved a proposal to
> release
> > Apache Kylin 1.1.1-incubating. This release only includes license
> cleanup,
> > no Java code change; For more information please check KYLIN-999.
> >
> > Proposal:
> > http://s.apache.org/kylin-1.1.1-vote_rc1
> >
> > Vote result:
> > 7 binding +1 votes
> > 9 non-binding +1 votes
> > No -1 votes
> > http://s.apache.org/kylin-1.1.1-result_rc1
> >
> >
> > The commit to be voted upon:
> >
> https://github.com/apache/incubator-kylin/commit/708ea38d7f764048e67e8e1ee8a13955983d12ba
> >
> > Its hash is 708ea38d7f764048e67e8e1ee8a13955983d12ba.
> >
> > The artifacts to be voted on are located here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1.1-incubating-rc1/
> >
> > The hashes of the artifacts are as follows:
> > apache-kylin-1.1.1-incubating-src.tar.gz.md5
> > ff942b2eba870b04552bc8c8dace5517
> > apache-kylin-1.1.1-incubating-src.tar.gz.sha1
> > cc8990ba7821b02f4bf6da5f870b30a915881535
> >
> > A staged Maven repository is available for review at:
> > https://repository.apache.org/content/repositories/orgapachekylin-1013/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/shaofengshi.asc
> >
> > Pursuant to the Releases section of the Incubation Policy and with
> > the endorsement of our mentors we would now like to request
> > the permission of the Incubator PMC to publish the release. The vote
> > is open for 72 hours, or until the necessary number of votes (3 +1)
> > is reached.
> >
> > [ ] +1 Release this package
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> >
> > Shaofeng Shi, on behalf of Apache Kylin PPMC
> > shaofeng...@apache.org
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Draft report November 2015 -- please review

[Marvin Humphrey]

> Apex

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The project is still using the original Atlassian instance of JIRA.
>   INFRA-10144 has tracked the Apache JIRA migration request since August.

JIRA imports are non-trivial and Apex is not the first project to get
snagged.  I would expect a resolution eventually through interaction between
Infra and podling contributors or Mentors without requiring escalation to
IPMC or Board, but thanks for keeping the IPMC/Board informed.

>   Chris Nauroth (cnauroth):

> I would like to request that the infra team prioritize completion of
> the JIRA migration tracked in INFRA-10144.

Anyone have suggestions about the most constructive ways to for Apex to
pursue this?

> AsterixDB

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The discussion on the use of an external Gerrit instance for code
>   reviews is considered to be resolved.
>   The current workflow ensures that
>   a) The ASF git repository is the canonical repository for the project.
>   b) Only committers can manually commit changes to the ASF git
>  repository.
>   c) All discussions on the Gerrit instance are sent to
>  notificati...@asterixdb.incubator.apache.org.
>   While it would be good to also have the Gerrit instance run on ASF
>   hardware, this is neither necessary to document the provenance of the
>   code nor to enable list members to follow and participate in the
>   activities of the project. Also, there seems to be no infra capacity
>   to provide a Gerrit service.

Thanks for the update, AsterixDB.  The broader issue is being discussed
extensively elsewhere within the Foundation.

Unfortunately most of the debate is on private lists (board@apache,
members@apache, operations@apache), which excludes stakeholders such as most
contributors to AsterixDB -- among many others.  Personally, this bothers me
quite a bit, as it clashes with what we claim are Apache ideals of openness.
Hopefully efforts to move the conversations public will succeed sooner
rather than later.

I suggest that interested parties subscribe to infrastructure-dev@apache,
since that is the public venue where some discussion has been taking place.
Discussions may also emerge on legal-discuss@apache or dev@community.apache.

> 
> Blur
>
> Blur is a search platform capable of searching massive amounts of data
> in a cloud computing environment.
>
> Blur has been incubating since 2012-07-24.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Greater community involvement.
>   2. Produce releases.
>   3.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>  - No
>
> How has the community developed since the last report?
>
>  - Subscriptions: user@ - 55[0]; dev@ - 70[+3]
>
> How has the project developed since the last report?
>
>  - A few additional features, and bug fixes.
>
> Date of last release:
>
>   2014-07-29
>
> When were the last committers or PMC members elected?
>
>   2014-07-28
>
> Signed-off-by:
>
>   [ ](blur) Doug Cutting
>   [X](blur) Patrick Hunt
>   [ ](blur) Tim Williams
>
> Shepherd/Mentor notes:
>
>
>

This report yields very little insight about the state of Blur's community.
There are many excellent reports from other podlings this month; perhaps
Blur could look to them for inspiration.

> Climate Model Diagnostic Analyzer

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The project is still in its nascence and the PPMC is still learning the
>   Apache way and moving out of JPL/CMU centric development. The project team
>   wants to do a good job they are just moving along slowly.

Thanks for the update, CMDA -- we look forward to continued progress.  It's
great to have you here in the Incubator, but please don't stay too long! ;)

> Cotton

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   Development of Cotton has largely been inactive for the last two months,
>   due to limited time from the original developer and community engagements
>   including MesosCon Seattle and MesosCon Europe.
>
> How has the community developed since the last report?
>
>   There has been limited participation on the mailing lists and JIRA,
>   however a discussion on the private@ list was established about this issue
>   and there's a desire to keep the project in the incubator and be more
>   proactive in building community in the coming months.

Kudos for transparency, Cotton.  Hope that things go well -- building a
community takes hard work!

> DataFu

> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   * Performing the initial release remains the most important milestone.

Nice report in general, DataFu.  This bullet point isn't really an issue that
the IPMC or Board needs to be monitor closely though.  For future 

Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[Julian Hyde]

Forwarding my vote from dev@:

+1 binding

Julian


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

Re: [VOTE] Release Apache Slider 0.81.1-incubating

[Gour Saha]

Hi Jean,

If possible, would you be able to do the mentor sign off for Slider?
Really appreciate it.

-Gour




On 10/29/15, 3:44 AM, "Jean-Baptiste Onofré"  wrote:

>+1 (binding)
>
>Regards
>JB
>
>On 10/28/2015 06:40 PM, Yu Liu wrote:
>> Vote: +1
>>
>> Thank you
>> 
>> From: Jon Maron 
>> Sent: Wednesday, October 28, 2015 6:42 AM
>> To: d...@slider.incubator.apache.org
>> Cc: general@incubator.apache.org
>> Subject: Re: [VOTE] Release Apache Slider 0.81.1-incubating
>>
>> If you¹re looking for an expandable zip/tar file:
>>https://repository.apache.org/content/repositories/orgapacheslider-1008/o
>>rg/apache/slider/slider-assembly/0.81.1-incubating/
>>
>> ‹ Jon
>>
>>> On Oct 28, 2015, at 12:25 AM, Rohith Sharma K S
>>> wrote:
>>>
>>> Hi
>>>
>>> Can anyone tell where is the RC release available link?
>>> OR
>>> If voting is completed, where do I get release? Any link is
>>>appreciated!!
>>> OR
>>> Should I build from source to verify RC?
>>>
>>> Thanks & Regards
>>> Rohith Sharma K S
>>>
>>> -Original Message-
>>> From: Gour Saha [mailto:gs...@hortonworks.com]
>>> Sent: 28 October 2015 03:57
>>> To: general@incubator.apache.org
>>> Cc: 
>>> Subject: Re: [VOTE] Release Apache Slider 0.81.1-incubating
>>>
>>> +1 (binding)
>>>
>>> Confirmed and signed Jon's PGP fingerprint to MIT PGP repo as well.
>>>
>>>
>>> -Gour
>>>
>>> On 10/26/15, 11:43 AM, "Jon Maron"  wrote:
>>>
 Hello,

 This is a call for a vote for releasing Apache Slider
0.81.1-incubating.

 This is a source release.

 Summary of fixes: http://s.apache.org/sgG Release Notes:
 http://s.apache.org/ZZP Vote thread: http://s.apache.org/Ejv
 Results: http://s.apache.org/ufJ

 Staged artifacts:
 
https://repository.apache.org/content/repositories/orgapacheslider-1008
 /or
 g/apache/slider

 Git source:
 
https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit
 ;h= a9b1d659c642ab7eb7b21ecbae97f805259c9f9f
 SHA1: a9b1d659c642ab7eb7b21ecbae97f805259c9f9f
 Tag: slider-0.81.1-incubating

 PGP key:
 http://pgp.mit.edu:11371/pks/lookup?op=vindex=jma...@apache.org

 Basic build/test instructions:
 http://slider.incubator.apache.org/developing/building.html

 Please vote on releasing this package as Apache Slider
0.81.1-incubating.

 This vote will be open for 72 hours.

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thank You,
 The Apache Slider Team

 -
 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
>>
>
>-- 
>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
>
>


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

Re: Unsubscribe not working

[Konstantin Boudnik]

Potentially it might mean that you have also subscribed from other mail aliases?

On Sun, Nov 08, 2015 at 07:45PM, Robert Kausch - US wrote:
> Sorry for having to send this to the whole list, but I don't think the
> unsubscribe functionality is working. I've been trying for 10 days, and I'm
> still receiving email from the list. 
> 
> Sent from my iPhone
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


signature.asc
Description: Digital signature

Re: [DISCUSS] S2Graph Incubator Proposal

[Hyunsik Choi]

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  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  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 to
>> efficiently store user relation and user activities as one large graph
>> and provide unified query to traverse graph. It was open sourced on
>> Github about a 3 months ago in June 2015.
>>
>> Over time S2Graph, together with HBase as storage tier, has begun to
>> be adapted into various applications, such as messaging, social feeds,
>> realtime recommendations at Kakao.
>>
>> Users can benefit from S2Graph`s generalized high level API instead of
>> low-level key/value API for graph abstraction, just like Phoenix
>> provide SQL layer over HBase.
>>
>> == Rationale ==
>> Graph data(highly interconnected data) is very abundant and important
>> these days.
>> When users have a multitude of relationships, each with complex
>> properties associated with them, graph model is more intuitive and
>> efficient than tabular format(RDBMS).
>> There are many ASF projects that provide SQL layer, but there is no
>> ASF projects that provide scalable graph layer on existing hadoop echo
>> system.
>> When graph data grows to trillion edge scale, the process of
>> traversing takes a long time and costly. However, with the benefit of
>> HBase`s scalable architecture, S2Graph can traverse large graph in
>> breadth first search manner efficiently.
>>
>> S2Graph also interoperates with several existing Apache
>> projects(HBase, Spark) to provide way to merge real time events and
>> batch processed data using property graph data model.
>>
>> Many developers are running their own domain specific API servers to
>> serve their data products, but graph model is general and S2Graph API
>> fully support traverse on graph, so it can be used as scalable general
>> purpose API serving layer for various domains.
>> As long as data can be modeled as graph, then users can avoid tedious
>> work for developing customized API servers by using S2Graph.
>>
>> == Initial Goals ==
>> The initial goals will be to move the existing codebase to Apache and
>> integrate with the Apache development process. Once this is
>> accomplished, we plan for incremental development and releases that
>> follow the Apache guidelines.
>>
>> == Current Status ==
>>
>> === Meritocracy ===
>> S2Graph operated on meritocratic principles from the get go.
>> Currently, all the discussions pertaining to S2Graph development are
>> public on Github. The current incubation
>> proposal includes the major code contributors to S2Graph. Several
>> additional people have worked on the S2graph codebase for industry use
>> cases and would be interested in becoming committers. We are starting
>> with a small committer group and we plan to add additional committers
>> following an open merit-based decision process during the incubation
>> phase.
>>
>> === Community ===
>> We have already begun building a community but at this time the
>> community consists only of S2Graph developers – all Kakao employees –
>> and prospective users.
>> S2Graph seeks to develop developer and user communities during incubation.
>>
>> === Core Developers ===
>> S2Graph is currently being designed and developed by 2 engineers from
>> Kakao. - Doyung Yoon, Deawon Jeong.
>>
>> === Alignment ===
>> Our proposed S2Graph effort aligns closely with Apache HBase. 

Re: [DISCUSS] S2Graph Incubator Proposal

[Seetharam Venkatesh]

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  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 
> 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  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 to
> >> efficiently store user relation and user activities as one large graph
> >> and provide unified query to traverse graph. It was open sourced on
> >> Github about a 3 months ago in June 2015.
> >>
> >> Over time S2Graph, together with HBase as storage tier, has begun to
> >> be adapted into various applications, such as messaging, social feeds,
> >> realtime recommendations at Kakao.
> >>
> >> Users can benefit from S2Graph`s generalized high level API instead of
> >> low-level key/value API for graph abstraction, just like Phoenix
> >> provide SQL layer over HBase.
> >>
> >> == Rationale ==
> >> Graph data(highly interconnected data) is very abundant and important
> >> these days.
> >> When users have a multitude of relationships, each with complex
> >> properties associated with them, graph model is more intuitive and
> >> efficient than tabular format(RDBMS).
> >> There are many ASF projects that provide SQL layer, but there is no
> >> ASF projects that provide scalable graph layer on existing hadoop echo
> >> system.
> >> When graph data grows to trillion edge scale, the process of
> >> traversing takes a long time and costly. However, with the benefit of
> >> HBase`s scalable architecture, S2Graph can traverse large graph in
> >> breadth first search manner efficiently.
> >>
> >> S2Graph also interoperates with several existing Apache
> >> projects(HBase, Spark) to provide way to merge real time events and
> >> batch processed data using property graph data model.
> >>
> >> Many developers are running their own domain specific API servers to
> >> serve their data products, but graph model is general and S2Graph API
> >> fully support traverse on graph, so it can be used as scalable general
> >> purpose API serving layer for various domains.
> >> As long as data can be modeled as graph, then users can avoid tedious
> >> work for developing customized API servers by using S2Graph.
> >>
> >> == Initial Goals ==
> >> The initial goals will be to move the existing codebase to Apache and
> >> integrate with the Apache development process. Once this is
> >> accomplished, we plan for incremental development and releases that
> >> follow the Apache guidelines.
> >>
> >> == Current Status ==
> >>
> >> === Meritocracy ===
> >> S2Graph operated on meritocratic principles from the get go.
> >> Currently, all the discussions pertaining to S2Graph development are
> >> public on Github. The current incubation
> >> proposal includes the major code contributors to S2Graph. Several
> >> additional people have worked on the S2graph codebase for industry use
> >> cases and would be interested in becoming committers. We are starting
> >> with a small committer group and we plan to add additional committers
> >> following an open merit-based decision process during the incubation
> >> phase.
> >>
> >> === Community ===
> >> We have already begun building a community but at this time the
> >> community consists only of 

Re: [VOTE] Release Apache Kylin 1.1.1 (incubating)

[ShaoFeng Shi]

Thanks Luke for answering this for me; yes the commit (619499b) is
automatically made by the maven, and I picked the last commit made by human
as the base to vote; Just let me know if this is an issue and I can send an
updated version soon. Thanks!

2015-11-09 8:33 GMT+08:00 Luke Han :

> Hi John,
> The commit (619499b) you mentioned is auto generated by maven release
> tool during script execution which changed the version to remove SNAPSHOT
> just followed latest commit: 708ea3 (by committer).
>  The main change of this release is to totally remove Google Font,
> please refer to KYLIN-999 for more detail [1] and v1.1.1-incubating commit
> history [2]
>
>
>
> Thanks.
>
>
> [1]. https://issues.apache.org/jira/browse/KYLIN-999
> [2].
> https://github.com/apache/incubator-kylin/commits/kylin-1.1.1-incubating
>
>
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Mon, Nov 9, 2015 at 12:23 AM, John D. Ament 
> wrote:
>
> > It's a bit confusing, because I would have expected the vote to be based
> on
> > commit
> >
> >
> https://github.com/apache/incubator-kylin/commit/6a9499b4d0fabb54211a8a536c2e18d3fe8b4a5d
> >
> > If you follow the commit above, then only KYLIN-999 is included in this
> > release (over 1.1 release).  Whereas if you follow 708ea3, much more
> > content is included.  Can you clarify which commit is accurate?
> >
> > John
> >
> > On Sat, Nov 7, 2015 at 7:46 PM ShaoFeng Shi 
> > wrote:
> >
> > > Hi all,
> > >
> > > The Apache Kylin community has voted on and approved a proposal to
> > release
> > > Apache Kylin 1.1.1-incubating. This release only includes license
> > cleanup,
> > > no Java code change; For more information please check KYLIN-999.
> > >
> > > Proposal:
> > > http://s.apache.org/kylin-1.1.1-vote_rc1
> > >
> > > Vote result:
> > > 7 binding +1 votes
> > > 9 non-binding +1 votes
> > > No -1 votes
> > > http://s.apache.org/kylin-1.1.1-result_rc1
> > >
> > >
> > > The commit to be voted upon:
> > >
> > >
> >
> https://github.com/apache/incubator-kylin/commit/708ea38d7f764048e67e8e1ee8a13955983d12ba
> > >
> > > Its hash is 708ea38d7f764048e67e8e1ee8a13955983d12ba.
> > >
> > > The artifacts to be voted on are located here:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1.1-incubating-rc1/
> > >
> > > The hashes of the artifacts are as follows:
> > > apache-kylin-1.1.1-incubating-src.tar.gz.md5
> > > ff942b2eba870b04552bc8c8dace5517
> > > apache-kylin-1.1.1-incubating-src.tar.gz.sha1
> > > cc8990ba7821b02f4bf6da5f870b30a915881535
> > >
> > > A staged Maven repository is available for review at:
> > >
> https://repository.apache.org/content/repositories/orgapachekylin-1013/
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/shaofengshi.asc
> > >
> > > Pursuant to the Releases section of the Incubation Policy and with
> > > the endorsement of our mentors we would now like to request
> > > the permission of the Incubator PMC to publish the release. The vote
> > > is open for 72 hours, or until the necessary number of votes (3 +1)
> > > is reached.
> > >
> > > [ ] +1 Release this package
> > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > > Shaofeng Shi, on behalf of Apache Kylin PPMC
> > > shaofeng...@apache.org
> > >
> >
>



-- 
Best regards,

Shaofeng Shi

Re: [DISCUSS] S2Graph Incubator Proposal

[Hyunsik Choi]

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
 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  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 
>> 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  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 to
>> >> efficiently store user relation and user activities as one large graph
>> >> and provide unified query to traverse graph. It was open sourced on
>> >> Github about a 3 months ago in June 2015.
>> >>
>> >> Over time S2Graph, together with HBase as storage tier, has begun to
>> >> be adapted into various applications, such as messaging, social feeds,
>> >> realtime recommendations at Kakao.
>> >>
>> >> Users can benefit from S2Graph`s generalized high level API instead of
>> >> low-level key/value API for graph abstraction, just like Phoenix
>> >> provide SQL layer over HBase.
>> >>
>> >> == Rationale ==
>> >> Graph data(highly interconnected data) is very abundant and important
>> >> these days.
>> >> When users have a multitude of relationships, each with complex
>> >> properties associated with them, graph model is more intuitive and
>> >> efficient than tabular format(RDBMS).
>> >> There are many ASF projects that provide SQL layer, but there is no
>> >> ASF projects that provide scalable graph layer on existing hadoop echo
>> >> system.
>> >> When graph data grows to trillion edge scale, the process of
>> >> traversing takes a long time and costly. However, with the benefit of
>> >> HBase`s scalable architecture, S2Graph can traverse large graph in
>> >> breadth first search manner efficiently.
>> >>
>> >> S2Graph also interoperates with several existing Apache
>> >> projects(HBase, Spark) to provide way to merge real time events and
>> >> batch processed data using property graph data model.
>> >>
>> >> Many developers are running their own domain specific API servers to
>> >> serve their data products, but graph model is general and S2Graph API
>> >> fully support traverse on graph, so it can be used as scalable general
>> >> purpose API serving layer for various domains.
>> >> As long as data can be modeled as graph, then users can avoid tedious
>> >> work for developing customized API servers by using S2Graph.
>> >>
>> >> == Initial Goals ==
>> >> The initial goals will be to move the existing codebase to Apache and
>> >> integrate with the Apache development process. Once this is
>> >> accomplished, we plan for incremental development and releases that
>> >> follow the Apache guidelines.
>> >>
>> >> == Current Status ==
>> >>
>> >> === Meritocracy ===
>> >> S2Graph operated on meritocratic principles from the get go.
>> >> Currently, all the discussions pertaining to S2Graph development are
>> >> public on Github. The current incubation
>> >> proposal includes the major code contributors to S2Graph. Several
>> >> 

Releases during incubation?

[Todd Lipcon]

Hey folks,

Hopefully quick policy question here:

Once a project is under proposal for incubation, what is the foundation
policy on that project making releases outside of Apache from its current
home?

For example, suppose there's an open source project FooBar, with a public
release FooBar 1.0.0 in use by various people out in the world. FooBar is
then proposed to the incubator. During the discussion/voting timeframe,
someone discovers a bug in FooBar 1.0.0, and the team would like to release
FooBar 1.0.1 from the project's current home (eg github). Would this be an
issue?

More controversial variant:

How about early during the incubation period, while the project is still in
the process of transitioning the necessary infrastructure, etc, into the
ASF repositories? Assuming that the project is making good faith efforts
towards making a release compatible with ASF guidelines, would it be
allowed to make "external" releases during this initial period of
incubation, for the purposes of bug fixes?

Thanks
Todd

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ali Lown]

Hi Ian,

Perhaps you could provide some more information on exactly what steps
you took to the wave-dev list, where we can try to help you with
getting this to work on your machine, I doubt everyone else on
incubator-general is quite as interested...

Using a different Java version on Windows normally just requires
changing the path system variable to reflect the location of the JDK
you are interested in using.

Ali

On 9 November 2015 at 19:08, Ian Dunlop  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> I did try to use the CLI to build it but ran into java issues since
> windows seems determined to use java 8 and i can only get java 7 to
> run inside eclipse. Getting windows to use an older version of java
> seems like a fairly difficult or poorly documented task nowadays.
> Suggestions welcome (though as noted earlier they may belong a a
> different list).
>
> Cheers,
>
> Ian
>
> On 08/11/15 19:41, John D. Ament wrote:
>> Typically speaking, releases should compile.  If there are steps
>> required to make it compile they should be shared. On Nov 8, 2015
>> 14:33, "Upayavira"  wrote:
>>
>>> Ian,
>>>
>>> Please bear in mind that this release vote is to validate the
>>> legal aspects of the release, not its technical merits. Technical
>>> merits can be resolved in subsequent releases.
>>>
>>> Upayavira
>>>
>>> On Fri, Nov 6, 2015, at 02:51 PM, Ian Dunlop wrote:
>> Hello,
>>
>> I'll give it at 0 the moment since I encountered a build issue. I
>> downloaded the src zip and imported the code into Eclipse Mars
>> (4.50) with jdk 1.7.0_79 & ANT 1.9.4 but found the following
>> issues:
>>
>> 1) BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:28:
>> Cannot find
>> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path}
>> imported from C:\Users\idunlop\workspace\waveinabox\build.xml
>>
>> Resolved by commenting out
>>
>> 
>>
>>  
>>
>> and tried again
>>
>> 2)
>>
>> BUILD FAILED Target "define-gxpc" does not exist in the project
>> "waveinabox". It is used from target "gen-gxp".
>>
>> Resolved by removing define-gxpc from
>>
>> > depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp">
>> > destdir="${gen.dir}/gxp" target="org.waveprotocol.box.server.gxp"
>> />  
>>
>> 3)
>>
>> BUILD FAILED C:\Users\idunlop\workspace\waveinabox\build.xml:120:
>> Problem: failed to create task or type buildproto Cause: The name
>> is undefined. Action: Check the spelling. Action: Check that any
>> custom tasks/types have been declared. Action: Check that any
>> / declarations have taken place.
>>
>> At that point I figured it best to report the issues here:
>>
>> Is there a procedure for building in eclipse, am I missing an ant
>> setting somewhere?
>>
>> So, apart fromn the compile issue everything else looks good:
>>
>> signatures are good artifact/hashes good DISCLAIMER OK LICENCE OK
>> NOTICE OK
>>
>> Cheers,
>>
>> Ian
>>
>>
>>
>> On 04/11/2015 07:14, Justin Mclean wrote:
>> Hi,
>>
>> +1 binding.
>>
>> Could you please fix the LICENCE Appendix in the next
>> release. The text should be "Copyright [] [name of
>> copyright owner]” not "Copyright 2013 The Apache Software
>> Foundation”.
>>
>> I checked: - artefact has incubating in name - signatures
>> and hashes good - DISCLAIMER exists - LICENSE  has minor
>> issue with the copyright in the appendix. Not required but
>> it could also use the sort form in LICENSE [1] particularly
>> as you bundle the software LICENSE files. - NOTICE good. -
>> All source files have Apache headers - No unexpected binary
>> file in source release (but see below) - can compile from
>> source - test pass
>>
>> I notice there’s a couple of photographs in the source
>> release, I assume you have permission from the person who
>> took them to use these? IF so you may want to put that in
>> the LICENSE.
>>
>> There's a number of binary file without extensions in
>> /thumbnail_patterns/ but they all look to be PNGs is this
>> the case? Where did these images come from?
>>
>> I had a quick look at the binary release and the LICENCE
>> and NOTICE appear comprehensive. I didn;t do a though
>> check. I did notice that the year is incorrect in the
>> NOTICE file and LICENSE appendix has the same issue.  It’s
>> actually wrong here as non ASF Apache licensed software is
>> mentioned. There no need to mean Apache licensed software
>> in the LICENCE but no harm is done by donning so. [2]
>>
>> Thanks, Justin
>>
>> 1.
>> http://www.apache.org/dev/licensing-howto.html#permissive-deps
>>
>>
> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
>>
>>
>>
>> --
> - ---
>>
>>
>>
>>
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For 

Re: Releases during incubation?

[Joe Schaefer]

Subversion cut a release while in incubation on their old system.
Shouldn't pose a problem for others.

On Mon, Nov 9, 2015 at 8:03 PM, Todd Lipcon  wrote:

> Hey folks,
>
> Hopefully quick policy question here:
>
> Once a project is under proposal for incubation, what is the foundation
> policy on that project making releases outside of Apache from its current
> home?
>
> For example, suppose there's an open source project FooBar, with a public
> release FooBar 1.0.0 in use by various people out in the world. FooBar is
> then proposed to the incubator. During the discussion/voting timeframe,
> someone discovers a bug in FooBar 1.0.0, and the team would like to release
> FooBar 1.0.1 from the project's current home (eg github). Would this be an
> issue?
>
> More controversial variant:
>
> How about early during the incubation period, while the project is still in
> the process of transitioning the necessary infrastructure, etc, into the
> ASF repositories? Assuming that the project is making good faith efforts
> towards making a release compatible with ASF guidelines, would it be
> allowed to make "external" releases during this initial period of
> incubation, for the purposes of bug fixes?
>
> Thanks
> Todd
>

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

[Ali Lown]

Hi Justin,

Thanks for taking a look at the RC, we will fix these minor points for
the next release.

> I notice there’s a couple of photographs in the source release, I assume you 
> have permission from the person who took them to use these? IF so you may 
> want to put that in the LICENSE.

Are you referring to the screenshots under war/static/? Those are
untouched since the migration from Google, so fall under the license
from them.

> There's a number of binary file without extensions in /thumbnail_patterns/ 
> but they all look to be PNGs is this the case? Where did these images come 
> from?

These icons are from the Tango Desktop Project, which licenses them
into the public domain, who are mentioned in THANKS. I can mention
this explicitly in THANKS if preferable?


Are there any other IPMC able to take a look at this release, as I
don't seem to have enough votes yet?

Regards,
Ali

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