Re: Incubator voting status page
Branko Čibej wrote on Mon, Jan 28, 2013 at 08:22:42 +0100: > On 27.01.2013 16:17, Daniel Shahaf wrote: > > Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100: > >> On 26.01.2013 14:27, Benson Margulies wrote: > >>> Brane, are you currently using the pickled clutch metadata? If we just > >>> need to add a field to it we can. > >> Nope, I'm currently walking the incubator archive tree. The clutch > >> metadata is in general good enough, since if clutch can generate > >> target/current.ent, I can certainly get the information I need from > >> that. The only question is the conversion from > >> l...@podling.incubator.apache.org (which clutch knows about) to > >> archive/podling.apache.org/list (which is where the podling mail > >> archives will be in future) is consistent. > >> > > Yes, it is, for all *@p.i.a.o lists. > > Well, I've found an inconsistency while changing the scripts to parse > the content/podlings.xml and content/projects/.xml. > Onami's dev list is the old-style: > > onami-...@incubator.apache.org > > but its archive is new-style: > > onami.incubator.apache.org/dev > > I don't want to special-case the script for this; can we make the > archive consistent with the mailing list address? > They seem consistent with the other "new-style" podlings: minotaur,9:~apmail/public-arch% find . -maxdepth 2 -name \*onami\* ./onami.apache.org minotaur,9:~apmail/public-arch% grep -h List-Id onami.apache.org/*/* | uniq List-Id: List-Id: List-Id: Daniel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator voting status page
On 27.01.2013 16:17, Daniel Shahaf wrote: > Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100: >> On 26.01.2013 14:27, Benson Margulies wrote: >>> Brane, are you currently using the pickled clutch metadata? If we just >>> need to add a field to it we can. >> Nope, I'm currently walking the incubator archive tree. The clutch >> metadata is in general good enough, since if clutch can generate >> target/current.ent, I can certainly get the information I need from >> that. The only question is the conversion from >> l...@podling.incubator.apache.org (which clutch knows about) to >> archive/podling.apache.org/list (which is where the podling mail >> archives will be in future) is consistent. >> > Yes, it is, for all *@p.i.a.o lists. Well, I've found an inconsistency while changing the scripts to parse the content/podlings.xml and content/projects/.xml. Onami's dev list is the old-style: onami-...@incubator.apache.org but its archive is new-style: onami.incubator.apache.org/dev I don't want to special-case the script for this; can we make the archive consistent with the mailing list address? I also found two other problems: flex and photark removed the 'id="mail-dev"' attributes from their status XML files, and also replaced the list address with the web archive address, so there's no machine-readable way to find their mailing list address. I think it would be a good idea to require that the .xml files are machine-readable in the sense that all relevant information about a podling can be extracted from them without special-casing scripts. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Open Climate Workbench
On 26 Jan 2013, at 19:48, Mattmann, Chris A (388J) wrote: > Hi Everyone! > > I bring to the Incubator a new proposal for the Apache Open Climate > Workbench (incubating) project. I've added the proposal to the Incubator > wiki here: > > http://wiki.apache.org/incubator/ClimateProposal Sounds quite exciting! I'd like to come on board, though whether as an active participant or passively will depend on time and circumstance. Some years back I spent a lot of time&effort on the somewhat-related task of developing systems, firstly to produce, archive and distribute some of the datasets (mostly the Global AVHRR 1Km series in the '90s) and secondly to develop tools to visualise different datasets alongside and superimposed on each other. I see your proposal has a slightly different focus (and obviously benefits from a new generation of infrastructure in which a terabyte is no longer a mindblowing amount of data to manage), but I hope my background might still serve to kick-start an involvement! -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Ambari (incubating) 1.2.0 Release Candidate RC0.
Thanks for the correction Ted :). Yes thats the case! mahadev On Sun, Jan 27, 2013 at 6:51 PM, Ted Dunning wrote: > Do you mean a call for a vote to release 1.2.0? > > On Sun, Jan 27, 2013 at 6:16 PM, Mahadev Konar wrote: > >> Hi everyone, >> >> This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote >> was held on developer mailing list and it >> passed with 8 +1's with 6 of them binding. >> >> mahadev (IPMC, PPMC) >> ddas (IPMC, PPMC) >> acmurthy (IPMC) >> jitendra (PPMC) >> hitesh (PPMC) >> yusaku (PPMC) >> >> >> http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E >> >> >> The staging Staging site is: >> http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/ >> >> with user docs at: >> >> http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html >> and dev docs at: >> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development >> >> SVN source tag: >> https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0 >> >> PGP release keys (signed using 8EE2F25C) >> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x0DFF492D8EE2F25C >> >> One can look into the issues fixed in this release at >> >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI >> >> Vote will be open for 72 hours. >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> thanks >> mahadev >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Ambari (incubating) 1.2.0 Release Candidate RC0.
Do you mean a call for a vote to release 1.2.0? On Sun, Jan 27, 2013 at 6:16 PM, Mahadev Konar wrote: > Hi everyone, > > This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote > was held on developer mailing list and it > passed with 8 +1's with 6 of them binding. > > mahadev (IPMC, PPMC) > ddas (IPMC, PPMC) > acmurthy (IPMC) > jitendra (PPMC) > hitesh (PPMC) > yusaku (PPMC) > > > http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E > > > The staging Staging site is: > http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/ > > with user docs at: > > http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html > and dev docs at: > https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development > > SVN source tag: > https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0 > > PGP release keys (signed using 8EE2F25C) > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x0DFF492D8EE2F25C > > One can look into the issues fixed in this release at > > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI > > Vote will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > thanks > mahadev > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[VOTE] Apache Ambari (incubating) 1.2.0 Release Candidate RC0.
Hi everyone, This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote was held on developer mailing list and it passed with 8 +1's with 6 of them binding. mahadev (IPMC, PPMC) ddas (IPMC, PPMC) acmurthy (IPMC) jitendra (PPMC) hitesh (PPMC) yusaku (PPMC) http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E The staging Staging site is: http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/ with user docs at: http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html and dev docs at: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development SVN source tag: https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0 PGP release keys (signed using 8EE2F25C) http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x0DFF492D8EE2F25C One can look into the issues fixed in this release at https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks mahadev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Open Climate Workbench
Hi Suresh, We would be honored to have you on board. Thank you and I'm looking forward to your help and guidance! Cheers, Chris P.S. Add yourself to the wiki, no problem! On 1/27/13 4:36 PM, "Suresh Marru" wrote: > >On Jan 27, 2013, at 1:56 PM, "Mattmann, Chris A (388J)" > wrote: > >> Hey Suresh, >> >> Thanks a ton man and great to hear! >> >> To your comment below: >> >> On 1/27/13 5:56 AM, "Suresh Marru" wrote: >> >>> Hi Chris, >>> >>> Great proposal, I am personally looking forward to see more of these >>> federal government and international collaboration efforts adopt open >>> community process. Impressive to see this project is pulling together >>> initial developers from government and universities of US, South >>>Africa, >>> UK, Germany and India (I will hope all of them will be able to get >>>their >>> CLA's cleared). You are really scraping the black ice on bureaucratic >>> highways and preventing at least some reinventing wheels with valuable >>> tax payers money in multiple countries. >>> >>> Will this system evaluate and be inclusive of the community earth >>>system >>> modeling community? >> >> Yep this proposal includes some of those that are directly involved in >> that community including Tsengdar Lee, as well as members of the Earth >> System Grid Federation. We will definitely be inclusive and are happy to >> have involvement. > >Sounds very good. I am unable to resist my itch, so will like to jump on >the band wagon as a committer. Please let me know if I can add myself to >the proposal wiki. > >Thanks, >Suresh > >> Thanks! >> >> Cheers, >> Chris >> >>> >>> Suresh >>> >>> On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)" >>> wrote: >>> Hi Everyone! I bring to the Incubator a new proposal for the Apache Open Climate Workbench (incubating) project. I've added the proposal to the Incubator wiki here: http://wiki.apache.org/incubator/ClimateProposal The project is a distributed, scalable approach for the rapid comparison of remote sensing data (e.g., from NASA) with that of climate model output generated by major US and international activities including the US National Climate Assessment, the Coordinated Regional Downscaling Experiment (CORDEX), the North American Regional Climate Change Assessment Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC). Much of the software to be donated and evolved here at Apache as a community includes core dependencies to several Apache projects (OODT, Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc. We welcome your feedback over the next week or so for discussion and look forward to it! Cheers, Chris Mattmann Proposed Mentor and Champion ---proposal text = 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
Re: [DISCUSS] Apache Open Climate Workbench
On Jan 27, 2013, at 1:56 PM, "Mattmann, Chris A (388J)" wrote: > Hey Suresh, > > Thanks a ton man and great to hear! > > To your comment below: > > On 1/27/13 5:56 AM, "Suresh Marru" wrote: > >> Hi Chris, >> >> Great proposal, I am personally looking forward to see more of these >> federal government and international collaboration efforts adopt open >> community process. Impressive to see this project is pulling together >> initial developers from government and universities of US, South Africa, >> UK, Germany and India (I will hope all of them will be able to get their >> CLA's cleared). You are really scraping the black ice on bureaucratic >> highways and preventing at least some reinventing wheels with valuable >> tax payers money in multiple countries. >> >> Will this system evaluate and be inclusive of the community earth system >> modeling community? > > Yep this proposal includes some of those that are directly involved in > that community including Tsengdar Lee, as well as members of the Earth > System Grid Federation. We will definitely be inclusive and are happy to > have involvement. Sounds very good. I am unable to resist my itch, so will like to jump on the band wagon as a committer. Please let me know if I can add myself to the proposal wiki. Thanks, Suresh > Thanks! > > Cheers, > Chris > >> >> Suresh >> >> On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)" >> wrote: >> >>> Hi Everyone! >>> >>> I bring to the Incubator a new proposal for the Apache Open Climate >>> Workbench (incubating) project. I've added the proposal to the Incubator >>> wiki here: >>> >>> http://wiki.apache.org/incubator/ClimateProposal >>> >>> >>> The project is a distributed, scalable approach for the rapid comparison >>> of remote sensing data (e.g., from NASA) with that of climate model >>> output >>> generated by major US and international activities including the US >>> National Climate Assessment, the Coordinated Regional Downscaling >>> Experiment (CORDEX), the North American Regional Climate Change >>> Assessment >>> Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC). >>> Much of the software to be donated and evolved here at Apache as a >>> community includes core dependencies to several Apache projects (OODT, >>> Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python >>> software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc. >>> >>> We welcome your feedback over the next week or so for discussion and >>> look >>> forward to it! >>> >>> Cheers, >>> Chris Mattmann >>> Proposed Mentor and Champion >>> >>> ---proposal text >>> >>> = 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
[IP Clearance] CloudStack - enabling Juniper SRX/F5 BigIP inline mode functionality
Citrix wishes to donate to code that enables Juniper SRX and F5 Big IP to work in inline mode within CloudStack. - Code is on people.a.o [1] - Author (Kelven Yang) has signed an ICLA which has been acknowledged by secretary@ - IP clearance form is up on the incubator website. - Vote has passed on cloudstack-dev@i.a.o If there are any concerns about this donation, please don't hesitate to raise them. --David [1] http://people.apache.org/~yasker/SRX_F5_inline_mode/0001-CLOUDSTACK-306-Implement-SRX-firewall.patch [2] http://incubator.apache.org/ip-clearance/cloudstack-srx-f5-inline-mode.html [3] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] CloudStack automated SSH key reset
Citrix wishes to donate code that permits users of CloudStack to reset the SSH key of a VM in an automated fashion. - The code in question is on review board [1] - The author (Harikrishna Patnala) has submitted an ICLA to secretary@ which has been received. - The IP clearance form is on the incubator website [2] - The vote on cloudstack-dev@i.a.o has passed [3] If there are any concerns with this donation, please don't hesitate to raise them. --David [1] https://reviews.apache.org/r/8905/diff/2/ [2] http://incubator.apache.org/ip-clearance/cloudstack-reset-ssh-key.html [3] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] CloudStack - Public IP assignment for EIP in Basic zone
Citrix wishes to donate a feature around providing the option to assign a public IP as an Elastic IP in Basic Zones in CloudStack. - The patch is available on people.a.o [1] - The author (Murali Reddy) has signed an ICLA which has been recorded as received by secretary@ - The IP Clearance form has been uploaded to the incubator website [2] - The vote has passed on the cloudstack-dev@i.a.o mailing list [3] If there are any concerns around this donation, please don't hesitate to raise them. --David [1] http://people.apache.org/~muralireddy/0001-CLOUDSTACK-265-provide-option-to-turn-off-automatic-.patch [2] http://incubator.staging.apache.org/ip-clearance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone.html [3] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP Clearance] L4-L7 Network Services in shared networks using VLAN isolation in CloudStack
Citrix has offered a donation of code to enable L4-L7 Network Services in shared networks using VLAN isolation in CloudStack. - Code is available on people.a.o [1] - Author (Murali Reddy) has submitted a ICLA to secretary@, and it's noted on the committer index as having been received. - IP Clearance page is up on the incubator site [2] - Vote has passed on cloudstack-dev@i.a.o list. [3] If you have concerns about this donation, please don't hesitate to raise those questions. --David [1] http://people.apache.org/~muralireddy/0001-CLOUDSTACK-312-enable-L4-L7-network-services-in-the-.patch [2] http://incubator.apache.org/ip-clearance/cloudstack-network-services-in-shared-networks.html [3] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201301.mbox/%3c7a92ff96df135843b4b608fb576bfc3e012da3adf...@sjcpmailbox01.citrite.net%3e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Open Climate Workbench
Hey Suresh, Thanks a ton man and great to hear! To your comment below: On 1/27/13 5:56 AM, "Suresh Marru" wrote: >Hi Chris, > >Great proposal, I am personally looking forward to see more of these >federal government and international collaboration efforts adopt open >community process. Impressive to see this project is pulling together >initial developers from government and universities of US, South Africa, >UK, Germany and India (I will hope all of them will be able to get their >CLA's cleared). You are really scraping the black ice on bureaucratic >highways and preventing at least some reinventing wheels with valuable >tax payers money in multiple countries. > >Will this system evaluate and be inclusive of the community earth system >modeling community? Yep this proposal includes some of those that are directly involved in that community including Tsengdar Lee, as well as members of the Earth System Grid Federation. We will definitely be inclusive and are happy to have involvement. Thanks! Cheers, Chris > >Suresh > >On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)" > wrote: > >> Hi Everyone! >> >> I bring to the Incubator a new proposal for the Apache Open Climate >> Workbench (incubating) project. I've added the proposal to the Incubator >> wiki here: >> >> http://wiki.apache.org/incubator/ClimateProposal >> >> >> The project is a distributed, scalable approach for the rapid comparison >> of remote sensing data (e.g., from NASA) with that of climate model >>output >> generated by major US and international activities including the US >> National Climate Assessment, the Coordinated Regional Downscaling >> Experiment (CORDEX), the North American Regional Climate Change >>Assessment >> Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC). >> Much of the software to be donated and evolved here at Apache as a >> community includes core dependencies to several Apache projects (OODT, >> Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python >> software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc. >> >> We welcome your feedback over the next week or so for discussion and >>look >> forward to it! >> >> Cheers, >> Chris Mattmann >> Proposed Mentor and Champion >> >> ---proposal text >> >> = 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) tech
[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563830#comment-13563830 ] Suresh Marru commented on INCUBATOR-125: Marvin, great job in putting together this short and concise document. I think it will also be useful to mention about the DISCLAIMER file requirement [1] for the incubator podlings. [1] - http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer > How-to guide for "Assembling LICENSE and NOTICE" > > > Key: INCUBATOR-125 > URL: https://issues.apache.org/jira/browse/INCUBATOR-125 > Project: Incubator > Issue Type: Improvement > Components: site >Reporter: Marvin Humphrey > Attachments: licensing_howto.mdtext > > > While the ASF provides reference documentation for LICENSE and NOTICE, > confusion persists and existing versions vary widely in quality. > To address these problems, we should augment the reference documentation with > a "how-to" guide which provides formulaic instructions for assembling LICENSE > and NOTICE under common conditions. > One key feature of this how-to should be a mapping of approved licenses to > what they require as far as NOTICE. This mapping will help PMCs determine > when the licensing information of a dependency contains a "required third > party notice" which must be added to NOTICE. > There are at least four possible locations where this how-to might live: > * www.apache.org/dev/licensing_howto.html -- probably the best location, > considering the intended audience. > * www.apache.org/legal/licensing_howto.html -- if legal wants it. > * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, > because the information applies to TLPs as well as podlings and we have a > problem with duplication. > * Somewhere on community.apache.org -- in theory. -- 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
Re: Incubator voting status page
Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100: > On 26.01.2013 14:27, Benson Margulies wrote: > > Brane, are you currently using the pickled clutch metadata? If we just > > need to add a field to it we can. > > Nope, I'm currently walking the incubator archive tree. The clutch > metadata is in general good enough, since if clutch can generate > target/current.ent, I can certainly get the information I need from > that. The only question is the conversion from > l...@podling.incubator.apache.org (which clutch knows about) to > archive/podling.apache.org/list (which is where the podling mail > archives will be in future) is consistent. > Yes, it is, for all *@p.i.a.o lists. To your original question: I usually use podlings.xml/[status=current]. > -- Brane > > > - > 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] Apache Open Climate Workbench
Hi Chris, Great proposal, I am personally looking forward to see more of these federal government and international collaboration efforts adopt open community process. Impressive to see this project is pulling together initial developers from government and universities of US, South Africa, UK, Germany and India (I will hope all of them will be able to get their CLA's cleared). You are really scraping the black ice on bureaucratic highways and preventing at least some reinventing wheels with valuable tax payers money in multiple countries. Will this system evaluate and be inclusive of the community earth system modeling community? Suresh On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)" wrote: > Hi Everyone! > > I bring to the Incubator a new proposal for the Apache Open Climate > Workbench (incubating) project. I've added the proposal to the Incubator > wiki here: > > http://wiki.apache.org/incubator/ClimateProposal > > > The project is a distributed, scalable approach for the rapid comparison > of remote sensing data (e.g., from NASA) with that of climate model output > generated by major US and international activities including the US > National Climate Assessment, the Coordinated Regional Downscaling > Experiment (CORDEX), the North American Regional Climate Change Assessment > Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC). > Much of the software to be donated and evolved here at Apache as a > community includes core dependencies to several Apache projects (OODT, > Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python > software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc. > > We welcome your feedback over the next week or so for discussion and look > forward to it! > > Cheers, > Chris Mattmann > Proposed Mentor and Champion > > ---proposal text > > = 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 "
