[RESULT] [VOTE] Accept Geode into the Apache Incubator
On Sun, Apr 19, 2015 at 10:46 PM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... With seventeen +1 binding votes, one +1 non-binding vote (eighteen +1 votes total) NO +/-0 or -1 votes, this VOTE PASSES. Thanks to all who voted! Here's a tally of +1 binding votes: Jan Iversen Chris Mattmann Suresh Marru Ted Dunning Henry Saputra James Carman Rob Vesse Chris Douglas Konstantin Boudnik Jakob Homan Chip Childers P. Taylor Goetz Justin Erenkrantz Jim Jagielski Alan Cabrera Niall Pemberton Roman Shaposhnik and an additional tally of +1 non-binding votes: Stuart Williams Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Geode into the Apache Incubator
On Sun, Apr 19, 2015 at 10:46 PM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Geode into the Apache Incubator
+1 Niall (binding) On Monday, April 20, 2015, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active comm
Re: [VOTE] Accept Geode into the Apache Incubator
+1 Regards, Alan Sent from my iPhone > On Apr 19, 2015, at 10:46 PM, Roman Shaposhnik wrote: > > Following the discussion earlier in the thread: > http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to >
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding) > On Apr 20, 2015, at 1:46 AM, Roman Shaposhnik wrote: > > Following the discussion earlier in the thread: > http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active
Re: [VOTE] Accept Geode into the Apache Incubator
+1. -- justin On Apr 20, 2015 1:47 AM, "Roman Shaposhnik" wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active community
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding) -Taylor > On Apr 20, 2015, at 1:46 AM, Roman Shaposhnik wrote: > > Following the discussion earlier in the thread: > http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them int
Re: [VOTE] Accept Geode into the Apache Incubator
On Mon, Apr 20, 2015 at 1:46 AM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > +1 (binding)
Re: [VOTE] Accept Geode into the Apache Incubator
+1. Binding. On 20 April 2015 at 14:21, Pid wrote: > On 20/04/2015 06:46, Roman Shaposhnik wrote: >> Following the discussion earlier in the thread: >>http://s.apache.org/Oxt >> >> I would like to call a VOTE for accepting Geode >> as a new incubator project. >> >> The proposal is available at: >> https://wiki.apache.org/incubator/GeodeProposal >> and is also included at the bottom of this email. >> >> Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST >> >> [x] +1 accept Geode in the Incubator > > Non-binding. > > > p > > >> [ ] ±0 >> [ ] -1 because... >> >> Thanks, >> Roman. >> >> == Abstract == >> Geode is a data management platform that provides real-time, >> consistent access to data-intensive applications throughout widely >> distributed cloud architectures. >> >> Geode pools memory (along with CPU, network and optionally local disk) >> across multiple processes to manage application objects and behavior. >> It uses dynamic replication and data partitioning techniques for high >> availability, improved performance, scalability, and fault tolerance. >> Geode is both a distributed data container and an in-memory data >> management system providing reliable asynchronous event notifications >> and guaranteed message delivery. >> >> == Proposal == >> The goal of this proposal is to bring the core of Pivotal Software, >> Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software >> Foundation (ASF) in order to build a vibrant, diverse and >> self-governed open source community around the technology. Pivotal >> will continue to market and sell Pivotal GemFire based on Geode. Geode >> and Pivotal GemFire will be managed separately. This proposal covers >> the Geode source code (mainly written in Java), Geode documentation >> and other materials currently available on GitHub. >> >> While Geode is our primary choice for a name of the project, in order >> to facilitate PODLINGNAMESEARCH we have come up with two alternatives: >> * Haptic >> * FIG >> >> == Background == >> GemFire is an extremely mature and robust product that can trace its >> legacy all the way back to one of the first Object Databases for >> Smalltalk: GemStone. The GemFire code base has been maintained by the >> same group of engineers as a closed source project. Because of that, >> even though the engineers behind GemFire are the de-facto knowledge >> leaders for distributed in-memory management, they have had little >> exposure to the open source governance process.The original >> company developing GemStone and GemFire was acquired by VMWare in 2010 >> and later spun off as part of Pivotal Software in 2013. Today GemFire >> is used by over 600 enterprise customers. An example deployment >> includes China National Railways that uses Pivotal GemFire to run >> railway ticketing for the entire country of China with a 10 node >> cluster that manages 2 gigabytes "hot data" in memory, and 10 backup >> nodes for high availability and elastic scale. >> >> == Rationale == >> Modern-day data management architectures require a robust in-memory >> data grid solution to handle a variety of use cases, ranging from >> enterprise-wide caching to real-time transactional applications at >> scale. In addition, as memory size and network bandwidth growth >> continues to outpace those of disk, the importance of managing large >> pools of RAM at scale increases. It is essential to innovate at the >> same pace and Pivotal strongly believes that in the Big Data space, >> this can be optimally achieved through a vibrant, diverse, >> self-governed community collectively innovating around a single >> codebase while at the same time cross-pollinating with various other >> data management communities. ASF is the ideal place to meet these >> ambitious goals. >> >> == Initial Goals == >> Our initial goals are to bring Geode into the ASF, transition internal >> engineering processes into the open, and foster a collaborative >> development model according to the "Apache Way." Pivotal plans to >> develop new functionality in an open, community-driven way. To get >> there, the existing internal build, test and release processes will be >> refactored to support open development. >> >> == Current Status == >> Currently, the project code base is licensed for evaluation purposes >> and is available for download from Pivotal.io >> (https://network.pivotal.io/products/project-geode). The documentation >> and wiki pages are available as public GitHub repositories under >> Project Geode organization on GitHub >> (https://github.com/project-geode). Although Pivotal GemFire was >> developed as a proprietary, closed-source product, the internal >> engineering practices adopted by the development team lend themselves >> well to an open, collaborative and meritocratic environment. >> >> The Pivotal GemFire team has always focused on building a robust end >> user community of paying and non-paying customers. The existing >> documentation along wit
Re: [VOTE] Accept Geode into the Apache Incubator
On 20/04/2015 06:46, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [x] +1 accept Geode in the Incubator Non-binding. p > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active
Re: [VOTE] Accept Geode into the Apache Incubator
+1 [binding] Let's the Dao be with you, guys! On Sun, Apr 19, 2015 at 10:46PM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding) Rob On 19/04/2015 22:46, "Roman Shaposhnik" wrote: >Following the discussion earlier in the thread: > http://s.apache.org/Oxt > >I would like to call a VOTE for accepting Geode >as a new incubator project. > >The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal >and is also included at the bottom of this email. > >Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > >Thanks, >Roman. > >== Abstract == >Geode is a data management platform that provides real-time, >consistent access to data-intensive applications throughout widely >distributed cloud architectures. > >Geode pools memory (along with CPU, network and optionally local disk) >across multiple processes to manage application objects and behavior. >It uses dynamic replication and data partitioning techniques for high >availability, improved performance, scalability, and fault tolerance. >Geode is both a distributed data container and an in-memory data >management system providing reliable asynchronous event notifications >and guaranteed message delivery. > >== Proposal == >The goal of this proposal is to bring the core of Pivotal Software, >Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software >Foundation (ASF) in order to build a vibrant, diverse and >self-governed open source community around the technology. Pivotal >will continue to market and sell Pivotal GemFire based on Geode. Geode >and Pivotal GemFire will be managed separately. This proposal covers >the Geode source code (mainly written in Java), Geode documentation >and other materials currently available on GitHub. > >While Geode is our primary choice for a name of the project, in order >to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > >== Background == >GemFire is an extremely mature and robust product that can trace its >legacy all the way back to one of the first Object Databases for >Smalltalk: GemStone. The GemFire code base has been maintained by the >same group of engineers as a closed source project. Because of that, >even though the engineers behind GemFire are the de-facto knowledge >leaders for distributed in-memory management, they have had little >exposure to the open source governance process.The original >company developing GemStone and GemFire was acquired by VMWare in 2010 >and later spun off as part of Pivotal Software in 2013. Today GemFire >is used by over 600 enterprise customers. An example deployment >includes China National Railways that uses Pivotal GemFire to run >railway ticketing for the entire country of China with a 10 node >cluster that manages 2 gigabytes "hot data" in memory, and 10 backup >nodes for high availability and elastic scale. > >== Rationale == >Modern-day data management architectures require a robust in-memory >data grid solution to handle a variety of use cases, ranging from >enterprise-wide caching to real-time transactional applications at >scale. In addition, as memory size and network bandwidth growth >continues to outpace those of disk, the importance of managing large >pools of RAM at scale increases. It is essential to innovate at the >same pace and Pivotal strongly believes that in the Big Data space, >this can be optimally achieved through a vibrant, diverse, >self-governed community collectively innovating around a single >codebase while at the same time cross-pollinating with various other >data management communities. ASF is the ideal place to meet these >ambitious goals. > >== Initial Goals == >Our initial goals are to bring Geode into the ASF, transition internal >engineering processes into the open, and foster a collaborative >development model according to the "Apache Way." Pivotal plans to >develop new functionality in an open, community-driven way. To get >there, the existing internal build, test and release processes will be >refactored to support open development. > >== Current Status == >Currently, the project code base is licensed for evaluation purposes >and is available for download from Pivotal.io >(https://network.pivotal.io/products/project-geode). The documentation >and wiki pages are available as public GitHub repositories under >Project Geode organization on GitHub >(https://github.com/project-geode). Although Pivotal GemFire was >developed as a proprietary, closed-source product, the internal >engineering practices adopted by the development team lend themselves >well to an open, collaborative and meritocratic environment. > >The Pivotal GemFire team has always focused on building a robust end >user community of paying and non-paying customers. The existing >documentation along with StackOverflow and other similar forums are >expected to facilitate conversions between our existing users so as to >transform them into an active community of Geode members, stakeholders >and developers. > >=== Meritocracy === >Our proposed li
Re: [VOTE] Accept Geode into the Apache Incubator
+1 -C On Sun, Apr 19, 2015 at 10:46 PM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active community of
Re: [VOTE] Accept Geode into the Apache Incubator
+1 On Mon, Apr 20, 2015 at 12:09 PM Henry Saputra wrote: > +1 (binding) > > On Sun, Apr 19, 2015 at 10:46 PM, Roman Shaposhnik wrote: > > Following the discussion earlier in the thread: > >http://s.apache.org/Oxt > > > > I would like to call a VOTE for accepting Geode > > as a new incubator project. > > > > The proposal is available at: > > https://wiki.apache.org/incubator/GeodeProposal > > and is also included at the bottom of this email. > > > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > > > [ ] +1 accept Geode in the Incubator > > [ ] ±0 > > [ ] -1 because... > > > > Thanks, > > Roman. > > > > == Abstract == > > Geode is a data management platform that provides real-time, > > consistent access to data-intensive applications throughout widely > > distributed cloud architectures. > > > > Geode pools memory (along with CPU, network and optionally local disk) > > across multiple processes to manage application objects and behavior. > > It uses dynamic replication and data partitioning techniques for high > > availability, improved performance, scalability, and fault tolerance. > > Geode is both a distributed data container and an in-memory data > > management system providing reliable asynchronous event notifications > > and guaranteed message delivery. > > > > == Proposal == > > The goal of this proposal is to bring the core of Pivotal Software, > > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > > Foundation (ASF) in order to build a vibrant, diverse and > > self-governed open source community around the technology. Pivotal > > will continue to market and sell Pivotal GemFire based on Geode. Geode > > and Pivotal GemFire will be managed separately. This proposal covers > > the Geode source code (mainly written in Java), Geode documentation > > and other materials currently available on GitHub. > > > > While Geode is our primary choice for a name of the project, in order > > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > > * Haptic > > * FIG > > > > == Background == > > GemFire is an extremely mature and robust product that can trace its > > legacy all the way back to one of the first Object Databases for > > Smalltalk: GemStone. The GemFire code base has been maintained by the > > same group of engineers as a closed source project. Because of that, > > even though the engineers behind GemFire are the de-facto knowledge > > leaders for distributed in-memory management, they have had little > > exposure to the open source governance process.The original > > company developing GemStone and GemFire was acquired by VMWare in 2010 > > and later spun off as part of Pivotal Software in 2013. Today GemFire > > is used by over 600 enterprise customers. An example deployment > > includes China National Railways that uses Pivotal GemFire to run > > railway ticketing for the entire country of China with a 10 node > > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > > nodes for high availability and elastic scale. > > > > == Rationale == > > Modern-day data management architectures require a robust in-memory > > data grid solution to handle a variety of use cases, ranging from > > enterprise-wide caching to real-time transactional applications at > > scale. In addition, as memory size and network bandwidth growth > > continues to outpace those of disk, the importance of managing large > > pools of RAM at scale increases. It is essential to innovate at the > > same pace and Pivotal strongly believes that in the Big Data space, > > this can be optimally achieved through a vibrant, diverse, > > self-governed community collectively innovating around a single > > codebase while at the same time cross-pollinating with various other > > data management communities. ASF is the ideal place to meet these > > ambitious goals. > > > > == Initial Goals == > > Our initial goals are to bring Geode into the ASF, transition internal > > engineering processes into the open, and foster a collaborative > > development model according to the "Apache Way." Pivotal plans to > > develop new functionality in an open, community-driven way. To get > > there, the existing internal build, test and release processes will be > > refactored to support open development. > > > > == Current Status == > > Currently, the project code base is licensed for evaluation purposes > > and is available for download from Pivotal.io > > (https://network.pivotal.io/products/project-geode). The documentation > > and wiki pages are available as public GitHub repositories under > > Project Geode organization on GitHub > > (https://github.com/project-geode). Although Pivotal GemFire was > > developed as a proprietary, closed-source product, the internal > > engineering practices adopted by the development team lend themselves > > well to an open, collaborative and meritocratic environment. > > > > The Pivotal GemFire team has always focused on building
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding) On Sun, Apr 19, 2015 at 10:46 PM, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active commu
Re: [VOTE] Accept Geode into the Apache Incubator
+1 On Mon, Apr 20, 2015 at 10:53 AM, Suresh Marru wrote: > + 1 (binding) > > Suresh > > > On Apr 20, 2015, at 1:46 AM, Roman Shaposhnik wrote: > > > > Following the discussion earlier in the thread: > > http://s.apache.org/Oxt > > > > I would like to call a VOTE for accepting Geode > > as a new incubator project. > > > > The proposal is available at: > >https://wiki.apache.org/incubator/GeodeProposal > > and is also included at the bottom of this email. > > > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > > > [ ] +1 accept Geode in the Incubator > > [ ] ±0 > > [ ] -1 because... > > > > Thanks, > > Roman. > > > > == Abstract == > > Geode is a data management platform that provides real-time, > > consistent access to data-intensive applications throughout widely > > distributed cloud architectures. > > > > Geode pools memory (along with CPU, network and optionally local disk) > > across multiple processes to manage application objects and behavior. > > It uses dynamic replication and data partitioning techniques for high > > availability, improved performance, scalability, and fault tolerance. > > Geode is both a distributed data container and an in-memory data > > management system providing reliable asynchronous event notifications > > and guaranteed message delivery. > > > > == Proposal == > > The goal of this proposal is to bring the core of Pivotal Software, > > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > > Foundation (ASF) in order to build a vibrant, diverse and > > self-governed open source community around the technology. Pivotal > > will continue to market and sell Pivotal GemFire based on Geode. Geode > > and Pivotal GemFire will be managed separately. This proposal covers > > the Geode source code (mainly written in Java), Geode documentation > > and other materials currently available on GitHub. > > > > While Geode is our primary choice for a name of the project, in order > > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > > * Haptic > > * FIG > > > > == Background == > > GemFire is an extremely mature and robust product that can trace its > > legacy all the way back to one of the first Object Databases for > > Smalltalk: GemStone. The GemFire code base has been maintained by the > > same group of engineers as a closed source project. Because of that, > > even though the engineers behind GemFire are the de-facto knowledge > > leaders for distributed in-memory management, they have had little > > exposure to the open source governance process.The original > > company developing GemStone and GemFire was acquired by VMWare in 2010 > > and later spun off as part of Pivotal Software in 2013. Today GemFire > > is used by over 600 enterprise customers. An example deployment > > includes China National Railways that uses Pivotal GemFire to run > > railway ticketing for the entire country of China with a 10 node > > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > > nodes for high availability and elastic scale. > > > > == Rationale == > > Modern-day data management architectures require a robust in-memory > > data grid solution to handle a variety of use cases, ranging from > > enterprise-wide caching to real-time transactional applications at > > scale. In addition, as memory size and network bandwidth growth > > continues to outpace those of disk, the importance of managing large > > pools of RAM at scale increases. It is essential to innovate at the > > same pace and Pivotal strongly believes that in the Big Data space, > > this can be optimally achieved through a vibrant, diverse, > > self-governed community collectively innovating around a single > > codebase while at the same time cross-pollinating with various other > > data management communities. ASF is the ideal place to meet these > > ambitious goals. > > > > == Initial Goals == > > Our initial goals are to bring Geode into the ASF, transition internal > > engineering processes into the open, and foster a collaborative > > development model according to the "Apache Way." Pivotal plans to > > develop new functionality in an open, community-driven way. To get > > there, the existing internal build, test and release processes will be > > refactored to support open development. > > > > == Current Status == > > Currently, the project code base is licensed for evaluation purposes > > and is available for download from Pivotal.io > > (https://network.pivotal.io/products/project-geode). The documentation > > and wiki pages are available as public GitHub repositories under > > Project Geode organization on GitHub > > (https://github.com/project-geode). Although Pivotal GemFire was > > developed as a proprietary, closed-source product, the internal > > engineering practices adopted by the development team lend themselves > > well to an open, collaborative and meritocratic environment. > > > > The Pivotal GemFire team has always focused on bu
Re: [VOTE] Accept Geode into the Apache Incubator
+ 1 (binding) Suresh > On Apr 20, 2015, at 1:46 AM, Roman Shaposhnik wrote: > > Following the discussion earlier in the thread: > http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding). Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Roman Shaposhnik Reply-To: "general@incubator.apache.org" Date: Monday, April 20, 2015 at 1:46 AM To: "general@incubator.apache.org" Subject: [VOTE] Accept Geode into the Apache Incubator >Following the discussion earlier in the thread: > http://s.apache.org/Oxt > >I would like to call a VOTE for accepting Geode >as a new incubator project. > >The proposal is available at: >https://wiki.apache.org/incubator/GeodeProposal >and is also included at the bottom of this email. > >Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > >Thanks, >Roman. > >== Abstract == >Geode is a data management platform that provides real-time, >consistent access to data-intensive applications throughout widely >distributed cloud architectures. > >Geode pools memory (along with CPU, network and optionally local disk) >across multiple processes to manage application objects and behavior. >It uses dynamic replication and data partitioning techniques for high >availability, improved performance, scalability, and fault tolerance. >Geode is both a distributed data container and an in-memory data >management system providing reliable asynchronous event notifications >and guaranteed message delivery. > >== Proposal == >The goal of this proposal is to bring the core of Pivotal Software, >Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software >Foundation (ASF) in order to build a vibrant, diverse and >self-governed open source community around the technology. Pivotal >will continue to market and sell Pivotal GemFire based on Geode. Geode >and Pivotal GemFire will be managed separately. This proposal covers >the Geode source code (mainly written in Java), Geode documentation >and other materials currently available on GitHub. > >While Geode is our primary choice for a name of the project, in order >to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > >== Background == >GemFire is an extremely mature and robust product that can trace its >legacy all the way back to one of the first Object Databases for >Smalltalk: GemStone. The GemFire code base has been maintained by the >same group of engineers as a closed source project. Because of that, >even though the engineers behind GemFire are the de-facto knowledge >leaders for distributed in-memory management, they have had little >exposure to the open source governance process.The original >company developing GemStone and GemFire was acquired by VMWare in 2010 >and later spun off as part of Pivotal Software in 2013. Today GemFire >is used by over 600 enterprise customers. An example deployment >includes China National Railways that uses Pivotal GemFire to run >railway ticketing for the entire country of China with a 10 node >cluster that manages 2 gigabytes "hot data" in memory, and 10 backup >nodes for high availability and elastic scale. > >== Rationale == >Modern-day data management architectures require a robust in-memory >data grid solution to handle a variety of use cases, ranging from >enterprise-wide caching to real-time transactional applications at >scale. In addition, as memory size and network bandwidth growth >continues to outpace those of disk, the importance of managing large >pools of RAM at scale increases. It is essential to innovate at the >same pace and Pivotal strongly believes that in the Big Data space, >this can be optimally achieved through a vibrant, diverse, >self-governed community collectively innovating around a single >codebase while at the same time cross-pollinating with various other >data management communities. ASF is the ideal place to meet these >ambitious goals. > >== Initial Goals == >Our initial goals are to bring Geode into the ASF, transition internal >engineering processes into the open, and foster a collaborative >development model according to the "Apache Way." Pivotal plans to >develop new functionality in an open, community-driven way. To get >there, the existing internal build,
Re: [VOTE] Accept Geode into the Apache Incubator
+1 (binding) rgds jan i On Monday, April 20, 2015, Roman Shaposhnik wrote: > Following the discussion earlier in the thread: >http://s.apache.org/Oxt > > I would like to call a VOTE for accepting Geode > as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/GeodeProposal > and is also included at the bottom of this email. > > Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST > > [ ] +1 accept Geode in the Incubator > [ ] ±0 > [ ] -1 because... > > Thanks, > Roman. > > == Abstract == > Geode is a data management platform that provides real-time, > consistent access to data-intensive applications throughout widely > distributed cloud architectures. > > Geode pools memory (along with CPU, network and optionally local disk) > across multiple processes to manage application objects and behavior. > It uses dynamic replication and data partitioning techniques for high > availability, improved performance, scalability, and fault tolerance. > Geode is both a distributed data container and an in-memory data > management system providing reliable asynchronous event notifications > and guaranteed message delivery. > > == Proposal == > The goal of this proposal is to bring the core of Pivotal Software, > Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software > Foundation (ASF) in order to build a vibrant, diverse and > self-governed open source community around the technology. Pivotal > will continue to market and sell Pivotal GemFire based on Geode. Geode > and Pivotal GemFire will be managed separately. This proposal covers > the Geode source code (mainly written in Java), Geode documentation > and other materials currently available on GitHub. > > While Geode is our primary choice for a name of the project, in order > to facilitate PODLINGNAMESEARCH we have come up with two alternatives: > * Haptic > * FIG > > == Background == > GemFire is an extremely mature and robust product that can trace its > legacy all the way back to one of the first Object Databases for > Smalltalk: GemStone. The GemFire code base has been maintained by the > same group of engineers as a closed source project. Because of that, > even though the engineers behind GemFire are the de-facto knowledge > leaders for distributed in-memory management, they have had little > exposure to the open source governance process.The original > company developing GemStone and GemFire was acquired by VMWare in 2010 > and later spun off as part of Pivotal Software in 2013. Today GemFire > is used by over 600 enterprise customers. An example deployment > includes China National Railways that uses Pivotal GemFire to run > railway ticketing for the entire country of China with a 10 node > cluster that manages 2 gigabytes "hot data" in memory, and 10 backup > nodes for high availability and elastic scale. > > == Rationale == > Modern-day data management architectures require a robust in-memory > data grid solution to handle a variety of use cases, ranging from > enterprise-wide caching to real-time transactional applications at > scale. In addition, as memory size and network bandwidth growth > continues to outpace those of disk, the importance of managing large > pools of RAM at scale increases. It is essential to innovate at the > same pace and Pivotal strongly believes that in the Big Data space, > this can be optimally achieved through a vibrant, diverse, > self-governed community collectively innovating around a single > codebase while at the same time cross-pollinating with various other > data management communities. ASF is the ideal place to meet these > ambitious goals. > > == Initial Goals == > Our initial goals are to bring Geode into the ASF, transition internal > engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Pivotal plans to > develop new functionality in an open, community-driven way. To get > there, the existing internal build, test and release processes will be > refactored to support open development. > > == Current Status == > Currently, the project code base is licensed for evaluation purposes > and is available for download from Pivotal.io > (https://network.pivotal.io/products/project-geode). The documentation > and wiki pages are available as public GitHub repositories under > Project Geode organization on GitHub > (https://github.com/project-geode). Although Pivotal GemFire was > developed as a proprietary, closed-source product, the internal > engineering practices adopted by the development team lend themselves > well to an open, collaborative and meritocratic environment. > > The Pivotal GemFire team has always focused on building a robust end > user community of paying and non-paying customers. The existing > documentation along with StackOverflow and other similar forums are > expected to facilitate conversions between our existing users so as to > transform them into an active
[VOTE] Accept Geode into the Apache Incubator
Following the discussion earlier in the thread: http://s.apache.org/Oxt I would like to call a VOTE for accepting Geode as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/GeodeProposal and is also included at the bottom of this email. Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST [ ] +1 accept Geode in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. Geode pools memory (along with CPU, network and optionally local disk) across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques for high availability, improved performance, scalability, and fault tolerance. Geode is both a distributed data container and an in-memory data management system providing reliable asynchronous event notifications and guaranteed message delivery. == Proposal == The goal of this proposal is to bring the core of Pivotal Software, Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software Foundation (ASF) in order to build a vibrant, diverse and self-governed open source community around the technology. Pivotal will continue to market and sell Pivotal GemFire based on Geode. Geode and Pivotal GemFire will be managed separately. This proposal covers the Geode source code (mainly written in Java), Geode documentation and other materials currently available on GitHub. While Geode is our primary choice for a name of the project, in order to facilitate PODLINGNAMESEARCH we have come up with two alternatives: * Haptic * FIG == Background == GemFire is an extremely mature and robust product that can trace its legacy all the way back to one of the first Object Databases for Smalltalk: GemStone. The GemFire code base has been maintained by the same group of engineers as a closed source project. Because of that, even though the engineers behind GemFire are the de-facto knowledge leaders for distributed in-memory management, they have had little exposure to the open source governance process.The original company developing GemStone and GemFire was acquired by VMWare in 2010 and later spun off as part of Pivotal Software in 2013. Today GemFire is used by over 600 enterprise customers. An example deployment includes China National Railways that uses Pivotal GemFire to run railway ticketing for the entire country of China with a 10 node cluster that manages 2 gigabytes "hot data" in memory, and 10 backup nodes for high availability and elastic scale. == Rationale == Modern-day data management architectures require a robust in-memory data grid solution to handle a variety of use cases, ranging from enterprise-wide caching to real-time transactional applications at scale. In addition, as memory size and network bandwidth growth continues to outpace those of disk, the importance of managing large pools of RAM at scale increases. It is essential to innovate at the same pace and Pivotal strongly believes that in the Big Data space, this can be optimally achieved through a vibrant, diverse, self-governed community collectively innovating around a single codebase while at the same time cross-pollinating with various other data management communities. ASF is the ideal place to meet these ambitious goals. == Initial Goals == Our initial goals are to bring Geode into the ASF, transition internal engineering processes into the open, and foster a collaborative development model according to the "Apache Way." Pivotal plans to develop new functionality in an open, community-driven way. To get there, the existing internal build, test and release processes will be refactored to support open development. == Current Status == Currently, the project code base is licensed for evaluation purposes and is available for download from Pivotal.io (https://network.pivotal.io/products/project-geode). The documentation and wiki pages are available as public GitHub repositories under Project Geode organization on GitHub (https://github.com/project-geode). Although Pivotal GemFire was developed as a proprietary, closed-source product, the internal engineering practices adopted by the development team lend themselves well to an open, collaborative and meritocratic environment. The Pivotal GemFire team has always focused on building a robust end user community of paying and non-paying customers. The existing documentation along with StackOverflow and other similar forums are expected to facilitate conversions between our existing users so as to transform them into an active community of Geode members, stakeholders and developers. === Meritocracy === Our proposed list of initial committers include the current GemFire R&D team, Pivotal Field Engineers, and several existing customers and partners. This group will form a base for the broa
