Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc5)
+1 from me: SIGS and CHECKSUM check out. [chipotle:~/tmp/apache-spark-0.9.0-rc5] mattmann% $HOME/bin/stage_apache_rc spark 0.9.0-incubating http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5/ % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 5387k 100 5387k0 0 1217k 0 0:00:04 0:00:04 --:--:-- 1234k % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 490 100 4900 0 3678 0 --:--:-- --:--:-- --:--:-- 6901 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 10077 100770 0644 0 --:--:-- --:--:-- --:--:-- 1262 [chipotle:~/tmp/apache-spark-0.9.0-rc5] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file spark-0.9.0-incubating.tgz.asc gpg: Signature made Thu Jan 23 22:33:27 2014 PST using RSA key ID 9E4FE3AF gpg: Good signature from Patrick Wendell pwend...@gmail.com gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 5AA9 0E72 812F F246 7904 277D 548F 5FEE 9E4F E3AF [chipotle:~/tmp/apache-spark-0.9.0-rc5] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.tar.gz': No such file or directory md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory spark-0.9.0-incubating.tgz: OK [chipotle:~/tmp/apache-spark-0.9.0-rc5] mattmann% Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-283, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Patrick Wendell pwend...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, January 27, 2014 12:02 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Release Apache Spark 0.9.0-incubating (rc5) 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=9 5d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9 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: [ANNOUNCE] Billie Rinaldi joins the IPMC
Welcome Billie! Sent from my iPhone On Dec 12, 2013, at 12:35 PM, Marvin Humphrey mar...@rectangular.com wrote: Apache Member Billie Rinaldi, the PMC Chair for Accumulo and a member of the Ambari PMC, has elected to join the Incubator PMC. May you have as much success as an IPMC member as you had as a PPMC member of the Accumulo podling! Marvin Humphrey, on behalf of the Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Ambari from Apache Incubator
+1 (binding). G'luck guys! 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 Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Owen O'Malley omal...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, November 18, 2013 4:14 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Graduate Ambari from Apache Incubator +1 for graduation (binding) On Sun, Nov 17, 2013 at 9:52 AM, Arun C. Murthy a...@hortonworks.com wrote: [ ] +1 Graduate Ambari from Incubator +1 for graduation (binding) thanks, Arun On Nov 15, 2013, at 9:12 AM, Yusaku Sako yus...@hortonworks.com wrote: This is a call for vote to graduate Ambari from Apache Incubator. The Apache Ambari project has been incubating since August 2011. We have made significant progress with the project during the two years of Incubation, adding 27 committers for a total of 36 committers [1], and producing 8 releases following ASF policies and guidelines. The Apache Ambari community has voted to graduate Ambari as a TLP [2]. The community vote results can be found at [3]. The discussion thread for the board resolution can be found at [4]. Please cast your votes: [ ] +1 Graduate Ambari from Incubator [ ] +0 Indifferent to graduation status of Ambari [ ] -1 Reject graduation of Ambari from Incubator This vote will remain open for at least 72 hours from now. Please find the proposed board resolution below. [1] http://people.apache.org/committers-by-project.html#ambari [2] http://markmail.org/thread/cp5ajf2uvfl3oj66 [3] http://markmail.org/message/l6zss4rgfcs3gvpm [4] http://markmail.org/thread/36dplr3pwzmazwmg Regards, Yusaku Sako ### X. Establish the Apache Ambari 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 Hadoop cluster management. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ambari Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ambari Project be and hereby is responsible for the creation and maintenance of software related to Hadoop cluster management; and be it further RESOLVED, that the office of Vice President, Apache Ambari 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 Ambari Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ambari 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 Ambari Project: * Babiichuk Andriy (ababiichuk) * Arun Murthy (acmurthy) * Aleksandr Kovalenko (akovalenko) * Antonenko Aleksandr Igorevich (alexantonenko) * Andrii Tkach (atkach) * Bernd Fondermann (berndf) * Billie Rinaldi (billie) * Christopher Douglas (cdouglas) * Chad Roberts (croberts) * Devaraj Das (ddas) * Dmitry Lysnichenko (dmitriusan) * Dmytro Sen (dsen) * Eric Yang (eyang) * Hitesh Shah (hitesh) * Jagane Sundar (jagane) * Jaimin Jetly (jaimin) * Jitendra Pandey (jitendra) * John Speidel (jspeidel) * Kan Zhang (kzhang) * Mahadev Konar (mahadev) * Papirkovskyy Myroslav (mpapirkovskyy) * Nate Cole (ncole) * Oleksandr Diachenko (odiachenko) * Owen O¹Malley (omalley) * Oleg Nechiporenko (onechiporenko) * Ramya Sunil (ramya) * Varun Kapoor (reznor) * Sumit Mohanty (smohanty) * Srimanth Gunturi (srimanth) * Siddharth Wagle (swagle) * Thomas Beerbower (tbeerbower) * Suhas (vgogate) * Vikram Dixit K (vikram) * Vinod Kumar Vavilapalli (vinodkv) * Xi Wang (xiwang) * Yusaku Sako (yusaku) NOW, THEREFORE, BE IT
Re: Code import for Apache Accumulo
+1 Sent from my iPhone On Nov 4, 2013, at 12:25 PM, Jim Jagielski j...@jagunet.com wrote: +1 On Oct 30, 2013, at 8:22 AM, David Nalley da...@gnsa.us wrote: Hi Josh: Separate repo (or not), release cycles, etc are project decisions. As far as importation of the code; it almost certainly needs to go through IP Clearance. http://incubator.apache.org/ip-clearance/ If you have questions or need help with that process, don't hesitate to ask. --David On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser els...@apache.org wrote: Hi, Over at Apache Accumulo, we just got a nice bit of code that integrates the R programming language (via RStudio) with Accumulo. This was done completely by the community (non-committers) and we're trying to figure out what's best for it and where it can live. The general consensus for us is that we would want to import it into it's own repository (treat it as a contrib-project) since Accumulo has no need to depend on it and thus it can be versioned at its own pace. The contributors are currently working on ICLA/CCLA forms, but I wanted to see what else we (the Accumulo PMC) would need to do to import this code. Thanks! - Josh - 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] Accept Storm into the Incubator
+1 binding. Good luck guys! ++ 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: Doug Cutting cutt...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, September 12, 2013 12:19 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept Storm into the Incubator 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
Re: Web voting
Hey Marvin, I started to flesh out a potential REST API for Apache Steve (no code there yet, just ideas). Thoughts and contributions are of course welcome. Alan C. also contributed to this: https://wiki.apache.org/Steve/SteveRESTAPI Cheers, Chris -Original Message- From: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, September 3, 2013 5:10 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Web voting On Tue, Sep 3, 2013 at 3:32 AM, Christian Grobmeier grobme...@gmail.com wrote: Am 03.09.13 12:18, schrieb Tammo van Lessen: I find Loomio [1] looks very promising. It's probably not exactly tailor-made for our decision making progress but it can showcase [2] what is possible and if it can help us. Looks pretty nice. Is it a requirement to send individual votes to the ml (like with voting on releases). I would say no -- but the results must be auditable. A final tally tabulating all votes cast is a requirement. I also think it would be useful to send out email notification that a vote has been cast to the personal email of the individual who cast it. To my mind it's a feature if we can achieve auditability without individual emails to the list, as that improves the list's signal-to-noise ratio. For auditability's sake, we need to limit those who can vote to a whitelist. Code we run on our own servers can hook into LDAP, or maybe even mailing-list membership records. What sort of implementation challenges would whitelisting present if we use external voting services? in some cases we need secret votes (like with the IPMC chair vote) We have acceptable solutions now for all our voting needs, including secret votes with Apache Steve. Web voting would be for the sake of making some votes easier; we don't have to use it all the time. Loomio looks hackable actually. AGPL, though. :\ 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] Graduate Apache Curator as an Apache Top Level Project
+1 binding from me. 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: Jordan Zimmerman jor...@jordanzimmerman.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, August 28, 2013 10:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Graduate Apache Curator as an Apache Top Level Project 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.ji ra.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,
Re: [PROPOSAL] Aurora for Incubation
Sure, makes sense to me. 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: Wednesday, August 28, 2013 4:08 PM To: general@incubator.apache.org general@incubator.apache.org Subject: 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
I'm -0 on the initiative. I don't support it, but then again, since I'm not willing to propose something different and since at least some people think it's needed, I'm not going to stand in its way. 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: Bertrand Delacretaz bdelacre...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, July 30, 2013 3:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Creation of the Incubator Ombudsman On Tue, Jul 30, 2013 at 5:55 AM, Marvin Humphrey mar...@rectangular.com wrote: ...Bertrand was skeptical about an ASF-wide ombud, but didn't raise any objection to an Incubator-specific position. http://s.apache.org/NAa ... Just laziness on my part...what I said there also applies to an Incubator ombudsman, I'll repeat it here: I don't think we need it - people should feel free to contact people that they trust (IPMC members, mentors, ASF members) privately if there's a need, and not having someone elected in the ombudsman role means people are free to talk to whoever *they* think will help. -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: Moderation of report reminders
Hey Marvin, Thanks for the background -- my vote would be for the allow list approach. 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: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, July 13, 2013 10:57 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Moderation of report reminders Greets, This report cycle, I audited the report reminders sent out by Marvin[1]. After waiting a couple of days for moderation to clear, I used a web browser to check the dev list archives for each podling in the report cycle to see whether the message had arrived. Reminders did not made it through for three podlings: Celix, Tajo, and VXQuery. For each of the three, I subscribed to the dev list to sidestep moderation, sent a manual reminder, then promptly unsubscribed. The nudging worked: all eventually filed reports. Report reminders not getting moderated through has been a problem for years, and it's time we solved it once and for all. Obviously, the labor-intensive approach I took this month is not sustainable -- we need something automatic. One possibility would be to set up a script to trawl the mbox archives scanning for report reminders a couple days after they were sent out, then mail general@incubator with a report enumerating which reminders didn't go through. This may sound like a large project, but we would be able to leverage a lot of code which Brane wrote for the vote scan: https://svn.apache.org/repos/asf/incubator/public/trunk/voter/ We might also gather other information during the same trawl and generate a more rich report: * Generate message counts for each podling mailing list, as a rough barometer of activity. * Scan for Mentor email addresses in recent messages, as a crude shepherding aid. * (Suggestions?) A second possibility might be to consolidate `-allow` lists. (I'm not sure whether this is technically feasible -- it came up yesterday on the infra list, but the discussion was not conclusive. Perhaps one of the Infrastructure people on this list could comment.) The idea is that instead of having dedicated `-allow` lists for each podling dev list, we would have one omnibus public-allow@incubator list. Once we approve `Marvin no-re...@apache.org` by adding it to that list, then reminders will always go through, even for new podlings. Thoughts? Marvin Humphrey [1] https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_remind ers - 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
Apache Open Climate Workbench report: added to Wiki
...sorry for tardiness, Marvin. Just wanted to let you know I added a report to the wiki. Also, thanks to Alan for his comments. Yes, we have to get our podling status page updated. I'll spend some time tonight doing just that. Apache OCW community: heads up /CC. 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 ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache JSPWiki for graduating out of the incubator
+1 from me (binding). Good luck! 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: Juan Pablo Santos Rodríguez juanpa...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, July 6, 2013 3:33 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] recommend Apache JSPWiki for graduating out of the incubator Hi all, The Apache JSPWiki podling is a project which holds a feature-rich and extensible WikiWiki engine, built around the standard Java EE components Java, Servlets, and Java Server Pages. We've been incubating for a very long time (almost 6 years); we feel we are ready for graduation. Since Jan 2012, we've shipped 2 releases, added 1 committer, adhered to the Apache Way in deciding technical and non-technical issues and revamped our website. We've already done an internal VOTE on the proposal which passed with a big majority [#1], and we consider the podling namesearch task as completed [#2]. Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation proposal to the board. [+1] yes, go forward [+0] don't care [-1] nope, because [blocker_reason] The VOTE is open for at least 72h thanks br, juan pablo [#1] http://s.apache.org/654 (an additional vote was received off-list, cfr. with http://s.apache.org/tC7) [#2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 - Proposed Board Resolution Report X. Establish the Apache JSPWiki Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache JSPWiki Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache JSPWiki Project be and hereby is responsible for the creation and maintenance of software related to JSPWiki, a feature-rich and extensible Wiki engine built around the standard Java EE components Java, Servlets, and Java Server Pages; and be it further RESOLVED, that the office of Vice President, Apache JSPWiki 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 JSPWiki Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache JSPWiki 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 JSPWiki Project: * Murray Altheim alth...@apache.org * Dirk Frederickx brus...@apache.org * Florian Holeczekflori...@apache.org * Andrew Jaquith ajaqu...@apache.org * Glen Mazza gma...@apache.org * Harry Metske mets...@apache.org * Craig L Russell c...@apache.org * Juan Pablo Santos juanpa...@apache.org * Christoph Sauer csa...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Juan Pablo Santos be appointed to the office of Vice President, Apache JSPWiki, 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 JSPWiki Project be and hereby is tasked with the migration and rationalization of the Apache Incubator JSPWiki podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator JSPWiki podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe,
Re: Creating announce@ lists by default
+1 great work Marvin. ++ 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: Greg Stein gst...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, July 2, 2013 7:32 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Creating announce@ lists by default On Tue, Jul 2, 2013 at 9:59 PM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, May 9, 2013 at 7:29 PM, Noah Slater nsla...@apache.org wrote: Hey Marvin, Did you get anywhere with this? Finally, yes. I've written up the subject on the Incubator wiki and linked to it from the proposal guide. https://wiki.apache.org/incubator/MailingListOptions Hell yeah!! I 3 that page. Repeat: 3 Great job, Marvin! I have zero suggestions to improve. (now just save it under www.a.o/dev/ and get it fully linked in from everywhere) Cheers, -g - 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] Apache Spark for the Incubator
Hi Karthik, Yes it is. You can join by sending blank emails to: dev-subscr...@spark.incubator.apache.org commits-subscr...@spark.incubator.apache.org 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: karthik tunga karthik.tu...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 25, 2013 11:22 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [RESULT] [VOTE] Apache Spark for the Incubator Hi, Is the mailing list setup ? Cheers, Karthik On 20 June 2013 02:38, Matei Zaharia ma...@eecs.berkeley.edu wrote: Thanks Chris! We'll get started on all the required steps. Matei On Jun 20, 2013, at 4:35 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, This VOTE has passed with the following tallies: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* Scott Deboy Ted Dunning* Hitesh Shah Paul Ramirez* Ralph Goers* Alan Cabrera* Thilina Gunarathne Marcel Offermans* Alex Karasulu* Chris Douglas* Andrew Hart* Deepal jayasinghe Ashish Joe Brockmeier* Mohammad Nour El-Din* Arun C Murthy* Tim Williams* Arvind Prabhakar* Matt Franklin* Matei Zaharia Andy Konwinski +0.9 Marvin Humphrey * -indicates IPMC I'll go ahead and get the JIRA tickets filed for email/issue tracking/Git, and then work with the community to get them moving on' over. Thanks for VOTE'ing! 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 7, 2013 10:34 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Apache Spark for the Incubator Hi Folks, OK discussion has died down, time to VOTE to accept Spark into the Apache Incubator. I'll let the VOTE run for at least a week. So far I've heard +1s from the following folks, so no need for them to VOTE again unless they want to change their VOTE: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* * -indicates IPMC [ ] +1 Accept Spark into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept Spark into the Apache Incubator because.. Proposal text is below. === 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
Re: [VOTE] Release Curator 2.1.0-incubating
Hi Jordan, I'd be happy to review this, but can you please stage the sources and sign them with your ASC key so I know what bits I'm voting on? You provided the link to the tag in Git which is great, but I'd like to see the bits staged to your p.a.o (old method) account, or to http://www.apache.org/dev/release.html#upload-ci per the new method. 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: Jordan Zimmerman randg...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 26, 2013 8:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Release Curator 2.1.0-incubating Hello, This is a vote for the release of Apache Curator, version 2.1.0-incubating. This has been voted on via the d...@curator.incubator.apache.org mailing list and now requires a vote on @general. 2 IPMC votes have already been cast on the vote held on dev@curator: +1 (PPMC / binding) * Patrick Hunt * Luciano Resende There were also 2 non-binding votes: +1 * Jordan Zimmerman * Eric Tschetter *** 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=12314425; version=12324401 Staging repo: https://dist.apache.org/repos/dist/dev/incubator/curator/2.1.0-incubating/ Binary artifacts: https://repository.apache.org/content/repositories/orgapachecurator-041/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-curator.git;a=tag;h=ap ache-curator-2.1.0-incubating 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) Thank you! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Curator 2.1.0-incubating
on a MacBook Air Mac OS X 10.8.4, with the following Java and MVN version: [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating] mattmann% mvn --version Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) Maven home: /usr/share/maven Java version: 1.6.0_45, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.8.4, arch: x86_64, family: mac [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating] mattmann% [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating] mattmann% java -version java version 1.6.0_45 Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406) Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode) [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating] mattmann% +1 from me still though. 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: Jordan Zimmerman jor...@jordanzimmerman.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 28, 2013 1:06 PM To: general@incubator.apache.org general@incubator.apache.org Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Curator 2.1.0-incubating The bits are staged here: https://dist.apache.org/repos/dist/dev/incubator/curator/2.1.0-incubating/ Is that a problem? Jordan Zimmerman On Jun 28, 2013, at 3:50 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Jordan, I'd be happy to review this, but can you please stage the sources and sign them with your ASC key so I know what bits I'm voting on? You provided the link to the tag in Git which is great, but I'd like to see the bits staged to your p.a.o (old method) account, or to http://www.apache.org/dev/release.html#upload-ci per the new method. 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: Jordan Zimmerman randg...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 26, 2013 8:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Release Curator 2.1.0-incubating Hello, This is a vote for the release of Apache Curator, version 2.1.0-incubating. This has been voted on via the d...@curator.incubator.apache.org mailing list and now requires a vote on @general. 2 IPMC votes have already been cast on the vote held on dev@curator: +1 (PPMC / binding) * Patrick Hunt * Luciano Resende There were also 2 non-binding votes: +1 * Jordan Zimmerman * Eric Tschetter *** 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=1231442 5 version=12324401 Staging repo: https://dist.apache.org/repos/dist/dev/incubator/curator/2.1.0-incubatin g/ Binary artifacts: https://repository.apache.org/content/repositories/orgapachecurator-041/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-curator.git;a=tag;h= ap ache-curator-2.1.0-incubating 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) Thank you! - 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: [MENTOR] Re: Missing Release Distribution in Clutch Status?
Thanks David.. ++ 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: David Crossley cross...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 20, 2013 7:05 PM To: general@incubator.apache.org general@incubator.apache.org Cc: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: Re: [MENTOR] Re: Missing Release Distribution in Clutch Status? Mattmann, Chris A (398J) wrote: Hey Guys, Sorry I missed this. Real quick CC to general@i.a.o. I'm not an expert in the Clutch. IPMC peeps that know the clutch, Knox has a release in the dist area: http://www.apache.org/dyn/closer.cgi/incubator/knox/ (^^ for example the 0.2.0 release) Can someone give us some insight as to why the clutch indicates we don't have a release in the distro area? See the Knox entry in the Other issues section: http://incubator.apache.org/clutch.html#other It is because Knox is missing the required file naming convention: http://incubator.apache.org/clutch.html#h-hasRelease So the cron job that scans for releases does not find it. -David Thank you! 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: larry mccay larry.mc...@gmail.com Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Date: Thursday, June 20, 2013 11:46 AM To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: [MENTOR] Re: Missing Release Distribution in Clutch Status? adding mentor prefix... On Mon, Jun 17, 2013 at 3:40 PM, larry mccay larry.mc...@gmail.com wrote: Touching this to bring it back to the top... @Chris - do you have any insight into this status indicator for us? On Thu, Jun 13, 2013 at 2:51 PM, larry mccay larry.mc...@gmail.comwrote: Here is the location of ambari - who has a true for release bits column - of course this is just one mirror - not sure how to map the mirrors: http://www.us.apache.org/dist/incubator/ambari/ambari-0.9-incubating/ relative path seems to map correctly to me... On Thu, Jun 13, 2013 at 2:32 PM, Kevin Minder kevin.min...@hortonworks.com wrote: We do have release bits in http://www.apache.org/dist/**incubator/knox/0.2.0/http://www.apache. or g/dist/incubator/knox/0.2.0/ I wonder if they need to be in the root? On 6/13/13 1:29 PM, larry mccay wrote: All - This page shows the status of clutch currently in incubation. It indicates that we don't have a release in our distribution area. Does this mean that we don't have our release in the right place? http://incubator.apache.org/**clutch.htmlhttp://incubator.apache.or g/ clutch.html thanks, --larry - 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: [MENTOR] Re: Missing Release Distribution in Clutch Status?
Hey Guys, Sorry I missed this. Real quick CC to general@i.a.o. I'm not an expert in the Clutch. IPMC peeps that know the clutch, Knox has a release in the dist area: http://www.apache.org/dyn/closer.cgi/incubator/knox/ (^^ for example the 0.2.0 release) Can someone give us some insight as to why the clutch indicates we don't have a release in the distro area? Thank you! 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: larry mccay larry.mc...@gmail.com Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Date: Thursday, June 20, 2013 11:46 AM To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: [MENTOR] Re: Missing Release Distribution in Clutch Status? adding mentor prefix... On Mon, Jun 17, 2013 at 3:40 PM, larry mccay larry.mc...@gmail.com wrote: Touching this to bring it back to the top... @Chris - do you have any insight into this status indicator for us? On Thu, Jun 13, 2013 at 2:51 PM, larry mccay larry.mc...@gmail.comwrote: Here is the location of ambari - who has a true for release bits column - of course this is just one mirror - not sure how to map the mirrors: http://www.us.apache.org/dist/incubator/ambari/ambari-0.9-incubating/ relative path seems to map correctly to me... On Thu, Jun 13, 2013 at 2:32 PM, Kevin Minder kevin.min...@hortonworks.com wrote: We do have release bits in http://www.apache.org/dist/**incubator/knox/0.2.0/http://www.apache.or g/dist/incubator/knox/0.2.0/ I wonder if they need to be in the root? On 6/13/13 1:29 PM, larry mccay wrote: All - This page shows the status of clutch currently in incubation. It indicates that we don't have a release in our distribution area. Does this mean that we don't have our release in the right place? http://incubator.apache.org/**clutch.htmlhttp://incubator.apache.org/ clutch.html thanks, --larry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: please follow through to publish doc changes
Hi David, That's my bad. Having not published the site using the CMS since we switched over, I knew I had to read the docs again but hadn't. I fully intended to though. Anyways, sorry. 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: David Crossley cross...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 20, 2013 7:11 PM To: general@incubator.apache.org general@incubator.apache.org Subject: please follow through to publish doc changes The problem seems to be getting worse. Some people make source changes to docs, but then do not follow through to publish those changes via the CMS. Then other changes bank up behind the logjam. http://incubator.apache.org/guides/website.html -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
[RESULT] [VOTE] Apache Spark for the Incubator
Hi Folks, This VOTE has passed with the following tallies: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* Scott Deboy Ted Dunning* Hitesh Shah Paul Ramirez* Ralph Goers* Alan Cabrera* Thilina Gunarathne Marcel Offermans* Alex Karasulu* Chris Douglas* Andrew Hart* Deepal jayasinghe Ashish Joe Brockmeier* Mohammad Nour El-Din* Arun C Murthy* Tim Williams* Arvind Prabhakar* Matt Franklin* Matei Zaharia Andy Konwinski +0.9 Marvin Humphrey * -indicates IPMC I'll go ahead and get the JIRA tickets filed for email/issue tracking/Git, and then work with the community to get them moving on' over. Thanks for VOTE'ing! 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 7, 2013 10:34 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Apache Spark for the Incubator Hi Folks, OK discussion has died down, time to VOTE to accept Spark into the Apache Incubator. I'll let the VOTE run for at least a week. So far I've heard +1s from the following folks, so no need for them to VOTE again unless they want to change their VOTE: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* * -indicates IPMC [ ] +1 Accept Spark into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept Spark into the Apache Incubator because.. Proposal text is below. === 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,
Re: [RESULT] [VOTE] Graduation of Apache Mesos
Hey Andy, Ahhh, ooops, sorry yeah I searched my email archives but didn't find your VOTEs. I'm happy to send an amended list, or simply state on the record here via email that your guys' VOTEs counted. Either way the resolution is on the agenda and your email is now in the archive so we are good. I sincerely apologize for missing the VOTEs and either way I appreciate your support on the proposed graduation VOTE. Fingers crossed that Mesos graduates tomorrow and if so, looking forward to the next steps :) 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: Andy Konwinski andykonwin...@gmail.com Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Tuesday, June 18, 2013 4:38 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: [RESULT] [VOTE] Graduation of Apache Mesos Hey Chris, it looks like a bunch binding and non binding votes by folks (including myself, Arun Murthy, Chris Douglas, Ted Dunning, Matt Franklin, ...) on the [PROPOSAL] Apache Spark for the Incubator thread and maybe you missed counting these in this tally? See my attached screenshot for what I'm referring to. I am probably missing something here; like, did we all vote on the wrong thread maybe? Sorry if so. Andy On Mon, Jun 17, 2013 at 8:56 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, OK, this VOTE has passed with the following tallies: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik Christian Grobmeier* Henry Saputra* Alex Karasulu* Roman Shaposhnik* Alan Cabrera* * - indicates IPMC I'll go ahead and add the resolution to the board agenda for consideration at our June 2013 meeting. 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 1:03 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Graduation of Apache Mesos 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 mailto:cdde1f13.d6ea1%25chris.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
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
] ZooKeeperTest.MasterDetectorExpireSlaveZKSessionNewMaster (3459 ms) On Thu, Jun 13, 2013 at 8:59 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Ben, +1 from me (binding) SIGS pass (minor nit: your GPG key should probably be made available at id.apache.org http://id.apache.org, which will in turn make it available here http://people.apache.org/keys/group/mesos.asc) I was able to import Ben's key: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% gpg --keyserver pgpkeys.mit.edu http://pgpkeys.mit.edu --recv-key D141A5B6 gpg: requesting key D141A5B6 from hkp server pgpkeys.mit.edu http://pgpkeys.mit.edu gpg: key D141A5B6: public key Benjamin Mahler benjamin.mah...@gmail.com imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Good signature from Benjamin Mahler benjamin.mah...@gmail.com gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E3A6 E5EF 7B67 C142 5B53 F072 D0BE BB95 D141 A5B6 [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% CHECKSUMS pass: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.12.0-incubating.tar.gz: OK [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% BUILD OK: [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% ./configure --disable-java checking build system type... x86_64-apple-darwin12.4.0 checking host system type... x86_64-apple-darwin12.4.0 checking target system type... x86_64-apple-darwin12.4.0 ..long time byte-compiling build/bdist.macosx-10.8-intel/egg/_mesos.py to _mesos.pyc creating build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/PKG-INFO - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/SOURCES.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/dependency_links.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/requires.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO writing build/bdist.macosx-10.8-intel/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.12.0-py2.7-macosx-10.8-intel.egg' and adding 'build/bdist.macosx-10.8-intel/egg' to it removing 'build/bdist.macosx-10.8-intel/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, June 10, 2013 5:05 PM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) 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 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=57d7 https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d 7 b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http
[RESULT] [VOTE] Graduation of Apache Mesos
Hi Folks, OK, this VOTE has passed with the following tallies: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik Christian Grobmeier* Henry Saputra* Alex Karasulu* Roman Shaposhnik* Alan Cabrera* * - indicates IPMC I'll go ahead and add the resolution to the board agenda for consideration at our June 2013 meeting. 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 1:03 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Graduation of Apache Mesos 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
Re: [PROPOSAL] Creation of the Incubator Ombudsman
I'm not in favor of an Ombudsman. Seems like an extra layer of overhead beyond what the Chair already provides. Seriously does someone need a title in order to be the clearinghouse for folks' honest assessments of the Incubator, its personnel, or other sensitive issues? My 2c. 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: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, June 17, 2013 7:11 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Creation of the Incubator Ombudsman On Sun, Jun 16, 2013 at 8:55 PM, Alex Harui aha...@adobe.com wrote: Just curious, is the ombudsman not allowed to be a mentor for a podling? Otherwise, that podling doesn't have a safe third-party? Good point. Podlings are heavily dependent on their Mentors, especially for providing IPMC votes on releases. If you offend a Mentor and they leave, will you be able to find someone else from the limited pool of IPMC members? A reluctance to speak out is very understandable. Put another way, when the ombud is also a Mentor, the military-justice analogy seems valid. I suppose that if the IPMC Chair is not the same as the ombud, they could serve as a backup ombud. That would satisfy your concern so long as the ombud and the Chair aren't both Mentors for the same podling. 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: [DISCUSS] Merits of pTLP idea
Hey Ross, Thanks for taking the time to reply. Mine are inline below: -Original Message- From: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, June 15, 2013 3:50 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Merits of pTLP idea On 14 June 2013 18:11, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: 2. It's harder to discharge a pTLP rather than a podling Jim, Ross: It's going to be harder to pick up the pieces if pTLPs are unsuccessful, than it would be for a podling. I think that is a misrepresentation of what has been said. It's not about picking up the pieces it's about providing adequate mentoring to give a project fighting chance. I guess you and I can agree to disagree that those two different cases don't end up the same result/Net effect -- which they do. Picking up the pieces should a project fail is easy. Preventing a project from unnecessarily failure is less easy. I estimate I've worked with something like 50 new project teams over the years. More than half of them outside the ASF. In my experience the success or failure of a project (assuming a good engineering team and a genuinely useful product) is less to do with the people doing the development work and more to do with the guidance those smart people get at key decision points relating to the open source model. And I'd estimate that I'd worked with at least that many if not more, both within and inside government, outside in academia, in private industry and others. Based on my experience it's actually more of an even distribution of both -- you can't succeed without the people doing the development work, and you can't succeed without those people being high caliber. Mentorship is key and you need high caliber there too, but I'd expect the balance to be 50/50. So it's not about picking up the pieces it's about spotting when the process is failing early enough to fix it and then having the right vehicle to provide support. In the majority of cases the mentoring model we have is perfect. It works far more than it fails. When it fails the problem is ISSUE 01 coupled with 03 (all other issues are symptoms of those issues in my opinion). pTLP can help address this but not, in my opinion, when coupled to your larger dismantling proposal. Ross: pTLP is a *part* of my deconstruction proposal. Stop trying to act like I didn't suggest it -- steps 4/5 in my proposal. I suggested it. Nearly 2 years ago. Further as becomes clear below in your replies, you are also missing the part _where_I_am_agreeing_with_you_about_incremental_steps :) I keep saying my proposal is a series of steps that can be executed incrementally, but when taken together when the dust clears, you will have a dismantled Incubator -- not a dismantled Incubation process. The process rocks. The mentorship is as best as can be expected when it works. The collective whole of a decision making body of 170 people..doesn't. And it sucks. I want to explore pTLP as part of the existing incubation process, not as a replacement for it. Precisely how that will work requires some experimentation - hence the Stratos proposal. 3. There isn't any benefit to implementing pTLPs Jim: I see no real benefit to implementing pTLPs. Chris: The benefits would immediately be that they don't have to go in front of a 170+ person committee to get a decision. Chris, podlings that don't hit ISSUE 01 (that's the majority) don't have to go to the IPMC now. Why are you claiming they do? The process is one of *notification* that a vote has been conducted not one of review. If mentors allow the IPMC to get in the way that's a failing of the mentors not the process. In the 18+ projects I've mentored at the ASF we have only ever once had to request an IPMC member vote. Once. Even then it was painless because we had a brilliant mentor who had already addressed all the issues in the release (not me I hasten to add - thanks Ate). Sometimes it has taken some robust protection of the podling here in the IPMC lists (take a look at some of my posts relating to AOO for example), but that's part of the job of a mentor in my opinion. Ross -- look what you just said. You said that one of the big successes you and your podlings have had over the years is keeping those podlings away from the IPMC. Shouldn't that suggest that there is something wrong with the IPMC? There is. I didn't say that there is something wrong with Incubation and Mentors I said IPMC. Note there is a key legal definition and difference. My proposal (pTLP being an incremental step in it) precisely calls out what you said above as an issue, see the heading titled: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal Mentors encourage their podlings to operate autonomously In my proposed experiment I want to take the advantages of the pTLP (specifically it clearly defines
Re: [PROPOSAL] Creation of the Incubator Ombudsman
+1, the chair is already the Ombudsman. Or should be at least. No need for duplication and more overhead (and confusion). ++ 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: Joseph Schaefer joe_schae...@yahoo.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, June 15, 2013 10:52 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Creation of the Incubator Ombudsman This is a suggestion that has come up in the past, and the typical counter-argument is that this is something the chair needs to provide themselves. Sent from my iPhone On Jun 15, 2013, at 1:18 PM, Ross Gardler rgard...@opendirective.com wrote: Sent from a mobile device, please excuse mistakes and brevity On 15 Jun 2013 16:53, Alan Cabrera a...@toolazydogs.com wrote: Problem: podlings are confused on where to go when there's a problem. Cause: we seem to collect/handle/organize problems in an ad hoc manner and sometimes mentors are the problem. Solution: we create an elected Incubator Ombudsman. From now on I'm only going to look at solutions in the context of the issues on the wiki page. If a proposal doesn't apply to one or more issues I'm not interested. In this case... The only problem that would need an ombudsmen is ISSUE 01 (inactive mentors). Mentors should always know where to go to solve a problem (we have specialist committees for pretty much every issue that will arise). If mentors are inactive then ISSUE 01 is in play. The current place to go is the IPMC. At this point ISSUE 03 may well come into play. The idea of an Ombudsman overlaps with my earlier proposal for a psuedo-board in the IPMC. Its also similar to both suggested solutions for ISSUE 03 in the wiki. For these reasons I suggest the Ombudsmen proposal has merit. I also suggest that this ombudsmen could be the organisation responsible for acting if a podling (or a pTLP, if the experiment shows merit in this model) is failing. As always the details needs to be ironed out but since the proposal directly addresses ISSUE 03 I would like to see it explored. I especially like that it complements my pTLP experiment which is designed to address ISSUE 01 (but clearly your proposal is worth exploring even without that potential advantage). Ross Regards, Alan - 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] Accept Stratos proposal as an incubating project
+1 binding. 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 14, 2013 2:49 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept Stratos proposal as an incubating project 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
Of course, I'm fully supportive of the pTLP concept as I believe it begins to implement parts of the proposal I threw up. BTW, note there aren't a ton of options besides the recent one on the wiki proposed by Bertrand, and added to by Alan, Ant, Ross and a lot of others. Those are concerns/issues with the Incubator. They aren't a proposal of what to do. Someone please point me to something that's been as discussed; worked on; and that contains a responsibility transition matrix. A *lot* of thought has went into this. I'm not just whining throw out the Incubator; it sucks -- I'm saying here's a set of incremental actions that taken as a whole, or individually towards an eventual whole will still allow projects to come into our Foundation, but to do so in a way that's a more natural fit for where we want these projects to end up anyways. I would urge the board to consider: * I've spent a great deal of time discussing the benefits and pitfalls of the approach with people at length for nearly 2 years now. So, no need to rehash those, I request folks to do research in the archives for the threads Incubation yes, Incubator no by Bill Rowe, anything that references the Incubator Deconstruction Proposal, etc. * pTLP are nothing different than what existed before there was an Incubator. Yes we have more projects now. So what. We'll continue to have more projects and those will eventually graduate to TLP, so we'll be in the same place. * This is an incremental step in the deconstruction proposal. We aren't saying implement the whole thing at once -- we are taking some constructive steps here (including what happened RE: discussion on the ComDev side of inheriting the docs). Let's get some data points here, report back, etc., in the vein of Apache with the small incremental, reversible change part. * The board needs to [DISCUSS] this. It's an important issue and I have a few podlings in mind already that would fit the pTLP concept. Kudos to Ross for having the courage to push this forward. Note, Ross was one of the most vocal discussers, seeing both the merit and potential pitfalls of my proposal. In short, if I've got Ross convinced enough to at least try it, then give it a chance. 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 14, 2013 6:48 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project On 14 June 2013 14:45, Jim Jagielski j...@jagunet.com wrote: On Jun 14, 2013, at 9:31 AM, Ross Gardler rgard...@opendirective.com wrote: Thanks for your comments Jim. You will see from the archives that I share most of your concerns about probationary TLPs. However a number of IPMC members have argued strongly for the concept. To be clear, the only info that seems official about pTLPs is the Wiki page proposal: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal IMO, it simply doesn't provide enough meat, details and rationale for me to be able to commit to it enough; there's a difference between the concept and the implementation of that concept. Agreed (and partially discussed elsewhere in this thread). Greg outlines a minimum he wants to see from the proposal to the board. I agree with his minimum and will be looking to two supporters of the pTLP concept to coordinate delivery of that minimum (I discussed this with both of them prior to make this suggestion, both agreed). Ross - 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: [DISCUSS] Accept Stratos as an Apache Incubation Project
I'm putting my replies to this in a separate thread, and going to combine responses to Shane and Jim in it too since pTLP is not only related to accepting Stratos as an Apache Incubation project. ++ 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 14, 2013 8:38 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project On 14 June 2013 15:42, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Those are concerns/issues with the Incubator. They aren't a proposal of what to do. For concrete suggestions about how to address the issues in the wiki take a look at the solutions section under each issue. All issue have at least one suggestion, many have more. * pTLP are nothing different than what existed before there was an Incubator. Sorry Chris, I disagree. It is *very* different. Where it isn't so different is in cases where there are plenty of experienced and active mentors (I believe Stratos is one such case which is why I proposed it as a test case). * This is an incremental step in the deconstruction proposal. Not for me it isn't. It's an incremental step towards finding the merits in your proposal for a specific type of project. I have never supported the deconstruction proposal and I trust people (including the board when the IPMC makes its recommendations) are clear on this. My championing of this proposal should not be seen as a championing of the whole deconstruction idea. Note, Ross was one of the most vocal discussers, seeing both the merit and potential pitfalls of my proposal. In short, if I've got Ross convinced enough to at least try it, then give it a chance. The only thing you have convinced me of is that there is no opportunity to find the merits while this pTLP idea is wrapped up in the larger deconstruction proposal. I made this clear in the initial proposal of the idea and I made it clear in my response to Jim. I'm making it clear again here. I want to expose the merits and avoid the pitfalls of your larger proposal. I am *not* adding my weight to your larger proposal. I am merely moving past an incomplete wiki page with practical activity. I will do the same with many of the other proposals that have merit (e.g. Ant has started to build momentum behind his tooling suggestions, |I hope to help there too). Ross 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 14, 2013 6:48 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project On 14 June 2013 14:45, Jim Jagielski j...@jagunet.com wrote: On Jun 14, 2013, at 9:31 AM, Ross Gardler rgard...@opendirective.com wrote: Thanks for your comments Jim. You will see from the archives that I share most of your concerns about probationary TLPs. However a number of IPMC members have argued strongly for the concept. To be clear, the only info that seems official about pTLPs is the Wiki page proposal: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal IMO, it simply doesn't provide enough meat, details and rationale for me to be able to commit to it enough; there's a difference between the concept and the implementation of that concept. Agreed (and partially discussed elsewhere in this thread). Greg outlines a minimum he wants to see from the proposal to the board. I agree with his minimum and will be looking to two supporters of the pTLP concept to coordinate delivery of that minimum (I discussed this with both of them prior to make this suggestion, both agreed). Ross
[DISCUSS] Merits of pTLP idea
Snipping this part out since this isn't directly related to Stratos:
Let's start with these point made by Ross, Shane and Jim. I start out
with my interpretation of their sentiments. These are my own. If they
are wrong my bad.
1. pTLPs *are* different.
Shane, Jim: pTLPs are different from a brand and community perspective.
Shane says that the outside world who arguably doesn't really get what
podlings
are nee see Open Office press releases and pre-media; and also pre-media
for other recent podlings before they became podlings including Flex [2]
and other projects will be more confused by pTLPs since they assume
the whole process of moving through a work flow of
podling-work toward graduation [licensing;releases;new
committers/PMC;diversity]-graduation [or retire]
is something that is known and has been educated to the outside world.
This is
what I think Jim is talking about when he says he likes what the Incubator
does
in terms of growing an Apache community.
Chris: I agree with both of the sentiments above. To me that's the whole
notion of Incubation,
yes; Incubator no. In other words, why do we need a meta committee of
170+ individuals
to have oversight (ha!) over the above process?? What better example of
the board kicking
the can down the road, and doing it in a ridiculously unsustainable way.
The above *process*
*should* exist. It's great. That's why I say Incubation *should* exist.
Should the Incubator aka
from a legal perspective, a committee; a home; a brand (if it even has
one?) exist? I say
Incubator, no. We can do all the above b/c our TLP projects do all of
the above. The
board does have oversight of those projects, but it disperses that
oversight into
the great decentralized leadership that our communities have.
2. It's harder to discharge a pTLP rather than a podling
Jim, Ross: It's going to be harder to pick up the pieces if pTLPs are
unsuccessful, than
it would be for a podling.
Chris: Please explain to me how this is? Wouldn't the process work very
similarly:
1. time to get rid of {pTLP|podling}
- [DISCUSS] threads, to get community involved
- community leaders jump in (this happens in the Incubator too; see
Mesos)
2. Based on results of #1
- retire
- continue with some measurements X months down the road
3. If continued from #2
- remeasure; if no progress, retire
- if progress, great, eventually converge to optimality and health again
(or not)
Yes, those are the community aspects. Let's talk infrastructure.
Discharging projects
whether they are pTLP or podling are fairly similar I'd imagine (mailing
lists; SVN,
archives; perms, etc.) Let's talk brand/IP -- depends on how far along the
pTLP or
podling got with this, either way this involves some careful work, pTLP or
podling or not.
3. There isn't any benefit to implementing pTLPs
Jim: I see no real benefit to implementing pTLPs.
Chris: The benefits would immediately be that they don't have to go in
front of a 170+ person
committee to get a decision. Those doing the work in the project will have
binding
VOTEs, and they will operate that way. For oversight they have 3 ASF
members watching
them (this *should* be the way that podlings work now -- but in reality we
only have
a requirement of 1+ ASF member -- the Champion/Mentor -- that's it -- see
recent
threads in Incubator where Ant and I uncovered this). So, we make pTLPs
have a requirement
of 3 ASF members.
Other benefits would also be in release VOTEs where those doing the
releases could
have their VOTEs be binding (which they will anyways) -- and we'll have
the benefit
of members who've seen VOTEs before watching them, still having oversight,
and still
having it be distributed. The board isn't responsible -- the pTLP ASF
members are. The
board reviews the progress; it doesn't flex its muscle or hammer if it
doesn't have to.
OK hope that summarizes my thoughts and replies in a single email to the
recent replies.
Cheers,
Chris
[1]
http://www.infoworld.com/d/applications/apache-asserts-openoffice-stewardsh
ip-176140
[2]
http://www.peterelst.com/blog/2011/12/27/apache-flex-incubator-proposal-is-
up-for-a-vote/
-Original Message-
From: Ross Gardler rgard...@opendirective.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Friday, June 14, 2013 8:38 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
On 14 June 2013 15:42, Mattmann, Chris A (398J)
chris.a.mattm...@jpl.nasa.gov wrote:
Those are concerns/issues with the Incubator. They aren't
a proposal of what to do.
For concrete suggestions about how to address the issues in the wiki
take a look at the solutions section under each issue. All issue
have at least one suggestion, many have more.
* pTLP are nothing different than what existed before there was an
Incubator.
Sorry Chris, I disagree. It is *very* different. Where it isn't so
different is in cases where
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
+1 to all Greg's comments below. Thanks dude. 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: Greg Stein gst...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, June 14, 2013 6:32 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project Speaking as a Director, the Board will need a *definition* of probation. This is more than just a wiki page. I believe it needs to be a page laid down in www.a.o/dev/ that defines the constraints laid down upon a pTLP (I really like Ross' acronym there!). These differences/constraints should effectively match those we apply to podlings: release constraints, disclosures, etc. Next up will be a description/discussion of whether oversight is maintained with the move from IPMC to Board reporting (this is probably easy). The key point here is an argument on whether losing the IPMC oversight impacts the podling/pTLP, the Board, or the Foundation. There probably needs to be some kind of rough metric on what kind of podling makeup or proposal that could reasonably pass muster with the Board to become a pTLP. Frankly, the Board is going to be *very* subjective on what groups could become a pTLP. I believe there should be some kind of prose somewhere which states that a pTLP is going to be rare/subjective, and that $conditions are needed before even considering a proposal to the Board. Personally, I am hugely supportive of the pTLP concept, and am happy to see a candidate. Cheers, -g On Fri, Jun 14, 2013 at 4:23 AM, ant elder ant.el...@gmail.com wrote: I'm also +1 (and excited!) on trying out this as a probationary TLPs, and with doing that using the approaches outlined by Ross and others in other emails on this thread (which is basically having a vote now to accept this as a podling so we can get started and then working up a probationary TLP proposal for it to submit to the board meeting). I also commit that as mentor i'll help try to make that work well while at the same time provide oversight so that any issue that might arise do get reported. ...ant On Thu, Jun 13, 2013 at 3:12 AM, Ross Gardler rgard...@opendirective.comwrote: So here's a thought... There have been many discussions about different ways to incubate projects. One of the most radical ideas is to dismantle the incubator and replace the podling concept with probationary TLPs reporting to the board. As readers of this list will know I do not support the idea of dismantling the IPMC. I believe it does a great job that is not easily replaced by a board of nine directors. However, I have always acknowledged that the idea has merit under a certain set of circumstances. For me those circumstances are present in the Apache Stratos proposal. That is there are sufficient mentors and initial committers who are ASF Members that we can be reasonably certain that this project will succeed here at the ASF. I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. For my part my intention is to get the project set-up and then dissolve into the background. I do not intend to monitor the project on a day-to-day basis. However, I do promise to help pick up the pieces if the experiment should go horribly wrong. Of course running a single experiment will only allow us to define the incubation process for probationary TLPs, It is not going to solve all the problems Chris sees in the IPMC. However it will give us an opportunity to define the process, ask the board to approve this process and thus lay the foundations for other projects wishing to follow this path. So, what do you think? Ross On 11 June 2013 10:10, Ross Gardler rgard...@opendirective.com wrote: It's with great pleasure that I invite the IPMC to review a new proposal [1] for the Apache Incubator. Please let us know if you have any questions or comments - as you will see there are plenty of people on the initial commit
Re: Change of Chair
Welcome, Marvin! :) 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: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 13, 2013 7:31 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Change of Chair On Thu, Jun 13, 2013 at 2:03 PM, Benson Margulies bimargul...@gmail.com wrote: I have tendered my resignation as VP, Incubator. The PMC has recommend Marvin Humphrey as my successor in a motion submitted to the Foundation board for consideration at the meeting next week. Thank you for serving as Chair, Benson. I have very much enjoyed participating in the Incubator during your time in office. Thanks as well to everyone who has contributed to the Incubator over the years for having taught me so much, collectively; and thanks to the current members of the IPMC for honoring me with the Chair's responsibilities. I love my career as an open-source developer and I'm glad for the chances the Incubator provides to foster successful projects and make it easier for others to take the same path. For those reading this list who are not yet familiar with the role that a PMC Chair plays in the governance of a typical Apache project, the most visible task is to deliver a report to the Apache Software Foundation's Board of Directors every three months. Aside from that, the Chair generally participates in project development as an ordinary member of the PMC. Under normal circumstances, it is not a demanding job. http://www.apache.org/dev/pmc.html#chair The Incubator is different because it reports monthly and aggregates the reports of many podlings. Our report is the closest thing the Incubator has to a product, and when done well, it offers substantial value by keeping us coordinated and focused. However, well-done Incubator reports have historically required substantial individual effort by the Chair. My primary goal as Chair will be to streamline the report procedure. I hope to build institutions and increase automation in order that the Incubator may deliver consistently high-quality reports month after month regardless of any one person's availability as the board meeting approaches. Some ASF projects elect their PMC Chair annually; for others, the Chair may serve for an indefinite period. I have proposed to serve for six months and then make way for someone else -- both because I have other projects I am putting on hold and will want to return to, and because experience has taught me that rotating multiple people through a leadership role enriches the community and deepens involvement. If all goes well, perhaps my successor will not have to work as hard as I will to live up to the standards set by my predecessors. 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: [DISCUSS] Accept Stratos as an Apache Incubation Project
+1 of course from me, with a commitment to doing work to help out and making sure this doesn't fail; instead that it succeeds which I'm sure it will. I'll also sign up for a round of beers at the next ApacheCon. For sure! :) 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 7:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project So here's a thought... There have been many discussions about different ways to incubate projects. One of the most radical ideas is to dismantle the incubator and replace the podling concept with probationary TLPs reporting to the board. As readers of this list will know I do not support the idea of dismantling the IPMC. I believe it does a great job that is not easily replaced by a board of nine directors. However, I have always acknowledged that the idea has merit under a certain set of circumstances. For me those circumstances are present in the Apache Stratos proposal. That is there are sufficient mentors and initial committers who are ASF Members that we can be reasonably certain that this project will succeed here at the ASF. I would therefore like to propose that we use Apache Stratos as a test case for the probationary TLP idea. I've already talked to Chris (who is driving the deconstruct the IPMC case) and Ant (who is less keen on dismantling the IPMC but wants to see how a probationary TLP model will play out). Both have agreed to help with this experiment if the IPMC and the Board wish it to proceed. I have not, however, discussed it with all the initial comitters or even mentors - I'm expecting them to speak up now. For my part my intention is to get the project set-up and then dissolve into the background. I do not intend to monitor the project on a day-to-day basis. However, I do promise to help pick up the pieces if the experiment should go horribly wrong. Of course running a single experiment will only allow us to define the incubation process for probationary TLPs, It is not going to solve all the problems Chris sees in the IPMC. However it will give us an opportunity to define the process, ask the board to approve this process and thus lay the foundations for other projects wishing to follow this path. So, what do you think? Ross On 11 June 2013 10:10, Ross Gardler rgard...@opendirective.com wrote: It's with great pleasure that I invite the IPMC to review a new proposal [1] for the Apache Incubator. Please let us know if you have any questions or comments - as you will see there are plenty of people on the initial commit list ready and willing to answer your questions. I copy the full text of the proposal for your convenience: = Stratos - A PaaS Framework = == Abstract == Stratos will be a polyglot [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]] framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform-wide insight including monitoring and billing. == Proposal == The Stratos PaaS framework will encompass four layers: 1. An [[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|Ia aS]]-agnostic layer that can interface with a wide variety of IaaS systems to provide elastic resources, and for multiple IaaS infrastructures to be automated at one time (hybrid clouds.) 2. A PaaS Controller with a cloud controller that automates and monitors IaaS runtime interactions, distributes artifacts to the underlying runtimes, deploys workloads, directs runtime traffic to the right runtimes using a tenant-aware elastic load balancer, and provides a portal for monitoring and provisioning of tenants on the system. 3. Foundational Services including security, logging, messaging, registry, storage (relational, file, and noSQL), task management, and billing. Foundational services will be loosely-coupled to allow swapping in alternate foundational services. 4. A Cartridge Architecture allowing frameworks, servers, and other runtimes to participate in the advantages of the system. The Cartridge Architecture must support multi-tenant workloads, and provide for various levels of tenant isolation and policy-based
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Will do tonight, Ben :) ++ 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 13, 2013 5:56 PM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) 72 hours has passed and we have the following +1's: Binding (2 more needed): Alex Karasulu Non-Binding: Vinod Kone Deepal jayasinghe Brenden Matthews Yan Xu Could some IPMC members please take a look? It would be greatly appreciated! Ben 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] Release Apache Mesos 0.12.0-incubating (RC1)
Hi Ben, +1 from me (binding) SIGS pass (minor nit: your GPG key should probably be made available at id.apache.org, which will in turn make it available here http://people.apache.org/keys/group/mesos.asc) I was able to import Ben's key: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% gpg --keyserver pgpkeys.mit.edu --recv-key D141A5B6 gpg: requesting key D141A5B6 from hkp server pgpkeys.mit.edu gpg: key D141A5B6: public key Benjamin Mahler benjamin.mah...@gmail.com imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Good signature from Benjamin Mahler benjamin.mah...@gmail.com gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E3A6 E5EF 7B67 C142 5B53 F072 D0BE BB95 D141 A5B6 [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% CHECKSUMS pass: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.12.0-incubating.tar.gz: OK [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% BUILD OK: [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% ./configure --disable-java checking build system type... x86_64-apple-darwin12.4.0 checking host system type... x86_64-apple-darwin12.4.0 checking target system type... x86_64-apple-darwin12.4.0 ..long time byte-compiling build/bdist.macosx-10.8-intel/egg/_mesos.py to _mesos.pyc creating build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/PKG-INFO - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/SOURCES.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/dependency_links.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/requires.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO writing build/bdist.macosx-10.8-intel/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.12.0-py2.7-macosx-10.8-intel.egg' and adding 'build/bdist.macosx-10.8-intel/egg' to it removing 'build/bdist.macosx-10.8-intel/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. [chipotle:~/tmp/apache-mesos-0.12.0/mesos-0.12.0] mattmann% 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, June 10, 2013 5:05 PM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) 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=57d7 b9719dce662881b162eba10b5765a807d53c 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
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
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] Accept Apache HotdoG into the Incubator
+1 binding. 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: Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 11:22 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept Apache HotdoG into the Incubator 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
[VOTE] Graduation of Apache Mesos
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 ++ - 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
Hi Joe, Thanks, I'll update the status page, the canonical set of Mesos committers/PPMC members is here (and also part of the proposed resolution below): http://people.apache.org/committers-by-project.html#mesos 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: Joe Brockmeier j...@zonker.net Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 1:31 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Graduation of Apache Mesos Have you updated your Incubator status page prior to this? I think there must be quite a few committers added since the proposal that are missing there. On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) 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
Re: [VOTE] Graduation of Apache Mesos
Woot awesome Andy! Sent from my iPhone On Jun 12, 2013, at 3:48 PM, Benjamin Hindman b...@eecs.berkeley.edu wrote: Thanks Andy! On Wed, Jun 12, 2013 at 3:35 PM, Andy Konwinski andykonwin...@gmail.comwrote: I've regenerated the incubator website and clutch so that the following live pages are now up to date: * our status page http://incubator.apache.org/projects/mesos.html * the list of projects page http://incubator.apache.org/projects/ * our entry on the clutch page http://incubator.apache.org/clutch.html, which shows all green except for our somewhat large # days in incubation, which implies it is about time we graduate! Andy On Wed, Jun 12, 2013 at 3:13 PM, Andy Konwinski andykonwin...@gmail.com wrote: Thanks Joe for pointing this out, Chris, I beat you to it. I updated the files that the status page http://incubator.apache.org/projects/mesos.html and list of projects page http://incubator.apache.org/projects/ (which lists our mentors) are generated from in SVN. Andy On Wed, Jun 12, 2013 at 3:11 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Joe, Thanks, I'll update the status page, the canonical set of Mesos committers/PPMC members is here (and also part of the proposed resolution below): http://people.apache.org/committers-by-project.html#mesos 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: Joe Brockmeier j...@zonker.net Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 1:31 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Graduation of Apache Mesos Have you updated your Incubator status page prior to this? I think there must be quite a few committers added since the proposal that are missing there. On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) 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
Re: Apache HotdoG interest?
ACK go for it ++ 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: Adam Estrada aestr...@apache.org Date: Saturday, June 8, 2013 3:18 PM To: jpluser chris.a.mattm...@jpl.nasa.gov Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: Apache HotdoG interest? +1 this sounds great! If I get an ACK, I will add myself to the project wiki ASAP! Thanks in advance, Adam. On Wed, Jun 5, 2013 at 10:51 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hey Adam, I noticed you were interested in Apache HotdoG -- would you like to join the project as an initial committer and PPMC member? I know you are interested in being a mentor; which requires you to be a member of the IPMC which at present you are not. That being said there is nothing stopping you from doing mentor-ish roles and tasks. Meaning, you can still help out with IPMC HotdoG reporting (should the project be accepted into the Incubator after our restarted VOTE and after we get a 3rd mentor from the IPMC to sign up ;) ); with the community for HotdoG and bringing new contributors to it; and of course with the code! Demonstration of these types of qualities is precisely the types of things we look for in a mentor and an IPMC member and there is nothing stopping you from doing that to help out HotdoG. Suggestion: (if the rest of the Hotdog community members have no objection; which are present during discussion they have not) 1. Adam adds himself as PPMC member and committer to: http://wiki.apache.org/incubator/HotdoGProposal 2. Should HotdoG be accepted as Apache Incubator project; Adam does mentor roles and participates that way. Adam that sound good? Thanks for your interest! 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 ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Spark for the Incubator
Note: we discussed adding Roman before the VOTE and it was fine with the incoming Spark community, so Roman is now on the wiki for the proposal. In case this changes anyone's VOTE on the VOTE thread, feel free to speak up or change your VOTE. Otherwise, nothing else to see here folks. 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: Roman Shaposhnik r...@apache.org Date: Saturday, June 8, 2013 3:03 PM To: jpluser chris.a.mattm...@jpl.nasa.gov Subject: Re: [PROPOSAL] Apache Spark for the Incubator On Mon, Jun 3, 2013 at 6:40 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Roman, I've conferred with the incoming Spark community and we are happy to have you as a mentor for the project. Feel free to add yourself to the wiki proposal. Great news! Done. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Spark for the Incubator
Hi Folks, OK discussion has died down, time to VOTE to accept Spark into the Apache Incubator. I'll let the VOTE run for at least a week. So far I've heard +1s from the following folks, so no need for them to VOTE again unless they want to change their VOTE: +1 Chris Mattmann* Konstantin Boudnik Henry Saputra* Reynold Xin Pei Chen Roman Shaposhnik* Suresh Marru* * -indicates IPMC [ ] +1 Accept Spark into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept Spark into the Apache Incubator because.. Proposal text is below. === 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 industry partners and collaborators are well aligned with our code base. There are also a number of related Apache projects and dependencies, that will be mentioned in the Relationships with Other Apache products section. == Known Risks == === Orphaned Products === Given the current level of investment in Spark - the risk of the project being abandoned is minimal. There are several constituents who are highly incentivized to continue development. The U.C. Berkeley AMPLab relies on Spark as a platform for a large number of long-term research projects. Several companies have build verticalized products which are tightly dependent on Spark. Other companies have devoted significant internal infrastructure investment in Spark. === Inexperience with Open Source === Spark has existed as a healthy open source project for several years. During that time, Matei and others have curated an open-source community successfully, attracting developers from a diverse group of
Re: [VOTE] Accept Apache MetaModel into the Apache incubator
+1 (binding). Good luck guys! 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: Thursday, June 6, 2013 3:30 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [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
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Paul, guys; I just noticed that HotdoG only has 2 mentors right now (myself, and pramirez). Is there another IPMC mentor that would be willing to sign up for the project? I think we should probably cancel the VOTE Paul, and restart it with another mentor. Besides that, Adam Estrada (VP, SIS) has expressed interest also in the proposal. So we should sort that out. Sorry for the delay, hopefully we can restart the VOTE shortly when we have a 3rd mentor and sort out Adam's participation. Paul can you send a [CANCEL] [VOTE] thread? 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 11:21 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Hey Jim, I think it should probably read: We're looking for people interested in HotDog and to move the proposal into the Apache Community. The project is moving from a previously open source external community into Apache. I've updated the proposal on the wiki as such: https://wiki.apache.org/incubator/HotdoGProposal 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: Jim Jagielski j...@jagunet.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 10:55 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: We're looking for developers and sponsors. Sponsors?? - 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
Apache HotdoG interest?
Hey Adam, I noticed you were interested in Apache HotdoG -- would you like to join the project as an initial committer and PPMC member? I know you are interested in being a mentor; which requires you to be a member of the IPMC which at present you are not. That being said there is nothing stopping you from doing mentor-ish roles and tasks. Meaning, you can still help out with IPMC HotdoG reporting (should the project be accepted into the Incubator after our restarted VOTE and after we get a 3rd mentor from the IPMC to sign up ;) ); with the community for HotdoG and bringing new contributors to it; and of course with the code! Demonstration of these types of qualities is precisely the types of things we look for in a mentor and an IPMC member and there is nothing stopping you from doing that to help out HotdoG. Suggestion: (if the rest of the Hotdog community members have no objection; which are present during discussion they have not) 1. Adam adds himself as PPMC member and committer to: http://wiki.apache.org/incubator/HotdoGProposal 2. Should HotdoG be accepted as Apache Incubator project; Adam does mentor roles and participates that way. Adam that sound good? Thanks for your interest! 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 ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Hey Alan, Great question if there is an official policy here. My read is that no it's based on tribal knowledge and informal assumption. That said, let's take a simple data point: how many proposals over the past few years have been accepted with less than 3 mentors (not considering like you mentioned that mentors do go AWOL from time to time and that over the life of a podling, there may be less than 3 active at a given time)? It's Paul's proposal as Champion so, up to him, but my recommendation would be to find 1 more wiling IPMC $victim..err mentor! 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: Alan Cabrera l...@toolazydogs.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 7:48 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Mentors come and go. Is there an explicit rule that a podling needs three mentors before it can start to be incubated? Regards, Alan On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Paul, guys; I just noticed that HotdoG only has 2 mentors right now (myself, and pramirez). Is there another IPMC mentor that would be willing to sign up for the project? I think we should probably cancel the VOTE Paul, and restart it with another mentor. Besides that, Adam Estrada (VP, SIS) has expressed interest also in the proposal. So we should sort that out. Sorry for the delay, hopefully we can restart the VOTE shortly when we have a 3rd mentor and sort out Adam's participation. Paul can you send a [CANCEL] [VOTE] thread? 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 11:21 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Hey Jim, I think it should probably read: We're looking for people interested in HotDog and to move the proposal into the Apache Community. The project is moving from a previously open source external community into Apache. I've updated the proposal on the wiki as such: https://wiki.apache.org/incubator/HotdoGProposal 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: Jim Jagielski j...@jagunet.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 10:55 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: We're looking for developers and sponsors. Sponsors?? - 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
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Precisely, Ross. 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 7:51 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator There is no explicit rule (to my knowledge). The number 3 came about because that's how many votes are needed for a release. With 3 mentors on the project it means the project needs to come to the IPMC for additional votes. As we've seen this can become very messy. Ross On 5 June 2013 15:48, Alan Cabrera l...@toolazydogs.com wrote: Mentors come and go. Is there an explicit rule that a podling needs three mentors before it can start to be incubated? Regards, Alan On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Paul, guys; I just noticed that HotdoG only has 2 mentors right now (myself, and pramirez). Is there another IPMC mentor that would be willing to sign up for the project? I think we should probably cancel the VOTE Paul, and restart it with another mentor. Besides that, Adam Estrada (VP, SIS) has expressed interest also in the proposal. So we should sort that out. Sorry for the delay, hopefully we can restart the VOTE shortly when we have a 3rd mentor and sort out Adam's participation. Paul can you send a [CANCEL] [VOTE] thread? 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 11:21 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Hey Jim, I think it should probably read: We're looking for people interested in HotDog and to move the proposal into the Apache Community. The project is moving from a previously open source external community into Apache. I've updated the proposal on the wiki as such: https://wiki.apache.org/incubator/HotdoGProposal 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: Jim Jagielski j...@jagunet.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 10:55 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: We're looking for developers and sponsors. Sponsors?? - 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
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Alan, Stop putting words in my mouth. I'm not suggesting tweaking anything nor changing Incubator process. Notice I said I think we should probably.. Please tell me where I said You [or we] must.. Again, it's Ramirez's call since he put the proposal up and is the Champion. If he gets at least 3 IPMC +1s in a new thread (which it looks like he will create), nothing has changed, all is well. 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: Alan Cabrera l...@toolazydogs.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 8:00 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Please, let's not make up new rules as we go along. To be sure as IPMC members we should proactively inform the prospective podling of the potential problems they will encounter entering the Incubator with less than 3 mentors. It would commendable if IPMC members actively hunted such mentors down for the potential podling. But let's not do ad hoc tweaking to our processes. Let's keep things simple and let the vote continue. Regards, Alan On Jun 5, 2013, at 7:54 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hey Alan, Great question if there is an official policy here. My read is that no it's based on tribal knowledge and informal assumption. That said, let's take a simple data point: how many proposals over the past few years have been accepted with less than 3 mentors (not considering like you mentioned that mentors do go AWOL from time to time and that over the life of a podling, there may be less than 3 active at a given time)? It's Paul's proposal as Champion so, up to him, but my recommendation would be to find 1 more wiling IPMC $victim..err mentor! 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: Alan Cabrera l...@toolazydogs.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 7:48 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Mentors come and go. Is there an explicit rule that a podling needs three mentors before it can start to be incubated? Regards, Alan On Jun 5, 2013, at 7:37 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Paul, guys; I just noticed that HotdoG only has 2 mentors right now (myself, and pramirez). Is there another IPMC mentor that would be willing to sign up for the project? I think we should probably cancel the VOTE Paul, and restart it with another mentor. Besides that, Adam Estrada (VP, SIS) has expressed interest also in the proposal. So we should sort that out. Sorry for the delay, hopefully we can restart the VOTE shortly when we have a 3rd mentor and sort out Adam's participation. Paul can you send a [CANCEL] [VOTE] thread? 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 11:21 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator Hey Jim, I think it should probably read: We're looking
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Right Ant, that official policy doesn't say 3, and I found the same one (hoping that it said 3; or at least said NOT 3, so it would be definitive, which it's not in any other form besides 1) Regardless, like I said, VOTE cancelled, so this is moot so would be great to let this thread die now :) 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: ant elder ant.el...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 8:07 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator On Wed, Jun 5, 2013 at 3:54 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hey Alan, Great question if there is an official policy here. My read is that no it's based on tribal knowledge and informal assumption. There is an official policy which is documented on the Incubator policy page. That says A Podling has one or more Mentors, one of which MUST be an Apache Member. - http://incubator.apache.org/incubation/Incubation_Policy.html#Mentor I think its fine to carry on without three, mentors come and go and can easily be added if more are required. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Looking at: http://people.apache.org/committers-by-project.html#incubator-pmc It would seem that there would be a cn for incubator-pmc in LDAP. So I tried running modify_committee.pl on mino and got back: No LDAP groups found with cn=incubator-pmc! So either I'm doing that wrong or don't have the karma. 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: Alan Cabrera l...@toolazydogs.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 5, 2013 8:40 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator On Jun 5, 2013, at 8:37 AM, Greg Reddin gred...@gmail.com wrote: On Wed, Jun 5, 2013 at 10:26 AM, Alan Cabrera l...@toolazydogs.com wrote: On Jun 5, 2013, at 8:21 AM, Greg Reddin gred...@gmail.com wrote: Added my name to the proposal. I'm willing to mentor. Benson, One of my podling tools doesn't see that Greg is on the IPMC though he is an ASF member. I think we need to update the LDAP entries if he's already been ACK'd. Greg Stein pointed out yesterday that the ACK date was 3/15/2010 Great, just need someone with the karmic powers to do the needful. :) Regards, Alan - 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 Apache HotdoG into the Incubator
+1 (binding). 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: Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 10:28 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept Apache HotdoG into the Incubator 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
[DISCUSS] [VOTE] Accept Apache HotdoG into the Incubator
Hey Jim, I think it should probably read: We're looking for people interested in HotDog and to move the proposal into the Apache Community. The project is moving from a previously open source external community into Apache. I've updated the proposal on the wiki as such: https://wiki.apache.org/incubator/HotdoGProposal 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: Jim Jagielski j...@jagunet.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, June 4, 2013 10:55 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Accept Apache HotdoG into the Incubator On Jun 4, 2013, at 1:28 PM, Ramirez, Paul M (398J) paul.m.rami...@jpl.nasa.gov wrote: We're looking for developers and sponsors. Sponsors?? - 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] Apache Spark for the Incubator
Hi Henry, Thanks for your support! I will leave it up to Matei and the incoming Spark community to decide if they would like to add you (or anyone else) to the wiki as a contributor on the project. Thanks! 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 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
Re: [PROPOSAL] Apache Spark for the Incubator
Thanks for the support, Pei. I think the questions you had about frameworks/etc., hopefully were answered. 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: Chen, Pei pei.c...@childrens.harvard.edu Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 11:45 AM To: general@incubator.apache.org general@incubator.apache.org Subject: RE: [PROPOSAL] Apache Spark for the Incubator +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
Re: [PROPOSAL] Apache Spark for the Incubator
Thanks for the support Roman! I will leave it up to the incoming Spark community members to decide if they need more mentors and we'll be in touch. Thank you again. 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: Roman Shaposhnik r...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 3:25 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator Extremely enthusiastic +1!!! If you ever need help with mentorship -- please let me know. Also, looking forward to seeing this in Bigtop! Thanks, Roman. 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
Re: [VOTE] Accept Apache BeanShell in the Incubator
+1 (binding). 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: Simone Tripodi simonetrip...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 24, 2013 12:23 AM To: general@incubator.apache.org general@incubator.apache.org Subject: [VOTE] Accept Apache BeanShell in the Incubator Dear ASF members, We would like to propose BeanShell for the incubator. The proposal draft is available at: https://wiki.apache.org/incubator/BeanShellProposal, follows below the proposal Open is open for at least 72h and closes approximately on May 27th at 8:20am GMT [ ] +1 accept BeanShell in the Incubator [ ] +/-0 [ ] -1 because (provide a reason) Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ ~~ ~ = BeanShell = == Abstract == The following proposal is about BeanShell, see JSR-274: The BeanShell Scripting Language implementation. == Proposal == BeanShell is a small, free, embeddable Java source interpreter with object scripting language features, written in Java. BeanShell dynamically executes standard Java syntax and extends it with common scripting conveniences such as loose types, commands, and method closures like those in Perl and JavaScript. Users can use BeanShell interactively for Java experimentation and debugging as well as to extend your applications in new ways. Scripting Java lends itself to a wide variety of applications including rapid prototyping, user scripting extension, rules engines, configuration, testing, dynamic deployment, embedded systems, and even Java education. BeanShell is small and embeddable, so users can call BeanShell from Java applications to execute Java code dynamically at run-time or to provide extensibility in applications. Alternatively, users can use standalone BeanShell scripts to manipulate Java applications; working with Java objects and APIs dynamically. Since BeanShell is written in Java and runs in the same VM as application, users can freely pass references to live objects into scripts and return them as results. == Background == BeanShell is a long living project born in the 2000 thanks to Patrick Niemeyer initial effort, who is still maintaining the project, with the help of Daniel Leuck and contributions voluntarily sent by users. == Rationale == Currently there are no projects hosted by the ASF focused on providing JSR-274 implementation, moving the existing BeanShell project under the Apache umbrella would mean the ASF provides the JSR-274 reference implementation. = Current Status = == Meritocracy == The historical BeanShell team believes in meritocracy and always acted as a community. Mailing list, open issue tracker and other communication channels have always been adopted since its first release. The adoption in a larger community, such as Apache, is the natural evolution for BeanShell. Moreover, the Apache standards will enforce the existing BeanShell community practices and will be a foundation for future committers involvement. == Core Developers == In alphabetical order: * Daniel Leuck dan at ikayzo dot com, * Patrick Niemeyer pat at ikayzo dot com * Pedro Giffuni pfg at apache dot org * Simone Tripodi simonetripodi at apache dot org == Alignment == Main aim of the project is to develop and maintain a fully flavored JSR-274 implementation that can be used by other Apache projects that need a Java Scripting Language. = Known Risks = == Orphaned Products == The increasing number of BeanShell adopters and the raising interest for the JSR-274 technology let us believe that there is a minimal risk for this work to being abandoned from the community. Moreover, BeanShell has been already used by the following projects for years: * Apache OpenOffice * Apache Maven * Apache JMeter == Inexperience with Open Source == All of the committers have experience working in one or more open source projects inside and outside ASF. == Homogeneous Developers == The list of initial committers are geographically distributed across the world with no one company being associated with a majority of the developers. Many of these initial developers are experienced Apache committers already and all are experienced with working in distributed development communities. == Reliance on
Re: [PROPOSAL] Apache Spark for the Incubator
Thanks Suresh, after conferring with the incoming Spark community members, I will add you as a mentor on 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: Suresh Marru sma...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, June 1, 2013 9:12 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator On May 31, 2013, at 2:03 PM, 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. Thanks Chris for the alert. Great proposal indeed, if the podling needs help I am in. Suresh 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
Re: [PROPOSAL] Apache Spark for the Incubator
Hi Konstantin, Thanks for your kind words and expressed interest. I will leave it to Matei and the incoming Spark community members to comment on adding you (or anyone else) as a contributor to the wiki. If they are OK with it, then I am very much too. 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: Konstantin Boudnik c...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 12:29 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator Great news! Definitely +1 (non-binding, I guess) on adding Spark to the family of ASF project! I also express the interest to contribute to the project and move it forward to the graduation! Bigtop has been packaging and providing Spark as a part of Hadoop 1.x software stacks for some time; and hopefully would be able to offer it as a part of Hadoop 2.x line in the coming days. Dr. Konstantin Boudnik Hadoop committer BigTop PMC On Fri, May 31, 2013 at 06:03PM, Mattmann, Chris A (398J) 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
Re: [PROPOSAL] Apache Spark for the Incubator
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 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
Re: [PROPOSAL] Apache Spark for the Incubator
Hi Roman, I've conferred with the incoming Spark community and we are happy to have you as a mentor for the project. Feel free to add yourself to the wiki proposal. 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: Roman Shaposhnik r...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 3:25 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator Extremely enthusiastic +1!!! If you ever need help with mentorship -- please let me know. Also, looking forward to seeing this in Bigtop! Thanks, Roman. 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
Re: [PROPOSAL] Apache Spark for the Incubator
Dear Konstantin, Thanks! The incoming Spark project is excited about the relationship with Bigtop that could happen here. As for new committers, after conferring with the Spark project members, we would like to adopt a simple policy of having all new committers not add themselves to the wiki as of yet, but simply join the project mailing lists when they are created, and then from there, contribute. I and other mentors, and the Spark community are committed to being inclusive, so hopefully won't take too long for anybody to become a PPMC member/committer on the project after some demonstrated contributions. Thanks for your interest and again for your kind words. 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: Konstantin Boudnik c...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 12:29 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Spark for the Incubator Great news! Definitely +1 (non-binding, I guess) on adding Spark to the family of ASF project! I also express the interest to contribute to the project and move it forward to the graduation! Bigtop has been packaging and providing Spark as a part of Hadoop 1.x software stacks for some time; and hopefully would be able to offer it as a part of Hadoop 2.x line in the coming days. Dr. Konstantin Boudnik Hadoop committer BigTop PMC On Fri, May 31, 2013 at 06:03PM, Mattmann, Chris A (398J) 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
Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)
+1 from me (binding). Verified GPG keys: [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% curl http://www.apache.org/dist/incubator/mesos/KEYS KEYS % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 7192 100 71920 0 13447 0 --:--:-- --:--:-- --:--:-- 20202 [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% gpg --import KEYS gpg: key F6FB762C: Benjamin Hindman b...@apache.org not changed gpg: key 1B207A4D: Andy Konwinski (CODE SIGNING KEY) and...@apache.org not changed gpg: Total number processed: 2 gpg: unchanged: 2 [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Tue May 28 11:14:54 2013 PDT using RSA key ID 5C6E508C gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% gpg --keyserver pgpkeys.mit.edu --recv-key 5C6E508C gpg: requesting key 5C6E508C from hkp server pgpkeys.mit.edu gpg: key 5C6E508C: public key Vinod Kone (Key for signing Apache releases) vinodk...@apache.org imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Tue May 28 11:14:54 2013 PDT using RSA key ID 5C6E508C gpg: Good signature from Vinod Kone (Key for signing Apache releases) vinodk...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F8C2 3D78 85E7 9F19 7508 AF5B 2B1D 89DA 5C6E 508C [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% ^^ minor nit ^^ Would be nice to make sure Vinod's key is in our KEYS file. Verified MD5 sigs: [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.11.0-incubating.tar.gz: OK [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% Build and ran tests: [chipotle:~/tmp/apache-mesos-0.11.0-rc3/mesos-0.11.0] mattmann% ./configure --disable-java checking build system type... i386-apple-darwin12.3.0 checking host system type... i386-apple-darwin12.3.0 checking build system type... (cached) i386-apple-darwin12.3.0 checking target system type... i386-apple-darwin12.3.0 checking for a BSD-compatible install... /usr/bin/install -c ..long time.. copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO writing build/bdist.macosx-10.8-intel/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.11.0-py2.7-macosx-10.8-intel.egg' and adding 'build/bdist.macosx-10.8-intel/egg' to it removing 'build/bdist.macosx-10.8-intel/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. [chipotle:~/tmp/apache-mesos-0.11.0-rc3/mesos-0.11.0] mattmann% Great work Vinod and community! Since the 72 hour window is passed, Vinod you can send the [RESULT] [VOTE] thread, tally the VOTEs, and push the release. 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: Vinod Kone vi...@twitter.com Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Tuesday, May 28, 2013 11:24 AM To: general@incubator.apache.org general@incubator.apache.org, mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3) Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.11.0. This will be the third incubator release for Mesos in Apache . The candidate for Mesos 0.11.0-incubating release is available at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11 .0-incubating.tar.gz The tag to be voted on: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbca a0d348a88188c17a8b06b57306832a7a5885 The MD5 checksum of the tarball can be found at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11 .0-incubating.tar.gz.md5 The signature of the tarball can be found at:
Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)
Hey Guys, Sorry looks like current tally only includes 2 IPMC +1s. We need 1 more IMPC positive VOTE. Can someone on the IPMC review please? 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Saturday, June 1, 2013 10:38 AM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org, general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3) +1 from me (binding). Verified GPG keys: [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% curl http://www.apache.org/dist/incubator/mesos/KEYS KEYS % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 7192 100 71920 0 13447 0 --:--:-- --:--:-- --:--:-- 20202 [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% gpg --import KEYS gpg: key F6FB762C: Benjamin Hindman b...@apache.org not changed gpg: key 1B207A4D: Andy Konwinski (CODE SIGNING KEY) and...@apache.org not changed gpg: Total number processed: 2 gpg: unchanged: 2 [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Tue May 28 11:14:54 2013 PDT using RSA key ID 5C6E508C gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% gpg --keyserver pgpkeys.mit.edu --recv-key 5C6E508C gpg: requesting key 5C6E508C from hkp server pgpkeys.mit.edu gpg: key 5C6E508C: public key Vinod Kone (Key for signing Apache releases) vinodk...@apache.org imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Tue May 28 11:14:54 2013 PDT using RSA key ID 5C6E508C gpg: Good signature from Vinod Kone (Key for signing Apache releases) vinodk...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F8C2 3D78 85E7 9F19 7508 AF5B 2B1D 89DA 5C6E 508C [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% ^^ minor nit ^^ Would be nice to make sure Vinod's key is in our KEYS file. Verified MD5 sigs: [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.11.0-incubating.tar.gz: OK [chipotle:~/tmp/apache-mesos-0.11.0-rc3] mattmann% Build and ran tests: [chipotle:~/tmp/apache-mesos-0.11.0-rc3/mesos-0.11.0] mattmann% ./configure --disable-java checking build system type... i386-apple-darwin12.3.0 checking host system type... i386-apple-darwin12.3.0 checking build system type... (cached) i386-apple-darwin12.3.0 checking target system type... i386-apple-darwin12.3.0 checking for a BSD-compatible install... /usr/bin/install -c ..long time.. copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.8-intel/egg/EGG-INFO writing build/bdist.macosx-10.8-intel/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.11.0-py2.7-macosx-10.8-intel.egg' and adding 'build/bdist.macosx-10.8-intel/egg' to it removing 'build/bdist.macosx-10.8-intel/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. [chipotle:~/tmp/apache-mesos-0.11.0-rc3/mesos-0.11.0] mattmann% Great work Vinod and community! Since the 72 hour window is passed, Vinod you can send the [RESULT] [VOTE] thread, tally the VOTEs, and push the release. 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 ++
Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)
Thanks Brian! Vinod, since Brian is a member of the IPMC, I believe we now have enough VOTEs to send a [RESULT]. 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: Brian McCallister bri...@skife.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, June 1, 2013 5:01 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3) +1 On Tue, May 28, 2013 at 2:24 PM, Vinod Kone vinodk...@gmail.com wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.11.0. This will be the third incubator release for Mesos in Apache . The candidate for Mesos 0.11.0-incubating release is available at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz The tag to be voted on: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbc aa0d348a88188c17a8b06b57306832a7a5885 The MD5 checksum of the tarball can be found at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x2B1D89DA5C6E508C Please vote on releasing this package as Apache Mesos 0.11.0-incubating! The vote is open until Friday, May 31st at 18:30 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.11.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
[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 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 industry partners and collaborators are well aligned with our code base. There are also a number of related Apache projects and dependencies, that will be mentioned in the Relationships with Other Apache products section. == Known Risks == === Orphaned Products === Given the current level of investment in Spark - the risk of the project being abandoned is minimal.
Re: [PROPOSAL] Apache Spark for the Incubator
Guys, I've added: Thomas Dudziak as a mentor to the proposal at his request. He is a member of the ASF and should be granted IPMC access soon. 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, May 31, 2013 11:03 AM To: general@incubator.apache.org 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
Re: YAMP to fix the Incubator (*)
I'm not sure why Yet another proposal is needed. This is already longer than my own, and kind of completely ignores the fact that I already wrote a TL;DR version of this. Bertrand's rationale is that it's hard to track email. Precisely why I wrote my own proposal for this over a year and a half ago. Can someone clearly state in non general terms how this is different than: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 1:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) There is already some really good ideas in this page. Thank you for kicking this off Bertrand. http://wiki.apache.org/incubator/IncubatorIssues2013 On 13 May 2013 15:04, Bertrand Delacretaz bdelacre...@apache.org wrote: (Yet Another Meta Proposal ;-) Dunno if it's just me but I have totally lost track of what the current proposals are, who's supporting which options etc. To try to make sense of all this, I have created http://wiki.apache.org/incubator/IncubatorIssues2013 and suggest that whoever thinks the Incubator needs improvements lists their issues there, as concisely as possible, with suggestions for fixing. People can then comment there (with their names in brackets so we see who says what) - having all that on one page should help. -Bertrand (*) I actually don't think the Incubator is broken BTW...but fleshing out that page should allow us to find out - 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: YAMP to fix the Incubator (*)
hahhahha, done! http://wiki.apache.org/incubator/IncubatorIssues2013#Issue_08_-_The_IPMC_is _broken ++ 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 7:39 AM To: general general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) Feel free to add a IPMC is broken with a solution of destroy it and link to TL:DR proposal as a solution. Sent from a mobile device, please excuse mistakes and brevity On 14 May 2013 18:17, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: I'm not sure why Yet another proposal is needed. This is already longer than my own, and kind of completely ignores the fact that I already wrote a TL;DR version of this. Bertrand's rationale is that it's hard to track email. Precisely why I wrote my own proposal for this over a year and a half ago. Can someone clearly state in non general terms how this is different than: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 1:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) There is already some really good ideas in this page. Thank you for kicking this off Bertrand. http://wiki.apache.org/incubator/IncubatorIssues2013 On 13 May 2013 15:04, Bertrand Delacretaz bdelacre...@apache.org wrote: (Yet Another Meta Proposal ;-) Dunno if it's just me but I have totally lost track of what the current proposals are, who's supporting which options etc. To try to make sense of all this, I have created http://wiki.apache.org/incubator/IncubatorIssues2013 and suggest that whoever thinks the Incubator needs improvements lists their issues there, as concisely as possible, with suggestions for fixing. People can then comment there (with their names in brackets so we see who says what) - having all that on one page should help. -Bertrand (*) I actually don't think the Incubator is broken BTW...but fleshing out that page should allow us to find out - 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: YAMP to fix the Incubator (*)
And you seem to consistently imply that my proposal means destroy it when I've constantly demonstrated that in fact it's a series of steps, that are easily reversible in the traditional Apache way. The documentation moving to the stewardship of ComDev not working out? Move it back. Probationary TLPs not working out? Move them back. Anyways I'm done pointing it out. ++ 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 8:11 AM To: general general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) I've removed the reference to me. It seemed to imply I agree with your position here. I do not. I was merely encouraging you to add your suggestion to the document since you felt it was being ignored. In my opinion the IPMC is not broken. My suggestions for some minor improvements are on the wiki page. Ross Sent from a mobile device, please excuse mistakes and brevity On 14 May 2013 18:44, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: hahhahha, done! http://wiki.apache.org/incubator/IncubatorIssues2013#Issue_08_-_The_IPMC_ is _broken ++ 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 7:39 AM To: general general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) Feel free to add a IPMC is broken with a solution of destroy it and link to TL:DR proposal as a solution. Sent from a mobile device, please excuse mistakes and brevity On 14 May 2013 18:17, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: I'm not sure why Yet another proposal is needed. This is already longer than my own, and kind of completely ignores the fact that I already wrote a TL;DR version of this. Bertrand's rationale is that it's hard to track email. Precisely why I wrote my own proposal for this over a year and a half ago. Can someone clearly state in non general terms how this is different than: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal 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: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 14, 2013 1:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: YAMP to fix the Incubator (*) There is already some really good ideas in this page. Thank you for kicking this off Bertrand. http://wiki.apache.org/incubator/IncubatorIssues2013 On 13 May 2013 15:04, Bertrand Delacretaz bdelacre...@apache.org wrote: (Yet Another Meta Proposal ;-) Dunno if it's just me but I have totally lost track of what the current proposals are, who's supporting which options etc. To try to make sense of all this, I have created http://wiki.apache.org/incubator/IncubatorIssues2013 and suggest that whoever thinks the Incubator needs improvements lists their issues there, as concisely as possible, with suggestions for fixing. People can then comment there (with their names in brackets so we see who says what) - having all that on one page should help. -Bertrand (*) I actually
Re: YAMP to fix the Incubator (*)
Thanks can you please identify how my proposal isn't granular? It suggests next steps about 5 of them and then lists shifts in responsibility around 10 or more of then with applicable next steps. Sent from my iPhone On May 14, 2013, at 2:22 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tuesday, May 14, 2013, Mattmann, Chris A (398J) wrote: hahhahha, done! http://wiki.apache.org/incubator/IncubatorIssues2013#Issue_08_-_The_IPMC_is _broken thanks - although I don't share your views about the brokenness of the Incubator (hence YAMP to have a more granular view on things), having all the suggestions for change in a single place should help build consensus on what we actually want to do. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [META DISCUSS] talking about the overall state of this PMC
Benson, -Original Message- From: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, May 11, 2013 6:44 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [META DISCUSS] talking about the overall state of this PMC [..snip..] One possible path is that, at some point, I as VP pick one. I plan to let this discussion continue for at least a week, if not more, before I remotely consider taking that step. I think it's clear, though, that _this committee_ does not believe in the 'direct-to-PMC' model, so anyone interested in that alternative should talk elsewhere and/or with the board, as per Ant's message. Based on what evidence? # of emails sent in either direction? If you think it's clear in either direction, call a VOTE. I think that's the only demonstrable way to suggest what's clear and what's not. 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 ++ On Sat, May 11, 2013 at 12:25 PM, Alan Cabrera l...@toolazydogs.com wrote: On May 11, 2013, at 7:26 AM, ant elder ant.el...@gmail.com wrote: I also agree that there isn't consensus in the Incubator PMC to do this, but I'm not sure we need it. Lovely. Regards, Alan - 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: [META DISCUSS] talking about the overall state of this PMC
Hi Alan, -Original Message- From: Alan Cabrera l...@toolazydogs.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, May 11, 2013 7:01 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [META DISCUSS] talking about the overall state of this PMC [..snip..] and more weakness in _supervising_ (or at least in documenting supervision). Could tooling help here? Tooling is important, but it doesn't solve the META COMMITTEE issue. Aka there is a ton of people on this umbrella project, and reaching consensus on anything is quite difficult. The ASF doesn't work this way -- there isn't an umbrella project controlling all of the sub projects. The board isn't an umbrella committee. It's not designed that way. They have ultimate authority/power, based on the election of the membership, but they are honestly dead slow to use it -- and for good reason. Such power should not be wielded lightly. Yet, we try in the IPMC to use it constantly. Having VOTEs for this, and that, privately and publicly, for people and/or for releases. It doesn't work. When it does work it's through the effort of Champions that existed well before the name was ever coined. A lot of Champions (Ross, Joe, me, Jukka, Chris D, you=Alan, Ant, Alan G., to name a few) have our own interests in pushing our podlings through that we brought to the ASF -- other Champions are Board members of the ASF, or ASF veterans that simply care about the impact that these new projects will have on the Foundation. But it's really those Champions, and/or those combined mentors who are active that push the podling through *in spite of* the wild west that is the IPMC. This has been documented in numerous threads and numbers things have been undertaken over the past year and a half some of which helped to improve the situation (only 1 IPMC mentor VOTE needed for PPMC addition; Joe's experiment; formal definition of Champion role; etc etc); and other things have been tried that had little to no effect (email threads; proposal wars; bickering, blah blah). We have a few competing proposals for changes to address these, especially supervision weakness. Is the reporting problem the sole issue? No, it's a variety of things centered around the general nature of umbrella projects, which we have the worst kind of in the IPMC. People on the IPMC telling PPMCs and projects how to run their communities? The ASF doesn't stand for that in its regular projects; why teach the podlings that their VOTEs don't count, and that the only people who cast binding release and membership VOTEs are members of some meta committee that have no merit in their project? I wish that I felt confident as Joe does that just electing more people from inside the projects was all we needed to do; maybe Alan's idea combined with that is the way to go. I'm not sure which way to go but I'm really liking the direction of this email. I feel that I'm getting a sense of what you feel are the core problems we're trying to solve. I'd be curious as to the intersection of those problems with the ones I've been pointing out for years. And I did more than point them out. I wrote a proposal that has incremental next steps to take in each way. Recently we had a situation on private where I felt that there was a consensus to be had, but some people needed to be nudged a bit to allow it to emerge. That's not what I see here when considering the choices of using more or less of shepherds, champions, and mentors. I think that a lot of members didn't read it, thinking that there was yet another email storm to ignore. This was the point that I was trying to make in my earlier emails. *It is the constant churning of roles and processes that is exhausting this IPMC, not the actual work.* It is this bureaucratic churning that's sapping the emotional energy if the IPMC members. Why are we churning? Because we are not holding members/mentors up to their commitments. Because we are constantly coming up w/ new ad hoc exceptions for every policy we have. It's way bigger than holding members/mentors up to their commitments. I (and others) are questioning the core of the commitment and it's rationale. We need less process. Less roles. More accountability. More tooling. I totally agree with this -- I've put up an incremental, step-by-step method to achieve all of that. One possible path is that, at some point, I as VP pick one. I plan to let this discussion continue for at least a week, if not more, before I remotely consider taking that step. Ultimately we voted you in to be our VP. I feel that you are listening to our concerns. I'll support what ever your decision is even if I don't agree. I think it's clear, though, that _this committee_ does not believe in the 'direct-to-PMC' model, so anyone interested in that alternative should talk elsewhere and/or with the board, as per Ant's message. What this direct to PMC
Re: [META DISCUSS] talking about the overall state of this PMC
-Original Message-
From: Benson Margulies bimargul...@gmail.com
Reply-To: general@incubator.apache.org general@incubator.apache.org
Date: Saturday, May 11, 2013 8:56 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: Re: [META DISCUSS] talking about the overall state of this PMC
If you think it's clear in either direction, call a VOTE. I think that's
the only demonstrable way to suggest what's clear and what's not.
Please see several emails from Greg and others on the board@ list
recently pointing out the inappropriateness of overuse of votes.
And please see the last 10 years of Apache policy regarding what consensus
means, and what it doesn't.
I'm sick of your sweeping statements -- be direct. You have a problem with
my proposal -- good -- no matter how many go off this list or bugger
off,
or take your proposal elsewhere emails you send, the point is, I've done
the work; have mentored projects, and have done a lot more than simply talk
about what to get done and what not to get done in the past N years
of the Incubator. So yes, I care just as much as you do, and I've done the
work to document my care.
If even *one* person strongly objects, there is no consensus. There is
a strong handful of people who strongly object. So there's no
consensus. This isn't a majority issue.
It doesn't matter if it's a majority or not issue. You made a sweeping
statement:
{quote}
I think it's clear, though, that _this committee_ does not believe in
the 'direct-to-PMC' model, so anyone interested in that alternative
should talk elsewhere and/or with the board, as per Ant's message.
{quote}
How_on_Earth can you get a gauge on what 170+ people believe, or what they
don't?
I suggested calling a VOTE, I wouldn't even know what the binding results
of the VOTE would be -- but at least it's measurable and quantifiable
instead
of declarative which is the language that I see you prefer using.
I don't uniquely own the role of testing consensus. If you want to
send a message that tests consensus on your proposal, or more
accurately tests consensus on the idea of asking the board for
permission to do a trial run of your proposal, go right ahead. I feel
confident that it will attract enough firm -1 votes to demonstrate a
lack of consensus in favor of the idea.
One the one hand you want to make thinly veiled statements about what
power you have as VP; on the other you pull back and claim what roles
you don't own. So, which one is it, Benson?
I for one am also sick of the whoo hah hah, and I've given up that this
committee will decide much of anything. That's not a slight to the
committee,
which contains some of the most well respected (by me and others) members
of
the ASF. It's more a slight to the ridiculous model that the IPMC has
employed,
and the thumbing its nose at the traditional mantras of the ASF that it
ignores
(e.g., the utter uselessness and destruction that umbrella projects, once
arrived
at, create).
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
++
-
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: Would like to be added to Climate incubator group
Thanks Suresh! ++ 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: Suresh Marru sma...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 7, 2013 9:01 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Would like to be added to Climate incubator group On May 6, 2013, at 2:15 PM, Michael Joyce jo...@apache.org wrote: Hello! I just wanted to check up on this. Is there anything I need to do to help get this resolved? Thanks much! On Mon, Apr 29, 2013 at 8:41 PM, Michael Joyce jo...@apache.org wrote: Hello! I'm part of the Open Climate Workbench podling and need to be added to the incubator group for commits. Can you help me out? Hi Michael, If I am understanding your request correctly, you were listed as the Initial Committers when the Climate Proposal [1] was approved and you are wanting to have the right commit bits right? I just added you to incubator unix group, I see you are already added to climate group in asf-authorization-template. Try a commit to climate svn. Cheers, Suresh [1] - http://wiki.apache.org/incubator/ClimateProposal Thanks much - 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: A lot of reports missing these period
Hey Christian, My guess is that since the wiki was down these slipped. I know that I plan on producing reports by end of week and getting them up there ASAP for my podlings. 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: Christian Grobmeier grobme...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 7, 2013 1:42 PM To: general@incubator.apache.org general@incubator.apache.org Subject: A lot of reports missing these period Folks, its reporting time and at the wiki are a lot of them missing! http://wiki.apache.org/incubator/May2013 Ambari Blur DeltaSpike (hasn't it graduated?) Droids Falcon Hadoop Development Tools MRQL Open Climate Workbench Provisionr Tajo Tez Please mentors of these projects catch up with your podlings. Cheers Christian - 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: [META DISCUSS] talking about the overall state of this PMC
I would posit the exact same thing. +1 my friend. This has been my whole point all along. 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: Greg Stein gst...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, May 7, 2013 9:15 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [META DISCUSS] talking about the overall state of this PMC On a whole different direction, one way to scale is to shift from Incubator-managed podlings to Board-managed. The podling would effectively be a TLP on probation. The Champion, Mentors, and Board would be providing oversight. I would posit that the Board is more capable of oversight than the IPMC. The Directors have signed up to spend a lot of time -- more than we expect of most volunteers. Not to mention the Board reviews 50+ reports every month. Another five won't kill the Board :-P Thus, I might suggest that a proposed-podling may want to try the above approach. (I dunno if the Board would agree, but somebody has to formally ask!) Cheers, -g On Tue, May 7, 2013 at 11:55 AM, Upayavira u...@odoko.co.uk wrote: The problem that most podlings I've been involved with, whilst having six mentors, have ended up with just me playing any part. On paper, it looks like these podlings are in a great place, in fact, they only have a single active mentor. What is wanted is to know who is, and who isn't active. To spot problems. Benson's idea is to say that a simple 'I'm here' message would really help the incubator PMC. I'd agree with that. The question is, who's job is it to track all this. Should the PMC go look and do all the leg-work, or should projects and their mentors take some of the load? Really, the more responsibility is centralised, the less the incubator will scale. Looking for ways that mentors can show their involvement is a good thing. I guess that could be automated (grep through mail archives for mentor email addresses each month), but until that happens, I'd say it would be a good thing for mentors/champions to take some of that load off the incubator PMC. It need merely be a reply to a Marvin 'are you there' email. Upayavira On Tue, May 7, 2013, at 04:37 PM, Tim Williams wrote: On Tue, May 7, 2013 at 11:20 AM, Benson Margulies bimargul...@gmail.com wrote: There was a consensus to add the Champion role, and we haven't even tried it seriously, and now you propose to eliminate it. That doesn't seem reasonable to me. I'd rather try to make it useful and then evaluate it. In other words, +1 to Bertrand. 'Holding mentors to their responsibility' as a completely generic concept is an idea that constantly fails to reach a consensus, due to the 'volunteer dilemma'. For others in this thread, I completely disagree that a monthly one line edit to the XML file or a one line email is an unreasonable burden. Fair enough, disagree. Any mentor, let alone champion, for whom that is an unreasonable burden should not have signed up in the first place. That's unfair. I signed up to *mentor* not send silly heartbeat checks that exist because other podling's mentors failed to live up to their responsibility. This feels beyond the minimal governance necessary and a solution to the wrong problem. It'd helpful to say precisely what problem that this heartbeat is intended to solve, in that way, we are afforded the opportunity to propose an alternative solution - for example, by focusing on highlighting the problem mentors/podlings. Thanks, --tim - 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: Time for April 2013 Incubator PMC report
Hey Ben, Since I missed this last month, I've added a report for Mesos based on the below to the May 2013 report, here: http://wiki.apache.org/incubator/May2013 I went ahead and updated your original template report and signed off on it. Thanks for pushing this. IPMC, note this is an out of band report from Mesos to let folks know what's going on with the project. 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Thursday, April 18, 2013 10:12 AM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: Time for April 2013 Incubator PMC report Great job, Ben. We can go ahead and include this in next month's Incubator report since I was underwater the past week and didn't catch this until now. CC'ing general@incubator so they know you did this on time and Mesos PPMC handled its business here. 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Tuesday, April 9, 2013 8:17 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: Re: Time for April 2013 Incubator PMC report Hey Chris, I wrote up a draft report: Mesos Mesos is a cluster manager that provides resource sharing and isolation across cluster applications. Mesos has been incubating since 2010-12-23. Three most important issues to address in the move towards graduation: 1. Improved documentation and support. 2. Grow community (more developers contributing as the end goal). 3. Mentor and add additional commit Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We would like to move to git, and have been waiting for https://issues.apache.org/jira/browse/INFRA-6065, but we've seen no activity on the ticket as of yet. We've also had a hard time getting votes for our releases, as before. How has the community developed since the last report? We've seen an increase in activity on the mailing list. Airbnb has been increasingly using Mesos, not only for Chronos, but also for Hadoop (using our newly written Hadoop framework). There has also been a production engineering meetup where Mesos was presented: http://www.meetup.com/SF-Bay-Area-Large-Scale-Production-Engineering/even t s/97563092/ How has the project developed since the last report? On top of the usual bug fixes and reliability improvements, we've implemented resource monitoring to gain visibility into the resource consumption of executors running in Mesos. We are also much closer to shipping a feature that allows the slave to upgrade gracefully (without killing all tasks underneath it). On Tue, Apr 2, 2013 at 1:06 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Mesos Peeps, Time for an IPMC report for April 2013: http://wiki.apache.org/incubator/April2013 Anyone want to take a crack at it before I review and/or update and sign off? 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 ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [META DISCUSS] talking about the overall state of this PMC
Hey Guys, Sorry but what are we discussing that's different from formalizing the role of the Champion, this thread originally started by Bertrand, and seconded by me and numerous others [1]? Cheers, Chris [1] http://s.apache.org/U6w ++ 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: Upayavira u...@odoko.co.uk Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Sunday, May 5, 2013 10:43 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [META DISCUSS] talking about the overall state of this PMC Having read your wiki post, I find it a simple, considered upping of the game, which I think would be worth the effort of trying, especially as the mini-reports don't get to the board unless there are issues. There really could do with being a little more 'cost' to being a podling, or a mentor for that matter, and this proposal moves gently in that direction. If folks approve, we'll need to seek champions for all existing podlings, and decide what to do about those for which we cannot identify one. Upayavira On Mon, May 6, 2013, at 02:56 AM, Benson Margulies wrote: Discussions on Ross' and Chris' proposals ground to a halt. In my view, there are real issues that drove those discussions, even if those discussions drove some of us to distraction. A bit before the wiki crashed, I wrote: http://wiki.apache.org/incubator/BensonApril2013ProcessProposals The TL;DR version of this is: 1: let's take Champions seriously as a role 2: let's ask for a minimal heartbeat from every podling every month As the person responsible for filing the report, it seems to me that I could, with some justification, ask the Champions and mentors to please comply with these ideas, with the goal of having a more accurate picture to present. However, I'd rather seek a consensus for these, or something like them, as a formal procedure. Note that I labelled this thread [META DISCUSS]. I invite people with views on these ideas to start a thread or threads as appropriate. I would ask people, as a favor to me and others, not to use these ideas as a launchpad 'let's radically restructure instead.' These will reach a consensus or not, and other proposals will reach a consensus or not, but I submit that it is easier on us all to deal with them one-at-a-time. --benson - 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: [Incubator Wiki] Update of HotdoGProposal by H. Joe Lee
Benson, HDF Group is a growing research industry originally seeded by NASA investments and now privately funded. HDF is the de facto scientific data file format for NASA, NOAA and other remote sensing missions. There are huge communities of people that use this software. The HDF group would like to use this opportunity to experiment with the Apache Incubator model after lots of prodding by people like me to get more scientific projects into Apache and to steward them here. While this project may be specific it has the opportunity to grow into a host of other downstream, very useful tools and capabilities, and furthermore, HDF Group has a ton of other software that could be potentially stewarded at the ASF, provided this experiment is useful. Hope that clarifies. 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: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, April 29, 2013 4:29 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [Incubator Wiki] Update of HotdoGProposal by H. Joe Lee I have some qualms about this as a stand-alone project. It's a conversion tool between two defined formats. You will build it, it will get done, and then what? What will keep a community engaged? If would make more sense to imaging some project that was in the business of building and maintaining a suite of related tools, where new things could be expected to come up. On Mon, Apr 29, 2013 at 6:52 PM, Apache Wiki wikidi...@apache.org wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Incubator Wiki for change notification. The HotdoGProposal page has been changed by H. Joe Lee: http://wiki.apache.org/incubator/HotdoGProposal?action=diffrev1=9rev2=1 0 = Background = = Rationale = - The HEG tool is limited to some NASA HDF-EOS2 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 with correct coordinate system. + The HEG tool is limited to some NASA HDF-EOS2 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 with correct coordinate system. = Initial Goals = + + We'll improve GDAL to support NASA HDF products better by handling geo-location information correctly and automatically. + = Current Status = + + We're looking for developers and sponsors. + == Meritocracy == == Community == + + GIS and Earth Science + == Core developers == * H. Joe Lee hyoklee AT hdfgroup DOT org @@ -42, +51 @@ * http://wiki.apache.org/HotdoG = Initial Committers = + = Affiliations = * H. Joe Lee (The HDF Group) @@ -51, +61 @@ * Mike Folk - The HDF Group = Sponsors = + == Champion == * Paul Ramirez paul DOT m DOT ramirez AT jpl DOT nasa DOT gov - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Time for April 2013 Incubator PMC report
Great job, Ben. We can go ahead and include this in next month's Incubator report since I was underwater the past week and didn't catch this until now. CC'ing general@incubator so they know you did this on time and Mesos PPMC handled its business here. 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: Benjamin Mahler benjamin.mah...@gmail.com Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Tuesday, April 9, 2013 8:17 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: Re: Time for April 2013 Incubator PMC report Hey Chris, I wrote up a draft report: Mesos Mesos is a cluster manager that provides resource sharing and isolation across cluster applications. Mesos has been incubating since 2010-12-23. Three most important issues to address in the move towards graduation: 1. Improved documentation and support. 2. Grow community (more developers contributing as the end goal). 3. Mentor and add additional commit Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We would like to move to git, and have been waiting for https://issues.apache.org/jira/browse/INFRA-6065, but we've seen no activity on the ticket as of yet. We've also had a hard time getting votes for our releases, as before. How has the community developed since the last report? We've seen an increase in activity on the mailing list. Airbnb has been increasingly using Mesos, not only for Chronos, but also for Hadoop (using our newly written Hadoop framework). There has also been a production engineering meetup where Mesos was presented: http://www.meetup.com/SF-Bay-Area-Large-Scale-Production-Engineering/event s/97563092/ How has the project developed since the last report? On top of the usual bug fixes and reliability improvements, we've implemented resource monitoring to gain visibility into the resource consumption of executors running in Mesos. We are also much closer to shipping a feature that allows the slave to upgrade gracefully (without killing all tasks underneath it). On Tue, Apr 2, 2013 at 1:06 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Mesos Peeps, Time for an IPMC report for April 2013: http://wiki.apache.org/incubator/April2013 Anyone want to take a crack at it before I review and/or update and sign off? 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 ++ - 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.11.0-incubating (RC1)
Hi Folks, Any other IPMC members have some time to review this RC? The Mesos PPMC would appreciate a review and has 1 binding VOTE atm from me. Thank you! 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Thursday, April 4, 2013 8:07 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org, general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1) Dear Ben, +1 from me (binding): SIGS check out: [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Thu Mar 7 14:41:36 2013 PST using RSA key ID F6FB762C gpg: Good signature from Benjamin Hindman b...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4BF2 061E 7300 3185 CA06 E30F F99D 6AD0 F6FB 762C [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% Checksums check out: [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.11.0-incubating.tar.gz: OK [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% More below: -Original Message- From: Benjamin Hindman b...@berkeley.edu Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Thursday, March 7, 2013 3:52 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1) Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the third incubator release for Mesos in Apache . The candidate for Mesos 0.11.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos /tags/release-0.11.0-incubating-RC1 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.11.0-incubating! The vote is open until Sunday, March 10th at 5:00 pm PST and passes if a majority of at least 3 +1 IPMC votes are cast. One thing I would recommend here -- just a suggestion. State that you are leaving the VOTE open for at least 72 hours. That way you can continue the VOTE open whilst garnering attention from potential reviewers. When you have the required VOTEs, then can wrap it up if it's post that. Just gives you time whilst reviewing and RC'ing. [X] +1 Release this package as Apache Mesos 0.11.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. 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 ++ - 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.11.0-incubating (RC1)
Okey dok, we will work to address those issues in RC #2. Thank you Luciano! 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: Luciano Resende luckbr1...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, April 15, 2013 6:51 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1) On Mon, Apr 15, 2013 at 3:07 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, Any other IPMC members have some time to review this RC? The Mesos PPMC would appreciate a review and has 1 binding VOTE atm from me. Thank you! -1 Extracted release is missing Incubator DISCLAIMER http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer Looks like the LICENSE information got attached to the NOTICE file, instead of LICENSE. Please update the LICENSE file accordingly and then clean up the NOTICE with required attributions. http://incubator.apache.org/guides/releasemanagement.html#note-license-and -notice The following might also be helpful http://www.apache.org/dev/release.html#license -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: April report filed
Hey Benson et al., Sorry I will get the Climate report on the wiki in the next few hours. If possible, I would like it to be included in this month's report. Sorry about it being late. 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: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, April 12, 2013 3:59 AM To: general@incubator.apache.org general@incubator.apache.org Subject: April report filed I committed the April report. Since no one added any releases to this report, there are no releases listed. I removed the mention of Onami as graduating since there is no motion to establish an Onami PMC on the agenda. If someone adds one please add it to the Incubator repot header. There is no report for Open Climate Workshop; there might be other missing reports. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: April report filed
Hey Folks, I've went ahead and filed the CLIMATE report. http://wiki.apache.org/incubator/April2013 CLIMATE mentors; please scope it out and sign off. Benson if possible, I would appreciate your consideration in including the report in the overall Incubator report. Sorry for the tardiness. 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: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, April 12, 2013 6:27 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: April report filed Hey Benson et al., Sorry I will get the Climate report on the wiki in the next few hours. If possible, I would like it to be included in this month's report. Sorry about it being late. 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: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, April 12, 2013 3:59 AM To: general@incubator.apache.org general@incubator.apache.org Subject: April report filed I committed the April report. Since no one added any releases to this report, there are no releases listed. I removed the mention of Onami as graduating since there is no motion to establish an Onami PMC on the agenda. If someone adds one please add it to the Incubator repot header. There is no report for Open Climate Workshop; there might be other missing reports. - 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: April report filed
No problem you got it! Just didn't want to step on anyone's toes. Adding now! 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: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, April 12, 2013 8:46 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: April report filed In case that sounded harsh, which was not intended: I have a meeting in 15 minutes that i Need to prepare for, and then I'm off to go home, collect my entourage, and go to the airport to fly to Portland. So I'd be _grateful_ if you'd commit it yourself. On Fri, Apr 12, 2013 at 11:44 AM, Benson Margulies bimargul...@gmail.comwrote: Chris, You have access to commit to the board agenda, so why don't you just put it there yourself? --benson On Fri, Apr 12, 2013 at 9:27 AM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hey Benson et al., Sorry I will get the Climate report on the wiki in the next few hours. If possible, I would like it to be included in this month's report. Sorry about it being late. 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: Benson Margulies bimargul...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, April 12, 2013 3:59 AM To: general@incubator.apache.org general@incubator.apache.org Subject: April report filed I committed the April report. Since no one added any releases to this report, there are no releases listed. I removed the mention of Onami as graduating since there is no motion to establish an Onami PMC on the agenda. If someone adds one please add it to the Incubator repot header. There is no report for Open Climate Workshop; there might be other missing reports. - 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: Incubator structure (was Re: Vote on personal matters: majority vote vs consensus)
Hey Ross, -Original Message- From: Ross Gardler rgard...@opendirective.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, April 4, 2013 6:22 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: Incubator structure (was Re: Vote on personal matters: majority vote vs consensus) On 4 April 2013 09:06, Greg Stein gst...@gmail.com wrote: On Sun, Mar 31, 2013 at 8:20 PM, Ross Gardler rgard...@opendirective.com wrote: On 31 March 2013 17:08, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Why is it so hard to see that the board is already watching those 22 nascent projects in the same manner they watch the 137 TLPs? Because they are not watching with the same manner. They are delegating a huge range of tasks such as IP oversight and mentoring to the IPMC. I believe this is simply a matter of training and mentor oversight. That is the key issue. I can name many really good mentors. The problem is that prior to the new processes introduced by Jukka we had a great many projects that stagnated because of inattentive mentoring. The current IPMC reporting process picks those up and addresses them internally within the IPMC. This is the reason that we have seen more podlings graduate in the last year. I see it a teeny bit differently (though later emails from you and Greg seem to have brought our ideas into alignment). You directly equate Jukka's processes with graduating so many podlings. While I think Jukka's processes were great, they were a means to an ends -- they along with some key IPMC members who are active (you will see later that you are in that short list of active ones ^_^) are the reasons more podlings graduated. Coupled with Joe's experiment, and coupled with the removal of the IPMC 3 +1s for releases which both came before Jukka's time. Another key was the clarification of the role of Champion and Champions really stepping up. Note that those burdens being removed are precisely the initial steps towards the removal of the meta committee that is the IPMC since both steps in effect reduced the power of the umbrella to stall and stagnate podlings. I went back, starting in March 2012 [1] when Jukka took over to cull a list of shepherds and active mentors that signed off on at least 1 report for the IPMC (before there were shepherds). Here is the list and tallies for each month that the mentors signed off on at least 1 report. Note in tallies below I count the mentor or shepherd Nx per month so if they signed N multiple reports, they still get a count of N. I went ahead and uploaded these scripts to [2] in case folks are interested in how I tallied (note I also removed some nonsense from these files by hand mainly stop words since I didn't do a ton of data cleansing): Mentors [ tallies per month since March 2012] --- 18 rgardler 18 bdelacretaz 16 mattmann 15 phunt 15 kevan 13 tomwhite 9 jukka 9 jim 7 greddin 7 cdouglas 7 adc 7 Alan 6 joes 6 bodewig 6 ate 5 wave 5 tommaso 5 omalley 5 olamy 5 elecharny 4 simonetripodi 4 lresende 4 hwright 4 gstein 4 gianugo 4 Gates 3 struberg 3 nick 3 mnour 3 jbonofre 3 coheigea 3 Struberg 3 Petracek 3 Mark 3 Gerhard 3 Cabrera 2 wavw 2 twilliams 2 rfrovarp 2 marrs 2 ddas 2 cutting 2 berndf 2 ant 2 Ralph 2 Olivier 2 Lamy 2 Goers 2 Devaraj 2 Das 2 (struberg) 2 (rgoers) 2 (gates) 1 yegor 1 wrowe 1 thorsten 1 rfeng 1 mfranklin 1 line 1 jvermillard 1 grobmeier 1 generic 1 dkulp 1 dennisl 1 dashorst 1 brett 1 bmargulies 1 asavory 1 Williams 1 Upayavira 1 Tim 1 Reddin 1 Martijn 1 Lundberg 1 Greg 1 Fisher 1 Dennis 1 Dave 1 Dashorst 1 (wave) 1 (greddin) 1 (gates@) If we cut off the above at 3 sign offs or more, we see that there are 31 mentors that fit that criteria. If we say at least 6 sign offs on reports in the last year (averaging less than 1 sign off every 2 months) then that number drops to 15. The point being that whatever number we pick any of those 15-31 (or whatever N) mentors could simply be considered candidates for these new VPs for incoming projects without an Incubator whilst the incoming projects are learning the Apache way from their 3 ASF members and others in the community. In fact, this is really what the role of the Champion is now. Sort of a provisional podling VP until the incoming project community VP (aka real VP) is elected. If we remove that aspect of the IPMCs oversight then who will catch these projects that don't have mentors actively looking after them? It will be the boards responsibility to do that. I contest that this does not scale. We need a solution that will scale appropriately whilst also removing the inefficiencies introduced by a large IPMC. Ross says the Board pays less attention to these (by implication) than
Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1)
Dear Ben, +1 from me (binding): SIGS check out: [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.11.0-incubating.tar.gz.asc gpg: Signature made Thu Mar 7 14:41:36 2013 PST using RSA key ID F6FB762C gpg: Good signature from Benjamin Hindman b...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4BF2 061E 7300 3185 CA06 E30F F99D 6AD0 F6FB 762C [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% Checksums check out: [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% $HOME/bin/verify_md5_checksums md5sum: stat '*.bz2': No such file or directory md5sum: stat '*.zip': No such file or directory mesos-0.11.0-incubating.tar.gz: OK [terra:~/tmp/apache-mesos-0.11.0-incubating] mattmann% More below: -Original Message- From: Benjamin Hindman b...@berkeley.edu Reply-To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Date: Thursday, March 7, 2013 3:52 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos mesos-...@incubator.apache.org Subject: [VOTE] Release Apache Mesos 0.11.0-incubating (RC1) Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the third incubator release for Mesos in Apache . The candidate for Mesos 0.11.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos /tags/release-0.11.0-incubating-RC1 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.11.0-incubating-RC1/mesos -0.11.0-incubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.11.0-incubating! The vote is open until Sunday, March 10th at 5:00 pm PST and passes if a majority of at least 3 +1 IPMC votes are cast. One thing I would recommend here -- just a suggestion. State that you are leaving the VOTE open for at least 72 hours. That way you can continue the VOTE open whilst garnering attention from potential reviewers. When you have the required VOTEs, then can wrap it up if it's post that. Just gives you time whilst reviewing and RC'ing. [X] +1 Release this package as Apache Mesos 0.11.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. 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 ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
