Re: [VOTE] Graduate Apache Geode (incubating)

[Avinash Dongre]

+1

On Mon, Nov 7, 2016 at 12:35 PM, Sergio Fernández  wrote:

> +1
>
> good luck, guys!
>
> On Sun, Nov 6, 2016 at 11:42 PM, John D. Ament 
> wrote:
>
> > +1
> >
> > On Nov 6, 2016 15:58, "Roman Shaposhnik"  wrote:
> >
> > > Hi!
> > >
> > > after a very positive discussion in the Geode community
> > > and at the IPMC level:
> > > http://markmail.org/message/z4prj62hr7rn6cu6
> > > I'd like to bring the following resolution for a formal vote.
> > >
> > > Please vote on the resolution pasted below to graduate
> > > Apache Geode from the incubator to top level project.
> > >
> > > [ ] +1 Graduate Apache Geode from the Incubator.
> > > [ ] +0 Don't care.
> > > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Many thanks to our mentors and everyone else for the support,
> > > Roman (on behalf of the Apache Geode PPMC).
> > >
> > > Resolution:
> > >
> > > Establish the Apache Geode Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best
> > > interests of the Foundation and consistent with the
> > > Foundation's purpose to establish a Project Management
> > > Committee charged with the creation and maintenance of
> > > open-source software, for distribution at no charge to the
> > > public, related to a data management platform that provides
> > > real-time, consistent access to data-intensive applications
> > > throughout widely distributed cloud architectures.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > Committee (PMC), to be known as the "Apache Geode Project",
> > > be and hereby is established pursuant to Bylaws of the
> > > Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Geode Project be and hereby is
> > > responsible for the creation and maintenance of software
> > > related to a data management platform that provides real-time,
> > > consistent access to data-intensive applications throughout
> > > widely distributed cloud architectures.
> > >
> > > RESOLVED, that the office of "Vice President, Apache Geode" be
> > > and hereby is created, the person holding such office to
> > > serve at the direction of the Board of Directors as the chair
> > > of the Apache Geode Project, and to have primary responsibility
> > > for management of the projects within the scope of
> > > responsibility of the Apache Geode Project; and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and
> > > hereby are appointed to serve as the initial members of the
> > > Apache Geode Project:
> > >
> > > * Anilkumar Gingade 
> > > * Anthony Baker 
> > > * Ashvin Agrawal 
> > > * Avinash Dongre 
> > > * Barry Oglesby < bogle...@apache.org>
> > > * Bruce Schuchardt 
> > > * Dan Smith 
> > > * Darrel Schneider 
> > > * Dave Barnes 
> > > * Eric Shu 
> > > * Greg Chase 
> > > * Hitesh Khamesra 
> > > * Jason Huynh 
> > > * Jens Deppe 
> > > * Jianxia Chen 
> > > * Jinmei Liao 
> > > * John Blum 
> > > * Karen Miller 
> > > * Konstantin Boudnik 
> > > * Kirk Lund 
> > > * Mark Bretl 
> > > * Nabarun Nag 
> > > * Niall Pemberton 
> > > * Nitin Lamba 
> > > * Roman Shaposhnik 
> > > * Sai Boorlagadda 
> > > * Swapnil Bawaskar 
> > > * Udo Kohlmeyer 
> > > * William Markito 
> > > * Xiaojian Zhou 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> > > be appointed to the office of Vice President, Apache Geode, to
> > > serve in accordance with and subject to the direction of the
> > > Board of Directors and the Bylaws of the Foundation until
> > > death, resignation, retirement, removal or disqualification,
> > > or until a successor is appointed; and be it further
> > >
> > > RESOLVED, that the initial Apache Geode PMC be and hereby is
> > > tasked with the creation of a set of bylaws intended to
> > > encourage open development and increased participation in the
> > > Apache Geode Project; and be it further
> > >
> > > RESOLVED, that the Apache Geode Project be and hereby
> > > is tasked with the migration and rationalization of the Apache
> > > Incubator Geode podling; and be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache
> > > Incubator Geode podling encumbered upon the Apache Incubator
> > > Project are hereafter discharged.
> > >
> > > 

Re: [VOTE] Graduate Apache Geode (incubating)

[Sergio Fernández]

+1

good luck, guys!

On Sun, Nov 6, 2016 at 11:42 PM, John D. Ament 
wrote:

> +1
>
> On Nov 6, 2016 15:58, "Roman Shaposhnik"  wrote:
>
> > Hi!
> >
> > after a very positive discussion in the Geode community
> > and at the IPMC level:
> > http://markmail.org/message/z4prj62hr7rn6cu6
> > I'd like to bring the following resolution for a formal vote.
> >
> > Please vote on the resolution pasted below to graduate
> > Apache Geode from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Geode from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> > Roman (on behalf of the Apache Geode PPMC).
> >
> > Resolution:
> >
> > Establish the Apache Geode Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of the Foundation and consistent with the
> > Foundation's purpose to establish a Project Management
> > Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to the
> > public, related to a data management platform that provides
> > real-time, consistent access to data-intensive applications
> > throughout widely distributed cloud architectures.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Geode Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Geode Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a data management platform that provides real-time,
> > consistent access to data-intensive applications throughout
> > widely distributed cloud architectures.
> >
> > RESOLVED, that the office of "Vice President, Apache Geode" be
> > and hereby is created, the person holding such office to
> > serve at the direction of the Board of Directors as the chair
> > of the Apache Geode Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Geode Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and
> > hereby are appointed to serve as the initial members of the
> > Apache Geode Project:
> >
> > * Anilkumar Gingade 
> > * Anthony Baker 
> > * Ashvin Agrawal 
> > * Avinash Dongre 
> > * Barry Oglesby < bogle...@apache.org>
> > * Bruce Schuchardt 
> > * Dan Smith 
> > * Darrel Schneider 
> > * Dave Barnes 
> > * Eric Shu 
> > * Greg Chase 
> > * Hitesh Khamesra 
> > * Jason Huynh 
> > * Jens Deppe 
> > * Jianxia Chen 
> > * Jinmei Liao 
> > * John Blum 
> > * Karen Miller 
> > * Konstantin Boudnik 
> > * Kirk Lund 
> > * Mark Bretl 
> > * Nabarun Nag 
> > * Niall Pemberton 
> > * Nitin Lamba 
> > * Roman Shaposhnik 
> > * Sai Boorlagadda 
> > * Swapnil Bawaskar 
> > * Udo Kohlmeyer 
> > * William Markito 
> > * Xiaojian Zhou 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> > be appointed to the office of Vice President, Apache Geode, to
> > serve in accordance with and subject to the direction of the
> > Board of Directors and the Bylaws of the Foundation until
> > death, resignation, retirement, removal or disqualification,
> > or until a successor is appointed; and be it further
> >
> > RESOLVED, that the initial Apache Geode PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache Geode Project; and be it further
> >
> > RESOLVED, that the Apache Geode Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Geode podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator Geode podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: 

Re: [VOTE] Graduate Apache Geode (incubating)

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 11/06/2016 09:58 PM, Roman Shaposhnik wrote:

Hi!

after a very positive discussion in the Geode community
and at the IPMC level:
http://markmail.org/message/z4prj62hr7rn6cu6
I'd like to bring the following resolution for a formal vote.

Please vote on the resolution pasted below to graduate
Apache Geode from the incubator to top level project.

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

This vote will be open for at least 72 hours.

Many thanks to our mentors and everyone else for the support,
Roman (on behalf of the Apache Geode PPMC).

Resolution:

Establish the Apache Geode Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to a data management platform that provides
real-time, consistent access to data-intensive applications
throughout widely distributed cloud architectures.

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

RESOLVED, that the Apache Geode Project be and hereby is
responsible for the creation and maintenance of software
related to a data management platform that provides real-time,
consistent access to data-intensive applications throughout
widely distributed cloud architectures.

RESOLVED, that the office of "Vice President, Apache Geode" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Geode Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Geode Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Geode Project:

* Anilkumar Gingade 
* Anthony Baker 
* Ashvin Agrawal 
* Avinash Dongre 
* Barry Oglesby < bogle...@apache.org>
* Bruce Schuchardt 
* Dan Smith 
* Darrel Schneider 
* Dave Barnes 
* Eric Shu 
* Greg Chase 
* Hitesh Khamesra 
* Jason Huynh 
* Jens Deppe 
* Jianxia Chen 
* Jinmei Liao 
* John Blum 
* Karen Miller 
* Konstantin Boudnik 
* Kirk Lund 
* Mark Bretl 
* Nabarun Nag 
* Niall Pemberton 
* Nitin Lamba 
* Roman Shaposhnik 
* Sai Boorlagadda 
* Swapnil Bawaskar 
* Udo Kohlmeyer 
* William Markito 
* Xiaojian Zhou 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
be appointed to the office of Vice President, Apache Geode, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Geode PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Geode Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Geode podling encumbered upon the Apache Incubator
Project are hereafter discharged.

-
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

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Luciano Resende]

On Sun, Nov 6, 2016 at 7:36 PM, Justin Mclean 
wrote:

> Hi,
>
> > I understand that the most important thing for Apache is the source
> release
> > artifact, but that does not prohibit a project from distributing
> > convenience binaries as long as they meet all the legal requirements
> > mandated by Apache.
>
> Which is fine but currently it is not clear (to an external person)
> exactly what is what in that directory and the VOTE email doesn’t clarify
> it.
>

Yes, it's a bit confusing, so maybe it's a matter of adding a README to
clarify what are the artifacts being released.


>
> > Also, the release structure hasn't changed much from
> > our previous release
>
> Which I asked about the last RC and got no reply. I took a guess but still
> not sure if it was right or not and if everything got reviewed.
>
>
Sorry for not getting back to you on the list of artifacts, I have
documented them on the following thread on the SystemML mailing list:
https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01121.html

Also, from previous RC the community removed one jar from the release
(*-standalone.jar) and all other artifacts were reviewed by the SystemML
podling members. We are also looking into reducing the number of
distributed artifacts for our next release which should avoid further
confusion on the matter.


> Thanks,
> Justin




-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Justin Mclean]

Hi,

> I understand that the most important thing for Apache is the source release
> artifact, but that does not prohibit a project from distributing
> convenience binaries as long as they meet all the legal requirements
> mandated by Apache.

Which is fine but currently it is not clear (to an external person) exactly 
what is what in that directory and the VOTE email doesn’t clarify it.

> Also, the release structure hasn't changed much from
> our previous release

Which I asked about the last RC and got no reply. I took a guess but still not 
sure if it was right or not and if everything got reviewed.

Thanks,
Justin

Re: [DISCUSS] OpenWhisk Proposal

[Henry Saputra]

Ah, I didnt know ASF infra is ok to let Github as main source repo for a
podling.

I stand corrected.

- Henry

On Sun, Nov 6, 2016 at 1:06 AM, Greg Stein  wrote:

> On Sat, Nov 5, 2016 at 4:44 PM, Henry Saputra 
> wrote:
>
> > I second John, about Github uses.
> >
> > The statement "As a community we would like to keep the master repository
> > as well as issue tracking on GitHub
> > " at currently stand is a
> no-no
> > and putting in proposal would make it as goal which at this time not an
> > option in ASF infra.
> >
>
> As a *podling*, their use of GitHub is an acceptable option within ASF
> Infra. [1]
>
> As a TLP, it is NOT.
>
> Thus, when they want to graduate: either Infra has ready to give any TLP
> the option of using GitHub as their primary focal point of development (and
> OpenWhisk gets to use that option) ... or OpenWhisk must move to the
> ASF-supported, non-GitHub option.
>
> Infra is hoping to provide the GitHub option, but we have no date. We have
> development to do, we have risks that we can't do what is needed, etc etc.
> If OpenWhisk reaches a discussion about graduation, and Infra has not
> completed such work, then the OpenWhisk community will have a decision on
> wait or shift their development focal point.
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>
> [1] only OpenWhisk. at this time, no other podling is approved for such
> deployment, from an Infra standpoint. ... and as John notes: IPMC is
> ultimately in charge of how podlings operate. I merely state that Infra
> will support this concrete case, which I believe is a good experiment.
> there are things to learn about whether this will work/not for podlings.
> (eg. normally IPMC members get to randomly commit to podlings, how is that
> done w.r.t GitHub? do we get all commit emails? issue emails? etc)
>

Please grant wiki write access for me

[BonoLv]

My incubator wiki user name is  "BonoLv" . Please grant write access
permission for me .

Thx.

Request to join Incubator PMC

[Niclas Hedhman]

Hi,
I (apache ID "niclas") would like to rejoin the Incubator PMC.

Thanks
-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Luciano Resende]

On Sun, Nov 6, 2016 at 6:24 PM, John D. Ament  wrote:

> On Sun, Nov 6, 2016 at 9:22 PM Luciano Resende 
> wrote:
>
> > On Sun, Nov 6, 2016 at 3:15 PM, Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > > The release artifacts can be found at :
> > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> > > > 11.0-incubating-rc5/
> > >
> > > Again it a little confusing what is actually being released here, why
> are
> > > jars included here? [1] Remember maven is not the primary release area
> > [2]
> > >
> > > What exactly were the artefacts that were voted on the dev list?
> > >
> > > Justin
> > >
> > > 1. https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> > > 11.0-incubating-rc5/
> > > 2. http://www.apache.org/dev/release.html#where-do-releases-go
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> > Thanks for taking the time to review SystemML RC Justin.
> > Please see this thread:
> >
> > https://www.mail-archive.com/dev@systemml.incubator.apache.
> org/msg01121.html
> >
> > But in summary, the release folder you linked above contains the
> following
> > artifacts
> >
> > - Source Release
> >
>
> This is the only artifact that should be in the dist area, along with the
> appropriate signature files.  Can you remove the others?
>
>
>
I understand that the most important thing for Apache is the source release
artifact, but that does not prohibit a project from distributing
convenience binaries as long as they meet all the legal requirements
mandated by Apache. Also, the release structure hasn't changed much from
our previous releases, and by looking into recently approved podling
releases, they seem to have binary releases as well, maybe except the jar
related artifacts, that I believe would be ok to remove if that is causing
confusion.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[John D. Ament]

On Sun, Nov 6, 2016 at 9:22 PM Luciano Resende  wrote:

> On Sun, Nov 6, 2016 at 3:15 PM, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > The release artifacts can be found at :
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> > > 11.0-incubating-rc5/
> >
> > Again it a little confusing what is actually being released here, why are
> > jars included here? [1] Remember maven is not the primary release area
> [2]
> >
> > What exactly were the artefacts that were voted on the dev list?
> >
> > Justin
> >
> > 1. https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> > 11.0-incubating-rc5/
> > 2. http://www.apache.org/dev/release.html#where-do-releases-go
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> Thanks for taking the time to review SystemML RC Justin.
> Please see this thread:
>
> https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01121.html
>
> But in summary, the release folder you linked above contains the following
> artifacts
>
> - Source Release
>

This is the only artifact that should be in the dist area, along with the
appropriate signature files.  Can you remove the others?


> - Binary Release
> - Standalone Release (to run in local mode, without dependency on a runtime
> such as Apache Spark)
> - And the convenience binary jar.
>
> Thanks
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Luciano Resende]

On Sun, Nov 6, 2016 at 3:15 PM, Justin Mclean 
wrote:

> Hi,
>
> > The release artifacts can be found at :
> >
> > https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> > 11.0-incubating-rc5/
>
> Again it a little confusing what is actually being released here, why are
> jars included here? [1] Remember maven is not the primary release area [2]
>
> What exactly were the artefacts that were voted on the dev list?
>
> Justin
>
> 1. https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> 11.0-incubating-rc5/
> 2. http://www.apache.org/dev/release.html#where-do-releases-go
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Thanks for taking the time to review SystemML RC Justin.
Please see this thread:
https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01121.html

But in summary, the release folder you linked above contains the following
artifacts

- Source Release
- Binary Release
- Standalone Release (to run in local mode, without dependency on a runtime
such as Apache Spark)
- And the convenience binary jar.

Thanks

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Justin Mclean]

Hi,

> The release artifacts can be found at :
> 
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> 11.0-incubating-rc5/

Again it a little confusing what is actually being released here, why are jars 
included here? [1] Remember maven is not the primary release area [2]

What exactly were the artefacts that were voted on the dev list?

Justin

1. 
https://dist.apache.org/repos/dist/dev/incubator/systemml/0.11.0-incubating-rc5/
2. http://www.apache.org/dev/release.html#where-do-releases-go
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Geode (incubating)

[John D. Ament]

+1

On Nov 6, 2016 15:58, "Roman Shaposhnik"  wrote:

> Hi!
>
> after a very positive discussion in the Geode community
> and at the IPMC level:
> http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
>
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
>
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache Geode PPMC).
>
> Resolution:
>
> Establish the Apache Geode Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to a data management platform that provides
> real-time, consistent access to data-intensive applications
> throughout widely distributed cloud architectures.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Geode Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby is
> responsible for the creation and maintenance of software
> related to a data management platform that provides real-time,
> consistent access to data-intensive applications throughout
> widely distributed cloud architectures.
>
> RESOLVED, that the office of "Vice President, Apache Geode" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Geode Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Geode Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Geode Project:
>
> * Anilkumar Gingade 
> * Anthony Baker 
> * Ashvin Agrawal 
> * Avinash Dongre 
> * Barry Oglesby < bogle...@apache.org>
> * Bruce Schuchardt 
> * Dan Smith 
> * Darrel Schneider 
> * Dave Barnes 
> * Eric Shu 
> * Greg Chase 
> * Hitesh Khamesra 
> * Jason Huynh 
> * Jens Deppe 
> * Jianxia Chen 
> * Jinmei Liao 
> * John Blum 
> * Karen Miller 
> * Konstantin Boudnik 
> * Kirk Lund 
> * Mark Bretl 
> * Nabarun Nag 
> * Niall Pemberton 
> * Nitin Lamba 
> * Roman Shaposhnik 
> * Sai Boorlagadda 
> * Swapnil Bawaskar 
> * Udo Kohlmeyer 
> * William Markito 
> * Xiaojian Zhou 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> be appointed to the office of Vice President, Apache Geode, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Geode PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Geode Project; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Geode podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Geode podling encumbered upon the Apache Incubator
> Project 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 Apache Geode (incubating)

[William Markito Oliveira]

+1

~/William

> On Nov 6, 2016, at 3:54 PM, Niall Pemberton  wrote:
> 
> +1 (binding)
> 
> Niall
> 
> On Sun, Nov 6, 2016 at 8:58 PM, Roman Shaposhnik 
> wrote:
> 
>> Hi!
>> 
>> after a very positive discussion in the Geode community
>> and at the IPMC level:
>>http://markmail.org/message/z4prj62hr7rn6cu6
>> I'd like to bring the following resolution for a formal vote.
>> 
>> Please vote on the resolution pasted below to graduate
>> Apache Geode from the incubator to top level project.
>> 
>> [ ] +1 Graduate Apache Geode from the Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't graduate Apache Geode from the Incubator because...
>> 
>> This vote will be open for at least 72 hours.
>> 
>> Many thanks to our mentors and everyone else for the support,
>> Roman (on behalf of the Apache Geode PPMC).
>> 
>> Resolution:
>> 
>> Establish the Apache Geode Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the
>> public, related to a data management platform that provides
>> real-time, consistent access to data-intensive applications
>> throughout widely distributed cloud architectures.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Geode Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>> 
>> RESOLVED, that the Apache Geode Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to a data management platform that provides real-time,
>> consistent access to data-intensive applications throughout
>> widely distributed cloud architectures.
>> 
>> RESOLVED, that the office of "Vice President, Apache Geode" be
>> and hereby is created, the person holding such office to
>> serve at the direction of the Board of Directors as the chair
>> of the Apache Geode Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Geode Project; and be it further
>> 
>> RESOLVED, that the persons listed immediately below be and
>> hereby are appointed to serve as the initial members of the
>> Apache Geode Project:
>> 
>> * Anilkumar Gingade 
>> * Anthony Baker 
>> * Ashvin Agrawal 
>> * Avinash Dongre 
>> * Barry Oglesby < bogle...@apache.org>
>> * Bruce Schuchardt 
>> * Dan Smith 
>> * Darrel Schneider 
>> * Dave Barnes 
>> * Eric Shu 
>> * Greg Chase 
>> * Hitesh Khamesra 
>> * Jason Huynh 
>> * Jens Deppe 
>> * Jianxia Chen 
>> * Jinmei Liao 
>> * John Blum 
>> * Karen Miller 
>> * Konstantin Boudnik 
>> * Kirk Lund 
>> * Mark Bretl 
>> * Nabarun Nag 
>> * Niall Pemberton 
>> * Nitin Lamba 
>> * Roman Shaposhnik 
>> * Sai Boorlagadda 
>> * Swapnil Bawaskar 
>> * Udo Kohlmeyer 
>> * William Markito 
>> * Xiaojian Zhou 
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
>> be appointed to the office of Vice President, Apache Geode, to
>> serve in accordance with and subject to the direction of the
>> Board of Directors and the Bylaws of the Foundation until
>> death, resignation, retirement, removal or disqualification,
>> or until a successor is appointed; and be it further
>> 
>> RESOLVED, that the initial Apache Geode PMC be and hereby is
>> tasked with the creation of a set of bylaws intended to
>> encourage open development and increased participation in the
>> Apache Geode Project; and be it further
>> 
>> RESOLVED, that the Apache Geode Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Geode podling; and be it further
>> 
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Geode podling encumbered upon the Apache Incubator
>> Project 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 

Re: [VOTE] Graduate Apache Geode (incubating)

[Niall Pemberton]

+1 (binding)

Niall

On Sun, Nov 6, 2016 at 8:58 PM, Roman Shaposhnik 
wrote:

> Hi!
>
> after a very positive discussion in the Geode community
> and at the IPMC level:
> http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
>
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
>
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache Geode PPMC).
>
> Resolution:
>
> Establish the Apache Geode Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to a data management platform that provides
> real-time, consistent access to data-intensive applications
> throughout widely distributed cloud architectures.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Geode Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby is
> responsible for the creation and maintenance of software
> related to a data management platform that provides real-time,
> consistent access to data-intensive applications throughout
> widely distributed cloud architectures.
>
> RESOLVED, that the office of "Vice President, Apache Geode" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Geode Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Geode Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Geode Project:
>
> * Anilkumar Gingade 
> * Anthony Baker 
> * Ashvin Agrawal 
> * Avinash Dongre 
> * Barry Oglesby < bogle...@apache.org>
> * Bruce Schuchardt 
> * Dan Smith 
> * Darrel Schneider 
> * Dave Barnes 
> * Eric Shu 
> * Greg Chase 
> * Hitesh Khamesra 
> * Jason Huynh 
> * Jens Deppe 
> * Jianxia Chen 
> * Jinmei Liao 
> * John Blum 
> * Karen Miller 
> * Konstantin Boudnik 
> * Kirk Lund 
> * Mark Bretl 
> * Nabarun Nag 
> * Niall Pemberton 
> * Nitin Lamba 
> * Roman Shaposhnik 
> * Sai Boorlagadda 
> * Swapnil Bawaskar 
> * Udo Kohlmeyer 
> * William Markito 
> * Xiaojian Zhou 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> be appointed to the office of Vice President, Apache Geode, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Geode PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Geode Project; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Geode podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Geode podling encumbered upon the Apache Incubator
> Project 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 Apache Geode (incubating)

[Suneel Marthi]

+1 binding 

Sent from my iPhone

> On Nov 6, 2016, at 3:58 PM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> after a very positive discussion in the Geode community
> and at the IPMC level:
>http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
> 
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
> 
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache Geode PPMC).
> 
> Resolution:
> 
> Establish the Apache Geode Project
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to a data management platform that provides
> real-time, consistent access to data-intensive applications
> throughout widely distributed cloud architectures.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Geode Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Geode Project be and hereby is
> responsible for the creation and maintenance of software
> related to a data management platform that provides real-time,
> consistent access to data-intensive applications throughout
> widely distributed cloud architectures.
> 
> RESOLVED, that the office of "Vice President, Apache Geode" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Geode Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Geode Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Geode Project:
> 
> * Anilkumar Gingade 
> * Anthony Baker 
> * Ashvin Agrawal 
> * Avinash Dongre 
> * Barry Oglesby < bogle...@apache.org>
> * Bruce Schuchardt 
> * Dan Smith 
> * Darrel Schneider 
> * Dave Barnes 
> * Eric Shu 
> * Greg Chase 
> * Hitesh Khamesra 
> * Jason Huynh 
> * Jens Deppe 
> * Jianxia Chen 
> * Jinmei Liao 
> * John Blum 
> * Karen Miller 
> * Konstantin Boudnik 
> * Kirk Lund 
> * Mark Bretl 
> * Nabarun Nag 
> * Niall Pemberton 
> * Nitin Lamba 
> * Roman Shaposhnik 
> * Sai Boorlagadda 
> * Swapnil Bawaskar 
> * Udo Kohlmeyer 
> * William Markito 
> * Xiaojian Zhou 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> be appointed to the office of Vice President, Apache Geode, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
> 
> RESOLVED, that the initial Apache Geode PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Geode Project; and be it further
> 
> RESOLVED, that the Apache Geode Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Geode podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Geode podling encumbered upon the Apache Incubator
> Project 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 Apache Geode (incubating)

[Swapnil Bawaskar]

+1

On Sunday, November 6, 2016, Anthony Baker  wrote:

> +1
>
> Anthony
>
> On Sun, Nov 6, 2016 at 12:58 PM, Roman Shaposhnik  > wrote:
> > Hi!
> >
> > after a very positive discussion in the Geode community
> > and at the IPMC level:
> > http://markmail.org/message/z4prj62hr7rn6cu6
> > I'd like to bring the following resolution for a formal vote.
> >
> > Please vote on the resolution pasted below to graduate
> > Apache Geode from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Geode from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> >
> > This vote will be open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for the support,
> > Roman (on behalf of the Apache Geode PPMC).
> >
> > Resolution:
> >
> > Establish the Apache Geode Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of the Foundation and consistent with the
> > Foundation's purpose to establish a Project Management
> > Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to the
> > public, related to a data management platform that provides
> > real-time, consistent access to data-intensive applications
> > throughout widely distributed cloud architectures.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Geode Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Geode Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a data management platform that provides real-time,
> > consistent access to data-intensive applications throughout
> > widely distributed cloud architectures.
> >
> > RESOLVED, that the office of "Vice President, Apache Geode" be
> > and hereby is created, the person holding such office to
> > serve at the direction of the Board of Directors as the chair
> > of the Apache Geode Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Geode Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and
> > hereby are appointed to serve as the initial members of the
> > Apache Geode Project:
> >
> > * Anilkumar Gingade >
> > * Anthony Baker >
> > * Ashvin Agrawal >
> > * Avinash Dongre >
> > * Barry Oglesby < bogle...@apache.org >
> > * Bruce Schuchardt >
> > * Dan Smith >
> > * Darrel Schneider >
> > * Dave Barnes >
> > * Eric Shu >
> > * Greg Chase >
> > * Hitesh Khamesra >
> > * Jason Huynh >
> > * Jens Deppe >
> > * Jianxia Chen >
> > * Jinmei Liao >
> > * John Blum >
> > * Karen Miller >
> > * Konstantin Boudnik >
> > * Kirk Lund >
> > * Mark Bretl >
> > * Nabarun Nag >
> > * Niall Pemberton >
> > * Nitin Lamba >
> > * Roman Shaposhnik >
> > * Sai Boorlagadda >
> > * Swapnil Bawaskar >
> > * Udo Kohlmeyer >
> > * William Markito >
> > * Xiaojian Zhou >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> > be appointed to the office of Vice President, Apache Geode, to
> > serve in accordance with and subject to the direction of the
> > Board of Directors and the Bylaws of the Foundation until
> > death, resignation, retirement, removal or disqualification,
> > or until a successor is appointed; and be it further
> >
> > RESOLVED, that the initial Apache Geode PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache Geode Project; and be it further
> >
> > RESOLVED, that the Apache Geode Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Geode podling; and be it further
> >
> > RESOLVED, that all 

Re: [VOTE] Graduate Apache Geode (incubating)

[Anthony Baker]

+1

Anthony

On Sun, Nov 6, 2016 at 12:58 PM, Roman Shaposhnik  wrote:
> Hi!
>
> after a very positive discussion in the Geode community
> and at the IPMC level:
> http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
>
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
>
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...
>
> This vote will be open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache Geode PPMC).
>
> Resolution:
>
> Establish the Apache Geode Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to a data management platform that provides
> real-time, consistent access to data-intensive applications
> throughout widely distributed cloud architectures.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Geode Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby is
> responsible for the creation and maintenance of software
> related to a data management platform that provides real-time,
> consistent access to data-intensive applications throughout
> widely distributed cloud architectures.
>
> RESOLVED, that the office of "Vice President, Apache Geode" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Geode Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Geode Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Geode Project:
>
> * Anilkumar Gingade 
> * Anthony Baker 
> * Ashvin Agrawal 
> * Avinash Dongre 
> * Barry Oglesby < bogle...@apache.org>
> * Bruce Schuchardt 
> * Dan Smith 
> * Darrel Schneider 
> * Dave Barnes 
> * Eric Shu 
> * Greg Chase 
> * Hitesh Khamesra 
> * Jason Huynh 
> * Jens Deppe 
> * Jianxia Chen 
> * Jinmei Liao 
> * John Blum 
> * Karen Miller 
> * Konstantin Boudnik 
> * Kirk Lund 
> * Mark Bretl 
> * Nabarun Nag 
> * Niall Pemberton 
> * Nitin Lamba 
> * Roman Shaposhnik 
> * Sai Boorlagadda 
> * Swapnil Bawaskar 
> * Udo Kohlmeyer 
> * William Markito 
> * Xiaojian Zhou 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> be appointed to the office of Vice President, Apache Geode, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Geode PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Geode Project; and be it further
>
> RESOLVED, that the Apache Geode Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Geode podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Geode podling encumbered upon the Apache Incubator
> Project 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 Apache Geode (incubating)

[Mark Struberg]

+1 (binding)

LieGrue,
strub







> On Sunday, 6 November 2016, 21:59, Roman Shaposhnik  wrote:
> > On Sun, Nov 6, 2016 at 12:58 PM, Roman Shaposhnik  
> wrote:
>>  Hi!
>> 
>>  after a very positive discussion in the Geode community
>>  and at the IPMC level:
>> http://markmail.org/message/z4prj62hr7rn6cu6
>>  I'd like to bring the following resolution for a formal vote.
>> 
>>  Please vote on the resolution pasted below to graduate
>>  Apache Geode from the incubator to top level project.
>> 
>>  [ ] +1 Graduate Apache Geode from the Incubator.
>>  [ ] +0 Don't care.
>>  [ ] -1 Don't graduate Apache Geode from the Incubator because...
> 
> +1 (binding)
> 
> Thanks,
> 
> Roman.
> 
> -
> 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 Apache Geode (incubating)

[Roman Shaposhnik]

On Sun, Nov 6, 2016 at 12:58 PM, Roman Shaposhnik  wrote:
> Hi!
>
> after a very positive discussion in the Geode community
> and at the IPMC level:
> http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
>
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
>
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...

+1 (binding)

Thanks,
Roman.

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

[VOTE] Graduate Apache Geode (incubating)

[Roman Shaposhnik]

Hi!

after a very positive discussion in the Geode community
and at the IPMC level:
http://markmail.org/message/z4prj62hr7rn6cu6
I'd like to bring the following resolution for a formal vote.

Please vote on the resolution pasted below to graduate
Apache Geode from the incubator to top level project.

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

This vote will be open for at least 72 hours.

Many thanks to our mentors and everyone else for the support,
Roman (on behalf of the Apache Geode PPMC).

Resolution:

Establish the Apache Geode Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to a data management platform that provides
real-time, consistent access to data-intensive applications
throughout widely distributed cloud architectures.

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

RESOLVED, that the Apache Geode Project be and hereby is
responsible for the creation and maintenance of software
related to a data management platform that provides real-time,
consistent access to data-intensive applications throughout
widely distributed cloud architectures.

RESOLVED, that the office of "Vice President, Apache Geode" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Geode Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Geode Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Geode Project:

* Anilkumar Gingade 
* Anthony Baker 
* Ashvin Agrawal 
* Avinash Dongre 
* Barry Oglesby < bogle...@apache.org>
* Bruce Schuchardt 
* Dan Smith 
* Darrel Schneider 
* Dave Barnes 
* Eric Shu 
* Greg Chase 
* Hitesh Khamesra 
* Jason Huynh 
* Jens Deppe 
* Jianxia Chen 
* Jinmei Liao 
* John Blum 
* Karen Miller 
* Konstantin Boudnik 
* Kirk Lund 
* Mark Bretl 
* Nabarun Nag 
* Niall Pemberton 
* Nitin Lamba 
* Roman Shaposhnik 
* Sai Boorlagadda 
* Swapnil Bawaskar 
* Udo Kohlmeyer 
* William Markito 
* Xiaojian Zhou 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
be appointed to the office of Vice President, Apache Geode, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Geode PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Geode Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Geode podling encumbered upon the Apache Incubator
Project are hereafter discharged.

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

RE: [DISCUSS] RocketMQ Incubation Proposal

[Ross Gardler]

+1

> -Original Message-
> From: Luke Han [mailto:luke...@gmail.com]
> Sent: Sunday, November 6, 2016 4:46 AM
> To: general@incubator.apache.org
> Subject: Re: [DISCUSS] RocketMQ Incubation Proposal
> 
> > My feeling reading RocketMQ is that its done in a "this is why
> > RocketMQ is better than" approach instead of "this is why RocketMQ
> > differs from them" approach.
> 
> 
> > - How can RocketMQ work with the existing Kafka or ActiveMQ
> > communities to build cross platform clients?
> > - How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
> > persistence stores?
> 
> I'm afraid such question will misleading ASF's position for new project
> especially from a new community (not native English community, but maybe
> biggest one of the world) who are new to ASF and trying their best to learn 
> and
> follow the Apache Way.
> 
> I don't think ASF community will ask every project have to use currently 
> Apache
> project's client, library or anything else. There are many project just come 
> here
> and grow to success without too much "cross".
> 
> IMO, such question should go to dev@ list if it will be accepted later. or 
> just
> send to author separately:-)
> 
> Thanks
> Luke
> 
> 
> 
> 
> Best Regards!
> -
> 
> Luke Han
> 
> On Sun, Nov 6, 2016 at 2:53 AM, John D. Ament 
> wrote:
> 
> > Hi Bruce,
> >
> > On Sat, Nov 5, 2016 at 12:21 PM Bruce Snyder 
> > wrote:
> >
> > > Hi John,
> > >
> > > Proposals for new ASF projects are offered to this list for
> > > constructive feedback. I am happy to help steer the RocketMQ
> > > proposal and project
> > using
> > > your suggestions.
> > >
> > > First, as explained previously in this discussion thread by Von
> > > Gosling, there was some company IP that was mistakenly committed to
> > > the Github repository and through a '...unlucky... scavenging
> > > activity' the history was erased, as Von put it. I interpret this to
> > > mean that someone's git-fu
> > went
> > > awry which unintentionally caused the history to be removed. Von
> > > also
> > gives
> > > further explanation of the project history in a response below.
> > > Indeed, this is an unfortunate situation (and one that I've seen
> > > before with
> > git),
> > > but should this prevent the project from coming to the ASF to
> > > improve and grow under the auspices of the ASF and The Apache Way?
> > >
> >
> > I was simply trying to reiterate for Roman's sanity of what I
> > understood happened, based on Von's email, and my understanding of it.
> > I don't particularly see any concerns with it (as you mention, it
> > happens all of the time), but you may want to consider removing
> > notions that the software was open sourced in 2012, since it sounds like it
> was more of a mistake.
> > The ASF has no requirement that code coming has to be already open
> > sourced, we expect an SGA to be filed with the software coming in.
> >
> > FWIW, I still don't have a good understanding of OMS and its
> > relationship to RocketMQ.  It may be relevant (e.g. a commercial
> > product based on the open source product) or may be completely
> > irrelevant (internal project name vs external project name).
> >
> >
> > >
> > > Second, regarding your statement: 'and its a bit surprising, since
> > > Bruce
> > is
> > > the chair of one of the competitors' -- All projects at the ASF
> > > exist together regardless of their focus and all projects needs good
> > > mentors, regardless of whether they are seen as competing or not. My
> > > interest in helping the RocketMQ project is no different than my
> > > interest in
> > continuing
> > > to be involved with the ActiveMQ project. I have nearly 15 years
> > experience
> > > at the ASF and I'm not here to play games and favor one project over
> > > another. I continue to be involved with the ASF to collaborate
> > > constructively with others on open source and to foster a community
> > > of inclusiveness where we can all continually learn and grow. The
> > > ASF is an inclusive place where even experienced projects can learn
> > > from new projects. As I've said for many years, we all come for code
> > > and stay for the people. My intent is to use my experience to help a
> > > new project and people to the ASF.
> > >
> >
> > This is more of a concern of mine around the structure and content of
> > the proposal, and how some of it potentially leads to issues for the
> > eventual website around RocketMQ.  While the ASF will not limit itself
> > to a single product for a technological/functional area, I do see it
> > as an issue that a project provides references stating why you should
> > use "it" vs another Apache project.  I interpret the current
> > "Relationships to other Apache Products" section as being just that
> > right now.  My only edit to that area was to fix the moin-moin mark up
> > in use, since it wasn't creating a valid table (just as an FYI).
> >
> > Typically when 

Re: [DISCUSS] RocketMQ Incubation Proposal

[Luke Han]

Hi John,
  That make sense, I agree the proposal should refine to less
competitive
but more focus on it's own design and architecture.

  Would love to see that section to be updated before vote:-)

  Thanks
Luke


Best Regards!
-

Luke Han

On Sun, Nov 6, 2016 at 9:44 PM, John D. Ament  wrote:

> Luke, Von,
>
> thanks for the responses.  Some more comments in line.
>
> On Sun, Nov 6, 2016 at 7:48 AM vongosling  wrote:
>
> > Hi, john:
> >
> > Thank you providing AsterixDB proposal, so as to help our complement our
> > proposal. Or to say, give us some advice for RocketMQ community
> development
> > roadmap~
> >
> > Next, let me clarify some question we have talked about.
> >
> >
> > 1. About ONS and RocketMQ relationship~
> >
> > ONS is our Cloud Messaging Service, you also think it as our internal
> > messaging name. But it is built base on RocketMQ, adding some extra
> > features mainly associated with security, audit, web console, etc...
> Have
> > I made everything clear to you. If not, I can depict it using some
> > pictures~
> >
>
> I think I get it now.  Please update the proposal to note that Alibaba
> provides a service named ONS that is derived from RocketMQ.
>
>
> >
> >
> > 2. How can RocketMQ work with the existing Kafka or ActiveMQ communities
> to
> > build cross platform clients?
> >
> > IMO, excellent products, They must have a common feature. That is its
> > pluggable mechanism. We can use it, just like i have said in the latest
> > reply(we are developing kafka-proxy this product, in the near future, we
> > hope to invite kafka guys to make a technical exchange). We can use this
> > idea to integrate RocketMQ with Kafka and ActiveMQ ecosystem seamlessly.
> >
> > In addition, we are planning to draft some messaging specification.we
> want
> > it absorb the advantage of the existing Corbar‘s Notification Service
> > Specification, JMS, AMQP, MQTT and other text protocol.It not include API
> > layer standard, but also possess wireless protocol advantage. May be it
> > will experience a long time to discuss. But If an agreement is reached,
> may
> > be, no matter Kafka, ActiveMQ, RocketMQ or other MQ products, there was
> no
> > doubting that cross platform client is not a difficult thing because our
> > common cross-platform protocol.
> >
> > 3. How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
> > persistence stores?
> >
> > As I have said, nowadays, RocketMQ storage is custom-built for
> low-latency
> > purpose. It just use JDK primitive FIle API and some JNI tech..
> > In the next step, if we hope to leverage Cassandra, Geode, Derby or other
> > full-blown product, we must research them intensively, knowing about and
> > make sure they are suitable for our low latency design goal. At the same
> > time, we also abstract our storage layer(you can think it as SPI), let it
> > meet adaptor design pattern(We will also make use of JDK's service
> locator
> > pattern to support our storage SPI ). All these are in ready, many
> concrete
> > implementation adapter can be created, may be by RocketMQ project guys,
> may
> > be contributed by community enthusiast. if latter way, we must give some
> > guidance and help for them. The guidance seems like this
> > https://github.com/alibaba/RocketMQ/wiki/multi-language-sdk.
> >
> >
> > Last, Thanks again every apache guys(Especially Bruce, Brian, Ross, John,
> > Roman, Greg, Jim etc... )magnanimous diverse culture. We have reasons to
> > believe that Apache is the most suitable home as an open source project
> > following an established development model. We are always willing to lend
> > an ear to the apache and communities, making our product ecosystem
> towards
> > a more healthy and more active direction~
> >
> >
> I think maybe take a look again at the response sent to Bruce yesterday.  I
> want to make sure you're understanding the concern I have.  Greg said it
> best - Apache products do not compete with one another.  I specifically
> want to see the "Relationships with Other Apache Products" section updated
> to focus on the consuming relationships, and limit the competitive aspects
> of it.  These questions were simply leading questions to try to give you
> some ideas of what you could put in that section.
>
> John
>
>
> >
> > Best Regards ~
> >
> > Von Gosling
> >
> >
> > 2016-11-06 17:20 GMT+08:00 Greg Stein :
> >
> > > On Fri, Nov 4, 2016 at 4:26 PM, John D. Ament 
> > > wrote:
> > > >...
> > >
> > > > I'm still a bit leary about the "relationship with other apache
> > products"
> > > > section still.  I'm not interested in seeing how a podling competes
> > with
> > > > other projects
> > >
> > >
> > > Apache projects don't "compete" with anybody. The source code is
> > *offered*
> > > to the public.
> > >
> > > As a 501(c)(3), we're specifically disallowed from competing with
> > > commercial 

[DRAFT] Incubator PMC Board Report - November 2016

[John D. Ament]

All,

Please find the current board report below.  As usual I've done my best to
categorize podlings, but please feel free to edit the report and make
changes as fit.

I added two new categories for it this month - podlings that seem to have
become stagnant, and podlings that seem to have completed all steps
required to graduate (would be good to run the maturity model against them).

We still have a few reports requiring sign off - so please mentors review
and sign off:

Toree
Sirona
Metron
Joshua
Hivemall
Fineract
DistributedLog
DataFu
Climate Model Diagnostic Analyzer


- John



---

Incubator PMC report for November 2016

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 currently 63 podlings incubating - no change from last month.
The Geode podling has begun discussions around graduation.  There were two
new IPMC members added this past month.  The IPMC approved 17 releases this
month as well.

* Community

  New IPMC members:

  - Felix Meschberger
  - Stephan Ewen

  People who left the IPMC:

  - None

* New Podlings

  - None

* Graduations

  The board has motions for the following:

  - None

* Releases

  The following releases entered distribution during the month of
  October:

  - Apache Unomi1.1.0-incubating 2016-10-03
  - Apache Impala   2.7.0-incubating 2016-10-04
  - Apache Fluo 1.0.0-incubating 2016-10-05
  - Apache Htrace   4.2.0-incubating 2016-10-07
  - Apache PredictionIO 0.10.0-incubating2016-10-07
  - Apache Pirk 0.2.0-incubating 2016-10-09
  - Apache HAWQ 2.0.0.0-incubating   2016-10-10
  - Apache CarbonData   0.1.1-incubating 2016-10-11
  - Apache Metron   0.2.1BETA-incubating 2016-10-13
  - Apache Geode1.0.0-incubating 2016-10-15
  - Apache Mnemonic 0.3.0-incubating 2016-10-21
  - Apache Juneau   6.0.0-incubating 2016-10-24
  - Apache Fineract 0.4.0-incubating 2016-10-25
  - Apache Fluo Recipes 1.0.0-incubating 2016-10-27
  - Apache Rya  3.2.10-incubating2016-10-28
  - Apache S2Graph  0.1.0-incubating 2016-10-30
  - Apache Beam 0.3.0-incubating 2016-10-31


* IP Clearance

  - None

* Legal / Trademarks

  - Incoming podlings are pushing more for GitHub as master approaches.
  - In addition, the usage of GitHub Issues continues to be asked.
  - Better alignment between all impacted parties is needed for both of
these.

* Infrastructure

  - While the loss of a server is never convenient, the report manager
gives huge kudos to the infra team for replacing the moin-moin wiki server
quickly, avoiding much impact on this months report.

* Miscellaneous

  - None

* Credits

  - Report Manager: John D. Ament

 Summary of podling reports 

* Still getting started at the Incubator

  - AriaTosca
  - Guacamole
  - Hivemall
  - iota
  - NetBeans
  - Spot
  - Toree


* Not yet ready to graduate

  Stagnant:

  - Metron
  - Sirona

  No release:

  - Blur
  - Climate Model Diagnostic Analyzer
  - DistributedLog
  - Edgent
  - Joshua


  Community growth:

  - DataFu
  - Fineract
  - Fluo
  - Impala
  - PredictionIO
  - S2Graph
  - Streams
  - Unomi


* Potentially Ready to Graduate

  - BatchEE
  - Beam
  - CarbonData
  - Eagle
  - Geode
  - Slider
  - SystemML
  - Tamaya

* Did not report, expected next month

  - Annotator

--
   Table of Contents
AriaTosca
Beam
Blur
CarbonData
Climate Model Diagnostic Analyzer
DataFu
DistributedLog
Eagle
Edgent
Fineract
Fluo
Guacamole
Hivemall
Impala
iota
Joshua
Metron
NetBeans
PredictionIO
S2Graph
Sirona
Slider
Spot
Streams
SystemML
Tamaya
Toree
Unomi

--


AriaTosca

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

 AriaTosca has been incubating since 2016-08-27.

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

   1. Finalize migration of existing ARIA code, including Parser-NG with
TOSCA and TOSCA for NFV profiles, and workflow engine to the ASF repo.
   2. Create and publish release process for ARIA-TOSCA Project, release
process will include Parser, TOSCA profiles, Workflow Engine, CLI.
   3. Publish "How To Contribute" guide at ARIA-TOSCA Website.

 Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
 aware of?
   There's an INFRA jira we created over a month ago which has yet to be
addressed - please see here
   INFRA-12733 - Ability to create a Sprint Board for AriaTosca WAITING FOR
USER

   It is not entirely critical for the project's progress, but it could be
helpful if 

Re: [DISCUSS] RocketMQ Incubation Proposal

[John D. Ament]

Luke, Von,

thanks for the responses.  Some more comments in line.

On Sun, Nov 6, 2016 at 7:48 AM vongosling  wrote:

> Hi, john:
>
> Thank you providing AsterixDB proposal, so as to help our complement our
> proposal. Or to say, give us some advice for RocketMQ community development
> roadmap~
>
> Next, let me clarify some question we have talked about.
>
>
> 1. About ONS and RocketMQ relationship~
>
> ONS is our Cloud Messaging Service, you also think it as our internal
> messaging name. But it is built base on RocketMQ, adding some extra
> features mainly associated with security, audit, web console, etc...  Have
> I made everything clear to you. If not, I can depict it using some
> pictures~
>

I think I get it now.  Please update the proposal to note that Alibaba
provides a service named ONS that is derived from RocketMQ.


>
>
> 2. How can RocketMQ work with the existing Kafka or ActiveMQ communities to
> build cross platform clients?
>
> IMO, excellent products, They must have a common feature. That is its
> pluggable mechanism. We can use it, just like i have said in the latest
> reply(we are developing kafka-proxy this product, in the near future, we
> hope to invite kafka guys to make a technical exchange). We can use this
> idea to integrate RocketMQ with Kafka and ActiveMQ ecosystem seamlessly.
>
> In addition, we are planning to draft some messaging specification.we want
> it absorb the advantage of the existing Corbar‘s Notification Service
> Specification, JMS, AMQP, MQTT and other text protocol.It not include API
> layer standard, but also possess wireless protocol advantage. May be it
> will experience a long time to discuss. But If an agreement is reached, may
> be, no matter Kafka, ActiveMQ, RocketMQ or other MQ products, there was no
> doubting that cross platform client is not a difficult thing because our
> common cross-platform protocol.
>
> 3. How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
> persistence stores?
>
> As I have said, nowadays, RocketMQ storage is custom-built for low-latency
> purpose. It just use JDK primitive FIle API and some JNI tech..
> In the next step, if we hope to leverage Cassandra, Geode, Derby or other
> full-blown product, we must research them intensively, knowing about and
> make sure they are suitable for our low latency design goal. At the same
> time, we also abstract our storage layer(you can think it as SPI), let it
> meet adaptor design pattern(We will also make use of JDK's service locator
> pattern to support our storage SPI ). All these are in ready, many concrete
> implementation adapter can be created, may be by RocketMQ project guys, may
> be contributed by community enthusiast. if latter way, we must give some
> guidance and help for them. The guidance seems like this
> https://github.com/alibaba/RocketMQ/wiki/multi-language-sdk.
>
>
> Last, Thanks again every apache guys(Especially Bruce, Brian, Ross, John,
> Roman, Greg, Jim etc... )magnanimous diverse culture. We have reasons to
> believe that Apache is the most suitable home as an open source project
> following an established development model. We are always willing to lend
> an ear to the apache and communities, making our product ecosystem towards
> a more healthy and more active direction~
>
>
I think maybe take a look again at the response sent to Bruce yesterday.  I
want to make sure you're understanding the concern I have.  Greg said it
best - Apache products do not compete with one another.  I specifically
want to see the "Relationships with Other Apache Products" section updated
to focus on the consuming relationships, and limit the competitive aspects
of it.  These questions were simply leading questions to try to give you
some ideas of what you could put in that section.

John


>
> Best Regards ~
>
> Von Gosling
>
>
> 2016-11-06 17:20 GMT+08:00 Greg Stein :
>
> > On Fri, Nov 4, 2016 at 4:26 PM, John D. Ament 
> > wrote:
> > >...
> >
> > > I'm still a bit leary about the "relationship with other apache
> products"
> > > section still.  I'm not interested in seeing how a podling competes
> with
> > > other projects
> >
> >
> > Apache projects don't "compete" with anybody. The source code is
> *offered*
> > to the public.
> >
> > As a 501(c)(3), we're specifically disallowed from competing with
> > commercial organizations. But even within the ASF and other open source
> > projects, the ASF is simply providing a home for communities to organize,
> > to grow, to construct software for the public. At its most base level,
> the
> > Foundation doesn't care what the project does, how "successful" it is (by
> > whatever metric), or if ten of its communities all produce software to do
> > the same thing. Each community might have a different thought, a
> different
> > approach, or even something as minor as a different view on release
> cycles.
> >
> > All communities are welcome.
> >
> > Cheers,
> > 

Re: [DISCUSS] RocketMQ Incubation Proposal

[vongosling]

Hi, john:

Thank you providing AsterixDB proposal, so as to help our complement our
proposal. Or to say, give us some advice for RocketMQ community development
roadmap~

Next, let me clarify some question we have talked about.


1. About ONS and RocketMQ relationship~

ONS is our Cloud Messaging Service, you also think it as our internal
messaging name. But it is built base on RocketMQ, adding some extra
features mainly associated with security, audit, web console, etc...  Have
I made everything clear to you. If not, I can depict it using some
pictures~


2. How can RocketMQ work with the existing Kafka or ActiveMQ communities to
build cross platform clients?

IMO, excellent products, They must have a common feature. That is its
pluggable mechanism. We can use it, just like i have said in the latest
reply(we are developing kafka-proxy this product, in the near future, we
hope to invite kafka guys to make a technical exchange). We can use this
idea to integrate RocketMQ with Kafka and ActiveMQ ecosystem seamlessly.

In addition, we are planning to draft some messaging specification.we want
it absorb the advantage of the existing Corbar‘s Notification Service
Specification, JMS, AMQP, MQTT and other text protocol.It not include API
layer standard, but also possess wireless protocol advantage. May be it
will experience a long time to discuss. But If an agreement is reached, may
be, no matter Kafka, ActiveMQ, RocketMQ or other MQ products, there was no
doubting that cross platform client is not a difficult thing because our
common cross-platform protocol.

3. How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
persistence stores?

As I have said, nowadays, RocketMQ storage is custom-built for low-latency
purpose. It just use JDK primitive FIle API and some JNI tech..
In the next step, if we hope to leverage Cassandra, Geode, Derby or other
full-blown product, we must research them intensively, knowing about and
make sure they are suitable for our low latency design goal. At the same
time, we also abstract our storage layer(you can think it as SPI), let it
meet adaptor design pattern(We will also make use of JDK's service locator
pattern to support our storage SPI ). All these are in ready, many concrete
implementation adapter can be created, may be by RocketMQ project guys, may
be contributed by community enthusiast. if latter way, we must give some
guidance and help for them. The guidance seems like this
https://github.com/alibaba/RocketMQ/wiki/multi-language-sdk.


Last, Thanks again every apache guys(Especially Bruce, Brian, Ross, John,
Roman, Greg, Jim etc... )magnanimous diverse culture. We have reasons to
believe that Apache is the most suitable home as an open source project
following an established development model. We are always willing to lend
an ear to the apache and communities, making our product ecosystem towards
a more healthy and more active direction~


Best Regards ~

Von Gosling


2016-11-06 17:20 GMT+08:00 Greg Stein :

> On Fri, Nov 4, 2016 at 4:26 PM, John D. Ament 
> wrote:
> >...
>
> > I'm still a bit leary about the "relationship with other apache products"
> > section still.  I'm not interested in seeing how a podling competes with
> > other projects
>
>
> Apache projects don't "compete" with anybody. The source code is *offered*
> to the public.
>
> As a 501(c)(3), we're specifically disallowed from competing with
> commercial organizations. But even within the ASF and other open source
> projects, the ASF is simply providing a home for communities to organize,
> to grow, to construct software for the public. At its most base level, the
> Foundation doesn't care what the project does, how "successful" it is (by
> whatever metric), or if ten of its communities all produce software to do
> the same thing. Each community might have a different thought, a different
> approach, or even something as minor as a different view on release cycles.
>
> All communities are welcome.
>
> Cheers,
> -g
>



-- 
Nothing is impossible

Re: [DISCUSS] RocketMQ Incubation Proposal

[Luke Han]

> My feeling reading RocketMQ is that its done in a "this
> is why RocketMQ is better than" approach instead of "this is why RocketMQ
> differs from them" approach.


> - How can RocketMQ work with the existing Kafka or ActiveMQ communities to
> build cross platform clients?
> - How can RocketMQ look to leverage Cassandra, Geode, Derby as backend
> persistence stores?

I'm afraid such question will misleading ASF's position for new project
especially
from a new community (not native English community, but maybe biggest one
of the world) who are new to ASF and trying their best to learn and follow
the
Apache Way.

I don't think ASF community will ask every project have to use
currently Apache
project's client, library or anything else. There are many project just
come here
and grow to success without too much "cross".

IMO, such question should go to dev@ list if it will be accepted later. or
just send
to author separately:-)

Thanks
Luke




Best Regards!
-

Luke Han

On Sun, Nov 6, 2016 at 2:53 AM, John D. Ament 
wrote:

> Hi Bruce,
>
> On Sat, Nov 5, 2016 at 12:21 PM Bruce Snyder 
> wrote:
>
> > Hi John,
> >
> > Proposals for new ASF projects are offered to this list for constructive
> > feedback. I am happy to help steer the RocketMQ proposal and project
> using
> > your suggestions.
> >
> > First, as explained previously in this discussion thread by Von Gosling,
> > there was some company IP that was mistakenly committed to the Github
> > repository and through a '...unlucky... scavenging activity' the history
> > was
> > erased, as Von put it. I interpret this to mean that someone's git-fu
> went
> > awry which unintentionally caused the history to be removed. Von also
> gives
> > further explanation of the project history in a response below. Indeed,
> > this is an unfortunate situation (and one that I've seen before with
> git),
> > but should this prevent the project from coming to the ASF to improve and
> > grow under the auspices of the ASF and The Apache Way?
> >
>
> I was simply trying to reiterate for Roman's sanity of what I understood
> happened, based on Von's email, and my understanding of it.  I don't
> particularly see any concerns with it (as you mention, it happens all of
> the time), but you may want to consider removing notions that the software
> was open sourced in 2012, since it sounds like it was more of a mistake.
> The ASF has no requirement that code coming has to be already open sourced,
> we expect an SGA to be filed with the software coming in.
>
> FWIW, I still don't have a good understanding of OMS and its relationship
> to RocketMQ.  It may be relevant (e.g. a commercial product based on the
> open source product) or may be completely irrelevant (internal project name
> vs external project name).
>
>
> >
> > Second, regarding your statement: 'and its a bit surprising, since Bruce
> is
> > the chair of one of the competitors' -- All projects at the ASF exist
> > together regardless of their focus and all projects needs good mentors,
> > regardless of whether they are seen as competing or not. My interest in
> > helping the RocketMQ project is no different than my interest in
> continuing
> > to be involved with the ActiveMQ project. I have nearly 15 years
> experience
> > at the ASF and I'm not here to play games and favor one project over
> > another. I continue to be involved with the ASF to collaborate
> > constructively with others on open source and to foster a community of
> > inclusiveness where we can all continually learn and grow. The ASF is an
> > inclusive place where even experienced projects can learn from new
> > projects. As I've said for many years, we all come for code and stay for
> > the people. My intent is to use my experience to help a new project and
> > people to the ASF.
> >
>
> This is more of a concern of mine around the structure and content of the
> proposal, and how some of it potentially leads to issues for the eventual
> website around RocketMQ.  While the ASF will not limit itself to a single
> product for a technological/functional area, I do see it as an issue that a
> project provides references stating why you should use "it" vs another
> Apache project.  I interpret the current "Relationships to other Apache
> Products" section as being just that right now.  My only edit to that area
> was to fix the moin-moin mark up in use, since it wasn't creating a valid
> table (just as an FYI).
>
> Typically when podlings come in, that section lists out the dependencies
> they have on existing ASF projects/products.  Hence why I had responded
> with the list I sent out - that list is more akin to what we usually see.
> Here's some example proposals that do that a bit cleaner from my POV:
>
> https://wiki.apache.org/incubator/AsterixDBProposal
> https://wiki.apache.org/incubator/BrooklynProposal
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> As you can see 

Re: [DISCUSS] RocketMQ Incubation Proposal

[Greg Stein]

On Fri, Nov 4, 2016 at 4:26 PM, John D. Ament 
wrote:
>...

> I'm still a bit leary about the "relationship with other apache products"
> section still.  I'm not interested in seeing how a podling competes with
> other projects


Apache projects don't "compete" with anybody. The source code is *offered*
to the public.

As a 501(c)(3), we're specifically disallowed from competing with
commercial organizations. But even within the ASF and other open source
projects, the ASF is simply providing a home for communities to organize,
to grow, to construct software for the public. At its most base level, the
Foundation doesn't care what the project does, how "successful" it is (by
whatever metric), or if ten of its communities all produce software to do
the same thing. Each community might have a different thought, a different
approach, or even something as minor as a different view on release cycles.

All communities are welcome.

Cheers,
-g

Re: [DISCUSS] OpenWhisk Proposal

[Greg Stein]

On Sat, Nov 5, 2016 at 4:44 PM, Henry Saputra 
wrote:

> I second John, about Github uses.
>
> The statement "As a community we would like to keep the master repository
> as well as issue tracking on GitHub
> " at currently stand is a no-no
> and putting in proposal would make it as goal which at this time not an
> option in ASF infra.
>

As a *podling*, their use of GitHub is an acceptable option within ASF
Infra. [1]

As a TLP, it is NOT.

Thus, when they want to graduate: either Infra has ready to give any TLP
the option of using GitHub as their primary focal point of development (and
OpenWhisk gets to use that option) ... or OpenWhisk must move to the
ASF-supported, non-GitHub option.

Infra is hoping to provide the GitHub option, but we have no date. We have
development to do, we have risks that we can't do what is needed, etc etc.
If OpenWhisk reaches a discussion about graduation, and Infra has not
completed such work, then the OpenWhisk community will have a decision on
wait or shift their development focal point.

Cheers,
Greg Stein
Infrastructure Administrator, ASF

[1] only OpenWhisk. at this time, no other podling is approved for such
deployment, from an Infra standpoint. ... and as John notes: IPMC is
ultimately in charge of how podlings operate. I merely state that Infra
will support this concrete case, which I believe is a good experiment.
there are things to learn about whether this will work/not for podlings.
(eg. normally IPMC members get to randomly commit to podlings, how is that
done w.r.t GitHub? do we get all commit emails? issue emails? etc)