Re: [VOTE] Release Apache Streams Project version 0.2-incubating (rc2)
Hi, It passes all the basic checks for a release, but sorry it's -1 (binding) from me until the likely copyright issues around the test data are sorted out. I checked: - release has incubating in the name - signature and hashes fine - DISCLAIMER exists - LICENSE and NOTICE fine for the code but see below - No unexpected binary files - All source files have Apache headers - Can compile from source I think there's also a very minor issue with the NOTICE file. The copyright year range is 2012-2015. I assume that date range also includes the original copyright owners who should be added to the NOTICE file. However of concern is the test data, it looks like there's data in there from twitter, facebook, instragram, google+, wikipedia, reddit, amazon, the economist and other places. Does the project have permission to distribute this data from the copyright owners? (If so I would of also expected the owners to be aded to the LICENSE file, assuming that is the content is obtainable under an Apache compatible license in the first place.) One possible solution to make a release without the test data. The files in question may also be required to be removed from Apache hosted version control. I'm not a lawyer and it may be best to ask legal-discuss@ for advice on what to do here. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Parquet MR (Incubating) 1.6.0 RC2
Hi everyone, I propose the following RC to be released as official Apache Parquet 1.6.0 release. This RC passed the vote in the Parquet community with 2 binding IPMC votes. The thread is here: * http://s.apache.org/parquet-1.6.0-ppmc-vote This is the first Apache release of Parquet MR. Like the 2.2.0 release of Parquet Format, this uses the old parquet.* package names and will be immediately followed by a 1.7.0 release that is strictly a move to org.apache.parquet.* packages and artifacts. The commit id is 4f660778f89d4164c72676f6b15bbc74c0d09373. * http://s.apache.org/apache-parquet-mr-1.6.0-incubating-rc2 * https://github.com/apache/incubator-parquet-mr/tree/4f660778 The release tarball, signature, and checksums are here: * https://dist.apache.org/repos/dist/dev/incubator/parquet/apache-parquet-mr-1.6.0-incubating-rc2/ You can find the KEYS file here: * https://dist.apache.org/repos/dist/dev/incubator/parquet/KEYS Full changes for the release can be found here: * https://github.com/apache/incubator-parquet-mr/blob/4f660778/CHANGES.md#version-160 Please download, verify, and test. Building the project requires both protoc and thrift compilers. We recommend versions 2.5.0 and 0.7.0 and there are build instructions in the README. This vote will close in 3 days. [ ] +1 Release this as Apache Parquet Format 1.6.0 [ ] +0 [ ] -1 Do not release this because... -- Ryan Blue - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Geode Incubation proposal
Hi! I would like to open up a discussion thread on the proposals for the core of Pivotal's GemFire to join ASF as an incubating project under the name Geode. The proposal wiki is available here: https://wiki.apache.org/incubator/GeodeProposal and the text of the proposal is attached to the bottom of this email as well. Given the timing of ApacheCON, we would love to chat with anybody interested in giving us feedback. That said, of course, the bulk of the discussion is expected to happen on this thread. Thanks for your time and consideration! Roman (Geode proposal champion and a nominated mentor). == 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 propo
Re: [DISCUSS] Geode Incubation proposal
Just as a quick remark. Geode might be a trademark owned by AMD: http://en.wikipedia.org/wiki/Geode_%28processor%29 Cheers Daniel On Sun, Apr 12, 2015 at 8:46 PM, Roman Shaposhnik wrote: > Hi! > > I would like to open up a discussion thread on > the proposals for the core of Pivotal's GemFire > to join ASF as an incubating project under the > name Geode. > > The proposal wiki is available here: >https://wiki.apache.org/incubator/GeodeProposal > and the text of the proposal is attached to the > bottom of this email as well. > > Given the timing of ApacheCON, we would love to > chat with anybody interested in giving us feedback. > That said, of course, the bulk of the discussion is > expected to happen on this thread. > > Thanks for your time and consideration! > Roman (Geode proposal champion and a nominated mentor). > > == 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 Gem
Re: [DISCUSS] Geode Incubation proposal
On Sunday, April 12, 2015, dsh wrote: > Just as a quick remark. Geode might be a trademark owned by AMD: > http://en.wikipedia.org/wiki/Geode_%28processor%29 Good catch, we need to hear the opinion of trademark@ because it depend on it is in an overlapping field (as I understood it). F.x. Corinthia is registered as a print font and hotel chain, but that was not a problem. I think it is a good proposal and the project seems to have good chances of growing under the wings of apache. rgds jan i > > Cheers > Daniel > > On Sun, Apr 12, 2015 at 8:46 PM, Roman Shaposhnik > wrote: > > > Hi! > > > > I would like to open up a discussion thread on > > the proposals for the core of Pivotal's GemFire > > to join ASF as an incubating project under the > > name Geode. > > > > The proposal wiki is available here: > >https://wiki.apache.org/incubator/GeodeProposal > > and the text of the proposal is attached to the > > bottom of this email as well. > > > > Given the timing of ApacheCON, we would love to > > chat with anybody interested in giving us feedback. > > That said, of course, the bulk of the discussion is > > expected to happen on this thread. > > > > Thanks for your time and consideration! > > Roman (Geode proposal champion and a nominated mentor). > > > > == 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 == > > Currentl
Re: [DISCUSS] Geode Incubation proposal
Roman, Could you comment on the potential issue that this proposal is only offering up the distributed object storage. The problem that might arise with this is that by offering up a particular specialized core capability, other projects may find it difficult to use this core capability which would inhibit growth of the community. What do you think about that? On Sun, Apr 12, 2015 at 8:46 PM, Roman Shaposhnik wrote: > Hi! > > I would like to open up a discussion thread on > the proposals for the core of Pivotal's GemFire > to join ASF as an incubating project under the > name Geode. > > The proposal wiki is available here: >https://wiki.apache.org/incubator/GeodeProposal > and the text of the proposal is attached to the > bottom of this email as well. > > Given the timing of ApacheCON, we would love to > chat with anybody interested in giving us feedback. > That said, of course, the bulk of the discussion is > expected to happen on this thread. > > Thanks for your time and consideration! > Roman (Geode proposal champion and a nominated mentor). > > == 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 Piv
Re: [DISCUSS] Geode Incubation proposal
On Sun, Apr 12, 2015 at 1:00 PM, Ted Dunning wrote: > Roman, > > Could you comment on the potential issue that this proposal is only > offering up the distributed object storage. The problem that might arise > with this is that by offering up a particular specialized core capability, > other projects may find it difficult to use this core capability which > would inhibit growth of the community. > > What do you think about that? I was trying to address that very point in the Rationale section. While it is true that today Geode is the engine for GemFire, it is at the same time a pretty sophisticated piece of engineering work with subsystems that can find use outside of GemFire applications. Just to give you a few examples: there's a kick-ass eventing systems in there and the off-heap memory management implementation is one the best ones I've seen. I could absolutely see Geode integrating much tighter at the level of in-memory data exchange layer (think Tachyon done right) with the rest of the bigdata ecosystem as well. That said, making Geode as modular as possible is exactly why we're proposing it for Incubation: this is exactly the kind of extended use cases that ASF communities are great at figuring out. Long story short, it is definitely our desire to see Geode applicable way outside of core GemFire capabilities and I believe it has got what it takes. Thanks, Roman. P.S. In fact, you've just given me a great subject for a blog post. Stay tuned! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Geode Incubation proposal
Roman, Is this the same as Project Geode which seems to be clogging my twitter feed this afternoon? http://projectgeode.org/ If so, it looks like you already figured out the naming issue. Is whoever behind this going to hand over the "geode" name to ASF? John On Sun, Apr 12, 2015 at 2:47 PM Roman Shaposhnik wrote: > Hi! > > I would like to open up a discussion thread on > the proposals for the core of Pivotal's GemFire > to join ASF as an incubating project under the > name Geode. > > The proposal wiki is available here: >https://wiki.apache.org/incubator/GeodeProposal > and the text of the proposal is attached to the > bottom of this email as well. > > Given the timing of ApacheCON, we would love to > chat with anybody interested in giving us feedback. > That said, of course, the bulk of the discussion is > expected to happen on this thread. > > Thanks for your time and consideration! > Roman (Geode proposal champion and a nominated mentor). > > == 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 practic
Re: [VOTE] Release Apache Streams Project version 0.2-incubating (rc2)
Justin, The short answer is the project has not asked for permission from any data providers to include data sourced from their APIs as test data. I'm not expecting a rush to add +1s to a vote after legal has been mentioned in the thread, so I'll cancel it. I'll prepare a new release with all test resources with unclear licensing removed and the tests that require them deactivated for now. Steve Blackmon sblack...@apache.org On Sun, Apr 12, 2015 at 10:24 AM, Justin Mclean wrote: > Hi, > > It passes all the basic checks for a release, but sorry it's -1 (binding) > from me until the likely copyright issues around the test data are sorted out. > > I checked: > - release has incubating in the name > - signature and hashes fine > - DISCLAIMER exists > - LICENSE and NOTICE fine for the code but see below > - No unexpected binary files > - All source files have Apache headers > - Can compile from source > > I think there's also a very minor issue with the NOTICE file. The copyright > year range is 2012-2015. I assume that date range also includes the original > copyright owners who should be added to the NOTICE file. > > However of concern is the test data, it looks like there's data in there from > twitter, facebook, instragram, google+, wikipedia, reddit, amazon, the > economist and other places. Does the project have permission to distribute > this data from the copyright owners? (If so I would of also expected the > owners to be aded to the LICENSE file, assuming that is the content is > obtainable under an Apache compatible license in the first place.) > > One possible solution to make a release without the test data. The files in > question may also be required to be removed from Apache hosted version > control. I'm not a lawyer and it may be best to ask legal-discuss@ for advice > on what to do here. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCELLED] [VOTE] Release Apache Streams Project version 0.2-incubating (rc2)
Steve Blackmon sblack...@apache.org On Sun, Apr 12, 2015 at 7:01 PM, Steve Blackmon wrote: > Justin, > > The short answer is the project has not asked for permission from any > data providers to include data sourced from their APIs as test data. > > I'm not expecting a rush to add +1s to a vote after legal has been > mentioned in the thread, so I'll cancel it. > > I'll prepare a new release with all test resources with unclear > licensing removed and the tests that require them deactivated for now. > > Steve Blackmon > sblack...@apache.org > > > On Sun, Apr 12, 2015 at 10:24 AM, Justin Mclean > wrote: >> Hi, >> >> It passes all the basic checks for a release, but sorry it's -1 (binding) >> from me until the likely copyright issues around the test data are sorted >> out. >> >> I checked: >> - release has incubating in the name >> - signature and hashes fine >> - DISCLAIMER exists >> - LICENSE and NOTICE fine for the code but see below >> - No unexpected binary files >> - All source files have Apache headers >> - Can compile from source >> >> I think there's also a very minor issue with the NOTICE file. The copyright >> year range is 2012-2015. I assume that date range also includes the original >> copyright owners who should be added to the NOTICE file. >> >> However of concern is the test data, it looks like there's data in there >> from twitter, facebook, instragram, google+, wikipedia, reddit, amazon, the >> economist and other places. Does the project have permission to distribute >> this data from the copyright owners? (If so I would of also expected the >> owners to be aded to the LICENSE file, assuming that is the content is >> obtainable under an Apache compatible license in the first place.) >> >> One possible solution to make a release without the test data. The files in >> question may also be required to be removed from Apache hosted version >> control. I'm not a lawyer and it may be best to ask legal-discuss@ for >> advice on what to do here. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Geode Incubation proposal
Where "hand over the Geode name" also means hand over the domain name and GitHub organizations that have rather confusingly been launched in the last few days. I'd also like to be able to review the source referred to in the proposal without having to sign up to "the Pivotal network" - how can I do that? Ross -Original Message- From: John D. Ament [mailto:johndam...@apache.org] Sent: Sunday, April 12, 2015 1:50 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Geode Incubation proposal Roman, Is this the same as Project Geode which seems to be clogging my twitter feed this afternoon? http://projectgeode.org/ If so, it looks like you already figured out the naming issue. Is whoever behind this going to hand over the "geode" name to ASF? John On Sun, Apr 12, 2015 at 2:47 PM Roman Shaposhnik wrote: > Hi! > > I would like to open up a discussion thread on the proposals for the > core of Pivotal's GemFire to join ASF as an incubating project under > the name Geode. > > The proposal wiki is available here: >https://wiki.apache.org/incubator/GeodeProposal > and the text of the proposal is attached to the bottom of this email > as well. > > Given the timing of ApacheCON, we would love to chat with anybody > interested in giving us feedback. > That said, of course, the bulk of the discussion is expected to happen > on this thread. > > Thanks for your time and consideration! > Roman (Geode proposal champion and a nominated mentor). > > == 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 b
Re: [DISCUSS] Geode Incubation proposal
On Sun, Apr 12, 2015 at 1:50 PM, John D. Ament wrote: > Roman, > > Is this the same as Project Geode which seems to be clogging my twitter > feed this afternoon? Sorry about that -- we get excited about open source ;-) > http://projectgeode.org/ > > If so, it looks like you already figured out the naming issue. Is whoever > behind this going to hand over the "geode" name to ASF? Yes. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Geode Incubation proposal
On Sun, Apr 12, 2015 at 8:49 PM, Ross Gardler (MS OPEN TECH) wrote: > Where "hand over the Geode name" also means hand over the domain name and > GitHub organizations > that have rather confusingly been launched in the last few days. Yup. Everything that's been published on GitHub is going to transition to ASF once the proposal gets voted in. > I'd also like to be able to review the source referred to in the proposal > without having to sign up to "the Pivotal network" - how can I do that? The issue here is export and license compliance. Unfortunately, singing up is the only way to go right now. Why is it problematic for you? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Streams Project version 0.2-incubating (rc2)
Hi, > I'll prepare a new release with all test resources with unclear > licensing removed and the tests that require them deactivated for now. That could be an easy short term solution, but I wouldn't remove the tests just yet as it may be that they could be downloaded not bundled and/or hosted elsewhere if that is required. It may also be OK to release this release candidate if the incubator knows the issues raised are being looked into and will be fixed in a future release. I'd hold off on cancelling the vote until other people state their opinion . Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Geode Incubation proposal
Since I'm getting a few off-list questions, I just want to make one point clear: On Sun, Apr 12, 2015 at 8:53 PM, Roman Shaposhnik wrote: >> I'd also like to be able to review the source referred to in the proposal >> without having to sign up to "the Pivotal network" - how can I do that? > > The issue here is export and license compliance. Unfortunately, singing > up is the only way to go right now. Why is it problematic for you? The software currently is NOT under ALv2. It is available under the evaluation license. The whole point of the proposal is to make it available under ALv2 as an Incubating project. Our apologies for making folks click through the evaluation license. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release apache-calcite-1.2.0-incubating
Hi all, The Calcite community has voted on and approved a proposal to release Apache Calcite 1.2.0-incubating. Thanks to everyone who has contributed to this release. This is a short release, less than a month after 1.1, but there are 42 fixed issues nevertheless. In particular, Avatica has better coverage of the JDBC API and is much more robust. You can read the release notes here: https://github.com/apache/incubator-calcite/blob/branch-1.2/doc/HISTORY.md During the vote we noted issue https://issues.apache.org/jira/browse/CALCITE-677: one test fails if you run in a time zone east of Greenwich. The bug is minor, but affects the build process as documented in the HOWTO. After a prolonged debate we reached consensus that a note accompanying the release announcement was sufficient. Proposal: http://s.apache.org/calcite-1.2-vote Vote result: 3 binding +1 votes 2 non-binding +1 votes No -1 votes http://s.apache.org/calcite-1.2-result The commit to be voted upon: http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/d60f2aa3aa9ce7cda7c4f6986af5729d50a28679 Its hash is d60f2aa3aa9ce7cda7c4f6986af5729d50a28679. The artifacts to be voted on are located here: https://dist.apache.org/repos/dist/dev/incubator/calcite/apache-calcite-1.2.0-incubating-rc1 The hashes of the artifacts are as follows: src.tar.gz.md5 ead5878c92896668a51ab71a4108b070 src.tar.gz.sha1 9cd0b8c542dd8b1af50661543e6af3c67ad9da82 src.zip.md5 85a547882c800677f46f59444c8a1539 src.zip.sha1 cefa18ab2243814ef8a2cde352d4059c2da3dc28 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecalcite-1007 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/jhyde.asc Pursuant to the Releases section of the Incubation Policy we would now like to request the permission of the Incubator PMC to publish the release. The vote is open for 72 hours, or until the necessary number of votes (3 +1) is reached. [ ] +1 Release this package as Apache Calcite 1.2.0-incubating [ ] -1 Do not release this package because... Julian Hyde, on behalf of Apache Calcite PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Geode Incubation proposal
Pivotal are asking me to agree to an "evaluation license" which I cannot view before I sign up. So I have to review the privacy policy first. Pivotal's privacy policy goes a *long* way beyond the point I am comfortable with when getting open source software (or deciding whether I want to agree with an evaluation license I can't read). I guess your defense could be that it's not open source yet, that's fine, but you are asking me, as an IPMC Member, to make a judgement on the validity of the proposal but I can't evaluate the code since I can't access it or the license under which I am allowed to view it. Most importantly, the "export and license obligations" you mention are something that have to go away before we can accept the project (or more accurately before it can graduate). Since I can't evaluate the code or the license I have no way of evaluating whether this is possible. There is no mention of such an item under "known risks" or the "crypotography" section of the proposal so what's this "export" stuff about (assuming the license thing is the evaluation license)? Given the points above I do not see how I can evaluate this proposal in its current form. Ross -Original Message- From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf Of Roman Shaposhnik Sent: Sunday, April 12, 2015 11:56 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Geode Incubation proposal Since I'm getting a few off-list questions, I just want to make one point clear: On Sun, Apr 12, 2015 at 8:53 PM, Roman Shaposhnik wrote: >> I'd also like to be able to review the source referred to in the >> proposal without having to sign up to "the Pivotal network" - how can I do >> that? > > The issue here is export and license compliance. Unfortunately, > singing up is the only way to go right now. Why is it problematic for you? The software currently is NOT under ALv2. It is available under the evaluation license. The whole point of the proposal is to make it available under ALv2 as an Incubating project. Our apologies for making folks click through the evaluation license. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Geode Incubation proposal
Ross, do we evaluate source code at the incubation-entry level, or do we evaluate proposed development goals and development community propositions? I'm curious about your thoughts. Yours, Bill On Apr 13, 2015 12:16 AM, "Ross Gardler (MS OPEN TECH)" < ross.gard...@microsoft.com> wrote: > Pivotal are asking me to agree to an "evaluation license" which I cannot > view before I sign up. So I have to review the privacy policy first. > > Pivotal's privacy policy goes a *long* way beyond the point I am > comfortable with when getting open source software (or deciding whether I > want to agree with an evaluation license I can't read). I guess your > defense could be that it's not open source yet, that's fine, but you are > asking me, as an IPMC Member, to make a judgement on the validity of the > proposal but I can't evaluate the code since I can't access it or the > license under which I am allowed to view it. > > Most importantly, the "export and license obligations" you mention are > something that have to go away before we can accept the project (or more > accurately before it can graduate). Since I can't evaluate the code or the > license I have no way of evaluating whether this is possible. There is no > mention of such an item under "known risks" or the "crypotography" section > of the proposal so what's this "export" stuff about (assuming the license > thing is the evaluation license)? > > Given the points above I do not see how I can evaluate this proposal in > its current form. > > Ross > > -Original Message- > From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf Of > Roman Shaposhnik > Sent: Sunday, April 12, 2015 11:56 PM > To: general@incubator.apache.org > Subject: Re: [DISCUSS] Geode Incubation proposal > > Since I'm getting a few off-list questions, I just want to make one point > clear: > > On Sun, Apr 12, 2015 at 8:53 PM, Roman Shaposhnik > wrote: > >> I'd also like to be able to review the source referred to in the > >> proposal without having to sign up to "the Pivotal network" - how can > I do that? > > > > The issue here is export and license compliance. Unfortunately, > > singing up is the only way to go right now. Why is it problematic for > you? > > The software currently is NOT under ALv2. It is available under the > evaluation license. The whole point of the proposal is to make it available > under ALv2 as an Incubating project. > > Our apologies for making folks click through the evaluation license. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [DISCUSS] Geode Incubation proposal
On Sun, Apr 12, 2015 at 10:15 PM, Ross Gardler (MS OPEN TECH) wrote: > Pivotal are asking me to agree to an "evaluation license" which I cannot view > before I sign up. > So I have to review the privacy policy first. This must be a bug in your browser. What OS/Browser are you using? The text of the license is also available in a separate file under the name "Evaluation License": https://network.pivotal.io/products/project-geode > Most importantly, the "export and license obligations" you mention are > something that > have to go away before we can accept the project (or more accurately before > it can graduate). > Since I can't evaluate the code or the license I have no way of evaluating > whether this is possible. > > There is no mention of such an item under "known risks" or the > "crypotography" section of the proposal > so what's this "export" stuff about (assuming the license thing is the > evaluation license)? Sorry for not being more explicit: this is just how Pivotal distribution network works. And we have to use it in this particular case in order to guarantee that the evaluation license has been explicitly acknowledged (as opposed to just being there in a tarball). All these constraints has nothing to do with the source code itself. > Given the points above I do not see how I can evaluate this proposal in its > current form. I see that Bill has asked the question that I wanted to ask here, so I'll let you reply in that part of the thread. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Geode Incubation proposal
I think it is common to take a quick look at code coming in. In particular, a glance to see whether there is any hygiene around licensing is an important question. Many projects in the world at large have no good record of who write the code but still imagine that they can change the licensing. Such projects are not suitable for Apache incubation since without a clean rewrite, they are not possible to Apache license. Commercially developed code rarely has that sort of problem, but there may be other problems that a quick perusal would turn up or eliminate. At the very least, it seems reasonable to put a link to the content of the evaluation license in the proposal. On Mon, Apr 13, 2015 at 7:32 AM, William A Rowe Jr wrote: > Ross, > > do we evaluate source code at the incubation-entry level, or do we evaluate > proposed development goals and development community propositions? I'm > curious about your thoughts. > > Yours, > > Bill > On Apr 13, 2015 12:16 AM, "Ross Gardler (MS OPEN TECH)" < > ross.gard...@microsoft.com> wrote: > > > Pivotal are asking me to agree to an "evaluation license" which I cannot > > view before I sign up. So I have to review the privacy policy first. > > > > Pivotal's privacy policy goes a *long* way beyond the point I am > > comfortable with when getting open source software (or deciding whether I > > want to agree with an evaluation license I can't read). I guess your > > defense could be that it's not open source yet, that's fine, but you are > > asking me, as an IPMC Member, to make a judgement on the validity of the > > proposal but I can't evaluate the code since I can't access it or the > > license under which I am allowed to view it. > > > > Most importantly, the "export and license obligations" you mention are > > something that have to go away before we can accept the project (or more > > accurately before it can graduate). Since I can't evaluate the code or > the > > license I have no way of evaluating whether this is possible. There is no > > mention of such an item under "known risks" or the "crypotography" > section > > of the proposal so what's this "export" stuff about (assuming the license > > thing is the evaluation license)? > > > > Given the points above I do not see how I can evaluate this proposal in > > its current form. > > > > Ross > > > > -Original Message- > > From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf Of > > Roman Shaposhnik > > Sent: Sunday, April 12, 2015 11:56 PM > > To: general@incubator.apache.org > > Subject: Re: [DISCUSS] Geode Incubation proposal > > > > Since I'm getting a few off-list questions, I just want to make one point > > clear: > > > > On Sun, Apr 12, 2015 at 8:53 PM, Roman Shaposhnik > > wrote: > > >> I'd also like to be able to review the source referred to in the > > >> proposal without having to sign up to "the Pivotal network" - how can > > I do that? > > > > > > The issue here is export and license compliance. Unfortunately, > > > singing up is the only way to go right now. Why is it problematic for > > you? > > > > The software currently is NOT under ALv2. It is available under the > > evaluation license. The whole point of the proposal is to make it > available > > under ALv2 as an Incubating project. > > > > Our apologies for making folks click through the evaluation license. > > > > Thanks, > > Roman. > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [DISCUSS] Geode Incubation proposal
On Mon, Apr 13, 2015 at 7:38 AM, Roman Shaposhnik wrote: > > There is no mention of such an item under "known risks" or the > "crypotography" section of the proposal > > so what's this "export" stuff about (assuming the license thing is the > evaluation license)? > > Sorry for not being more explicit: this is just how Pivotal > distribution network works. > And we have to use it in this particular case in order to guarantee > that the evaluation > license has been explicitly acknowledged (as opposed to just being there > in a > tarball). All these constraints has nothing to do with the source code > itself. It is fair to put a bit of text into the risks statement that says that the code is currently encumbered with export limitations due to corporate policy but that these limits will be released as part of the software grant.
