| | 16 | |
| | 17 | == Transcript == |
| | 18 | {{{ |
| | 19 | rbray> Bruce will be absent today he is on vacation. Tom will most likely be late |
| | 20 | -->| danmo (n=dmorisse@157-146.svr.royaume.com) has joined #mapguide |
| | 21 | <jasonbirch> I'm here. |
| | 22 | <jasonbirch> Fire alarm - test only :) |
| | 23 | <rbray> Hey looks like you and me. |
| | 24 | <jasonbirch> HarisK you around? |
| | 25 | <Andy_Morsell> I'm here as well |
| | 26 | * danmo lurking |
| | 27 | <HarisK> Hi |
| | 28 | <jasonbirch> That's enough for a vote :) |
| | 29 | <rbray> OK, so we have Harris, Jason, Andy, and myself. Bruce is on vacation, Tom is in a meeting. |
| | 30 | <jasonbirch> As is Paul |
| | 31 | <rbray> No he will be late too. |
| | 32 | <rbray> Any agenda items? I did not have any for today. |
| | 33 | <madair> lurking for Paul |
| | 34 | <jasonbirch> Maybe talk a bit about roadmap, putting more realistic dates to it |
| | 35 | <jasonbirch> Also, f2f at FOSS4g? |
| | 36 | <rbray> Let's start with the later. Who will be as FOSS4G? |
| | 37 | <Andy_Morsell> I will be there. Sunday night through Thursday afternoon. |
| | 38 | <jasonbirch> Me! |
| | 39 | <rbray> I will be there everyday except Wednesday (don't ask). |
| | 40 | <rbray> I have to check with Tom and Bruce, I think Bruce can be there but I bet Tom cannot. |
| | 41 | <rbray> Nathalie has planned a BOF and given most of us are there a F2F meeting of the PSC would be good. |
| | 42 | <rbray> We should start a wiki page agenda for that soon. |
| | 43 | <jasonbirch> After? |
| | 44 | <jasonbirch> At a pub? |
| | 45 | <jasonbirch> :) |
| | 46 | <rbray> Definitely. |
| | 47 | <rbray> I'll buy! |
| | 48 | <HarisK> I am there at saturday |
| | 49 | <jasonbirch> I'll _really_ be there then. :) |
| | 50 | <rbray> Jason when you say after, do you mean one evening or Thursday evening? |
| | 51 | <Andy_Morsell> I could do that Monday night, my girlfriend arrives on Tuesday so will be with her that evening. Weds is the banquet night. |
| | 52 | <rbray> I kind of like Monday night. |
| | 53 | <jasonbirch> Isn't there a mixer at the Strathcona that night? |
| | 54 | <jasonbirch> Not that it really matters... |
| | 55 | <jasonbirch> Monday works OK for me. |
| | 56 | <rbray> OK. I will start an agenda page on the wiki. |
| | 57 | <jasonbirch> Cool. |
| | 58 | <rbray> Feel free to add to it once it is up. |
| | 59 | <jasonbirch> I'm sure we'll be talking about the REST stuff by then :) |
| | 60 | <rbray> hope so. |
| | 61 | <rbray> Let's talk Roadmap. |
| | 62 | <Andy_Morsell> I see that the BOF for MGOS is Tues from 4:45 to 7:00 |
| | 63 | <jasonbirch> K. |
| | 64 | <jasonbirch> That's right. http://wiki.osgeo.org/index.php/FOSS4G2007_BOF_Sessions |
| | 65 | <rbray> Yes the BOF is Tuesday night, and I will miss it. I have to be on a plane. |
| | 66 | <Andy_Morsell> Nothing like being double-booked..... bummer. |
| | 67 | <rbray> Yea |
| | 68 | <jasonbirch> That's OK, Nathalie can do all the talking :) |
| | 69 | <rbray> So when can we realistically release a 2.0 beta 1? |
| | 70 | <rbray> And what will be in it, besides Fusion? |
| | 71 | <rbray> I personally still like late October. |
| | 72 | <rbray> I know we can have the ISAPI and the Apache mod in by then. |
| | 73 | <rbray> And Fusion should be code complete. |
| | 74 | <pagameba> hi all |
| | 75 | <rbray> Hey Paul. |
| | 76 | <jasonbirch> Cool. Maybe an alpha? :) |
| | 77 | <jasonbirch> It would be nice to get automated builds running. Maybe I'll bug Mat again at the conference and see if his head is still exploding. |
| | 78 | <rbray> Paul: We decided to have a F2F at FOSS on Monday night (I am buying). |
| | 79 | <pagameba> Hi Bob |
| | 80 | <pagameba> F2F? |
| | 81 | <jasonbirch> face to face :) |
| | 82 | <pagameba> ah |
| | 83 | * pagameba catches up |
| | 84 | <Andy_Morsell> Don't all of the current RFC's (including the FastCGI one) target 1.3? Those should be updated if there's not going to be another point release. |
| | 85 | <jasonbirch> Yes... |
| | 86 | <rbray> Yes, we'll do that. |
| | 87 | <jasonbirch> Last meeting I think we decided on 2.0 instead of 1.3 |
| | 88 | <rbray> Yep |
| | 89 | <jasonbirch> I'm guessing that none of the defects (including those applied to 1.2) are critical enough for a 1.2.1? |
| | 90 | <rbray> I like the alpha idea. Especially with all the new stuff. |
| | 91 | <HarisK> Is ISAPi extension and Apache mod already in progress ? |
| | 92 | <jasonbirch> Yes. |
| | 93 | <jasonbirch> What' you're not subscribed to the commits list? :) |
| | 94 | <rbray> We may need a 1.2.1 if we get some high priority bugs. |
| | 95 | <HarisK> I missed that, I would check it |
| | 96 | <rbray> But i would like to reserve judgement on 1.2.1 until a reason comes up. |
| | 97 | <jasonbirch> HarisK: http://lists.osgeo.org/mailman/listinfo/mapguide-commits |
| | 98 | <jasonbirch> Also for fdo |
| | 99 | <jasonbirch> in http://lists.osgeo.org/mailman/listinfo/fdo-commits |
| | 100 | <HarisK> was there rfc about ISAPI extension ? |
| | 101 | <pagameba> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc22 |
| | 102 | <pagameba> ? |
| | 103 | <pagameba> HarisK, you voted +1 :) |
| | 104 | <jasonbirch> rbray: OK. I saw a note on the users list from a person that couldn't deploy 1.2 because of an outstanding defect. |
| | 105 | <jasonbirch> lol |
| | 106 | <HarisK> yes, sorry I forgot about that |
| | 107 | <rbray> I did not see that e-mail. Guess we should think about a 1.2.1 then. |
| | 108 | <HarisK> It looks like I developed second extension :) |
| | 109 | * pagameba wonders if we should update the status of some RFCs, or add another column to indicate if it was implemented and in which version |
| | 110 | <rbray> HarisK: Can we merge them? |
| | 111 | <jasonbirch> That would be cool... |
| | 112 | <jasonbirch> to both pagameba and rbray |
| | 113 | <HarisK> I need to look how is implemented |
| | 114 | <HarisK> I would certainly like to |
| | 115 | <rbray> Paul: Sounds like you have volunteered to update the RFC page :) |
| | 116 | <pagameba> argh |
| | 117 | <HarisK> so it is in svn now ? |
| | 118 | <rbray> Yes I believe so. |
| | 119 | <jasonbirch> http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/ApacheAgent |
| | 120 | <HarisK> thanks, sorry for interuptions |
| | 121 | <jasonbirch> http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/ApacheAgent |
| | 122 | <jasonbirch> doh: http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/IsapiAgent |
| | 123 | <jasonbirch> Huh. Wonder if we could get that REST stuff into 2.0 :) |
| | 124 | <rbray> Depends when it will be done and when we want to release. |
| | 125 | <HarisK> I now remebber looking into this code |
| | 126 | <HarisK> basically what I diid supoprts all of that + http-live connection + working threads pool + json |
| | 127 | <HarisK> anyhow, it is compatible |
| | 128 | <jasonbirch> Are you sure that live connections is a good idea? |
| | 129 | <CIA-25> MapGuide: stevedang * r1974 /trunk/MgDev/Oem/dbxml-2.3.10/ (15063 files in 887 dirs): |
| | 130 | <CIA-25> MapGuide: MapGuide RFC 23: Berkeley DB XML 2.3 Upgrade. |
| | 131 | <CIA-25> MapGuide: - Check in source code. |
| | 132 | <rbray> yes the DBXML upgrade is also part of 2.0. |
| | 133 | <jasonbirch> I'm thinking about scale rather than individual user responsiveness. |
| | 134 | <jasonbirch> Heh :) |
| | 135 | <jasonbirch> CIA knows when to pipe up :) |
| | 136 | * pagameba has updated http://trac.osgeo.org/mapguide/wiki/MapGuideRfcs |
| | 137 | <pagameba> RFC 20 is out of date |
| | 138 | <jasonbirch> IS Rfc20 dead in the water because of the requirement to re-associate a session with a different user? |
| | 139 | <rbray> Not sure. I'll have to check on it here. |
| | 140 | <rbray> This is also in: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc26 |
| | 141 | <pagameba> I like the concept but embedding the user id in the session won't work |
| | 142 | <jasonbirch> No |
| | 143 | <jasonbirch> You need a way of polling the session for its userid. |
| | 144 | <rbray> Assuming 26 gets approved. |
| | 145 | <jasonbirch> Didn't we vote on that already? |
| | 146 | <rbray> If so the page is out of date. |
| | 147 | <pagameba> Bob asked earlier if there was a target date for 2.0? |
| | 148 | <jasonbirch> Yes he did |
| | 149 | <pagameba> I think mid/end October for a alpha/beta would be good |
| | 150 | <pagameba> but I don't know what we can complete by then |
| | 151 | <pagameba> by we, I mean ADSK :) |
| | 152 | <rbray> I am leaning toward Alpha at the end of Oct. |
| | 153 | <jasonbirch> I dropped the ball on 26; I started the motion but did not say it passed or update the page. |
| | 154 | <rbray> I'll talk to Trevor about RFC 20. It is interesting. |
| | 155 | <rbray> And the outlined approach is not good. |
| | 156 | <rbray> So Harris, when do you think the REST stuff might be completed? |
| | 157 | <HarisK> whatever I will say I will lie |
| | 158 | <rbray> Ha |
| | 159 | <HarisK> my plans are for end of year |
| | 160 | <HarisK> that will included FDO Rest as well |
| | 161 | <rbray> OK, then maybe that is a 2.1 feature unless it magically gets done before the first RC |
| | 162 | <pagameba> HarisK: have you looked at FeatureServer? |
| | 163 | <rbray> FDO rest? |
| | 164 | <HarisK> yes but not very much ( python ) |
| | 165 | <pagameba> http://featureserver.org/ |
| | 166 | <HarisK> yes I have protoype of FDO rest also |
| | 167 | <jasonbirch> FeatureServer follows a great model. |
| | 168 | <rbray> Yes. Wouldnt that be exposign FeatureService and hence FDO, but through MG? |
| | 169 | <jasonbirch> I've been meaning to help Crschmidt hack FDO support into it. |
| | 170 | <pagameba> if you do FDO rest along the same lines then the same clients can use it |
| | 171 | <HarisK> I kind of like to put fdo web service on it own |
| | 172 | <jasonbirch> Might get together at foss4g. |
| | 173 | <rbray> Then you lose some stuff, like connection pooling, and other things MG adds. |
| | 174 | <rbray> Joins. |
| | 175 | <HarisK> idea is to have also fdo rest fdo provider :) |
| | 176 | <rbray> Extended expression support, and more. |
| | 177 | <HarisK> yes, my opinion is that part should go from mapGuide |
| | 178 | <HarisK> to FDO middle tier |
| | 179 | <rbray> I guess I am confused. We need a whiteboard. |
| | 180 | <HarisK> so any client can benefit from things like FDO caching |
| | 181 | <jasonbirch> Oh, move FeatureService outside of MapGuide... |
| | 182 | <HarisK> caching , logging, spatial security to FDO middle tier |
| | 183 | <rbray> Hmm, Feature Service depends on Resource Servive. |
| | 184 | <rbray> HarisK: MG does a bunch of that. Why pull it out? |
| | 185 | <rbray> Why not extend what is there? |
| | 186 | <jasonbirch> So you don't have to install MapGuide to expose your features. |
| | 187 | <HarisK> I think fdo HAVE A FEATURE NOT JUST WITH mAPgUIDE |
| | 188 | <jasonbirch> Oops :) |
| | 189 | <HarisK> sorry my caps lock |
| | 190 | <HarisK> what I mean is that fdo can be used with other applications as well |
| | 191 | <HarisK> and have caching, joins, secutiy... |
| | 192 | <rbray> Difference of opinion here I think. You can use Feature Service without using any other features of MG |
| | 193 | <HarisK> I suppose for example that Autodesk MAp and Mapguide both imlements it's own fdo connecton caching |
| | 194 | <rbray> And you get the benefits of pooling, joins, etc. |
| | 195 | <rbray> While reusing the server infrastructure. |
| | 196 | <jasonbirch> I'm not sure that I would want an entire MapGuide install on my feature serving servers... |
| | 197 | <rbray> This sounds like a good discussion for the F2F. I am not against it, jus trying to understand. |
| | 198 | <HarisK> I see FDO as spatial data service and MapGuide as stylization service |
| | 199 | <jasonbirch> Ohhh. GIS service too HarisK |
| | 200 | <rbray> OK, I see things differently. |
| | 201 | <rbray> For me, MapGuide is a geospatial server that exposes a number of different services. |
| | 202 | <HarisK> this are just my preliminary thoughts, lot of work to be done to get some protoypes and feeling how it works |
| | 203 | <rbray> including spatial data, stylization, and content management. |
| | 204 | <rbray> Let's continue this at the F2F. |
| | 205 | <jasonbirch> Sounds good... |
| | 206 | <HarisK> ok |
| | 207 | <rbray> I'll try and get the Roadmap page in Trac updated. |
| | 208 | <rbray> Other topics for today? |
| | 209 | <rbray> Silence, means we are done. When should we meet again? At FOSS? |
| | 210 | <jasonbirch> Not from me. I would like to ensure that we can meet like this on a regular basis though... if only to talk. |
| | 211 | <jasonbirch> Yes, FOSS next. |
| | 212 | <rbray> ok, let's adjourn then. |
| | 213 | <rbray> Thanks everyone! |
| | 214 | <HarisK> thanks |
| | 215 | }}} |
