Re: [VOTE] Release of Apache Allura 1.1.0 incubating
NOTICE and LICENSE looks good. Hash and Sig files are good. +1 (binding) - Henry On Wed, Feb 12, 2014 at 5:06 PM, Dave Brondsema d...@brondsema.net wrote: Hi everyone, This is a call for a vote on Apache Allura 1.1.0 incubating. This will be our second release in the incubator. Allura is forge software for the development of software projects, including source control systems, issue tracking, discussion, wiki, and other software project management tools. A vote was held on developer mailing list and it passed with 7 +1's, and no -1's or +0's. 1 vote was from an IPMC member (me). Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52F15D4C.7060906%40brondsema.net%3E Result thread: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201402.mbox/%3C52FBA8A9.502%40brondsema.net%3E Source tarball, signature and checksums are available at: https://dist.apache.org/repos/dist/dev/incubator/allura/ Checksums: MD5:ea72b33323dc8c85ad26d08de4bbc534 SHA1: 170729db7c7b26fc3244293bc0a37989121d3973 SHA512: 24b65e731d2ec5df33ab4959b0edd72ec5fee58ae5ce704b10ef45ecc07259357a645d4989935423a6be7d4f1add8b2512578b9b2133ac5059f6d3c6d7235934 The KEYS file can be found at: http://www.apache.org/dist/incubator/allura/KEYS The release has been signed with key (9BB3CE70): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x56F0526F9BB3CE70 Source corresponding to this release can be found at: Commit: a2bc6726d63298638bacf4d02e697e92aaee0bf4 Tag:asf_release_1.1.0 Browse: https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.1.0 The RAT report is available at: https://sourceforge.net/p/allura/pastebin/52f15c143e5e833783530b74 Vote will be open for at least 72 hours: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks! -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating
Hi Andrew, Are you saying it is ok to contain compiled executed binaries if they were signed? There had been long discussion in general@ list about what should be contained in release artifacts (with 0.8.1 Spark release) and I believe the conclusion was to avoid executable binaries in the source release artifacts. - Henry On Mon, Feb 24, 2014 at 10:11 AM, Andrew Purtell apurt...@apache.org wrote: Hi Sebb, On Sat, Feb 22, 2014 at 2:19 AM, sebb seb...@gmail.com wrote: I've had a quick look at the (sole) archive, and it contains both source and compiled jars. Although it is OK to release convenience binaries, there must be a source only release, as that is the ASF mission - to release open source. The what must every release contain doc says: Every ASF release *must* contain a source package, which must be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools. The source package must be cryptographically signed http://www.apache.org/dev/release-signing.html by the Release Manager with a detached signature; and that package together with its signature must be tested prior to voting +1 for release. We can mentor the podling to produce a separate source only tarball, but this might be a point of confusion, because the candidate tarball here conforms to the above language, I have personally built and tested this release from the properly signed tarball. It is a source tarball also containing compiled binaries. -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Knox from the Incubator
+1 (binding) Good luck guys! - Henry On Thu, Feb 6, 2014 at 8:49 PM, Chris Mattmann mattm...@apache.org wrote: Hi Everyone, The Apache Knox Incubating podling has VOTEd to graduate from the Incubator. The community VOTE has passed below with the provided tallies. The graduation resolution draft is pasted below. We welcome your VOTE'ing on Knox's graduation from the Incubator. I will leave this VOTE open for at least 72 hours. [ ] +1 Recommend graduation of Apache Knox from the Incubator. [ ] +0 Don't care. [ ] -1 Don't recommend graduation of Apache Knox from the Incubator because.. Thanks for your VOTE! Cheers, Chris -Original Message- From: Chris Mattmann mattm...@apache.org Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Date: Thursday, February 6, 2014 8:38 PM To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: [RESULT] [VOTE] Graduation of Apache Knox from the Incubator Hi Guys, Sorry it took forever for me to close this VOTE! :) Here are the tallies: +1 Chris Mattmann* Alan Gates* Larry McCay Dilli Arumugam Kevin Minder * - indicates IPMC This VOTE has passed. I'll now take it to general@incubator.apache.org. Thanks for VOTE'ing! Cheers, Chris -Original Message- From: Chris Mattmann mattm...@apache.org Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Date: Thursday, December 19, 2013 2:41 PM To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: [VOTE] Graduation of Apache Knox from the Incubator Hi Folks, Time to VOTE on the following resolution to graduate Apache Knox from the Apache Incubator. Here's a draft resolution to VOTE on (with Kevin listed as PMC chair). I'll leave the VOTE open for the next week. If all goes well here, I'll take it to general@incubator.a.o and if all goes well there, we'll take it to the Apache board for consideration in their January 2014 board meeting. Thanks! [ ] +1 Graduate Apache Knox from the Incubator [ ] +0 Don't care. [ ] -1 Don't graduate Apache Knox from the Incubator because.. Thanks and here's my enthusiastic +1! Cheers, Chris --draft resolution 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 secure access for Apache Hadoop clusters. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Knox Project be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Knox Project be and hereby is responsible for the creation and maintenance of software related to secure access for Apache Hadoop clusters; and be it further RESOLVED, that the office of Vice President, Apache Knox, 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 Knox Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Knox 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 Knox Project: * Christopher Douglas cdoug...@apache.org * Chris Mattmann mattm...@apache.org * Devaraj Das d...@apache.org * Dilli Dorai dillido...@apache.org * Alan Gates ga...@apache.org * John Speidelkminder jspei...@apache.org * Kevin Minder kmin...@apache.org * Larry McCay lmc...@apache.org * Mahadev Konar maha...@apache.org * Owen O'Malley omal...@apache.org * Sumit Mohanty smoha...@apache.org * Tom Beerbower tbeerbo...@apache.org * Thomas White tomwh...@apache.org * Venkatesh Seetharam venkat...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kevin Minder be appointed to the office of Vice President, Apache Knox, 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 Apache Knox Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Knox podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Knox 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For
Re: Github pull request hooks
W00t! Looks like it is working :) Thanks Jake and Daniel. - Henry On Friday, February 7, 2014, Jake Farrell jfarr...@apache.org wrote: I just wanted to follow up on my previous comments about the Github webhooks not posting comments, Daniel Gruno and I have been debugging the Github webhooks we had in place to send pull request notifications and we have fixed it so comments for issues and pull requests will now go to the dev@ lists. If anyone replies to this mail it will stay on the dev@ list. -Jake NOTE: This still remains a project/PMC responsibility to ensure communication is recorded as this is coming from a 3rd party we do not control. Communications should be encouraged to occur on our mailing lists. We (infra) are working to make things easier and allow for better integrations and are always open to anyone wanting to help contribute to these efforts.
Re: Github pull request hooks
Hi Jake, Looks like all the emails from the PR has the same subject: [GitHub] incubator-spark pull request: Is there a way to get the Title of the pull request included in the Subject line? Thanks, Henry On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell jfarr...@apache.org wrote: I just wanted to follow up on my previous comments about the Github webhooks not posting comments, Daniel Gruno and I have been debugging the Github webhooks we had in place to send pull request notifications and we have fixed it so comments for issues and pull requests will now go to the dev@ lists. If anyone replies to this mail it will stay on the dev@ list. -Jake NOTE: This still remains a project/PMC responsibility to ensure communication is recorded as this is coming from a 3rd party we do not control. Communications should be encouraged to occur on our mailing lists. We (infra) are working to make things easier and allow for better integrations and are always open to anyone wanting to help contribute to these efforts. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Github pull request hooks
Ah looks like the missing PR title only happen for the emails describing comments from the Github pull requests. - Henry On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra henry.sapu...@gmail.com wrote: Hi Jake, Looks like all the emails from the PR has the same subject: [GitHub] incubator-spark pull request: Is there a way to get the Title of the pull request included in the Subject line? Thanks, Henry On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell jfarr...@apache.org wrote: I just wanted to follow up on my previous comments about the Github webhooks not posting comments, Daniel Gruno and I have been debugging the Github webhooks we had in place to send pull request notifications and we have fixed it so comments for issues and pull requests will now go to the dev@ lists. If anyone replies to this mail it will stay on the dev@ list. -Jake NOTE: This still remains a project/PMC responsibility to ensure communication is recorded as this is coming from a 3rd party we do not control. Communications should be encouraged to occur on our mailing lists. We (infra) are working to make things easier and allow for better integrations and are always open to anyone wanting to help contribute to these efforts. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Spark from the Incubator
HI Marvin, The automatic email to dev@ list for github mirror PR, does it happen for all ASF github mirrors or each podling need to do some setup to make it work? - Henry On Thu, Feb 6, 2014 at 9:53 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce jo...@apache.org wrote: How is doing a review on Github any different than doing a review on Review Board? One is captured to Apache controlled channels and the other is not. If there's concern that work on Github isn't being adequately mirrored on the mailing lists then that sounds like an Infra problem to me. It's not an Infra problem. It's the problem of any PMC which fails to ensure that all of its communications are properly archived. If anyone here is interested in contributing towards this feature, I encourage you to subscribe to the infrastructure-dev@apache list. I also encourage everyone to ponder carefully: * How to ensure that no information is lost when capturing communications in GitHub channels through notifications to our dev lists. * The impact of adding GitHub integration features on long-term ASF Infra labor costs. There are plenty of hooks [1] that makes this easy to do and, if I'm not mistaken, pull requests through Github are already supposed to mail dev@. That's right. I've actually worked on the specific hook that does that[1][2]. I would assume that any comment on them should as well. Why would you assume that GitHub comments are being mailed to dev lists? They are not. Every Apache PMC member is tasked with oversight of their project, and that includes ensuring that all decisions happen on the dev list and are properly documented. It is not enough to assume that Infra is taking care of archival -- ensuring that the archival actually happens is the PMC's direct responsibility. Marvin Humphrey [1] https://issues.apache.org/jira/browse/INFRA-4651 [2] Thread on legal-discuss@apache: http://s.apache.org/Nhx - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Spark from the Incubator
HI David Nalley, Thank you for your comment and concern, really appreciate it. As Patrick had mentioned in his reply, this is not a persistent problem. The reminder I sent was about particular topic which could be interpreted as design or roadmap topic rather than review for a patch. Rather than reminding an individual or two involved in the discussion, I decided to send email to dev@ list to show by example the open and transparent discussions the ASF way. Hope this gives some more clarification about the state of the podling embracing the ASF way. - Henry On Thu, Feb 6, 2014 at 9:19 PM, Patrick Wendell pwend...@gmail.com wrote: Hey All - chiming in as an active Spark committer. The part that disturbs me is that after the vote passed in the community, and came to the IPMC a mentor is still having to remind folks that things like strategy and roadmap discussions need to happen on the mailing list. That's a pretty foundational concept in my mind for an Apache project. Henry gave a reminder on the mailing list not because it's a persistent problem but because it never explicitly came up prior to this. We use github for review comments and in one case this week there was a brief discussion that could be interpreted as roadmap - so Henry just gave a reminder not to do that. I can't imagine why any project would *want* to use github review comments for long term roadmap discussion... it's a terrible medium for that anyways! We have a very active developer list and that is where these discussions take place. The missing account issues are somewhat troubling, but also not really within the purview of the podling to fix either; though I find it odd that people committed to the podling (and many initial committers) haven't asked for their Apache account or needed to use it. This is because those people have still contributed a lot of code via other commiters who merge so it's not an immediate urgency. For perspective I am a committer on two other ASF projects but I've never personally committed code to either - I do it through the more active committers who basically spend all their time merging patches. A few of the initial commiters are not currently active on the project; they've made major contributions over the last few years of development and are committers in recognition of those contributions (see above). Popping up a level. We are happy to have github discussions forward to either our dev- list or a reviews- list or something like that (I beleive Matei is setting that up now). If IPCM folks want to debate whether we should *have* to do that, it seems sensible to fork a thread and discuss elsewhere. If IPMC folks want to debate whether github should be allowed at all, I also think it's better discussed outside of this graduation thread. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Spark from the Incubator
Hi Craig, I am one of the mentors for Spark podling. Currently the Spark operates via the ASF Github mirror to do review and commit requests. The podling uses the Github pull requests mechanism, please see how to contribute page [1] By definition ASF committers are people who CAN commit code to the repository and since currently the Spark podling uses Github Pull Request flow that allow committers to push to his/her own forked repo and allow other people to merge the code to Spark ASF git repository. However, there a mechanism to preserve the actual commit comment and credit to the original individual whom commit the code to his/her own copy of the source repository. From traditional code commit like with SVN the flow seem to make them like outsider but they have been contributing to the podling with the knowledge and participations as committers Love to chat or explain more to you about it if you need more clarification. Hope this helps to ease your concern about Spark podling readiness to become TLP. Thanks, Henry [1] https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark On Wed, Feb 5, 2014 at 9:05 AM, Craig L Russell craig.russ...@oracle.com wrote: Hi Matei, On Feb 4, 2014, at 12:26 PM, Matei Zaharia wrote: Hi Craig, Thanks for the list, I’m following up with these folks to get them accounts. I think some people filed an ICLA but never received an account and were thus never added to the repo. This is a significant failure of the leadership of this project to request accounts. The project status on http://incubator.apache.org/projects/spark.html says that all active committers have submitted a contributors agreement as of a week ago. The project started seven months ago. Setting up the project, filing ICLAs, and getting accounts for committers is supposed to be part of the initial activities, not a graduation exercise. A couple of questions: - What do you mean by “does not appear to be a committer” — that they weren’t added to the repo? They were not given credentials to commit to the repo. All of these individuals have contributed code, but it was merged by someone else. This is a major issue. At Apache, committers update the repo with their own code. Occasionally, they commit code on behalf of others but this should be a rare exception, such as a person from the outside contributing a patch or two. If committers on the project are routinely committing patches on behalf of other active members of the project, there is something fundamentally wrong with the leadership of the project. Perhaps it is a feature of using git that it's so easy to write code, create a pull request, and have someone else do the easy job of merging. - Andrew Xia is listed as having an ICLA on file here: http://people.apache.org/committer-index.html Yes, I missed this. Andrew's public name is different. There are some folks on the proposed PMC list who do not appear to have been active on the mail lists, which are the life blood of a project. I'm still -1 on this project graduating without demonstrated understanding of how Apache projects work. Craig Matei On Feb 4, 2014, at 8:12 AM, Craig L Russell craig.russ...@oracle.com wrote: -1 for this resolution as written. Some of the proposed PMC members have filed ICLAs but are not committers; some have not even filed ICLAs; some appear to have been part of the original proposal but have not contributed to the project during incubation. Regards, Craig On Jan 31, 2014, at 6:04 PM, Matei Zaharia wrote: RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Spark Project: * Mosharaf Chowdhury mosha...@apache.org * Jason Dai jason...@apache.org * Tathagata Das t...@eecs.berkeley.edu This person does not appear to be a committer. * Ankur Dave ankurd...@gmail.com This person does not appear to be a committer. * Aaron Davidson aarondavid...@berkeley.edu This person does not appear to be a committer. * Thomas Dudziak to...@apache.org * Robert Evans bo...@apache.org * Thomas Graves tgra...@apache.org * Andy Konwinski and...@apache.org * Stephen Haberman steph...@apache.org * Mark Hamstra markhams...@apache.org * Shane Huang shane_hu...@apache.org * Ryan LeCompte ryanlecom...@apache.org * Haoyuan Li haoy...@apache.org * Sean McNamara mcnam...@apache.org * Mridul Muralidharam mrid...@yahoo-inc.com This person does not appear to be a committer. * Kay Ousterhout k...@eecs.berkeley.edu There is no ICLA on file for this person. * Nick Pentreath mln...@apache.org * Imran Rashid im...@quantifind.com This person does not appear to be a committer. * Charles Reiss wog...@apache.org * Josh Rosen joshro...@apache.org * Prashant Sharma prash...@apache.org * Ram Sriharsha harsh...@yahoo-inc.com There is no ICLA on file for this person. * Shivaram Venkataraman
Re: [VOTE] Graduation of Apache Spark from the Incubator
Thanks so much to sebb, Craig, Bertrand for catching the issue. Will work with Apache Spark PPMCs to resolve it. - Henry On Wed, Feb 5, 2014 at 1:34 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Feb 4, 2014 at 5:12 PM, Craig L Russell craig.russ...@oracle.com wrote: ...Some of the proposed PMC members have filed ICLAs but are not committers; some have not even filed ICLAs; some appear to have been part of the original proposal but have not contributed to the project during incubation... Ouch...thanks for catching that, Craig. Here's my -1 as well, we'll need to see an updated list of PMC members consisting of people who have demonstrated their commitment to the project. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Change of IPMC Chair
Congrats Roman! On Monday, February 3, 2014, Marvin Humphrey mar...@rectangular.com wrote: Greetings, Congratulations to Roman Shaposhnik! The Incubator PMC has voted to recommend Roman as our next Chair in a resolution to the Board next week. My wholehearted thanks go out to everyone who has contributed to a podling or otherwise worked to advance the Incubator during my tenure as Chair. I look forward to supporting Roman and to continued collaboration with you all, both here in the Incubator and elsewhere. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:;
Re: Incubator ApacheCon presentations
I think one of the topics to be covered is about quality. Perception in incubator that it is a low quality so some podlings want to graduate ASAP without learning fully the ropes of being ASF community. - Henry On Fri, Jan 31, 2014 at 11:46 AM, Suresh Marru sma...@apache.org wrote: These are great topics Marvin, looking foreword for them. Hi All, I am planning to propose a talk targeted for recently graduated incubator podlings. Along with sharing my own experiences, I want to highlight importance of giving back to IPMC by hanging around and helping future podlings, and most importantly some of the pitfalls to avoid once we move into self-governance mode. Any volunteers to join in co-presenting this talk or contributing to the content? We don’t need to overwhelm the mailing list and choose to directly email me at smarru at a.o Thanks, Suresh On Jan 29, 2014, at 8:04 PM, Marvin Humphrey mar...@rectangular.com wrote: Greets, I'm planning to propose two presentations for ApacheCon Denver: one on releases, and one overview of the Incubator. _Releasing Apache Software_ This presentation will explore technical, procedural, legal and cultural aspects of releasing Apache software; the distinction between releasing and distributing; the relationship between Apache's source releases and binary artifacts; evolving consensus as to what liberties may be taken with incubating releases; and how codifying the release process helps to fortify the the Apache brand. Audience: Apache committers Level: intermediate _Getting the Most Out of the Incubator_ Knowing what to expect from the incubation process is of great benefit for both contributors to projects currently under incubation and those considering bringing a project to Apache. We'll cover the major stages of incubation, the institutions and roles that incubating projects must interact with, and how to get the most out for what you put in. Audience: Anyone with an interest in the Incubator. Level: beginner Thoughts, feedback? Anybody else submitting talks? Marvin Humphrey - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]
+1 (binding) On Fri, Jan 31, 2014 at 4:42 PM, Terence Yim cht...@gmail.com wrote: Hi all, This is to call for a vote for release of Apache Twill v0.1.0-incubating. This will be the first incubator release for Apache Twill. Vote on twill-dev: http://s.apache.org/Rsy Result on vote on twill-dev: http://s.apache.org/KMR The tag to be voted upon is v0.1.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating Please vote on releasing this package as Apache Twill 0.1.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.1.0-incubating [ ] -1 Do not release this package because ... Thanks, Apache Twill Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]
Looks like it is updated already. Missing one section: Subscribe all Mentors on the pmc and general lists. - Henry On Sat, Feb 1, 2014 at 2:02 PM, Terence Yim cht...@gmail.com wrote: Hi Patrick, I've updated the status page yesterday with dates (both Incubation status reports and Project setup section). Is it not update enough? Thanks, Terence On Sat, Feb 1, 2014 at 1:13 PM, Patrick Hunt ph...@apache.org wrote: -1, the release looks good however the status page needs to be updated before you publish this (generally, but specifically see the Project Setup section): http://incubator.apache.org/projects/twill.html If you're not familiar with the mechanics of this see: http://incubator.apache.org/guides/website.html#Edit+your+project+status+page Patrick On Fri, Jan 31, 2014 at 4:42 PM, Terence Yim cht...@gmail.com wrote: Hi all, This is to call for a vote for release of Apache Twill v0.1.0-incubating. This will be the first incubator release for Apache Twill. Vote on twill-dev: http://s.apache.org/Rsy Result on vote on twill-dev: http://s.apache.org/KMR The tag to be voted upon is v0.1.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating Please vote on releasing this package as Apache Twill 0.1.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.1.0-incubating [ ] -1 Do not release this package because ... Thanks, Apache Twill Team - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]
Ah, isn't this meant all mentors should be on private and dev lists? I believe you guys already done that - Henry On Sat, Feb 1, 2014 at 4:30 PM, Terence Yim cht...@gmail.com wrote: Hi Henry, It's because it's not done yet, hence there is completion date. Terence On Sat, Feb 1, 2014 at 2:42 PM, Henry Saputra henry.sapu...@gmail.com wrote: Looks like it is updated already. Missing one section: Subscribe all Mentors on the pmc and general lists. - Henry On Sat, Feb 1, 2014 at 2:02 PM, Terence Yim cht...@gmail.com wrote: Hi Patrick, I've updated the status page yesterday with dates (both Incubation status reports and Project setup section). Is it not update enough? Thanks, Terence On Sat, Feb 1, 2014 at 1:13 PM, Patrick Hunt ph...@apache.org wrote: -1, the release looks good however the status page needs to be updated before you publish this (generally, but specifically see the Project Setup section): http://incubator.apache.org/projects/twill.html If you're not familiar with the mechanics of this see: http://incubator.apache.org/guides/website.html#Edit+your+project+status+page Patrick On Fri, Jan 31, 2014 at 4:42 PM, Terence Yim cht...@gmail.com wrote: Hi all, This is to call for a vote for release of Apache Twill v0.1.0-incubating. This will be the first incubator release for Apache Twill. Vote on twill-dev: http://s.apache.org/Rsy Result on vote on twill-dev: http://s.apache.org/KMR The tag to be voted upon is v0.1.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating Please vote on releasing this package as Apache Twill 0.1.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.1.0-incubating [ ] -1 Do not release this package because ... Thanks, Apache Twill Team - 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 - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc5)
Thanks for the reminder Patrick On Thu, Jan 30, 2014 at 3:34 PM, Patrick Hunt ph...@apache.org wrote: -1 due to the status page not being up to date. But otw the sig/xsums looked good, RAT checked out clean and I ran through the release checklist which looks ok. If you fix the status I'll change my vote to +1. A couple nits that I noticed (but not to hold a rel for): * your notice files should be updated for 2014 * the release artifact (spark-0.9.0-incubating.tgz) is missing the DISCLAIMER file, I see that the text is included in the readme, this is somewhat non-standard but seems fine. Patrick On Thu, Jan 30, 2014 at 2:50 PM, Patrick Hunt ph...@apache.org wrote: Hi Patrick, prior to any incubator release you should ensure that your status page is up to date. The Project Setup section in particular: http://incubator.apache.org/projects/spark.html Patrick On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.9.0. A vote on this release has passed within the Spark PPMC. The tag to be voted on is v0.9.0-incubating (commit 95d28ff3): https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9 The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The list of keys associated with Spark is available at: https://people.apache.org/keys/group/spark.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-1006/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/ Please vote on releasing this package as Apache Spark 0.9.0-incubating! The vote is open until Thursday, January 30, at 08:05 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.9.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Release Apache Spark 0.9.0-incubating (rc5)
As usual, thanks for driving the release Patrick =) - Henry On Thu, Jan 30, 2014 at 7:38 PM, Patrick Wendell pwend...@gmail.com wrote: Voting is now closed. This vote passes with 3 IPCM +1 votes and no 0 or -1 votes. Thank you to everyone who voted. Totals: +1: Matei Zaharia Andy Konwinski Henry Saputra* Jean-Baptiste Onofré* Patrick Wendell Patrick Hunt* 0: -1: * = binding Thanks to all those who voted. - Patrick On Thu, Jan 30, 2014 at 7:18 PM, Patrick Hunt ph...@apache.org wrote: The status page is updated and it looks good to me. +1 Release this package as Apache Spark 0.9.0-incubating Patrick On Thu, Jan 30, 2014 at 3:34 PM, Patrick Hunt ph...@apache.org wrote: -1 due to the status page not being up to date. But otw the sig/xsums looked good, RAT checked out clean and I ran through the release checklist which looks ok. If you fix the status I'll change my vote to +1. A couple nits that I noticed (but not to hold a rel for): * your notice files should be updated for 2014 * the release artifact (spark-0.9.0-incubating.tgz) is missing the DISCLAIMER file, I see that the text is included in the readme, this is somewhat non-standard but seems fine. Patrick On Thu, Jan 30, 2014 at 2:50 PM, Patrick Hunt ph...@apache.org wrote: Hi Patrick, prior to any incubator release you should ensure that your status page is up to date. The Project Setup section in particular: http://incubator.apache.org/projects/spark.html Patrick On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.9.0. A vote on this release has passed within the Spark PPMC. The tag to be voted on is v0.9.0-incubating (commit 95d28ff3): https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9 The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The list of keys associated with Spark is available at: https://people.apache.org/keys/group/spark.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-1006/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/ Please vote on releasing this package as Apache Spark 0.9.0-incubating! The vote is open until Thursday, January 30, at 08:05 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.9.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc5)
NOTICE and LICENSE files look ok - good Signatures and hashes are checked - good No executable files in the source - good Code compiled with sbt - good +1 (binding) - Henry On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.9.0. A vote on this release has passed within the Spark PPMC. The tag to be voted on is v0.9.0-incubating (commit 95d28ff3): https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9 The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The list of keys associated with Spark is available at: https://people.apache.org/keys/group/spark.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-1006/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/ Please vote on releasing this package as Apache Spark 0.9.0-incubating! The vote is open until Thursday, January 30, at 08:05 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.9.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Report Manager for February
Hi Marvin, is there any wiki page describing the TODO for Report Manager? On Mon, Jan 20, 2014 at 7:54 PM, Marvin Humphrey mar...@rectangular.com wrote: Greets, Thanks very much to Roman Shaposhnik for serving as Report Manager for the Incubator's January Board report! Anyone up for February? As with Release Managers, the more people in our community that acquire a deep understanding of our facilities by taking a turn serving as Report Manager, the healthier we'll be! Marvin Humphrey - 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
[RESULT] [VOTE] Release Apache Metamodel 4.0.0 incubating
Missing one +1 from Dave
On Tuesday, January 21, 2014, Ankit Kumar
ak.ankitku...@gmail.comjavascript:_e({}, 'cvml',
'ak.ankitku...@gmail.com');
wrote:
HI All,
The vote for Apache Metamodel 4.0.0-incubating is closed. The vote passes
with 4(+1) votes.
Following IPMC votes were received.
*+1*
hsaputra
mfranklin
arvind
nslater
Regards
Ankit
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
Cool, thanks Dave! On Mon, Jan 20, 2014 at 2:54 PM, Dave Brondsema d...@brondsema.net wrote: +1 In addition to that JIRA ticket, I also appreciate the clarification earlier in this email thread about exactly which file is being voted on for release. I was unsure since there were so many jar files. The source zip looks good to me. On 1/19/14 12:17 PM, Henry Saputra wrote: HI Dave, just want to clarify if any concern or issue you raised should block the RC or could we get +1 from you given the new JIRA Kasper filed to fix the LICENSE? - Henry On Mon, Jan 13, 2014 at 9:07 PM, Dave Brondsema d...@brondsema.net wrote: Hi Ankit and other Metamodel developers, Congrats on getting this far with your first release so far. Here's a few questions and concerns: The NOTICE file should only have what's needed. In your git repo, the last 3 lines I don't think should be there. The NOTICE file in the source jar files look better though. More info on brevity: http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCAAS6%3D7jc2bHJK_H14bRFEkuDhvfECKw7Qz3%3DaXuMBhQTuWHx1g%40mail.gmail.com%3E However, the NOTICE files in the source jar files do not have Apache or incubating in the Metamodel name. (If you do re-spin this release you can bump 2013 to 2014 at that point too - I do realize you started this release in 2013, no problem) The *.asc.md5 and *.asc.sha1 files are hashes of PGP signatures and seem unnecessary to me. Not a blocker, but I wouldn't bother creating them for future releases. Less unnecessary files to look at is better. I see your PGP key is at http://www.apache.org/dist/incubator/metamodel/KEYS too. Good. I am not familiar with policies specifically for maven .jar releases. I would think the DISCLAIMER file would still be required. http://incubator.apache.org/guides/release-java.html doesn't mention it, but wouldn't it be appropriate in META-INFO alongside LICENSE and NOTICE? Perhaps someone else can shed some light on this. -Dave On 1/13/14 7:32 AM, Ankit Kumar wrote: Hi All, Please vote on releasing the following candidate as Apache MetaModel(incubating) version 4.0.0. This will be the first incubator release for Metamodel in Apache. The tag to be voted on is v4.0.0-incubating:https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating Release artifacts are signed with the following key:https://people.apache.org/keys/committer/ankitkumar2711.asc Release engineer public key id: B68FA0EF The staging repository for this release can be found at:https://repository.apache.org/content/repositories/orgapachemetamodel-010/ Source jars can be found here: https://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/ Result thread link from dev mailing list: http://mail-archives.apache.org/mod_mbox/metamodel-dev/201401.mbox/%3CCALuGr6aPmPwKgGb5ft%3Dy_BDKPwBKbS7g7QR%2BS6YHAkVg6_nH%2Bg%40mail.gmail.com%3E Please vote on releasing this package as Apache MetaModel 4.0.0-incubating. The vote is open until 16th January 2014 14:00 CET and passes if a majority of at least 3 IPMC votes are cast. Regards Ankit -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - 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 -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
Noah, can we address these with next release or do you think should block the release? On Wed, Jan 15, 2014 at 10:49 AM, Noah Slater nsla...@apache.org wrote: Just to be clear, is this the single release artefact we're voting on: http://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/MetaModel-4.0.0-incubating-source-release.zip Is it common to have asc.md5 and asc.sha1? They seem redundant to me. Sigs and hashes: OK DEPENDENCIES is in the release, but not in the Git tag. I guess that's okay? It's the only difference. What is HEADER.txt doing in the source? (Sorry for not catching these on the original vote.) On 13 January 2014 13:32, Ankit Kumar ak.ankitku...@gmail.com wrote: Hi All, Please vote on releasing the following candidate as Apache MetaModel(incubating) version 4.0.0. This will be the first incubator release for Metamodel in Apache. The tag to be voted on is v4.0.0-incubating:https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating Release artifacts are signed with the following key:https://people.apache.org/keys/committer/ankitkumar2711.asc Release engineer public key id: B68FA0EF The staging repository for this release can be found at:https://repository.apache.org/content/repositories/orgapachemetamodel-010/ Source jars can be found here: https://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/ Result thread link from dev mailing list: http://mail-archives.apache.org/mod_mbox/metamodel-dev/201401.mbox/%3CCALuGr6aPmPwKgGb5ft%3Dy_BDKPwBKbS7g7QR%2BS6YHAkVg6_nH%2Bg%40mail.gmail.com%3E Please vote on releasing this package as Apache MetaModel 4.0.0-incubating. The vote is open until 16th January 2014 14:00 CET and passes if a majority of at least 3 IPMC votes are cast. Regards Ankit -- Noah Slater https://twitter.com/nslater - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
I assume we will get +1 from you for this release candidate given Kasper's new JIRA task filed? - Henry On Thu, Jan 16, 2014 at 7:56 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Jan 16, 2014 at 6:04 AM, Kasper Sørensen kasper.soren...@humaninference.com wrote: I've made a task for the additional licenses in the LICENSE file that you mention: https://issues.apache.org/jira/browse/METAMODEL-34 Do tell if this task is somehow not sufficient to mend the issue that you identified. Looks good to me! I withdraw my -1 vote. Thanks, Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
HI Dave, just want to clarify if any concern or issue you raised should block the RC or could we get +1 from you given the new JIRA Kasper filed to fix the LICENSE? - Henry On Mon, Jan 13, 2014 at 9:07 PM, Dave Brondsema d...@brondsema.net wrote: Hi Ankit and other Metamodel developers, Congrats on getting this far with your first release so far. Here's a few questions and concerns: The NOTICE file should only have what's needed. In your git repo, the last 3 lines I don't think should be there. The NOTICE file in the source jar files look better though. More info on brevity: http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCAAS6%3D7jc2bHJK_H14bRFEkuDhvfECKw7Qz3%3DaXuMBhQTuWHx1g%40mail.gmail.com%3E However, the NOTICE files in the source jar files do not have Apache or incubating in the Metamodel name. (If you do re-spin this release you can bump 2013 to 2014 at that point too - I do realize you started this release in 2013, no problem) The *.asc.md5 and *.asc.sha1 files are hashes of PGP signatures and seem unnecessary to me. Not a blocker, but I wouldn't bother creating them for future releases. Less unnecessary files to look at is better. I see your PGP key is at http://www.apache.org/dist/incubator/metamodel/KEYS too. Good. I am not familiar with policies specifically for maven .jar releases. I would think the DISCLAIMER file would still be required. http://incubator.apache.org/guides/release-java.html doesn't mention it, but wouldn't it be appropriate in META-INFO alongside LICENSE and NOTICE? Perhaps someone else can shed some light on this. -Dave On 1/13/14 7:32 AM, Ankit Kumar wrote: Hi All, Please vote on releasing the following candidate as Apache MetaModel(incubating) version 4.0.0. This will be the first incubator release for Metamodel in Apache. The tag to be voted on is v4.0.0-incubating:https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating Release artifacts are signed with the following key:https://people.apache.org/keys/committer/ankitkumar2711.asc Release engineer public key id: B68FA0EF The staging repository for this release can be found at:https://repository.apache.org/content/repositories/orgapachemetamodel-010/ Source jars can be found here: https://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/ Result thread link from dev mailing list: http://mail-archives.apache.org/mod_mbox/metamodel-dev/201401.mbox/%3CCALuGr6aPmPwKgGb5ft%3Dy_BDKPwBKbS7g7QR%2BS6YHAkVg6_nH%2Bg%40mail.gmail.com%3E Please vote on releasing this package as Apache MetaModel 4.0.0-incubating. The vote is open until 16th January 2014 14:00 CET and passes if a majority of at least 3 IPMC votes are cast. Regards Ankit -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
Sounds good to me Marvin. I agree mentors votes are the ones should count most. I just want to make sure no -1 VOTE from IPMCs about this RC. - Henry On Sunday, January 19, 2014, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Jan 19, 2014 at 9:15 AM, Henry Saputra henry.sapu...@gmail.comjavascript:; wrote: I assume we will get +1 from you for this release candidate given Kasper's new JIRA task filed? My freelance vote is not needed, and I'm not going to set a precedent where Mentors don't have to vote because they can count on people like me to let them off the hook. (See http://s.apache.org/Kca.) When the vote is tallied, there is no need to include me in the list, because I have withdrawn the vote I cast earlier. This RC will already pass with enough +1 votes from MetaModel's Mentors -- which is as it should be. Kudos! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:;
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
I think DEPENDENCIES are generated by Maven. Hmm I am not sure about HEADER.txt, we'll bring the discussion back to MetaModel podling dev for another round. - Henry On Wed, Jan 15, 2014 at 10:49 AM, Noah Slater nsla...@apache.org wrote: Just to be clear, is this the single release artefact we're voting on: http://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/MetaModel-4.0.0-incubating-source-release.zip Is it common to have asc.md5 and asc.sha1? They seem redundant to me. Sigs and hashes: OK DEPENDENCIES is in the release, but not in the Git tag. I guess that's okay? It's the only difference. What is HEADER.txt doing in the source? (Sorry for not catching these on the original vote.) On 13 January 2014 13:32, Ankit Kumar ak.ankitku...@gmail.com wrote: Hi All, Please vote on releasing the following candidate as Apache MetaModel(incubating) version 4.0.0. This will be the first incubator release for Metamodel in Apache. The tag to be voted on is v4.0.0-incubating:https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating Release artifacts are signed with the following key:https://people.apache.org/keys/committer/ankitkumar2711.asc Release engineer public key id: B68FA0EF The staging repository for this release can be found at:https://repository.apache.org/content/repositories/orgapachemetamodel-010/ Source jars can be found here: https://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/ Result thread link from dev mailing list: http://mail-archives.apache.org/mod_mbox/metamodel-dev/201401.mbox/%3CCALuGr6aPmPwKgGb5ft%3Dy_BDKPwBKbS7g7QR%2BS6YHAkVg6_nH%2Bg%40mail.gmail.com%3E Please vote on releasing this package as Apache MetaModel 4.0.0-incubating. The vote is open until 16th January 2014 14:00 CET and passes if a majority of at least 3 IPMC votes are cast. Regards Ankit -- Noah Slater https://twitter.com/nslater - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
HI Marvin, As usual, thanks for the useful review. We will revise the LICENSE and NOTICE files in MetaModel podling dev list and come back for VOTE. - Henry On Wed, Jan 15, 2014 at 9:14 AM, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Jan 14, 2014 at 11:55 PM, Henry Saputra henry.sapu...@gmail.com wrote: Do you think it is a blocker for the release for the NOTICE file extra lines of information? In the NOTICE file in the release candidate, the last three lines with content are... Portions of this software were originally based on the following: Copyright 2010-2013 Human Inference Enterprise B.V. These have been licensed to the Apache Software Foundation under a software grant. The committer who added those lines is Kaspar Sørenson, who works for Human Inference. If Human Inference wants that copyright notice, it's here to stay. (Nobody else should mess with it now that it's there -- modifying copyright notices is potentially illegal.) The last line about the software grant is superfluous and IMO ought to be removed -- but it is innocuous and does not block release. The LICENSE file, however, contains many licenses which do not apply to the source package. The extraneous licenses are for jar files which will be bundled with a binary, but that is not what the ASF releases. The extra material in the LICENSE file should ordinarily block if this were a TLP release. However, what we have here is a licensing documentation bug, not a legal issue which would put the Foundation at risk, and I think Incubator lenience should come into play. I'm going to lodge a binding -1 vote for now, but I am willing to remove it if the MetaModel podling presents a plan for fixing up LICENSE in their next release. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Open Climate Workbench from the Incubator
+1 (binding) Good luck guys! On Wed, Jan 15, 2014 at 9:46 AM, Chris Mattmann mattm...@apache.org wrote: Hi Folks, The Apache Open Climate Workbench community has VOTEd to graduate from the Apache Incubator. I'm now calling an official IPMC VOTE to make this happen as well. Here's the community tally: +1 -- Chris Mattmann* Michael Joyce Denis Nadeau Cameron Goodale Paul Ramirez* Chris Douglas* Andrew Hart* +0 - -1 - * - indicates IPMC member We've made 3 releases of the software, have added new committers and PPMC members and in general done great work to build this community in the Apache way. Please VOTE to graduate Apache Open Climate Workbench from the Incubator. I'll leave the VOTE open for the next week and tally the results after then. The graduation resolution is pasted below. Thanks! Cheers, Chris ---snip 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 preparation, evaluation and analysis of massive climate remote sensing and model output data. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Open Climate Workbench Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Open Climate Workbench Project be and hereby is responsible for the creation and maintenance of software related to preparation, evaluation and analysis of massive climate remote sensing and model output data; and be it further RESOLVED, that the office of Vice President, Apache Open Climate Workbench, 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 Open Climate Workbench Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Open Climate Workbench 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 Open Climate Workbench Project: * Andrew Hart ah...@apache.org * Maziyar Boustani boust...@apache.org * Christopher Douglas cdoug...@apache.org * Chris Jack cj...@apache.org * Dan Crichton crich...@apache.org * Denis Nadeau nad...@apache.org * estani est...@apache.org * Cameron Goodale good...@apache.org * Alex Goodman good...@apache.org * Huikyo Lee huiky...@apache.org * Jason Peter Evans jasonev...@apache.org * Jinwon Kim j...@apache.org * Michael James Joyce jo...@apache.org * Laura Carriere lcarri...@apache.org * Lluis Fita Borrell lfitaborr...@apache.org * Luca Cinquini ll...@apache.org * Chris Mattmann mattm...@apache.org * Nick Kew n...@apache.org * Paul Loikith ploik...@apache.org * Paul Michael Ramirez prami...@apache.org * Paul Zimdars pzimd...@apache.org * M. V. S. Rama Rao rama...@apache.org * J Sansay san...@apache.org * Shakeh Khudikyan skhud...@apache.org * Suresh Marru sma...@apache.org * Duane Waliser wali...@apache.org * Kim Whitehall whiteh...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Michael Joyce be appointed to the office of Vice President, Apache Open Climate Workbench, 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 Apache Open Climate Workbench Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Open Climate Workbench podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Open Climate Workbench podling encumbered upon the Apache Incubator Project are hereafter discharged. ---snip -Original Message- From: Michael Joyce jo...@apache.org Reply-To: d...@climate.incubator.apache.org d...@climate.incubator.apache.org Date: Wednesday, January 15, 2014 9:41 AM To: dev d...@climate.incubator.apache.org Subject: Re: [VOTE] Graduation of Apache Open Climate Workbench from the Incubator Hay everyone, Just a quick follow up to provide a summary of the vote. +1 -- Chris Mattmann Michael Joyce Denis Nadeau Cameron Goodale Paul Ramirez Chris Douglas Andrew Hart +0 - -1 - Unfortunately, I don't think everything will get done in time for todays board meeting. However we have plenty of time to get everything taken care of for February! Thanks everyone! -- Joyce On Sun, Jan 12, 2014 at 10:05 AM, Andrew Hart
Re: [VOTE] Release Apache Metamodel 4.0.0 incubating
Thanks for the input Dave, really useful. Do you think it is a blocker for the release for the NOTICE file extra lines of information? The NOTICE file in source jar should be the same with the one from git repo. Could you tell me which NOTICE file in the source jar you were referring to? - Henry On Mon, Jan 13, 2014 at 9:07 PM, Dave Brondsema d...@brondsema.net wrote: Hi Ankit and other Metamodel developers, Congrats on getting this far with your first release so far. Here's a few questions and concerns: The NOTICE file should only have what's needed. In your git repo, the last 3 lines I don't think should be there. The NOTICE file in the source jar files look better though. More info on brevity: http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCAAS6%3D7jc2bHJK_H14bRFEkuDhvfECKw7Qz3%3DaXuMBhQTuWHx1g%40mail.gmail.com%3E However, the NOTICE files in the source jar files do not have Apache or incubating in the Metamodel name. (If you do re-spin this release you can bump 2013 to 2014 at that point too - I do realize you started this release in 2013, no problem) The *.asc.md5 and *.asc.sha1 files are hashes of PGP signatures and seem unnecessary to me. Not a blocker, but I wouldn't bother creating them for future releases. Less unnecessary files to look at is better. I see your PGP key is at http://www.apache.org/dist/incubator/metamodel/KEYS too. Good. I am not familiar with policies specifically for maven .jar releases. I would think the DISCLAIMER file would still be required. http://incubator.apache.org/guides/release-java.html doesn't mention it, but wouldn't it be appropriate in META-INFO alongside LICENSE and NOTICE? Perhaps someone else can shed some light on this. -Dave On 1/13/14 7:32 AM, Ankit Kumar wrote: Hi All, Please vote on releasing the following candidate as Apache MetaModel(incubating) version 4.0.0. This will be the first incubator release for Metamodel in Apache. The tag to be voted on is v4.0.0-incubating:https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating Release artifacts are signed with the following key:https://people.apache.org/keys/committer/ankitkumar2711.asc Release engineer public key id: B68FA0EF The staging repository for this release can be found at:https://repository.apache.org/content/repositories/orgapachemetamodel-010/ Source jars can be found here: https://repository.apache.org/content/repositories/orgapachemetamodel-010/org/apache/metamodel/MetaModel/4.0.0-incubating/ Result thread link from dev mailing list: http://mail-archives.apache.org/mod_mbox/metamodel-dev/201401.mbox/%3CCALuGr6aPmPwKgGb5ft%3Dy_BDKPwBKbS7g7QR%2BS6YHAkVg6_nH%2Bg%40mail.gmail.com%3E Please vote on releasing this package as Apache MetaModel 4.0.0-incubating. The vote is open until 16th January 2014 14:00 CET and passes if a majority of at least 3 IPMC votes are cast. Regards Ankit -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hoya Proposal
Ah yes, I missed the additional hadoop in the path. Close enough :) On Thursday, January 9, 2014, Steve Loughran wrote: no its wrong, it should all be under org.apache.hoya. I had the hadoop prefix so that I could perhaps put it straight into the hadoop code as another tools module -no need for incubation. But as the actual providers and all tests are related to the deployment of hbase and accumulo, it really comes downstream of those. so a rename is needed. but yes, ASF headers everywhere On 8 January 2014 22:48, Henry Saputra henry.sapu...@gmail.comjavascript:; wrote: I like how the initial code already put under org.apache.hadoop.hoya with correct ASF header =) - Henry On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran ste...@hortonworks.comjavascript:; wrote: I'm starting to put together the incubation proposal for Hoya: a tool to dynamically deploy applications such as HBase or Accumulo on YARN https://wiki.apache.org/incubator/HoyaProposal It does already work to the extent that it can bring up either application, run different clusters of different versions, and remember where containers were allocated so that on application restart it can ask for them back. That increases data locality and makes a big difference with HBase. It also needs a lot more work -YARN-896 is adding YARN features that help, but there's lots of fun to be had in Hoya including -leading edge work in failure handling, modelling cluster unreliability and reacting to it. Can we move beyond simple blacklisting to greylisting, accepting unreliable boxes if we have no altenatives Then there's adding more providers, to support different application installations -I'm starting to write a functional test framework which need provider-specific workload generations Other features: AM should have a web ui that redirects to the live endpoints to all the app-specific UIs (e.g. HBase Master GUI), as well as displaying cluster state itself, for people and for management tools To summarise: lots of fun to be had -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:; -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [RESULT] [VOTE] Release Apache Metamodel 4.0.0 incubating
Hi Marvin, Sorry about the confusing message. Looks like there was a misunderstanding on how to send VOTE request to general@ list. We will sort it out and try it again. - Henry On Wed, Jan 8, 2014 at 7:46 AM, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Jan 8, 2014 at 1:42 AM, Ankit Kumar ak.ankitku...@gmail.com wrote: The vote is now closed. This vote passes with 4 IPMC +1's and no 0 or -1 votes. +1 (4 Total) Henry Saputra Juan Jose van der linden Arvind Prabhakar Matt Franklin 0 (0 Total) -1 (0 Total) * = Binding Vote The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-metamodel-dev/201312.mbox/%3CCAAHPopELo0OJx_rR6kGNjppKLMbFjw-%2BE8XyH68ds31%3DxD4t-A%40mail.gmail.com%3E Thanks to everyone who helped with this release. Hi, I found this message confusing at first because it refers to the result of the dev@metamodel VOTE thread, but appears to presents the result as final. It seems that the MetaModel Mentors are on top of things, though: http://s.apache.org/oql (Henry Saputra) Ok, so next step please send RESULT thread reply to the VOTE thread to tally up the vote so we could bring the VOTE to the general@incubator.apache.org list to get final look or reviews by incubating community and IPMCs. To reinforce Henry, here's a relevant excerpt from the Incubator's policy on releases: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. So, although there are 4 IPMC +1 votes, the full IPMC has not yet been given an opportunity to review the release candidate. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hoya Proposal
I like how the initial code already put under org.apache.hadoop.hoya with correct ASF header =) - Henry On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran ste...@hortonworks.com wrote: I'm starting to put together the incubation proposal for Hoya: a tool to dynamically deploy applications such as HBase or Accumulo on YARN https://wiki.apache.org/incubator/HoyaProposal It does already work to the extent that it can bring up either application, run different clusters of different versions, and remember where containers were allocated so that on application restart it can ask for them back. That increases data locality and makes a big difference with HBase. It also needs a lot more work -YARN-896 is adding YARN features that help, but there's lots of fun to be had in Hoya including -leading edge work in failure handling, modelling cluster unreliability and reacting to it. Can we move beyond simple blacklisting to greylisting, accepting unreliable boxes if we have no altenatives Then there's adding more providers, to support different application installations -I'm starting to write a functional test framework which need provider-specific workload generations Other features: AM should have a web ui that redirects to the live endpoints to all the app-specific UIs (e.g. HBase Master GUI), as well as displaying cluster state itself, for people and for management tools To summarise: lots of fun to be had -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Seeking champion for JSON-Schema project
Hi Russ, It would probably better to write up initial proposal to get more feedback or attention from IPMCs or Apache members. - Henry On Sun, Jan 5, 2014 at 3:11 PM, Russ Jackson rjack...@jscomm.net wrote: Hi. I'm looking for a champion to help me try to get a new Java project into the Apache incubator. I've creating a project that allows users to define JSON schema documents that are then used to validate JSON data documents. The motivation for this was to (a) be able to validate JSON coming in to RESTful web services via POST and PUT and (b) to be able to validate, via unit tests, JSON leaving a REST service via GET so that service contracts with clients can be more fully enforced. I've also created a schema repository manager as well as the ability to generate REST web service documentation from the schemas (and via reflection over the annotations on the service classes). Thanks for the help - I'm very excited about this and am hoping you are too. Russ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding January 2014
HI Roman, I am one of the mentors for MetaModel podling. The initial discussion about bylaws come from me since I had some bad experience with some projects so I brought up the topic. But per recommendations by other mentors in the podling we decided to put off the bylaws effort for now. But you are right, at this point the discussion is too early and we are now trying to get back to focus on delivering a release. Thanks for the report =) - Henry On Mon, Jan 6, 2014 at 9:46 PM, Roman Shaposhnik r...@apache.org wrote: Aurora Justin Mclean (jmclean): Project is off to a good start with lots of activity on the mailing list and in JIRA. Mentors are not very active but there are no issues that need attention. BatchEE John Ament (johndament): BatchEE is a new podling, with a small team working on it currently. It's a fork of the RI for Java Batch from Java EE 7. I think short term they should focus on getting a release out there to draw in community interest; which should help build the podling more and drive feature interest. Celix Dave Fisher (wave): This podling is growing. They plan a release soon and let's see how that goes. When it comes time for graduation I have some concerns that this podling's community may be too small. log4cxx2 Christian Grobmeier (grobmeier): the podling is just getting started MetaModel Roman Shaposhnik (rvs): In general project seem to be on the right track with a healthy amount of community interaction happening over the mailing list and a strong desire to do a release. Two issues have caught my attention though: 1. I am not quite sure what motivated a strong drive towards having by-laws this early in the game. In my experience the focus on by-laws can, at times, put a damping factor on community growth. IOW, what I've seen in the past is that communities try to come up with by-laws when the usual process of consensus building starts to fail. Nothing actionable here for the project -- just keep this in mind. 2. The JIRA feels a bit empty for the project that has been developing for more than 6 month (grand total of 33 issues). At the same time the number of commits in the Git repo is on par with the development pace. What it tells me is that there's no strong correlation between JIRAs and commits. This raises a red flag of whether all of the changes that are committed get a proper community vetting before they go in. I couldn't find any traces of the review requests either: https://reviews.apache.org/groups/metamodel/ This in my opinion is a pretty big concern for the project. ODF Toolkit John Ament (johndament): ODF Toolkit has been incubating for a long time. Activity on their list is in frequent, but active enough that it still is running. Considering what the project is, I think the best resolution for this podling is to graduate as a sub project under something like OpenOffice or POI. Olingo (No shepherd review filed.) Ripple Roman Shaposhnik (rvs): The project appears to be doing well Samza (No shepherd review filed.) Sirona (No shepherd review filed.) Spark Alan Cabrera (acabrera): Seems like a nice active project. IMO, there's no need to wait import to JIRA to graduate. Seems like they can graduate now. Stratos Raphael Bircher (rbircher): The project looks realy active. Continue like this guys! Twill (No shepherd review filed.) VXQuery Raphael Bircher (rbircher): The mailing list traffic is not very high. However, the basic discussions are on the lists. Usergrid (No shepherd review filed.) - - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Question about jar files in svn.
But at the end, when a podling prepare a release there should not include jar files as part of the source release artifacts to be VOTED on, is this correct? - Henry On Thu, Dec 19, 2013 at 9:21 AM, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk tras...@stratuscom.com wrote: We’re having a discussion over in d...@river.apache.org that was triggered by the recent discussion here about the Spark podling release. The River discussions seem to be playing out productively. Here are links for other people who may be interested: https://issues.apache.org/jira/browse/RIVER-432 http://markmail.org/thread/abppti56ipnhnnfy To be more specific, there doesn’t seem to be any doubt that jars shouldn’t be included in source release packages, but would it be fair to say that they should also not be in the svn? My understanding is that it is fine to store jars in version control outside of the main source tree, analogous to providing a separate -deps download. Between that and technical solutions which download deps on the fly such as Ivy and Maven, I think that renders the question about whether binaries can reside in the main source tree within version control moot. But there's no strictly enforced policy AFAIK because we discourage people from considering our source control repositories distribution points. (Note to podlings: this is why we make links to source control only available through the developer portions of our websites, etc.) That way we don't have to be rigid about enforcing the policies which apply to releases at every single commit point, even as we make best efforts to keep our trees clean. FWIW, the same principles which give us a measure of flexibility about LICENSE and NOTICE in version control could arguably apply to jar files as well. Here's Board member Doug Cutting back in September on legal-discuss@apache: http://s.apache.org/GNP I think perhaps you're looking for clear lines where things are actually a bit fuzzy. Certainly releases are official distributions and need LICENSE and NOTICE files. That line is clear. On the other hand, we try to discourage folks from thinking that source control is a distribution. Rather we wish it to be considered our shared workspace, containing works in progress, not yet always ready for distribution to folks outside the foundation. But, since we work in public, folks from outside the foundation can see our shared workspace and might occasionally mistake it for an official distribution. We'd like them to still see a LICENSE and NOTICE file. So it's not a hard-and-fast requirement that every tree that can possibly be checked out have a LICENSE and NOTICE file at its root, but it's a good practice for those trees that are likely to be checked out have them, so that folks who might consume them are well informed. Again, policy flexibility with respect to version control becomes academic if you can restructure the build. Nevertheless, I hope that this additional background is helpful for River's ongoing discussions. Cheers, Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Question about jar files in svn.
Ah I see. So the point of concern is the external jars, but jars that are generated by the project itself (for example for tests) should be fine? - Henry On Thu, Dec 19, 2013 at 10:34 AM, sebb seb...@gmail.com wrote: On 19 December 2013 18:26, Henry Saputra henry.sapu...@gmail.com wrote: But at the end, when a podling prepare a release there should not include jar files as part of the source release artifacts to be VOTED on, is this correct? I think that depends on what the jar files are. For example. Apache Commons Compress includes some jar files in SVN and the source release as part of the test data. But I would not expect to find external jar files in the source release. - Henry On Thu, Dec 19, 2013 at 9:21 AM, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk tras...@stratuscom.com wrote: We’re having a discussion over in d...@river.apache.org that was triggered by the recent discussion here about the Spark podling release. The River discussions seem to be playing out productively. Here are links for other people who may be interested: https://issues.apache.org/jira/browse/RIVER-432 http://markmail.org/thread/abppti56ipnhnnfy To be more specific, there doesn’t seem to be any doubt that jars shouldn’t be included in source release packages, but would it be fair to say that they should also not be in the svn? My understanding is that it is fine to store jars in version control outside of the main source tree, analogous to providing a separate -deps download. Between that and technical solutions which download deps on the fly such as Ivy and Maven, I think that renders the question about whether binaries can reside in the main source tree within version control moot. But there's no strictly enforced policy AFAIK because we discourage people from considering our source control repositories distribution points. (Note to podlings: this is why we make links to source control only available through the developer portions of our websites, etc.) That way we don't have to be rigid about enforcing the policies which apply to releases at every single commit point, even as we make best efforts to keep our trees clean. FWIW, the same principles which give us a measure of flexibility about LICENSE and NOTICE in version control could arguably apply to jar files as well. Here's Board member Doug Cutting back in September on legal-discuss@apache: http://s.apache.org/GNP I think perhaps you're looking for clear lines where things are actually a bit fuzzy. Certainly releases are official distributions and need LICENSE and NOTICE files. That line is clear. On the other hand, we try to discourage folks from thinking that source control is a distribution. Rather we wish it to be considered our shared workspace, containing works in progress, not yet always ready for distribution to folks outside the foundation. But, since we work in public, folks from outside the foundation can see our shared workspace and might occasionally mistake it for an official distribution. We'd like them to still see a LICENSE and NOTICE file. So it's not a hard-and-fast requirement that every tree that can possibly be checked out have a LICENSE and NOTICE file at its root, but it's a good practice for those trees that are likely to be checked out have them, so that folks who might consume them are well informed. Again, policy flexibility with respect to version control becomes academic if you can restructure the build. Nevertheless, I hope that this additional background is helpful for River's ongoing discussions. Cheers, Marvin Humphrey - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.8.0-incubating (rc4)
Thanks for the links Andrew, those are good insights. - Henry On Sun, Dec 15, 2013 at 11:56 PM, Andrew Phillips andr...@apache.org wrote: You might also want to have a look at how Scala itself deals with the issue of required binaries for the build: https://github.com/scala/scala/blob/master/pull-binary-libs.sh https://github.com/scala/scala/blob/master/tools/binary-repo-lib.sh I'm not necessarily a huge fan of this (builds on *nix only, for example), but it's at least another approach to throw into the mix... ap -- Andrew Phillips Apache jclouds - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.8.0-incubating (rc4)
NOTICE, LICENSE, and README files looks good. Checksum and signatures on the source jar looks good. Per comments by Marvin and sebb, Spark will resolve the included jar files in the source distribution in next release of 0.9 I am giving: +1 since this is 0.8.1 release which really hard to change build packaging. We'll get it right for 0.9. - Henry On Fri, Dec 13, 2013 at 7:13 PM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.8.1. The tag to be voted on is v0.8.1-incubating (commit b87d31d): https://git-wip-us.apache.org/repos/asf/incubator-spark/repo?p=incubator-spark.git;a=commit;h=b87d31dd8eb4b4e47c0138e9242d0dd6922c8c4e The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-040/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4-docs/ For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=blob;f=CHANGES.txt;h=ce0aeab524505b63c7999e0371157ac2def6fe1c;hb=branch-0.8 A vote on this release has passed within the Spark PPMC [1]. Please vote on releasing this package as Apache Spark 0.8.1-incubating! The vote is open until Tuesday, December 17th at 03:30 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.8.1-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ [1] http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201312.mbox/%3CCABPQxsuEYMn_JE0qEOcrt4J5-N1PJWgGcN7m0qzNefW7fsz2PA%40mail.gmail.com%3E (Note that at present the concluding message isn't shown due to lag in the mail archives.) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.8.0-incubating (rc4)
Hi Sebb, thanks for the review. When you said However they both contain binaries, which is not good. were you talking about the spark-0.8.1-incubating-bin-* files ? - Henry On Fri, Dec 13, 2013 at 7:13 PM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.8.1. The tag to be voted on is v0.8.1-incubating (commit b87d31d): https://git-wip-us.apache.org/repos/asf/incubator-spark/repo?p=incubator-spark.git;a=commit;h=b87d31dd8eb4b4e47c0138e9242d0dd6922c8c4e The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-040/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.8.1-incubating-rc4-docs/ For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=blob;f=CHANGES.txt;h=ce0aeab524505b63c7999e0371157ac2def6fe1c;hb=branch-0.8 A vote on this release has passed within the Spark PPMC [1]. Please vote on releasing this package as Apache Spark 0.8.1-incubating! The vote is open until Tuesday, December 17th at 03:30 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.8.1-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ [1] http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201312.mbox/%3CCABPQxsuEYMn_JE0qEOcrt4J5-N1PJWgGcN7m0qzNefW7fsz2PA%40mail.gmail.com%3E (Note that at present the concluding message isn't shown due to lag in the mail archives.) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Enable Release Checklist Experiment
So it begins =) +1 Thanks for leading the effort, Marvin - Henry On Fri, Dec 13, 2013 at 12:59 PM, Marvin Humphrey mar...@rectangular.com wrote: Greetings, As the next step in our ongoing efforts to reform the release voting process, I propose that we run an experiment allowing the PPMC members of select podlings to earn binding votes under limited circumstances by completing a release checklist. For participating podlings, the Incubator's release management guide... http://incubator.apache.org/guides/releasemanagement.html ... would be supplanted by the following documents: http://incubator.apache.org/guides/release_manifest.txt http://incubator.apache.org/guides/release.html The scope of this VOTE is limited to approving the following patch to our policy page: https://paste.apache.org/k4vJ Here is the patch content minus markup: 2013 Alternate Release Voting Process Select podlings pre-cleared by a majority vote of the IPMC MAY participate in an alternate release voting process: Should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's dev list and create a permanently archived Release Manifest as described in the Experimental Release Guide. At least three +1 votes from PPMC members are required (see the Apache Voting Process page). If the majority of PPMC votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Formal approval requires three binding +1 votes and more positive than negative votes. Votes cast by members of the Incubator PMC are always binding. For all releases after the first, votes cast by members of the PPMC are binding if a Mentor approves the Release Manifest. Please note that the proposed change is both incremental and reversible: * It is incremental because podlings must be opted in by vote of the IPMC to participate. * It is reversible because once the experiment has run its course the policy change can be reverted with zero impact through lazy consensus. Those who may have questions about the legitimacy of allowing binding votes from non-IPMC members should see this post from Roy Fielding: http://s.apache.org/v7 Please vote: [ ] +1 Yes, apply the patch enabling the experiment. [ ] -1 No, do not apply the patch enabling the experiment. This majority VOTE will run for 7 days and will close at 13:00 PST on Friday, December 20, 2013. Votes cast by members of the Incubator PMC are binding. Here is my own +1. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: S4 Podling - May need some help
Any updates from the mentors? I remember there were some sparks shown to re-energize the community about few months ago like to have weekly chats - Henry On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: S4 Podling - May need some help
Thanks Patrick. - Henry On Fri, Dec 6, 2013 at 1:41 PM, Patrick Hunt ph...@apache.org wrote: On Fri, Dec 6, 2013 at 1:37 PM, Henry Saputra henry.sapu...@gmail.com wrote: Any updates from the mentors? I reviewed/signedoff on the report. I've commented both in public and in private to the s4 folks that they should consider retirement as an option. I was/am waiting to see what the community decides. Patrick I remember there were some sparks shown to re-energize the community about few months ago like to have weekly chats - Henry On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote: Hi, I completed my shepherd review of S4 now that their board report is in place. Here's a copy: The board report reflects my sentiments as well. S4 seems to be in a bit of rut. I tried kicking off some conversations on the dev mailing list, no luck. It seems like there are at best five active participants, between the users list and dev list. Considering that there hasn't been a commit since last board report, it doesn't come off as a good sign for me. I think retirement may be an option to start exploring. It seems like through a combination of low dev activity and low user feedback S4 is having difficulty progressing. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
+1 (binding) Good luck guys On Thu, Dec 5, 2013 at 1:43 PM, Stack st...@duboce.net wrote: Discussion of the Phoenix proposal has settled since its original posting on November 7th. Feedback has been incorporated. Let us now move to a vote. Should Phoenix become an Apache incubator project? [] +1 Accept Phoenix into the Incubator [] +0 Don't care whether or which [] -1 Do not accept Phoenix into the Incubator because... The latest version of the proposal can be found here [1]. It is also posted below for your convenience. Let the vote run 72 hours. Thank you, St.Ack 1. https://wiki.apache.org/incubator/PhoenixProposal Abstract Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. Proposal Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. Background Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. Rationale As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. Initial Goals The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. Current Status Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. Meritocracy The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. Community Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative cross sampling of other organizations including Intel, Hortonworks, and Cloudera. Alignment Our proposed Phoenix effort aligns closely with Apache HBase. The HBase project perimeter is denoted by a simple byte-array
Re: Apache Marmotta - the podling has left the nest
Good luck guys :) On Friday, November 29, 2013, Jakob Frank wrote: Dear Incubator, dear Marmotta community, about one week ago, the Board has decided to establish Marmotta as a new TLP. An interesting and challenging journey has come to its end. When we started out from the Linked Media Framework towards Apache in December 2012 we already had invested several years of development into the project, but we were a rather small and focused group of developers. During incubation, this situation changed dramatically: The community opened up, grew and broadened in skills, ideas but also geographically. New users, contributors and committers joined and are helping out with pointers to documentation deficits, bug reports, and of course with documentation and code. After the code was transferred to the Apache infrastructure, we cleaned and improved the source code under the sharp eyes of the Apache community. During the last year, the addition of new features has slowed down but on the other side the codebase has stabilized and the system is working more stable than ever before. Now, with the growing community and hopefully soon more committers, I'm sure we will soon start adding further improvements and new features. One of more challenging tasks was the thorough analysis and cleanup of licenses and dependencies. Getting LICENSE NOTICE correct - well, rather acceptable - for the first release was long and tiresome work. But not for void, in return you, and all downstream projects and users, get the legal protection and warrant of the Apache Software Foundation. At this point, I'd like to thank all who contributed to the NL by picking the pieces together, nagging here and there and pointing to the bits that are missing. This is the place to express our thanks and gratitude to our mentors during incubation: Andy Seaborne, Fabian Christ, Nandana Mihindukulasooriya, thank you so much for your help and guidance during the last year! We are glad you stay with us after graduation, be it in the PMC or on the mailing lists! Our thanks also go the incubator community for all the advices we got, often indirect via the general discussion on the list. Marmotta might leave the incubator, but I'm sure most of us will stick around. A journey has come to its end? Well, not an end at all, we rather passed an important milestone and the journey already goes on: We are currently working on our first release as a Top-Level Project and hope to finally have it ready before Christmas. What a nice present ;-) Best, Jakob Frank (Marmotta PMC Chair) on behalf of the Marmotta PMC TL;DR: A big THANK YOU to our mentors Andy Seaborne, Fabian Christ and Nandana Mihindukulasooriya, and to the general Incubator for seeing us through the incubation process.
Re: [VOTE] Accept Twill for Incubation
Hi Andreas, have you created ticket to track bootstrapping of Twill into ASF incubator? Would like to follow up on the updates. Thanks, - Henry On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... -Andreas. = Abstract = Twill is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. = Proposal = Twill is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Twill also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. = Background = Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Twill is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Twill, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Twill also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Twill is not a replacement for YARN, it’s a framework that operates on top of YARN. = Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Twill’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Twill as an Apache project makes sense because Twill is a framework built on top of YARN, and Twill uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). = Current Status = Twill was initially developed at Continuuity under the name of Weave. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository after renaming to Twill. == Meritocracy == Our intent with this incubator proposal is to start building a diverse developer community around Twill following the Apache meritocracy model. Since Twill was initially developed in early 2013, we have had fast adoption and contributions within Continuuity. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. == Community == Twill is currently being used internally at Continuuity and is at the core of our products. We hope to extend our contributor base significantly and we will invite all who are interested in simplifying the development of distributed applications to participate. == Core Developers == Twill is currently being developed by five engineers at Continuuity: Terence Yim, Andreas Neumann, Gary Helmling, Poorna Chandra and Albert Shau. Terence Yim is an Apache committer for Helix, Andreas is an Apache committer and PMC member for Oozie, and Gary Helmling is an Apache committer and PMC 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
Re: [VOTE] Accept Twill for Incubation
Thanks :) On Tuesday, November 26, 2013, Andreas Neumann wrote: Hi Henry, we had created some tasks, but not an enclosing umbrella issue. I just opened that and all the subtasks: https://issues.apache.org/jira/browse/TWILL-5 (Currently we are unable to manage issues in Jira because only our champion is listed as an admin...) Thanks -Andreas. On Tue, Nov 26, 2013 at 12:28 PM, Henry Saputra henry.sapu...@gmail.comjavascript:; wrote: Hi Andreas, have you created ticket to track bootstrapping of Twill into ASF incubator? Would like to follow up on the updates. Thanks, - Henry On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... -Andreas. = Abstract = Twill is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. = Proposal = Twill is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Twill also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. = Background = Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Twill is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Twill, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Twill also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Twill is not a replacement for YARN, it’s a framework that operates on top of YARN. = Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Twill’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Twill as an Apache project makes sense because Twill is a framework built on top of YARN, and Twill uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). = Current Status = Twill was initially developed at Continuuity under the name of Weave. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository after renaming to Twill. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:;
Re: [PROPOSAL] Phoenix for Incubation
It is indeed very specific for HBase use I suppose. Would it be more beneficial to make it sub-project of HBase to get full community support from HBase? On Wed, Nov 13, 2013 at 12:43 PM, James Taylor jtay...@salesforce.com wrote: Hi All, We're pleased to share a draft ASF incubation proposal for Phoenix, a SQL layer over HBase, initially developed at Salesforce.com and subsequently open sourced on github (https://github.com/forcedotcom/phoenix). Instead of using Map-reduce to processes queries, it compiles SQL directly into native HBase calls. The complete proposal can be found here: https://wiki.apache.org/incubator/PhoenixProposal, and is also pasted below. Your feedback is greatly appreciated. James == Abstract == Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. == Proposal == Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. == Background == Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. == Rationale == As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. == Initial Goals == The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. == Current Status == Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. === Meritocracy === The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. === Community === Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list composed of hundreds of users. === Core Developers === The core developers of our project are listed in our contributors and initial PPMC below. Though many are employed at Salesforce.com, there is a representative cross sampling of other organizations including Intel, Hortonworks, Cloudera, and Twitter. ===
Re: [DISCUSS] [VOTE] Accept Twill for Incubation
We had similar issue with MetaModel where there are a lot of projects with name MetaModel but the name was approved given it needs to always mentioned as Apache MetaModel. I think we could do similar approach with Twill? - Henry On Tue, Nov 12, 2013 at 2:53 PM, Andreas Neumann a...@apache.org wrote: This is valuable feedback, and I am not quite sure how to deal with this after the vote has already passed. I took a look at retwill, and it seems that it has not had any activity (wiki edits, issues, pull requests, releases, commits) for about 18 months. In fact, it appears that it was abandoned in May 2012, only two months after it was created in March of the same year. What is the general feeling on this list? Is it a strong enough conflict to require a different project name? Thanks -Andreas. On Tue, Nov 12, 2013 at 1:45 PM, Olemis Lang ole...@gmail.com wrote: On Fri, Nov 8, 2013 at 2:25 PM, Andreas Neumann a...@apache.org wrote: Andrea, thanks for the link, we did see that project but thought that it is not relevant because it has not had any activity for 6 years, so it is probably dead. Should we be more concerned about this? There is a continuation (fork) named retwill [1]_ . BTW twill is a dependency to run the test suite of Apache™ Bloodhound . IMO , I do not think twill is a suitable name . It's very spread and popular in some circle . Choosing that name might cause some confusion . .. [1] https://bitbucket.org/brandizzi/retwill .. [2] http://shop.oreilly.com/product/9780596527808.do [...] -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCEL] [VOTE] Release Apache Tajo-0.2-incubating RC1
Clean up voting monitoring On Sun, Oct 27, 2013 at 12:40 AM, Hyunsik Choi hyun...@apache.org wrote: Hi folks This is the first release candidate for Apache Tajo-0.2-incubating, and it is also the first official release for Tajo. The PPMC vote [1][2] was passed with 5 binding +1s and no -1. Release git tag is at: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc1 Release notes is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/RELEASE_NOTES.html Release artifacts, signatures, md5, and sha512 are at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/ and the KEYS file containing the PGP keys used to sign the release can currently be found at: http://people.apache.org/keys/group/tajo.asc The RAT report is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc1/rat.txt Please vote [ ] +1 release this package as apache-tajo-0.2-incubating [ ] -1 do not release this package because ... Thanks, Hyunsik Choi [1] http://markmail.org/message/unaim5aalwjuajr3 [2] http://markmail.org/message/ywxozclddlp4avov - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Twill for Incubation
+1 (binding) Good luck guys! - Henry On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... -Andreas. = Abstract = Twill is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. = Proposal = Twill is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Twill also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. = Background = Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Twill is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Twill, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Twill also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Twill is not a replacement for YARN, it’s a framework that operates on top of YARN. = Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Twill’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Twill as an Apache project makes sense because Twill is a framework built on top of YARN, and Twill uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). = Current Status = Twill was initially developed at Continuuity under the name of Weave. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository after renaming to Twill. == Meritocracy == Our intent with this incubator proposal is to start building a diverse developer community around Twill following the Apache meritocracy model. Since Twill was initially developed in early 2013, we have had fast adoption and contributions within Continuuity. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. == Community == Twill is currently being used internally at Continuuity and is at the core of our products. We hope to extend our contributor base significantly and we will invite all who are interested in simplifying the development of distributed applications to participate. == Core Developers == Twill is currently being developed by five engineers at Continuuity: Terence Yim, Andreas Neumann, Gary Helmling, Poorna Chandra and Albert Shau. Terence Yim is an Apache committer for Helix, Andreas is an Apache committer and PMC member for Oozie, and Gary Helmling is an Apache committer and PMC 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,
Re: [VOTE] Release Apache Tajo-0.2-incubating RC3
+1 (binding) Congrats! On Mon, Nov 4, 2013 at 9:16 PM, Hyunsik Choi hyun...@apache.org wrote: Hi folks This is the fourth candidate for Apache Tajo-0.2-incubating, and it is also the first official release for Tajo. The PPMC vote [1][2][3] was passed with 3 binding +4s and no -1. Release git tag is at: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc3 Release notes is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/RELEASE_NOTES.html Release artifacts, signatures, md5, and sha1 are at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/ and the KEYS file containing the PGP keys used to sign the release can currently be found at: http://people.apache.org/keys/group/tajo.asc The RAT report is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/rat.txt Please vote [ ] +1 release this package as apache-tajo-0.2-incubating [ ] -1 do not release this package because ... Thanks, Hyunsik Choi [1] http://markmail.org/message/cvwzgdfkq2zfmmbo [2] http://markmail.org/message/crhbpagwo3pvm4et [3] http://markmail.org/message/kofx3nfjzcr7chqu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Weave for Apache Incubator
I think Twill fits well with what Weave project trying to do with Hadoop and still in the spirit of the original weave name. Other than name, the proposal looks good. Looking forward to the VOTE thread. - Henry On Tue, Nov 5, 2013 at 3:18 PM, Andreas Neumann a...@apache.org wrote: Regarding the naming issue, we understand that Weave may be problematic, so we did a little bit of searching for a new name. Here is a list of name candidates in order of our preference: - Tartan - Sisal - Twill Do these ring a bell or raise concerns? A quick search did not bring up any open source projects named Tartan, but there appear to be some non-Apache projects named Sisal and Twill. I am not sure how unique a project name has to be, it is really hard to find something that does not exist at all... On Wed, Oct 30, 2013 at 11:28 AM, David Nalley da...@gnsa.us wrote: On Tue, Oct 29, 2013 at 6:14 PM, Upayavira u...@odoko.co.uk wrote: And Apache Wave too (which is what I first saw before I read the title more carefully). Upayavira On Tue, Oct 29, 2013, at 09:12 PM, Matt Benson wrote: Hi, I am concerned about potential confusion with Apache Commons Weaver [1]. So it might also be a trademark related issue. Weave has a TM registration pending from Intuit in the software space. There's also OIC Weave - which is data visualization software. No judgement - just things to consider and weigh (and that will need to be dealt with when you handle the podling name search) --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache MRQL 0.9.0 incubating (RC5)
Signatures look ok Hashes look ok License file looks fine (assuming no other 3rd party files licenses involved) RAT report looks good. +1 (binding) Good luck guys and congrats! - Henry On Mon, Oct 14, 2013 at 5:37 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: Hello, This is a call for a vote on Apache MRQL 0.9.0 incubating. This is our third try for our first release. We have resolved all the issues that have been discussed in our previous tries. Apache MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Hama, and Spark. A vote was held on the MRQL developer mailing list and it passed with three +1 PPMC votes, and zero -1 or 0 votes (see the vote thread [1] and result thread [2]), and now requires a vote on this list. The vote will be open for 72 hours and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache MRQL 0.9.0-incubating [ ] -1 Do not release this package because ... The release tarballs, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.0-incubating-RC5/ The release candidate consists of the following source distribution archives: - mrql-dist-0.9.0-incubating-src.[tar.gz|zip] SHA1 of TGZ: C99D 6789 BD67 8764 52AC DF5F 0F0D 4D72 6106 2141 SHA1 of ZIP: BEBA FE68 6A77 38BC 937C 24B3 959A 400D 001F B39F You can compile the sources using 'mvn install'. In addition, the following supplementary binary distributions are provided for user convenience at the same location: - mrql-dist-0.9.0-incubating-bin.[tar.gz|zip] SHA1 of TGZ: 4C04 E4F5 36F5 631E 6552 AB2E 8CBB 6171 2942 AF90 SHA1 of ZIP: 6165 8DCD 178C 094D 21E3 3B1B AA46 1028 9CB6 B5F7 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemrql-140/ The release candidate has been signed through the key 798764F1 in: http://www.apache.org/dist/incubator/mrql/KEYS The release candidate is based on the sources tagged with MRQL-0.9.0-incubating-RC5 in: https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=7386f5d7edeea21d38e7a6c95e8fbe5e59e27d26 RAT check: http://people.apache.org/~fegaras/dist/mrql-0.9.0-incubating-RC5/rat.txt To learn more about Apache MRQL, please visit: http://wiki.apache.org/mrql/ Thanks, Leonidas Fegaras [1] http://markmail.org/message/5okv2n6lshd3tgh6 [2] http://markmail.org/message/alyra637j5djxcrv - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache MRQL 0.9.0 incubating (RC5)
Apologize for the delay @MRQL guys. Just casted my +1 binding VOTE. Congrats! - Henry On Wed, Oct 30, 2013 at 7:28 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: Hello, It has been 16 days since we opened this vote for our first MRQL release. We have collected two IPMC votes but we still need one more IPMC vote to approve the release. We are planning to close this vote on Monday and declare it void if we do not get another IPMC vote. This is our first release and we have spent a lot of time to migrate our old source code to the Apache infrastructure and to adapt the Apache policies in all parts of the project. Please check our release and vote on releasing Apache MRQL 0.9.0 incubating. Thank you Leonidas Fegaras On 10/14/2013 07:37 AM, Leonidas Fegaras wrote: Hello, This is a call for a vote on Apache MRQL 0.9.0 incubating. This is our third try for our first release. We have resolved all the issues that have been discussed in our previous tries. Apache MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Hama, and Spark. A vote was held on the MRQL developer mailing list and it passed with three +1 PPMC votes, and zero -1 or 0 votes (see the vote thread [1] and result thread [2]), and now requires a vote on this list. The vote will be open for 72 hours and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache MRQL 0.9.0-incubating [ ] -1 Do not release this package because ... The release tarballs, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.0-incubating-RC5/ The release candidate consists of the following source distribution archives: - mrql-dist-0.9.0-incubating-src.[tar.gz|zip] SHA1 of TGZ: C99D 6789 BD67 8764 52AC DF5F 0F0D 4D72 6106 2141 SHA1 of ZIP: BEBA FE68 6A77 38BC 937C 24B3 959A 400D 001F B39F You can compile the sources using 'mvn install'. In addition, the following supplementary binary distributions are provided for user convenience at the same location: - mrql-dist-0.9.0-incubating-bin.[tar.gz|zip] SHA1 of TGZ: 4C04 E4F5 36F5 631E 6552 AB2E 8CBB 6171 2942 AF90 SHA1 of ZIP: 6165 8DCD 178C 094D 21E3 3B1B AA46 1028 9CB6 B5F7 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemrql-140/ The release candidate has been signed through the key 798764F1 in: http://www.apache.org/dist/incubator/mrql/KEYS The release candidate is based on the sources tagged with MRQL-0.9.0-incubating-RC5 in: https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=7386f5d7edeea21d38e7a6c95e8fbe5e59e27d26 RAT check: http://people.apache.org/~fegaras/dist/mrql-0.9.0-incubating-RC5/rat.txt To learn more about Apache MRQL, please visit: http://wiki.apache.org/mrql/ Thanks, Leonidas Fegaras [1] http://markmail.org/message/5okv2n6lshd3tgh6 [2] http://markmail.org/message/alyra637j5djxcrv - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona as an incubated project
Glad finally see the VOTE thread happening =) +1 (binding) - Henry On Tue, Oct 8, 2013 at 6:29 PM, Olivier Lamy ol...@apache.org wrote: Hi, Since discussion about the Sirona seems done, I'd like to call a vote for Sirona to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/SironaProposal Let's keep this vote open for three business days. [ ] +1 Accept Sirona into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Sirona because... ## page was renamed from MonitoringProposal = Apache Sirona = == Abstract == Apache Sirona aims to provide a simple but extensible monitoring solution for Java applications. Apache Sirona provides two kind of components : * Apache Sirona Core to provide a base framework for monitoring/recording a Java application. * Default based plugins * Apache Sirona base reporting web application (provide a basic reporting on recorded figures). == Background == Currently, Apache Sirona source is hosted in Apache Commons Sandbox scm. The development has begun few years ago but goes to dormant statut. == Rationale == Currently users who need some monitoring need to use some non Open Source solutions or GPL solutions. The goal is to provide a solution based on the Apache License. == Initial Goals == Apache Sirona doesn't have any release currently. The initial goal of this project will be to build community in the spirit of the Apache Way, and to address new features and bug-fixes of the first releases. === Current Status === Intent of the proposal is to build a diverse community of developers around Sirona. Sirona started in the Apache Commons Sandbox, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Apache Sirona stakeholders desire to expand the user and developer base of Apache Sirona further in the future == Known Risks == === Orphaned Products === Sirona is a new product. So without community adoption the risks of it being orphaned exist. === Inexperience with Open Source === The code has been developed in Apache Commons Sandbox mostly by Romain Manni-Bucau and Olivier Lamy who intimately familiar with the Apache model for open-source development and is experienced with working with new contributors. === 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 Apache Sirona will be developed on salaried and volunteer time. === Relationships with Other Apache Products === Apache Sirona depends upon other Apache Projects: Velocity and various Apache Commons components and build systems like Maven. === 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 Apache Sirona to become an Apache project. == Documentation == Docs: http://commons.apache.org/sandbox/commons-monitoring/ == Initial Source == https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk == 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 : == Cryptography == Apache Sirona does not depend upon any cryptography tools or libraries. == Required Resources == === Mailing lists === * sirona-private (with moderated subscriptions) * sirona-dev * sirona-commits * sirona-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/sirona == Issue Tracking == JIRA Sirona (key: SIRONA) == Other Resources == The existing code already has unit and integration tests so we would like to use Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committer == * Romain Manni-Bucau (rmannibu...@apache.org) * Jean-Louis Monteiro (jlmonte...@apache.org) * Fred Zhang (no ASF account) * Fabrice Bacchella (no ASF account) * Christian Grobmeier (grobme...@apache.org) == Affiliations == * Olivier Lamy, Ecetera * Fred Zhang, Ecetera == Sponsors == === Champion === * Olivier Lamy (ol...@apache.org) === Nominated Mentors === * Olivier Lamy (ol...@apache.org) * Henri Gomez (hgo...@apache.org) * Jean-Baptiste Onofré
Re: [RESULTS] Usergrid BaaS Stack for Apache Incubator (revised proposal)
Welcome to ASF incubator Usergrid =) - Henry On Thu, Oct 3, 2013 at 9:49 AM, Dave snoopd...@gmail.com wrote: I am officially closing the vote. We have 11 binding +1 votes, 4 non-binding votes and no -1 notes. Usergrid is now officially part of the Apache Incubator. Thanks to everybody who helped put together the proposal, those who joined the discussion, those who voted and the Usergrid community. +1 binding votes Afkham Azeez Alan D. Cabrera Alex Karasulu Ate Douma Bertrand Delacretaz Chip Childers David Nalley Henry Saputra Jim Jagielski Luciano Resende Marvin Humphrey +1 non-binding Larry McCay Lewis John Mcgibbney Lieven Govaerts Raminder Singh Totals 11 binding +1 votes 4 non-binding +1 votes 0 -1 votes Thanks, Dave PS. this also happens to be the 2nd anniversary of the day that Usergrid was released on Github. Happy Birthday Usergrid! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)
+1 (binding) Good luck guys - Henry On Mon, Sep 30, 2013 at 12:27 PM, Dave snoopd...@gmail.com wrote: I would like to call for a new vote on Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. The original proposal has been revised to name Dave Johnson as the Champion and to bring Jim Jagielski back in as a Mentor and to add John Lewis Mcgibbney as a Mentor. I also add some text to the Initial Committers section and a new Interested Contributors section to list those who have expressed interest in contributing. Here is a link to the revised proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on
Re: [VOTE] Accept Aurora for Apache Incubation
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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] first release of Apache Blur (incubating)
+1 (binding) congrats! On Mon, Sep 23, 2013 at 5:50 PM, Aaron McCurry amccu...@gmail.com wrote: We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Spark 0.8.0-incubating (RC6)
Cast vote as IPMC for the record: +1 (binding) Thanks, Henry On Fri, Sep 20, 2013 at 1:56 PM, Patrick Wendell pwend...@gmail.com wrote: Please vote on releasing the following candidate as Apache Spark (incubating) version 0.8.0. This will be the first incubator release for Spark in Apache. The tag to be voted on is v0.8.0-incubating (commit 3b85a85): https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=3b85a8558da2c87873c85f227a189e45bf16b65d The release files, including signatures, digests, etc can be found at: http://people.apache.org/~pwendell/spark-0.8.0-incubating-rc6/files/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/pwendell.asc The staging repository for this release can be found at: https://repository.apache.org/content/repositories/orgapachespark-059/ The documentation corresponding to this release can be found at: http://people.apache.org/~pwendell/spark-0.8.0-incubating-rc6/docs/ A vote on this release has passed within the Spark PPMC [1] including +1 votes from our IPMC mentors (Chris Mattman and Henry Saputra). Please vote on releasing this package as Apache Spark 0.8.0-incubating! The vote is open until Monday, September 23rd at 21:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Spark 0.8.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Spark, please see http://spark.incubator.apache.org/ [1] http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201309.mbox/%3CCABPQxsvS14wfiABj32b_%2BgtLafmDog%3DcbWjn7v4FoqG5g-a7mQ%40mail.gmail.com%3E - Patrick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] first milestone release of Apache Drill (incubating)
Signature looks good Hashes looks good +1 (binding) Congrats for the first release guys - Henry On Tuesday, September 17, 2013, Ted Dunning wrote: We've held a vote on drill-dev to release the first milestone release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3ccaka9qdkmxjp-r8v+zwabm5e4b5osrypjyp+dupvq2lr-d70...@mail.gmail.com%3E The vote passed with 4 x +1 binding votes 7 x +1 non-binding votes An additional non-binding +1 vote was received after the vote closed. A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201309.mbox/%3CCAKa9qDn1+TnKVP=p_=Lh==mOS=azctuz6_qvsm4u3z4gdhh...@mail.gmail.com%3E The source only release artifactscan be found together with signatures here: http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4/ Please vote on this release
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
This is good news! Looking forward for this project into ASF incubation =) - Henry On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski j...@jagunet.com wrote: I would like to propose Usergrid, a multi-tenant Backend-as-a-Service stack for web mobile applications based on RESTful APIs, as an Apache Incubator podling. Here is a link to the proposal: https://wiki.apache.org/incubator/UsergridProposal It is also pasted below: = Usergrid Proposal = == Abstract == Usergrid is a multi-tenant Backend-as-a-Service stack for web mobile applications, based on RESTful APIs. == Proposal == Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed of an integrated distributed NoSQL database, application layer and client tier with SDKs for developers looking to rapidly build web and/or mobile applications. It provides elementary services (user registration management, data storage, file storage, queues) and retrieval features (full text search, geolocation search, joins) to power common app features. It is a multi-tenant system designed for deployment to public cloud environments (such as Amazon Web Services, Rackspace, etc.) or to run on traditional server infrastructures so that anyone can run their own private BaaS deployment. For architects and back-end teams, it aims to provide a distributed, easily extendable, operationally predictable and highly scalable solution. For front-end developers, it aims to simplify the development process by enabling them to rapidly build and operate mobile and web applications without requiring backend expertise. == Background == Developing web or mobile applications obviously necessitates writing and maintaining more than just front-end code. Even simple applications can implicitly rely on server code being run to store users, perform database queries, serve images and video files, etc. Developing and maintaining such backend services requires skills not always available or expected of app development teams. Beyond that, the proliferation of apps inside of companies leads to the creation of many different, ad-hoc, unequally maintained backend solutions created by employees and contractors alike and hosted on a wide variety of environments. This is causing poor resource usage, operational issues, as well as security, privacy compliance concerns. In response to this problem, companies have long tried to standardize their server-side stack or unify them behind an ESB or API strategy. Backends-as-a-Service follow a similar approach but their unique characteristic is strongly tying 1) a persistence tier (typically a database), 2) a server-side application tier delivering a set of common services and 3) a set of client-side application interface mechanisms. For example, a BaaS could package 1) MongoDB with 2) a node.js application that offers access through 3) WebSockets. In the case of Usergrid, the trifecta is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. The Backend-as-a-Service approach has steadily gained popularity in the last few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, each operating tens of thousands of apps for tens of thousands of developers. The trend has already reached large organizations as well, with global companies such as Korea Telecom internally building a privately-run BaaS platform. But so far, there have been limited options for developers that want a non-proprietary, open option for hosting and providing these services themselves, or for enterprise and government users who want to provide these capabilities from their own data centers, especially on a very large scale. == Rationale == The issue this proposal deals with is implicit in the name. Backend-as-a-Service platforms are usually offered solely as proprietary cloud services. They are typically closed sourced, hosted on public clouds, and require subscription payment. Usergrid opens the playing field, by making a fully-featured BaaS platform freely available to all. This includes developers that previously could not afford them, such as mobile enthusiasts, small boutiques, and cost-sensitive startups. This also includes large companies that benefit from a reference implementation they can deploy in trust, or extend to their needs without losing time writing less-vetted, less-performant boilerplate functionality. Usergrid has been open source since 2011 and has grown as an independent project, garnering 11 primary committers, 35 total contributors, 260+ participants on its mailing list, with 3,700+ commits, 200+ external contributions, 350+ stars and 100+ forks on Github, not to mention several large scale production deployments at major global companies in the media, retail, telecommunication and government spaces. The Apache Software Foundation's Way, by putting community before the code, will help Usergrid establish a vibrant, more diverse community to
Re: [VOTE] Accept Storm into the Incubator
+1 (binding) On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: Discussion about the Storm proposal has subsided, issues raised now seemingly resolved. I'd like to call a vote to accept Storm as a new Incubator podling. The proposal is included below and is also at: https://wiki.apache.org/incubator/StormProposal Let's keep the vote open for four working days, until 18 September. [ ] +1 Accept Storm into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Storm because... Doug = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm’s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com, which will seed the Apache git repository. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, 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 low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as Zookeeper, Thrift, Mesos). We could include additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near future. == Known Risks == === Orphaned Products === The risk of the Storm project being abandoned is minimal. There are at least 50 organizations (Twitter, Yahoo!, Microsoft, Groupon, Baidu, Alibaba, Alipay, Taobao, PARC, RocketFuel etc) are
Re: [PROPOSAL] Storm for Apache Incubator
Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, Sep 4, 2013 at 1:07 AM, Nathan Marz nat...@nathanmarz.com wrote: Hi everyone, I'd like to propose Storm to be an Apache Incubator project. After much thought I believe this is the right next step for the project, and I look forward to hearing everyone's thoughts and feedback! Here's a link to the proposal: https://wiki.apache.org/incubator/StormProposal The proposal is also pasted below. -Nathan = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm’s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com , which will seed the Apache git repository. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, 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 low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as
Re: [VOTE] Graduate Apache Curator as an Apache Top Level Project
+1 Good luck guys - Henry On Wed, Aug 28, 2013 at 10:44 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: This message is opening a VOTE to graduate the Apache Curator podling from the Apache Incubator as an Apache Top Level Project. Apache Curator entered the Incubator in April of 2013. We have made significant progress with the project since moving to Apache. We currently have 4 committers listed on our status page [1] including 2 who were accepted after the podling was formed. A VOTE was held on the curator-dev group with 8 binding +1 and 2 non-binding +1 votes for graduation [2]. A VOTE was also held to adopt the graduation resolution (below) with 7 +1 votes for acceptance [3]. According to Ohloh, Curator has a large, active development team [4]. During incubation, Curator: * Produced 4 releases * Added 2 new Committer/PPMC members and showed constant community activities * Cleared IP on code * Developed roadmap(s) for major and minor releases in a community process [5] * Established that Apache Curator is a suitable name [6] * Showed that its community is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices Please cast your vote: [ ] +1 Graduate the Apache Curator podling from Apache Incubator as a TLP [ ] +0 Indifferent to the graduation status of Apache Curator podling [ ] -1 Reject graduation of Apache Curator podling from Apache Incubator because ... We'll run the vote for at least 72 hours. [1] http://curator.incubator.apache.org/team-list.html#Contributors [2] http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C44CD80F8-10B1-4FBA-A9D9-6DDEA7280FA5%40jordanzimmerman.com%3E [3] http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C3859DF43-460C-406E-B816-DD9F4049B4DC%40jordanzimmerman.com%3E [4] http://www.ohloh.net/p/apache-curator/factoids#FactoidTeamSizeLarge [5] https://issues.apache.org/jira/browse/CURATOR#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-28 Sincerely, The Apache Curator Team Resolution: X. Establish the Apache Curator 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 library and tools for working with Apache ZooKeeper. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Curator Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Curator Project be and hereby is responsible for the creation and maintenance of software related to a library and tools for working with Apache ZooKeeper; and be it further RESOLVED, that the office of Vice President, Apache Curator 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 Curator Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Curator 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 Curator Project: * Jordan Zimmerman (randgalt) * Jay Zarfoss (zarfide) * Eric Tschetter (cheddar) * Ioannis Canellos (iocanel) * Patrick Hunt (phunt) * Mahadev Konar (mahadev) * Luciano Resende (lresende) * Enis Söztutar (enis) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jordan Zimmerman be appointed to the office of Vice President, Apache Curator, 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 Curator 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 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
Re: [PROPOSAL] Aurora for Incubation
Hi Marvin, Dave, +1 for dev@, private@ and commits@ lists for start. If Aurora picks up more clients as user which making dev@ list too noisy we could always request for user@ list. - Henry On Wed, Aug 28, 2013 at 9:37 AM, Marvin Humphrey mar...@rectangular.comwrote: On Tue, Aug 27, 2013 at 4:36 PM, Dave Lester d...@ischool.berkeley.edu wrote: We recommended an aurora-user list because Aurora is currently production-ready and used by Twitter. We anticipate that once we have an initial release in the Incubator, it will be straightforward to for current Mesos users to begin using Aurora. Development discussion would still made on aurora-dev. How does that sound? See http://wiki.apache.org/incubator/MailingListOptions. For small-ish projects, we recommend that user traffic be shunted onto the dev list at first because we have observed that great new contributors tend to emerge from the pool of highly engaged users. You want to foster conversations which flow seemlessly from how do I do this to how do I implement this to welcome new committer so-and-so. Breaking out a separate user@ list is not generally desirable until the project has hit critical mass and dev list traffic is high. Community growth is a difficult problem that is central to the Apache mission, and it will be an important challenge for the proposed Aurora podling since all the initial contributors work for the same company (Twitter). It will be tempting to make architectural decisions in private for the sake of efficiency, but doing so will stunt the project's growth. It's important to hold project discussions out in the open where as many people as possible can witness them and potentially jump in. The issues/notifications/ci list is a different story. Making the dev list a good read with a high signal-to-noise ratio is a good recruitment tactic. There are often people who are interested in high-level development conversations and user discussions but who get annoyed by CI spam and issue tracker trivialities. In my opinion, it would be fruitful to start off with just dev@, private@and commits@ lists; discuss adding a notifications@ list as one of the first community decisions you make on your dev@ list; and perhaps add a user@list later when the time is ripe. However, all of these decisions are ultimately up to the community; us Incubator denizens are just providing the best guidance we can based on what seems to have worked in the past. Marvin Humphrey
Re: [PROPOSAL] Aurora for Incubation
Hi Dave, This looks like interesting project and good contributions from Twitter engineering. But given that close relationship with Apache Mesos, wouldn't it be more effective to be delivered as extension or feature contribution to Apache Mesos? - Henry On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester d...@ischool.berkeley.eduwrote: Hi All, We're pleased to share a draft ASF incubation proposal for Aurora, a service scheduler used to schedule jobs onto Apache Mesos that we've developed at Twitter. Aurora provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. The complete proposal can be found: https://wiki.apache.org/incubator/AuroraProposal, and also pasted below. In particular, we'd love to add additional mentors to the project. Your feedback is appreciated. Dave = Abstract = Aurora is a service scheduler used to schedule jobs onto Apache Mesos. = Proposal = Aurora is a scheduler that provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. Aurora builds on top of Apache Mesos and provides common features that allow any site to run large scale production applications. While the project is currently used in production at Twitter, we wish to develop a community to increase contributions and see it thrive in the future. = Background = The initial development of Aurora was done at Twitter, and is planned to be open sourced. This proposal is for Aurora to join the Apache Incubator. = Rationale = While the Apache Mesos core focuses on distributing individual tasks across nodes in a cluster, typical services consist of dozens or hundreds of replicas of tasks. As a service scheduler, Aurora provides the abstraction of a job to bundle and manage these tasks. Aurora provides many key functionalities centered around a job, including: definition, the concept of an instance and the serverset, deployment and scheduling, health checking, and introspection. It also allows cross-cutting concerns to be handled like observability and log collection. = Current Status = == Meritocracy == By submitting this incubator proposal, we’re expressing our intent to build a diverse developer community around Aurora that will conduct itself according to The Apache Way and use meritocratic means of accepting contributions. Several members of the Aurora team overlap with Apache Mesos, which successfully graduated from the Incubator and has embraced a meritocratic model of governance; we plan to follow a similar path forward with Aurora and believe that a synergy between both projects will make this even easier. == Community == Aurora is currently being used internally at Twitter. By open sourcing the project, we hope to extend our contributor base significantly and create a vibrant community around the project. == Core Developers == Aurora is currently being developed by a team of seven engineers at Twitter. == Alignment == The ASF is a natural choice to host the Aurora project, given the goal of open sourcing the project and fostering a community to grow and support the software. Additionally, Aurora integrates with Apache Mesos, and Apache ZooKeeper for service discovery. We believe that inclusion within Apache will build stronger ties between these projects, and create further alignment between their goals and communities. = Known Risks = == Orphaned Products == The core developers plan to continue working full time on the project, and there is very little risk of Aurora being abandoned since it is running hundreds of services as part of Twitter’s infrastructure. Additionally, members of the Mesos community beyond Twitter have expressed interest in an advanced scheduler like Aurora (see “Interested Parties” section); we believe that need will drive some of the community involvement necessary for the project to incubate successfully. == Inexperience with Open Source == Initial Aurora committers have varying levels of experience using and contributing to Open Source projects, however by working with our mentors and the Apache community we believe we will be able to conduct ourselves in accordance with Apache Incubator guidelines. The close relationship between the Aurora team and Apache Mesos means there is an awareness of the incubation process and a willingness to embrace The Apache Way. == Homogenous Developers == The initial set of committers are from a single organization, however we expect that once approved for incubation the project will attract contributors from more organizations. We have already had conversations with other companies who have expressed 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
Re: [PROPOSAL] Aurora for Incubation
HI Dave, thanks for your reply. Yeah I think it would be super useful to highlight ability to use Aurora with other systems. Another question: looks like from the proposal, it does not rely on Mesos library as external dependencies at all? Like other incubator projects, would you consider not having aurora-user and aurora-issues lists at the beginning of incubation? I think we would like to have dev list as the main list to have development discussion in the early phase of incubation (other IPMCs probably would recommend the same) Thanks again, - Henry On Mon, Aug 26, 2013 at 4:13 PM, Dave Lester d...@ischool.berkeley.eduwrote: Hi Henry, Great question. Multiple schedulers are actively being developed for Mesos, including Aurora by Twitter, Chronos by Airbnb ( http://nerds.airbnb.com/introducing-chronos/), one called Marathon that I understand will be open sourced in the future, and I've spoken with several different folks at meetups who are developing their own. There is some overlap between these schedulers, but they also meet different use-cases so I still think it makes sense to create Aurora as a separate Apache project from the Mesos core. It's also worth noting (and perhaps this is something to highlight in the proposal itself) that a scheduler like Aurora could potentially be used with other systems should the community wish to pursue that development in the future. Dave On Mon, Aug 26, 2013 at 3:55 PM, Henry Saputra henry.sapu...@gmail.comwrote: Hi Dave, This looks like interesting project and good contributions from Twitter engineering. But given that close relationship with Apache Mesos, wouldn't it be more effective to be delivered as extension or feature contribution to Apache Mesos? - Henry On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester d...@ischool.berkeley.eduwrote: Hi All, We're pleased to share a draft ASF incubation proposal for Aurora, a service scheduler used to schedule jobs onto Apache Mesos that we've developed at Twitter. Aurora provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. The complete proposal can be found: https://wiki.apache.org/incubator/AuroraProposal, and also pasted below. In particular, we'd love to add additional mentors to the project. Your feedback is appreciated. Dave = Abstract = Aurora is a service scheduler used to schedule jobs onto Apache Mesos. = Proposal = Aurora is a scheduler that provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. Aurora builds on top of Apache Mesos and provides common features that allow any site to run large scale production applications. While the project is currently used in production at Twitter, we wish to develop a community to increase contributions and see it thrive in the future. = Background = The initial development of Aurora was done at Twitter, and is planned to be open sourced. This proposal is for Aurora to join the Apache Incubator. = Rationale = While the Apache Mesos core focuses on distributing individual tasks across nodes in a cluster, typical services consist of dozens or hundreds of replicas of tasks. As a service scheduler, Aurora provides the abstraction of a job to bundle and manage these tasks. Aurora provides many key functionalities centered around a job, including: definition, the concept of an instance and the serverset, deployment and scheduling, health checking, and introspection. It also allows cross-cutting concerns to be handled like observability and log collection. = Current Status = == Meritocracy == By submitting this incubator proposal, we’re expressing our intent to build a diverse developer community around Aurora that will conduct itself according to The Apache Way and use meritocratic means of accepting contributions. Several members of the Aurora team overlap with Apache Mesos, which successfully graduated from the Incubator and has embraced a meritocratic model of governance; we plan to follow a similar path forward with Aurora and believe that a synergy between both projects will make this even easier. == Community == Aurora is currently being used internally at Twitter. By open sourcing the project, we hope to extend our contributor base significantly and create a vibrant community around the project. == Core Developers == Aurora is currently being developed by a team of seven engineers at Twitter. == Alignment == The ASF is a natural choice to host the Aurora project, given the goal of open sourcing the project and fostering a community to grow and support the software. Additionally, Aurora integrates with Apache Mesos, and Apache ZooKeeper for service discovery. We believe that inclusion within Apache will build stronger ties between these projects, and create further alignment between their goals
Re: [VOTE]: Accept Sentry in Apache Incubator
Should be good addition to ASF family =) +1 (binding) Good luck guys - Henry On Mon, Aug 5, 2013 at 6:23 AM, Shreepadma Venugopalan shreepa...@cloudera.com wrote: Following the discussions last week, I'm calling a vote to accept Sentry as a new project in the Apache Incubator. The proposal draft is available at: https://wiki.apache.org/incubator/SentryProposal and is also pasted to the bottom of this email. It is identical to what was proposed except for a) addition of two new mentors, and b) removal of the user list for now, per Marvin's suggestion. The proposal thread is available at: http://goo.gl/bvvJPh [ ] +1 Accept Sentry in the Incubator [ ] +/-0 Don't care [ ] -1 Don't accept Sentry in the Incubator because... Thanks. Shreepadma = Sentry - A fine-grained Authorization System for the Hadoop ecosystem = == Abstract == Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop cluster. Sentry can be used to enforce various access policy rules when accessing data stored on Hadoop Distributed File System through various Hadoop ecosystem components such as Apache Hive, Apache Pig or others. == Proposal == Traditionally, user access control in Apache Hadoop has been implemented using file based permissions on HDFS. Following the UNIX permissions model, HDFS offers all or nothing semantics allowing administrator to configure system to allow certain users or user groups read, write or perform both operations on files. This system does not enable more fine grained permissions that allow access policies for logical parts within one file. Furthermore, this model can't be used to restrict access to the rich set of objects in the metadata catalog that are stored outside HDFS. Sentry will provide true role-based fine-grained user access control for Apache Hadoop and its ecosystem components such as Hive, Pig or HBase. This includes providing fine- grained role based access to both data as well as the metadata, which provides a rich object based abstraction such as databases, tables or columns. == Background == Sentry was initially developed by Cloudera to allow users fine grained access to data as well as the metadata in Apache Hadoop. Sentry has been maintained as an open source project on Cloudera’s github. Sentry was previously called “Access”. All code in Sentry is open source and has been made publicly available under the Apache 2 license. During this time, Sentry has been formally released two times as versions 1.0.0 and 1.1.0. == Rationale == Currently, users don't have a way to achieve fine grained enforceable user access control to data stored in HDFS and their associated metadata. While users can use file based permissions to control access to specific directories and files, it is insufficient because access can't be restricted to file parts i.e., to specific lines or logical columns. In the absence of such support, users have to resort to duplicating data. Furthermore, file based permissions are insufficient to provide any form of access control to the metadata that provides an object abstraction such as databases, tables, columns or partitions over the data stored in HDFS. Current Sentry developers subscribe to the mission of ASF and are familiar with the open source development process. Several members are already committers and PMC members of various other Apache projects. == Initial Goals == Sentry is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. == Current Status == === Meritocracy === Intent of the proposal is to build a diverse community of developers around Sentry. Sentry started as a open source project on Github, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Sentry stakeholders desire to expand the user and developer base of Sentry further in the future. The current sets of developers in Sentry are committed to building a strong user base and open source community around the project. Development discussions within the current team have been on a public mailing [[ https://groups.google.com/a/cloudera.org/forum/#!forum/access-dev | list]]. === Core Developers === The core developers for the Sentry project are Brock Noland, Shreepadma Venugopalan, Prasad Mujumdar and Jarek Jarcec Cecho. Other contributors include Arvind Prabhakar and Xuefu Zhang. All engineers have deep expertise in Hadoop and various other ecosystem components. === Alignment === Sentry complements the access control
Re: [PROPOSAL] Samza Proposal
Well, usually VOTE is conducted after discussion had calmed down. Looks like this time the VOTE starts even though there were some question about the proposal. Would be great to actually add links to the comparisons in the thread even though the VOTE had concluded. - Henry On Wed, Jul 31, 2013 at 1:29 PM, Phillip Rhodes motley.crue@gmail.comwrote: Same here. Not that it matters as far as admission to the incubator (that vote is over now anyway), but I think a lot of people (including potential users of Samza) would like to see more about how it compares contrasts with other stream oriented systems. Phil This message optimized for indexing by NSA PRISM On Fri, Jul 26, 2013 at 8:27 PM, Alex Karasulu akaras...@apache.org wrote: +1 I would love to see the documents comparing and contrasting Samza with MUPD8 and Storm. On Sat, Jul 27, 2013 at 2:53 AM, Enis Söztutar e...@apache.org wrote: +1 on incubation. Enis On Tue, Jul 23, 2013 at 7:17 PM, Chris Riccomini criccomini@gmail.comwrote: Hey Henry and Debo, Thanks for calling this out. Samza's feature set includes: - *Simpe API:* Unlike most low-level messaging system APIs, Samza provides a very simple call-back based process message API that should be familiar to anyone that's used Map/Reduce. - *Managed state:* Samza manages snapshotting and restoration of a stream processor's state. Samza will restore a stream processor's state to a snapshot consistent with the processor's last read messages when the processor is restarted. - *Fault tolerance:* Samza will work with YARN to restart your stream processor if there is a machine or processor failure. - Durability: Samza uses Kafka to guarantee that no messages will ever be lost. - *Scalability:* Samza is partitioned and distributed at every level. Kafka provides ordered, partitioned, replayable, fault-tolerant streams. YARN provides a distributed environment for Samza containers to run in. - *Pluggable:* Though Samza works out of the box with Kafka and YARN, Samza provides a pluggable API that lets you run Samza with other messaging systems and execution environments. - *Processor isolation:* Samza works with Apache YARN, which supports processor security through Hadoop's security model, and resource isolation through Linux CGroups. Some of these feature are available in S4, and some are not. The same holds true for Storm. The open source stream processing systems that are available are actually quite young, and no single system offers a complete solution. Problems like how a stream processor's state (e.g. counts) should be managed, whether a stream should be buffered remotely on disk or not, what to do when duplicate messages are received or messages are lost, and how to model underlying messaging systems are all pretty new. Samza's main differentiators are: - State is modeled as a stream. When a processor fails and is restarted, the state stream is entirely replayed to restore it. - Streams are ordered, partitioned, replayable, and fault tolerant. - YARN is used for processor isolation, security, and fault tolerance. - All streams are materialized to Kafka. If you guys are interested, I have much more in-depth documents comparing and contrasting Samza with MUPD8 and Storm. Cheers, Chris On Tue, Jul 23, 2013 at 6:48 PM, Henry Saputra henry.sapu...@gmail.com wrote: Looks like this is similar to S4 (http://incubator.apache.org/s4/) which allow stream and real time data processing via DAG? - Henry On Tue, Jul 23, 2013 at 10:47 AM, Chris Ricco criccomini@gmail.com wrote: Hey All, Sending along an incubator proposal for Samza. Thanks! Chris https://wiki.apache.org/incubator/SamzaProposal == Abstract == Samza is a stream processing system for running continuous computation on infinite streams of data. == Proposal == Samza provides a system for processing stream data from publish-subscribe systems such as Apache Kafka. The developer writes a stream processing task, and executes it as a Samza job. Samza then routes messages between stream processing tasks and the publish-subscribe systems that the messages are addressed to. == Background == Samza was developed at LinkedIn to enable easier processing of streaming data on top of Apache Kafka. Current use cases include content processing pipelines, aggregating operational log data, data ingestion into distributed database infrastructure, and measuring user activity across different
Re: [PROPOSAL] Samza Proposal
NP Good luck and congrats - Henry On Wednesday, July 31, 2013, Chris Riccomini wrote: Hey Guys, Jakob (the project Champion) is in the process of getting all of the resources requested in our proposal (JIRA, Hudson, webspace, etc). As soon as we have webspace allocated, we'll put the Samza site up, which has all of these docs on it. Henry, as you said, I'll follow up with this thread when they're up. Cheers, Chris On Wed, Jul 31, 2013 at 2:04 PM, Henry Saputra henry.sapu...@gmail.comjavascript:; wrote: Well, usually VOTE is conducted after discussion had calmed down. Looks like this time the VOTE starts even though there were some question about the proposal. Would be great to actually add links to the comparisons in the thread even though the VOTE had concluded. - Henry On Wed, Jul 31, 2013 at 1:29 PM, Phillip Rhodes motley.crue@gmail.comwrote: Same here. Not that it matters as far as admission to the incubator (that vote is over now anyway), but I think a lot of people (including potential users of Samza) would like to see more about how it compares contrasts with other stream oriented systems. Phil This message optimized for indexing by NSA PRISM On Fri, Jul 26, 2013 at 8:27 PM, Alex Karasulu akaras...@apache.org wrote: +1 I would love to see the documents comparing and contrasting Samza with MUPD8 and Storm. On Sat, Jul 27, 2013 at 2:53 AM, Enis Söztutar e...@apache.org wrote: +1 on incubation. Enis On Tue, Jul 23, 2013 at 7:17 PM, Chris Riccomini criccomini@gmail.comwrote: Hey Henry and Debo, Thanks for calling this out. Samza's feature set includes: - *Simpe API:* Unlike most low-level messaging system APIs, Samza provides a very simple call-back based process message API that should be familiar to anyone that's used Map/Reduce. - *Managed state:* Samza manages snapshotting and restoration of a stream processor's state. Samza will restore a stream processor's state to a snapshot consistent with the processor's last read messages when the processor is restarted. - *Fault tolerance:* Samza will work with YARN to restart your stream processor if there is a machine or processor failure. - Durability: Samza uses Kafka to guarantee that no messages will ever be lost. - *Scalability:* Samza is partitioned and distributed at every level. Kafka provides ordered, partitioned, replayable, fault-tolerant streams. YARN provides a distributed environment for Samza containers to run in. - *Pluggable:* Though Samza works out of the box with Kafka and YARN, Samza provides a pluggable API that lets you run Samza with other messaging systems and execution environments. - *Processor isolation:* Samza works with Apache YARN, which supports processor security through Hadoop's security model, and resource isolation through Linux CGroups. Some of these feature are available in S4, and some are not. The same holds true for Storm. The open source stream processing systems that are available are actually quite young, and no single system offers a c
Re: [PROPOSAL] Samza Proposal
Looks like this is similar to S4 (http://incubator.apache.org/s4/) which allow stream and real time data processing via DAG? - Henry On Tue, Jul 23, 2013 at 10:47 AM, Chris Ricco criccomini@gmail.comwrote: Hey All, Sending along an incubator proposal for Samza. Thanks! Chris https://wiki.apache.org/incubator/SamzaProposal == Abstract == Samza is a stream processing system for running continuous computation on infinite streams of data. == Proposal == Samza provides a system for processing stream data from publish-subscribe systems such as Apache Kafka. The developer writes a stream processing task, and executes it as a Samza job. Samza then routes messages between stream processing tasks and the publish-subscribe systems that the messages are addressed to. == Background == Samza was developed at LinkedIn to enable easier processing of streaming data on top of Apache Kafka. Current use cases include content processing pipelines, aggregating operational log data, data ingestion into distributed database infrastructure, and measuring user activity across different aggregation types. Samza is focused on providing an easy to use framework to process streams. It uses Apache YARN to provide a mechanism for deploying stream processing tasks in a distributed cluster. Samza also takes advantage of YARN to make decisions about stream processor locality, co-partition of streams, and provide security. Apache Kafka is also leveraged to provide a mechanism to pass messages from one stream processor to the next. Apache Kafka is also used to help manage a stream processor's state, so that it can be recovered in the event of a failure. Samza is written in Scala. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to reliably process large amounts of streaming data. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a reliable stream processing system such as Samza. While our use case of processing events from a large website like LinkedIn has driven the design of Samza, its uses are varied and we expect many new use cases to emerge. Samza provides a generic API to process messages from streaming infrastructure and will appeal to many users. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Samza following the Apache meritocracy model. Since Samza was initially developed in late 2011, we have had fast adoption and contributions by multiple teams at LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Samza is currently being used internally at LinkedIn. We hope to extend our contributor base significantly and invite all those who are interested in building large-scale distributed systems to participate. === Core Developers === Samza is currently being developed by four engineers at LinkedIn: Jay Kreps, Jakob Homan, Sriram Subramanian, and Chris Riccomini. Jakob is an ASF Member, Incubator PMC member and PMC member on Apache Hadoop, Kafka and Giraph. Jay is a member of the Apache Kafka PMC and contributor to various Apache projects. Chris has been an active contributor for several projects including Apache Kafka and Apache YARN. Sriram has contributed to Samza, as well as Apache Kafka. === Alignment === The ASF is the natural choice to host the Samza project as its goal of encouraging community-driven open-source projects fits with our vision for Samza. Additionally, many other projects with which we are familiar with and expect Samza to integrate with, such as Apache ZooKeeper, YARN, HDFS and log4j are hosted by the ASF and we will benefit and provide benefit by close proximity to them. == Known Risks == === Orphaned Products === The core 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
Re: [RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator
Hi All, Sorry for the delay, but the mailing lists are ready for MetaModel: priv...@metamodel.incubator.apache.org d...@metamodel.incubator.apache.org comm...@metamodel.incubator.apache.org Please subscribe to them by sending email to private-subscribe@, dev-subscribe@, and commits-subscribe@ The private@ list is moderated and only MetaModel's PPMC can subscribe to them. Thanks and looking forward seeing you guys in the dev@ lists =) - Henry On Wed, Jun 12, 2013 at 6:34 PM, Henry Saputra henry.sapu...@gmail.comwrote: Hi All, Thank you for everyone for participating and warm welcome for the MetaModel project proposal. The VOTE is now officially closed with the result (* means IPMC): +1s: Henry Saputra* Matt Franklin* Chris Mattmann* Noah Slater* Rahul Sharma Ankit Kumar Christian Grobmeier* Arvind Prabhakar* Kasper Sorensen Noah Slater* Manuel Van den Berg Joe Brockmeier* Suresh Marru* Ted Dunning* Rich Bowen Alan Cabrera* Marcel Offermans* Alex Karasulu* 0s: None -1s: None This means with 18 +1s (13 binding) and no 0 and -1 the proposal is accepted. I will continue with the bootstrap process to bring MetaModel into Apache incubator. Thank you again for those participated in the VOTE. Thanks, Henry On Thu, Jun 6, 2013 at 3:30 PM, Henry Saputra henry.sapu...@gmail.comwrote: Hi All, I'd like to call a VOTE for acceptance of MetaModel into the Apache incubator. The vote will close on June 12, 2013 at 6:00 PM (PST). [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is: http://wiki.apache.org/incubator/MetaModelProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Henry Saputra Champion for Apache MetaModel P.S. Here's my +1 (binding) - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org . === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties
Re: [VOTE] Accept Stratos proposal as an incubating project
+1 binding. Good luck guys! - Henry On Fri, Jun 14, 2013 at 2:49 PM, Ross Gardler rgard...@opendirective.comwrote: I would like to invite the IPMC vote to accept the Stratos proposal [1]. I want to clarify that this vote is for the Stratos project to enter the incubator as a standard podling under the existing incubation policy. The acceptance or otherwise of the probationary TLP idea is a separate issue that will be explored during the first month of incubation, potentially resulting in a further IPMC vote. This vote is *only* for accepting the Stratos project as a podling. [ ] +1 Accept the Stratos project as an incubating project [ ] +0 [ ] -1 Do not accept the Stratos project as an incubating project because... (provide reason) It's late on Friday evening here in the UK. I'll let this vote run well into next week to allow for the weekend. Thank you for your votes. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Ah ok thanks for the clarification Chris! - Henry On Wed, Jun 12, 2013 at 9:45 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hey Henry, Either way I don't think it's doctrine -- I've seen releases and voted on them with or without. I think it's nice to have a sha or sha1, but not required. Cheers, Chris ++ 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 ++ -Original Message- From: Henry Saputra henry.sapu...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 11, 2013 12:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) Does an incubator project release requires sha1 checksum too? From: http://www.apache.org/dev/release-signing.html: An SHA checksum *should* also be created and *must* be suffixed .sha Looks like it should but not required? - Henry On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12 . 0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d 7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12 . 0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12 . 0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Mesos
+1 binding Awesome work guys =) - Henry On Wed, Jun 12, 2013 at 1:03 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi All, The Apache Mesos community is ready to graduate. They have added committers and PPMC members while in the Incubator; have made a few releases; are discussing their issues on list and in the Apache way, and are inclusive and representative of Apache's goals as a Foundation. I'm extremely happy to put them up for Incubator graduation. We've VOTEd as a community to move forward with this: DISCUSS thread here: http://s.apache.org/XAu VOTE thread here: http://s.apache.org/K8C VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov Project Incubator status page here: http://incubator.apache.org/projects/mesos.html Board resolution pasted at bottom of email. Existing tallies from the community VOTE: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik * - indicates IPMC Please VOTE to graduate Apache Mesos from the Incubator. Though only Incubator PMC member VOTEs are binding, all are welcome to voice your opinion. I'll leave the VOTE open for at least 72 hours, and hopefully can get enough VOTEs in time to close it by Saturday or Sunday in time for the board meeting on 6/19. [ ] +1 Graduate Apache Mesos from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Mesos from the Incubator because.. Thanks everyone! Cheers, Chris ---board resolution 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 efficient cluster management, resource isolation and sharing across distributed applications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Mesos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mesos Project be and hereby is responsible for the creation and maintenance of software related to efficient cluster management, resource isolation and sharing across distributed applications; and be it further RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mesos 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 Mesos Project: * Ali Ghodsi a...@apache.org * Andy Konwinski and...@apache.org * Benjamin Hindhman b...@apache.org * Benjamin Mahler bmah...@apache.org * Brian McCalister bri...@apache.org * Ian Holsman i...@apache.org * Matei Alexandru Zahari ma...@apache.org * Chris Mattmann mattm...@apache.org * Tom White tomwh...@apache.org * Vinod Kone vinodk...@apache.org * Brenden Matthews bren...@apache.org * Thomas Marshall tmarsh...@apache.org * Charles Reiss wog...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be appointed to the office of Vice President, Apache Mesos, 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 Apache Mesos Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Mesos podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Mesos podling encumbered upon the Apache Incubator Project are hereafter discharged. ++ 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 ++
[RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator
Hi All, Thank you for everyone for participating and warm welcome for the MetaModel project proposal. The VOTE is now officially closed with the result (* means IPMC): +1s: Henry Saputra* Matt Franklin* Chris Mattmann* Noah Slater* Rahul Sharma Ankit Kumar Christian Grobmeier* Arvind Prabhakar* Kasper Sorensen Noah Slater* Manuel Van den Berg Joe Brockmeier* Suresh Marru* Ted Dunning* Rich Bowen Alan Cabrera* Marcel Offermans* Alex Karasulu* 0s: None -1s: None This means with 18 +1s (13 binding) and no 0 and -1 the proposal is accepted. I will continue with the bootstrap process to bring MetaModel into Apache incubator. Thank you again for those participated in the VOTE. Thanks, Henry On Thu, Jun 6, 2013 at 3:30 PM, Henry Saputra henry.sapu...@gmail.comwrote: Hi All, I'd like to call a VOTE for acceptance of MetaModel into the Apache incubator. The vote will close on June 12, 2013 at 6:00 PM (PST). [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is: http://wiki.apache.org/incubator/MetaModelProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Henry Saputra Champion for Apache MetaModel P.S. Here's my +1 (binding) - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We
Re: [VOTE] Accept Apache HotdoG into the Incubator
+1 binding. Good luck guys - Henry On Wed, Jun 12, 2013 at 11:22 AM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: All, I'd like to call a VOTE for the acceptance of Apache HotdoG into the Incubator. I'll leave the VOTE open for the rest of the week and close it out Monday, June 17th early am PT. [ ] +1 Accept Apache HotdoG into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache HotdoG because... Full Proposal is pasted at the end of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. This is a second pass at this vote as I canceled it to pull in more mentors. The following people voted on the first pass: Henry Saputra +1 (binding) Chris Mattmann + 1 (binding) Thanks! Paul Ramirez P.S. +1 from me (binding) = HotdoG Proposal = == Abstract == The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS format into GeoTIFF format. This is the first of a potential series of incoming projects originating from The HDF Group -- the non-profit organization is interested in evaluating the ASF as a potential home for many of its projects. The HDF Group is an independently funded organization that started many years ago with major investment from NASA as the Hierarchical Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote sensing data format for NASA missions, and an increasing number of other disciplines including bio medicine, radio astronomy, climate science, and other domains. HDF is both a data and metadata format, as well as a model for representing and access information. There are numerous downstream tools that can read and write HDF data, including a growing number of Geospatial data tools (ESRI-based, and also OpenGeo and other community led efforts). In addition, major interoperability efforts are also occurring between the remote sensing community and the climate modeling community (which has traditionally favored NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common data format and model. HotdoG is poised to be a first of its kind in the form of bringing one of the major 2 data formats for science to the ASF (the other being the NetCDF format). == Proposal == HotdoG is a software converter that converts Earth Science data in HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of remote sensing data to interoperate with common GIS tools (like WebGIS, Web Processing, image analysis, and geo computational tools). We feel that the project is an incremental step, and an appropriate focus with tangible success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF conversion. There are numerous interesting paths that we can take the toolkit in -- as conversion from remotely sensed data to GeoTIFF involves ensuring that the HDF-EOS metadata elements can be appropriately represented using GeoTIFF headers, and the associated format. Furthermore, capturing the HDF's appropriate geo datum in GeoTIFF will be another important challenge. == Background == GeoTIFF is a data and metadata standard for Earth science applications. It is based on binary Tagged Image File Format (TIFF). A GeoTIFF file has geographic (or cartographic) data embedded as tags within the TIFF file that are used to geo-locate the image. This is required for correct integration of the image in Geographic Information Systems (GIS) and other popular tools like Google Earth Pro. In the recent years, GeoTIFF has gained popularity as a visualization format among NASA HDF Earth science user communities according to the NASA data user's survey. However, the conversion from HDF to GeoTIFF is not straightforward for end users because NASA HDF data products are diverse and organized in many different ways. For example, go to http://hdfeos.org/zoo and you'll see many scripting language examples because no single script can correctly visualize all NASA HDF data. == Rationale == The HEG tool is limited to some NASA HDF-EOS2 products (no support for HDF-EOS5 products) and it is not an open-source tool. The latest GDAL (version 1.9.2 and above) is an open-source tool but it cannot handle many non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure HDF5) correctly and automatically. == Initial Goals == We'll improve GDAL to support NASA HDF products better by handling geo-location information and physical meaning of data correctly and automatically. We'll handle NASA products intelligently so novice users don't have to supply many options or figure out the details about the data products. For advanced users, we'll give a full control of accessing HDF products in many different ways so that the converted GeoTIFF file is scientifically valid and meaningful. We aim to provide command line tools first and evolve them into a GUI tool. == Current Status == We're looking
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Does an incubator project release requires sha1 checksum too? From: http://www.apache.org/dev/release-signing.html: An SHA checksum *should* also be created and *must* be suffixed .sha Looks like it should but not required? - Henry On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
Re: [PROPOSAL] MetaModel for the Apache Incubator
Hey Noah, thats great and I think as long as the VOTE has not bee closed we can add new initial members. Looks like the discussions have calmed down so if no one object I will start the VOTE thread sometime today. Thanks, Henry On Wed, Jun 5, 2013 at 2:24 AM, Noah Slater nsla...@apache.org wrote: Great. I assume that if someone is eager to join as a mentor and the vote is already done, we can add them after the fact. On 5 June 2013 10:22, Henry Saputra henry.sapu...@gmail.com wrote: Thanks Noah. I think the discussion has calmed down and hopefully we could start Vote thread tomorrow. - Henry On Wednesday, June 5, 2013, Noah Slater wrote: I sent a note to the CouchDB list to see if anyone else wants to volunteer as a mentor. On 31 May 2013 21:35, Henry Saputra henry.sapu...@gmail.com wrote: Added Noah Slater (nslater at apache dot org) as mentor and initial committer to the proposal. - Henry On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a sta http://eobjects.org/svn/MetaModelbutwill be moved to an Apache repository. === Issue tracking === JIRA MetaModel (METAMODEL) === Other resources === We would like to have wiki page located at: http://wiki.apache.org/MetaModel In later development phase a set of database servers (specifically MongoDB, CouchDB, MySQL, PostgreSQL, MS SQL Server (Express), Firebird) should be made available for integration
Re: [PROPOSAL] MetaModel for the Apache Incubator
Ah ok, thanks Marvin. I agree, the proposal will be frozen once formal VOTE sent out. Thank you for the reminder. - Henry On Thu, Jun 6, 2013 at 10:17 AM, Marvin Humphrey mar...@rectangular.comwrote: On Thu, Jun 6, 2013 at 9:46 AM, Henry Saputra henry.sapu...@gmail.com wrote: Hey Noah, thats great and I think as long as the VOTE has not bee closed we can add new initial members. The IPMC votes on specific language, so as soon as a VOTE thread is *opened* the proposal must be frozen. When Mentors join a podling later, there's often little formality about it (which seems fine) -- but we ought to maintain rigor about formal VOTEs. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Apache MetaModel into the Apache incubator
Hi All, I'd like to call a VOTE for acceptance of MetaModel into the Apache incubator. The vote will close on June 12, 2013 at 6:00 PM (PST). [] +1 Accept MetaModel into the Apache incubator [] +0 Don't care. [] -1 Don't accept MetaModel into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is: http://wiki.apache.org/incubator/MetaModelProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Henry Saputra Champion for Apache MetaModel P.S. Here's my +1 (binding) - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been “dragged” into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. === Community === The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it’s open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data warehouse automation project), we believe that the critical mass to sustain a community is there. === Core developers === MetaModel was founded
Re: [PROPOSAL] MetaModel for the Apache Incubator
Thanks Noah. I think the discussion has calmed down and hopefully we could start Vote thread tomorrow. - Henry On Wednesday, June 5, 2013, Noah Slater wrote: I sent a note to the CouchDB list to see if anyone else wants to volunteer as a mentor. On 31 May 2013 21:35, Henry Saputra henry.sapu...@gmail.com wrote: Added Noah Slater (nslater at apache dot org) as mentor and initial committer to the proposal. - Henry On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a sta http://eobjects.org/svn/MetaModelbut will be moved to an Apache repository. === Issue tracking === JIRA MetaModel (METAMODEL) === Other resources === We would like to have wiki page located at: http://wiki.apache.org/MetaModel In later development phase a set of database servers (specifically MongoDB, CouchDB, MySQL, PostgreSQL, MS SQL Server (Express), Firebird) should be made available for integration testing. Currently this is done internally at Human Inference. === Initial committers === Kasper Sørensen (i.am.kasper.sorensen [at] gmail.com), Project Founder, works at Human Inference Ankit Kumar (ak.ankitkumar [at] gmail.com), works at Human Inference Sameer Arora (sameer11sep [at] gmail.com) Henry Saputra (hsaputra [at] apache.org) Juan José van der Linden (delostilos [at] gmail.com), works for Quipu Arvind Prabhakar (arvind at apache dot org) Matt Franklin (mfranklin at apache dot org) == Sponsors == === Champion === Matt Franklin (mfranklin at apache dot org) === Nominated mentors === Henry Saputra (hsaputra at apache dot org) Arvind Prabhakar (arvind at apache dot org) Matt
Re: [VOTE] Accept Apache HotdoG into the Incubator
+1 (binding) Looks like a good project with awesome initial contributors, good luck guys. - Henry On Tue, Jun 4, 2013 at 10:28 AM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: All, I'd like to call a VOTE for the acceptance of Apache HotdoG into the Incubator. I'll leave the VOTE open for the rest of the week and close it out Monday, June 11th early am PT. [ ] +1 Accept Apache HotdoG into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache HotdoG because... Full Proposal is pasted at the end of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks! Paul Ramirez P.S. +1 from me (binding) = HotdoG Proposal = == Abstract == The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS format into GeoTIFF format. This is the first of a potential series of incoming projects originating from The HDF Group -- the non-profit organization is interested in evaluating the ASF as a potential home for many of its projects. The HDF Group is an independently funded organization that started many years ago with major investment from NASA as the Hierarchical Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote sensing data format for NASA missions, and an increasing number of other disciplines including bio medicine, radio astronomy, climate science, and other domains. HDF is both a data and metadata format, as well as a model for representing and access information. There are numerous downstream tools that can read and write HDF data, including a growing number of Geospatial data tools (ESRI-based, and also OpenGeo and other community led efforts). In addition, major interoperability efforts are also occurring between the remote sensing community and the climate modeling community (which has traditionally favored NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common data format and model. HotdoG is poised to be a first of its kind in the form of bringing one of the major 2 data formats for science to the ASF (the other being the NetCDF format). == Proposal == HotdoG is a software converter that converts Earth Science data in HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of remote sensing data to interoperate with common GIS tools (like WebGIS, Web Processing, image analysis, and geo computational tools). We feel that the project is an incremental step, and an appropriate focus with tangible success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF conversion. There are numerous interesting paths that we can take the toolkit in -- as conversion from remotely sensed data to GeoTIFF involves ensuring that the HDF-EOS metadata elements can be appropriately represented using GeoTIFF headers, and the associated format. Furthermore, capturing the HDF's appropriate geo datum in GeoTIFF will be another important challenge. == Background == GeoTIFF is a data and metadata standard for Earth science applications. It is based on binary Tagged Image File Format (TIFF). A GeoTIFF file has geographic (or cartographic) data embedded as tags within the TIFF file that are used to geo-locate the image. This is required for correct integration of the image in Geographic Information Systems (GIS) and other popular tools like Google Earth Pro. In the recent years, GeoTIFF has gained popularity as a visualization format among NASA HDF Earth science user communities according to the NASA data user's survey. However, the conversion from HDF to GeoTIFF is not straightforward for end users because NASA HDF data products are diverse and organized in many different ways. For example, go to http://hdfeos.org/zoo and you'll see many scripting language examples because no single script can correctly visualize all NASA HDF data. == Rationale == The HEG tool is limited to some NASA HDF-EOS2 products (no support for HDF-EOS5 products) and it is not an open-source tool. The latest GDAL (version 1.9.2 and above) is an open-source tool but it cannot handle many non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure HDF5) correctly and automatically. == Initial Goals == We'll improve GDAL to support NASA HDF products better by handling geo-location information and physical meaning of data correctly and automatically. We'll handle NASA products intelligently so novice users don't have to supply many options or figure out the details about the data products. For advanced users, we'll give a full control of accessing HDF products in many different ways so that the converted GeoTIFF file is scientifically valid and meaningful. We aim to provide command line tools first and evolve them into a GUI tool. == Current Status == We're looking for developers and sponsors. === Meritocracy === We will discuss the milestone and the future plan in an open forum. We
Re: [PROPOSAL] Apache Spark for the Incubator
Thanks Chris, looking forward for this project to be part of ASF family. I have added my name as mentor in the proposal. - Henry On Mon, Jun 3, 2013 at 6:41 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Henry, I've conferred with the incoming Spark community and we are very happy to have you as a mentor on the project. Please feel free to add yourself to the wiki. Cheers, Chris ++ 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 ++ -Original Message- From: Henry Saputra henry.sapu...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 12:38 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator Wow! I have been using Shark, which runs on top of Shark, with Mesos in our prototype for API analytics for a while and would LOVE to help as mentor and initial contributors. - Henry On Fri, May 31, 2013 at 11:03 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, I'm pleased to bring you a proposal to the Apache Incubator for the Apache Spark project: https://wiki.apache.org/incubator/SparkProposal The work originates from the Berkeley AMPLab and through a number of industry participants, and other institutions. Spark is a framework for large-scale data analysis on clusters, with a particular focus on low latency operations. The source code is written in Scala, and provides a number of APIs and bindings in various programming languages. The proposal text is copied to the bottom of this email. I'm going to leave this thread open for the next week for discussion. Once it's died down, I'll call an official VOTE. Suresh, Ross G. -- heads up -- this project may be of interest to you both and would welcome you guys as additional mentors. We currently have 3 mentors committed to the project, but would love to have more. People interested in contributing should declare their interest here on the general@incubator thread and those potential contributors will be discussed by the incoming Spark community. Questions -- let's hear em'! :) Cheers, Chris (Champion, incoming Apache Spark) === Abstract === Spark is an open source system for large-scale data analysis on clusters. === Proposal === Spark is an open source system for fast and flexible large-scale data analysis. Spark provides a general purpose runtime that supports low-latency execution in several forms. These include interactive exploration of very large datasets, near real-time stream processing, and ad-hoc SQL analytics (through higher layer extensions). Spark interfaces with HDFS, HBase, Cassandra and several other storage storage layers, and exposes APIs in Scala, Java and Python. Background Spark started as U.C. Berkeley research project, designed to efficiently run machine learning algorithms on large datasets. Over time, it has evolved into a general computing engine as outlined above. Spark¹s developer community has also grown to include additional institutions, such as universities, research labs, and corporations. Funding has been provided by various institutions including the U.S. National Science Foundation, DARPA, and a number of industry sponsors. See: https://amplab.cs.berkeley.edu/sponsors/ for full details. === Rationale === As the number of contributors to Spark has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Spark is a natural fit for the Apache foundation: Spark already interoperates with several existing Apache projects (HDFS, HBase, Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar with the Apache process and and subscribes to the Apache mission - the team includes multiple Apache committers already. Finally, joining Apache will help coordinate the development effort of the growing number of organizations which contribute to Spark. == Initial Goals == The initial goals will most likely be to move the existing codebase to Apache and integrate with the Apache development process. Furthermore, we plan for incremental development, and releases along with the Apache guidelines. === Current Status === == Meritocracy == The Spark project already operates on meritocratic principles. Today, Spark has
Re: [PROPOSAL] MetaModel for the Apache Incubator
Thank you Matt. I have updated the proposal to reflect the change of Champion for MetaModel proposal. Thanks, - Henry On Fri, May 31, 2013 at 5:44 PM, Matt Franklin m.ben.frank...@gmail.comwrote: Now that Henry is a member, I would like this proposal to reflect that he has really been the primary champion, not me. I am looking forward to staying on as a mentor, but Henry has been the driving force in getting MetaModel organized and proposed. I am more than willing to champion this project and help keep it going, but Henry's passion for its success is hard to match. On Fri, May 31, 2013 at 4:35 PM, Henry Saputra henry.sapu...@gmail.com wrote: Added Noah Slater (nslater at apache dot org) as mentor and initial committer to the proposal. - Henry On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists
Re: [PROPOSAL] Apache Spark for the Incubator
Wow! I have been using Shark, which runs on top of Shark, with Mesos in our prototype for API analytics for a while and would LOVE to help as mentor and initial contributors. - Henry On Fri, May 31, 2013 at 11:03 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, I'm pleased to bring you a proposal to the Apache Incubator for the Apache Spark project: https://wiki.apache.org/incubator/SparkProposal The work originates from the Berkeley AMPLab and through a number of industry participants, and other institutions. Spark is a framework for large-scale data analysis on clusters, with a particular focus on low latency operations. The source code is written in Scala, and provides a number of APIs and bindings in various programming languages. The proposal text is copied to the bottom of this email. I'm going to leave this thread open for the next week for discussion. Once it's died down, I'll call an official VOTE. Suresh, Ross G. -- heads up -- this project may be of interest to you both and would welcome you guys as additional mentors. We currently have 3 mentors committed to the project, but would love to have more. People interested in contributing should declare their interest here on the general@incubator thread and those potential contributors will be discussed by the incoming Spark community. Questions -- let's hear em'! :) Cheers, Chris (Champion, incoming Apache Spark) === Abstract === Spark is an open source system for large-scale data analysis on clusters. === Proposal === Spark is an open source system for fast and flexible large-scale data analysis. Spark provides a general purpose runtime that supports low-latency execution in several forms. These include interactive exploration of very large datasets, near real-time stream processing, and ad-hoc SQL analytics (through higher layer extensions). Spark interfaces with HDFS, HBase, Cassandra and several other storage storage layers, and exposes APIs in Scala, Java and Python. Background Spark started as U.C. Berkeley research project, designed to efficiently run machine learning algorithms on large datasets. Over time, it has evolved into a general computing engine as outlined above. Spark¹s developer community has also grown to include additional institutions, such as universities, research labs, and corporations. Funding has been provided by various institutions including the U.S. National Science Foundation, DARPA, and a number of industry sponsors. See: https://amplab.cs.berkeley.edu/sponsors/ for full details. === Rationale === As the number of contributors to Spark has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Spark is a natural fit for the Apache foundation: Spark already interoperates with several existing Apache projects (HDFS, HBase, Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar with the Apache process and and subscribes to the Apache mission - the team includes multiple Apache committers already. Finally, joining Apache will help coordinate the development effort of the growing number of organizations which contribute to Spark. == Initial Goals == The initial goals will most likely be to move the existing codebase to Apache and integrate with the Apache development process. Furthermore, we plan for incremental development, and releases along with the Apache guidelines. === Current Status === == Meritocracy == The Spark project already operates on meritocratic principles. Today, Spark has several developers and has accepted multiple major patches from outside of U.C. Berkeley. While this process has remained mostly informal (we do not have an official committer list), an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Spark project would include several of these participants as committers from the onset. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. === Community === Acceptance into the Apache foundation would bolster the already strong user and developer community around Spark. That community includes dozens of contributors from several institutions, a meetup group with several hundred members, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our contributors and initial PPMC below. Though many exist at UC Berkeley, there is a representative cross sampling of other organizations including Quantifind, Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. === Alignment === Our proposed effort aligns with several ongoing BIGDATA and U.S. National priority funding interests including the NSF and its Expeditions program, and the DARPA XDATA project. Our
Re: [PROPOSAL] MetaModel for the Apache Incubator
Awesome! Looks like perfect match too! Can I also add you as initial contributors? - Henry On Fri, May 31, 2013 at 12:41 PM, Noah Slater nsla...@apache.org wrote: I would be interested in mentoring this project. (I am a CouchDB PMC member.) On Tuesday, 28 May 2013, Henry Saputra wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been “dragged” into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. === Community === The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it’s open source projects DataCleaner, SassyReader
[PROPOSAL] Apache Spark for the Incubator
I believe it is more of a framework but you can take a look at Shark which using Spark to do data warehousing that support hive query ( http://shark.cs.berkeley.edu) - Henry On Friday, May 31, 2013, Chen, Pei wrote: +1 (non-binding) This seems like a really interesting project. Q- Is Spark just a framework/API or does it also have some tools implemented for data analytics? --Pei -Original Message- From: Mattmann, Chris A (398J) [mailto:chris.a.mattm...@jpl.nasa.gov] Sent: Friday, May 31, 2013 2:04 PM To: general@incubator.apache.org Subject: [PROPOSAL] Apache Spark for the Incubator Hi Folks, I'm pleased to bring you a proposal to the Apache Incubator for the Apache Spark project: https://wiki.apache.org/incubator/SparkProposal The work originates from the Berkeley AMPLab and through a number of industry participants, and other institutions. Spark is a framework for large- scale data analysis on clusters, with a particular focus on low latency operations. The source code is written in Scala, and provides a number of APIs and bindings in various programming languages. The proposal text is copied to the bottom of this email. I'm going to leave this thread open for the next week for discussion. Once it's died down, I'll call an official VOTE. Suresh, Ross G. -- heads up -- this project may be of interest to you both and would welcome you guys as additional mentors. We currently have 3 mentors committed to the project, but would love to have more. People interested in contributing should declare their interest here on the general@incubator thread and those potential contributors will be discussed by the incoming Spark community. Questions -- let's hear em'! :) Cheers, Chris (Champion, incoming Apache Spark) === Abstract === Spark is an open source system for large-scale data analysis on clusters. === Proposal === Spark is an open source system for fast and flexible large-scale data analysis. Spark provides a general purpose runtime that supports low-latency execution in several forms. These include interactive exploration of very large datasets, near real-time stream processing, and ad-hoc SQL analytics (through higher layer extensions). Spark interfaces with HDFS, HBase, Cassandra and several other storage storage layers, and exposes APIs in Scala, Java and Python. Background Spark started as U.C. Berkeley research project, designed to efficiently run machine learning algorithms on large datasets. Over time, it has evolved into a general computing engine as outlined above. Spark¹s developer community has also grown to include additional institutions, such as universities, research labs, and corporations. Funding has been provided by various institutions including the U.S. National Science Foundation, DARPA, and a number of industry sponsors. See: https://amplab.cs.berkeley.edu/sponsors/ for full details. === Rationale === As the number of contributors to Spark has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Spark is a natural fit for the Apache foundation: Spark already interoperates with several existing Apache projects (HDFS, HBase, Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar with the Apache process and and subscribes to the Apache mission - the team includes multiple Apache committers already. Finally, joining Apache will help coordinate the development effort of the growing number of organizations which contribute to Spark. == Initial Goals == The initial goals will most likely be to move the existing codebase to Apache and integrate with the Apache development process. Furthermore, we plan for incremental development, and releases along with the Apache guidelines. === Current Status === == Meritocracy == The Spark project already operates on meritocratic principles. Today, Spark has several developers and has accepted multiple major patches from outside of U.C. Berkeley. While this process has remained mostly informal (we do not have an official committer list), an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Spark project would include several of these participants as committers from the onset. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. === Community === Acceptance into the Apache foundation would bolster the already strong user and developer community around Spark. That community includes dozens of contributors from several institutions, a meetup group with several hundred members, and an active mailing list composed of hundreds of users. Core Developers The core developers of our project are listed in our
Re: [PROPOSAL] MetaModel for the Apache Incubator
Added Noah Slater (nslater at apache dot org) as mentor and initial committer to the proposal. - Henry On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.comwrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been “dragged” into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. === Community === The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it’s open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data warehouse automation project), we believe that the critical mass to sustain a community is there. === Core developers === MetaModel was founded by Kasper Sørensen in 2009
Re: [PROPOSAL] MetaModel for the Apache Incubator
Yeah, I guess the words meta and model had been used a lot recently in incubator list =) And also, we are still looking for mentors from IPMCs to help if anyone interested ;) - Henry On Thu, May 30, 2013 at 7:36 AM, Alan Cabrera l...@toolazydogs.com wrote: On May 29, 2013, at 12:33 AM, ant elder ant.el...@gmail.com wrote: From the subject line I thought this was going to be another attempt to sort out the incubator :-/ LOL, so did I! Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache jclouds 1.6.1-incubating
Hi Andrew, looks like http://people.apache.org/~abayer/jclouds-1.6.1-incubating-rc1 resulted to 404? - Henry On Thu, May 30, 2013 at 12:44 PM, Andrew Bayer aba...@apache.org wrote: Hello, This is the first release candidate for Apache jclouds 1.6.1-incubating, the first jclouds release at Apache. We are calling this vote on both the IPMC and the jclouds PPMC at the same time, as the code for this release has already been vetted by the jclouds developers leading up to this RC. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412styleName=HtmlprojectId=12314430 *** Please download, test and vote by Sunday, June 2nd, 1pm PDT. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~abayer/jclouds-1.6.1-incubating-rc1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachejclouds-039 The tags to be voted upon: - jclouds - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=57718280be4bccea9e7885c5c3c38550f818d0dd - jclouds-labs - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=df11ed5cc10e86b6ee33be2c85f25717ca59b6f4 - jclouds-chef - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=989d9a484ac3f4fa919307173b7a8839817bb797 - jclouds-karaf - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=964f2694b5198c7916869308c2c644a2f71927ff - jclouds-cli - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=8f0491d33ca07eab01d90e9a4571d6d046865638 Whirr's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jclouds/KEYS [ ] +1 [ ] 0 [ ] -1 (explain why) Please note whether you're voting as an IPMC member, a jclouds PPMC member, or both. Thanks! A.
Re: [PROPOSAL] MetaModel for the Apache Incubator
There are already a lot of discussions about it and this aint one of them =P - Henry On Wed, May 29, 2013 at 12:33 AM, ant elder ant.el...@gmail.com wrote: From the subject line I thought this was going to be another attempt to sort out the incubator :-/ ...ant On Tue, May 28, 2013 at 7:20 PM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been “dragged” into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. === Community === The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM
Re: [PROPOSAL] MetaModel for the Apache Incubator
Hi Arvind, For concern 1 I will let the lead engineer Kasper to answer. I believe if the contributors already signed copyright agreement to Human Inference then it should be fine since it means all code contributions belong to Human Inference which will then be transferred to ASF. Someone might want to help clarifying this if I am mistaken. As for concern 2, I have scanned the master pom.xml's dependencyManagement section and looks like all dependencies are Apache 2.0 friendly. Again, Kasper could help verify if this is the case. - Henry On Wed, May 29, 2013 at 10:31 PM, Arvind Prabhakar arv...@apache.orgwrote: Henry, Thank you for submitting this proposal. I am very glad to be a mentor for this project and look forward to working with you and the broader community. I have a couple of comments with regards to the stated proposal - First - as noted in the proposal MetaModel has been an open source project with contributions coming from various corners of the world. Given this development model, do the individual contributors hold copyright over their contributed code? If so, you will likely need their consent in order to provide this code to the Incubator for the purposes of starting this project. Second - I noticed that the proposal calls out the LGPL dependency that will be removed before sourcing the initial drop. Along the same lines, I urge you to go through the the legal FAQ [1] to make sure that there are no other dependencies that merit removal or special handling. [1] http://www.apache.org/legal/resolved.html Regards, Arvind Prabhakar On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore
[PROPOSAL] MetaModel for the Apache Incubator
Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been “dragged” into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. === Community === The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it’s open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data warehouse automation project), we believe that the critical mass to sustain a community is there. === Core developers === MetaModel was founded by Kasper Sørensen in 2009. Later it was incorporated as a core library by Human Inference, meaning that more than 20 developers have been involved in its making in this commercial setting. Furthermore a smaller number of contributors have submitted patches for the library. Others have started
Re: [VOTE] Release Curator version 2.0.1-incubating RC2
signature looks ok, hash checksum looks ok, license and standard ASF files exists. +1 - Henry On Tue, May 28, 2013 at 3:36 PM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Hello, This is a vote for the release of Apache Curator version 2.0.1-incubating RC2 This has been voted on via the d...@curator.incubator.apache.org mailing list (vote thread [1]), 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) * Patrick Hunt * Mahadev Konar * Enis Söztutar *** Please download, test and vote within 3 working days 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=12314425version=12324348 Staging repo: https://dist.apache.org/repos/dist/dev/incubator/curator/2.0.1-incubating-rc2/ Binary artifacts: https://repository.apache.org/content/repositories/orgapachecurator-012/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-curator.git;a=tag;h=9630c63b05a3dafd3d63ccffbb2e95e0a19162c0 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/201305.mbox/%3C90CD3675-8864-4983-B07B-4B4CCB9E4772%40jordanzimmerman.com%3E
Re: Need some help for releasing S4 0.6.0
+1 (binding) We should probably make the MD5 and SHA sum more inline with other Apache releases to help make verification easier. But I dont think is a release blocker. - Henry On Mon, May 13, 2013 at 9:04 AM, Matthieu Morel mmo...@apache.org wrote: Hi all, we currently have the following +1 votes: 1 IPMC / PPMC vote (phunt) 2 PPMC votes (kishoreg, mmorel) 1 non binding committer vote (dferro) So we haven't reached the quorum yet. Can we get some help (votes) to finalize this release? (The vote thread has the following subject: [VOTE] S4 0.6.0 Incubating Release Candidate 5) Thanks! Matthieu On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel mmo...@apache.org wrote: Hello, this is the *fifth* release candidate for Apache S4, version 0.6.0 We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking issue in RC2, related to metrics logging configuration, issues related to the package contents and license headers in RC3, and removed included javadoc files in RC4. This release fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12321702 *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 GMT *** Note that we are voting upon the source (tag). Source package in zip format: http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/ The (git) tag to be voted upon: 0.6.0-RC5: https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0 S4 KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS The README.md file contains instructions for installing the gradle wrapper (which is not shipped with the source release). We include a RAT check task. (Can be used by fetching rat from /lib dir in the git repo and using the .rat-excludes file at the root of the git repo) It can be run with : gradlew rat output Please cast your vote, thanks! [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) NOTES: - All releases by podlings must be approved by the Incubator PMC. The conventional process is for the podling to follow the usual Apache process and then call for a Incubator PMC VOTE on the general incubator list. For RC5 however, following recommendations from our mentors, we are proceeding to a parallel vote on both general@incubator and s4-dev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Need some help for releasing S4 0.6.0
The hashes contain additional text: MD5 (apache-s4-0.6.0-incubating-src.zip) = for the MD5 and apache-s4-0.6.0-incubating-src.zip for the SHA1. Making it harder to just diff the hash for the artifacts. Looks like not a blocker for release but I believe typically the hashes do not contain this additional meta text. - Henry On Mon, May 13, 2013 at 9:04 AM, Matthieu Morel mmo...@apache.org wrote: Hi all, we currently have the following +1 votes: 1 IPMC / PPMC vote (phunt) 2 PPMC votes (kishoreg, mmorel) 1 non binding committer vote (dferro) So we haven't reached the quorum yet. Can we get some help (votes) to finalize this release? (The vote thread has the following subject: [VOTE] S4 0.6.0 Incubating Release Candidate 5) Thanks! Matthieu On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel mmo...@apache.org wrote: Hello, this is the *fifth* release candidate for Apache S4, version 0.6.0 We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking issue in RC2, related to metrics logging configuration, issues related to the package contents and license headers in RC3, and removed included javadoc files in RC4. This release fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12321702 *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 GMT *** Note that we are voting upon the source (tag). Source package in zip format: http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/ The (git) tag to be voted upon: 0.6.0-RC5: https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0 S4 KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS The README.md file contains instructions for installing the gradle wrapper (which is not shipped with the source release). We include a RAT check task. (Can be used by fetching rat from /lib dir in the git repo and using the .rat-excludes file at the root of the git repo) It can be run with : gradlew rat output Please cast your vote, thanks! [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) NOTES: - All releases by podlings must be approved by the Incubator PMC. The conventional process is for the podling to follow the usual Apache process and then call for a Incubator PMC VOTE on the general incubator list. For RC5 however, following recommendations from our mentors, we are proceeding to a parallel vote on both general@incubator and s4-dev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] helix 0.6.1-incubating
Looks like the release artifact does not exist: https://repository.apache.org/content/repositories/orgapachehelix-121 Is it suppose to be https://repository.apache.org/content/repositories/orgapachehelix-021 ? - Henry On Sun, May 12, 2013 at 12:18 AM, Shi Lu lush...@gmail.com wrote: Hi, This is to call for a vote on releasing the following candidate as Apache Helix 0.6.1-incubating. This is the first release candidate of our second release at Apache. Apache Helix is a generic cluster management framework that makes it easy to build partitioned and replicated, fault tolerant and scalable distributed systems. Release notes: http://helix.incubator.apache.org/releasenotes/release-0.6.1-incubating.html Our vote thread on helix-dev: http://markmail.org/message/xymuvmcjxobmhjd3?q=+list:org%2Eapache%2Ehelix%2Edev The following IPMC members have voted +1 Patrick Hunt Olivier Lamy Release artifacts: https://repository.apache.org/content/repositories/orgapachehelix-121 Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.1-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.1-incubating/src/ The 0.6.1-incubating release tag https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=commit;h=355d1692a9036fa8741ef828db45446515ff018f KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/helix/KEYS Please vote on the release. The vote will be open for 72 hours. Thanks, Apache Helix team.
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Good luck guys - Henry On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is
