Re: [VOTE] Release 1.5.1 of NetBeans HTML/Java API
Remaining fourteen hours of the 72h voting period are ahead us. I guess one more binding vote would be good. Please give HTML/Java API few minutes to cast your vote. Thanks. -jt 2017-11-14 20:47 GMT+01:00 Mark Struberg : > +1 (binding) over here as well again. > LieGrue,strub > > > On Tuesday, 14 November 2017, 10:47:50 GMT+1, Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > > On Mon, Nov 13, 2017 at 10:27 PM, Jaroslav Tulach > wrote: > > ...I'd > > like to ask you to hold the Incubator PMC vote to release: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > +1 for the release of > SHA1(incubating-netbeans-html4j-1.5.1.zip)= > f33391e801d03026f3ca2e989976d264e9750888 > > Checked the signatures, digests, build and depencencies/notice/license > files and rat plugin results. > > Nitpick: DISCLAIMER uses "HTML APIs via Java" as the project name, I > think the project name should include the word "NetBeans" > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 Best Regards, Von Gosling > 在 2017年11月9日，12:25，Jim Apple 写道： > > The graduation of Impala to a TLP has been discussed[0] on dev@impala, > voted on[1] on dev@impala, and discussed[2] on general@incubator. All > threads were open 72 hours or more, and all seem to have quiesced. > > This is a call for a VOTE to graduate Impala to a TLP. The draft resolution > is below. Please select from: > > [ ] +1: Graduate Impala to a TLP > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > [0]: < > https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c0328a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E >> > > [1]: < > https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d67d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E >> > > [2]: < > https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc510470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E >> > > > > Establish the Apache Impala Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to a high-performance distributed SQL engine. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Impala Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Impala Project be and hereby is responsible > for the creation and maintenance of software related to a > high-performance distributed SQL engine; and be it further > > RESOLVED, that the office of "Vice President, Apache Impala" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache Impala > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Impala > Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache Impala Project: > > * Alex Behm > * Bharath Vissapragada > * Brock Noland > * Carl Steinbach > * Casey Ching > * Daniel Hecht > * Dimitris Tsirogiannis > * Henry Robinson > * Ishaan Joshi > * Jim Apple > * John Russell > * Juan Yu > * Lars Volker > * Lenni Kuff > * Marcel Kornacker > * Martin Grund > * Matthew Jacobs > * Michael Brown > * Michael Ho > * Sailesh Mukil > * Skye Wanderman-Milne > * Taras Bobrovytsky > * Tim Armstrong > * Todd Lipcon > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to > the office of Vice President, Apache Impala, to serve in accordance with > and subject to the direction of the Board of Directors and the Bylaws of > the Foundation until death, resignation, retirement, removal or > disqualification, or until a successor is appointed; and be it further > > RESOLVED, that the initial Apache Impala PMC be and hereby is tasked > with the creation of a set of bylaws intended to encourage open > development and increased participation in the Apache Impala Project; > and be it further > > RESOLVED, that the Apache Impala Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator Impala > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Impala podling encumbered upon the Apache Incubator PMC are hereafter > discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 (binding) Willem Jiang On Thu, Nov 16, 2017 at 2:55 AM, Ted Dunning wrote: > +1 > > > > On Wed, Nov 15, 2017 at 12:02 PM, Luke Han wrote: > > > +1 (binding) > > > > > > Best Regards! > > - > > > > Luke Han > > > > On Wed, Nov 15, 2017 at 7:08 AM, Gangumalla, Uma < > uma.ganguma...@intel.com > > > > > wrote: > > > > > +1 (binding) > > > > > > Regards, > > > Uma > > > > > > On Nov 8, 2017 8:28 PM, "Jim Apple" wrote: > > > > > > > The graduation of Impala to a TLP has been discussed[0] on > > dev@impala > > > , > > > > voted on[1] on dev@impala, and discussed[2] on > general@incubator. > > > All > > > > threads were open 72 hours or more, and all seem to have > quiesced. > > > > > > > > This is a call for a VOTE to graduate Impala to a TLP. The draft > > > resolution > > > > is below. Please select from: > > > > > > > > [ ] +1: Graduate Impala to a TLP > > > > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > > > > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > > > > > > > > > > > > > > > [0]: < > > > > https://lists.apache.org/thread.html/ > > 2f5db4788aff9b0557354b9106c032 > > > > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E > > > > > > > > > > > > > [1]: < > > > > https://lists.apache.org/thread.html/ > > a5a7c6895b3e019347d6e4e4cf49d6 > > > > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E > > > > > > > > > > > > > [2]: < > > > > https://lists.apache.org/thread.html/ > > 6b8598408f76a472532923c5a7fc51 > > > > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > > > > > > > > > Establish the Apache Impala Project > > > > > > > > WHEREAS, the Board of Directors deems it to be in the best > > interests > > > of > > > > the Foundation and consistent with the Foundation's purpose to > > > establish > > > > a Project Management Committee charged with the creation and > > > maintenance > > > > of open-source software, for distribution at no charge to the > > public, > > > > related to a high-performance distributed SQL engine. > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee > > > > (PMC), to be known as the "Apache Impala Project", be and hereby > is > > > > established pursuant to Bylaws of the Foundation; and be it > further > > > > > > > > RESOLVED, that the Apache Impala Project be and hereby is > > responsible > > > > for the creation and maintenance of software related to a > > > > high-performance distributed SQL engine; and be it further > > > > > > > > RESOLVED, that the office of "Vice President, Apache Impala" be > and > > > > hereby is created, the person holding such office to serve at the > > > > direction of the Board of Directors as the chair of the Apache > > Impala > > > > Project, and to have primary responsibility for management of the > > > > projects within the scope of responsibility of the Apache Impala > > > > Project; and be it further > > > > > > > > RESOLVED, that the persons listed immediately below be and hereby > > are > > > > appointed to serve as the initial members of the Apache Impala > > > Project: > > > > > > > > * Alex Behm > > > > * Bharath Vissapragada > > > > * Brock Noland > > > > * Carl Steinbach > > > > * Casey Ching > > > > * Daniel Hecht > > > > * Dimitris Tsirogiannis > > > > * Henry Robinson > > > > * Ishaan Joshi > > > > * Jim Apple > > > > * John Russell > > > > * Juan Yu > > > > * Lars Volker > > > > * Lenni Kuff > > > > * Marcel Kornacker > > > > * Martin Grund > > > > * Matthew Jacobs > > > > * Michael Brown > > > > * Michael Ho > > > > * Sailesh Mukil > > > > * Skye Wanderman-Milne > > > > * Taras Bobrovytsky > > > > * Tim Armstrong > > > > * Todd Lipcon > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be > appointed > > > to > > > > the office of Vice President, Apache Impala, to serve in > accordance > > > with > > > > and subject to the direction of the Board of Directors and the > > > Bylaws of > > > > the Foundation until death, resignation, retirement, removal or > > > > disqualification, or until a successor is appointed; and be it > > > further > > > > > > > > RESOLVED, that the initial Apache Impala PMC be and hereby is > > tasked > > > > with the creation of a set of bylaws intended to encourage open > > > > development and increased participation in the Apache Impala > > Project; > > > > and be it further > > > > > > > > RESOLVED, that the Apache
Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]
forwarding my +1 from dev list +1 (binding) Regards, Uma On Tue, Nov 14, 2017 at 4:53 PM, William Guo wrote: > Hi all, > The Apache Griffin community has voted on and approved a proposal to > release Apache Griffin 0.1.6-rc2. > We now kindly request that the Incubator PMC members review and vote > on this incubator release candidate. > > Apache Griffin is data quality service for modern data system, it > defines a standard process to define, measure data quality for well-known > dimensions. With Apache Griffin, users will be able to quickly define their > data quality requirements and then get the result in near real time in > systematical approach. > > > Griffin vote thread > https://lists.apache.org/thread.html/c538bf4293d410bfdb574f605b6da9 > e508f3ef9dc64127e1945888e9@%3Cdev.griffin.apache.org%3E > Griffin vote result thread > https://lists.apache.org/thread.html/769d1c7ad3da35cc02cca960763965 > 48d199126f6e9d6da33ecaf581@%3Cdev.griffin.apache.org%3E > > The source tarball, including signatures, digests, etc. can be found > at: > https://dist.apache.org/repos/dist/dev/incubator/griffin/0. > 1.6-incubating > > The tag to be voted upon is 0.1.6-incubating: > https://git-wip-us.apache.org/repos/asf?p=incubator-griffin. > git;a=shortlog;h=refs/tags/0.1.6-incubating > > The release hash is : > https://git-wip-us.apache.org/repos/asf?p=incubator-griffin. > git;a=commit;h=60e23edc96656f7382b74956bfb057e3eee9dda6 > > The Nexus Staging URL: > https://repository.apache.org/content/repositories/ > orgapachegriffin-1009 > > Release artifacts are signed with the following key: > 753AD8D8DF507D7232A9BDBD9B403B9B1BFBCC23 > > KEYS file available: > https://dist.apache.org/repos/dist/dev/incubator/griffin/KEYS > > For information about the contents of this release, see: > https://dist.apache.org/repos/dist/dev/incubator/griffin/0. > 1.6-incubating/CHANGES.txt > > > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, run and test. > Please vote on releasing this package as Apache Griffin > 0.1.6-incubating > The vote will be open for 72 hours. > [ ] +1 Release this package as Apache Griffin 0.1.6-incubating > [ ] +0 no opinion > [ ] -1 Do not release this package because ... > > > Thanks, > William > on behalf of Apache Griffin PPMC > >
Re: [VOTE] Accept ServiceComb into the Apache Incubator
+1 (binding) Regards, Uma On 11/13/17, 10:15 PM, "Willem Jiang" wrote: Hi All, I would like to start a VOTE to bring the ServiceComb project in as an Apache incubator podling. The ASF voting rules are described: https://www.apache.org/foundation/voting.html A vote for accepting a new Apache Incubator podling is a majority vote for which only Incubator PMC member votes are binding. This vote will run for at least 72 hours. Please VOTE as follows [] +1 Accept ServiceComb into the Apache Incubator [] +0 Abstain. [] -1 Do not accept ServiceComb into the Apache Incubator because ... The proposal is listed below, but you can also access it on the wiki: https://wiki.apache.org/incubator/ServiceCombProposal Best regards, Willem Jiang = ServiceComb Proposal = == Abstract == ServiceComb is a microservice framework that provides a set of tools and components to make development and deployment of cloud applications easier. It provides functionalities such as service contract enforcement, service registration, service discovery, load balance, service reliability (latency and fault tolerance, flow control and graceful degradation, handler chain tracing), eventual data consistency and so forth. == Proposal == The goal of this proposal is to bring the existing ServiceComb codebase and existing developers into the Apache Software Foundation (ASF) in order to build a vibrant, diverse and self-governed open source community around the technology. So far the major contributors to the project have been affiliated with Huawei and Huawei is planning to continue market and sell the Cloud Service Engine leveraging the ServiceComb framework. ServiceComb is currently a registered trademark owned by Huawei, and Huawei is happy to donate this trademark to Apache. Huawei is submitting this proposal to donate the Service source code and associated artifacts (documentation, web site content, wiki, etc.) to the Apache Software Foundation Incubator under the Apache License, Version 2.0 and is asking Incubator PMC to establish an open source community. These artifacts are currently available on GitHub at https://github.com/ServiceComb/ and include: * Java Chassis: a multi-protocol (RPC & Restful) microservice framework which adopts contract-first design * Service Center: a service registry that enforces service contract upon service registration and discovery * Saga: a distributed coordinator to achieve eventual data consistency based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem * ServiceComb.github.io: the website repo of ServiceComb. * The other projects will be moved to another place if ServiceComb is accepted by Apache as an incubator project. == Background == Microservices is a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services. ServiceComb is an open source microservice framework initiated as part of Huawei CSE projects (Cloud Service Engine) which was developed in 2015. It is a part of ServiceStage of Huawei Public Cloud which is one-stop PaaS platform for enterprises and developers. Besides ServiceStage, it’s also used in the Huawei Core Network IOT Platform and Huawei consumer cloud. The number of companies using ServiceComb to develop their enterprise applications, they are chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and the number is over 5 and counting. == Rationale == ServiceComb has been developed as a total, open source solution for developing cloud native applications. So far ServiceComb has existed as a GitHub project with committers mostly working for Huawei. We feel that moving it to a neutral organization like Apache, with its strong governance model, is expected to help get more contributions from various organizations and developers, who may be concerned by exclusive control of ServiceComb by Huawei. == Initial Goals == Our initial goals are to bring ServiceComb into the ASF, transition internal engineering processes into the open, and foster a collaborative development model according to the "Apache Way." Huawei and the current contributors to ServiceComb plan 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. 1. More specifically, our initial plan of moving ServiceComb to ASF is focused on: 2. open up the governance model in order to simplify and streamline contributions from the community 3. move the existing codebase
Re: [DISCUSS] Storage-class memory ecosystem program
and please.. don't just send the log of the discussions here... Email (asynchronous) follows a different format than a chat conversation. When you write an email, you usually put int extra effort on giving the context... when you go to a chat channel is more like.. Example: *** Hey.. wasup.. remember what we were talking yesterday? Yeah.. lets do it.. *** Bang... nobody will know when you send that to the dev list log. when you search 3 months from now.. even less. ok, Ok.. I gave a silly example.. but I can easily see that kind of thing happening in real life. Instead... send an email to the dev list.. summarizing the whole online discussion: *** We had a discussion online, and we had a discussion about "context goes here", and we decided that would be cool to do what "context goes here". ** If you just copy the log from slack into the mail list, you're not really solving the problem. people will just ignore the list and slack became the official source for communications. On Wed, Nov 15, 2017 at 2:52 PM, Bertrand Delacretaz wrote: > On Wed, Nov 15, 2017 at 8:48 PM, Clebert Suconic > wrote: >> ...I still think you should keep discussions >> at the dev list > > Yes. > > "If it didn't happen on the dev list it didn't happen" is stil valid as ever. > > Slack and other channels are fine for throwaway watercooler > discussions, nothing more. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Clebert Suconic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache MXNet (incubating) 0.12.1 release RC0
Sorry for my slowness. +1 from me. On Sun, Nov 12, 2017 at 12:51 AM, Sebastian wrote: > +1 binding > > > On 11.11.2017 07:44, Suneel Marthi wrote: > >> +1 binding >> >> On Sat, Nov 11, 2017 at 4:07 AM, Meghna Baijal < >> meghnabaijal2...@gmail.com> >> wrote: >> >> Hello All, >>> >>> >>> This is a call for releasing Apache MXNet (incubating) 0.12.1, release >>> candidate 0. >>> >>> >>> Apache MXNet community has voted and approved the release. >>> >>> >>> *Vote thread:* >>> >>> https://lists.apache.org/thread.html/254d533bf9b2df9ac2de960ba6303d >>> 89d5d39a783573b4c6e47e4e08@%3Cdev.mxnet.apache.org%3E >>> >>> >>> *Result thread:* >>> >>> https://lists.apache.org/thread.html/2027f372ebff981ea2e585f6215d8a >>> 6a844058e7628a1f16ebd351c9@%3Cdev.mxnet.apache.org%3E >>> >>> >>> *The source tarball, including signatures, digests, etc. can be found >>> at:* >>> >>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.12.1.rc0/ >>> >>> >>> >>> *The release tag can be found here: * >>> >>> https://github.com/apache/incubator-mxnet/tree/0.12.1.rc0 >>> >>> >>> >>> *The release hash is *e0c7906693f0c79b0ce34a4d777c26a6bf1903c1* and can >>> be >>> found here:* >>> >>> https://github.com/apache/incubator-mxnet/commit/ >>> e0c7906693f0c79b0ce34a4d777c26a6bf1903c1 >>> >>> >>> >>> *Release artifacts are signed with the following key:* >>> >>> 69FF E8D6 1051 FFE7 E61B 02C2 80FD 81D7 703D F31B >>> >>> >>> >>> *KEY files are available here:* >>> >>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.12.1.rc0/ >>> >>> >>> >>> *For information about the contents of this release, see:* >>> >>> https://cwiki.apache.org/confluence/display/MXNET/ >>> MXNet+0.12.1+Release+Notes >>> >>> >>> >>> The vote will be open for at least 72 hours. >>> >>> >>> [ ] +1 Release this package as 0.12.1 >>> >>> [ ] +0 no opinion >>> >>> [ ] -1 Do not release this package because... >>> >>> >>> Thanks, >>> >>> Meghna Baijal >>> >>> >> > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Storage-class memory ecosystem program
On Wed, Nov 15, 2017 at 8:48 PM, Clebert Suconic wrote: > ...I still think you should keep discussions > at the dev list Yes. "If it didn't happen on the dev list it didn't happen" is stil valid as ever. Slack and other channels are fine for throwaway watercooler discussions, nothing more. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Storage-class memory ecosystem program
I couldn't find anything at storage-class-memory.slack.com I am joining the thing.. but I still think you should keep discussions at the dev list. if someone could help me to get on the group please? On Wed, Nov 15, 2017 at 2:19 PM, Gang(Gary) Wang wrote: > I see your point, Lazy is one of motivation why we want to code, so perhaps > a Slack summary bot is desired... :-) > > > On Wed, Nov 15, 2017 at 10:46 AM, Clebert Suconic > wrote: > >> I don't think you should sync it... >> >> Someone else please correct me if I'm wrong.. but I was educated >> inside the project I work at.. (activemq) that talking on a private >> list is ok... but you should always direct the discussions to the dev >> list with a summary of the decision.. etc I was once told if it >> didn't happen in the mail list.. it didn't happen. >> >> >> for instance.. a few weeks from now... (Not even saying months or >> years).. the context of the private discussions will be lost.. they >> won't make any sense.. syncing chat here will just spam the list. >> >> >> from my understanding the mail list is the place to go for discussion >> on the apache way. I guess I'm just trying to do the same here.. >> >> for instance I didn't go to the slack channel.. hence nothing really >> happened at apache. >> >> On Wed, Nov 15, 2017 at 1:39 PM, Gary Wong wrote: >> > It is #storage-class-memory >> > >> > Let me take a look to see if there is a way to sync slack channel with >> mail >> > list bi-directionally... >> > >> > On Wed, Nov 15, 2017 at 9:42 AM, Clebert Suconic < >> clebert.suco...@gmail.com> >> > wrote: >> > >> >> All the communication is happening on slatck? >> >> >> >> shouldn't that all happen on a mail list? >> >> >> >> >> >> It's ok to talk on a list.. but you should consider always feeding the >> >> list. >> >> >> >> >> >> What is the slack channel again? I will join in regardless. >> >> >> >> On Wed, Nov 15, 2017 at 11:56 AM, Gang(Gary) Wang >> >> wrote: >> >> > Hi Lewis, >> >> > >> >> > Invitation sent, Welcome to join us. >> >> > >> >> > Best. >> >> > Gary >> >> > >> >> > >> >> > On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney < >> >> lewi...@apache.org> >> >> > wrote: >> >> > >> >> >> Hi Gary, >> >> >> I was watching this thread evolve a while back and ended up dropping >> >> it. I >> >> >> have been working on Apache Gora (Generic Object Representation using >> >> Avro) >> >> >> for a number of years. Gora is described as follows >> >> >> >> >> >> The Apache Gora open source framework provides an in-memory data >> model >> >> >> and persistence for big data. Gora supports persisting to >> >> >> * column stores, >> >> >> * key value stores, >> >> >> * document stores, >> >> >> * distributed in-memory key/value stores, >> >> >> * in-memory data grids, >> >> >> * in-memory caches, >> >> >> * distributed multi-model stores, and >> >> >> * hybrid in-memory architectures >> >> >> Gora also enables analysis of data with extensive Apache Hadoop >> >> MapReduce >> >> >> and Apache Spark support. Gora uses the Apache Software License v2.0. >> >> >> >> >> >> Please send me an invite to the slack channel > >> org> >> >> >> >> >> >> Thanks >> >> >> Lewis >> >> >> >> >> >> On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: >> >> >> > Hi all, >> >> >> > >> >> >> > We can expect more and more projects will take the huge potential >> >> >> > advantages of storage-class memory for data processing and >> analytics >> >> >> > because silicon companies are able to produce high capacity >> >> non-volatile >> >> >> > memory on a large scale, this hardware technology will >> fundamentally >> >> >> change >> >> >> > the way to construct high performance applications similar to what >> >> >> happened >> >> >> > when replacing tape with disk technology since the 1980s. so if >> >> >> possible, I >> >> >> > advocate establishing an Apache working group to enhance the >> >> >> collaboration >> >> >> > and synergies mentioned by Patrick Stuedi for storage-class memory >> >> >> > technology-oriented projects. >> >> >> > >> >> >> > Best. >> >> >> > Gary. >> >> >> > >> >> >> >> >> >> >> - >> >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >> >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Clebert Suconic >> >> >> >> - >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >> >> >> >> >> >> -- >> Clebert Suconic >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> -- Clebert Suconic - To un
Re: [DISCUSS] Storage-class memory ecosystem program
I see your point, Lazy is one of motivation why we want to code, so perhaps a Slack summary bot is desired... :-) On Wed, Nov 15, 2017 at 10:46 AM, Clebert Suconic wrote: > I don't think you should sync it... > > Someone else please correct me if I'm wrong.. but I was educated > inside the project I work at.. (activemq) that talking on a private > list is ok... but you should always direct the discussions to the dev > list with a summary of the decision.. etc I was once told if it > didn't happen in the mail list.. it didn't happen. > > > for instance.. a few weeks from now... (Not even saying months or > years).. the context of the private discussions will be lost.. they > won't make any sense.. syncing chat here will just spam the list. > > > from my understanding the mail list is the place to go for discussion > on the apache way. I guess I'm just trying to do the same here.. > > for instance I didn't go to the slack channel.. hence nothing really > happened at apache. > > On Wed, Nov 15, 2017 at 1:39 PM, Gary Wong wrote: > > It is #storage-class-memory > > > > Let me take a look to see if there is a way to sync slack channel with > mail > > list bi-directionally... > > > > On Wed, Nov 15, 2017 at 9:42 AM, Clebert Suconic < > clebert.suco...@gmail.com> > > wrote: > > > >> All the communication is happening on slatck? > >> > >> shouldn't that all happen on a mail list? > >> > >> > >> It's ok to talk on a list.. but you should consider always feeding the > >> list. > >> > >> > >> What is the slack channel again? I will join in regardless. > >> > >> On Wed, Nov 15, 2017 at 11:56 AM, Gang(Gary) Wang > >> wrote: > >> > Hi Lewis, > >> > > >> > Invitation sent, Welcome to join us. > >> > > >> > Best. > >> > Gary > >> > > >> > > >> > On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney < > >> lewi...@apache.org> > >> > wrote: > >> > > >> >> Hi Gary, > >> >> I was watching this thread evolve a while back and ended up dropping > >> it. I > >> >> have been working on Apache Gora (Generic Object Representation using > >> Avro) > >> >> for a number of years. Gora is described as follows > >> >> > >> >> The Apache Gora open source framework provides an in-memory data > model > >> >> and persistence for big data. Gora supports persisting to > >> >> * column stores, > >> >> * key value stores, > >> >> * document stores, > >> >> * distributed in-memory key/value stores, > >> >> * in-memory data grids, > >> >> * in-memory caches, > >> >> * distributed multi-model stores, and > >> >> * hybrid in-memory architectures > >> >> Gora also enables analysis of data with extensive Apache Hadoop > >> MapReduce > >> >> and Apache Spark support. Gora uses the Apache Software License v2.0. > >> >> > >> >> Please send me an invite to the slack channel >> org> > >> >> > >> >> Thanks > >> >> Lewis > >> >> > >> >> On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: > >> >> > Hi all, > >> >> > > >> >> > We can expect more and more projects will take the huge potential > >> >> > advantages of storage-class memory for data processing and > analytics > >> >> > because silicon companies are able to produce high capacity > >> non-volatile > >> >> > memory on a large scale, this hardware technology will > fundamentally > >> >> change > >> >> > the way to construct high performance applications similar to what > >> >> happened > >> >> > when replacing tape with disk technology since the 1980s. so if > >> >> possible, I > >> >> > advocate establishing an Apache working group to enhance the > >> >> collaboration > >> >> > and synergies mentioned by Patrick Stuedi for storage-class memory > >> >> > technology-oriented projects. > >> >> > > >> >> > Best. > >> >> > Gary. > >> >> > > >> >> > >> >> > - > >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> >> For additional commands, e-mail: general-h...@incubator.apache.org > >> >> > >> >> > >> > >> > >> > >> -- > >> Clebert Suconic > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > -- > Clebert Suconic > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[RESULT][VOTE]Release of Apache Mnemonic-0.10.0-incubating [rc1]
Hi all, After being opened for over more than 72 hours, the vote for releasing Apache Mnemonic 0.10.0-incubating passed with 3 binding +1s, 2 non-binding +1s and no 0 or -1. The link to vote thread is https://mail-archives.apache.org/mod_mbox/incubator-general/201711.mbox/ * Binding votes +1s: * Henry Saputra (hsaputra) Gangumalla, Uma (umamahesh) Luke Han(lukehan) * Non-binding votes +1s: * Gang Wang (garyw) Carlos Alberto Villavicencio Sanchez (solrac901) <0 or -1 vote if any> Project Members Role Info http://mnemonic.incubator.apache.org/develop/ *Thanks all* Cheers Johnu on behalf of the Apache Mnemonic (incubating) community - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 On Wed, Nov 15, 2017 at 12:02 PM, Luke Han wrote: > +1 (binding) > > > Best Regards! > - > > Luke Han > > On Wed, Nov 15, 2017 at 7:08 AM, Gangumalla, Uma > > wrote: > > > +1 (binding) > > > > Regards, > > Uma > > > > On Nov 8, 2017 8:28 PM, "Jim Apple" wrote: > > > > > The graduation of Impala to a TLP has been discussed[0] on > dev@impala > > , > > > voted on[1] on dev@impala, and discussed[2] on general@incubator. > > All > > > threads were open 72 hours or more, and all seem to have quiesced. > > > > > > This is a call for a VOTE to graduate Impala to a TLP. The draft > > resolution > > > is below. Please select from: > > > > > > [ ] +1: Graduate Impala to a TLP > > > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > > > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > > > > > > > > > > [0]: < > > > https://lists.apache.org/thread.html/ > 2f5db4788aff9b0557354b9106c032 > > > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E > > > > > > > > > > [1]: < > > > https://lists.apache.org/thread.html/ > a5a7c6895b3e019347d6e4e4cf49d6 > > > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E > > > > > > > > > > [2]: < > > > https://lists.apache.org/thread.html/ > 6b8598408f76a472532923c5a7fc51 > > > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > > > Establish the Apache Impala Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best > interests > > of > > > the Foundation and consistent with the Foundation's purpose to > > establish > > > a Project Management Committee charged with the creation and > > maintenance > > > of open-source software, for distribution at no charge to the > public, > > > related to a high-performance distributed SQL engine. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache Impala Project", be and hereby is > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache Impala Project be and hereby is > responsible > > > for the creation and maintenance of software related to a > > > high-performance distributed SQL engine; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache Impala" be and > > > hereby is created, the person holding such office to serve at the > > > direction of the Board of Directors as the chair of the Apache > Impala > > > Project, and to have primary responsibility for management of the > > > projects within the scope of responsibility of the Apache Impala > > > Project; and be it further > > > > > > RESOLVED, that the persons listed immediately below be and hereby > are > > > appointed to serve as the initial members of the Apache Impala > > Project: > > > > > > * Alex Behm > > > * Bharath Vissapragada > > > * Brock Noland > > > * Carl Steinbach > > > * Casey Ching > > > * Daniel Hecht > > > * Dimitris Tsirogiannis > > > * Henry Robinson > > > * Ishaan Joshi > > > * Jim Apple > > > * John Russell > > > * Juan Yu > > > * Lars Volker > > > * Lenni Kuff > > > * Marcel Kornacker > > > * Martin Grund > > > * Matthew Jacobs > > > * Michael Brown > > > * Michael Ho > > > * Sailesh Mukil > > > * Skye Wanderman-Milne > > > * Taras Bobrovytsky > > > * Tim Armstrong > > > * Todd Lipcon > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed > > to > > > the office of Vice President, Apache Impala, to serve in accordance > > with > > > and subject to the direction of the Board of Directors and the > > Bylaws of > > > the Foundation until death, resignation, retirement, removal or > > > disqualification, or until a successor is appointed; and be it > > further > > > > > > RESOLVED, that the initial Apache Impala PMC be and hereby is > tasked > > > with the creation of a set of bylaws intended to encourage open > > > development and increased participation in the Apache Impala > Project; > > > and be it further > > > > > > RESOLVED, that the Apache Impala Project be and hereby is tasked > with > > > the migration and rationalization of the Apache Incubator Impala > > > podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator > > > Impala podling encumbered upon the Apache Incubator PMC are > hereafter > > > discharged. > > > > > > > > > >
Re: [DISCUSS] Storage-class memory ecosystem program
I don't think you should sync it... Someone else please correct me if I'm wrong.. but I was educated inside the project I work at.. (activemq) that talking on a private list is ok... but you should always direct the discussions to the dev list with a summary of the decision.. etc I was once told if it didn't happen in the mail list.. it didn't happen. for instance.. a few weeks from now... (Not even saying months or years).. the context of the private discussions will be lost.. they won't make any sense.. syncing chat here will just spam the list. from my understanding the mail list is the place to go for discussion on the apache way. I guess I'm just trying to do the same here.. for instance I didn't go to the slack channel.. hence nothing really happened at apache. On Wed, Nov 15, 2017 at 1:39 PM, Gary Wong wrote: > It is #storage-class-memory > > Let me take a look to see if there is a way to sync slack channel with mail > list bi-directionally... > > On Wed, Nov 15, 2017 at 9:42 AM, Clebert Suconic > wrote: > >> All the communication is happening on slatck? >> >> shouldn't that all happen on a mail list? >> >> >> It's ok to talk on a list.. but you should consider always feeding the >> list. >> >> >> What is the slack channel again? I will join in regardless. >> >> On Wed, Nov 15, 2017 at 11:56 AM, Gang(Gary) Wang >> wrote: >> > Hi Lewis, >> > >> > Invitation sent, Welcome to join us. >> > >> > Best. >> > Gary >> > >> > >> > On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney < >> lewi...@apache.org> >> > wrote: >> > >> >> Hi Gary, >> >> I was watching this thread evolve a while back and ended up dropping >> it. I >> >> have been working on Apache Gora (Generic Object Representation using >> Avro) >> >> for a number of years. Gora is described as follows >> >> >> >> The Apache Gora open source framework provides an in-memory data model >> >> and persistence for big data. Gora supports persisting to >> >> * column stores, >> >> * key value stores, >> >> * document stores, >> >> * distributed in-memory key/value stores, >> >> * in-memory data grids, >> >> * in-memory caches, >> >> * distributed multi-model stores, and >> >> * hybrid in-memory architectures >> >> Gora also enables analysis of data with extensive Apache Hadoop >> MapReduce >> >> and Apache Spark support. Gora uses the Apache Software License v2.0. >> >> >> >> Please send me an invite to the slack channel > org> >> >> >> >> Thanks >> >> Lewis >> >> >> >> On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: >> >> > Hi all, >> >> > >> >> > We can expect more and more projects will take the huge potential >> >> > advantages of storage-class memory for data processing and analytics >> >> > because silicon companies are able to produce high capacity >> non-volatile >> >> > memory on a large scale, this hardware technology will fundamentally >> >> change >> >> > the way to construct high performance applications similar to what >> >> happened >> >> > when replacing tape with disk technology since the 1980s. so if >> >> possible, I >> >> > advocate establishing an Apache working group to enhance the >> >> collaboration >> >> > and synergies mentioned by Patrick Stuedi for storage-class memory >> >> > technology-oriented projects. >> >> > >> >> > Best. >> >> > Gary. >> >> > >> >> >> >> - >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >> >> >> >> >> >> -- >> Clebert Suconic >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> -- Clebert Suconic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Storage-class memory ecosystem program
It is #storage-class-memory Let me take a look to see if there is a way to sync slack channel with mail list bi-directionally... On Wed, Nov 15, 2017 at 9:42 AM, Clebert Suconic wrote: > All the communication is happening on slatck? > > shouldn't that all happen on a mail list? > > > It's ok to talk on a list.. but you should consider always feeding the > list. > > > What is the slack channel again? I will join in regardless. > > On Wed, Nov 15, 2017 at 11:56 AM, Gang(Gary) Wang > wrote: > > Hi Lewis, > > > > Invitation sent, Welcome to join us. > > > > Best. > > Gary > > > > > > On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney < > lewi...@apache.org> > > wrote: > > > >> Hi Gary, > >> I was watching this thread evolve a while back and ended up dropping > it. I > >> have been working on Apache Gora (Generic Object Representation using > Avro) > >> for a number of years. Gora is described as follows > >> > >> The Apache Gora open source framework provides an in-memory data model > >> and persistence for big data. Gora supports persisting to > >> * column stores, > >> * key value stores, > >> * document stores, > >> * distributed in-memory key/value stores, > >> * in-memory data grids, > >> * in-memory caches, > >> * distributed multi-model stores, and > >> * hybrid in-memory architectures > >> Gora also enables analysis of data with extensive Apache Hadoop > MapReduce > >> and Apache Spark support. Gora uses the Apache Software License v2.0. > >> > >> Please send me an invite to the slack channel org> > >> > >> Thanks > >> Lewis > >> > >> On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: > >> > Hi all, > >> > > >> > We can expect more and more projects will take the huge potential > >> > advantages of storage-class memory for data processing and analytics > >> > because silicon companies are able to produce high capacity > non-volatile > >> > memory on a large scale, this hardware technology will fundamentally > >> change > >> > the way to construct high performance applications similar to what > >> happened > >> > when replacing tape with disk technology since the 1980s. so if > >> possible, I > >> > advocate establishing an Apache working group to enhance the > >> collaboration > >> > and synergies mentioned by Patrick Stuedi for storage-class memory > >> > technology-oriented projects. > >> > > >> > Best. > >> > Gary. > >> > > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > -- > Clebert Suconic > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release of Apache Mnemonic-0.10.0-incubating [rc1]
Forward binding vote from dev list: +1 (binding) On Thu, Nov 9, 2017 at 12:47 PM Johnu George wrote: > Hello incubator PMCs, > > The Apache Mnemonic community PPMCs and developers have voted and > approved the proposal to release Apache Mnemonic 0.10.0 (incubating). > Apache Mnemonic is an advanced hybrid memory storage oriented library, > it's proposed a non-volatile/durable Java object model and durable > computing model that bring several advantages to significantly improve > the performance of massive real-time data processing/analytics. > Developers can use this library to design their cache-less and SerDe > less high performance applications. > > > [VOTE] thread: > > > http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201711.mbox/%3CCALuGr6auOV9BqQ5FNmQ_V%2B5qbzrNfiaH6gYyxk-H%2BLBhmo%3DwuA%40mail.gmail.com%3E > > > http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201711.mbox/%3CCANLc_9%2BeJ%2BZURAZT%2BTfr-U3AgV5q0h5R7o%3DdA_rd6nf0nd%3DNHA%40mail.gmail.com%3E > > [VOTE RESULT] thread: > > > http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201711.mbox/%3CCABtC0%2Bj2eV1fAMSJU4PEVOsoDUfPBUdQvbnXd5HTN4oSpjauKg%40mail.gmail.com%3E > > We now kindly request the Incubator PMC members review and vote on > this incubator release. > > The Apache Mnemonic-0.10.0-incubating release candidate is now > available with the following artifacts for a project vote: > > The source tarball, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.10.0-incubating-rc1/src/ > > The tag to be voted upon is v0.10.0-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=shortlog;h=refs/tags/v0.10.0-incubating > > The release hash is 0e6cf3534b2f1a6407021e0d99073d794690f71b: > > https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=commit;h=0e6cf3534b2f1a6407021e0d99073d794690f71b > > Release artifacts are signed with the following key: > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS > > KEYS file available: > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS > > For information about the contents of this release, see: > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.10.0-incubating-rc1/CHANGES.txt > > The vote will be open for ~72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. The > please vote: > > [ ] +1 Release this package as apache-mnemonic-0.10.0-incubating > [ ] +0 no opinion > [ ] -1 Do not release this package because... > > Thanks, > Johnu on behalf of the Apache Mnemonic (incubating) community > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [Vote] Release of Apache-Griffin-0.1.6-incubating [RC2]
Forward binding vote from dev list: +1 (binding) On Tue, Nov 14, 2017 at 5:56 PM William Guo wrote: > Hi all, > The Apache Griffin community has voted on and approved a proposal to > release Apache Griffin 0.1.6-rc2. > We now kindly request that the Incubator PMC members review and vote > on this incubator release candidate. > > Apache Griffin is data quality service for modern data system, it > defines a standard process to define, measure data quality for well-known > dimensions. With Apache Griffin, users will be able to quickly define their > data quality requirements and then get the result in near real time in > systematical approach. > > > Griffin vote thread > > https://lists.apache.org/thread.html/c538bf4293d410bfdb574f605b6da9e508f3ef9dc64127e1945888e9@%3Cdev.griffin.apache.org%3E > Griffin vote result thread > > https://lists.apache.org/thread.html/769d1c7ad3da35cc02cca96076396548d199126f6e9d6da33ecaf581@%3Cdev.griffin.apache.org%3E > > The source tarball, including signatures, digests, etc. can be found > at: > > https://dist.apache.org/repos/dist/dev/incubator/griffin/0.1.6-incubating > > The tag to be voted upon is 0.1.6-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.git;a=shortlog;h=refs/tags/0.1.6-incubating > > The release hash is : > > https://git-wip-us.apache.org/repos/asf?p=incubator-griffin.git;a=commit;h=60e23edc96656f7382b74956bfb057e3eee9dda6 > > The Nexus Staging URL: > > https://repository.apache.org/content/repositories/orgapachegriffin-1009 > > Release artifacts are signed with the following key: > 753AD8D8DF507D7232A9BDBD9B403B9B1BFBCC23 > > KEYS file available: > https://dist.apache.org/repos/dist/dev/incubator/griffin/KEYS > > For information about the contents of this release, see: > > https://dist.apache.org/repos/dist/dev/incubator/griffin/0.1.6-incubating/CHANGES.txt > > > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, run and test. > Please vote on releasing this package as Apache Griffin > 0.1.6-incubating > The vote will be open for 72 hours. > [ ] +1 Release this package as Apache Griffin 0.1.6-incubating > [ ] +0 no opinion > [ ] -1 Do not release this package because ... > > > Thanks, > William > on behalf of Apache Griffin PPMC > >
Re: [DISCUSS] Storage-class memory ecosystem program
All the communication is happening on slatck? shouldn't that all happen on a mail list? It's ok to talk on a list.. but you should consider always feeding the list. What is the slack channel again? I will join in regardless. On Wed, Nov 15, 2017 at 11:56 AM, Gang(Gary) Wang wrote: > Hi Lewis, > > Invitation sent, Welcome to join us. > > Best. > Gary > > > On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney > wrote: > >> Hi Gary, >> I was watching this thread evolve a while back and ended up dropping it. I >> have been working on Apache Gora (Generic Object Representation using Avro) >> for a number of years. Gora is described as follows >> >> The Apache Gora open source framework provides an in-memory data model >> and persistence for big data. Gora supports persisting to >> * column stores, >> * key value stores, >> * document stores, >> * distributed in-memory key/value stores, >> * in-memory data grids, >> * in-memory caches, >> * distributed multi-model stores, and >> * hybrid in-memory architectures >> Gora also enables analysis of data with extensive Apache Hadoop MapReduce >> and Apache Spark support. Gora uses the Apache Software License v2.0. >> >> Please send me an invite to the slack channel >> >> Thanks >> Lewis >> >> On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: >> > Hi all, >> > >> > We can expect more and more projects will take the huge potential >> > advantages of storage-class memory for data processing and analytics >> > because silicon companies are able to produce high capacity non-volatile >> > memory on a large scale, this hardware technology will fundamentally >> change >> > the way to construct high performance applications similar to what >> happened >> > when replacing tape with disk technology since the 1980s. so if >> possible, I >> > advocate establishing an Apache working group to enhance the >> collaboration >> > and synergies mentioned by Patrick Stuedi for storage-class memory >> > technology-oriented projects. >> > >> > Best. >> > Gary. >> > >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> -- Clebert Suconic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Storage-class memory ecosystem program
Hi Lewis, Invitation sent, Welcome to join us. Best. Gary On Tue, Nov 14, 2017 at 11:24 PM, Lewis John McGibbney wrote: > Hi Gary, > I was watching this thread evolve a while back and ended up dropping it. I > have been working on Apache Gora (Generic Object Representation using Avro) > for a number of years. Gora is described as follows > > The Apache Gora open source framework provides an in-memory data model > and persistence for big data. Gora supports persisting to > * column stores, > * key value stores, > * document stores, > * distributed in-memory key/value stores, > * in-memory data grids, > * in-memory caches, > * distributed multi-model stores, and > * hybrid in-memory architectures > Gora also enables analysis of data with extensive Apache Hadoop MapReduce > and Apache Spark support. Gora uses the Apache Software License v2.0. > > Please send me an invite to the slack channel > > Thanks > Lewis > > On 2017-10-19 11:55, "Gang(Gary) Wang" wrote: > > Hi all, > > > > We can expect more and more projects will take the huge potential > > advantages of storage-class memory for data processing and analytics > > because silicon companies are able to produce high capacity non-volatile > > memory on a large scale, this hardware technology will fundamentally > change > > the way to construct high performance applications similar to what > happened > > when replacing tape with disk technology since the 1980s. so if > possible, I > > advocate establishing an Apache working group to enhance the > collaboration > > and synergies mentioned by Patrick Stuedi for storage-class memory > > technology-oriented projects. > > > > Best. > > Gary. > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 (binding) Best Regards! - Luke Han On Wed, Nov 15, 2017 at 7:08 AM, Gangumalla, Uma wrote: > +1 (binding) > > Regards, > Uma > > On Nov 8, 2017 8:28 PM, "Jim Apple" wrote: > > > The graduation of Impala to a TLP has been discussed[0] on dev@impala > , > > voted on[1] on dev@impala, and discussed[2] on general@incubator. > All > > threads were open 72 hours or more, and all seem to have quiesced. > > > > This is a call for a VOTE to graduate Impala to a TLP. The draft > resolution > > is below. Please select from: > > > > [ ] +1: Graduate Impala to a TLP > > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > > > > > [0]: < > > https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032 > > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E > > > > > > > [1]: < > > https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6 > > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E > > > > > > > [2]: < > > https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc51 > > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > Establish the Apache Impala Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests > of > > the Foundation and consistent with the Foundation's purpose to > establish > > a Project Management Committee charged with the creation and > maintenance > > of open-source software, for distribution at no charge to the public, > > related to a high-performance distributed SQL engine. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache Impala Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache Impala Project be and hereby is responsible > > for the creation and maintenance of software related to a > > high-performance distributed SQL engine; and be it further > > > > RESOLVED, that the office of "Vice President, Apache Impala" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache Impala > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache Impala > > Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache Impala > Project: > > > > * Alex Behm > > * Bharath Vissapragada > > * Brock Noland > > * Carl Steinbach > > * Casey Ching > > * Daniel Hecht > > * Dimitris Tsirogiannis > > * Henry Robinson > > * Ishaan Joshi > > * Jim Apple > > * John Russell > > * Juan Yu > > * Lars Volker > > * Lenni Kuff > > * Marcel Kornacker > > * Martin Grund > > * Matthew Jacobs > > * Michael Brown > > * Michael Ho > > * Sailesh Mukil > > * Skye Wanderman-Milne > > * Taras Bobrovytsky > > * Tim Armstrong > > * Todd Lipcon > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed > to > > the office of Vice President, Apache Impala, to serve in accordance > with > > and subject to the direction of the Board of Directors and the > Bylaws of > > the Foundation until death, resignation, retirement, removal or > > disqualification, or until a successor is appointed; and be it > further > > > > RESOLVED, that the initial Apache Impala PMC be and hereby is tasked > > with the creation of a set of bylaws intended to encourage open > > development and increased participation in the Apache Impala Project; > > and be it further > > > > RESOLVED, that the Apache Impala Project be and hereby is tasked with > > the migration and rationalization of the Apache Incubator Impala > > podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator > > Impala podling encumbered upon the Apache Incubator PMC are hereafter > > discharged. > > > > >
Re: [VOTE] Accept ServiceComb into the Apache Incubator
+1 (binding) Thanks Luke Best Regards! - Luke Han On Wed, Nov 15, 2017 at 4:07 PM, Sean Yin wrote: > +1 > > Best Regards, > Sean > > On Wed, Nov 15, 2017 at 4:38 AM, Dave Fisher > wrote: > > > +1 (Binding) > > > > > On Nov 13, 2017, at 10:15 PM, Willem Jiang > > wrote: > > > > > > Hi All, > > > > > > I would like to start a VOTE to bring the ServiceComb project in as an > > > Apache incubator podling. > > > > > > The ASF voting rules are described: > > > > > > https://www.apache.org/foundation/voting.html > > > > > > A vote for accepting a new Apache Incubator podling is a majority vote > > for > > > which only Incubator PMC member votes are binding. > > > > > > This vote will run for at least 72 hours. Please VOTE as follows > > > [] +1 Accept ServiceComb into the Apache Incubator > > > [] +0 Abstain. > > > [] -1 Do not accept ServiceComb into the Apache Incubator because ... > > > > > > The proposal is listed below, but you can also access it on the wiki: > > > > > > https://wiki.apache.org/incubator/ServiceCombProposal > > > > > > Best regards, > > > > > > Willem Jiang > > > > > > = ServiceComb Proposal = > > > > > > == Abstract == > > > > > > ServiceComb is a microservice framework that provides a set of tools > and > > > components to make development and deployment of cloud applications > > easier. > > > It provides functionalities such as service contract enforcement, > service > > > registration, service discovery, load balance, service reliability > > (latency > > > and fault tolerance, flow control and graceful degradation, handler > chain > > > tracing), eventual data consistency and so forth. > > > > > > == Proposal == > > > > > > The goal of this proposal is to bring the existing ServiceComb codebase > > and > > > existing developers into the Apache Software Foundation (ASF) in order > to > > > build a vibrant, diverse and self-governed open source community around > > the > > > technology. > > > So far the major contributors to the project have been affiliated with > > > Huawei and Huawei is planning to continue market and sell the Cloud > > Service > > > Engine leveraging the ServiceComb framework. > > > ServiceComb is currently a registered trademark owned by Huawei, and > > Huawei > > > is happy to donate this trademark to Apache. > > > > > > Huawei is submitting this proposal to donate the Service source code > and > > > associated artifacts (documentation, web site content, wiki, etc.) to > the > > > Apache Software Foundation Incubator under the Apache License, Version > > 2.0 > > > and is asking Incubator PMC to establish an open source community. > These > > > artifacts are currently available on GitHub at > > > https://github.com/ServiceComb/ and include: > > > * Java Chassis: a multi-protocol (RPC & Restful) microservice framework > > > which adopts contract-first design > > > * Service Center: a service registry that enforces service contract > upon > > > service registration and discovery > > > * Saga: a distributed coordinator to achieve eventual data consistency > > > based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem > > > * ServiceComb.github.io: the website repo of ServiceComb. > > > * The other projects will be moved to another place if ServiceComb is > > > accepted by Apache as an incubator project. > > > > > > == Background == > > > > > > Microservices is a variant of the service-oriented architecture (SOA) > > > architectural style that structures an application as a collection of > > > loosely coupled services. ServiceComb is an open source microservice > > > framework initiated as part of Huawei CSE projects (Cloud Service > Engine) > > > which was developed in 2015. It is a part of ServiceStage of Huawei > > Public > > > Cloud which is one-stop PaaS platform for enterprises and developers. > > > Besides ServiceStage, it’s also used in the Huawei Core Network IOT > > > Platform and Huawei consumer cloud. The number of companies using > > > ServiceComb to develop their enterprise applications, they are > > > chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, > and > > the > > > number is over 5 and counting. > > > > > > == Rationale == > > > > > > ServiceComb has been developed as a total, open source solution for > > > developing cloud native applications. So far ServiceComb has existed > as a > > > GitHub project with committers mostly working for Huawei. We feel that > > > moving it to a neutral organization like Apache, with its strong > > governance > > > model, is expected to help get more contributions from various > > > organizations and developers, who may be concerned by exclusive control > > of > > > ServiceComb by Huawei. > > > > > > == Initial Goals == > > > > > > Our initial goals are to bring ServiceComb into the ASF, transition > > > internal engineering processes into the open, and foster a > collaborative > > > development model according to the "Apache Way." Huawei and the current > > >
Re: [VOTE] Release of Apache Mnemonic-0.10.0-incubating [rc1]
+1 (binding) Luke Best Regards! - Luke Han On Wed, Nov 15, 2017 at 7:06 AM, Gangumalla, Uma wrote: > +1 (binding) > > Regards, > Uma > > On 11/14/17, 1:41 PM, "Gang(Gary) Wang" wrote: > > +1 Thanks! > > Best, > Gary > > > On Tue, Nov 14, 2017 at 9:27 AM, solrac...@apache.org < > solrac...@apache.org> > wrote: > > > +1 > > > > 2017-11-14 11:19 GMT-06:00 Johnu George : > > > > > Hi everyone, > > >Can you please vote for this new release? > > > > > > Thanks, > > > Johnu > > > > > > On Thu, Nov 9, 2017 at 11:47 AM, Johnu George > wrote: > > > > Hello incubator PMCs, > > > > > > > > The Apache Mnemonic community PPMCs and developers have voted and > > > > approved the proposal to release Apache Mnemonic 0.10.0 > (incubating). > > > > Apache Mnemonic is an advanced hybrid memory storage oriented > library, > > > > it's proposed a non-volatile/durable Java object model and > durable > > > > computing model that bring several advantages to significantly > improve > > > > the performance of massive real-time data processing/analytics. > > > > Developers can use this library to design their cache-less and > SerDe > > > > less high performance applications. > > > > > > > > > > > > [VOTE] thread: > > > > > > > > http://mail-archives.apache.org/mod_mbox/incubator- > > > mnemonic-dev/201711.mbox/%3CCALuGr6auOV9BqQ5FNmQ_V% > > > 2B5qbzrNfiaH6gYyxk-H%2BLBhmo%3DwuA%40mail.gmail.com%3E > > > > > > > > http://mail-archives.apache.org/mod_mbox/incubator- > > > mnemonic-dev/201711.mbox/%3CCANLc_9%2BeJ%2BZURAZT%2BTfr- > > > U3AgV5q0h5R7o%3DdA_rd6nf0nd%3DNHA%40mail.gmail.com%3E > > > > > > > > [VOTE RESULT] thread: > > > > > > > > http://mail-archives.apache.org/mod_mbox/incubator- > > > mnemonic-dev/201711.mbox/%3CCABtC0%2Bj2eV1fAMSJU4PEVOsoDUfPBUdQvb > > > nXd5HTN4oSpjauKg%40mail.gmail.com%3E > > > > > > > > We now kindly request the Incubator PMC members review and vote > on > > > > this incubator release. > > > > > > > > The Apache Mnemonic-0.10.0-incubating release candidate is now > > > > available with the following artifacts for a project vote: > > > > > > > > The source tarball, including signatures, digests, etc. can be > found > > at: > > > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0. > > > 10.0-incubating-rc1/src/ > > > > > > > > The tag to be voted upon is v0.10.0-incubating: > > > > https://git-wip-us.apache.org/repos/asf?p=incubator- > > > mnemonic.git;a=shortlog;h=refs/tags/v0.10.0-incubating > > > > > > > > The release hash is 0e6cf3534b2f1a6407021e0d99073d794690f71b: > > > > https://git-wip-us.apache.org/repos/asf?p=incubator- > > > mnemonic.git;a=commit;h=0e6cf3534b2f1a6407021e0d99073d794690f71b > > > > > > > > Release artifacts are signed with the following key: > > > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS > > > > > > > > KEYS file available: > > > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS > > > > > > > > For information about the contents of this release, see: > > > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0. > > > 10.0-incubating-rc1/CHANGES.txt > > > > > > > > The vote will be open for ~72 hours. > > > > Please download the release candidate and evaluate the necessary > items > > > > including checking hashes, signatures, build from source, and > test. > > The > > > > please vote: > > > > > > > > [ ] +1 Release this package as apache-mnemonic-0.10.0-incubating > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > > Thanks, > > > > Johnu on behalf of the Apache Mnemonic (incubating) community > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > >
Re: Naming was: Release 1.5.1 of NetBeans HTML/Java API
Hi, On Wed, Nov 15, 2017 at 9:40 AM, Jaroslav Tulach wrote: > ...People usually associate NetBeans with the image of an IDE. Or (at most) > with the image of general desktop application platform. However HTML/Java > API is different - it is heavily portable API that works everywrhere - it > is almost like "Cordova for Java"... >From an Apache point of view it's important IMO that projects be associated with their (P)PMCs, so NetBeans in your case. I understand what you're saying about that module being fairly independent of the IDE - I suppose that can be expressed in the modules description. I suggest discussing the details on the NetBeans dev list. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Naming was: Release 1.5.1 of NetBeans HTML/Java API
2017-11-14 10:47 GMT+01:00 Bertrand Delacretaz : > On Mon, Nov 13, 2017 at 10:27 PM, Jaroslav Tulach > wrote: > > ...I'd > > like to ask you to hold the Incubator PMC vote to release: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > +1 for the release of > SHA1(incubating-netbeans-html4j-1.5.1.zip)= > f33391e801d03026f3ca2e989976d264e9750888 > > Checked the signatures, digests, build and depencencies/notice/license > files and rat plugin results. > Thanks for the check, Bertrand. > > Nitpick: DISCLAIMER uses "HTML APIs via Java" as the project name, I > think the project name should include the word "NetBeans" > > True, the project is part of NetBeans Apache incubation, so it should not be ashamed to share the NetBeans name. I can change that for next version, unless following convinces you that it is not needed: People usually associate NetBeans with the image of an IDE. Or (at most) with the image of general desktop application platform. However HTML/Java API is different - it is heavily portable API that works everywrhere - it is almost like "Cordova for Java". The API is part of NetBeans as it allows us to write parts of the IDE in HTML5. However to stress the general purpose usefulness of the API I hesitated to highlight the relation with NetBeans in previous pre-Apache releases. That is the reason while I was avoiding mentions of NetBeans in the name of the API. -jt
Re: [VOTE] Accept ServiceComb into the Apache Incubator
+1 Best Regards, Sean On Wed, Nov 15, 2017 at 4:38 AM, Dave Fisher wrote: > +1 (Binding) > > > On Nov 13, 2017, at 10:15 PM, Willem Jiang > wrote: > > > > Hi All, > > > > I would like to start a VOTE to bring the ServiceComb project in as an > > Apache incubator podling. > > > > The ASF voting rules are described: > > > > https://www.apache.org/foundation/voting.html > > > > A vote for accepting a new Apache Incubator podling is a majority vote > for > > which only Incubator PMC member votes are binding. > > > > This vote will run for at least 72 hours. Please VOTE as follows > > [] +1 Accept ServiceComb into the Apache Incubator > > [] +0 Abstain. > > [] -1 Do not accept ServiceComb into the Apache Incubator because ... > > > > The proposal is listed below, but you can also access it on the wiki: > > > > https://wiki.apache.org/incubator/ServiceCombProposal > > > > Best regards, > > > > Willem Jiang > > > > = ServiceComb Proposal = > > > > == Abstract == > > > > ServiceComb is a microservice framework that provides a set of tools and > > components to make development and deployment of cloud applications > easier. > > It provides functionalities such as service contract enforcement, service > > registration, service discovery, load balance, service reliability > (latency > > and fault tolerance, flow control and graceful degradation, handler chain > > tracing), eventual data consistency and so forth. > > > > == Proposal == > > > > The goal of this proposal is to bring the existing ServiceComb codebase > and > > existing developers into the Apache Software Foundation (ASF) in order to > > build a vibrant, diverse and self-governed open source community around > the > > technology. > > So far the major contributors to the project have been affiliated with > > Huawei and Huawei is planning to continue market and sell the Cloud > Service > > Engine leveraging the ServiceComb framework. > > ServiceComb is currently a registered trademark owned by Huawei, and > Huawei > > is happy to donate this trademark to Apache. > > > > Huawei is submitting this proposal to donate the Service source code and > > associated artifacts (documentation, web site content, wiki, etc.) to the > > Apache Software Foundation Incubator under the Apache License, Version > 2.0 > > and is asking Incubator PMC to establish an open source community. These > > artifacts are currently available on GitHub at > > https://github.com/ServiceComb/ and include: > > * Java Chassis: a multi-protocol (RPC & Restful) microservice framework > > which adopts contract-first design > > * Service Center: a service registry that enforces service contract upon > > service registration and discovery > > * Saga: a distributed coordinator to achieve eventual data consistency > > based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem > > * ServiceComb.github.io: the website repo of ServiceComb. > > * The other projects will be moved to another place if ServiceComb is > > accepted by Apache as an incubator project. > > > > == Background == > > > > Microservices is a variant of the service-oriented architecture (SOA) > > architectural style that structures an application as a collection of > > loosely coupled services. ServiceComb is an open source microservice > > framework initiated as part of Huawei CSE projects (Cloud Service Engine) > > which was developed in 2015. It is a part of ServiceStage of Huawei > Public > > Cloud which is one-stop PaaS platform for enterprises and developers. > > Besides ServiceStage, it’s also used in the Huawei Core Network IOT > > Platform and Huawei consumer cloud. The number of companies using > > ServiceComb to develop their enterprise applications, they are > > chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and > the > > number is over 5 and counting. > > > > == Rationale == > > > > ServiceComb has been developed as a total, open source solution for > > developing cloud native applications. So far ServiceComb has existed as a > > GitHub project with committers mostly working for Huawei. We feel that > > moving it to a neutral organization like Apache, with its strong > governance > > model, is expected to help get more contributions from various > > organizations and developers, who may be concerned by exclusive control > of > > ServiceComb by Huawei. > > > > == Initial Goals == > > > > Our initial goals are to bring ServiceComb into the ASF, transition > > internal engineering processes into the open, and foster a collaborative > > development model according to the "Apache Way." Huawei and the current > > contributors to ServiceComb plan 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. > > > > 1. More specifically, our initial plan of moving ServiceComb to ASF is > > focused on: > > 2. open up the governance model in order to simplify and stream
