Editing ACEU16PodlingSharkTank

[Jean-Baptiste Onofré]

Hi all,

I would like to update:

https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank

to add Beam in the list.

However, the page looks "immutable".

Can someone edit it for me please (or give permission to do so) ?

Thanks
Regards
JB
--
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: Preferred name for package distributions

[Jean-Baptiste Onofré]

Hi Anthony,

I would prefer apache-FOO.

My $0.01

Regards
JB

On 04/26/2016 07:30 AM, Anthony Baker wrote:

In a recent thread on the dev@geode list [1] the subject of naming for
package manager distributions came up, specifically around a Homebrew
formula [2] for Apache Geode.  Does the ASF provide a recommendation on the
preferred format when a project name is used in a technical context?  That
is, should we prefer:

$ brew install apache-FOO
$ apt-get install apache-FOO
$ yum install apache-FOO

OR

$ brew install FOO
$ apt-get install FOO
$ yum install FOO

I reviewed the branding requirements [3] and found a really great thread
[4] on a related subject but not see a clear recommendation.

My observations [5]:

1) In the case of Homebrew, there are 57 Apache formula with only 6 using
the apache-FOO naming format (there are two others that are aliased to
support both forms).
2) Fedora / RHEL / ContOS use apache-FOO.
3) Ubuntu / Debian use FOO.

Should this be left to the discretion of the package distributions and/or
package maintainers?

Any pointers to previous discussions would be greatly appreciated.

Thanks,
Anthony

[1]
http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3c09f50a34-461b-4a56-81ca-c253d2a1f...@pivotal.io%3e
[2] https://github.com/Homebrew/homebrew-core/blob/master/Formula/geode.rb
[3] http://www.apache.org/foundation/marks/pmcs.html
[4]
http://mail-archives.apache.org/mod_mbox/incubator-general/201508.mbox/%3cCA+nPnMzLdtm=-mjzhy5yxeql564so2xaktb9gh7tvdearb3...@mail.gmail.com%3e
[5] https://pkgs.org/search/apache-



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

Preferred name for package distributions

[Anthony Baker]

In a recent thread on the dev@geode list [1] the subject of naming for
package manager distributions came up, specifically around a Homebrew
formula [2] for Apache Geode.  Does the ASF provide a recommendation on the
preferred format when a project name is used in a technical context?  That
is, should we prefer:

$ brew install apache-FOO
$ apt-get install apache-FOO
$ yum install apache-FOO

OR

$ brew install FOO
$ apt-get install FOO
$ yum install FOO

I reviewed the branding requirements [3] and found a really great thread
[4] on a related subject but not see a clear recommendation.

My observations [5]:

1) In the case of Homebrew, there are 57 Apache formula with only 6 using
the apache-FOO naming format (there are two others that are aliased to
support both forms).
2) Fedora / RHEL / ContOS use apache-FOO.
3) Ubuntu / Debian use FOO.

Should this be left to the discretion of the package distributions and/or
package maintainers?

Any pointers to previous discussions would be greatly appreciated.

Thanks,
Anthony

[1]
http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3c09f50a34-461b-4a56-81ca-c253d2a1f...@pivotal.io%3e
[2] https://github.com/Homebrew/homebrew-core/blob/master/Formula/geode.rb
[3] http://www.apache.org/foundation/marks/pmcs.html
[4]
http://mail-archives.apache.org/mod_mbox/incubator-general/201508.mbox/%3cCA+nPnMzLdtm=-mjzhy5yxeql564so2xaktb9gh7tvdearb3...@mail.gmail.com%3e
[5] https://pkgs.org/search/apache-

Re: [VOTE] Accept Gossip into the Apache Incubator

[Andrew Purtell]

+1 (binding)

> On Apr 25, 2016, at 11:14 AM, P. Taylor Goetz  wrote:
> 
> Following the discussion thread [1], I would like to call a VOTE to accept 
> Gossip into the Apache Incubator.
> 
> The Gossip proposal can be found here [2] and is also listed below.
> 
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
> 
> This vote will be open for at least 72 hours.
> 
> Obviously I am +1 (binding).
> 
> -Taylor
> 
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
> 
> 
> = Abstract =
> 
> Apache Gossip will be an implementation of the Gossip Protocol based on code 
> available here: https://github.com/edwardcapriolo/gossip/ which is already 
> licenced using the glorious Apache V2 License.
> 
> = Proposal =
> 
> Apache Gossip aims to provide a gossip based consensus protocol written in 
> Java for peer-to-peer communication to the Apache Incubator 
> (http://incubator.apache.org/). This implementation will effectively scale 
> from one to one-thousand node clusters. In addition to the code 
> implementation, the project should produce specifications of the wire 
> protocol, features, and expected behavior of the system such that compatible 
> implementations can communicate.
> 
> = Background =
> 
> The gossip protocol has been implemented to varying levels of rigor by a 
> number of entities. In particular, Apache Cassandra uses an implementation of 
> gossip to locate peers and transmit up/down state. Apache Spark leverages 
> tooling in Akka which provides peer-to-peer node discovery capabilities.
> 
>  * 
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
> 
>  * https://en.wikipedia.org/wiki/Gossip_protocol
> 
> = Rationale =
> 
> With distributed computing becoming extremely widespread, and the growth of 
> the buzz-factor of ‘the-internet-of-things’ it is increasingly important that 
> networks of IP addressable devices can form a peer-to-peer network. 
> Applications of peer-to-peer networks include generating crypto currency, 
> managing hardware such as solar power micro-grids, and more traditional roles 
> like grid/High Performance Computing and distributed storage systems. 
> Different implementations of gossip based consensus protocols have been 
> implemented in numerous languages or as part of more complex software stacks. 
> The Apache Software Foundation should lead the effort of producing a purpose 
> built tool that can be used by downstream projects to form peer-to-peer 
> networks.
> 
> = Initial Goals =
> 
>  * Migration of current code https://github.com/edwardcapriolo/gossip and 
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by 
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations devices 
> between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to 
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the 
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
> 
> = Current Status =
> 
> The current code has been around for some time. Previously it was a Google 
> code project. Since the fork in January 2015 there have been 55 commits and 4 
> releases.
> 
> == Meritocracy ==
> 
> We believe in meritocracy. All suggestions are taken seriously. We enjoy 
> helping new people become part of process. For other projects available on 
> our Github, once a user shows enough activity we grant them collaborator 
> status.
> 
> == Community ==
> 
> In a relatively short amount of time, with a small amount of promotion on 
> twitter and through blogging, we have 50+ followers on Github and several 
> forks of the project. With the Apache brand we should be able to attract 
> more. Once we have entered the incubator we believe it will be easier to 
> attempt to unify with other similar implementations.
> 
> == Core Developers ==
> 
> The code was forked on Jan 9th 2015, since then there have been 4 releases 
> and 55 commits. Since that period, the majority of the work was undertaken by 
> Edward Capriolo. Several people are interested in the features of this 
> proposal and have indicated they will volunteer their time.
> 
> == Alignment ==
> 
> Apache is the perfect organization to take on the Gossip project. Besides 
> 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Ted Dunning]

+1 binding



On Tue, Apr 26, 2016 at 3:26 AM, Jake Farrell  wrote:

> +1 binding
>
> -Jake
>
> On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz 
> wrote:
>
> > Following the discussion thread [1], I would like to call a VOTE to
> accept
> > Gossip into the Apache Incubator.
> >
> > The Gossip proposal can be found here [2] and is also listed below.
> >
> > [ ] +1 Accept Gossip into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Gossip into the Apache Incubator because…
> >
> > This vote will be open for at least 72 hours.
> >
> > Obviously I am +1 (binding).
> >
> > -Taylor
> >
> > [1] https://s.apache.org/gossip-discuss
> > [2] https://wiki.apache.org/incubator/GossipProposal
> >
> > 
> > = Abstract =
> >
> > Apache Gossip will be an implementation of the Gossip Protocol based on
> > code available here: https://github.com/edwardcapriolo/gossip/ which is
> > already licenced using the glorious Apache V2 License.
> >
> > = Proposal =
> >
> > Apache Gossip aims to provide a gossip based consensus protocol written
> in
> > Java for peer-to-peer communication to the Apache Incubator (
> > http://incubator.apache.org/). This implementation will effectively
> scale
> > from one to one-thousand node clusters. In addition to the code
> > implementation, the project should produce specifications of the wire
> > protocol, features, and expected behavior of the system such that
> > compatible implementations can communicate.
> >
> > = Background =
> >
> > The gossip protocol has been implemented to varying levels of rigor by a
> > number of entities. In particular, Apache Cassandra uses an
> implementation
> > of gossip to locate peers and transmit up/down state. Apache Spark
> > leverages tooling in Akka which provides peer-to-peer node discovery
> > capabilities.
> >
> >  *
> >
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
> >
> >  * https://en.wikipedia.org/wiki/Gossip_protocol
> >
> > = Rationale =
> >
> > With distributed computing becoming extremely widespread, and the growth
> > of the buzz-factor of ‘the-internet-of-things’ it is increasingly
> important
> > that networks of IP addressable devices can form a peer-to-peer network.
> > Applications of peer-to-peer networks include generating crypto currency,
> > managing hardware such as solar power micro-grids, and more traditional
> > roles like grid/High Performance Computing and distributed storage
> systems.
> > Different implementations of gossip based consensus protocols have been
> > implemented in numerous languages or as part of more complex software
> > stacks. The Apache Software Foundation should lead the effort of
> producing
> > a purpose built tool that can be used by downstream projects to form
> > peer-to-peer networks.
> >
> > = Initial Goals =
> >
> >  * Migration of current code https://github.com/edwardcapriolo/gossip
> and
> > existing community to the Apache Software Foundation infrastructure
> >  * Secure communications
> >   * Transport security using a pre-shared key
> >   * Public Key Infrastructure
> >  * Introduce a cluster name to wire protocol to avoid misconfigurations
> >  * Effectively operate when systems have multiple network interfaces by
> > controlling IP binding settings
> >  * Effectively operate when systems have Network Address Translations
> > devices between them using a broadcast IP settings
> >  * Develop advanced integration testing from cluster sizes of 1-1000
> nodes
> >   * Test convergence times
> >   * Demonstrate the tradeoffs of different settings in regard to
> > bandwidth/cpu/convergence time/accuracy
> >  * Gossip data other than cluster state such as application/user data
> >  * Provide detailed specifications such that others can implement the
> > protocol in other programming languages
> >  * Explore HTTP transport as an alternative to UDP
> >
> > = Current Status =
> >
> > The current code has been around for some time. Previously it was a
> Google
> > code project. Since the fork in January 2015 there have been 55 commits
> and
> > 4 releases.
> >
> > == Meritocracy ==
> >
> > We believe in meritocracy. All suggestions are taken seriously. We enjoy
> > helping new people become part of process. For other projects available
> on
> > our Github, once a user shows enough activity we grant them collaborator
> > status.
> >
> > == Community ==
> >
> > In a relatively short amount of time, with a small amount of promotion on
> > twitter and through blogging, we have 50+ followers on Github and several
> > forks of the project. With the Apache brand we should be able to attract
> > more. Once we have entered the incubator we believe it will be easier to
> > attempt to unify with other similar implementations.
> >
> > == Core Developers ==
> >
> > The code was forked on Jan 9th 2015, since then there have been 4
> releases
> > and 55 commits. Since that period, 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Jake Farrell]

+1 binding

-Jake

On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz  wrote:

> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on
> code available here: https://github.com/edwardcapriolo/gossip/ which is
> already licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator (
> http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that
> compatible implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark
> leverages tooling in Akka which provides peer-to-peer node discovery
> capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth
> of the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing
> a purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of projects directly, the active development 

Re: Showcase your project at ApacheCON: consider Podling Shark Tank

[Adam Bordelon]

Signed up. Thanks!

On Mon, Apr 25, 2016 at 6:05 PM, Roman Shaposhnik 
wrote:

> I've just added AdamBordelon wiki ID to the access page.
>
> Thanks,
> Roman.
>
> On Mon, Apr 25, 2016 at 4:39 PM, Adam Bordelon  wrote:
> > Can somebody please grant me (Apache/wiki id 'me') write access to
> > https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank ?
> > I'd like to add myself and Mohit to the list to pitch Myriad
> >
> > -Adam-
> > me@
> >
> > On Mon, Apr 25, 2016 at 1:27 PM, Roman Shaposhnik 
> wrote:
> >
> >> Hi!
> >>
> >> I apologize for the wide distribution, but since my email to general@
> >> didn't seem to have reached all of the podling communities, I took
> >> the liberty of direct email. Here's the deal:
> >>
> >> If you are (or anybody you know who's passionate about your project is)
> >> going to travel to Vancouver for ApacheCON we've got an awesome
> >> opportunity for you to showcase your project. Even if you don't have
> >> talks scheduled in the regular program, consider doing a lighting talk
> >> at Podling Shark Tank:
> >>  https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank
> >>
> >> You've got nothing to lose (in fact, the opposite: you're likely to get
> >> a prize!) and you will get a chance to receive feedback that might
> >> actually help you grow your community and ultimately graduate to the
> >> TLP status. Given our awesome panel of judges:
> >>  * Jim Jagielski
> >>  * Shane Curcuru
> >>  * Milind Bhandarkar
> >> We guarantee this to be a fun and useful event for your community!
> >>
> >> Please sign up on the wiki ASAP. The time is running out!
> >>
> >> Thanks,
> >> Roman.
> >>
> >> P.S. If you have *any* questions whatsoever, but especially if you have
> >> questions on logistics please email me directly.
> >>
>

Re: Showcase your project at ApacheCON: consider Podling Shark Tank

[Roman Shaposhnik]

I've just added AdamBordelon wiki ID to the access page.

Thanks,
Roman.

On Mon, Apr 25, 2016 at 4:39 PM, Adam Bordelon  wrote:
> Can somebody please grant me (Apache/wiki id 'me') write access to
> https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank ?
> I'd like to add myself and Mohit to the list to pitch Myriad
>
> -Adam-
> me@
>
> On Mon, Apr 25, 2016 at 1:27 PM, Roman Shaposhnik  wrote:
>
>> Hi!
>>
>> I apologize for the wide distribution, but since my email to general@
>> didn't seem to have reached all of the podling communities, I took
>> the liberty of direct email. Here's the deal:
>>
>> If you are (or anybody you know who's passionate about your project is)
>> going to travel to Vancouver for ApacheCON we've got an awesome
>> opportunity for you to showcase your project. Even if you don't have
>> talks scheduled in the regular program, consider doing a lighting talk
>> at Podling Shark Tank:
>>  https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank
>>
>> You've got nothing to lose (in fact, the opposite: you're likely to get
>> a prize!) and you will get a chance to receive feedback that might
>> actually help you grow your community and ultimately graduate to the
>> TLP status. Given our awesome panel of judges:
>>  * Jim Jagielski
>>  * Shane Curcuru
>>  * Milind Bhandarkar
>> We guarantee this to be a fun and useful event for your community!
>>
>> Please sign up on the wiki ASAP. The time is running out!
>>
>> Thanks,
>> Roman.
>>
>> P.S. If you have *any* questions whatsoever, but especially if you have
>> questions on logistics please email me directly.
>>

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

[jira] [Created] (INCUBATOR-130) Nuvem in limbo

[Sebb (JIRA)]

Sebb created INCUBATOR-130:
--

 Summary: Nuvem in limbo
 Key: INCUBATOR-130
 URL: https://issues.apache.org/jira/browse/INCUBATOR-130
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


The Nuvem podling appears to be in limbo.
According to podling.xml it graduated, but the comment says:

"The podling was voted to become part of Tuscany in Nov 2012 but (as of Aug 
2014) nothing has happened."

The SVN tree still exists.

Either the graduation should be completed or the podling should be retired.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: Showcase your project at ApacheCON: consider Podling Shark Tank

[Adam Bordelon]

Can somebody please grant me (Apache/wiki id 'me') write access to
https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank ?
I'd like to add myself and Mohit to the list to pitch Myriad

-Adam-
me@

On Mon, Apr 25, 2016 at 1:27 PM, Roman Shaposhnik  wrote:

> Hi!
>
> I apologize for the wide distribution, but since my email to general@
> didn't seem to have reached all of the podling communities, I took
> the liberty of direct email. Here's the deal:
>
> If you are (or anybody you know who's passionate about your project is)
> going to travel to Vancouver for ApacheCON we've got an awesome
> opportunity for you to showcase your project. Even if you don't have
> talks scheduled in the regular program, consider doing a lighting talk
> at Podling Shark Tank:
>  https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank
>
> You've got nothing to lose (in fact, the opposite: you're likely to get
> a prize!) and you will get a chance to receive feedback that might
> actually help you grow your community and ultimately graduate to the
> TLP status. Given our awesome panel of judges:
>  * Jim Jagielski
>  * Shane Curcuru
>  * Milind Bhandarkar
> We guarantee this to be a fun and useful event for your community!
>
> Please sign up on the wiki ASAP. The time is running out!
>
> Thanks,
> Roman.
>
> P.S. If you have *any* questions whatsoever, but especially if you have
> questions on logistics please email me directly.
>

Re: [VOTE] Accept Gossip into the Apache Incubator

[Ralph Goers]

+1 (binding)

Ralph

> On Apr 25, 2016, at 11:14 AM, P. Taylor Goetz  wrote:
> 
> Following the discussion thread [1], I would like to call a VOTE to accept 
> Gossip into the Apache Incubator.
> 
> The Gossip proposal can be found here [2] and is also listed below.
> 
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
> 
> This vote will be open for at least 72 hours.
> 
> Obviously I am +1 (binding).
> 
> -Taylor
> 
> [1] https://s.apache.org/gossip-discuss 
> [2] https://wiki.apache.org/incubator/GossipProposal 
> 
> 
> 
> = Abstract =
> 
> Apache Gossip will be an implementation of the Gossip Protocol based on code 
> available here: https://github.com/edwardcapriolo/gossip/ 
>  which is already licenced using 
> the glorious Apache V2 License.
> 
> = Proposal =
> 
> Apache Gossip aims to provide a gossip based consensus protocol written in 
> Java for peer-to-peer communication to the Apache Incubator 
> (http://incubator.apache.org/ ). This 
> implementation will effectively scale from one to one-thousand node clusters. 
> In addition to the code implementation, the project should produce 
> specifications of the wire protocol, features, and expected behavior of the 
> system such that compatible implementations can communicate.
> 
> = Background =
> 
> The gossip protocol has been implemented to varying levels of rigor by a 
> number of entities. In particular, Apache Cassandra uses an implementation of 
> gossip to locate peers and transmit up/down state. Apache Spark leverages 
> tooling in Akka which provides peer-to-peer node discovery capabilities.
> 
>  * 
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>  
> 
> 
>  * https://en.wikipedia.org/wiki/Gossip_protocol 
> 
> 
> = Rationale =
> 
> With distributed computing becoming extremely widespread, and the growth of 
> the buzz-factor of ‘the-internet-of-things’ it is increasingly important that 
> networks of IP addressable devices can form a peer-to-peer network. 
> Applications of peer-to-peer networks include generating crypto currency, 
> managing hardware such as solar power micro-grids, and more traditional roles 
> like grid/High Performance Computing and distributed storage systems. 
> Different implementations of gossip based consensus protocols have been 
> implemented in numerous languages or as part of more complex software stacks. 
> The Apache Software Foundation should lead the effort of producing a purpose 
> built tool that can be used by downstream projects to form peer-to-peer 
> networks.
> 
> = Initial Goals =
> 
>  * Migration of current code https://github.com/edwardcapriolo/gossip 
>  and existing community to the 
> Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by 
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations devices 
> between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to 
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the 
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
> 
> = Current Status =
> 
> The current code has been around for some time. Previously it was a Google 
> code project. Since the fork in January 2015 there have been 55 commits and 4 
> releases.
> 
> == Meritocracy ==
> 
> We believe in meritocracy. All suggestions are taken seriously. We enjoy 
> helping new people become part of process. For other projects available on 
> our Github, once a user shows enough activity we grant them collaborator 
> status.
> 
> == Community ==
> 
> In a relatively short amount of time, with a small amount of promotion on 
> twitter and through blogging, we have 50+ followers on Github and several 
> forks of the project. With the Apache brand we should be able to attract 
> more. Once we have entered the incubator we believe it will be easier to 
> attempt to unify with other similar implementations.
> 
> == Core Developers ==
> 
> The code 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Anatole Tresch]

+1 (non-binding)
looks very interesting and will probably be very useful for many Apache 
projects.


Am 25.04.2016 um 20:14 schrieb P. Taylor Goetz:
Following the discussion thread [1], I would like to call a VOTE to 
accept Gossip into the Apache Incubator.


The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based 
on code available here: https://github.com/edwardcapriolo/gossip/ 
which is already licenced using the glorious Apache V2 License.


= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol 
written in Java for peer-to-peer communication to the Apache Incubator 
(http://incubator.apache.org/). This implementation will effectively 
scale from one to one-thousand node clusters. In addition to the code 
implementation, the project should produce specifications of the wire 
protocol, features, and expected behavior of the system such that 
compatible implementations can communicate.


= Background =

The gossip protocol has been implemented to varying levels of rigor by 
a number of entities. In particular, Apache Cassandra uses an 
implementation of gossip to locate peers and transmit up/down state. 
Apache Spark leverages tooling in Akka which provides peer-to-peer 
node discovery capabilities.


 * 
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html


 * https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the 
growth of the buzz-factor of ‘the-internet-of-things’ it is 
increasingly important that networks of IP addressable devices can 
form a peer-to-peer network. Applications of peer-to-peer networks 
include generating crypto currency, managing hardware such as solar 
power micro-grids, and more traditional roles like grid/High 
Performance Computing and distributed storage systems. Different 
implementations of gossip based consensus protocols have been 
implemented in numerous languages or as part of more complex software 
stacks. The Apache Software Foundation should lead the effort of 
producing a purpose built tool that can be used by downstream projects 
to form peer-to-peer networks.


= Initial Goals =

 * Migration of current code https://github.com/edwardcapriolo/gossip 
and existing community to the Apache Software Foundation infrastructure

 * Secure communications
  * Transport security using a pre-shared key
  * Public Key Infrastructure
 * Introduce a cluster name to wire protocol to avoid misconfigurations
 * Effectively operate when systems have multiple network interfaces 
by controlling IP binding settings
 * Effectively operate when systems have Network Address Translations 
devices between them using a broadcast IP settings

 * Develop advanced integration testing from cluster sizes of 1-1000 nodes
  * Test convergence times
  * Demonstrate the tradeoffs of different settings in regard to 
bandwidth/cpu/convergence time/accuracy

 * Gossip data other than cluster state such as application/user data
 * Provide detailed specifications such that others can implement the 
protocol in other programming languages

 * Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a 
Google code project. Since the fork in January 2015 there have been 55 
commits and 4 releases.


== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We 
enjoy helping new people become part of process. For other projects 
available on our Github, once a user shows enough activity we grant 
them collaborator status.


== Community ==

In a relatively short amount of time, with a small amount of promotion 
on twitter and through blogging, we have 50+ followers on Github and 
several forks of the project. With the Apache brand we should be able 
to attract more. Once we have entered the incubator we believe it will 
be easier to attempt to unify with other similar implementations.


== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4 
releases and 55 commits. Since that period, the majority of the work 
was undertaken by Edward Capriolo. Several people are interested in 
the features of this proposal and have indicated they will volunteer 
their time.


== Alignment ==

Apache is the perfect organization to take on the Gossip project. 
Besides benefiting a number of projects directly, the active 
development and outreach will increase adoption of Gossip with the aim 
of it becoming a leader in the 

Re: [VOTE] Accept Gossip into the Apache Incubator

[John D. Ament]

+1 and welcome!
On Apr 25, 2016 14:14, "P. Taylor Goetz"  wrote:

> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on
> code available here: https://github.com/edwardcapriolo/gossip/ which is
> already licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator (
> http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that
> compatible implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark
> leverages tooling in Akka which provides peer-to-peer node discovery
> capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth
> of the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing
> a purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of projects directly, the active development and
> 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 04/25/2016 08:14 PM, P. Taylor Goetz wrote:

Following the discussion thread [1], I would like to call a VOTE to
accept Gossip into the Apache Incubator.

The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based on
code available here: https://github.com/edwardcapriolo/gossip/ which is
already licenced using the glorious Apache V2 License.

= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol written
in Java for peer-to-peer communication to the Apache Incubator
(http://incubator.apache.org/). This implementation will effectively
scale from one to one-thousand node clusters. In addition to the code
implementation, the project should produce specifications of the wire
protocol, features, and expected behavior of the system such that
compatible implementations can communicate.

= Background =

The gossip protocol has been implemented to varying levels of rigor by a
number of entities. In particular, Apache Cassandra uses an
implementation of gossip to locate peers and transmit up/down state.
Apache Spark leverages tooling in Akka which provides peer-to-peer node
discovery capabilities.

  *
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html

  * https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the growth
of the buzz-factor of ‘the-internet-of-things’ it is increasingly
important that networks of IP addressable devices can form a
peer-to-peer network. Applications of peer-to-peer networks include
generating crypto currency, managing hardware such as solar power
micro-grids, and more traditional roles like grid/High Performance
Computing and distributed storage systems. Different implementations of
gossip based consensus protocols have been implemented in numerous
languages or as part of more complex software stacks. The Apache
Software Foundation should lead the effort of producing a purpose built
tool that can be used by downstream projects to form peer-to-peer networks.

= Initial Goals =

  * Migration of current code https://github.com/edwardcapriolo/gossip
and existing community to the Apache Software Foundation infrastructure
  * Secure communications
   * Transport security using a pre-shared key
   * Public Key Infrastructure
  * Introduce a cluster name to wire protocol to avoid misconfigurations
  * Effectively operate when systems have multiple network interfaces by
controlling IP binding settings
  * Effectively operate when systems have Network Address Translations
devices between them using a broadcast IP settings
  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
   * Test convergence times
   * Demonstrate the tradeoffs of different settings in regard to
bandwidth/cpu/convergence time/accuracy
  * Gossip data other than cluster state such as application/user data
  * Provide detailed specifications such that others can implement the
protocol in other programming languages
  * Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a
Google code project. Since the fork in January 2015 there have been 55
commits and 4 releases.

== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We enjoy
helping new people become part of process. For other projects available
on our Github, once a user shows enough activity we grant them
collaborator status.

== Community ==

In a relatively short amount of time, with a small amount of promotion
on twitter and through blogging, we have 50+ followers on Github and
several forks of the project. With the Apache brand we should be able to
attract more. Once we have entered the incubator we believe it will be
easier to attempt to unify with other similar implementations.

== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4
releases and 55 commits. Since that period, the majority of the work was
undertaken by Edward Capriolo. Several people are interested in the
features of this proposal and have indicated they will volunteer their time.

== Alignment ==

Apache is the perfect organization to take on the Gossip project.
Besides benefiting a number of projects directly, the active development
and outreach will increase adoption of Gossip with the aim of it
becoming a leader in the space.

= Known Risks =

Several existing implementations of similar cluster membership systems
(gossip based and 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Phillip Rhodes]

+1


This message optimized for indexing by NSA PRISM

On Mon, Apr 25, 2016 at 3:40 PM, Edward Capriolo 
wrote:

> +1 nonbinding.
> GossipYa Heard?
>
> On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz 
> wrote:
>
> > Following the discussion thread [1], I would like to call a VOTE to
> accept
> > Gossip into the Apache Incubator.
> >
> > The Gossip proposal can be found here [2] and is also listed below.
> >
> > [ ] +1 Accept Gossip into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Gossip into the Apache Incubator because…
> >
> > This vote will be open for at least 72 hours.
> >
> > Obviously I am +1 (binding).
> >
> > -Taylor
> >
> > [1] https://s.apache.org/gossip-discuss
> > [2] https://wiki.apache.org/incubator/GossipProposal
> >
> > 
> > = Abstract =
> >
> > Apache Gossip will be an implementation of the Gossip Protocol based on
> > code available here: https://github.com/edwardcapriolo/gossip/ which is
> > already licenced using the glorious Apache V2 License.
> >
> > = Proposal =
> >
> > Apache Gossip aims to provide a gossip based consensus protocol written
> in
> > Java for peer-to-peer communication to the Apache Incubator (
> > http://incubator.apache.org/). This implementation will effectively
> scale
> > from one to one-thousand node clusters. In addition to the code
> > implementation, the project should produce specifications of the wire
> > protocol, features, and expected behavior of the system such that
> > compatible implementations can communicate.
> >
> > = Background =
> >
> > The gossip protocol has been implemented to varying levels of rigor by a
> > number of entities. In particular, Apache Cassandra uses an
> implementation
> > of gossip to locate peers and transmit up/down state. Apache Spark
> > leverages tooling in Akka which provides peer-to-peer node discovery
> > capabilities.
> >
> >  *
> >
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
> >
> >  * https://en.wikipedia.org/wiki/Gossip_protocol
> >
> > = Rationale =
> >
> > With distributed computing becoming extremely widespread, and the growth
> > of the buzz-factor of ‘the-internet-of-things’ it is increasingly
> important
> > that networks of IP addressable devices can form a peer-to-peer network.
> > Applications of peer-to-peer networks include generating crypto currency,
> > managing hardware such as solar power micro-grids, and more traditional
> > roles like grid/High Performance Computing and distributed storage
> systems.
> > Different implementations of gossip based consensus protocols have been
> > implemented in numerous languages or as part of more complex software
> > stacks. The Apache Software Foundation should lead the effort of
> producing
> > a purpose built tool that can be used by downstream projects to form
> > peer-to-peer networks.
> >
> > = Initial Goals =
> >
> >  * Migration of current code https://github.com/edwardcapriolo/gossip
> and
> > existing community to the Apache Software Foundation infrastructure
> >  * Secure communications
> >   * Transport security using a pre-shared key
> >   * Public Key Infrastructure
> >  * Introduce a cluster name to wire protocol to avoid misconfigurations
> >  * Effectively operate when systems have multiple network interfaces by
> > controlling IP binding settings
> >  * Effectively operate when systems have Network Address Translations
> > devices between them using a broadcast IP settings
> >  * Develop advanced integration testing from cluster sizes of 1-1000
> nodes
> >   * Test convergence times
> >   * Demonstrate the tradeoffs of different settings in regard to
> > bandwidth/cpu/convergence time/accuracy
> >  * Gossip data other than cluster state such as application/user data
> >  * Provide detailed specifications such that others can implement the
> > protocol in other programming languages
> >  * Explore HTTP transport as an alternative to UDP
> >
> > = Current Status =
> >
> > The current code has been around for some time. Previously it was a
> Google
> > code project. Since the fork in January 2015 there have been 55 commits
> and
> > 4 releases.
> >
> > == Meritocracy ==
> >
> > We believe in meritocracy. All suggestions are taken seriously. We enjoy
> > helping new people become part of process. For other projects available
> on
> > our Github, once a user shows enough activity we grant them collaborator
> > status.
> >
> > == Community ==
> >
> > In a relatively short amount of time, with a small amount of promotion on
> > twitter and through blogging, we have 50+ followers on Github and several
> > forks of the project. With the Apache brand we should be able to attract
> > more. Once we have entered the incubator we believe it will be easier to
> > attempt to unify with other similar implementations.
> >
> > == Core Developers ==
> >
> > The code was forked on Jan 9th 2015, since then there 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Edward Capriolo]

+1 nonbinding.
GossipYa Heard?

On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz  wrote:

> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on
> code available here: https://github.com/edwardcapriolo/gossip/ which is
> already licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator (
> http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that
> compatible implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark
> leverages tooling in Akka which provides peer-to-peer node discovery
> capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth
> of the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing
> a purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of projects directly, the 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Pierre Smits]

+1 (non-binding)

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Apr 25, 2016 at 9:20 PM, Sean Busbey  wrote:

> +1 (binding)
>
> On Mon, Apr 25, 2016 at 1:14 PM, P. Taylor Goetz 
> wrote:
> > Following the discussion thread [1], I would like to call a VOTE to
> accept
> > Gossip into the Apache Incubator.
> >
> > The Gossip proposal can be found here [2] and is also listed below.
> >
> > [ ] +1 Accept Gossip into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Gossip into the Apache Incubator because…
> >
> > This vote will be open for at least 72 hours.
> >
> > Obviously I am +1 (binding).
> >
> > -Taylor
> >
> > [1] https://s.apache.org/gossip-discuss
> > [2] https://wiki.apache.org/incubator/GossipProposal
> >
> > 
> > = Abstract =
> >
> > Apache Gossip will be an implementation of the Gossip Protocol based on
> code
> > available here: https://github.com/edwardcapriolo/gossip/ which is
> already
> > licenced using the glorious Apache V2 License.
> >
> > = Proposal =
> >
> > Apache Gossip aims to provide a gossip based consensus protocol written
> in
> > Java for peer-to-peer communication to the Apache Incubator
> > (http://incubator.apache.org/). This implementation will effectively
> scale
> > from one to one-thousand node clusters. In addition to the code
> > implementation, the project should produce specifications of the wire
> > protocol, features, and expected behavior of the system such that
> compatible
> > implementations can communicate.
> >
> > = Background =
> >
> > The gossip protocol has been implemented to varying levels of rigor by a
> > number of entities. In particular, Apache Cassandra uses an
> implementation
> > of gossip to locate peers and transmit up/down state. Apache Spark
> leverages
> > tooling in Akka which provides peer-to-peer node discovery capabilities.
> >
> >  *
> >
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
> >
> >  * https://en.wikipedia.org/wiki/Gossip_protocol
> >
> > = Rationale =
> >
> > With distributed computing becoming extremely widespread, and the growth
> of
> > the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> > that networks of IP addressable devices can form a peer-to-peer network.
> > Applications of peer-to-peer networks include generating crypto currency,
> > managing hardware such as solar power micro-grids, and more traditional
> > roles like grid/High Performance Computing and distributed storage
> systems.
> > Different implementations of gossip based consensus protocols have been
> > implemented in numerous languages or as part of more complex software
> > stacks. The Apache Software Foundation should lead the effort of
> producing a
> > purpose built tool that can be used by downstream projects to form
> > peer-to-peer networks.
> >
> > = Initial Goals =
> >
> >  * Migration of current code https://github.com/edwardcapriolo/gossip
> and
> > existing community to the Apache Software Foundation infrastructure
> >  * Secure communications
> >   * Transport security using a pre-shared key
> >   * Public Key Infrastructure
> >  * Introduce a cluster name to wire protocol to avoid misconfigurations
> >  * Effectively operate when systems have multiple network interfaces by
> > controlling IP binding settings
> >  * Effectively operate when systems have Network Address Translations
> > devices between them using a broadcast IP settings
> >  * Develop advanced integration testing from cluster sizes of 1-1000
> nodes
> >   * Test convergence times
> >   * Demonstrate the tradeoffs of different settings in regard to
> > bandwidth/cpu/convergence time/accuracy
> >  * Gossip data other than cluster state such as application/user data
> >  * Provide detailed specifications such that others can implement the
> > protocol in other programming languages
> >  * Explore HTTP transport as an alternative to UDP
> >
> > = Current Status =
> >
> > The current code has been around for some time. Previously it was a
> Google
> > code project. Since the fork in January 2015 there have been 55 commits
> and
> > 4 releases.
> >
> > == Meritocracy ==
> >
> > We believe in meritocracy. All suggestions are taken seriously. We enjoy
> > helping new people become part of process. For other projects available
> on
> > our Github, once a user shows enough activity we grant them collaborator
> > status.
> >
> > == Community ==
> >
> > In a relatively short amount of time, with a small amount of promotion on
> > twitter and through blogging, we have 50+ followers on Github and several
> > forks of the project. With the Apache brand we should be able to attract
> > more. Once we have entered the incubator we believe it will be easier to
> > attempt to unify with other similar implementations.

Re: [VOTE] Accept Gossip into the Apache Incubator

[Sean Busbey]

+1 (binding)

On Mon, Apr 25, 2016 at 1:14 PM, P. Taylor Goetz  wrote:
> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on code
> available here: https://github.com/edwardcapriolo/gossip/ which is already
> licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator
> (http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that compatible
> implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark leverages
> tooling in Akka which provides peer-to-peer node discovery capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth of
> the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing a
> purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of projects directly, the active development and
> 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Debo Dutta (dedutta)]

+1 non binding

Sent from my iPhone

On Apr 25, 2016, at 11:14 AM, P. Taylor Goetz 
> wrote:

Following the discussion thread [1], I would like to call a VOTE to accept 
Gossip into the Apache Incubator.

The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based on code 
available here: https://github.com/edwardcapriolo/gossip/ which is already 
licenced using the glorious Apache V2 License.

= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol written in Java 
for peer-to-peer communication to the Apache Incubator 
(http://incubator.apache.org/). This implementation will effectively scale from 
one to one-thousand node clusters. In addition to the code implementation, the 
project should produce specifications of the wire protocol, features, and 
expected behavior of the system such that compatible implementations can 
communicate.

= Background =

The gossip protocol has been implemented to varying levels of rigor by a number 
of entities. In particular, Apache Cassandra uses an implementation of gossip 
to locate peers and transmit up/down state. Apache Spark leverages tooling in 
Akka which provides peer-to-peer node discovery capabilities.

 * 
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html

 * https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the growth of the 
buzz-factor of ‘the-internet-of-things’ it is increasingly important that 
networks of IP addressable devices can form a peer-to-peer network. 
Applications of peer-to-peer networks include generating crypto currency, 
managing hardware such as solar power micro-grids, and more traditional roles 
like grid/High Performance Computing and distributed storage systems. Different 
implementations of gossip based consensus protocols have been implemented in 
numerous languages or as part of more complex software stacks. The Apache 
Software Foundation should lead the effort of producing a purpose built tool 
that can be used by downstream projects to form peer-to-peer networks.

= Initial Goals =

 * Migration of current code https://github.com/edwardcapriolo/gossip and 
existing community to the Apache Software Foundation infrastructure
 * Secure communications
  * Transport security using a pre-shared key
  * Public Key Infrastructure
 * Introduce a cluster name to wire protocol to avoid misconfigurations
 * Effectively operate when systems have multiple network interfaces by 
controlling IP binding settings
 * Effectively operate when systems have Network Address Translations devices 
between them using a broadcast IP settings
 * Develop advanced integration testing from cluster sizes of 1-1000 nodes
  * Test convergence times
  * Demonstrate the tradeoffs of different settings in regard to 
bandwidth/cpu/convergence time/accuracy
 * Gossip data other than cluster state such as application/user data
 * Provide detailed specifications such that others can implement the protocol 
in other programming languages
 * Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a Google code 
project. Since the fork in January 2015 there have been 55 commits and 4 
releases.

== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We enjoy 
helping new people become part of process. For other projects available on our 
Github, once a user shows enough activity we grant them collaborator status.

== Community ==

In a relatively short amount of time, with a small amount of promotion on 
twitter and through blogging, we have 50+ followers on Github and several forks 
of the project. With the Apache brand we should be able to attract more. Once 
we have entered the incubator we believe it will be easier to attempt to unify 
with other similar implementations.

== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4 releases and 
55 commits. Since that period, the majority of the work was undertaken by 
Edward Capriolo. Several people are interested in the features of this proposal 
and have indicated they will volunteer their time.

== Alignment ==

Apache is the perfect organization to take on the Gossip project. Besides 
benefiting a number of projects directly, the active development and outreach 
will increase adoption of Gossip with the aim of it becoming a leader in the 
space.

= Known Risks =

Re: [VOTE] Accept Gossip into the Apache Incubator

[Amol Kekre]

+1

Thks,
Amol

On Mon, Apr 25, 2016 at 11:22 AM, Josh Elser  wrote:

> +1 (binding)
>
> P. Taylor Goetz wrote:
>
>> Following the discussion thread [1], I would like to call a VOTE to
>> accept Gossip into the Apache Incubator.
>>
>> The Gossip proposal can be found here [2] and is also listed below.
>>
>> [ ] +1 Accept Gossip into the Apache Incubator
>> [ ] +0 Abstain.
>> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>>
>> This vote will be open for at least 72 hours.
>>
>> Obviously I am +1 (binding).
>>
>> -Taylor
>>
>> [1] https://s.apache.org/gossip-discuss
>> [2] https://wiki.apache.org/incubator/GossipProposal
>>
>> 
>> = Abstract =
>>
>> Apache Gossip will be an implementation of the Gossip Protocol based on
>> code available here: https://github.com/edwardcapriolo/gossip/ which is
>> already licenced using the glorious Apache V2 License.
>>
>> = Proposal =
>>
>> Apache Gossip aims to provide a gossip based consensus protocol written
>> in Java for peer-to-peer communication to the Apache Incubator
>> (http://incubator.apache.org/). This implementation will effectively
>> scale from one to one-thousand node clusters. In addition to the code
>> implementation, the project should produce specifications of the wire
>> protocol, features, and expected behavior of the system such that
>> compatible implementations can communicate.
>>
>> = Background =
>>
>> The gossip protocol has been implemented to varying levels of rigor by a
>> number of entities. In particular, Apache Cassandra uses an
>> implementation of gossip to locate peers and transmit up/down state.
>> Apache Spark leverages tooling in Akka which provides peer-to-peer node
>> discovery capabilities.
>>
>> *
>>
>> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>>
>> * https://en.wikipedia.org/wiki/Gossip_protocol
>>
>> = Rationale =
>>
>> With distributed computing becoming extremely widespread, and the growth
>> of the buzz-factor of ‘the-internet-of-things’ it is increasingly
>> important that networks of IP addressable devices can form a
>> peer-to-peer network. Applications of peer-to-peer networks include
>> generating crypto currency, managing hardware such as solar power
>> micro-grids, and more traditional roles like grid/High Performance
>> Computing and distributed storage systems. Different implementations of
>> gossip based consensus protocols have been implemented in numerous
>> languages or as part of more complex software stacks. The Apache
>> Software Foundation should lead the effort of producing a purpose built
>> tool that can be used by downstream projects to form peer-to-peer
>> networks.
>>
>> = Initial Goals =
>>
>> * Migration of current code https://github.com/edwardcapriolo/gossip and
>> existing community to the Apache Software Foundation infrastructure
>> * Secure communications
>> * Transport security using a pre-shared key
>> * Public Key Infrastructure
>> * Introduce a cluster name to wire protocol to avoid misconfigurations
>> * Effectively operate when systems have multiple network interfaces by
>> controlling IP binding settings
>> * Effectively operate when systems have Network Address Translations
>> devices between them using a broadcast IP settings
>> * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>> * Test convergence times
>> * Demonstrate the tradeoffs of different settings in regard to
>> bandwidth/cpu/convergence time/accuracy
>> * Gossip data other than cluster state such as application/user data
>> * Provide detailed specifications such that others can implement the
>> protocol in other programming languages
>> * Explore HTTP transport as an alternative to UDP
>>
>> = Current Status =
>>
>> The current code has been around for some time. Previously it was a
>> Google code project. Since the fork in January 2015 there have been 55
>> commits and 4 releases.
>>
>> == Meritocracy ==
>>
>> We believe in meritocracy. All suggestions are taken seriously. We enjoy
>> helping new people become part of process. For other projects available
>> on our Github, once a user shows enough activity we grant them
>> collaborator status.
>>
>> == Community ==
>>
>> In a relatively short amount of time, with a small amount of promotion
>> on twitter and through blogging, we have 50+ followers on Github and
>> several forks of the project. With the Apache brand we should be able to
>> attract more. Once we have entered the incubator we believe it will be
>> easier to attempt to unify with other similar implementations.
>>
>> == Core Developers ==
>>
>> The code was forked on Jan 9th 2015, since then there have been 4
>> releases and 55 commits. Since that period, the majority of the work was
>> undertaken by Edward Capriolo. Several people are interested in the
>> features of this proposal and have indicated they will volunteer their
>> time.
>>
>> == Alignment ==
>>
>> 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Josh Elser]

+1 (binding)

P. Taylor Goetz wrote:

Following the discussion thread [1], I would like to call a VOTE to
accept Gossip into the Apache Incubator.

The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based on
code available here: https://github.com/edwardcapriolo/gossip/ which is
already licenced using the glorious Apache V2 License.

= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol written
in Java for peer-to-peer communication to the Apache Incubator
(http://incubator.apache.org/). This implementation will effectively
scale from one to one-thousand node clusters. In addition to the code
implementation, the project should produce specifications of the wire
protocol, features, and expected behavior of the system such that
compatible implementations can communicate.

= Background =

The gossip protocol has been implemented to varying levels of rigor by a
number of entities. In particular, Apache Cassandra uses an
implementation of gossip to locate peers and transmit up/down state.
Apache Spark leverages tooling in Akka which provides peer-to-peer node
discovery capabilities.

*
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html

* https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the growth
of the buzz-factor of ‘the-internet-of-things’ it is increasingly
important that networks of IP addressable devices can form a
peer-to-peer network. Applications of peer-to-peer networks include
generating crypto currency, managing hardware such as solar power
micro-grids, and more traditional roles like grid/High Performance
Computing and distributed storage systems. Different implementations of
gossip based consensus protocols have been implemented in numerous
languages or as part of more complex software stacks. The Apache
Software Foundation should lead the effort of producing a purpose built
tool that can be used by downstream projects to form peer-to-peer networks.

= Initial Goals =

* Migration of current code https://github.com/edwardcapriolo/gossip and
existing community to the Apache Software Foundation infrastructure
* Secure communications
* Transport security using a pre-shared key
* Public Key Infrastructure
* Introduce a cluster name to wire protocol to avoid misconfigurations
* Effectively operate when systems have multiple network interfaces by
controlling IP binding settings
* Effectively operate when systems have Network Address Translations
devices between them using a broadcast IP settings
* Develop advanced integration testing from cluster sizes of 1-1000 nodes
* Test convergence times
* Demonstrate the tradeoffs of different settings in regard to
bandwidth/cpu/convergence time/accuracy
* Gossip data other than cluster state such as application/user data
* Provide detailed specifications such that others can implement the
protocol in other programming languages
* Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a
Google code project. Since the fork in January 2015 there have been 55
commits and 4 releases.

== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We enjoy
helping new people become part of process. For other projects available
on our Github, once a user shows enough activity we grant them
collaborator status.

== Community ==

In a relatively short amount of time, with a small amount of promotion
on twitter and through blogging, we have 50+ followers on Github and
several forks of the project. With the Apache brand we should be able to
attract more. Once we have entered the incubator we believe it will be
easier to attempt to unify with other similar implementations.

== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4
releases and 55 commits. Since that period, the majority of the work was
undertaken by Edward Capriolo. Several people are interested in the
features of this proposal and have indicated they will volunteer their time.

== Alignment ==

Apache is the perfect organization to take on the Gossip project.
Besides benefiting a number of projects directly, the active development
and outreach will increase adoption of Gossip with the aim of it
becoming a leader in the space.

= Known Risks =

Several existing implementations of similar cluster membership systems
(gossip based and otherwise) exist. A key challenge is moving from a
relatively niche technical 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Joe Witt]

+1 (non-binding)

Very interesting and hope to participate.

On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz  wrote:
> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on code
> available here: https://github.com/edwardcapriolo/gossip/ which is already
> licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator
> (http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that compatible
> implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark leverages
> tooling in Akka which provides peer-to-peer node discovery capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth of
> the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing a
> purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of 

Re: [VOTE] Accept Gossip into the Apache Incubator

[Chris Nauroth]

+1 (binding)

--Chris Nauroth

From: "P. Taylor Goetz" >
Reply-To: >
Date: Monday, April 25, 2016 at 11:14 AM
To: Incubator 
>
Subject: [VOTE] Accept Gossip into the Apache Incubator

Following the discussion thread [1], I would like to call a VOTE to accept 
Gossip into the Apache Incubator.

The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based on code 
available here: https://github.com/edwardcapriolo/gossip/ which is already 
licenced using the glorious Apache V2 License.

= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol written in Java 
for peer-to-peer communication to the Apache Incubator 
(http://incubator.apache.org/). This implementation will effectively scale from 
one to one-thousand node clusters. In addition to the code implementation, the 
project should produce specifications of the wire protocol, features, and 
expected behavior of the system such that compatible implementations can 
communicate.

= Background =

The gossip protocol has been implemented to varying levels of rigor by a number 
of entities. In particular, Apache Cassandra uses an implementation of gossip 
to locate peers and transmit up/down state. Apache Spark leverages tooling in 
Akka which provides peer-to-peer node discovery capabilities.

 * 
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html

 * https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the growth of the 
buzz-factor of ‘the-internet-of-things’ it is increasingly important that 
networks of IP addressable devices can form a peer-to-peer network. 
Applications of peer-to-peer networks include generating crypto currency, 
managing hardware such as solar power micro-grids, and more traditional roles 
like grid/High Performance Computing and distributed storage systems. Different 
implementations of gossip based consensus protocols have been implemented in 
numerous languages or as part of more complex software stacks. The Apache 
Software Foundation should lead the effort of producing a purpose built tool 
that can be used by downstream projects to form peer-to-peer networks.

= Initial Goals =

 * Migration of current code https://github.com/edwardcapriolo/gossip and 
existing community to the Apache Software Foundation infrastructure
 * Secure communications
  * Transport security using a pre-shared key
  * Public Key Infrastructure
 * Introduce a cluster name to wire protocol to avoid misconfigurations
 * Effectively operate when systems have multiple network interfaces by 
controlling IP binding settings
 * Effectively operate when systems have Network Address Translations devices 
between them using a broadcast IP settings
 * Develop advanced integration testing from cluster sizes of 1-1000 nodes
  * Test convergence times
  * Demonstrate the tradeoffs of different settings in regard to 
bandwidth/cpu/convergence time/accuracy
 * Gossip data other than cluster state such as application/user data
 * Provide detailed specifications such that others can implement the protocol 
in other programming languages
 * Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a Google code 
project. Since the fork in January 2015 there have been 55 commits and 4 
releases.

== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We enjoy 
helping new people become part of process. For other projects available on our 
Github, once a user shows enough activity we grant them collaborator status.

== Community ==

In a relatively short amount of time, with a small amount of promotion on 
twitter and through blogging, we have 50+ followers on Github and several forks 
of the project. With the Apache brand we should be able to attract more. Once 
we have entered the incubator we believe it will be easier to attempt to unify 
with other similar implementations.

== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4 releases and 
55 commits. Since that period, the majority of the work was undertaken by 
Edward Capriolo. Several people are interested in the features of this proposal 
and have indicated they will volunteer their time.

== Alignment ==

Apache is the perfect organization to 

[VOTE] Accept Gossip into the Apache Incubator

[P. Taylor Goetz]

Following the discussion thread [1], I would like to call a VOTE to accept 
Gossip into the Apache Incubator.

The Gossip proposal can be found here [2] and is also listed below.

[ ] +1 Accept Gossip into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Gossip into the Apache Incubator because…

This vote will be open for at least 72 hours.

Obviously I am +1 (binding).

-Taylor

[1] https://s.apache.org/gossip-discuss 
[2] https://wiki.apache.org/incubator/GossipProposal


= Abstract =

Apache Gossip will be an implementation of the Gossip Protocol based on code 
available here: https://github.com/edwardcapriolo/gossip/ which is already 
licenced using the glorious Apache V2 License.

= Proposal =

Apache Gossip aims to provide a gossip based consensus protocol written in Java 
for peer-to-peer communication to the Apache Incubator 
(http://incubator.apache.org/). This implementation will effectively scale from 
one to one-thousand node clusters. In addition to the code implementation, the 
project should produce specifications of the wire protocol, features, and 
expected behavior of the system such that compatible implementations can 
communicate.

= Background =

The gossip protocol has been implemented to varying levels of rigor by a number 
of entities. In particular, Apache Cassandra uses an implementation of gossip 
to locate peers and transmit up/down state. Apache Spark leverages tooling in 
Akka which provides peer-to-peer node discovery capabilities.

 * 
http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html

 * https://en.wikipedia.org/wiki/Gossip_protocol

= Rationale =

With distributed computing becoming extremely widespread, and the growth of the 
buzz-factor of ‘the-internet-of-things’ it is increasingly important that 
networks of IP addressable devices can form a peer-to-peer network. 
Applications of peer-to-peer networks include generating crypto currency, 
managing hardware such as solar power micro-grids, and more traditional roles 
like grid/High Performance Computing and distributed storage systems. Different 
implementations of gossip based consensus protocols have been implemented in 
numerous languages or as part of more complex software stacks. The Apache 
Software Foundation should lead the effort of producing a purpose built tool 
that can be used by downstream projects to form peer-to-peer networks.

= Initial Goals =

 * Migration of current code https://github.com/edwardcapriolo/gossip and 
existing community to the Apache Software Foundation infrastructure
 * Secure communications
  * Transport security using a pre-shared key
  * Public Key Infrastructure
 * Introduce a cluster name to wire protocol to avoid misconfigurations
 * Effectively operate when systems have multiple network interfaces by 
controlling IP binding settings
 * Effectively operate when systems have Network Address Translations devices 
between them using a broadcast IP settings
 * Develop advanced integration testing from cluster sizes of 1-1000 nodes
  * Test convergence times
  * Demonstrate the tradeoffs of different settings in regard to 
bandwidth/cpu/convergence time/accuracy
 * Gossip data other than cluster state such as application/user data
 * Provide detailed specifications such that others can implement the protocol 
in other programming languages
 * Explore HTTP transport as an alternative to UDP

= Current Status =

The current code has been around for some time. Previously it was a Google code 
project. Since the fork in January 2015 there have been 55 commits and 4 
releases.

== Meritocracy ==

We believe in meritocracy. All suggestions are taken seriously. We enjoy 
helping new people become part of process. For other projects available on our 
Github, once a user shows enough activity we grant them collaborator status.

== Community ==

In a relatively short amount of time, with a small amount of promotion on 
twitter and through blogging, we have 50+ followers on Github and several forks 
of the project. With the Apache brand we should be able to attract more. Once 
we have entered the incubator we believe it will be easier to attempt to unify 
with other similar implementations.

== Core Developers ==

The code was forked on Jan 9th 2015, since then there have been 4 releases and 
55 commits. Since that period, the majority of the work was undertaken by 
Edward Capriolo. Several people are interested in the features of this proposal 
and have indicated they will volunteer their time.

== Alignment ==

Apache is the perfect organization to take on the Gossip project. Besides 
benefiting a number of projects directly, the active development and outreach 
will increase adoption of Gossip with the aim of it becoming a leader in the 
space.

= Known Risks =

Several existing implementations of similar cluster membership systems (gossip 
based and otherwise) exist. 

Re: [PROPOSAL] Gossip incubator proposal

[John D. Ament]

Having the original author on board and an SGA from them would basically
lift any concerns I had.

So I'm wondering, are you guys ready to vote?

John

On Mon, Apr 25, 2016 at 12:47 PM P. Taylor Goetz  wrote:

>
> On Apr 25, 2016, at 4:41 AM, Bertrand Delacretaz 
> wrote:
>
> I would recommend documenting whatever decisions you make and having
> them ratified by the Incubator PMC to make them acts of the ASF.
>
> The best might be to add a section to the podling proposal describing
> how the incoming code will be handled in terms of SGA (or not, and if
> not why) so that the podling creation vote includes accepting those
> decisions.
>
> -Bertrand
>
>
> Thanks for the suggestion Bertrand. I added a statement to that effect in
> the proposal.
>
> We contacted both original authors informing them of our intentions and
> inviting them to join the project. We have since heard back from the
> original author, who responded positively and has been added as an initial
> committer. We would like to have SGAs from both authors, but given the
> second author hasn’t touched the code in 6 years, we’re not sure we’ll hear
> from him.
>
> Our intention is to proceed with the Incubator IP Clearance process
> regardless of whether or not we hear back from the second author. Given
> that we now have the first, original author on board, I feel we are in
> decent shape.
>
> -Taylor
>

Re: [PROPOSAL] Gossip incubator proposal

[P. Taylor Goetz]

> On Apr 25, 2016, at 1:19 PM, John D. Ament  wrote:
> 
> Having the original author on board and an SGA from them would basically
> lift any concerns I had.
> 
> So I'm wondering, are you guys ready to vote?

I believe so. I think all of the questions and concerns have been addressed.

I’ll start a vote thread shortly.

> 
> John

-Taylor



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [ANN] Apache Johnzon as new TLP

[Hendrik Dev]

i'll take care of the next steps ...

On Mon, Apr 25, 2016 at 7:07 PM, John D. Ament  wrote:
> Don't forget to do the requisite clean up work.  Johnzon still shows as a
> podling http://incubator.apache.org/projects/johnzon.html
> Please graduate them in podlings.xml.
>
> I sent out an email the other day with the reminder and a link to the full
> list of steps.
>
> John
>
> On Mon, Apr 25, 2016 at 1:02 PM Mark Struberg 
> wrote:
>
>> Hi!
>>
>> I'm happy to announce that the board has unanimously voted to graduate
>> Apache Johnzon to a TLP.
>>
>> Txs to all who helped along the way and best wishes to the Apache Johnzon
>> community for their further endeavours.
>>
>> LieGrue,
>> strub
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>



-- 
Hendrik Saly (salyh, hendrikdev22)
@hendrikdev22
PGP: 0x22D7F6EC

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

Re: [ANN] Apache Johnzon as new TLP

[John D. Ament]

Don't forget to do the requisite clean up work.  Johnzon still shows as a
podling http://incubator.apache.org/projects/johnzon.html
Please graduate them in podlings.xml.

I sent out an email the other day with the reminder and a link to the full
list of steps.

John

On Mon, Apr 25, 2016 at 1:02 PM Mark Struberg 
wrote:

> Hi!
>
> I'm happy to announce that the board has unanimously voted to graduate
> Apache Johnzon to a TLP.
>
> Txs to all who helped along the way and best wishes to the Apache Johnzon
> community for their further endeavours.
>
> LieGrue,
> strub
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[ANN] Apache Johnzon as new TLP

[Mark Struberg]

Hi!

I'm happy to announce that the board has unanimously voted to graduate Apache 
Johnzon to a TLP.

Txs to all who helped along the way and best wishes to the Apache Johnzon 
community for their further endeavours.

LieGrue,
strub

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

Re: [PROPOSAL] Gossip incubator proposal

[P. Taylor Goetz]

> On Apr 25, 2016, at 4:41 AM, Bertrand Delacretaz  
> wrote:
> 
> I would recommend documenting whatever decisions you make and having
> them ratified by the Incubator PMC to make them acts of the ASF.
> 
> The best might be to add a section to the podling proposal describing
> how the incoming code will be handled in terms of SGA (or not, and if
> not why) so that the podling creation vote includes accepting those
> decisions.
> 
> -Bertrand

Thanks for the suggestion Bertrand. I added a statement to that effect in the 
proposal.

We contacted both original authors informing them of our intentions and 
inviting them to join the project. We have since heard back from the original 
author, who responded positively and has been added as an initial committer. We 
would like to have SGAs from both authors, but given the second author hasn’t 
touched the code in 6 years, we’re not sure we’ll hear from him.

Our intention is to proceed with the Incubator IP Clearance process regardless 
of whether or not we hear back from the second author. Given that we now have 
the first, original author on board, I feel we are in decent shape.

-Taylor


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [PROPOSAL] Gossip incubator proposal

[Bertrand Delacretaz]

On Sun, Apr 24, 2016 at 3:28 PM, John D. Ament  wrote:
> And just to make sure you guys saw it, there was a (what I would consider)
> positive response from Legal:
> https://issues.apache.org/jira/browse/LEGAL-248 ...

I would recommend documenting whatever decisions you make and having
them ratified by the Incubator PMC to make them acts of the ASF.

The best might be to add a section to the podling proposal describing
how the incoming code will be handled in terms of SGA (or not, and if
not why) so that the podling creation vote includes accepting those
decisions.

-Bertrand

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