15:04 < djay> hello, everybody nice to get you for the PSC meeting 15:04 < djay> we don't have to wait for Nick which is currently in a meeting, speaking about ZOO-Project with Spatialitics representant 15:05 * jmckenna thinks we still have 5 minutes till meeting time 15:05 < djay> ok, I can wait 5 minutes 15:05 < djay> jmckenna: many thanks for updating the PSC meetings agenda 15:06 -!- maxi_ [~chatzilla@195.176.186.34] has joined #zoo-project 15:07 < jmckenna> how many do we need for quorum? 15:07 < maxi_> ciao 15:07 < djay> Hi maxi_ 15:07 < djay> so nice to see you 15:07 < djay> mmm, I should say "see" :) 15:08 < maxi_> yep, still alivce ;-) 15:08 < maxi_> alive.. 15:08 < djay> I'm sorry guys, I get Hayashi-san and Venka-sensei on Skype, so I'm contacting them to remind the irc channel :) 15:08 < djay> yes I wondered :) 15:09 < maxi_> you know.. foss4g deadlines summed to other thousand thing to do :-o 15:09 < jmckenna> remind them on web interface: http://webchat.freenode.net/ 15:09 < djay> yes, they forgotten to come on irc in fact, they were waiting for skype :) 15:09 -!- hhayashi [~chatzilla@softbank220014090109.bbtec.net] has joined #zoo-project 15:09 < djay> yep sorry jmckenna I forgot the link myself 15:09 < djay> hi hhayashi 15:10 < hhayashi> Hi Gerald 15:10 < jmckenna> hhayashi: long time my friend 15:10 < djay> We just need to wait for Venka-sensei, which just confirm he will arrive on irc 15:10 < djay> mm, I will give him the link, thx jmckenna 15:10 < hhayashi> Hi Jeff! 15:10 < jmckenna> :) 15:10 < djay> gasp, venka say he cannot connect to freenode 15:11 < djay> jmckenna: does your web interface is working from anywhere in the world ? 15:11 -!- venka [~chatzilla@i121-112-76-112.s11.a027.ap.plala.or.jp] has joined #zoo-project 15:11 < djay> ho great 15:11 < djay> hi venka 15:11 < venka> Hi all 15:11 < markusN> Hi all 15:11 < djay> so I think we are all here 15:11 < jmckenna> hi all 15:11 < maxi_> well, so I may start with an announce to the zoo-PSC: I'm going to be daddy in January, the tribe is growing up :-D 15:11 < jmckenna> maxi_: wow congrats!!!!!!!!!!!!!!!!!! 15:11 < djay> ho, so great maxi_ !!! Congratulation to you and your wife 15:12 < venka> Great news Maxi Congratulations!!!! 15:12 < maxi_> thanks guys! we'll KAMPAI in Denver ;-) 15:12 < jmckenna> i will teach your son or daughter to become millionare ice hockey star 15:12 < jmckenna> :) 15:12 < hhayashi> Congratulation you and your baby!! 15:12 < maxi_> :-o 15:12 < jmckenna> (beer got in the way of my plans, and girls) 15:12 < markusN> great maxi_ :D 15:13 < maxi_> ok, thanks. let's move to the meeting ;-) 15:13 < venka> (Maxi's baby can quickly learn how to become a millionaire suing FOSS4G) 15:13 < venka> http://www.zoo-project.org/trac/wiki/PSC/meetings/PSCMeet14 15:13 < venka> meeting page. 15:14 < djay> yep, jmckenna make relevant changes to it 15:14 < maxi_> i see 15:14 < djay> to not bother Venka this time, I would like to propose myself th chair the meeting 15:14 < venka> (suing was using) 15:14 < djay> s/th/to 15:14 < venka> +1 for Gerald as chair 15:15 < maxi_> +1 15:15 < jmckenna> +1 15:15 < djay> +1 15:15 < hhayashi> +1 15:15 < djay> So let start with the first itme 15:15 < djay> ZOO-Kernel-1.2.0rc2 release 15:15 < markusN> +1 15:16 < djay> the release was made available later last week 15:16 < djay> after publishing this realease, which comiled and worked fine with my old setup of Spidermonkey 15:17 < djay> I discovered that some problem occurs when linking to a newer version 15:17 < venka> Great news about rc2. What are the pensing issues before 1.2.0 release, Gerald. 15:17 < djay> about the release I took good note about the comment jmckenna made on the psc mailing list and try to apply this way for the new issues 15:17 < jmckenna> djay: great, thanks man 15:18 < venka> Some issue with Python services that Luca pointed. Has that been fixed? 15:18 < djay> so I tried to write tickets (42 and 43) which will be added to the Release page 15:19 < djay> about the pending issue, by now I don't see anyone. Nevertheless, we will have to publish a rc3 including correction of ticket 43 and 42 15:19 < jmckenna> excellent. yes important to use trac to file all issues, before even you start work on them. i've noticed you are doing this now, excellent! :) 15:19 < djay> venka: that was not fixed 15:19 < djay> in fact I cannot fix it as I cannot reproduce 15:19 < markusN> it is very important to make RCs (I say this as encouragement) 15:19 < venka> will be fixed before 1.2.0 release? 15:19 < djay> indeed we are using massively Python services as ZOO Services but never got this issue 15:20 < markusN> (unlike QGIS, they didn't get the point in the past) 15:20 < jmckenna> i believe that i asked him (reporter) to reproduce on a different system, not using the same binaries...but the reporter did not do that 15:20 < djay> markusN: I agree, I think better to provide numerous rc that publishing then update one week after a new release to apply any fixes 15:20 < djay> unfortunately this can explain why the 1.2.0 is not out already 15:21 < djay> nevertheless using some functionalities of the ZOO-API I noticed lot of missing capbilities which have tobe added, but this will be postoned for 1.3.0dev 15:21 < markusN> we made 7 RCs for GRASS 6.4.0 and it was a good idea (sure, everybody is impatient...9 15:21 < jmckenna> if the reporter is unwilling to do more testing, i feel the release should go on. 15:22 < venka> (Markus, you mention QGIS, we are also getting several issues with GRASS-6.4.1 in Japanese Locale, we need to discuss that some time) 15:22 < markusN> sure Venka, just I need to be contacted for that 15:22 < jmckenna> yes mapserver had many RCS for 6.0...they were much needed! 15:23 < djay> about rc2, I guess you noticed that I finally included a small test suite, which made me able to test all the basics functionalities of the ZOO-Kernel. In fact it was also a tool for me for releasing 15:23 < jmckenna> excellent. the test suite is in SVN correct? 15:23 < djay> jmckenna: yes, in fact you take a good example, maybe they should wait a bit more, to avoid the security fix ? 15:23 < djay> yes the test suite is in SVN 15:23 < venka> Great addition the test tool. 15:23 < jmckenna> great 15:23 < djay> I commited it indeed as I developed it 15:24 < djay> but when I did that I honnestly question myself 15:24 < djay> why are we not using similar stuff as MapServer use : RFCs 15:25 < jmckenna> remember my push for that at beginning of PSC here? 15:25 < venka> so we will have rc3 coming soon? 15:25 < jmckenna> venka did not agree with me at that time 15:25 < jmckenna> (RFCs) 15:25 < djay> Indeed, I think some discussion would occurs before I implement something new. Here it was a limited testing suite, but if we discussed somebody probably point me that we need to think about services level testing and kernel testing (even if this last is not that easy as it uses no service for testng) 15:26 < jmckenna> now we are becoming a mature project and you can see that these tools (Trac, SVN, IRC, RFCs) are our lifeline 15:26 < djay> jmckenna: yes I remember 15:26 < djay> and I think this is the right way to go honnestly 15:26 < djay> jmckenna: you're right 15:26 < jmckenna> great 15:26 < jmckenna> then let's just start using them 15:27 < venka> Did not agree because ZOO-Developer community is still small. No issues with lead developer, Gerald thinks that it is the right way to go. 15:27 < jmckenna> you can imagine an "rfc" folder in SVN at http://www.zoo-project.org/trac/browser/trunk/docs/development 15:27 < djay> sounds great indeed 15:27 < jmckenna> then just 'git er done' (saying to just do things and not wait for comments) 15:28 < djay> jmckenna: where I can get trouble is that I'm not sure what should go into rfc directory and what have to go directly in doc (I say that thinking of a next topix we should discuss during th is meeting) 15:28 < jmckenna> np i can create example 15:29 < djay> great 15:29 < djay> do we have to go as far as getting some guideline to write rfc ? 15:29 < djay> is there any workflow to define ? 15:30 < jmckenna> yes, a note should be added to our PSC guidelines 15:30 < djay> ok, great (can help me a lot I think). Can that become an action item for you jmckenna ? 15:30 < jmckenna> yes 15:30 < djay> wonderful 15:31 < jmckenna> then all major development features are forever documented in that rfc folder 15:32 < djay> So I think we can conclude about the 1.2.0 first topic of the meeting here, the rc3 will be published this week. Then, except if nobody find new bug, then we should go for the 1.2.0 official release 15:32 < djay> (nobody was somebody :) ) 15:32 < maxi_> +1 15:33 < djay> everybody agree to go to the next agenda item ? 15:33 < jmckenna> +1 15:34 < markusN> +1 15:34 < venka> +1 15:35 < hhayashi> +1 15:35 < djay> nice, so the next item is the ZOO-Docs release status 15:35 < jmckenna> great. i feel we are fully ready to launch the docs when 1.2.0 happens 15:36 < jmckenna> in fact the docs release could happen now 15:36 < djay> jmckenna: maybe remind the docs link, this way PSC can look into it 15:36 < jmckenna> (a view of them now in html: http://www.zoo-project.org/docs/) 15:36 < venka> maybe better to release docs when rc3 is released. Maybe easier for testers to have docs. 15:36 < jmckenna> with gerald we also added the 2010 workshop recently 15:37 < jmckenna> and also of note, (gerald please comment if i am wrong) we recently, like yesterday, had a contributor share their fully translated docs in french! 15:38 < djay> jmckenna: I think that there is a crontab to automatically produce the doc on the server (occuring each two hours) 15:38 < jmckenna> so now we see the benefits of these easy-to-edit text files for documentation :) 15:38 < maxi_> +1 (sorry i was 1 min away) 15:38 < jmckenna> djay: is that a question? 15:38 < djay> yes it was, sorry :) 15:39 < venka> Add how to translate in the docs, if it is not there already. 15:39 < djay> well, yes indeed the multiple languages support was introduced by a french guy (http://zoo-project.org/trac/ticket/44) named Thomas Gratier 15:39 < djay> venka: it is not there in fact 15:39 < venka> Great work by Thomas. 15:40 < markusN> great indeed! 15:40 < markusN> (may I make a small comment? The link color (yellow-orange) is hard to read for mid-agers like me... please make it a bit darker for better contrast) 15:40 < jmckenna> djay: re: cron job: I will check that it is setup. i remember looking at it earlier 15:41 < djay> great, but we have to valid his work then commit his modifications to the svn I guess 15:41 < jmckenna> markusN: good feedback. nick is the stylist here...but i will relay your feedback 15:41 < djay> and please note that the documentation was not fully translated into french, some pages only was. But I thin we have to encourage people to involve themself in the project. 15:42 < markusN> jmckenna: perhaps the letters are just to thin on big monitors with high DPI 15:42 < venka> Would be nice if Thomas could write a how-to-translate. 15:43 < djay> in fact, for documentation contributors I wondered if we have to use the same way that we use to validate dev account or use a separated way ? 15:43 < jmckenna> a short note should be added to the Doc Guide (http://www.zoo-project.org/docs/development/documentation.html) 15:43 < venka> Or is it that easy that we do not need a how-to for translators? 15:43 < djay> I mean, do we have to ask for psc to vote for accepting Documenters accounts 15:44 < jmckenna> it's that easy. a few notes need to be added to that existing how-to-document page 15:44 < jmckenna> (indeed Elvis in Beijing is adding pages for mapserver-CN translations) 15:44 < djay> In fact, I wonder also to give to all of them (documentors) to ssh account 15:44 < jmckenna> djay: i've missed your comments 15:45 < jmckenna> remember my earlier comments that we need an SVN doc group? 15:45 < djay> jmckenna: maybe after we commit the change (if acceptable) we can answer his mail about getting involved in ZOO-Project workshop material ttranslation 15:45 < jmckenna> here my comments again come into play 15:45 < markusN> (sidenote: in 8min I must leave to take a train) 15:45 < djay> in fact this is an important point about the ZOO-Documentation status for me 15:45 < djay> what about the Japanese transalation we get already ? 15:46 < djay> do we plan to get it into restructured text ? 15:46 < djay> markusN: thanks, for comming, the meeting cannot be cloed at that time I think. 15:46 < jmckenna> SVN doc group only has privilege to commit to docs folder. and it would be managed by Doc team (members are added by Doc team) 15:46 < markusN> djay: sure, was just FYI 15:46 < djay> markusN: you would be helpful to give feedbacks about the FEM item 15:46 < markusN> perhaps I can grab connection 40min later 15:47 < venka> djay, his mail? you mean Thomas? Japanese translation could be started after final English docs are released. 15:47 < jmckenna> i'm not aware of JP docs. yes they should easily commit them in text format 15:47 < djay> venka: I spoke about the material already translated 15:47 < jmckenna> it is very easy, once we setup an SVN doc group 15:47 < djay> jmckenna: you are not aware about japanese format ?? 15:47 < djay> http://zoo-project.org/site/ZooWorkshop/FOSS4GJapan/ja 15:47 < djay> form this page http://zoo-project.org/site/ZooDocumentation 15:48 < djay> we also get italian one 15:48 < djay> I didn't remember as it was not made as Wiki pages, forgive me 15:48 < djay> this great job was made by Lucas 15:48 < jmckenna> yes those pages must be converted to text format by the contributors and committed into svn, through the non-existing-as-yet SVN doc group :) 15:49 < djay> which help me a lot since long time now, I was thiking of giving him svn acces (sorry for this side effect of speaking about this :) ) 15:49 * jmckenna great to see this much attention to docs. they are extremely important for a project :) 15:50 < jmckenna> svn doc group: means not using ports and vpn etc to login. i mean a simple SVN login 15:50 < djay> jmckenna: so you didn't try as I asked you the https access right ? 15:50 < djay> nick did following few intructions through skype 15:51 < djay> I even guess that I've added info on how to setup yoru htts account 15:51 < djay> mmm, jmckenna cna you cnfirm that I asked you for testing please ? 15:51 < djay> I'm not sure anymore :) 15:51 < djay> http://zoo-project.org/trac/wiki/ZooWebSite/ZooKernel/Download?version=7 15:52 < jmckenna> skype: yikes. it should be a ticket 15:52 < jmckenna> see, i forget irc and skype and direct emails. ticket is recorded :) 15:52 < djay> ok, my fault. 15:52 < jmckenna> i will file a ticket 15:53 < jmckenna> my fault this time :) 15:53 < djay> documentation is here : http://zoo-project.org/trac/wiki/ZooDevDocumentation 15:54 < jmckenna> can we move on from docs now? :) 15:54 < markusN> sorry I must go, will try to reconnect later if I catch a wifi connection 15:54 < venka> +1 15:54 < djay> About ZOO-Documentation I wondered about pages like the one I just gave to you. The question should be : what have to go in the doc and what have to stay in the wiki ? 15:54 < djay> many thanks for coming markusN 15:54 < venka> bye Markus 15:54 < markusN> djay: we can also postpone the FEM dev stuff to the next meeting, no problem for me 15:54 < markusN> bye talk to you soon 15:55 < djay> bye 15:55 -!- markusN [~chatzilla@77.72.197.131] has quit [Quit: ChatZilla 0.9.87 [Firefox 5.0/20110615151330]] 15:55 < djay> ok, sorry I didn't notice the vote request 15:56 < djay> ok, +1 (I will discuss my questions through email about documentation) 15:56 < djay> Please, vote for "can we move on from docs now?" 15:57 < hhayashi> +1 15:57 < venka> +1 15:57 < maxi_> +1 15:57 < djay> great we can move on 15:57 < jmckenna> +1 15:57 < djay> so next topic : Preparations for ZOO-Workshop at FOSS4G2011 15:59 < djay> the current status of the Workshop preparation is that we get everything to finish the writting 15:59 * jmckenna just completed my mapserver workshop prep last night. it takes a lot of time to do these 16:00 < djay> indeed, yesterday we run the setup on the Nick's computer and he was able to run the final result web interface requesting services on his own 16:00 < djay> the plan for this year workshop is as follow : 16:00 < djay> 1) Introduction to ZOO-Project 16:00 < djay> 2) writting Buffer.zcfg: how to write a ZCFG file 16:01 < djay> 3) Python service developpement : Buffer and Intersection (all the other services are given as exercices) 16:01 < djay> 4) JavaScript service : Buffer interest (displaying a mask over the data except for the buffer around the selected featrue), POI in buffer around the selected feature 16:02 < djay> 5) Extras : output from Buffer and Intersection as application/x-zipped-shp 16:02 < djay> (for the last section, you have to know that the current ogr_sp developed during the workshop deal with features and no more with geometry only data) 16:03 < maxi_> nice program! 16:03 < djay> Indeed, in the Buffer and Intersection we keep the geojson and gml output 16:03 < djay> but we also added kml output support 16:03 < jmckenna> my personal feedback is to focus on the client side...let users see the service first in the workshop, in an easy-to-use javascript-y interface..and then work backwords. indeed i spent many days (week?) updating the mapserver workshop to use openlayers. so that is my own personal feedback for ZOO workshop, speaking from much experience 16:03 < djay> indeed two lines was required in python code and a new supported node in the zcfg only is required ot add new output format 16:04 < djay> jmckenna: I'm not sure to follow 16:04 < djay> as oyu noticed I never spoke about the OpenLayers tuff 16:04 < djay> and it was done this way volontary 16:04 < jmckenna> that is my point exactly 16:04 < djay> indeed, they won't touch a line of HTML of JS for the web interface 16:04 < jmckenna> ok just note my feedback..no worries man 16:04 < djay> the web interface will be available since the begining of the workshop 16:04 < djay> they even never add a button in fact 16:05 < djay> they just get an interface since the begining which will be animated through the services they will develop 16:05 < venka> Jeff: you mean start explaining the client side and then move to explaining the Server. 16:05 < djay> I guess we are right, for me it the way yo spoke about 16:05 < jmckenna> venka: exactly 16:05 < djay> jmckenna: you mean speaking about client side ? 16:05 < venka> ++1 for that 16:06 < djay> gasp in fact I never plan to speak one time about the interface except to introduce it as an url where they can tests their services 16:06 < jmckenna> that way workshop attendees can then refresh their client side app when gerald is having them code their services 16:06 < jmckenna> client-side answering the big question: why? what does WPS do? 16:07 < jmckenna> ok if you plan on doing that already excellent 16:07 < jmckenna> i missed that in your steps above 16:07 < maxi_> it depends always on level of participants, but i general i found it is generally low, so I support Jeff and Venka 16:08 < jmckenna> true 16:08 < djay> I think you are right 16:09 < jmckenna> and again for almost 10 years of foss4g workshops: each year presenters tell me: i asked for advanced users but i got beginners 16:09 < djay> maybe we can add this to the first section : Introduction to ZOO-Project. Finishing by presneting what WPS is able to add to your web client interface ? 16:09 < jmckenna> good idea 16:09 < djay> perfect 16:10 < maxi_> yes, it push people to undestand why wps exists.. 16:10 < djay> I agree 16:14 < jmckenna> WMS benchmarking meeting starts now in #foss4g :( 16:14 < venka> Next item? 16:14 < djay> gasp 16:14 < djay> do we postpone all the other items ? 16:14 < djay> if dkastl can vote I think we still have quorum 16:15 < jmckenna> i will do both, just we must keep moving :) 16:15 < djay> anyway, I would like to give a note about one item 16:15 < djay> great 16:15 < venka> djay: go ahead. 16:15 < djay> so I would like to sak for moving to the next item 16:15 < djay> Quick report from GĂ©rald about Fondazione Edmund Mach ( FEM) sponsored ZOO development 16:15 < djay> +1 16:15 < jmckenna> +1 16:15 < venka> +1 16:15 < maxi_> +1 16:16 < dkastl> +1 16:16 < djay> great :) 16:16 < djay> so GeoLabs SARL was directly contracted by FEM to introduce MapServer output support in the ZOO-Kernel 16:16 < djay> developpement was made and delivered to the FEM 16:17 < hhayashi> +1 16:17 < djay> I got good feedbacks from both Lucas and Markus about their experience using this new support 16:17 < jmckenna> djay: wow excellent. what is FEM??? 16:17 < djay> gasp, sorry 16:17 < djay> I thought everybody knows as it is one of our knowledge sponsor 16:17 < venka> Djay: great work. FEM is where MarkusN works. 16:18 < jmckenna> i did not know FEM, my apologies 16:18 < djay> so FEM stands for Fondazione Edmund Mach 16:18 < venka> (nothing to do with safe soft) 16:18 < djay> :) 16:18 < jmckenna> ok thanks, sorry for the dumb question :) 16:19 < djay> in fact, to be totally frank with you, PSC members. I would like ot say that I'm proud of the MapServer support integration 8-) 16:19 < hhayashi> :D 16:19 < djay> indeed, from almost any kind of dataset you can return back from yoru service you can get a WMS/WFS/WCS service automatically deployed 16:20 < venka> djay: Great work and you make the PSC proud. Will Mapserver support included in 1.2.0? 16:21 < djay> I don't think so huge modification of the ZOO-Kernel should be included in the 1.2.0 version 16:21 < djay> I even announce, during ICC which occurs some weeks ago (if I remeber well), that the 1.3.0 will support MapServer output 16:22 < jmckenna> no tickets filed so really no record of this development 16:22 < djay> absolutly jmckenna 16:22 < djay> it was a bit hard for me, indeed I'm not that familiar. 16:22 < djay> Lucas posted some tickets about this 16:23 < djay> but people probably don't understand, as the openlayers output, as he is the only one to get the patch to apply to the SVN source tree 16:23 < jmckenna> tickets after-the-dev are much different. but good to know you now realize this importance :) 16:23 < djay> it is also not a good idea, I think, to introduce the code in the SVN as we are on the way for the 1.2.0 already 16:23 < venka> Nice to see GRASS+MapServer+QGIS(WPS plugin) playing well with ZOO-Kernel. 16:23 < djay> yes, I confirm I clearly see the importance of such things 16:24 < djay> yes, so about the QGIS client, please I would like to announce to you that I get a working one on my laptop :) 16:24 < djay> I say that cause I noticed after updating my QGIS version that the WPS client is not working anymore :( 16:24 < djay> so I still use the old QGIS version 16:25 < venka> 1.6? 16:25 < djay> ho, even older I think 16:25 < jmckenna> i've never used the qgis plugin! wrist slap for me! :) 16:26 < djay> I can provide the version : 1.5.0 and the revision number : r13595:13597 but not sure it will help 16:26 < djay> well you did well jmckenna :) 16:27 < djay> unfortunately I think that this plugin is not really maintained or even tested by the community 16:27 < jmckenna> :) indeed i now have zoo running on my gentoo machine and on windows! 16:28 < djay> so for the FEM report I guess we finished already. When the 1.2.0-rc3 will be out I will commit the MapServer support publically 16:28 < venka> QGIS WPS plugin is important. PSC should think of finding someone (qgis developer) to help on this. 16:29 < djay> I would like everybody to understand something about this svn update: it makes almost everybody able to produce so easilly an interface to publish WMS/WFS/WCS service 16:29 < venka> djay: You could put the working QGIS plugin somewhere on the ZOO website. 16:29 < djay> I know it one of our goal, but just to make sure you know :) 16:30 < djay> venka: I can do that, good idea. Yoshida-san waiting for me to give him the plugin he told me yesterday and I still forgot to send to him;.. 16:30 < djay> I think we can move on to the next topic 16:30 < djay> +1 to move to the next topic 16:31 < jmckenna> +1 16:31 < maxi_> +1 16:31 < venka> (we could use Angelos pyCSW in future, maybe) 16:31 < venka> +1 16:31 < hhayashi> ...+1 16:31 < djay> (sure we will do, he get some free day out of army those days) 16:31 < djay> so the topic : "Report on WPS Benchmarking progress for FOSS4G2011 " 16:32 < djay> well in fact it is not going so well from my point of view 16:32 < jmckenna> i added that topic because it interests me 16:32 < djay> I can even say that it is probably the worst idea I never got before finally :) 16:32 < jmckenna> indeed the WMS benchmarking is not going well either - teams are very busy with other things it seems. 16:32 -!- Irssi: #zoo-project: Total of 10 nicks [1 ops, 0 halfops, 0 voices, 9 normal] 16:32 < djay> why I let me speak so frakly 16:33 < jmckenna> yes that is why i am an observer with WPS benchmarking - i know from experience it is a HUGE task 16:33 < jmckenna> and unpaid 16:33 < jmckenna> so i am curious how wps benchmarking is going 16:33 < djay> gasp, I was writting a sentence but not sure I can say that publically anymore :/ 16:33 < jmckenna> a sign of the industry times? not sure 16:33 < djay> mmm, so how to say that diploatically 16:33 < jmckenna> please i need to hear 16:33 < jmckenna> i am worried about WMS myself 16:34 < maxi_> yes, coursious.. 16:34 < djay> at the begining, and as you probably think also, we planned to make benchmarking about WPS Servers 16:36 < djay> so Benchmarking WPS Server intances should be as easy as : defining processes to get installed by WPS implementors, providing XML/KVP requests, request the WPS Instance, check for botht validity of XML answers and results 16:36 < jmckenna> makes sense 16:36 < djay> nevertheless, as we get "chance" to count WPS Clients implementor, we decided to tests also clients side 16:37 < djay> so my first question should be: are you testing WMS clients during the Benchmarking ? I don't think so 16:38 < jmckenna> well we are in fact testing WMS clients. 16:38 < djay> gasp, so I'm wrong 16:38 < jmckenna> client meaning the engine 16:38 < djay> hopefully you get working ones :) 16:38 < jmckenna> WMS standard vs WMS client 16:39 < maxi_> i would say that is out of testing WPS, other variables came into when you use clients... 16:39 < jmckenna> we are testing the engine's speed of WMS GetMap request,,, 16:42 < djay> nevertheless, the good point is that teams are well involved in the Shootout, almost everybody is joining and sharing ideas during the meeting 16:42 < djay> it is good to exchange with other WPS projects 16:42 < djay> this are good points 16:42 < venka> Nice to know. 16:43 < venka> Can we go ahead? 16:43 < djay> I thnk yes 16:44 < djay> so, are we agree to close the meeting ? 16:44 < venka> I think we are done with the agenda. 16:44 < venka> I think we are done with the agenda. 16:44 < venka> +1 to close the meet 16:44 < djay> +1 16:45 < jmckenna> +1 (wow 1.5 hours!) 16:45 < venka> bye all 16:45 < djay> bye venka 16:45 < maxi_> +1 16:45 < hhayashi> +1 bye all 16:45 < djay> many thanks for joining the metting 16:45 < djay> many thanks maxi_ and hhayashi