Re: [VOTE] Accept ResilientDB Into The Apache Incubator
+1 (non-binding) On Mon, Oct 16, 2023 at 6:48 AM zhongyi tan wrote: > +1 (binding） > > On Mon, Oct 16, 2023 at 6:49 PM Kevin Ratnasekera > > wrote: > > > +1 (binding) > > > > On Mon, Oct 16, 2023 at 12:20 PM Ayush Saxena > wrote: > > > > > +1(Binding) > > > > > > -Ayush > > > > > > > On 16-Oct-2023, at 3:47 PM, Roman Shaposhnik > > > wrote: > > > > > > > > On Mon, Oct 16, 2023 at 1:10 PM Atri Sharma > wrote: > > > >> > > > >> Following up the [DISCUSS] thread on ResilientDB, I would like to > > call > > > a > > > >> VOTE to accept into the Apache Incubator. > > > >> > > > >> Please cast your vote: > > > >> > > > >> [ ] +1, bring into the Incubator > > > >> [ ] +0, I don't care either way > > > >> [ ] -1, do not bring ResilientDB into the Incubator, because... > > > >> > > > >> The vote will open at least for 72 hours and only votes from the > > > >> Incubator PMC are binding, but votes from everyone are welcome. > > > >> > > > >> Please check out the ResilientDB Proposal from the incubator > wiki[1]. > > > >> > > > >> [1] > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > > > > > > +1 (binding) > > > > > > > > Thanks, > > > > Roman. > > > > > > > > P.S. I literally started to compose that same email just now ;-) > > > > > > > > - > > > > 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 > > > > > > > > > -- thanks ashish
Re: [VOTE] Accept Celeborn into the Apache Incubator
+1 (non-binding) On Tue, Oct 11, 2022 at 8:49 PM Yu Li wrote: > Hi all, > > Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like to > call a VOTE to accept Celeborn into the Apache Incubator, please check out > the Celeborn Proposal from the incubator wiki [3]. > > Please cast your vote: > > [ ] +1, bring Celeborn into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Celeborn into the Incubator, because... > > The vote will open at least for 72 hours, and only votes from the Incubator > PMC are binding, but votes from everyone are welcome. > > Best Regards, > Yu > > [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c > [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy > [3] https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal > -- thanks ashish
Re: [VOTE] Accept Zipkin into the Apache Incubator
com/openzipkin/docker-zipkin-azure > * git://github.com/openzipkin/zipkin-gcp > * git://github.com/openzipkin/docker-zipkin-gcp > * git://github.com/openzipkin/brave-cassandra > * git://github.com/openzipkin/docker-jre-full > * git://github.com/openzipkin/brave-karaf > > Depending on community progress, other repositories may be moved as well > > == Source and Intellectual Property Submission Plan == > Zipkin's initial source is licensed under the Apache License, Version 2.0. > https://github.com/openzipkin/zipkin/blob/master/LICENSE > > All source code is copyrighted to 'The OpenZipkin Authors', to which the > existing core community(members list in Initial Committers) has the rights to > re-assign to the ASF. > > == External Dependencies == > This is a listing of Maven coordinates for all of the external dependencies > Zipkin uses. All of the dependencies are in Sonatype and their licenses > should be accessible. > > == Cryptography == > Zipkin contains no cryptographic algorithms. > > = Required Resources = > == Mailing Lists == > * Zipkin-dev: for development discussions > * Zipkin-user: for community discussions > * Zipkin-private: for PPMC discussions > * Zipkin-commits: for code changes > > == Git Repositories == > The Zipkin team is experienced in git and requests to transfer GitHub > repositories(list in Initial Source) to Apache. > > == Issue Tracking == > The community would like to continue using GitHub Issues. > > = Initial Committers = > * Zoltán Nagy > * Adrian Cole, Pivotal > * Bas van Beek > * Brian Devins > * Eirik Sletteberg > * Jeanneret Pierre-Hugues > * Jordi Polo Carres > * José Carlos Chávez > * Kristof Adriaenssens > * Lance Linder > * Mick Semb Wever, > * Tommy Ludwig > > = Champion = > * Michael Semb Wever, m...@apache.org > > = Mentors = > * Michael Semb Wever, m...@apache.org > * Andriy Redko, r...@apache.org > * John D. Ament, johndam...@apache.org > * Willem Ning Jiang, ningji...@apache.org > > = Sponsoring Entity = > We are requesting the Apache Incubator to sponsor this project. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Druid into the Apache Incubator
perty Submission Plan == > > A complete set of the open source code needs to be licensed > from the owning organization to the Foundation. Commercial > legal counsel for the owning organization will review the > standard Foundation licensing paperwork and propose any > updates as needed. This license will enable Apache to > incubate and manage the Druid project moving forward. > > Other Druid paraphernalia to be transferred to Apache > consists of: > > * GitHub organization at https://github.com/druid-io/ > * Twitter account at https://twitter.com/druidio > * "druid.io" domain name > * "Druid" trademark assignment per Foundation standard > paper. The trademark assignment paperwork shall be > reviewed by the owning organization's commercial and IP > counsel > * CLAs - all rights in the code licensed above should > encompass the CLAs that existed between developers and > owning organization > > A copyright license to the code, trademark assignment of > Druid, and transfer of other paraphernalia to Apache should > be sufficient to cover all rights required by Apache to > operate the project. > > == External Dependencies == > > External dependencies distributed with Druid currently all > have one of the following Category A or B licenses: ASL, > BSD, CDDL, EPL, MIT, MPL; with one exception: the optional > Druid MySQL metadata store extension depends on MySQL > Connector/J, which is GPL licensed. Druid currently packages > this as a separate download; see our current presentation > on: http://druid.io/downloads.html. As part of incubation we > intend to determine the best strategy for handling the MySQL > extension. > > == Cryptography == > > Not applicable. > > == Initial Committers == > > The initial committers for incubation are the current set of > committers on Druid who have expressed interest in being > involved in Apache incubation. Affiliations are listed > where relevant. We may seek to add other committers during > incubation; for example, we would want to add any current > Druid committers who express an interest after incubation > begins. > > * Charles Allen (char...@allen-net.com) (Snap) > * David Lim (david.clarence@gmail.com) (Imply) > * Eric Tschetter (ched...@apache.org) (Splunk) > * Fangjin Yang (f...@imply.io) (Imply) > * Gian Merlino (g...@apache.org) (Imply) > * Himanshu Gupta (g.himan...@gmail.com) (Oath) > * Jihoon Son (jihoon...@apache.org) (Imply) > * Jonathan Wei (jon@imply.io) (Imply) > * Maxime Beauchemin (maximebeauche...@gmail.com) (Lyft) > * Mohamed Slim Bouguerra (slim.bougue...@gmail.com) (Hortonworks) > * Nishant Bangarwa (nish...@apache.org) (Hortonworks) > * Parag Jain (paragjai...@gmail.com) (Oath) > * Roman Leventov (leventov...@gmail.com) (Metamarkets) > * Xavier Léauté (xav...@leaute.com) (Confluent) > > == Sponsors == > > * Champion: Julian Hyde > * Nominated mentors: Julian Hyde, P. Taylor Goetz, Jun Rao > * Sponsoring entity: Apache Incubator > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept PageSpeed into the Apache Incubator
that time, the module has gained broad adoption, with > hundreds of thousands of installs including 1.2% of the top 10k sites. The > PageSpeed Optimization Libraries have been used in products such as the > Chrome Data Reduction proxy, PageSpeed Insights, Accelerated Mobile Pages > (AMP), and Google Web Light, as well as a plethora of CDN/Hosting/Plugin > channels to help any website deploy PageSpeed, including Verizon/Edgecast’s > CDN, we-amp’s IIS WebSpeed and ats_pagespeed, SiteGround, Section.IO, > OpenLitespeed, and cpanel. > > == Meritocracy == > We plan to invest in supporting a meritocracy. We will discuss the > requirements in an open forum. The project is used by a huge amount of > companies, and we intend to invite additional developers to participate. We > will encourage and monitor community participation so that privileges can > be extended to those that contribute. > > == Community == > The need for a platform capable of automatically optimizing web content in > the open source community has turned out tremendous. We are hoping that > embracing “the Apache way” will accelerate the growth of our community. We > have already been active at seeking and inviting contributions. > > == Core Developers == > The initial committers for pagespeed include experienced engineers: > > * Otto van der Schaaf - (We-Amp / IISWebSpeed) > * Kees Spoelstra - (We-Amp / IISWebSpeed) > * Ashish Kulkarni - (We-Amp / IISWebSpeed) > * Joshua Marantz - (Google) > * Maksim Orlovich - (Google) > > We realize that additional employer diversity is needed, and we will work > to recruit developers from additional companies. > > == Alignment == > The initial committers strongly believe that a system for optimizing web > content will gain broader adoption as an open source, community driven > project. > > == Known Risks == > > === Orphaned Products === > [[ > https://groups.google.com/forum/#!topic/mod-pagespeed-discuss/SYx1nOS6HsE|Google > has recently stepped down as the controlling entity of the project]]. > Individual committers from Google are still involved in the project along > with continued involvement from We-Amp. We plan to mitigate the risks of > this transition by recruiting additional committers. We expect the ASF to > be a good environment for growing our community. > > === Inexperience with Open Source === > The initial committers include Apache members (committers and PPMC members) > and developers who have varying degrees of experience with open source > projects. All have been involved with source code that has been released > under an open source license, and several also have experience developing > code with an open source development process. > > === Homogenous Developers === > The initial committers are employed by We-Amp B.V. and Google Inc. We are > committed to recruiting additional committers from other companies. > > === Reliance on Salaried Developers === > It is expected that PageSpeed development will occur on both salaried time > and on volunteer time, after hours (or 20% time). We-Amp’s committers are > paid by their company (IIS WebSpeed) to contribute to this project. > However, all involved are very passionate about the project, and we are > confident that the project will continue even if no salaried developers > contribute to the project. We are committed to recruiting additional > committers including non-salaried developers. > > === Relationships with Other Apache Products === > To the knowledge of the Initial Committers, there are no direct competitors > to pagespeed optimization within the Apache Software Foundation. The > project implements modules for both Apache httpd and Apache Traffic Server. > We look forward to collaborating with those communities, as well as other > Apache communities. > > === An Excessive Fascination with the Apache Brand === > Our rationale for developing pagespeed optimization as an Apache project is > detailed in the Rationale Section. We believe that the Apache brand and > community process will help us attract more contributors to this project, > and help grow the footprint of the project through usage at other > organizations and within other applications. Establishing consensus among > users and developers will result in a more valuable product for everyone. > > == Documentation == > References to further reading material: > > * [[https://www.modpagespeed.com/doc|Documentation]] > * [[https://www.modpagespeed.com|Examples (mod_pagespeed)]] > * [[https://www.ngxpagespeed.com/|Examples (ngx_pagespeed)]] > * [[ > https://github.com/apache/trafficserver/tree/master/plugins/experimental/ats_pagespeed/|ats_pagespeed > ]] > > == Initial Source == > The origin of th
Re: [VOTE] Heron to enter Apache Incubator
g > * u...@heron.incubator.apache.org > > == Subversion Directory == > > Git is the preferred source control system: git://git.apache.org/heron > > == Issue Tracking == > > JIRA: Heron (HERON) > > == Initial Committers == > > * Andrew Jorgensen (andrew at andrewjorgensen dot com) > * Ashvin Agrawal (ashvin at apache dot org)* > * Avrilia Floratou (avrilia dot floratou at gmail dot com) > * Bill Graham (billgraham at apache dot org)* > * Brian Hatfield (bmhatfield at gmail dot com) > * Chris Kellogg (cckellogg at gmail dot com) > * Huijun Wu (huijun dot wu dot 2010 at gmail dot com) > * Karthik Ramasamy (karthik at gmail dot com) > * Maosong Fu (maosongfu at gmail dot com) > * Neng Lu(freeneng at gmail dot com) > * Runhang Li (obj dot runhang at gmail dot com) > * Sanjeev Kulkarni (sanjeevrk at gmail dot com) > * Supun Kamburugamuve (supun at apache dot org)* > * Thomas Sun (tom dot ssf at gmail dot com) > * Yaliang Wang (yaliang dot w dot wang at ieee dot org) > > == Affiliations == > > * Andrew Jorgensen (Google) > * Ashvin Agrawal (Microsoft) > * Avrilia Floratou (Microsoft) > * Bill Graham (Twitter) > * Brian Hatfield (Google) > * Chris Kellogg (Twitter) > * Huijun Wu (Twitter) > * Karthik Ramasamy (Streamlio) > * Maosong Fu (Twitter) > * Neng Lu (Twitter) > * Runhang Li (Twitter) > * Sanjeev Kulkarni (Streamlio) > * Supun Kamburugamuve (Indiana University) > * Thomas Sun (Twitter) > * Yaliang Wang (Twitter) > > = Sponsors = > > == Champion == > > * Julien Le Dem (julien at apache dot org) > > == Nominated Mentors == > > * Jake Farrell (jfarrell at apache dot org) > * Jacques Nadeau (jacques at apache dot org) > * Julien Le Dem (julien at apache dot org) > * P. Taylor Goetz (ptgoetz at apache dot org) > > == Sponsoring Entity == > > The Apache Incubator > > == Footnotes == > > * 1 - Papers detailing Heron are available at > http://dl.acm.org/citation.cfm?id=2742788 and > http://sites.computer.org/debull/A15dec/p15.pdf. > * 2 - http://home.apache.org/phonebook.html?uid=billgraham > * 3 - http://home.apache.org/phonebook.html?uid=ashvin > * 4 - http://home.apache.org/phonebook.html?uid=supun -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESTART] [VOTE] Graduate Apache Beam
rs of the >> > >Apache Beam Project: >> > > >> > > * Tyler Akidau >> > > * Davor Bonaci >> > > * Robert Bradshaw >> > > * Ben Chambers >> > > * Luke Cwik >> > > * Stephan Ewen >> > > * Dan Halperin >> > > * Kenneth Knowles >> > > * Aljoscha Krettek >> > > * Maximilian Michels >> > > * Jean-Baptiste Onofré >> > > * Frances Perry >> > > * Amit Sela >> > > * Josh Wills >> > > >> > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci >> > >be appointed to the office of Vice President, Apache Beam, 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 Beam 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 Beam Project; and be it further >> > > >> > >RESOLVED, that the Apache Beam Project be and hereby >> > >is tasked with the migration and rationalization of the Apache >> > >Incubator Beam podling; and be it further >> > > >> > >RESOLVED, that all responsibilities pertaining to the Apache >> > >Incubator Beam podling encumbered upon the Apache Incubator >> > >Project are hereafter discharged. >> > > >> > >> > > > > -- > Guillaume Laforge > Apache Groovy committer & PMC Vice-President > Developer Advocate @ Google Cloud Platform > > Blog: http://glaforge.appspot.com/ > Social: @glaforge <http://twitter.com/glaforge> / Google+ > <https://plus.google.com/u/0/114130972232398734985/posts> -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Beam
+1 (non-binding) On Mon, Dec 5, 2016 at 10:28 AM, Davor Bonaci wrote: > Hi everyone, > Please vote to approve/disapprove the draft resolution proposed by the > Apache Beam PPMC below, which establishes Apache Beam as a new top-level > project at the Apache Software Foundation, as follows: > > [ ] Approve the proposed resolution > [ ] Disapprove the proposed resolution > > Before voting, please see the corresponding discussion thread [1], and vote > only after you feel ready to do so. The vote will be open for at least 72 > hours. This is a procedural vote [2]; it is adopted by a simple majority of > qualified votes (with no minimum). > > If approved by the Apache Incubator, the proposed resolution will be > submitted to the Board of Directors for their consideration. > > Thank you! > > Davor > > [1] > https://lists.apache.org/thread.html/b9c1071b35558846836814575ada3cdca61c72dc1e672ab994a9c936@%3Cgeneral.incubator.apache.org%3E > [2] http://apache.org/foundation/voting.html > > The full-text of the draft resolution proposed by the Apache Beam PPMC: > > X. Establish the Apache Beam 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 unified programming model for both >batch and streaming data processing, enabling efficient >execution across diverse distributed execution engines >and providing extensibility points for connecting to different >technologies and user communities. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management >Committee (PMC), to be known as the "Apache Beam Project", >be and hereby is established pursuant to Bylaws of the >Foundation; and be it further > >RESOLVED, that the Apache Beam Project be and hereby is >responsible for the creation and maintenance of software >related to a unified programming model for both batch and >streaming data processing, enabling efficient execution across >diverse distributed execution engines and providing extensibility >points for connecting to different technologies and user >communities; and be it further > >RESOLVED, that the office of "Vice President, Apache Beam" 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 Beam Project, and to have primary responsibility >for management of the projects within the scope of >responsibility of the Apache Beam 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 Beam Project: > > * Tyler Akidau > * Davor Bonaci > * Robert Bradshaw > * Ben Chambers > * Luke Cwik > * Stephan Ewen > * Dan Halperin > * Kenneth Knowles > * Aljoscha Krettek > * Maximilian Michels > * Jean-Baptiste Onofré > * Frances Perry > * Amit Sela > * Josh Wills > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci >be appointed to the office of Vice President, Apache Beam, 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 Beam 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 Beam Project; and be it further > >RESOLVED, that the Apache Beam Project be and hereby >is tasked with the migration and rationalization of the Apache >Incubator Beam podling; and be it further > >RESOLVED, that all responsibilities pertaining to the Apache >Incubator Beam podling encumbered upon the Apache Incubator >Project are hereafter discharged. -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept PredictionIO into the Apache Incubator
; We will migrate to Apache JIRA. > > JIRA PREDICTIONIO > https://issues.apache.org/jira/browse/PREDICTIONIO > > Other Resources > > TravisCI for builds and test running. > > PredictionIO's documentation, included in the code repo (docs/manual > directory), is built with Middleman and publicly hosted at > https://docs.prediction.io > > A blog to drive adoption and excitement at https://blog.prediction.io > > Initial Committers > > Pat Ferrell > Tamas Jambor > Justin Yip > Xusen Yin > Lee Moon Soo > Donald Szeto > Kenneth Chan > Tom Chan > Simon Chan > Marco Vivero > Matthew Tovbin > Yevgeny Khodorkovsky > Felipe Oliveira > Vitaly Gordon > Alex Merritt > > Affiliations > > Pat Ferrell - ActionML > Tamas Jambor - Channel4 > Justin Yip - independent > Xusen Yin - USC > Lee Moon Soo - NFLabs > Donald Szeto - Salesforce > Kenneth Chan - Salesforce > Tom Chan - Salesforce > Simon Chan - Salesforce > Marco Vivero - Salesforce > Matthew Tovbin - Salesforce > Yevgeny Khodorkovsky - Salesforce > Felipe Oliveira - Salesforce > Vitaly Gordon - Salesforce > Alex Merritt - ActionML > > Sponsors > > Champion > > Andrew Purtell > > Nominated Mentors > > Andrew Purtell > James Taylor > Lars Hofhansl > Suneel Marthi > Xiangrui Meng > Luciano Resende > > Sponsoring Entity > > Apache Incubator PMC > > > -- > Best regards, > >- Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Gossip into the Apache Incubator
nsport encryption. > = Required Resources = > == Mailing lists == > * d...@gossip.incubator.apache.org > * comm...@gossip.incubator.apache.org > * priv...@gossip.incubator.apache.org > The user list will be added when we have broader adoption. > == Git Repository == > https://git-wip-us.apache.org/repos/asf/incubator-gossip.git > == Issue Tracking == > JIRA tracker: GOSSIP > = Initial Committers = > * Edward Capriolo (ecapriolo at apache dot org) > * Josh Clemm (clemm22 at gmail dot com) > * P. Taylor Goetz (ptgoetz at apache dot org) > * Gary Dusbabek (gdusbabek at apache dot org) > * Dorian Ellerbe (Doellerbe06 at gmail dot com)(requires CLA) > * Sathish Dhinakaran (requires CLA) > * Joe Price (pricejosephd at gmail dot com)(requires CLA) > = Affiliations = > * Edward Capriolo - The Huffington Post > * P. Taylor Goetz - Hortonworks > * Gary Dusbabek - Silicon Valley Data Science > * Dorian Ellerbe - Dstillery > * Sathish Dhinakaran - Dstillery > * Sean Busbey - Cloudera > * Josh Elser - Hortonworks > > = Additional Interested Contributors = > > Those interested in getting involved with the project as it starts are > encourage to list themselves here. > > * Suneel Marthi (smarthi at apache dot org) - Red hat Inc. > * Debo Dutta (ddutta at apache dot org) - Cisco > > = Sponsors = > == Champion == > P. Taylor Goetz (ASF Member, IPMC) > > == Proposed Mentors == > * Sean Busbey (ASF Member, IPMC) > * Josh Elser (ASF Member, IPMC) > * P. Taylor Goetz (ASF Member, IPMC) > = Sponsoring Entity = > The Apache Incubator > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Sentry
+1 (non-binding) On Wed, Feb 24, 2016 at 11:20 AM, Sravya Tirukkovalur wrote: > Hi all, > > Following the positive discussion[1] and vote[2] in the Sentry > community and a discussion[3] on the incubator list to graduate > Sentry, I am calling a VOTE to graduate the project from the Incubator > to a TLP. Please vote on the resolution pasted below. > > [ ] +1 Graduate Sentry from the Incubator > [ ] +0 Don't care > [ ] -1 Don't graduate Sentry from the Incubator (please specify reason) > > This vote will be open for at least 72 hours. > > References: > > [1] https://s.apache.org/dev_discuss > [2] https://s.apache.org/dev_vote_result > [3] https://s.apache.org/general_discuss > Other: > https://s.apache.org/general_notify > https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment > > Resolution to create a TLP from graduating Incubator podling: > > == > > > X. Establish the Apache Sentry 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 Fine grained authorization to data and > metadata in Hadoop. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Sentry Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache Sentry Project be and hereby is > responsible for the creation and maintenance of software > related to Fine grained authorization to data and metadata in Hadoop; > and be it further > > RESOLVED, that the office of "Vice President, Apache Sentry" 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 Sentry Project, and to have primary responsibility > for management of the projects within the scope of > responsibility of the Apache Sentry 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 Sentry Project: > > * Ali Rizvi > >* Anne Yu > >* Arun Suresh > >* Brock Noland > >* Chaoyu Tang > >* Colin Ma > >* Daisy Zhou > >* Dapeng Sun > >* David Nalley > >* Erick Tryzelaar > >* Gregory Chanan > >* Guoquan Shen > >* Hadi Nahari > >* Hao Hao > >* Jarek Jarcec Cecho > >* Johnny Zhang > >* Karthik Ramachandran > >* Mark Grover > >* Milo Polte > >* Lenni Kuff > >* Patrick Daly > >* Patrick Hunt > >* Prasad Mujumdar > >* Raghu Mani > >* Sean Mackrory > >* Shreepadma Venugopalan > >* Sravya Tirukkovalur > >* Tuong Truong > >* Vamsee Yarlagadda > >* Xiaomeng Huang > >* Xuefu Zhang > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur > be appointed to the office of Vice President, Apache Sentry, 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 Sentry 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 Sentry Project; and be it further > > RESOLVED, that the Apache Sentry Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator Sentry podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Sentry podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > == > > > Regards, > Sravya Tirukkovalur > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Joshua as an Apache Incubator Podling
re made by a single contributor, the >>lead maintainer. He (Matt Post) plans to continue development for the next >>few years, but it is still a single point of failure, since the graduate >>students who worked on the project have moved on to jobs, mostly in >>industry. However, our goal is to help that process by growing the >>community in Apache, and at least in growing the community with users and >>participants from NASA JPL. >> >>=== Inexperience with Open Source === >>The team both at Johns Hopkins and NASA JPL have experience with many OSS >>software projects at Apache and elsewhere. We understand "how it works" >>here at the foundation. >> >> >>== Relationships with Other Apache Products == >>Joshua includes dependences on Hadoop, and also is included as a plugin in >>Apache Tika. We are also interested in coordinating with other projects >>including Spark, and other projects needing MT services for language >>translation. >> >>== Developers == >>Joshua only has one regular developer who is employed by Johns Hopkins >>University. NASA JPL (Mattmann and McGibbney) have been contributing >>lately including a Brew formula and other contributions to the project >>through the DARPA XDATA and Memex programs. >> >>== Documentation == >>Documentation and publications related to Joshua can be found at >>joshua-decoder.org. The source for the Joshua documentation is currently >>hosted on Github at >>https://github.com/joshua-decoder/joshua-decoder.github.com >> >>== Initial Source == >>Current source resides at Github: github.com/joshua-decoder/joshua (the >>main decoder and toolkit) and github.com/joshua-decoder/thrax (the grammar >>extraction tool). >> >>== External Dependencies == >>Joshua has a number of external dependencies. Only BerkeleyLM (Apache 2.0) >>and KenLM (LGPG 2.1) are run-time decoder dependencies (one of which is >>needed for translating sentences with pre-built models). The rest are >>dependencies for the build system and pipeline, used for constructing and >>training new models from parallel text. >> >>Apache projects: >> * Ant >> * Hadoop >> * Commons >> * Maven >> * Ivy >> >>There are also a number of other open-source projects with various >>licenses that the project depends on both dynamically (runtime), and >>statically. >> >>=== GNU GPL 2 === >> * Berkeley Aligner: https://code.google.com/p/berkeleyaligner/ >> >>=== LGPG 2.1 === >> * KenLM: github.com/kpu/kenlm >> >>=== Apache 2.0 === >> * BerkeleyLM: https://code.google.com/p/berkeleylm/ >> >>=== GNU GPL === >> * GIZA++: http://www.statmt.org/moses/giza/GIZA++.html >> >>== Required Resources == >> * Mailing Lists >> * priv...@joshua.incubator.apache.org >> * d...@joshua.incubator.apache.org >> * comm...@joshua.incubator.apache.org >> >> * Git Repos >> * https://git-wip-us.apache.org/repos/asf/joshua.git >> >> * Issue Tracking >> * JIRA Joshua (JOSHUA) >> >> * Continuous Integration >> * Jenkins builds on https://builds.apache.org/ >> >> * Web >> * http://joshua.incubator.apache.org/ >> * wiki at http://cwiki.apache.org >> >>== Initial Committers == >>The following is a list of the planned initial Apache committers (the >>active subset of the committers for the current repository on Github). >> >> * Matt Post (p...@cs.jhu.edu) >> * Lewis John McGibbney (lewi...@apache.org) >> * Chris Mattmann (mattm...@apache.org) >> >>== Affiliations == >> >> * Johns Hopkins University >> * Matt Post >> >> * NASA JPL >> * Chris Mattmann >> * Lewis John McGibbney >> >> >>== Sponsors == >>=== Champion === >> * Chris Mattmann (NASA/JPL) >> >>=== Nominated Mentors === >> * Paul Ramirez >> * Lewis John McGibbney >> * Chris Mattmann >> >>== Sponsoring Entity == >>The Apache Incubator >> >> >> >> >>++ >>Chris Mattmann, Ph.D. >>Chief Architect >>Instrument Software and Science Data Systems Section (398) >>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>Office: 168-519, Mailstop: 168-527 >>Email: chris.a.mattm...@nasa.gov >>WWW: http://sunset.usc.edu/~mattmann/ >>++ >>Adjunct Associate Professor, Computer Science Department >>University of Southern California, Los Angeles, CA 90089 USA >>++ >> >> >> > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Beam into the Apache Incubator
.com] > * Frances Perry [f...@google.com] > * James Malone[jamesmal...@google.com] > * Jean-Baptiste Onofré[jbono...@apache.org] > * Josh Wills [jwi...@apache.org] > * Kostas Tzoumas [kos...@data-artisans.com] > * Kenneth Knowles [k...@google.com] > * Luke Cwik [lc...@google.com] > * Maximilian Michels [m...@apache.org] > * Stephan Ewen[step...@data-artisans.com] > * Tom White [t...@cloudera.com] > * Tyler Akidau[taki...@google.com] > * Robert Bradshaw [rober...@google.com] > > == Additional Interested Contributors == > > * Debo Dutta [dedu...@cisco.com] > * Henry Saputra [hsapu...@apache.org] > * Taylor Goetz[ptgo...@gmail.com] > * James Carman[ja...@carmanconsulting.com] > * Joe Witt[joew...@apache.org] > * Vaibhav Gumashta[vgumas...@hortonworks.com] > * Prasanth Jayachandran [pjayachand...@hortonworks.com] > * Johan Edstrom [seij...@gmail.com] > * Hugo Louro [hmclo...@gmail.com] > * Krzysztof Sobkowiak [krzys.sobkow...@gmail.com] > * Jeff Genender [jgenen...@apache.org] > * Edward J. Yoon [edward.y...@samsung.com] > * Hao Chen[h...@apache.org] > * Byung-Gon Chun [bgc...@gmail.com] > * Charitha Elvitigala [charit...@apache.org] > * Alexander Bezzubov [b...@apache.org] > * Tsuyoshi Ozawa [oz...@apache.org] > * Mayank Bansal [maban...@gmail.com] > * Supun Kamburugamuve [su...@apache.org] > * Matthias Wessendorf [mat...@apache.org] > * Felix Cheung[felixche...@apache.org] > * Ajay Yadava [ajay.ya...@inmobi.com] > * Liang Chen [chenliang...@huawei.com] > * Renaud Richardet[renaud (at) apache (dot) org] > * Bakey Pan [bakey1...@gmail.com] > * Andreas Neumann [a...@apache.org] > * Suresh Marru[sma...@apache.org] > * Hadrian Zbarcea [hzbar...@gmail.com] > > == Affiliations == > > The initial committers are from six organizations. Google developed Dataflow > and the Dataflow SDK, data Artisans developed the Flink runner, and Cloudera > (Labs) developed the Spark runner. > > * Cloudera > * Tom White > * Data Artisans > * Aljoscha Krettek > * Kostas Tzoumas > * Maximilian Michels > * Stephan Ewen > * Google > * Ben Chambers > * Dan Halperin > * Davor Bonaci > * Frances Perry > * James Malone > * Kenneth Knowles > * Luke Cwik > * Tyler Akidau > * Robert Bradshaw > * PayPal > * Amit Sela > * Slack > * Josh Wills > * Talend > * Jean-Baptiste Onofré > > == Sponsors == > > === Champion === > > * Jean-Baptiste Onofre [jbono...@apache.org] > > === Nominated Mentors === > > * Jean-Baptiste Onofre [jbono...@apache.org] > * Jim Jagielski [j...@apache.org] > * Venkatesh Seetharam[venkat...@apache.org] > * Bertrand Delacretaz[bdelacre...@apache.org] > * Ted Dunning[tdunn...@apache.org] > > === Sponsoring Entity === > > The Apache Incubator > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Dataflow Incubator Proposal
Thanks Frances ! That explains it. Wrote a couple of posts on basic usage of Crunch, may be its time to rewrite them with Dataflow. On Fri, Jan 22, 2016 at 10:58 AM, Frances Perry wrote: > Crunch started as a clone of FlumeJava, which was Google internal. In the > meantime inside Google, FlumeJava evolved into Dataflow. So all three share > a number of concepts like PCollections, ParDo, DoFn, etc. However, Dataflow > adds a number of new things -- the biggest being a unified batch/streaming > semantics using concepts like Windowing and Triggers. Tyler Akidau's > OReilly post has a really nice explanation: > https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-102 > > On Fri, Jan 22, 2016 at 10:42 AM, Ashish wrote: > >> Crunch has Spark pipelines, but not sure about the runner abstraction. >> >> May be Josh Wills or Tom White can provide more insight on this topic. >> They are core devs for both projects :) >> >> On Fri, Jan 22, 2016 at 9:47 AM, Jean-Baptiste Onofré >> wrote: >> > Hi, >> > >> > I don't know deeply Crunch, but AFAIK, Crunch creates MapReduce >> pipeline, it >> > doesn't provide runner abstraction. It's based on FlumeJava. >> > >> > The logic is very similar (with DoFns, pipelines, ...). Correct me if I'm >> > wrong, but Crunch started after Google Dataflow, especially because >> Dataflow >> > was not opensourced at that time. >> > >> > So, I agree it's very similar/close. >> > >> > Regards >> > JB >> > >> > >> > On 01/22/2016 05:51 PM, Ashish wrote: >> >> >> >> Hi JB, >> >> >> >> Curious to know about how it compares to Apache Crunch? Constructs >> >> looks very familiar (had used Crunch long ago) >> >> >> >> Thoughts? >> >> >> >> - Ashish >> >> >> >> On Fri, Jan 22, 2016 at 6:33 AM, Jean-Baptiste Onofré >> >> wrote: >> >>> >> >>> Hi Seshu, >> >>> >> >>> I blogged about Apache Dataflow proposal: >> >>> http://blog.nanthrax.net/2016/01/introducing-apache-dataflow/ >> >>> >> >>> You can see in the "what's next ?" section that new runners, skins and >> >>> sources are on our roadmap. Definitely, a storm runner could be part of >> >>> this. >> >>> >> >>> Regards >> >>> JB >> >>> >> >>> >> >>> On 01/22/2016 03:31 PM, Adunuthula, Seshu wrote: >> >>>> >> >>>> >> >>>> Awesome to see CloudDataFlow coming to Apache. The Stream Processing >> >>>> area >> >>>> has been in general fragmented with a variety of solutions, hoping the >> >>>> community galvanizes around Apache Data Flow. >> >>>> >> >>>> We are still in the "Apache Storm" world, Any chance for folks >> building >> >>>> a >> >>>> "Storm Runner²? >> >>>> >> >>>> >> >>>> On 1/20/16, 9:39 AM, "James Malone" >> >>>> wrote: >> >>>> >> >>>>>> Great proposal. I like that your proposal includes a well presented >> >>>>>> roadmap, but I don't see any goals that directly address building a >> >>>>>> larger >> >>>>>> community. Y'all have any ideas around outreach that will help with >> >>>>>> adoption? >> >>>>>> >> >>>>> >> >>>>> Thank you and fair point. We have a few additional ideas which we can >> >>>>> put >> >>>>> into the Community section. >> >>>>> >> >>>>> >> >>>>>> >> >>>>>> As a start, I recommend y'all add a section to the proposal on the >> >>>>>> wiki >> >>>>>> page for "Additional Interested Contributors" so that folks who want >> >>>>>> to >> >>>>>> sign up to participate in the project can do so without requesting >> >>>>>> additions to the initial committer list. >> >>>>>> >> >>>>>> >> >>>>> This is a great idea and I think it makes a lot of sense to add an >> &
Re: [DISCUSS] Apache Dataflow Incubator Proposal
Crunch has Spark pipelines, but not sure about the runner abstraction. May be Josh Wills or Tom White can provide more insight on this topic. They are core devs for both projects :) On Fri, Jan 22, 2016 at 9:47 AM, Jean-Baptiste Onofré wrote: > Hi, > > I don't know deeply Crunch, but AFAIK, Crunch creates MapReduce pipeline, it > doesn't provide runner abstraction. It's based on FlumeJava. > > The logic is very similar (with DoFns, pipelines, ...). Correct me if I'm > wrong, but Crunch started after Google Dataflow, especially because Dataflow > was not opensourced at that time. > > So, I agree it's very similar/close. > > Regards > JB > > > On 01/22/2016 05:51 PM, Ashish wrote: >> >> Hi JB, >> >> Curious to know about how it compares to Apache Crunch? Constructs >> looks very familiar (had used Crunch long ago) >> >> Thoughts? >> >> - Ashish >> >> On Fri, Jan 22, 2016 at 6:33 AM, Jean-Baptiste Onofré >> wrote: >>> >>> Hi Seshu, >>> >>> I blogged about Apache Dataflow proposal: >>> http://blog.nanthrax.net/2016/01/introducing-apache-dataflow/ >>> >>> You can see in the "what's next ?" section that new runners, skins and >>> sources are on our roadmap. Definitely, a storm runner could be part of >>> this. >>> >>> Regards >>> JB >>> >>> >>> On 01/22/2016 03:31 PM, Adunuthula, Seshu wrote: >>>> >>>> >>>> Awesome to see CloudDataFlow coming to Apache. The Stream Processing >>>> area >>>> has been in general fragmented with a variety of solutions, hoping the >>>> community galvanizes around Apache Data Flow. >>>> >>>> We are still in the "Apache Storm" world, Any chance for folks building >>>> a >>>> "Storm Runner²? >>>> >>>> >>>> On 1/20/16, 9:39 AM, "James Malone" >>>> wrote: >>>> >>>>>> Great proposal. I like that your proposal includes a well presented >>>>>> roadmap, but I don't see any goals that directly address building a >>>>>> larger >>>>>> community. Y'all have any ideas around outreach that will help with >>>>>> adoption? >>>>>> >>>>> >>>>> Thank you and fair point. We have a few additional ideas which we can >>>>> put >>>>> into the Community section. >>>>> >>>>> >>>>>> >>>>>> As a start, I recommend y'all add a section to the proposal on the >>>>>> wiki >>>>>> page for "Additional Interested Contributors" so that folks who want >>>>>> to >>>>>> sign up to participate in the project can do so without requesting >>>>>> additions to the initial committer list. >>>>>> >>>>>> >>>>> This is a great idea and I think it makes a lot of sense to add an >>>>> "Additional >>>>> Interested Contributors" section to the proposal. >>>>> >>>>> >>>>>> On Wed, Jan 20, 2016 at 10:32 AM, James Malone < >>>>>> jamesmal...@google.com.invalid> wrote: >>>>>> >>>>>>> Hello everyone, >>>>>>> >>>>>>> Attached to this message is a proposed new project - Apache Dataflow, >>>>>> >>>>>> >>>>>> a >>>>>>> >>>>>>> >>>>>>> unified programming model for data processing and integration. >>>>>>> >>>>>>> The text of the proposal is included below. Additionally, the >>>>>> >>>>>> >>>>>> proposal is >>>>>>> >>>>>>> >>>>>>> in draft form on the wiki where we will make any required changes: >>>>>>> >>>>>>> https://wiki.apache.org/incubator/DataflowProposal >>>>>>> >>>>>>> We look forward to your feedback and input. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> James >>>>>>> >>>>>>> >>>>>>> >>>>>>> = Apache Dataflow = >>>>>&g
Re: [DISCUSS] Apache Dataflow Incubator Proposal
Hi JB, Curious to know about how it compares to Apache Crunch? Constructs looks very familiar (had used Crunch long ago) Thoughts? - Ashish On Fri, Jan 22, 2016 at 6:33 AM, Jean-Baptiste Onofré wrote: > Hi Seshu, > > I blogged about Apache Dataflow proposal: > http://blog.nanthrax.net/2016/01/introducing-apache-dataflow/ > > You can see in the "what's next ?" section that new runners, skins and > sources are on our roadmap. Definitely, a storm runner could be part of > this. > > Regards > JB > > > On 01/22/2016 03:31 PM, Adunuthula, Seshu wrote: >> >> Awesome to see CloudDataFlow coming to Apache. The Stream Processing area >> has been in general fragmented with a variety of solutions, hoping the >> community galvanizes around Apache Data Flow. >> >> We are still in the "Apache Storm" world, Any chance for folks building a >> "Storm Runner²? >> >> >> On 1/20/16, 9:39 AM, "James Malone" >> wrote: >> >>>> Great proposal. I like that your proposal includes a well presented >>>> roadmap, but I don't see any goals that directly address building a >>>> larger >>>> community. Y'all have any ideas around outreach that will help with >>>> adoption? >>>> >>> >>> Thank you and fair point. We have a few additional ideas which we can put >>> into the Community section. >>> >>> >>>> >>>> As a start, I recommend y'all add a section to the proposal on the wiki >>>> page for "Additional Interested Contributors" so that folks who want to >>>> sign up to participate in the project can do so without requesting >>>> additions to the initial committer list. >>>> >>>> >>> This is a great idea and I think it makes a lot of sense to add an >>> "Additional >>> Interested Contributors" section to the proposal. >>> >>> >>>> On Wed, Jan 20, 2016 at 10:32 AM, James Malone < >>>> jamesmal...@google.com.invalid> wrote: >>>> >>>>> Hello everyone, >>>>> >>>>> Attached to this message is a proposed new project - Apache Dataflow, >>>> >>>> a >>>>> >>>>> unified programming model for data processing and integration. >>>>> >>>>> The text of the proposal is included below. Additionally, the >>>> >>>> proposal is >>>>> >>>>> in draft form on the wiki where we will make any required changes: >>>>> >>>>> https://wiki.apache.org/incubator/DataflowProposal >>>>> >>>>> We look forward to your feedback and input. >>>>> >>>>> Best, >>>>> >>>>> James >>>>> >>>>> >>>>> >>>>> = Apache Dataflow = >>>>> >>>>> == Abstract == >>>>> >>>>> Dataflow is an open source, unified model and set of language-specific >>>> >>>> SDKs >>>>> >>>>> for defining and executing data processing workflows, and also data >>>>> ingestion and integration flows, supporting Enterprise Integration >>>> >>>> Patterns >>>>> >>>>> (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines >>>> >>>> simplify >>>>> >>>>> the mechanics of large-scale batch and streaming data processing and >>>> >>>> can >>>>> >>>>> run on a number of runtimes like Apache Flink, Apache Spark, and >>>> >>>> Google >>>>> >>>>> Cloud Dataflow (a cloud service). Dataflow also brings DSL in >>>> >>>> different >>>>> >>>>> languages, allowing users to easily implement their data integration >>>>> processes. >>>>> >>>>> == Proposal == >>>>> >>>>> Dataflow is a simple, flexible, and powerful system for distributed >>>> >>>> data >>>>> >>>>> processing at any scale. Dataflow provides a unified programming >>>> >>>> model, a >>>>> >>>>> software development kit to define and construct data processing >>>> >>>> pipelines, >>>>> >>>>> and runners to execut
Re: [VOTE] Accept Impala into the Apache Incubator
//github.com/cloudera/Impala/wiki) > > Impala’s auto-generated API documentation ( > http://impala.io/doc/html/index.html) > > = Initial Source = > Impala’s initial source contribution will come from > http://github.com/cloudera/Impala/. > > = External Dependencies = > > Impala depends upon a number of third-party libraries, which we list below. > We intend to compile a LICENSE.txt file in the very short term (see > https://issues.cloudera.org/browse/IMPALA-2670). > > * Google gflags (BSD) > * Google glog (BSD) > * Apache Thrift (Apache Software License v2.0) > * Apache Commons (Apache Software License v2.0) > * Apache Hadoop (Apache Software License v2.0) > * Apache HBase (Apache Software License v2.0) > * Apache Hive (Apache Software License v2.0) > * Boost (Boost Software License) > * OpenLdap (OpenLDAP Software License) > * rapidjson (MIT) > * Google RE2 (BSD-style) > * lz4 (BSD) > * snappy (BSD) > * cyrus-sasl (CMU License) > * Apache Avro (Apache Software License v2.0) > * Cloudera squeasel (Apache Software License v2.0) > * Apache htrace (Incubating) (Apache Software License v2.0) > * Apache Sentry (Incubating) (Apache Software License v2.0) > * Apache Shiro (Apache Software License v2.0) > * Twitter Bootstrap (Apache Software License v2.0) > * d3 (BSD) > * LLVM (BSD-like) > > Build and test dependencies: > > * ant (Apache Software License v2.0) > * Apache Maven (Apache Software License v2.0) > * cmake (BSD) > * clang (BSD) > * Google gtest (Apache Software License v2.0) > > = Required Resources = > > We request that following resources be created for the project to use: > > == Mailing lists == > > * priv...@impala.incubator.apache.org (moderated subscriptions) > * comm...@impala.incubator.apache.org > * d...@impala.incubator.apache.org > * iss...@impala.incubator.apache.org > * u...@impala.incubator.apache.org > > == Git repository == > https://git.apache.org/impala.git > > == JIRA instance == > JIRA project IMPALA (IMPALA or IMP) > > == Other Resources == > We hope to continue using Gerrit for our code review and commit workflow. > We are involved with discussions that the Kudu team at Cloudera have been > having with Jake Farrell to start discussions on how Gerrit can fit into > the ASF. We know that several other ASF projects or podlings are also > interested in Gerrit. > > If the Infrastructure team does not have the bandwidth to support gerrit, > we will continue to support our own instance of gerrit for Impala, and make > the necessary integrations such that commits are properly authenticated and > maintain sufficient provenance to uphold the ASF standards (e.g. via the > solution adopted by the AsterixDB podling). > > = Initial Committers = > > * Tim Armstrong > * Alex Behm > * Taras Bobrovytsky > * Casey Ching > * Martin Grund > * Daniel Hecht > * Michael Ho > * Matthew Jacobs > * Ishaan Joshi > * Lenni Kuff > * Marcel Kornacker > * Sailesh Mukil > * Henry Robinson > * John Russell > * Dimitris Tsirogiannis > * Skye Wanderman-Milne > * Juan Yu > > == Affiliations == > All: Cloudera Inc. > > = Sponsors = > > == Champion == > Tom White > > == Nominated Mentors == > * Tom White (Cloudera) > * Todd Lipcon (Cloudera) > * Carl Steinbach (LinkedIn) > * Brock Noland (StreamSets) > > > = Sponsoring Entity = > We ask that the Incubator PMC sponsor this proposal. -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Kudu into the Apache Incubator
icense >> * '''curl''': MIT >> * '''libunwind''': MIT >> * '''nvml''': BSD 3-clause >> * '''cyrus-sasl''': Cyrus SASL license (BSD-alike) >> * '''openssl''': OpenSSL License (BSD-alike) >> >> * '''Guava''': Apache 2.0 >> * '''StumbleUpon Async''': BSD >> * '''Apache Hadoop''': Apache 2.0 >> * '''Apache log4j''': Apache 2.0 >> * '''Netty''': Apache 2.0 >> * '''slf4j''': MIT >> * '''Apache Commons''': Apache 2.0 >> * '''murmur''': Apache 2.0 >> >> >> '''Build/test-only dependencies''': >> >> * '''CMake''': BSD 3-clause >> * '''gcovr''': BSD 3-clause >> * '''gmock''': BSD 3-clause >> * '''Apache Maven''': Apache 2.0 >> * '''JUnit''': EPL >> * '''Mockito''': MIT >> >> == Cryptography == >> >> Kudu does not currently include any cryptography-related code. >> >> == Required Resources == >> >> === Mailing lists === >> >> * priv...@kudu.incubator.apache.org (PMC) >> * comm...@kudu.incubator.apache.org (git push emails) >> * iss...@kudu.incubator.apache.org (JIRA issue feed) >> * d...@kudu.incubator.apache.org (Gerrit code reviews plus dev discussion) >> * u...@kudu.incubator.apache.org (User questions) >> >> >> === Repository === >> >> * git://git.apache.org/kudu >> >> === Gerrit === >> >> We hope to continue using Gerrit for our code review and commit workflow. >> The Kudu team has already been in contact with Jake Farrell to start >> discussions on how Gerrit can fit into the ASF. We know that several other >> ASF projects and podlings are also interested in Gerrit. >> >> >> >> If the Infrastructure team does not have the bandwidth to support Gerrit, >> we will continue to support our own instance of Gerrit for Kudu, and make >> the necessary integrations such that commits are properly authenticated and >> maintain sufficient provenance to uphold the ASF standards (e.g. via the >> solution adopted by the AsterixDB podling). >> >> == Issue Tracking == >> >> We would like to import our current JIRA project into the ASF JIRA, such >> that our historical commit messages and code comments continue to reference >> the appropriate bug numbers. >> >> == Initial Committers == >> >> * Adar Dembo a...@cloudera.com >> * Alex Feinberg a...@strlen.net >> * Andrew Wang w...@apache.org >> * Dan Burkert d...@cloudera.com >> * David Alves dral...@apache.org >> * Jean-Daniel Cryans jdcry...@apache.org >> * Mike Percy mpe...@apache.org >> * Misty Stanley-Jones mi...@apache.org >> * Todd Lipcon t...@apache.org >> >> The initial list of committers was seeded by listing those contributors who >> have contributed 20 or more patches in the last 12 months, indicating that >> they are active and have achieved merit through participation on the >> project. We chose not to include other contributors who either have not yet >> contributed a significant number of patches, or whose contributions are far >> in the past and we don’t expect to be active within the ASF. >> >> == Affiliations == >> >> * Adar Dembo - Cloudera >> * Alex Feinberg - Forward Networks >> * Andrew Wang - Cloudera >> * Dan Burkert - Cloudera >> * David Alves - Cloudera >> * Jean-Daniel Cryans - Cloudera >> * Mike Percy - Cloudera >> * Misty Stanley-Jones - Cloudera >> * Todd Lipcon - Cloudera >> >> == Sponsors == >> >> === Champion === >> >> * Todd Lipcon >> >> === Nominated Mentors === >> >> * Jake Farrell - ASF Member and Infra team member, Acquia >> * Brock Noland - ASF Member, StreamSets >> * Michael Stack - ASF Member, Cloudera >> * Jarek Jarcec Cecho - ASF Member, Cloudera >> * Chris Mattmann - ASF Member, NASA JPL and USC >> * Julien Le Dem - Incubator PMC, Dremio >> * Carl Steinbach - ASF Member, LinkedIn >> >> === Sponsoring Entity === >> >> The Apache Incubator > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Groovy into the Apache Incubator
ty is a guarantee against > the project being orphaned. > > === Inexperience with Open Source === > The majority of the proposers here have day jobs that has them working near > full-time on open source projects. A few of us have helped carry > other projects through the Incubator. Groovy to date has been developed as > an open source project. > > === Homogeneous Developers === > Now that Pivotal is ending its sponsorship, the initial group of committers > is going to be extremely heterogeneous when it comes to corporate > affiliations. > The Groovy community is also extremely diverse in terms of geography and > backgrounds of developers. > > === Reliance on Salaried Developers === > Most of the contributors are paid to work in the Java ecosystem. > While we might wander from our current employers, we probably won’t > go far from the Java family tree. > > === Relationships with Other Apache Products === > Groovy currently has a few ASF projects as optional dependencies but > otherwise doesn't depend on any ASF projects. A few > ASF projects already depend on Groovy. > > === An Excessive Fascination with the Apache Brand === > While we intend to leverage the Apache ‘branding’ when talking to other > projects as testament of our project’s ‘neutrality’, we have no plans > for making use of Apache brand in press releases nor posting billboards > advertising acceptance of Groovy into Apache Incubator. > > > == Documentation == > See [[http://www.groovy-lang.org/documentation.html|documentation]] > for the current state of the Groovy > documentation. > > A mature project website is also available at > [[http://www.groovy-lang.org/|groovy-lang.org]]. > > == Initial Source == > Initial source is available on GitHub under the ALv2 > [[https://github.com/groovy/groovy-core|groovy-core]] > > > == Source and Intellectual Property Submission Plan == > We know of no legal encumberments in the way of transfer of source to > Apache. In fact, given the > series of corporate due diligence procedures performed on the source > code during two of the > acquisitions we expect the code base to be squeaky clean from an IP > perspective. > > == External Dependencies == > Embedded dependencies (relocated): > >* Antlr 2, ANTLR 2 License (development branch includes Antlr4 > using BSD license) >* ASM, BSD >* Openbeans (ALv2) >* Apache Commons CLI (ALv2) > > Module or optional dependencies: > >* Apache Ant (ALv2) >* Apache Commons BSF (ALv2) >* Apache Commons Logging (ALv2) >* Apache Ivy (ALv2) >* Apache Log4j (ALv2) >* Apache Log4j 2 (ALv2) >* JAnsi (ALv2) >* JCommander (ALv2) >* JLine 2 (BSD) >* JUnit (EPL 1.0) >* Logback (EPL 1.0) >* QDox (ALv2) >* SLF4J (MIT) >* TestNG (ALv2) > > Build only dependencies: > >* bnd (ALv2) >* jarjar (ALv2) >* Checkstyle (LGPL) >* Cobertura (GPL) >* Gradle (ALv2) >* Asciidoctor (MIT) >* Simian (http://www.harukizaemon.com/simian/get_it_now.html) > > Test only dependencies: > >* Apache Commons HTTP Client (ALv2) >* Apache Lucene (ALv2) >* Eclipse OSGi (EPL 1.0) >* GPars (ALv2) >* HSQLDB (BSD) >* JMock (jMock Project License) >* OpenEJB (ALv2) >* Spock (ALv2) >* XMLUnit 1 (BSD) >* XStream (BSD) > > Cryptography > N/A > > == Required Resources == > > === Mailing lists === > * priv...@groovy.incubator.apache.org (moderated subscriptions) > * comm...@groovy.incubator.apache.org > * d...@groovy.incubator.apache.org > * iss...@groovy.incubator.apache.org > * u...@groovy.incubator.apache.org > > === Git Repository === > https://git-wip-us.apache.org/repos/asf/incubator-groovy.git > > === Issue Tracking === > JIRA Groovy (GROOVY) > > === Other Resources === > > A build server is currently sponsored by Jetbrains (TeamCity): > http://ci.groovy-lang.org?guest=1 > The CI server has a number of build plans including multiple JDKs (5 > to 9), 3rd party joint builds and integration with the Groovy website > (automatic deployment upon push). > > Means of setting up regular builds for Groovy on builds.apache.org > > == Initial Committers == > * Cédric Champeau > * Guillaume Laforge > * Jochen Theodorou > * Paul King > * Pascal Schumacher > > == Affiliations == > * Pivotal: Cédric Champeau, Jochen Theodorou > * Restlet: Guillaume Laforge > * ASERT: Paul King > * Pascal Schumacher > > == Sponsors == > > === Champion === > Roman Shaposhnik > > === Nominated Mentors === > * Bertrand Delacretaz - Apache Member > * Emmanuel Lecharny - Apache Member > * Jim Jagielski - Apache Member > * Roman Shaposhnik - Apache Member > * Andrew Bayer - Apache Member > * Konstantin Boudnik - IPMC Member > > Six mentors is plenty, we are not looking for more mentors at this time. > > === Sponsoring Entity === > We would like to propose Apache incubator to sponsor this project. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)
+1 (non-binding) On Mon, Oct 6, 2014 at 5:21 PM, Sharad Agarwal wrote: > Following the discussion earlier in the thread > https://www.mail-archive.com/general@incubator.apache.org/msg45208.html > I would like to call a Vote for accepting Lens as a new incubator project. > > The proposal is available at: > https://wiki.apache.org/incubator/LensProposal > > Vote is open till Oct 09, 2014 4 PM PST. > > [ ] +1 accept Lens in the Incubator > [ ] +/-0 > [ ] -1 because... > > Only Votes from Incubator PMC members are binding, but all are welcome to > express their thoughts. > I am +1 (non-binding). > > Thanks > Sharad > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Phoenix for incubator project
r-operates with Apache HBase by allowing > existing data, not created by Phoenix, to be queried. In addition, both > Apache Pig and Hadoop are supported for data input and output. Finally, the > Phoenix is included and installable through Apache Bigtop and the build and > test suite are run through Apache Maven. > > Phoenix offers an alternative query engine to Apache Hadoop (MapReduce). > Unlike MapReduce, Phoenix is designed for lower-latency, OLTP, and > interactive workloads. This makes the projects complimentary as users may > run MapReduce and Phoenix side-by-side. > > We plan to increase the interoperability between Phoenix, Apache Hive, and > standalone Apache HBase usage by standardizing on a new type system that > has been introduced in the current major release of HBase. By all these > products adopting this new serialization format, interoperability between > them will take a big step forward. > > In addition, we plan to explore providing lower level APIs for other > products such as Apache Drill to plug into when querying HBase data so that > they get the performance benefits of using Phoenix. > > A Excessive Fascination with the Apache Brand > > Phoenix is already a healthy and relatively well known open source project. > This proposal is not for the purpose of generating publicity. Rather, the > primary benefits to joining Apache are those outlined in the Rationale > section. > > Documentation > > Additional documentation on Phoenix may be found on its github website: > > Phoenix overview: > https://github.com/forcedotcom/phoenix/blob/master/README.md > > Phoenix wiki: https://github.com/forcedotcom/phoenix/wiki > > Phoenix road map: https://github.com/forcedotcom/phoenix/wiki#roadmap > > Phoenix issue tracking: > > https://github.com/forcedotcom/phoenix/issues?direction=desc&sort=updated&state=open > > Phoenix codebase: https://github.com/forcedotcom/phoenix > > Phoenix SQL language reference: http://forcedotcom.github.io/phoenix/ > > Phoenix performance: > > https://github.com/forcedotcom/phoenix/wiki/Performance#phoenix-vs-related-products > > User group: https://groups.google.com/group/phoenix-hbase-user > > Initial Source > > The Phoenix codebase is currently hosted on Github: > https://github.com/forcedotcom/phoenix. > > Source and Intellectual Property Submission Plan > > Currently, the Phoenix codebase is distributed under a BSD license. Upon > entering Apache, the Phoenix license will be migrated to the Apache 2.0 > License. > > External Dependencies > > Beyond relying on Apache HBase, Phoenix has the following external > dependencies: > > ANTLR 3.5 (BSD license: http://www.antlr3.org/license.html) > > Sqlline 1.1.2 (BSD license: > https://github.com/julianhyde/sqlline/blob/master/LICENSE) > > Open CSV 2.3 (Apache 2.0 license) > > Upon acceptance to the incubator, we would begin a thorough analysis of all > transitive dependencies to verify this information and introduce license > checking into the build and release process by integrating with Apache Rat. > > Required Resources > > Mailing list > > We will migrate the existing Phoenix mailing lists as follows: > > phoenix-hbase-u...@googlegroups.com --> us...@phoenix.incubator.apache.org > > phoenix-hbase-...@googlegroups.com --> d...@phoenix.incubator.apache.org > > priv...@phoenix.incubator.apache.org for IPMC members > > comm...@phoenix.incubator.apache.org > > The latter is to be consistent with the new PIAO naming scheme for > podlings. > > Source control > > The Phoenix team would like to use Git for source control, due to our > current use of Git. We request a writeable Git repo for Phoenix, and > mirroring to be set up to Github through INFRA. > > Issue Tracking > > Phoenix currently uses the github issue tracking system associated with its > github repo: > > https://github.com/forcedotcom/phoenix/issues?direction=desc&sort=updated&state=open > . > We will migrate to the Apache JIRA: > http://issues.apache.org/jira/browse/PHOENIX > > Other Resources > > Jenkins/Hudson for builds and test running. > Wiki for documentation purposes > Blog to improve project dissemination > > Initial Committers > > James Taylor > > Mujtaba Chohan > > Jesse Yates > > Eli Levine > > Simon Toens > > Maryann Xue > > Anoop Sam John > > Ramkrishna S Vasudevan > > Jeffrey Zhong > > Nick Dimiduk > > Affiliations > > The initial committers are from three organizations: Salesforce.com, Intel, > and Hortonworks. > > James Taylor (Salesforce.com) > Mujtaba Chohan (Salesforce.com) > Jesse Yates (Salesforce.com) > Eli Levine (Salesforce.com) > Simon Toens (Salesforce.com) > Maryann Xue (Intel) > Anoop Sam John (Intel) > Ramkrishna S Vasudevan (Intel) > Jeffrey Zhong (Hortonworks) > Nick Dimiduk (Hortonworks) > > Sponsors > > Champion > > Michael Stack > > Nominated Mentors > > Michael Stack > Lars Hofhansl > Andrew Purtell > Devaraj Das > Enis Soztutar > Steven Noels > > Sponsoring Entity > > The Apache Incubator > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Twill for Incubation
MC member for HBase. Poorna Chandra and Albert Shau have > made many contributions to Twill. > > == Alignment == > > The ASF is the natural choice to host the Twill project as its goal of > encouraging community-driven open source projects fits with our vision for > Twill. > > Additionally, many other projects with which we are familiar and expect > Twill to integrate with, such as ZooKeeper, YARN, HDFS, log4j, and others > mentioned in the External Dependencies section are Apache projects, and > Twill will benefit by close proximity to them. > > = Known Risks = > > == Orphaned Products == > > There is very little risk of Twill being orphaned, as it is a key part of > Continuuity’s products. The core Twill developers plan to continue to work > on Twill, and Continuuity has funding in place to support their efforts > going forward. > Many other Big Data companies can benefit from Twill, and we have already > received interest from various entities that would like to use and > contribute to Twill. > > == Inexperience with Open Source == > > Several of the core developers have experience with open source > development. Terence Yim, Andreas Neumann and Gary Helmling are currently > Apache committers for Helix, Oozie and HBase respectively > Homogeneous Developers > > The current core developers are all Continuuity employees. However, we > intend to establish a developer community that includes independent and > corporate contributors. We are encouraging new contributors via our mailing > lists, public presentations, and personal contacts, and we will continue to > do so. Various entities have already expressed interest in becoming > involved with Twill. > > == Reliance on Salaried Developers == > > Currently, these developers are paid to work on Twill. Once the project has > built a community, we expect to attract committers, developers and > community > other than the current core developers. However, because Continuuity > products use Twill internally, the reliance on salaried developers is > unlikely to change, at least in the near term. > > == Relationships with Other Apache Products == > > Twill is deeply integrated with Apache projects. Twill uses Apache YARN as > its underlying resource management and task scheduling system and Apache > Zookeeper for coordination. In addition, Twill uses Apache HDFS and Apache > Kafka. A number of other Apache projects are Twill dependencies and are > listed in the External Dependencies section. > > == An Excessive Fascination with the Apache Brand == > > While we respect the reputation of the Apache brand and have no doubt that > it will attract contributors and users, our interest is primarily to give > Twill a solid home as an open source project following an established > development model. We have also given additional reasons in the Rationale > and Alignment sections. > > = Documentation = > > The current documentation for Weave is at > https://github.com/continuuity/weave. > This will be adapted to the new name Twill. > > = Initial Source = > > The Weave codebase is currently hosted at > https://github.com/continuuity/weave. Weave will be renamed to Twill to > seed the Apache git repository. > > = External Dependencies = > > The dependencies all have Apache-compatible licenses: > * avro (Apache 2.0) > * hadoop (Apache 2.0) > * gson (Apache 2.0) > * guava-libraries (Apache 2.0) > * hbase (Apache 2.0) > * hdfs (Apache 2.0) > * kafka (Apache 2.0) > * netty (Apache 2.0) > * snappy-java (Apache 2.0) > * yarn (Apache 2.0) > * zookeeper (Apache 2.0) > * asm (BSD) > * junit (EPL v1.0) > * logback (EPL v1.0 ) > * slf4j (MIT) > > = Cryptography = > > Twill will depend on secure Hadoop, which can optionally use Kerberos. > > = Required Resources = > > == Mailing Lists == > > * twill-private for private PMC discussions (with moderated subscriptions) > * twill-dev for technical discussions among contributors > * twill-commits for notification about commits > > == Subversion Directory == > > Git is the preferred source control system: git://git.apache.org/twill > > == Issue Tracking == > > JIRA Twill (TWILL) > > == Other Resources == > > The existing code already has unit tests, so we would like a Hudson > instance to run them whenever a new patch is submitted. This can be added > after project creation. > > = Initial Committers = > > * Terence Yim > * Andreas Neumann > * Gary Helmling > * Poorna Chandra > * Albert Shau > > = Affiliations = > > * Terence Yim (Continuuity) > * Andreas Neumann (Continuuity) > * Gary Helmling (Continuuity) > * Poorna Chandra (Continuuity) > * Albert Shau (Continuuity) > > = Sponsors = > > == Champion == > > Vinod K (Apache Member) > > == Nominated Mentors == > > * Arun C Murthy > * Tom White > * Patrick Hunt > * Andrei Savu > > == Sponsoring Entity == > > We are requesting that the Incubator sponsor this project. > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
iki/**Leitstand> > >>>>>>>>>> < > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> http://de.wikipedia.org/wiki/**Leitstand< > http://de.wikipedia.org/wiki/Leitstand> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Fri, Sep 20, 2013 at 3:23 AM, Olivier Lamy > > >>>>>>>>>> > >>>>>>>>> wrote: > >>>>>> > >>>>>> > >>>>>>> > >>>>>>>>>> So It looks we have more interested folks. > >>>>>>>>>> > >>>>>>>>>>> But before starting the vote I'd like to find an other name for > >>>>>>>>>>> the > >>>>>>>>>>> project. > >>>>>>>>>>> Someone proposed "Baldur" or "Balder" (note, It's a popular > >>>>>>>>>>> germanic > >>>>>>>>>>> god). So as a French guy this proposition looks to be rude for > me > >>>>>>>>>>> > >>>>>>>>>> :-). > >>>>>> > >>>>>> > >>>>>>> More seriously, this name doesn't hurt me. > >>>>>>>>>>> > >>>>>>>>>>> If any other propositions, it's time to speak. > >>>>>>>>>>> > >>>>>>>>>>> Cheers > >>>>>>>>>>> -- > >>>>>>>>>>> Olivier > >>>>>>>>>>> > >>>>>>>>>>> On 16 September 2013 08:25, Tammo van Lessen > >>>>>>>>>>> >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>> Am 15.09.2013 15:35 schrieb "Romain Manni-Bucau" < > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> rmannibu...@gmail.com > >>>>>> > >>>>>> > >>>>>>> : > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Hi > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> Angular is great but i hope well keep extensibility possible > >>>>>>>>>>>>> > >>>>>>>>>>>> without > >>>>>> > >>>>>> > >>>>>>> js. > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> In > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> all case well get at least a thread on it to discuss about the > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> stack we > >>>>>> > >>>>>> > >>>>>>> want and well use ;) > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> Looking forward to that discussion ;) I'd prefer progressive > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> enhancement > >>>>>> > >>>>>> > >>>>>>> over SPAs in this context as well. Or even http://roca-style.org. > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> Tammo > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> -- > >>>>>>>>>>> Olivier Lamy > >>>>>>>>>>> Ecetera: http://ecetera.com.au > >>>>>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy > >>>>>>>>>>> > >>>>>>>>>>> > --** > >>>>>>>>>>> --** > >>>>>>>>>>> - > >>>>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator. > >>>>>>>>>>> apache.org< > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>>> For additional commands, e-mail: general-help@incubator.apache. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> **org general-h...@incubator.apache.org> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> -- > >>>>>>>>> > >>>>>>>>> Jean-Baptiste Onofré > >>>>>>>>> jbono...@apache.org > >>>>>>>>> http://blog.nanthrax.net > >>>>>>>>> Talend - http://www.talend.com > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> --** > >>>>>> > >>>>>> --**- > >>>>>> > >>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator. > apache.org< > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>>> For additional commands, e-mail: general-help@incubator.apache.** > >>>>>>>>> > >>>>>>>>> **org< > >>>>>>>>> > >>>>>>>> > >>>>>>>> general-help@incubator.apache.**org< > general-h...@incubator.apache.org> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> --**--** > >>>>>>> - > >>>>>>> To unsubscribe, e-mail: > >>>>>>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>>>>>> For additional commands, e-mail: > >>>>>>> general-help@incubator.apache.**org< > general-h...@incubator.apache.org> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Olivier Lamy > >>>>>> Ecetera: http://ecetera.com.au > >>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy > >>>>>> > >>>>>> --**--** > >>>>>> - > >>>>>> To unsubscribe, e-mail: > >>>>>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>>>>> For additional commands, e-mail: > >>>>>> general-help@incubator.apache.**org< > general-h...@incubator.apache.org> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> > >>>> > >>>> > --**--**- > >>>> To unsubscribe, e-mail: > >>>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>>> For additional commands, e-mail: > >>>> general-help@incubator.apache.**org > > >>>> > >>> > >>> > --**--**- > >>> To unsubscribe, e-mail: > >>> general-unsubscribe@incubator.**apache.org< > general-unsubscr...@incubator.apache.org> > >>> For additional commands, e-mail: > >>> general-help@incubator.apache.**org > >>> > >>> > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Aurora for Apache Incubation
pressed an interest in Aurora. > > == Reliance on Salaried Developers == > > Initial Aurora committers are salaried developers at Twitter, however > shortly after open sourcing the code we plan to diversify the project’s > core committers and contributors. > > == Relationships with Other Apache Products == > > Initially, Aurora has been developed as a scheduler for Apache Mesos. > Additionally, it relies on ZooKeeper for service discovery, allowing > servers to register at a location and clients to subsequently discover the > servers. > > == An Excessive Fascination with the Apache Brand == > > While we respect the reputation of the Apache brand and have no doubts that > it will attract contributors and users, our interest is primarily to give > Aurora a solid home as an open source project following an established > development model. We have also given reasons in the Rationale and > Alignment sections. > > = Documentation = > > This proposal exists online as > http://wiki.apache.org/incubator/AuroraProposal. Basic build instructions > are included in the existing github repository, and the source code has > thorough documentation. User documentation exists internally to Twitter, > and as part of incubation will be adapted to share and improve user > documentation overall. > > = Initial Source = > > JIRA Aurora (AURORA) > > = Source and Intellectual Property Submission Plan = > > A snapshot of the Aurora scheduler has been posted on github for review: > https://github.com/twitter/aurora > > = External Dependencies = > > All Aurora dependencies have Apache compatible licenses. > > = Cryptography = > Not applicable. > > = Required Resources = > > == Mailing Lists == > > * aurora-private for private PMC discussions > * aurora-dev > * aurora-commits > > == Subversion Directory == > > We prefer to use Git as our source control system: git:// > git.apache.org/aurora > > == Issue Tracking == > > JIRA Aurora (AURORA) > > = Initial Committers = > > * Jonathan Boulle (jon at twitter dot com) > * William Farner (bill at twitter dot com) > * Suman Karumuri (skarumuri at twitter dot com) > * Maxim Khutornenko (mkhutornenko at twitter dot com) > * Dave Lester (dlester at twitter dot com) > * Kevin Sweeney (ksweeney at twitter dot com) > * Brian Wickman (wickman at twitter dot com) > > = Affiliations = > > Twitter > > = Sponsors = > > == Champion == > > * Benjamin Hindman (benh at apache dot org) > > == Nominated Mentors == > > * Jake Farrell (jfarrell at apache dot org) > * Benjamin Hindman (benh at apache dot org) > * Chris Mattmann (mattmann at apache dot org) > * Henry Saputra (hsaputra at apache dot org) > > == Sponsoring Entity == > Incubator PMC > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator
rectory === > We prefer to use Git as our source control system: > git://git.apache.org/usergrid/. If possible, we would like to keep > leveraging the extremely useful github facilities for workflow using a > process much like that employed by the Apache Cordova project (documented > here http://wiki.apache.org/cordova/ContributorWorkflow). > > === Issue Tracking === > JIRA Usergrid (USERGRID) > > === Other Resources === > None. > > > == Initial Committers == > > * Alberto Leal (Globo.com) > * Alex Karasulu (Apigee) > * Dave Johnson (Apigee) > * Ed Anuff (Apigee) > * Nate McCall (The Last Pickle) > * Rod Simpson (Apigee) > * Scott Ganyo (Apigee) > * Shaozhuang Liu > * Sungju Jin (Korea Telecom) > * Tim Anglade (Apigee) > * Todd Nine (Apigee) > * Jim Jagielski (RedHat) > > > == Affiliations == > > * Apigee > * Korea Telecom > * Globo.com > * The Last Pickle > > > == Sponsors == > > === Champion === > Jim Jagielski > > === Nominated Mentors === > * Alex Karasulu > * Dave Johnson > > === Sponsoring Entity === > Incubator PMC > > > - > 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 > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
On Fri, Sep 20, 2013 at 6:53 AM, Olivier Lamy wrote: > So It looks we have more interested folks. > But before starting the vote I'd like to find an other name for the > project. > Someone proposed "Baldur" or "Balder" (note, It's a popular germanic > god). So as a French guy this proposition looks to be rude for me :-). > More seriously, this name doesn't hurt me. > If any other propositions, it's time to speak. > > Cheers > -- > Olivier How about "Apache Thor" (picked up from the movie Thor) -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Storm into the Incubator
MQ and JMQ as the default mechanism for internal > messaging layer, and 0MQ/JMQ is licensed under GNU Lesser General > Public License. Recently, we have made Storm messaging layer > pluggable, and plan to use Netty (which is licensed under Apache > License v2) as our default messaging plugin (while keep 0MQ as an > optional plugin). > > == Cryptography == > > We do not expect Storm to be a controlled export item due to the use > of encryption. > Storm enable encryptions via 2 plugins: >* SASL authentication plugins … Currently, we have provide “no-op” > authentication and digest authentication. In near future, we will > introduce Kerberos authentication. >* Tuple payload serialization plugins … Storm provides plugins for > plain-object serialization and blowfish encryption. > > == Required Resources == > > === Mailing lists === > > * storm-user > * storm-dev > * storm-commits > * storm-private (with moderated subscriptions) > > === Subversion Directory === > > Git is the preferred source control system: git://git.apache.org/storm > > > === Issue Tracking === > > JIRA Storm (STORM) > > == Initial Committers == > >* Nathan Marz >* James Xu >* Jason Jackson >* Andy Feng >* Flip Kromer >* David Lao >* P. Taylor Goetz > > == Affiliations == > >* Nathan Marz - Nathan’s Startup >* James Xu - Alibaba >* Jason Jackson - Twitter >* Andy Feng - Yahoo! >* Flip Kromer - Infochimps >* David Lao - Microsoft >* P. Taylor Goetz - Health Market Science > > == Sponsors == > > > === Champion === > >* Doug Cutting > > === Nominated Mentors === > > * Ted Dunning > * Arvind Prabhakar > * Devaraj Das > * Matt Franklin > * Benjamin Hindman > > === Sponsoring Entity === > > The Apache Incubator > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Graduate Apache Curator as an Apache Top Level Project
development and increased participation in the >Apache Curator Project; and be it further > >RESOLVED, that the Apache Curator Project be and hereby >is tasked with the migration and rationalization of the Apache >Incubator Curator podling; and be it further > >RESOLVED, that all responsibilities pertaining to the Apache >Incubator Curator podling encumbered upon the Apache Incubator >Project are hereafter discharged. > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Release Curator 2.2.0-incubating
+1 (non-binding) Verified checksum Build from source, works fine. On Mon, Aug 5, 2013 at 2:05 PM, Ioannis Canellos wrote: > Hello, > > This is a vote for the release of Apache Curator, version 2.2.0-incubating. > > This has been voted on via the d...@curator.incubator.apache.org mailing > list (vote thread [1], and results [2]), and now requires a vote on > general@incubator.apache.org. > > 3 IPMC votes have already been cast on the vote held on dev@curator: > > +1 (PPMC / binding) > * Luciano Resende > * Patric Hunt > * Enis Soztutar > > There were 0 -1 or +0 votes cast. > > *** Please download, test and vote by [August 8 2013]. > > Note that we are voting upon the source (tag), binaries are provided > for convenience. > > Link to release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425&version=12324635 > > Staging repo: > https://dist.apache.org/repos/dist/dev/incubator/curator/2.2.0-incubating > > Binary artifacts: > https://repository.apache.org/content/repositories/orgapachecurator-045/ > > > The tag to be voted upon: > > > https://git-wip-us.apache.org/repos/asf?p=incubator-curator.git;a=tag;h=699b1a9422cda7732c112c7640f4a06eaa2de27f > > > Curator's KEYS file containing PGP keys we use to sign the release: > http://www.apache.org/dist/incubator/curator/KEYS > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks! > > [1]: > http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201307.mbox/%3cCADHGh9XcoV7bKoBZLy6g8BbZWUY98oCO9FmVEn1FE5=ots2...@mail.gmail.com%3e > > [2]: > http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3ccadhgh9vifyghulpjuaryeyr61njjrlskqrkdrrgqdxhidpd...@mail.gmail.com%3e > > ----- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE]: Accept Sentry in Apache Incubator
ar at iqt.org) > * Greg Chanan (gchanan at apache.org) > * Hadi Nahari (hnahari at nvidia.com) > * Jarek Jarcec Cecho (jarcec at apache.org) > * Johnny Zhang (xiaoyuz at cloudera.com) > * Karthik Ramachandran (kramachandran at iqt.org) > * Mark Grover (mgrover at cloudera.com) > * Milo Polte (milo at wibidata.com) > * Lenni Kuff (lskuff at cloudera.com) > * Patrick Daly (daly at cloudera.com) > * Patrick Hunt (phunt at apache.org) > * Prasad Mujumdar (prasadm at apache.org) > * Raghu Mani (raghu.mani at oracle.com) > * Sean Mackrory (sean at cloudera.com) > * Shreepadma Venugopalan (shreepadma at cloudera.com) > * Sravya Tirukkovalur (sravya at cloudera.com) > * Tom White (tomwhite at apache.org) > * Xuefu Zhang (xuefu at apache.org) > > == Affiliations == > > * Ali Rizvi (Oracle) > * Arvind Prabhakar (Cloudera) > * Brock Noland (Cloudera) > * Chaoyu Tang (Cloudera) > * Daisy Zhou (Wibidata) > * David Nalley (Citrix) > * Erick Tryzelaar (Lab41) > * Greg Chanan (Cloudera) > * Hadi Nahari (Nvidia) > * Jarek Jarcec Cecho (Cloudera) > * Johnny Zhang (Cloudera) > * Karthik Ramachandran (Lab41) > * Mark Grover (Cloudera) > * Milo Polte (Wibidata) > * Lenni Kuff (Cloudera) > * Patrick Daly (Cloudera) > * Patrick Hunt (Cloudera) > * Prasad Mujumdar (Cloudera) > * Raghu Mani (Oracle) > * Sean Mackrory (Cloudera) > * Shreepadma Venugopalan (Cloudera) > * Sravya Tirukkovalur (Cloudera) > * Tom White (Cloudera) > * Xuefu Zhang (Cloudera) > > == Sponsors == > > === Champion === > > * Arvind Prabhakar (Cloudera) > > === Nominated Mentors === > > * Arvind Prabhakar (Cloudera) > * David Nalley (Citrix) > * Joe Brockmeier (Citrix) > * Olivier Lamy (Ecetera) > * Patrick Hunt (Cloudera) > * Tom White (Cloudera) > > === Sponsoring Entity === > > We are requesting the Incubator to sponsor this project. > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Samza into the Incubator
ore developers plan to work full time on the project. There is very > little risk of Samza being abandoned as it is part of LinkedIn's internal > infrastructure. > > Inexperience with Open Source > > All of the core developers have experience with open source development. > Jay and Chris has been involved with several open source projects released > by LinkedIn, and Jay is a committer on Apache Kafka. Jakob has been > actively involved with the ASF as a full-time Hadoop committer and PMC > member. Sriram is a contributor to Apache Kafka. > > Homogeneous Developers > > The current core developers are all from LinkedIn. However, we hope to > establish a developer community that includes contributors from several > corporations and we actively encouraging new contributors via the mailing > lists and public presentations of Samza. > > Reliance on Salaried Developers > > Currently, the developers are paid to do work on Samza. However, once the > project has a community built around it, we expect to get committers, > developers and community from outside the current core developers. However, > because LinkedIn relies on Samza internally, the reliance on salaried > developers is unlikely to change. > > Relationships with Other Apache Products > > Samza is deeply integrated with Apache products. Samza uses Apache Kafka as > its underlying message passing system. Samza also uses Apache YARN for task > scheduling. Both YARN and Kafka, in turn, rely on Apache ZooKeeper for > coordination. In addition, we hope to integrate with Apache HDFS in the > near future. > > An Excessive Fascination with the Apache Brand > > While we respect the reputation of the Apache brand and have no doubts that > it will attract contributors and users, our interest is primarily to give > Samza a solid home as an open source project following an established > development model. We have also given reasons in the Rationale and > Alignment sections. > > Documentation > > http://wiki.apache.org/incubator/SamzaProposal > > Initial Source > > Available upon request. > > External Dependencies > > The dependencies all have Apache compatible licenses. > > metrics (Apache 2.0) > zkclient (Apache 2.0) > zookeeper (Apache 2.0) > jetty (Apache 2.0) > jackson (Apache 2.0) > commons-httpclient (Apache 2.0) > slf4j (MIT) > avro (Apache 2.0) > hadoop (Apache 2.0) > junit (Common Public License) > grizzled-slf4j (BSD) > scalatra (https://github.com/scalatra/scalatra/blob/develop/LICENSE) > scala (http://www.scala-lang.org/node/146) > joptsimple (MIT) > kafka (Apache 2.0) > scalate (Apache 2.0) > leveldb jni (BSD) > Cryptography > > Samza will depend on secure Hadoop, which can optionally use Kerberos. > > Required Resources > > Mailing Lists > > samza-private for private PMC discussions (with moderated subscriptions) > samza-dev > samza-commits > > Subversion Directory > > Git is the preferred source control system: git://git.apache.org/samza > > Issue Tracking > > JIRA Samza (SAMZA) > > Other Resources > > The existing code already has unit tests, so we would like a Hudson > instance to run them whenever a new patch is submitted. This can be added > after project creation. > > Initial Committers > > Jay Kreps > Jakob Homan > Chris Riccomini > Sriram Subramanian > Affiliations > > Jay Kreps (LinkedIn) > Jakob Homan (LinkedIn) > Chris Riccomini (LinkedIn) > Sriram Subramanian (LinkedIn) > Sponsors > > Champion > > Jakob Homan (Apache Member) > > Nominated Mentors > > Arun C Murthy > Chris Douglas > Roman Shaposhnik > > Sponsoring Entity > > We are requesting the Incubator to sponsor this project. > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Apache Spark for the Incubator
tor.apache.org > * spark-developers@googlegroups --> d...@spark.incubator.apache.org > * spark-commits are hosted on Github, so we would request > comm...@spark.incubator.apache.org > > The latter is to be consistent with the new PIAO naming scheme for > podlings. > > === Source control === > The Spark team would like to use Git for source control, due to our > current use of Git. > We request a writeable Git repo for Spark, and mirroring to be set up to > Github through INFRA. Champion Mattmann can assist with creating INFRA > tickets for this. > > === Issue Tracking === > Spark currently uses a hosted JIRA deployment for issue tracking. We will > migrate to the Apache JIRA. > http://issues.apache.org/jira/browse/SPARK > > == Initial Committers == > * Matei Zaharia > * Ankur Dave > * Tathagata Das > * Haoyuan Li > * Josh Rosen > * Reynold Xin > * Shivaram Venkataraman > * Mosharaf Chowdhury > * Charles Reiss > * Andy Konwinski > * Patrick Wendell > * Imran Rashid > * Ryan LeCompte > * Ravi Pandya > * Ram Sriharsha > * Robert Evans > * Mridul Muralidharan > * Thomas Dudziak > * Mark Hamstra > * Stephen Haberman > * Jason Dai > * Shane Huang > * Andrew xia > * Nick Pentreath > * Sean McNamara > > == Affiliations == > The initial committers are from nine organizations: UC Berkeley, > Quantifind, Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Mxit and > Webtrends. > > * Matei Zaharia (UCB) > * Ankur Dave (UCB) > * Tathagata Das (UCB) > * Haoyuan Li (UCB) > * Josh Rosen (UCB) > * Reynold Xin (UCB) > * Shivaram Venkataraman (UCB) > * Mosharaf Chowdhury (UCB) > * Charles Reiss (UCB) > * Andy Konwinski (UCB) > * Patrick Wendell (UCB) > * Imran Rashid (Quantifind) > * Ryan LeCompte (Quantifind) > * Ravi Pandya (Microsoft) > * Ram Sriharsha (Yahoo!) > * Robert Evans (Yahoo!) > * Mridul Muralidharam (Yahoo!) > * Thomas Dudziak (ClearStory) > * Mark Hamstra (ClearStory) > * Stephen Haberman (Bizo) > * Jason Dai (Intel) > * Shane Huang (Intel) > * Andrew Xia (Intel) > * Nick Pentreath (Mxit) > * Sean McNamara (Webtrends) > > == Sponsors == > === Champion === > * Chris Mattmann > > === Nominated Mentors === > * Chris Mattmann > * Paul Ramirez > * Andrew Hart > * Thomas Dudziak > * Suresh Marru > * Henry Saputra > > === Sponsoring Entity === > The Apache Incubator > > > > > > ++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept jclouds into the Apache Incubator
Andrew Gaul, gaul at maginatics dot com > * Andrew Phillips, aphillips at qrmedia dot com > * Matt Stephenson, mattstep at mattstep dot net > * Everett Toews, everett dot toews at rackspace dot com > * Becca Wood, silkysun at silkysun dot net > > == Affiliations == > > * Ignasi Barrera, Abiquo > * Andrew Bayer, Cloudera > * Ioannis Canellos, Red Hat > * Adrian Cole, Netflix > * Andrew Gaul, Maginatics > * Matt Stephenson, Google > * Everett Toews, Rackspace > > == Sponsors == > === Champion === > > * Brian McCallister, Apache Software Foundation > > === Mentors === > > * Brian McCallister, Apache Software Foundation > * Tom White, Apache Software Foundation > * Henning Schmiedehausen, Apache Software Foundation > * David Nalley, Apache Software Foundation > * Jean-Baptiste Onofré, Apache Software Foundation > * Mohammad Nour El-Din, Apache Software Foundation > * Olivier Lamy, Apache Software Foundation > * Tomaz Muraus, Apache Software Foundation > * Suresh Marru, Apache Software Foundation > * Carlos Sanchez, Apache Software Foundation > > === Sponsoring Entity === > > The jclouds contributors and community request sponsorship from the > Incubator. > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Provisionr into the Apache Incubator
al committers are > paid by their employer to contribute to this project. However, they are all > passionate about the project, and we are confident that the project will > continue even if no salaried developers contribute to the project. We are > committed to recruiting additional committers including non-salaried > developers. > > === Relationships with Other Apache Products === > > Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a > numerous ways. We look forward to collaborating with those communities, as > well as other Apache communities (like Apache Helix). > > === A Excessive Fascination with the Apache Brand === > > We think that Provisionr will benefit from the community sharing ideas and > best practices for running cloud services. The ASF does a great job at > building communities, which is why we want to build Provisionr at Apache. > > == Documentation == > > * https://github.com/axemblr/axemblr-provisionr/wiki > * > > https://github.com/axemblr/axemblr-provisionr/wiki/Axemblr-Provisionr-in-5-Minutes > * > > https://github.com/axemblr/axemblr-provisionr/wiki/Starting-an-HDFS-cluster-on-EC2-with-Provisionr-and-Rundeck > * > > http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 > > == Initial Source == > > Available on GitHub: https://github.com/axemblr/axemblr-provisionr > > == Source and Intellectual Property Submission Plan == > > We are going to prepare a software grant as needed. The source code is > already available under the Apache 2.0 license. > > == External Dependencies == > > The existing external dependencies all have Apache compatible licenses: > Activiti (Apache 2.0), AWS SDK (Apache 2.0), jclouds (Apache 2.0), Google > Guava (Apache 2.0). > > == Cryptography == > > Provisionr uses standard APIs and tools for SSH and SSL. > > == Required Resources == > > === Mailing lists === > > * provisionr-private > * provisionr-dev > > === Version Control === > > Git repository > > === Issue Tracking === > > JIRA Provisionr (PROVISIONR) > > === Other Resources === > > The existing code already has unit and integration tests so we would like a > Jenkins instance to run them whenever a new patch is submitted. This can be > added after project creation. > > == Initial Committers == > > * Andrei Savu - asavu at apache dot org > * Ioan Eugen Stan - ieugen at apache dot org > * Alex Ciminian - alex.ciminian at gmail dot org > * Amandeep Khurana - amansk at gmail dot com > * Roman Shaposhnik - rvs at apache dot org > * Eric Sammer - esammer at apache dot org > > == Sponsors == > > === Champion === > > Tom White - tomwhite at apache dot org > > === Nominated Mentors === > > * Roman Shaposhnik - rvs at apache dot org > * Tom White - tomwhite at apache dot org > * Mohammad Nour - mnour at apache dot org > > === Sponsoring === > > Incubator PMC > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Tez into Incubator
e > * Thomas Graves > * Vikram Dixit > * Vinod Kumar Vavilapalli > * William Graham > > == Affiliations == > The initial committers are employees of Cloudera, Facebook, Hortonworks, > Microsoft, Twitter and Yahoo Inc. > > * Alan Gates - Hortonworks > * Arun C Murthy - Hortonworks > * Ashutosh Chauhan - Hortonworks > * Bikas Saha - Hortonworks > * Chris Douglas - Microsoft > * Daryn Sharp - Yahoo > * Devaraj Das - Hortonworks > * Gopal Vijayaraghavan - Hortonworks > * Gunther Hagleitner - Hortonworks > * Hitesh Shah - Hortonworks > * Jason Lowe - Yahoo > * Jean Xu - Facebook > * Jitendra Pandey - Hortonworks > * Julien Le Dem - Twitter > * Kevin Wilfong - Facebook > * Mike Liddell - Microsoft > * Namit Jain - Facebook > * Nathan Roberts - Yahoo > * Owen O'Malley - Hortonworks > * Robert Evans - Yahoo > * Siddharth Seth - Hortonworks > * Tom White - Cloudera > * Thomas Graves - Yahoo > * Vikram Dixit - Hortonworks > * Vinod Kumar Vavilapalli - Hortonworks > * William Graham - Twitter > > The nominated mentors are employees of Hortonworks, LinkedIn, > NASA JPL and Microsoft. > > * Alan Gates - Hortonworks > * Arun C Murthy - Hortonworks > * Chris Douglas - Microsoft > * Chris Mattman - NASA JPL > * Jakob Homan - LinkedIn > * Owen O'Malley - Hortonworks > > == Sponsors == > > === Champion === > Arun C Murthy > > === Nominated Mentors === > * Alan Gates – Architect at Hortonworks. > Committer for Pig. > * Arun C Murthy – Architect at > Hortonworks. Committer for Hadoop. > * Chris Douglas - Sr. Research Engineer at > Microsoft. Committer for Hadoop. > * Chris Mattman - Sr. Computer Scientist, > NASA JPL. Committer for Nutch, OODT and Tika. > * Jakob Homan – Sr. Software Engineer, > LinkedIn. Committer for Hadoop, Kafka, Giraph. > * Owen O'Malley – Architect at Hortonworks. > Committer for Hadoop, Ambari. > > === Sponsoring Entity === > Incubator > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Graduate Apache Crunch Podling from the Incubator
+1 On Tue, Feb 5, 2013 at 1:11 AM, Josh Wills wrote: > This is a call to graduate the Apache Crunch podling from Apache Incubator. > > Apache Crunch entered the Incubator in May of 2012. We have made > significant progress with the project since moving over to Apache. We have > ten committers listed on our status page at [1] including three accepted > after the podling was formed, and we have verified that Apache Crunch is a > suitable name. [2] > > We completed two releases (Apache Crunch 0.3.0-incubating and Apache Crunch > 0.4.0-incubating) and are currently preparing for a third. > > The community of Apache Crunch is active, healthy, and growing and has > demonstrated the ability to self-govern using accepted Apache practices. > > The Apache Crunch community voted overwhelmingly to graduate [3], > collecting three binding votes from our mentors and IPMC members Arun > Murthy, Tom White, and Patrick Hunt. You can view the discussion at [4] and > [5]. > > Our charter is below and on our wiki. [6] > > Please cast your votes: > > [ ] +1 Graduate Apache Crunch from Apache Incubator > [ ] +0 Indifferent to graduation status of Apache Crunch > [ ] -1 Reject graduation of Apache Crunch from Apache Incubator because... > > We'll run the vote for at least 72 hours (closing at the earliest at 8PM > GMT on February 7th.) > > [1] http://incubator.apache.org/projects/crunch.html > [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-18 > [3] http://markmail.org/message/7mplf2wyzqhs2gts > [4] http://markmail.org/message/3zu5wszwpaqegxic > [5] http://markmail.org/message/wbz43fpnta7r2w4e > [6] > https://cwiki.apache.org/confluence/display/CRUNCH/Graduation+Resolution > > X. Establish the Apache Crunch 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 the development of Java libraries for writing, testing, and > running MapReduce pipelines. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Crunch Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Crunch Project be and hereby is responsible > for the creation and maintenance of software related to development of > Java libraries for writing, testing, and running MapReduce pipelines; and > be it further > > RESOLVED, that the office of "Vice President, Apache Crunch" 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 Crunch Project, and to > have primary responsibility for management of the projects within the scope > of responsibility of the Apache Crunch 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 Crunch Project: > > * Brock Noland > * Christian Tzolov > * Gabriel Reid > * Josh Wills > * Kiyan Ahmadizadeh > * Matthias Friedrich > * Rahul Sharma > * Robert Chu > * Tom White > * Vinod Kumar Vavilapalli > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Josh Wills be appointed to the > office of Vice President, Apache Crunch, 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 Crunch 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 Crunch Project; and be it further > > RESOLVED, that the Apache Crunch Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator Crunch podling; > and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Crunch podling encumbered upon the Apache Incubator Project are > hereafter discharged. > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Drill into the Apache Incubator
and > developers of a Dremel-like tool is a key requirement for success of > the project. > > == Documentation == > Drill is inspired by Google's Dremel. Google has published a > [[http://research.google.com/pubs/pub36632.html|paper]] highlighting > Dremel's innovative nested column-based data format and execution > engine. > > == Initial Source == > The requirement and design documents are currently stored in MapR > Technologies' source code repository. They will be checked in as part > of the initial code dump. > > == Cryptography == > Drill will eventually support encryption on the wire. This is not one > of the initial goals, and we do not expect Drill to be a controlled > export item due to the use of encryption. > > == Required Resources == > > === Mailing List === > * drill-private > * drill-dev > * drill-user > > === Subversion Directory === > Git is the preferred source control system: git://git.apache.org/drill > > === Issue Tracking === > JIRA Drill (DRILL) > > == Initial Committers == > * Tomer Shiran > * Ted Dunning > * Jason Frantz > * MC Srivas > * Chris Wensel > * Keys Botzum > * Gera Shegalov > * Ryan Rawson > > == Affiliations == > The initial committers are employees of MapR Technologies, Drawn to > Scale and Concurrent. The nominated mentors are employees of MapR > Technologies, Lucid Imagination and Nokia. > > == Sponsors == > > === Champion === > Ted Dunning (tdunning at apache dot org) > > === Nominated Mentors === > * Ted Dunning – Chief Application > Architect at MapR Technologies, Committer for Lucene, Mahout and > ZooKeeper. > * Grant Ingersoll – Chief > Scientist at Lucid Imagination, Committer for Lucene, Mahout and other > projects. > * Isabel Drost – Software Developer at > Nokia Gate 5 GmbH, Committer for Lucene, Mahout and other projects. > > === Sponsoring Entity === > Incubator > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of DirectMemory as a TLP
+1 (non-binding) Hope am not too late On Wed, Aug 1, 2012 at 1:06 PM, Olivier Lamy wrote: > +1 > > 2012/8/1 Tim Williams : >> The DirectMemory community is ready to graduate and become a full TLP. >> We began incubation in October 2011 and have demonstrated our ability >> to function according to the Apache Way. We've successfully made a >> release. We have begun to grow the community. We didn't hold a >> separate formal vote - it's not a requirement - but the sense of the >> community is that we're ready to go[1]. >> >> Please VOTE to submit the below resolution to the board for consideration: >> >> [ ] +1 DirectMemory graduates to TLP >> [ ] -1 DirectMemory isn't ready, because... >> >> Vote will remain open for 72hrs... >> >> Thanks, >> --tim >> >> [1] - http://markmail.org/thread/3j4q7xehzn72dhk4 >> >> >> >> X. Resolution to establish the Apache DirectMemory 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 related a >>second level, off-heap, cache able to store large amounts of >> data without filling >>up the Java heap and thus avoiding long garbage collection cycles. >> >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>Committee (PMC), to be known as the "The Apache DirectMemory Project", >>be and hereby is established pursuant to Bylaws of the >>Foundation; and be it further >> >>RESOLVED, that The Apache DirectMemory Project be and hereby is >>responsible for the creation and maintenance of a software >>project related to a second level off-heap cache; and be it further >> >>RESOLVED, that the office of "Vice President, DirectMemory" 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 >>DirectMemory Project, and to have primary responsibility for >>management of the projects within the scope of responsibility of >>The Apache DirectMemory 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 DirectMemory Project: >> >> * Ioannic Canellos (iocanel) >> * Maurizio Cucchiara (mcucchiara) >> * Christian Grobmeier (grobmeier) >> * Olivier Lamy (olamy) >> * Raffaele P. Guidi (raffaeleguidi) >> * Simone Gianni (simoneg) >> * Simone Tripodi (simonetripodi) >> * Tommaso Teofill (tommaso) >> * Benoit Perroud (bperroud) >> >>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Raffaele P. >>Guidi be and hereby is appointed to the office of Vice >>President, DirectMemory, 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 DirectMemory Project be and hereby >>is tasked with the migration and rationalization of the Apache >>Incubator DirectMemory podling; and be it further >> >>RESOLVED, that all responsibility pertaining to the Apache >>Incubator DirectMemory podling encumbered upon the Apache Incubator >>PMC are hereafter discharged. > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Blur into the Apache Incubator
ooKeeper, and Thrift. It builds with Maven. During the course of > Blur development, a couple of patches have been committed back to the > Lucene project, including LUCENE-2205 and LUCENE-2215. Due to the > strong relationship with the before mentioned Apache projects, the > incubator is a good match for Blur. > > == Known Risks == > > === Orphaned Products === > There is only a small risk of being orphaned. The customers that > currently use Blur are committed to improving the codebase of the > project due to its fulfilling needs not addressed by any other > software. In addition, one customer is providing financial support to > further develop Blur given its importance on mission-critical > projects. > > === Inexperience with Open Source === > The codebase has been treated internally as an open source project > since its beginning, and Near Infinity has extensive experience > developing and releasing open source projects > (http://www.nearinfinity.com/products/open_source). We do not > anticipate difficulty in operating under the Apache Way. > > === Homogeneous Developers === > Current developers are all employed by Near Infinity but we are > actively seeking contributors from different companies and would > welcome their participation. > > === Reliance on Salaried Developers === > Blur was originally created by Aaron !McCurry as a personal project > and he remains the primary contributor. Currently, Aaron’s employer > (Near Infinity) fully supports his continued participation with paid, > dedicated time to work on Blur. All other current developers are paid > by Near Infinity to work on Blur as well. > > === Relationships with Other Apache Products === > Blur dependencies: > > * Apache Hadoop > * Apache Lucene > * Apache !ZooKeeper > * Apache Thrift > * Apache log4j > > === Apache Brand === > Our interest in releasing this code as an Apache project is due to its > strong relationship with other Apache projects, i.e. Blur has > dependencies on Hadoop, Lucene, !ZooKeeper, and Thrift and its > uniqueness within the Hadoop ecosystem. > > == Documentation == > Current documentation can be found at http://blur.io and > https://github.com/nearinfinity/blur. > > == Initial Source == > Blur has been in development since summer 2010. The core codebase > consists of about ~29,000 (~10,000 if the generated RPC code is not > included) lines of code mainly Java. > > == Source and Intellectual Property Submission Plan == > Blur core code, examples, documentation, and training materials will > be submitted by Near Infinity Corporation. > > == External Dependencies == > * concurrentlinkedhashmap - Apache 2.0 License - > http://code.google.com/p/concurrentlinkedhashmap/ > > == Cryptography == > none > > == Required Resources == > * Mailing Lists >* blur-private >* blur-dev >* blur-commits >* blur-user > * Subversion Directory >* https://git-wip-us.apache.org/repos/asf/blur.git > * Issue Tracking >* JIRA > * Continuous Integration >* Jenkins > * Web >* http://incubator.apache.org/blur/wiki at http://wiki.apache.org > or http://cwiki.apache.org > > == Initial Committers == > * Aaron !McCurry (aaron.mccurry at nearinfinity dot com) > * Scott Leberknight (scott.leberknight at nearinfinity dot com) > * Ryan Gimmy (ryan.gimmy at nearinfinity dot com) > * Tim Williams (twilliams at apache dot org) > * Patrick Hunt (phunt at apache dot org) > * Doug Cutting (cutting at apache dot org) > > == Affiliations == > * Aaron !McCurry, Near Infinity > * Scott Leberknight, Near Infinity > * Ryan Gimmy, Near Infinity > * Patrick Hunt, Cloudera > * Doug Cutting, Cloudera > > == Sponsors == > * Champion: Patrick Hunt > > == Nominated Mentors == > * Tim Williams (twilliams at apache dot org) > * Doug Cutting (cutting at apache dot org) > * Patrick Hunt (phunt at apache dot org) > > == Sponsoring Entity == > * Apache Incubator > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Write access for Ashish Desai
Could you please grant me the modify access to the incubator wiki page? My user name is Ashish Desai. Original Message Subject: Subscribe me From: Ashish Desai To: flex-dev-subscr...@incubator.apache.otg CC:
Re: [VOTE] CloudStack for Apache Incubator
s. >>> >>> Cryptography >>> >>> The CloudStack makes use of encryption functions available via Java and >>> the underlying OS. We expect that the CloudStack will have to follow the >>> export control procedures described at >>> http://www.apache.org/dev/crypto.html. When the CloudStack was previously >>> registered with BIS the open source version qualified for the TSU exception. >>> >>> The CloudStack uses https to communicate to XenServer and vCenter. ssh >>> and scp are used between the Management Server and hypervisor hosts as well. >>> >>> The CloudStack stores an MD5 hash of user password data. The CloudStack >>> uses MySQL encryption to store some data in an encrypted fashion. >>> >>> The CloudStack stores a pair of API public/secret keypairs for users. >>> This is done using javax.crypto.KeyGenerator with HMAC-SHA-1. >>> >>> The CloudStack does not specify key lengths explicitly. It uses SSH, SCP >>> and lets them negotiate encryption. >>> >>> The CloudStack provides a public HTTP-based API to provision and >>> deprovision VPN users. The CloudStack has internal Java-based abstractions >>> for managing VPN users. This Java software makes private API calls to >>> another system, which will then provision the VPN user in the VPN software >>> on that other system. The actual set up of the VPN session is done using >>> L2TP/IPSec. >>> >>> As mentioned earlier the CloudStack includes software to build and later >>> deploy Debian-based virtual machines. These VMs are stripped down versions >>> of Debian that include encryption sufficient for ssh/scp, https, and IPSec >>> VPN to work. The CloudStack does not include the source for these VMs. The >>> maximum encrypted throughput of the VPN has not been determined. >>> >>> Required Resources >>> >>> Mailing Lists >>> >>> We request mailing lists to match the mailing lists currently in use, >>> plus the recommended private list. These are: >>> >>> cloudstack-private: for confidential PPMC discussion >>> cloudstack-dev: for development discussions >>> cloudstack-user: for administrator and discussions >>> >>> Subversion Directory >>> >>> The CloudStack has used git for approximately two years. We understand >>> that there is a "prototype" git server available. We request an allocation >>> on this git server. We believe this will be less disruptive to the >>> committers than a change to SVN. >>> >>> We request "/repos/asf/incubator/cloudstack". >>> >>> Issue Tracking >>> >>> We would like an allocation for Jira. CloudStack uses bugzilla today, but >>> we have been planning a move to Jira for some time. We request that the >>> project name be "CloudStack". >>> >>> Other Resources >>> >>> The CloudStack Project includes several websites. Donation of these >>> websites was discussed in the IP submission plan. We would like to engage in >>> discussion on the logistics of this. >>> >>> Initial Committers >>> >>> In the past few months several new developers have joined the Citrix >>> CloudStack team. We are recommending that only the developers with several >>> months of experience with CloudStack join as initial committers. The Project >>> will then follow the meritocratic process to enable the newer team members >>> to become committers. We believe this will be a good exercise for us as we >>> transition to an Apache development model in the Project. >>> >>> The list of initial committers follows. At this time none of the initial >>> committers has a CLA on file with ASF. >>> >>> Abhinandan Prateek, abhinandan.prateek.at.citrix.com >>> Alena Prokharchyk, alena.prokharchyk.at.citrix.com >>> Alex Huang,alex.huang.at.citrix.com >>> Anthony Xu, xuefei.xu.at.citrix.com >>> Brian Federle, brian.federle.at.citrix.com >>> Chiradeep Vittal, chiradeep.vittal.at.citrix.com >>> David Nalley, david.nalley.at.citrix.com >>> Edison Su, edison.su.at.citrix.com >>> Frank Zhang, frank.zhang.at.citrix.com >>> Janardhana Reddy, janardhana.reddy.at.citrix.com >>> Jessica Tomechak, jessica.tomechak.at.citrix.com >>> Jessica Wang, jessica.wang.at.citrix.com >>> Kelven Yang, kelven.yang.at.citrix.com >>> Kevin Kluge, kevin.kluge.at.citrix.com >>> Kishan Kavala, kisha.kavala.at.citrix.com >>> Murali Reddy, murali.reddy.at.citrix.com >>> Nitin Mehta, nitin.mehta.at.citrix.com >>> Prachi Damle, prachi.damle.at.citrix.com >>> Sam Robertson, sam.robertson.at.citrix.com >>> Sheng Yang, sheng.yang.at.citrix.com >>> Sonny Chhen, sonny.chhen.at.citrix.com >>> Will Chan, will.chan.at.citrix.com >>> >>> Affiliations >>> >>> The initial committers are all affiliated with Citrix Systems. >>> >>> Sponsors >>> >>> Champion >>> >>> Jim Jagielski >>> >>> Nominated Mentors >>> >>> Jim Jagielski, Daniel Kulp, Alex Karasulu, Olivier Lamy, Brett Porter, >>> Mohammad Nour, Matt Hogstrom >>> >>> Sponsoring Entity >>> >>> We request that the Incubator sponsor this effort. >>> >>> >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
; While the Apache Software Foundation would be a good home for the > !DirectMemory project it already has some traction and it could live > on its own - however we see reciprocal benefits for both the ASF and > the project in adopting the brand to better reach the community > > = Documentation = > 1. [[https://github.com/raffaeleguidi/DirectMemory|The original > DirectMemory HomePage]] > 2. [[https://github.com/raffaeleguidi/DirectMemory/wiki|The original > DirectMemory Wiki]] > 3. [[https://github.com/raffaeleguidi/DirectMemory/issues|The > DirectMemory Issue Tracker (used also for enhancements, feature > requests and discussion)]] > > = Initial Source = > The intial source comprises code developed on > [[https://github.com/raffaeleguidi/DirectMemory/|GitHub]] contributed > under Grant from Raffaele P. Guidi for Directmemory. > > = Source and Intellectual Property Submission Plan = > Source code will be moved from > [[https://github.com/raffaeleguidi/DirectMemory/|GitHub]] space inside > the SVN space of the podling. > > = External Dependencies = > * Google Guava collections - > http://code.google.com/p/guava-libraries/ - Apache License V2.0 > * Protostuff - http://code.google.com/p/protostuff/ - Apache License V2.0 > * JoSQL - http://josql.sourceforge.net/ - Apache License V2.0 > * AspectJ - http://www.eclipse.org/org/ - Eclipse Public License > (Category B, used only in binary form) > * SLF4J - http://www.slf4j.org/ - MIT License (Category A) > * Logback - http://logback.qos.ch/ - dual licensed under EPL v1.0 and > LGPL 2.1 (Category B, but not really a dependency as it is astracted > by the SLF4j facade) > '''Build/Test time dependencies''' > * Maven - http://maven.apache.org/ - Apache License V2.0 > * JUnit - http://www.junit.org/ - CPL License v1.0 - (Category B, > used only in binary form) > * JUnit Benchmarks - > http://labs.carrotsearch.com/junit-benchmarks.html - Apache License > V2.0 > > = Cryptography = > The project does not handle cryptography in any way. > > = Required Resources = > * Mailing lists > * directmemory-private (with moderated subscriptions) > * directmemory-dev > * directmemory-user > * directmemory-commits > * Subversion directory > * https://svn.apache.org/repos/asf/incubator/directmemory > * Website > * Wiki (!DirectMemory) > * Issue Tracking > * JIRA (!DirectMemory) > > = Initial Committers = > Names of initial committers - in alphabetical order - with current ASF status: > > * Christian Grobmeier (ASF Member) > * Ioannis Canellos (ASF Committer) > * Maurizio Cucchiara (ASF Committer) > * Olivier Lamy (ASF Member) > * Raffaele P. Guidi (ICLA Signed) > * Simone Gianni (ASF Member) > * Simone Tripodi (ASF Member) > * Tommaso Teofili (ASF Member) > > = Sponsors = > == Champion == > * Christian Grobmeier > > == Nominated Mentors == > * Anthony Elder > * Christian Grobmeier > * Olivier Lamy > * Sylvain Wallez > * Tim Williams > > == Sponsoring Entity == > * The Apache Incubator > > = Other interested people (in alphabetical order) = > * TBD > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] S4 to join the Incubator
t; > === Orphaned Products === > > S4 has been used in production at Yahoo! and is being evaluated by > other organizations. The developers have continued to support the > project on their own time. We believe that adoption will increase > significantly as more tools and documentation become available. As the > project evolves, we may see new ideas that we may want to adopt or, if > it makes sense and is practical, we may want to merge two or more open > source projects. We believe that there is a clear need to have a well > supported open source stream processing platform and therefore, there > is low risk of the project becoming orphan. However, we are open to > combining projects in order to have fewer projects with a more active > community. Ultimately, this will be decided by the design ideas, the > implementation quality, and the adoption. > > === Inexperience with Open Source === > > The S4 code was open sourced by Yahoo! under Apache 2.0 license. One > committer of the S4 project, Flavio Junqueira, is intimately familiar > with the Apache model for open-source development and is experienced > with working with new contributors. Flavio is both a committer a PMC > member for ZooKeeper. The other developers have had experience as > contributors in other open-source projects. Most of the original S4 > developers continue to be committers. > > === Homogeneous Developers === > > The initial set of committers for S4 represent four different > companies: A9, Linkedin, Quantbench, and Yahoo!. This set is diverse > enough for a starting project. > > === Reliance on Salaried Developers === > > Some committers are contributing as part of their jobs, but as we move > to a more diverse set of developers we expect a good mix of salaried > and volunteer time. > > === Relationships with Other Apache Projects === > > S4 relies on the following Apache projects: > > * BCEL (bytecode generation library) > * commons cli (command line interface) > * commons logging (needed by some other dependency) > * log4j > * commons jexl (expression processing) > * zookeeper > * Maven and its usual plug-ins (build time only) > > Compared to existing projects, S4 complements existing functionality > in a few ways summarized below: > * Flume: S4 processes streams in a distributed fashion and enables > applications to form arbitrary graphs of processing elements. Flume > focuses on accumulating streams of logs in a centalized repository for > batch processing; > * Kafka: Kafka is a pub/sub messaging layer that interposes > generation of events and processing, while S4 itself forwards events > and processes them in a stream fashion. > * Hadoop: Hadoop focuses on batch processing of large data sets, > while S4 is a platform for stream processing of events. We would like > to implement extensions that enable processing in both platforms with > the same code. > > === An Excessive Fascination with the Apache Brand === > > The project has already received a significant amount of attention and > so far has been associated with Yahoo!. We would like, however, to > foster the development of a community around S4 that evolves > independently of the interests of a single company. Given the reliance > of S4 on some Apache projects and the principles promoted by the > foundation, we find it a suitable home for the project. > > == Documentation == > > * S4 Website: http://s4.io > * S4 documentation: http://docs.s4.io/ > * S4 Forum: http://groups.google.com/group/s4-project/topics > * S4 Mailing list (with archives): http://groups.google.com/group/s4-project > > == Source and Intellectual Property Submission Plan == > > The S4 source code is already licensed under Apache Software License > 2.0. The source code is available at https://github.com/s4 > > > == External Dependencies == > > * asm (3-clause BSD license) > * json (json.org's own license > http://www.crockford.com/JSON/license.html which is acceptable as per > Apache FAQ: http://www.apache.org/legal/resolved.html#json) > * kryo (4-clause BSD license) > * spring framework (Apache license - v 2) > * codehaus jackson (Apache license) > * junit (Common Public License - v 1.0) > > == Cryptography == > None > > == Required Resources == > > === Mailing lists === > * s4-dev > * s4-user > * s4-private (with moderated subscriptions) > * s4-commit > > === Subversion Directory === > > https://svn.apache.org/repos/asf/incubator/s4 > > === Issue Tracking === > > JIRA S4 (S4) > > == Initial Committers == > * Kishore Gopalakrishna (kg at s4 dot io) > * Flavio Junqueira (fpj at s4 dot io) > * Matthieu Morel (mm at s4 d
Re: [DISCUSS] DirectMemory to join the Apache Incubator
On Tue, Sep 20, 2011 at 3:54 PM, ant elder wrote: > That sounds like a really exciting project to bring to Apache. I'd be > happy to volunteer as a mentor if you need one, with the so many > existing ASF committors and members part of the project i expect > incubation should go pretty smoothly. > > ...ant Agree, I have been watching this project on github for a while. Seems like a nice extension to JCS (http://commons.apache.org/jcs/) thanks ashish - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
m) > > * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) > > * Vodacom South Africa (http://www.vodacom.com) > > * Mayo Clinic USA (http://www.mayoclinic.com) > > * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) > > == Core Developers == > > The core developers for AutoDeploy/Apache Kalumet project are : > > * Jean-Baptiste Onofré (founder in 2004). > > * Mike Duffy, WebSphere Consultant, contributes since 2005. > > == Open Source == > > Since the beginning, AutoDeploy was a Open Source project using GPL > license. It switched to Apache 2.0 license in 2009, approved by all > AutoDeploy developers (IP Clearance). > > As all AutoDeploy contributors has approved, Apache Kalumet uses the > Apache 2 license. > > AutoDeploy Console currently use NextApp Echo2 framework, released > under Mozilla Public License, which is a Category B license. > The Apache incubation phase will use Echo2, acting that we have to > switch to an Apache compliant framework (Pax Wicket and Vaadin could > be used) before any TLP graduation. > > = Known Risks = > > == Orphaned Products == > > AutoDeploy is already deployed in production at multiple companies. > (see Community Section) > AutoDeploy is getting traction with developers and thus the risks of > it being orphaned are minimal. > > == Inexperience with Open Source == > > All code developed for AutoDeploy has been open source from the start > (see Open Source section). > And mostly by an ASF member Jean-Baptiste Onofré who is intimately > familiar with the Apache model for open-source development and is > experienced with working with new contributors. > Jean-Baptiste Onofré, the creator of the project and one of the > committers is also a committer on Apache Karaf, Apache ServiceMix, > Apache Camel and Apache Ace. > > == Homogeneous Developers == > > The initial set of committers is from a small set of organizations. > However, we expect that once approved for incubation, the project will > attract new contributors from diverse organizations and will thus grow > organically. The participation of developers from several different > organizations in the mailing list is a strong indication for this > assertion. > > == Reliance on Salaried Developers == > > It is expected that Kalumet will be developed on salaried and > volunteer time, although all of the initial developers will work on it > mainly on salaried time. > > == Relationships with Other Apache Products == > > AutoDeploy/Apache Kalumet depends upon other Apache Projects: Xerces, > Xalan and multiple Apache Commons components and build systems like > Maven. It will also use Apache OSGi project (Felix, Karaf, ACE) and > project like Archiva. > > == A Fascination with the Apache Brand == > > The reason for joining Apache is to foster a healthy community of > contributors and consumers around the project. This is facilitated by > ASF and that is the primary reason we would like Kalumet to become an > Apache project. > > = Documentation = > > AutoDeploy docs: http://buildprocess.sourceforge.net/autodeploy.html > > == Initial Source == > > https://buildprocess.svn.sourceforge.net/svnroot/buildprocess/AutoDeploy/ > > == Source and Intellectual Property Submission Plan == > > The initial source is already Apache 2.0 licensed. > > == External Dependencies == > > The required external dependencies are all Apache License or > compatible licenses. Following components with non-Apache licenses are > enumerated : > > * Echo Web framework Mozilla Public License, which is a Category B > license (see plan to remove this dependency). > > == Cryptography == > > Kalumet does not depend upon any cryptography tools or libraries. > > = Required Resources = > > == Mailing lists == > > * kalumet-private (with moderated subscriptions) > > * kalumet-dev > > * kalumet-commits > > * kalumet-user > > == Subversion Directory == > > https://svn.apache.org/repos/asf/incubator/kalumet > > == Issue Tracking == > > JIRA Kalumet (Kalumet) > > == Other Resources == > > The existing code already has unit and integration tests so we would > like a Jenkins instance to run them whenever a new patch is submitted. > This can be added after project creation. > > == Initial Committer == > > * Mike Duffy (micdu...@gmail.com) > > * Ioannis Canellos (ioca...@apache.org) > > * Andreas Pieber (pie...@apache.org) > > * Achim Nierbeck (anierb...@apache.org) > > * Jamie Goodyear (jgoody...@apache.org) > > * Youhort Ly (youh...@gmail.com) > > == Affiliations == > > * Jean-Baptiste Onofré, Talend > > * Olivier Lamy, Talend > > = Sponsors = > > == Champion == > > * Olivier Lamy (ol...@apache.org) > > == Nominated Mentors == > > * Jim Jagielski (j...@apache.org) > > * Olivier Lamy (ol...@apache.org) > > * Jean-Baptiste Onofré (jbono...@apache.org) > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Giraph to join the incubator
ojects, Yahoo! as a company has a strong commitment to > open-source and we have several advisors that we can ask for help. > > === Homogenous Developers === > > At this time, the project is relatively young and the developers work at > only two companies (Yahoo! and Jybe). However, given the interest we have > seen in the project, we expect the diversity to improve in the near future. > > === Reliance on Salaried Developers === > > Currently Giraph is being developed by a combination of salaried and > volunteer time. We expect that other corporations will take an interest in > this project and likely contribute with salaried developers. Some > individuals will likely spend volunteer time on it as well. It is still > early in their project and we are hoping for a lot of growth. > > === Relationships with Other Apache Products === > > Giraph depends on many Apache projects: Hadoop, ZooKeeper, Log4j, Commons, > etc. It is built using Apache Maven. > > Giraph has some overlapping functionality with Apache Hama. However, there > are some significant differences. Giraph focuses on graph-based bulk > synchronous parallel (BSP) computing, while Apache Hama is more for general > purposed BSP computing. Giraph runs on the Hadoop infrastructure, while > Apache Hama uses its own computing framework. > > === An Excessive Fascination with the Apache Brand === > > The Apache brand is likely to help us find contributors, however, our > interests in Apache are primarily because the other projects that we depend > on are also Apache projects and it makes sense that all this software be > available from the same place. > > === Documentation === > > Currently we have little documentation, but several examples. We are > working on improving this situation. > > === Initial Source === > > The initial source of the code is from Yahoo! and began development in > December 2010. It is already available on GitHub at > https://github.com/aching/Giraph. > > === Source and Intellectual Property Submission Plan === > > We intend the entire code base to be licensed under the Apache License, > Version 2.0. > > === External Dependencies === > > The required dependencies are all Apache compatible licenses. The > following components with non-Apache licenses are enumerated: > * JSON – Public Domain > > === Cryptography === > > Giraph depends on secure Hadoop that can optionally use Kerberos. > > == Required Resources == > > === Mailing lists === > > * giraph-private (with moderated subscriptions) > * giraph-dev > * giraph-commits > * giraph-users > > === Subversion Directory === > > https://svn.apache.org/repos/asf/incubator/giraph > > === Issue Tracking === > > JIRA Giraph (GIRAPH) > > === Other Resources === > > Giraph has integration tests that can be run with the LocalJobRunner. > These same tests also designed to be run on a small (even single node) > Hadoop cluster. While not required at this time, it would be nice if such a > resource were available. > > === Initial Committers === > > * Avery Ching, aching at yahoo-inc dot com > * Christian Kunz, christian at jybe-inc dot com > * Owen O’Malley, owen at hortonworks dot com > * Phillip Rhodes, prhodes at apache dot org > * Hyunsik Choi, hyunsik at apache dot org > * Jakob Homan, jghoman at apache dot org > * Arun Suresh, asuresh at yahoo-inc dot com > > === Affiliations === > > * Avery Ching, Yahoo! > * Christian Kunz, Jybe > * Owen O'Malley, Hortonworks > * Phillip Rhodes, Fogbeam Labs > * Hyunsik Choi, Database Lab, Korea University > * Jakob Homan, LinkedIn > * Arun Suresh, Yahoo! > > == Sponsors == > > === Champion === > > Owen O’ Malley > > === Nominated Mentors === > > Owen O’Malley > > === Sponsoring Entity === > > Apache Incubator PMC > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Deft to join the incubator
Apache model for open-source > development. > > === Orphaned Products === > All participants are active users and contributors to open source. > One of them (Roger Schildmeijer) has experience as a contributor on > the Apache Cassandra open source project. > > === Homogeneous Developers === > Deft's initial set of committers include people that have a strong JVM > background, and are spread over a number of countries and different > employers. > > === Reliance on Salaried Developers === > None of the developers working on Deft are salaried specifically to > work on the project. The initial set of committers will continue to > use their spare time to develop Deft. > > === Relationships with Other Apache Products === > Deft has dependencies upon other Apache Projects: !HttpClient and > Maven. Also, Deft comes with a "built-in" asynchronous http client. It > could be worth time to investigate if parts of > [[http://mina.apache.org/asyncweb/client-ideas.html|Apache Mina's > async http client]] could be reused. > > === An Excessive Fascination with the Apache Brand === > The initial set of developers respect the Apache brand and feel that > Apache is the right place to establish a healthy open source > community. Deft itself will hopefully have benefits from Apache, in > terms of attracting a community and establishing a solid group of > developers. However, even if this proposal is not accepted, the > development will continue. As such, there is no need to, or reason > to, "abuse" the brand. > > == Documentation == > Infoq article about Deft: http://www.infoq.com/articles/deft-loft > > Deft documentation: http://deftserver.org/ > > Deft issue tracker and source: https://github.com/rschildmeijer/deft/ > > Deft Continuous Integration: http://savagesprout.com:8180/jenkins/ > > == External Dependencies == > The external dependencies that Deft uses are all Apache license or > compatible licenses. > > * Google Guava (http://code.google.com/p/guava-libraries/, Apache License > 2.0) > * Logback (http://logback.qos.ch, Dual license, LGPL 2.1 and EPL v1.0) > * Apache HttpClient (for unit/system tests) > (http://hc.apache.org/httpcomponents-client-ga/, Apache License 2.0) > * Ning's Async Http Client (for unit/system tests) > (https://github.com/sonatype/async-http-client, Apache License 2.0) > * JUnit (http://www.junit.org/, Common Public License - v 1.0) > * javax.activation > (http://mvnrepository.com/artifact/javax.activation/activation/1.1.1, > Common Development and Distribution License (CDDL) Version 1.0) > > == Required Resources == > === Mailing lists === > * deft-private > * deft-dev > * deft-commits > * deft-user > > === Subversion Directory === > https://svn.apache.org/repos/asf/incubator/deft > > === Issue Tracking === > JIRA DEFT (Deft) > > === Other Resources === > * Jenkins for continuos integration. > * deftserver.org domain to be transferred to ASF upon incubation. > > == Initial Committers == > * Roger Schildmeijer (schildmeijer [at] gmail com) > * Jim Petersson (jim.petersson [at] gmail com) > * Johnathan Meehan (jmeehan [at] phasevariance com) > * Nicholas Whitehead (nwhitehead [at] heliosdev org) > * Séven Le Mesle (slemesle [at] xebia fr) > > == Sponsors == > === Champion === > * Niklas Gustavsson n...@apache.org > > === Nominated Mentors === > * Emmanuel Lécharny (Apache Member) > * Mohammad Nour El-Din (Apache Member) > * Mark Struberg (Apache Memeber) > > === Sponsoring Entity === > * Apache Incubator PMC > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Oozie to join the Incubator
internal and external) in the email community > where > nearly 15 emails are exchanged per day. Furthermore, there were more than > 1500 > downloads of the Oozie binary in the last eight months from the github > site and > a large number of downloads were conducted by other companies such as > Cloudera. > Oozie has three major releases and more than 15 patch releases in the last > couple of years which further demonstrates Oozie as a very active project. > We > plan to extend and diversify this community further through Apache. > > Inexperience with Open Source > The core developers are all active users and followers of open source. > They are > already committers and contributors to the Oozie Github project. In > addition, > they are very familiar with Apache principals and philosophy for community > driven software development. > > Homogeneous Developers > The core developers are from Yahoo! as well as from several other > corporations, > including Cloudera and IBM. > > Reliance on Salaried Developers > Currently, the developers are paid to do work on Oozie. Companies like > Yahoo! > and Cloudera are invested in Oozie as the solution to the workflow > management > and scheduling problem in Hadoop clusters, and that is not likely to > change. In > addition, since workflow management is very important for most hadoop > based > data processing, non-salaried developers and researchers from various > institutes are expected to contribute to the project. > > Relationships with Other Apache Products > Oozie is based on Apache Hadoop to manage jobs created by different Apache > projects such as Hadoop, Pig, and Hive. Users of these products are > extensively > using Oozie as their workflow scheduler. > > An Excessive Fascination with the Apache Brand > We deeply respect the reputation of Apache and have had great success with > other Apache projects such as Pig and HCatalog. We are motivated to expand > and > increase the adoption and development of Oozie following Apache’s > established > open source model. We have also given reasons in the Rationale and > Alignment > sections. > > Documentation > Information about Oozie can be found at http://yahoo.github.com/oozie/. > The > following links provide more information about Oozie in open source: > >* Codebase at GitHub: https://github.com/yahoo/oozie. >* JIRA : http://oozie-jira.hadoop.developer.yahoo.net >* Continuous Integration (CI) build: > http://oozie-ci.hadoop.developer.yahoo.net/ > >* Yahoo user community: > http://tech.groups.yahoo.com/group/Oozie-users/ > Initial Source > Oozie has been under development since 2009 by a team of engineers at > Yahoo!. It > is currently hosted on GitHub under an Apache license at > https://github.com/yahoo/oozie. > > External Dependencies > The required external dependencies are all Apache License or compatible > licenses. Following the components with non-Apache licenses are > enumerated: > >* HSQLDB License: HSQLDB >* JDOM license: JDOM >* BSD: Serp >* CCDL v1: jaxb-api, ejb, JAF > NOTE: With the exception of HSQLDB and JDOM that are directly used by > Oozie, > the other listed components are transitive dependencies of other Apache > components used by Oozie. > > Cryptography > Oozie supports the Kerberos authentication mechanism to access secured > Hadoop > services. > > Required Resources > Mailing Lists >* oozie-private for private PMC discussions (with moderated > subscriptions) >* oozie-dev >* oozie-commits >* oozie-user > Subversion Directory > https://svn.apache.org/repos/asf/incubator/oozie > Issue Tracking > JIRA Oozie (OOZIE) > Other Resources > The existing code already has unit tests, so we would like a Hudson > instance > to run them whenever a new patch is submitted. This can be added after > project > creation. > > Initial Committers >* Mohammad K Islam (mislam77 at yahoo dot com) >* Angelo K Huang (angelohuang at gmail dot com) >* Mayank Bansal (mabansal at gmail dot com) >* Andreas Neumann (neunand at gmail dot com) >* Alejandro Abdelnur (tucu00 at gmail dot com) >* Chao Wang (brookwc at gmail dot com) > Affiliations >* Mohammad K Islam (Yahoo!) >* Angelo Huang (Yahoo!) >* Mayank Bansal (Yahoo!) >* Andreas Neumann (Yahoo!) >* Alejandro Abdelnur (Cloudera) >* Chao Wang (IBM) > Sponsors > Champion > Alan Gates > Nominated Mentors >* Owen O'Malley (Incubator PMC member) >* Alan Gates (Incubator PMC member) >* Christopher Douglas(Incubator PMC member) >* Devaraj Das (Hadoop PMC member) > Sponsoring EntityWe are requesting the Incubator to sponsor this project. > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [PROPOSAL] Deft for incubation
> === Orphaned Products === > All participants are active users and contributors to open source. > One of them (Roger Schildmeijer) has experience as a contributor on > the Apache Cassandra open source project. > > === Homogeneous Developers === > Deft's initial set of committers include people that have a strong JVM > background, and are spread over a number of countries and different > employers. > > === Reliance on Salaried Developers === > None of the developers working on Deft are salaried specifically to > work on the project. The initial set of committers will continue to > use their spare time to develop Deft. > > === Relationships with Other Apache Products === > Deft has dependencies upon other Apache Projects: !HttpClient and > Maven. Also, Deft comes with a "built-in" asynchronous http client. It > could be worth time to investigate if parts of > [[http://mina.apache.org/asyncweb/client-ideas.html|Apache Mina's > async http client]] could be reused. > > === An Excessive Fascination with the Apache Brand === > The initial set of developers respect the Apache brand and feel that > Apache is the right place to establish a healthy open source > community. Deft itself will hopefully have benefits from Apache, in > terms of attracting a community and establishing a solid group of > developers. However, even if this proposal is not accepted, the > development will continue. As such, there is no need to, or reason > to, "abuse" the brand. > > == Documentation == > Infoq article about Deft: http://www.infoq.com/articles/deft-loft > > Deft documentation: http://deftserver.org/ > > Deft issue tracker and source: https://github.com/rschildmeijer/deft/ > > Deft Continuous Integration: http://savagesprout.com:8180/jenkins/ > > == External Dependencies == > The external dependencies that Deft uses are all Apache license or > compatible licenses. > > * Google Guava (http://code.google.com/p/guava-libraries/, Apache License > 2.0) > * Logback (http://logback.qos.ch, Dual license, LGPL 2.1 and EPL v1.0) > * Apache HttpClient (for unit/system tests) > (http://hc.apache.org/httpcomponents-client-ga/, Apache License 2.0) > * Ning's Async Http Client (for unit/system tests) > (https://github.com/sonatype/async-http-client, Apache License 2.0) > * JUnit (http://www.junit.org/, Common Public License - v 1.0) > * javax.activation > (http://mvnrepository.com/artifact/javax.activation/activation/1.1.1, > Common Development and Distribution License (CDDL) Version 1.0) > > == Required Resources == > === Mailing lists === > * deft-private > * deft-dev > * deft-commits > * deft-user > > === Subversion Directory === > https://svn.apache.org/repos/asf/incubator/deft > > === Issue Tracking === > JIRA DEFT (Deft) > > === Other Resources === > * Jenkins for continuos integration. > * deftserver.org domain to be transferred to ASF upon incubation. > > == Initial Committers == > * Roger Schildmeijer (schildmeijer [at] gmail com) > * Jim Petersson (jim.petersson [at] gmail com) > * Johnathan Meehan (jmeehan [at] phasevariance com) > * Nicholas Whitehead (nwhitehead [at] heliosdev org) > * Séven Le Mesle (slemesle [at] xebia fr) > > == Sponsors == > === Champion === > * Niklas Gustavsson n...@apache.org > > === Nominated Mentors === > > > === Sponsoring Entity === > * Apache Incubator PMC > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Accept Bigtop for incubation
osting platforms. > For the latter, VM hosting time would be appreciated. > > = Initial Committers = > > * Alejandro Abdelnur (tucu at cloudera dot com) > * Andre Arcilla (arcilla at yahoo-inc dot com) > * Andrew Bayer (abayer at cloudera dot com) > * Konstantin Boudnik (cos at apache dot org) > * Eli Collins (eli at apache dot org) > * Travis Crawford (travis at twitter dot com) > * Bruno Mahé (bruno at cloudera dot com) > * Alan Gates (gates at apache dot org) > * Patrick Hunt (phunt at apache dot org) > * Peter Linnell (plinnell at cloudera dot com) > * Steve Loughran (stevel at apache dot org) > * Owen O'Malley (omalley at apache dot org) > * James Page (James.page at canonical dot com) > * Roman Shaposhnik (rvs at cloudera dot com) > * John Sichi (jvs at apache dot org) > * Michael Stack (stack at apache dot org) > * Tom White (tomwhite at apache dot org) > * Andrei Savu (asavu at apache dot org) > * Edward J. Yoon (edwardyoon at apache dot org) > > = Affiliations = > > * Alejandro Abdelnur, Cloudera > * Andre Arcilla, Yahoo! Inc. > * Andrew Bayer, Cloudera > * Konstantin Boudnik, free lancer > * Eli Collins, Cloudera > * Travis Crawford, Twitter > * Bruno Mahé, Cloudera > * Alan Gates, Yahoo! > * Patrick Hunt, Cloudera > * Peter Linnell, Cloudera > * Steve Loughran, HP Laboratories > * Owen O'Malley, Yahoo! > * James Page, Canonical > * Roman Shaposhnik, Cloudera > * John Sichi, Facebook > * Michael Stack, StumbleUpon > * Tom White, Cloudera > * Andrei Savu, Adobe > * Edward J. Yoon, Korea Telecom > > = Sponsors = > > == Champion == > > * Patrick Hunt > > == Nominated Mentors == > > * Patrick Hunt > * Tom White > * Owen O'Malley > * Alan Gates > * Steve Loughran > > == Sponsoring Entity == > > * Apache Incubator PMC > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [VOTE] Flume to join the Incubator.
he Maven. > > Flume users have created connectors that interact with several other Apache > projects including Apache HBase and Apache Cassandra. > > Flume's functionality has some indirect or direct overlap with the > functionality of Apache Chukwa but has several significant architectural > diffferences. Both systems can be used to collect log data to write to > hdfs. However, Chukwa's primary goals are the analytic and monitoring > aspects of a Hadoop cluster. Instead of focusing on analytics, Flume > focuses primarily upon data transport and integration with a wide set of > data sources and data destinations. Architecturally, Chukwa components > are > individually and statically configured. It also depends upon Hadoop > MapReduce for its core functionality. In contrast, Flume's components are > dynamically and centrally configured and does not depend directly upon > Hadoop MapReduce. Furthermore, Flume provides a more general model for > handling data and enables integration with projects such as Apache Hive, > data stores such as Apache HBase, Apache Cassandra and Voldemort, and > several Apache Lucene-related projects. > > == An Excessive Fascination with the Apache Brand == > > We would like Flume to become an Apache project to further foster a healthy > community of contributors and consumers around the project. Since Flume > directly interacts with many Apache Hadoop-related projects by solves an > important problem of many Hadoop users, residing in the Apache Software > Foundation will increase interaction with the larger community. > > = Documentation = > > * All Flume documentation (User Guide, Developer Guide, Cookbook, and > Windows Guide) is maintained within Flume sources and can be built > directly. > * Cloudera provides documentation specific to its distribution of Flume > at: > http://archive.cloudera.com/cdh/3/flume/ > * Flume wiki at GitHub: https://github.com/cloudera/flume/wiki > * Flume jira at Cloudera: https://issues.cloudera.org/browse/flume > > = Initial Source = > > * https://github.com/cloudera/flume/tree/ > > == Source and Intellectual Property Submission Plan == > > * The initial source is already licensed under the Apache License, Version > 2.0. https://github.com/cloudera/flume/blob/master/LICENSE > > == External Dependencies == > > The required external dependencies are all Apache License or compatible > licenses. Following components with non-Apache licenses are enumerated: > > * org.arabidopsis.ahocorasick : BSD-style > > Non-Apache build tools that are used by Flume are as follows: > > * AsciiDoc: GNU GPLv2 > * FindBugs: GNU LGPL > * Cobertura: GNU GPLv2 > * PMD : BSD-style > > == Cryptography == > > Flume uses standard APIs and tools for SSH and SSL communication where > necessary. > > = Required Resources = > > == Mailing lists == > > * flume-private (with moderated subscriptions) > * flume-dev > * flume-commits > * flume-user > > == Subversion Directory == > > https://svn.apache.org/repos/asf/incubator/flume > > == Issue Tracking == > > JIRA Flume (FLUME) > > == Other Resources == > > The existing code already has unit and integration tests so we would like a > Jenkins instance to run them whenever a new patch is submitted. This can be > added after project creation. > > = Initial Committers = > > * Andrew Bayer (abayer at cloudera dot com) > * Jonathan Hsieh (jon at cloudera dot com) > * Patrick Hunt (phunt at cloudera dot com) > * Aaron Kimball (akimball83 at gmail dot com) > * Bruce Mitchener (bruce.mitchener at gmail dot com) > * Arvind Prabhakar (arvind at cloudera dot com) > * Ahmed Radwan (ahmed at cloudera dot com) > * Henry Robinson (henry at cloudera dot com) > * Eric Sammer (esammer at cloudera dot com) > * Derek Deeter (ddeeterctrb at gmail dot com) > > = Affiliations = > > * Andrew Bayer, Cloudera > * Jonathan Hsieh, Cloudera > * Patrick Hunt, Cloudera > * Aaron Kimball, Odiago > * Bruce Mitchener, Independent > * Arvind Prabhakar, Cloudera > * Ahmed Radwan, Cloudera > * Henry Robinson, Cloudera > * Eric Sammer, Cloudera > * Derek Deeter, Intuit > > > = Sponsors = > > == Champion == > > * Nigel Daley > > == Nominated Mentors == > > * Tom White > * Nigel Daley > * Ralph Goers > * Patrick Hunt > > == Sponsoring Entity == > > * Apache Incubator PMC > > > -- > // Jonathan Hsieh (shay) > // Software Engineer, Cloudera > // j...@cloudera.com > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: [PROPOSAL] Flume for the Apache Incubator
direct overlap with the > functionality of Apache Chukwa but has several significant architectural > diffferences. Both systems can be used to collect log data to write to > hdfs. However, Chukwa's primary goals are the analytic and monitoring > aspects of a Hadoop cluster. Instead of focusing on analytics, Flume > focuses primarily upon data transport and integration with a wide set of > data sources and data destinations. Architecturally, Chukwa components > are > individually and statically configured. It also depends upon Hadoop > MapReduce for its core functionality. In contrast, Flume's components are > dynamically and centrally configured and does not depend directly upon > Hadoop MapReduce. Furthermore, Flume provides a more general model for > handling data and enables integration with projects such as Apache Hive, > data stores such as Apache HBase, Apache Cassandra and Voldemort, and > several Apache Lucene-related projects. > > == An Excessive Fascination with the Apache Brand == > > We would like Flume to become an Apache project to further foster a healthy > community of contributors and consumers around the project. Since Flume > directly interacts with many Apache Hadoop-related projects by solves an > important problem of many Hadoop users, residing in the the Apache Software > Foundation will increase interaction with the larger community. > > = Documentation = > > * All Flume documentation (User Guide, Developer Guide, Cookbook, and > Windows Guide) is maintained within Flume sources and can be built > directly. > * Cloudera provides documentation specific to its distribution of Flume > at: > http://archive.cloudera.com/cdh/3/flume/ > * Flume wiki at GitHub: https://github.com/cloudera/flume/wiki > * Flume jira at Cloudera: https://issues.cloudera.org/browse/flume > > = Initial Source = > > * https://github.com/cloudera/flume/tree/ > > == Source and Intellectual Property Submission Plan == > > * The initial source is already licensed under the Apache License, Version > 2.0. https://github.com/cloudera/flume/blob/master/LICENSE > > == External Dependencies == > > The required external dependencies are all Apache License or compatible > licenses. Following components with non-Apache licenses are enumerated: > > * org.arabidopsis.ahocorasick : BSD-style > > Non-Apache build tools that are used by Flume are as follows: > > * AsciiDoc: GNU GPLv2 > * FindBugs: GNU LGPL > * Cobertura: GNU GPLv2 > * PMD : BSD-style > > == Cryptography == > > Flume uses standard APIs and tools for SSH and SSL communication where > necessary. > > = Required Resources = > > == Mailing lists == > > * flume-private (with moderated subscriptions) > * flume-dev > * flume-commits > * flume-user > > == Subversion Directory == > > https://svn.apache.org/repos/asf/incubator/flume > > == Issue Tracking == > > JIRA Flume (FLUME) > > == Other Resources == > > The existing code already has unit and integration tests so we would like a > Hudson instance to run them whenever a new patch is submitted. This can be > added after project creation. > > = Initial Committers = > > * Andrew Bayer (abayer at cloudera dot com) > * Jonathan Hsieh (jon at cloudera dot com) > * Aaron Kimball (akimball83 at gmail dot com) > * Bruce Mitchener (bruce.mitchener at gmail dot com) > * Arvind Prabhakar (arvind at cloudera dot com) > * Ahmed Radwan (ahmed at cloudera dot com) > * Henry Robinson (henry at cloudera dot com) > * Eric Sammer (esammer at cloudera dot com) > > = Affiliations = > > * Andrew Bayer, Cloudera > * Jonathan Hsieh, Cloudera > * Aaron Kimball, Odiago > * Bruce Mitchener, Independent > * Arvind Prabhakar, Cloudera > * Ahmed Radwan, Cloudera > * Henry Robinson, Cloudera > * Eric Sammer, Cloudera > > > = Sponsors = > > == Champion == > > * Nigel Daley > > == Nominated Mentors == > > * Tom White > * Nigel Daley > > == Sponsoring Entity == > > * Apache Incubator PMC > > > -- > // Jonathan Hsieh (shay) > // Software Engineer, Cloudera > // j...@cloudera.com > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: Making Daffodil Replicator an Open Source : Suggestion
Dear members, Please find attached our thoughts. >I find this rather confusing. One of the criteria for exiting > incubation is a *diverse* set of committers - i.e. an appropriate > proportion of Daffodil "for-pay" developers but also non-Daffodil > folks. If your idea of the original number of committers (coming with > the donation of the project) varies between 3 and 30, I'm rather > suspicious about who you consider to be a committer. Having no idea of > the size of your codebase and your operations, I can tell you that the > usual initial set of committers of other projects hardly ever surpasses > 5 to 8 folks, and the rest will need to be voted in using common ASF > procedures. You as a commercial entity have no control over this other > than what is to be expected in a community project, and the Incubator > will check whether you are following ASF guidelines. Noel, I think that there has been some confusion. The number and profile of committers will be decided by ASF. All we can assure is that we will try to have as many developers / contributors working on the project. Some of them might be on a 'paid' basis, while some might come from our alumni, which currently numbers over 400. We dont know (as of now) how many there will be, however all we can say is that we will try and motivate as many people as we can. > To give you an idea about what is decent to add to an ASF distribution, > have a look at the Cocoon CREDITS: > http://cvs.apache.org/viewcvs.cgi/cocoon/trunk/CREDITS.txt? > rev=30946&root=Apache-SVN&view=markup Thanks for the above info. > Apart from such a file, it will be hard to find other attributions in > the Cocoon codebase linkable to a specific single commercial entity, > since having these would carry a false sense of ownership over the code > or project. Of course, our license permits repackaging and > redistribution, so you could always redistribute a more commercially > labeled version of the code through your own website, perhaps with some > value-added services, bearing in mind that the ASF license requires you > to link back to us as the originators of the code. I understand that this would mean that the ownership of Replicator would lie with ASF, and Daffodil (like anyone else) would be free to 'redistribute a more commercially labeled version of the code through your own website, perhaps with some value-added services, bearing in mind that the ASF license requires you to link back to us as the originators of the code.' Is my understanding correct? > Basically, Daffodil becomes Apache Daffodil, and it is up to you to > build a business model around this publicly available ASF project, but > the ASF will not serve as a "daffodil.org" entity alongside your > "daffodil.com". I hope I'm making myself clear here. You *will* be > relinquishing control up to the level that you carefully need to check > whether this is what you want. Point taken. > Another common issue is the inclusion of non-ASL licensed dependencies. > The ASF currently has a policy of not redistributing LGPL/GPL-licensed > code. Does your project depends on such code? Also, is there any way to > assess what you are planning to donate? No, our Replicator does not incorporate *any* LGPL/GPL-licensed code. We would be more than willing to provide you with a link on our website, which would give you access to the Replicator code. > Lastly, I would seriously recommend you to approach the db.apache.org > project as well, which might help you to recruit some sponsors and/or > interested developers. Thanks a lot for your advice Noel. We will be looking to the db.apache.org project for sponsors and / or developers. We will also be starting a fresh thread on this address, to understand what could / should / would be the business model for Daffodil Software (based upon a possible commercial fork of Replicator.) Best, Ashish > HTH, > > > -- > Steven Noelshttp://outerthought.org/ > Outerthought - Open Source Java & XMLAn Orixo Member > Read my weblog athttp://blogs.cocoondev.org/stevenn/ > stevenn at outerthought.orgstevenn at apache.org > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE:Making Daffodil Replicator an Open Source : Suggestion
of the code and is serious about > transferring power over the project from itself to the open-source > community that may form around the project. Of course if your company > owners are simply motivated by goodwill to the world and willing to pay > developers to work on something with no expectation of any return, that > is fine too - just not so common :-) Everything 'open' does have some goodwill associated with it, however, as explained above, there are some practical reasons behind the move too. > Having good business reasons for engaging in open-source projects is > nothing to be concerned about. IBM, Sun, BEA and others have made, and > continue to make, major contributions to the ASF, and I don't think > anyone regards them as charities. > > > If you are still interested in offering this code for adoption as an ASF > project (and I hope you are), I would suggest that you draft a new email > describing the features of Daffodil Replicator (esp. its cross-database > support) and include info on your motivations for this project, then > email this list again. It's unfortunate that no-one other than me has > responded so far, but I think there *will* be interest in this. We are still very much interested in offering Replicator to ASF, and I will be drafting the said mail asap. Warm Regards, Ashish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE:Making Daffodil Replicator an Open Source : Suggestion
Hi, Thanks for the informative mail. It did go a long way in bettering my understanding with regards to The Apache Software Foundation. However, based on your feedback, the following come to my mind: >Firstly, the code you are considering releasing under an open-source >licence is an add-on to a proprietory product. The ASF is unlikely to >consider adopting that kind of project.. 1. Daffodil Replicator is not an add-on to Daffodil DB (our Java database). It is a standalone product developed in-house by Daffodil Software. Daffodil Replicator use the standard JDBC driver interface to interact with databases. It is not interacting with any Daffodil DB's internal API. 2. With regards to your comment about the 'group of developers' and the fact that the 'code you are considering releasing can only be used with a proprietary database', the following: Replicator can be used by the following databases - SQL-Server, Oracle, Daffodil DB. (Note: These three databases have been tested with Replicator. I don't see why Replicator cannot be used with ALL others. However, testing needs to be done on the same.) Also, we can commit 20 - 30 developers from our talent pool, who can contribute from Day 1. Moreover, our forum (http://www.daffodildb.com:8080/forum) can be a good place to build up a pool of contributors. 3. Regarding Cloudscape, we are not sure if (or not) it provides support of Triggers and Multiple statements procedure (like PL/SQL in Oracle). If it does, we can ensure compatibility. (We would need some testing to be done, but that's not an issue.) On the other hand, if support of the said features doesn't exist, we can create the same. However, this would need access to the Derby source code. 4. Regarding our paradigm and business-model, we can (at this point of time) say that the objective for going the 'open source' way is singular: To build a robust product and a robust brand, at the same time leveraging the advantages of Open Source. Regards, Ashish Srivastava www.daffodildb.com PS: Please mark a CC to me for reply of this mail (although I subscribed the mailing list but I am unable to receive some mails) Subject: Making Daffodil Replicator an Open Source : Suggestion From: Simon Kitching <[EMAIL PROTECTED]> Content-Type: text/plain Date: Sat, 07 Aug 2004 13:10:17 +1200 On Sat, 2004-08-07 at 05:20, Nicola Ken Barozzi wrote: > Ashish Srivastava wrote: > > Hi, > > > > We are a product based company named Daffodil Software Ltd, based in > > India. We have developed many good products using JAVA out of which our > > two premium product Daffodil DB (an RDBMS) and Daffodil Replicator > > (database utility software) is largely accepted by world software > > community. > > > > We are planning to make our Daffodil Replicator an open source project. > > > > How can we make it with www.apache.org please let us know how we have to > > proceed. > > > > I visited at http://incubator.apache.org but unable to find the answer > > how to proceed in order to make our product open source. > > I'm cross-posting to lists where there might be interest in helping you > out on this. > > > www.daffodildb.com Hi Ashish, The following is just my personal opinion, as a member of the ASF (Apache Software Foundation); I am not speaking on behalf of the ASF. I think it is great that you are considering releasing some of your code under an open-source licence. I am sure there are a number of people that are willing to offer advice on the process of releasing your code as open-source. And if you do this, you are certainly welcome to reuse the Apache Public License legal document as the base for the license terms you release your code under; the ASF and its legal advisors deliberately designed the license in a way that makes it easy for non-ASF-hosted projects to use. However if you are suggesting that the code you release may be hosted and maintained by the Apache Software Foundation, I personally think this is unlikely to happen. Firstly, the code you are considering releasing under an open-source licence is an add-on to a proprietory product. The ASF is unlikely to consider adopting that kind of project. This doesn't mean that making the code open-source is a bad idea, it's just something that the ASF usually avoids being involved with. Secondly when the ASF adopts existing code, the provider of the code is expected to show evidence that there is a group of developers willing to continue maintenance and development of the code in the future. Apache doesn't want to end up hosting lots of code with no associated developers. Given that the code you are considering releasing can only be used with a proprietory database which does not have a large market share, I think this will b
RE: Making Daffodil Replicator an Open Source : Suggestion
Hi Brian, Thanks for the encouraging words! We at Daffodil Software are keen on taking the OS route and have planned to donate our Replicator product / tool as the first step. The source can be made available to you via our website. I would be sending you the login details regarding the same at the earliest. As of now, no one at Daffodil Software is involved with ASF hopefully all that will change soon. We would be more than happy for you to 'champion' the proposal, and also decide upon the right 'sponsor' for the same. Is there a sample proposal someone at ASF could send across, so that we could use it as a template for our proposal? Eagerly awaiting your reply. Regards, Ashish Srivastava www.daffodildb.com -Original Message- From: Brian McCallister [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 10, 2004 4:41 PM To: [EMAIL PROTECTED] Subject: Re: Making Daffodil Replicator an Open Source : Suggestion This sounds like a great tool! Offline synching for any JDBC compliant database with triggers and procedures is good stuff. Are the sources available anywhere right now? The general steps to enter incubation are described in the document: http://incubator.apache.org/incubation/Incubation_Policy.html Is anyone involved with the Daffodil Replicator already involved with the ASF? I ask as the next step is to generate a formal proposal, which entails a nomination my an ASF member ( http://www.apache.org/foundation/how-it-works.html#roles ) and deciding on a sponsor (either the incubator PMC, the board, or an existing TLP -- Daffodil sounds like it may fit well into the db.apache.org project, I invite you to bring up conversation on [EMAIL PROTECTED]). -Brian On Aug 10, 2004, at 3:30 AM, Ashish Srivastava wrote: > We have decided to make Daffodil Replicator an open source with Apache. > We have a team of 75 professionals who developed Daffodil DB and > Daffodil Replicator. And will continue working with same after making > it > open source. > > Any suggestion or comment? > > Project Description: > > Daffodil Replicator is a powerful data replication utility which allows > the users to work off line and can merge the data when get online. > > Daffodil Replicator is platform independent software based on JDBC > driver. Any Database which supports JDBC Driver with Triggers and > procedure can take part in replication either at publication server or > on subscription side. > > Important links: > > Documentation on Daffodil Replicator is available at: > http://www.daffodildb.com/pdf/daffodil_replicator.pdf > > Evaluation version of Daffodil Replicator is available at: > http://www.daffodildb.com:8080/eval/filldetails.jsp > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Making Daffodil Replicator an Open Source : Suggestion
We have decided to make Daffodil Replicator an open source with Apache. We have a team of 75 professionals who developed Daffodil DB and Daffodil Replicator. And will continue working with same after making it open source. Any suggestion or comment? Project Description: Daffodil Replicator is a powerful data replication utility which allows the users to work off line and can merge the data when get online. Daffodil Replicator is platform independent software based on JDBC driver. Any Database which supports JDBC Driver with Triggers and procedure can take part in replication either at publication server or on subscription side. Important links: Documentation on Daffodil Replicator is available at: http://www.daffodildb.com/pdf/daffodil_replicator.pdf Evaluation version of Daffodil Replicator is available at: http://www.daffodildb.com:8080/eval/filldetails.jsp
RE: Making Daffodil Replicator an Open Source : Suggestion
Hi Noel, >"Replicator integrates impeccably with all .. JDBC drivers" Daffodil Replicator is a tool which works on databases to create publication, subscription and merging the replicated data. To interact with databases Daffodil Replicator uses JDBC driver interface and it also assumes that base database supports following: * All basic data types * Primary key support * Triggers with: * Provision of getting old and new values * Row level triggers or any alternate way to achieve row level feature (as given in SQL-Server) * Auto increment field support or sequence support Daffodil Replicator is compatible to SQL-Server, Oracle and Daffodil DB. Providing support with additional database a very small task, we just only need to override the methods of one generic class which maps the datatypes and SQL syntax. We are very interested in making Daffodil Replicator compatible to Axiom and Derby databases. The developer community has shown great interest in this product which we are able to gauge from the high ratings given by well know software index web sites like www.jars.com <http://www.jars.com/> , Zaurus <http://www.killefiz.de/zaurus/> Software Index etc. You can download the current version of Daffodil Replicator from http://www.daffodildb.com:8080/eval/filldetails.jsp Regards, Ashish Srivastava www.daffodildb.com <http://www.daffodildb.com/> -Original Message- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: Monday, August 09, 2004 4:33 AM To: [EMAIL PROTECTED] Cc: Ashish Srivastava Subject: RE: Making Daffodil Replicator an Open Source : Suggestion Ashish Srivastava wrote: > We are planning to make our Daffodil Replicator an open source project. I have read the information at http://www.daffodildb.com/dbreplicator.php , but it is unclear from "Replicator integrates impeccably with all Daffodil database products as well as with selected third-party databases that provide JDBC drivers" to what extent Daffodil Replicator would work with other databases. If you are interested in contributing to replication that would work with Axion and Derby, please let us know. The key issue, however, is community interest. We would want to see interest from within the ASF, or an existing community outside the ASF. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Making Daffodil Replicator an Open Source : Suggestion
Hi, We are a product based company named Daffodil Software Ltd, based in India. We have developed many good products using JAVA out of which our two premium product Daffodil DB (an RDBMS) and Daffodil Replicator (database utility software) is largely accepted by world software community. We are planning to make our Daffodil Replicator an open source project. How can we make it with www.apache.org please let us know how we have to proceed. I visited at http://incubator.apache.org but unable to find the answer how to proceed in order to make our product open source. So I am mailing you. I also want to join apache as member. Thanks in anticipation Regards, Ashish Srivastava www.daffodildb.com -Original Message- From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED] Sent: Friday, August 06, 2004 1:30 PM To: Ashish Srivastava Cc: [EMAIL PROTECTED] Subject: Re: Making Daffodil Replicator an Open Source : Suggestion Ashish Srivastava wrote: > Hi, > > We are a product based company named Daffodil Software Ltd, based in > India. We have developed many good products using JAVA out of which our > two premium product Daffodil DB (an RDBMS) and Daffodil Replicator > (database utility software) is largely accepted by world software community. > > We are planning to make our Daffodil Replicator an open source project. > How can we make it with _www.apache.org_ <http://www.apache.org> , > please let us know how we have to proceed. New projects that come at Apache go through the Incubator. You can find some information on the website: http://incubator.apache.org/ If you have further questions, feel free to contact the Incubator on the general mailing list: [EMAIL PROTECTED] To subscribe send a mail to: [EMAIL PROTECTED] -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Geronimo
Hello, Fist of all nice to see Apache getting started with a J2EE initiative. Let me introduce myself as a 6 year java technology veteran, actively involved into commercial consultation services and personal hobby developments. I would like to be part of Geronimo initiative. Where do I get further details, such as current status of the project, propsed architecture, task list etc. Best regards, Ashish Gokhale
