Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive
And my axe! Erm... I mean, my +1. On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote: FYI. Alan. Begin forwarded message: From: Alan Gates ga...@hortonworks.com Date: February 4, 2013 10:18:09 PM PST To: hcatalog-...@incubator.apache.org Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive The Hive PMC has voted to accept HCatalog as a submodule of Hive. You can see the vote thread at http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e . We now need to vote to graduate from the incubator and become a submodule of Hive. This entails the following: 1) the establishment of an HCatalog submodule in the Apache Hive Project; 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule; and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Definitions for all these can be found in the (now adopted) Hive bylaws at https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer. This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13). PPMC members votes are binding in this vote, though input from all is welcome. If this vote passes the next step will be to submit the graduation motion to the Incubator PMC. Here's my +1. Alan. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Apache Open Climate Workbench into the Incubator
Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the RCMES project since 2009 funded initially by the American Recovery and Reinvestment Act (ARRA) project out at NASA, and then branching out into other sources of support and sustainability (NASA; NSF, etc. -- see the
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 (binding) -Andrew On 2/5/13 8:18 AM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the RCMES project since 2009 funded initially by the American Recovery and Reinvestment Act (ARRA) project out at NASA, and then branching out into other sources of
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
On 02/05/2013 05:18 PM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... +1 (non-binding) Good luck! Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the RCMES project since 2009 funded initially by the American
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 binding --Paul On Feb 5, 2013, at 8:30 AM, Andrew Hart ah...@apache.org wrote: +1 (binding) -Andrew On 2/5/13 8:18 AM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 (non-binding) On 05/02/13 16:18, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the RCMES project since 2009 funded initially by the American Recovery and Reinvestment Act (ARRA) project out at NASA, and then branching out into other sources of support and
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 (binding) Sent from a mobile device, please excuse mistakes and brevity On 5 Feb 2013 16:18, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the
Re: [VOTE] Graduate Apache Crunch Podling from the Incubator
+1 Doug On Mon, Feb 4, 2013 at 11:41 AM, Josh Wills jwi...@apache.org wrote: This is a call to graduate the Apache Crunch podling from Apache Incubator. Apache Crunch entered the Incubator in May of 2012. We have made significant progress with the project since moving over to Apache. We have ten committers listed on our status page at [1] including three accepted after the podling was formed, and we have verified that Apache Crunch is a suitable name. [2] We completed two releases (Apache Crunch 0.3.0-incubating and Apache Crunch 0.4.0-incubating) and are currently preparing for a third. The community of Apache Crunch is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. The Apache Crunch community voted overwhelmingly to graduate [3], collecting three binding votes from our mentors and IPMC members Arun Murthy, Tom White, and Patrick Hunt. You can view the discussion at [4] and [5]. Our charter is below and on our wiki. [6] Please cast your votes: [ ] +1 Graduate Apache Crunch from Apache Incubator [ ] +0 Indifferent to graduation status of Apache Crunch [ ] -1 Reject graduation of Apache Crunch from Apache Incubator because... We'll run the vote for at least 72 hours (closing at the earliest at 8PM GMT on February 7th.) [1] http://incubator.apache.org/projects/crunch.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-18 [3] http://markmail.org/message/7mplf2wyzqhs2gts [4] http://markmail.org/message/3zu5wszwpaqegxic [5] http://markmail.org/message/wbz43fpnta7r2w4e [6] https://cwiki.apache.org/confluence/display/CRUNCH/Graduation+Resolution X. Establish the Apache Crunch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the development of Java libraries for writing, testing, and running MapReduce pipelines. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Crunch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Crunch Project be and hereby is responsible for the creation and maintenance of software related to development of Java libraries for writing, testing, and running MapReduce pipelines; and be it further RESOLVED, that the office of Vice President, Apache Crunch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Crunch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Crunch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Crunch Project: * Brock Noland br...@apache.org * Christian Tzolov tzo...@apache.org * Gabriel Reid gr...@apache.org * Josh Wills jwi...@apache.org * Kiyan Ahmadizadeh ki...@apache.org * Matthias Friedrich m...@apache.org * Rahul Sharma rsha...@apache.org * Robert Chu robert...@apache.org * Tom White tomwh...@apache.org * Vinod Kumar Vavilapalli vino...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Josh Wills be appointed to the office of Vice President, Apache Crunch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Crunch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Crunch Project; and be it further RESOLVED, that the Apache Crunch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Crunch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Crunch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 (binding) On Tue, Feb 5, 2013 at 8:24 AM, Andrew Hart ah...@apache.org wrote: +1 (binding) -Andrew On 2/5/13 8:18 AM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|**Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/**what-we-do/assessment|U.Shttp://www.globalchange.gov/what-we-do/assessment%7CU.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/**|Northhttp://www.narccap.ucar.edu/%7CNorthAmerican Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.**jussieu.fr/|Coordinatedhttp://wcrp-cordex.ipsl.jussieu.fr/%7CCoordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Feb 5, 2013 at 9:59 PM, Ted Dunning ted.dunn...@gmail.com wrote: +1 (binding) On Tue, Feb 5, 2013 at 8:24 AM, Andrew Hart ah...@apache.org wrote: +1 (binding) -Andrew On 2/5/13 8:18 AM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|**Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/**what-we-do/assessment|U.S http://www.globalchange.gov/what-we-do/assessment%7CU.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/**|North http://www.narccap.ucar.edu/%7CNorthAmerican Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.**jussieu.fr/|Coordinated http://wcrp-cordex.ipsl.jussieu.fr/%7CCoordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to
Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive
+1, non-binding - Alex On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote: And my axe! Erm... I mean, my +1. On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote: FYI. Alan. Begin forwarded message: From: Alan Gates ga...@hortonworks.com Date: February 4, 2013 10:18:09 PM PST To: hcatalog-...@incubator.apache.org Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive The Hive PMC has voted to accept HCatalog as a submodule of Hive. You can see the vote thread at http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e . We now need to vote to graduate from the incubator and become a submodule of Hive. This entails the following: 1) the establishment of an HCatalog submodule in the Apache Hive Project; 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule; and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Definitions for all these can be found in the (now adopted) Hive bylaws at https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer. This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13). PPMC members votes are binding in this vote, though input from all is welcome. If this vote passes the next step will be to submit the graduation motion to the Incubator PMC. Here's my +1. Alan. -- Alexander Alten-Lorenz http://mapredit.blogspot.com German Hadoop LinkedIn Group: http://goo.gl/N8pCF - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Release Apache Onami-Logging 3.4.0-incubating
+1 for the workload :) 2013/2/4 Simone Tripodi simonetrip...@apache.org Hi all, More than 72 hours have passed and the current vote thread can be considered concluded and passes with the following resolution: three +1 binding votes from the following IPMCs: * Olivier Lamy * Christian Grobmeier * Mohammad Nour El-Din no other votes have been casted. I am going to promote released artifacts and make the announce as soon as they will be available. Thanks a lot everybody who took part to the review process! All the best, have a nice day, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Jan 23, 2013 at 2:48 PM, Simone Tripodi simonetrip...@apache.org wrote: Good morning IPMC, The Apache Onami community has voted[1] the release of Apache Onami-Logging 3.4.0-incubating, collecting two IPMC votes from members Olivier Lamy and Christian Grobmeier. This is the changelist: Bug [ONAMI-28] - Do not use code from com.google.inject.internal Dependency upgrade [ONAMI-61] - Update SLF4J to v1.7.2 New Feature [ONAMI-1] - Add the Apache Log4j 2 integration module Task [ONAMI-7] - Import Logging donated codebase to ASF SVN [ONAMI-16] - Update Logging docs [ONAMI-26] - Make all artifactId OSGi name compliant [ONAMI-31] - Update parent pom reference to released 1-incubating version SVN source tag https://svn.apache.org/repos/asf/incubator/onami/tags/org.apache.onami.logging.parent-3.4.0-incubating/ Staging repo: https://repository.apache.org/content/repositories/orgapacheonami-150/ Vote will be open for at least 72 hours and closes approximatively on 26th Jan 2013, at 1:40pm. [ ] +1, let's get it rmblee!!! [ ] +/-0, fine, but consider to fix few issues before... [ ] -1, nope, because... (and please explain why) So IPMCs please cast your votes! [1] http://markmail.org/message/pe5lzynixtpk2er5 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ -- Viele Grüße/Best Regards Daniel Manzke
Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive
+1 Binding. On Tue, Feb 5, 2013 at 1:24 AM, Alexander Alten-Lorenz wget.n...@gmail.comwrote: +1, non-binding - Alex On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote: And my axe! Erm... I mean, my +1. On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote: FYI. Alan. Begin forwarded message: From: Alan Gates ga...@hortonworks.com Date: February 4, 2013 10:18:09 PM PST To: hcatalog-...@incubator.apache.org Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive The Hive PMC has voted to accept HCatalog as a submodule of Hive. You can see the vote thread at http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e. We now need to vote to graduate from the incubator and become a submodule of Hive. This entails the following: 1) the establishment of an HCatalog submodule in the Apache Hive Project; 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule; and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Definitions for all these can be found in the (now adopted) Hive bylaws at https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer . This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13). PPMC members votes are binding in this vote, though input from all is welcome. If this vote passes the next step will be to submit the graduation motion to the Incubator PMC. Here's my +1. Alan. -- Alexander Alten-Lorenz http://mapredit.blogspot.com German Hadoop LinkedIn Group: http://goo.gl/N8pCF - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive
+1 (binding) On Tue, Feb 5, 2013 at 1:26 PM, Jakob Homan jgho...@gmail.com wrote: +1 Binding. On Tue, Feb 5, 2013 at 1:24 AM, Alexander Alten-Lorenz wget.n...@gmail.comwrote: +1, non-binding - Alex On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote: And my axe! Erm... I mean, my +1. On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote: FYI. Alan. Begin forwarded message: From: Alan Gates ga...@hortonworks.com Date: February 4, 2013 10:18:09 PM PST To: hcatalog-...@incubator.apache.org Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive The Hive PMC has voted to accept HCatalog as a submodule of Hive. You can see the vote thread at http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e. We now need to vote to graduate from the incubator and become a submodule of Hive. This entails the following: 1) the establishment of an HCatalog submodule in the Apache Hive Project; 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule; and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Definitions for all these can be found in the (now adopted) Hive bylaws at https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer . This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13). PPMC members votes are binding in this vote, though input from all is welcome. If this vote passes the next step will be to submit the graduation motion to the Incubator PMC. Here's my +1. Alan. -- Alexander Alten-Lorenz http://mapredit.blogspot.com German Hadoop LinkedIn Group: http://goo.gl/N8pCF - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive
+1 binding On Tue, Feb 5, 2013 at 11:28 PM, Owen O'Malley omal...@apache.org wrote: +1 (binding) On Tue, Feb 5, 2013 at 1:26 PM, Jakob Homan jgho...@gmail.com wrote: +1 Binding. On Tue, Feb 5, 2013 at 1:24 AM, Alexander Alten-Lorenz wget.n...@gmail.comwrote: +1, non-binding - Alex On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote: And my axe! Erm... I mean, my +1. On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote: FYI. Alan. Begin forwarded message: From: Alan Gates ga...@hortonworks.com Date: February 4, 2013 10:18:09 PM PST To: hcatalog-...@incubator.apache.org Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive The Hive PMC has voted to accept HCatalog as a submodule of Hive. You can see the vote thread at http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e . We now need to vote to graduate from the incubator and become a submodule of Hive. This entails the following: 1) the establishment of an HCatalog submodule in the Apache Hive Project; 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule; and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Definitions for all these can be found in the (now adopted) Hive bylaws at https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer . This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13). PPMC members votes are binding in this vote, though input from all is welcome. If this vote passes the next step will be to submit the graduation motion to the Incubator PMC. Here's my +1. Alan. -- Alexander Alten-Lorenz http://mapredit.blogspot.com German Hadoop LinkedIn Group: http://goo.gl/N8pCF - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, -- Alex
Re: [VOTE] Graduate Apache Crunch Podling from the Incubator
+1 Best of luck Captains On Feb 4, 2013, at 11:41 AM, Josh Wills wrote: This is a call to graduate the Apache Crunch podling from Apache Incubator. Apache Crunch entered the Incubator in May of 2012. We have made significant progress with the project since moving over to Apache. We have ten committers listed on our status page at [1] including three accepted after the podling was formed, and we have verified that Apache Crunch is a suitable name. [2] We completed two releases (Apache Crunch 0.3.0-incubating and Apache Crunch 0.4.0-incubating) and are currently preparing for a third. The community of Apache Crunch is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. The Apache Crunch community voted overwhelmingly to graduate [3], collecting three binding votes from our mentors and IPMC members Arun Murthy, Tom White, and Patrick Hunt. You can view the discussion at [4] and [5]. Our charter is below and on our wiki. [6] Please cast your votes: [ ] +1 Graduate Apache Crunch from Apache Incubator [ ] +0 Indifferent to graduation status of Apache Crunch [ ] -1 Reject graduation of Apache Crunch from Apache Incubator because... We'll run the vote for at least 72 hours (closing at the earliest at 8PM GMT on February 7th.) [1] http://incubator.apache.org/projects/crunch.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-18 [3] http://markmail.org/message/7mplf2wyzqhs2gts [4] http://markmail.org/message/3zu5wszwpaqegxic [5] http://markmail.org/message/wbz43fpnta7r2w4e [6] https://cwiki.apache.org/confluence/display/CRUNCH/Graduation+Resolution X. Establish the Apache Crunch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the development of Java libraries for writing, testing, and running MapReduce pipelines. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Crunch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Crunch Project be and hereby is responsible for the creation and maintenance of software related to development of Java libraries for writing, testing, and running MapReduce pipelines; and be it further RESOLVED, that the office of Vice President, Apache Crunch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Crunch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Crunch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Crunch Project: * Brock Noland br...@apache.org * Christian Tzolov tzo...@apache.org * Gabriel Reid gr...@apache.org * Josh Wills jwi...@apache.org * Kiyan Ahmadizadeh ki...@apache.org * Matthias Friedrich m...@apache.org * Rahul Sharma rsha...@apache.org * Robert Chu robert...@apache.org * Tom White tomwh...@apache.org * Vinod Kumar Vavilapalli vino...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Josh Wills be appointed to the office of Vice President, Apache Crunch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Crunch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Crunch Project; and be it further RESOLVED, that the Apache Crunch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Crunch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Crunch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 (binding) On Feb 5, 2013, at 8:18 AM, Mattmann, Chris A (388J) wrote: Hi Folks, OK, now that discussion has settled down, I'd like to call a VOTE for acceptance of Apache Open Climate Workbench into the Incubator. I'll leave the VOTE open the rest of the week and close it out next Monday, February 11th early am PT. [ ] +1 Accept Apache Open Climate Workbench into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator because... Full proposal is pasted at the bottom of this email. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thank you! Cheers, Chris P.S. Here's my +1 (binding) - = Apache Open Climate Workbench, tool for scalable comparison of remote sensing observations to climate model outputs, regionally and globally. = === Abstract === The Apache Open Climate Workbench proposal desires to contribute an existing community of software related to the analysis and evaluation of climate models, and related to the use of remote sensing data in that process. Specifically, we will bring a fundamental software toolkit for analysis and evaluation of climate model output against remote sensing data. The toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model Evaluation System (RCMES)]]. RCMES provides two fundamental components for the easy, intuitive comparison of climate model output against remote sensing data. The first component called RCMED (for Regional Climate Model Evaluation Database) is a scalable cloud database that decimates remote sensing data and renalysis data related to climate using Apache OODT extractors, Apache Tika, etc. These transformations make traditionally heterogeneous upstream remote sensing data and climate model output homogeneous and unify them into a data point model of the form (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) and Longitude (lng) are in WGS84 format, but can be reformatted on the fly. time is in ISO 8601 format, a string sortable format independent of underlying store. value carries with it units, related to interpretation and height allows for different values for different atmospheric vertical levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop and Apache Hive, along with hooks to PostGIS and MySQL (traditional relational databases). The second component of the system, RCMET (for Regional Climate Model Evaluation Toolkit) provides facilities for connecting to RCMED, dynamically obtaining remote sensing data for a space/time region of interest, grabbing associated model output (that the user brings, or from the Earth System Grid Federation) of the same form, and then regridding the remote sensing data to be on the model output grid, or the model output to be on the remote sensing data grid. The regridded data spatially is then temporally regridded using techniques including seasonal cycle compositing (e.g., all summer months, all Januaries, etc.), or by daily, monthly, etc. The uniform model output and remote sensing data are then analyzed using pluggable metrics, e.g., Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE), Bias, and other (possibly user-defined) techniques, computing an analyzed comparison or evaluation. This evaluation is then visualized by plugging in to the NCAR NCL library for producing static plots (histograms, time series, etc.) We also have performed a great deal of work in packaging RCMES to make the system easy to deploy. We have working Virtual Machines (VMWare VMX and Virtual Box OVA compatible formats) and we also have an installer built on Python Buildout (http://buildout.org/) called Easy RCMET for dynamically constructing the RCMET toolkit. RCMES is currently supporting a number of recognized climate projects of (inter-)national significance. In particular, RCMES is supporting the [[http://www.globalchange.gov/what-we-do/assessment|U.S. National Climate Assessment (NCA) activities]] on behalf of NASA's contribution to the NCA; is working with the [[http://www.narccap.ucar.edu/|North American Regional Climate Change Assessment Program (NARCCAP)]]; and is also working with the International [[http://wcrp-cordex.ipsl.jussieu.fr/|Coordinated Regional Downscaling Experiment (CORDEX)]]. === Proposal === We propose to transition the RCMES software community, which includes developers of the RCMET and RCMED software, along with users of RCMES in the CORDEX project across a variety of academic institutions, scientists helping to improve the RCMES metrics, and visualizations, and regridding algorithms, packagers making RCMES easier to install, and scientists helping to lead some of these international projects that are already using RCMES. We have been working on the RCMES project since 2009 funded initially by the American Recovery and
[jira] [Created] (PODLINGNAMESEARCH-21) Establish whether Apache Helix is a suitable name
kishore gopalakrishna created PODLINGNAMESEARCH-21: -- Summary: Establish whether Apache Helix is a suitable name Key: PODLINGNAMESEARCH-21 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-21 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: kishore gopalakrishna A suitable name search is required for Apache Helix to graduate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
