Project Steering Committee - Home

Meeting Info

The eleventh meeting of the MapGuide PSC will take place Thursday August 2nd at 18:00 UTC (1:00 PM ET / 11:00 AM MT / 10:00 AM PT).

Meeting Chair: Bob Bray

Universal Time: ​http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=2&year=2007&hour=11&min=0&sec=0&p1=55

Location: The meeting will be held on IRC at ​#mapguide

Agenda

• MGOS 1.2.0
• MGOS 1.3.0/2.0
• Fusion RFC

Actions

• MGOS 1.2.0 to be released SAP, need to update FDO to 3.2.3 to incorporate the latest GDAL build. Tom (release manager) to make this happen when he returns from vacation.
• Next version of MGOS (with Fusion) to be released as MGOS 2.0. Target code complete is end of September / early October with a first beta targeted for sometime in October.
• Fusion to be integrated, Paul will complete the RFC which needs to detail the integration plan. A full description of Fusion is not required in the RFC as the preview release provides the required information.
• Roadmap to be updated for MGOS 2.0. Bob and/or Tom action.
• Need to test/post the list requesting committers include either ticket # or a link to the RFC in the commit message.

Transcript

jasonbirch>	Let's get going :)
	<rbray>	ok, then lets start.
	<rbray>	First topic is MGOS 1.2.0 RC2 promotion to MGOS 1.2.0 release.
	<rbray>	I personally think we have held this up long enough and need to get it out the door.
	<rbray>	Andy are you still seeing stability issues?
	<jasonbirch>	Me too. BUt I fuess we'll need a new build of FDO.
	-->|	HarisK (n=chatzill@84-255-254-95.static.dsl.t-2.net) has joined #mapguide
	<HarisK>	Hi
	<pagameba>	In talking to some clients, they are very concerned with the (lack of) stability in 1.2
	<HarisK>	Jason thanks for reminder
	<Andy_Morsell>	Yes, there are still some major stability issues with GDAL (and/or FDO), but I agree, we can't hold it up any longer.
	<rbray>	Hey Harris, just starting to discuss MGOS 1.2 release.
	<pagameba>	hi HarisK
	<rbray>	Paul, can you summarize the issues?
	<pagameba>	their issues may very well be related to GDAL, but I also proposed using the CGI
	<pagameba>	the server crashes every few minutes under any kind of load
	<rbray>	FastCGI is still a significant problem. I know about that.
	<pagameba>	right
	<rbray>	With or without Raster?
	-->|	danmo (n=dmorisse@157-146.svr.royaume.com) has joined #mapguide
	<pagameba>	with raster I think
	<pagameba>	I haven't heard back (they are not very communicative when there are no problems) so I'm hoping that CGI fixed some of their problems
	<rbray>	OK, anything you can do to isolate it would be very helpful.
	<pagameba>	I'll follow up
	<jasonbirch>	I gave Jonathon an earlier build of the raster fixes (before biglock)
	<Andy_Morsell>	I'm also seeing major raster problems with the Autodesk MGE 2008 provider, so the problem may indeed be deeper.
	<jasonbirch>	I'm thinking that the latest raster fixes that FrankW committed should help considerably
	<rbray>	Andy: Can you send a summary of these to me and Tom?
	<rbray>	Andy: The Autodesk MGE 2008 issues that is.
	<jasonbirch>	It's relatively stable for me, but I have only tested with a smaller set of data (20 ECWs, < 100MB each)
	<bdechant>	Can you send them to me also Andy please?
	<Andy_Morsell>	Yes, Tom is already in the loop and Dave Wilson is working on the issue with some of my clients imagery in hand.
	<rbray>	OK, then that is fine.
	<pagameba>	should we release 1.2 rc 3 with the latest changes?
	<jasonbirch>	I'd say just go final with a new fdo/gdal build.
	<pagameba>	and plan to release 1.2 final in a week or so as long as there are no other issues?
	<pagameba>	I'm not entirely comfortable with changing a major part of the stack at the last second without an RC
	<jasonbirch>	?
	<rbray>	New FDO version I believe is what Paul is refering to.
	<pagameba>	right
	<pagameba>	unless the FDO thing is just a bugfix
	<jasonbirch>	The only part that is changing is GDAL, and I believe that it's a bugfix
	<jasonbirch>	Frank added a provider-wide semaphore to work around locking issues
	<pagameba>	in the GDAL provider?
	<rbray>	Yes
	<pagameba>	so why do we need a new build of FDO?
	<rbray>	We dont, just the GDAL Provider
	<jasonbirch>	The GDAL provider was the only part that changed.
	<rbray>	To my knowledge yes
	<jasonbirch>	It would be best if there was a 3.2.3 so that people don't get messed up on versions etc.
	<jasonbirch>	Otherwise they'll download the 3.2.2 (for Linux) and wonder why raster doesn't work.
	<rbray>	Yea, ok I see your point on that.
	<rbray>	Which is back to Pauls requirement for a RC3
	<pagameba>	so we do need to up the rev on FDO for the release
	<pagameba>	?
	<jasonbirch>	Personally, I think so.
	<rbray>	Yes we need to rev FDO.
	<jasonbirch>	FDO needs to rev FDO :)
	<pagameba>	so there would be new, untested code outside of bugfixes from the last RC in the next release
	<jasonbirch>	No there wouldn't (I think)
	<jasonbirch>	I don't think the 3.2.x branch has been touched outside of GDAL
	<rbray>	That is correct
	<pagameba>	where the changes in FDO 3.2.2 to 3.2.3 only in GDAL?
	<rbray>	I think that is true too.
	<pagameba>	and only to fix the raster stability problem?
	<pagameba>	or did other changes happen in FDO as well?
	<rbray>	We will need to check the history to be sure, but yes I think so.
	<rbray>	That is, there are no other changes.
	<pagameba>	ok, if the only changes happened to fix the raster stability then I'm okay with a final release
	<jasonbirch>	Uh, the GDAL stuff also has tileindex in it. Not sure when that was added, if it was before last release or not.
	<jasonbirch>	This has had far more testing than any earlier raster provider release though.
	<jasonbirch>	outside of the MapGuide release cycle.
	<rbray>	Lets just ship the thing!
	<HarisK>	as I remember, there were also changes in raster column name, because of MapGuide hardcoded strings for WMS provider
	<rbray>	After RC2?
	<jasonbirch>	No, that's just in the config file that my app generates.
	<HarisK>	there were two problems, one getting folter at all
	<HarisK>	and than implementing it
	<HarisK>	sorry folter == spatial filter
	<rbray>	Still sounds like a bug fix.
	<HarisK>	yes
	<rbray>	So then if we have a couple of bug fixes I would argue we release 1.2.0.
	<HarisK>	there is hardcoded raster column name in MapGuide and that was workarround for it
	<rbray>	Sounds like there were no major changes.
	<rbray>	The biggest problem I am aware of in 1.2 is FastCGI and we have a workaround for that.
	<jasonbirch>	I'd ship it. Outside of myself and Andy, nobody else saw problems with the raster provider with earlier RCs. I don't think that further RCs will help.
	<HarisK>	+1
	<rbray>	I am hoping to have a mod/isapi extension for testing sooner rather than later.
	<jasonbirch>	I was happy to see some code committed around that :)
	<pagameba>	+1
	<rbray>	Motion: Release MGOS 1.2.0 with the current set of bug fixes next week.
	<pagameba>	+1
	<jasonbirch>	seconded, _1
	<Andy_Morsell>	+1
	<jasonbirch>	That's a +
	<bdechant>	+1
	<HarisK>	+1
	<rbray>	And I am +1
	<rbray>	OK. That will happen when our Release Manager returns from vacation.
	<rbray>	Next week I think.
	<jasonbirch>	I'm guessing that we coordinate with FDO for a 3.2.3 release too?
	<rbray>	Bruce do you know if Tom is back on Monday?
	<rbray>	Yes Tom will do that.
	<HarisK>	release manager on release :)
	<Andy_Morsell>	We need to be prepared that MANY more people are likely to experience problems once this hits the streets. But, it's probably the only good way to get more people to start taxing it.
	<bdechant>	I believe Tom is back Monday
	<rbray>	Yep
	<rbray>	OK, next topic is either Fusion or next release.
	<rbray>	They are somewhat intertwined.
	<rbray>	Paul, do you want to start with the Fusion RFC?
	<pagameba>	sure
	<pagameba>	I started a page in the wiki
	<pagameba>	http://trac.osgeo.org/mapguide/wiki/MapGuideRfc24
	<pagameba>	I'm not entirely sure how to write it up
	<pagameba>	how much detail do we need?
	<rbray>	I think we mainly need the integration strategy documented.
	<pagameba>	ok
	<rbray>	For Fusion we can refer folks to the Demo.
	<rbray>	Preview thingy.
	<pagameba>	right
	<pagameba>	ok
	<jasonbirch>	Has everyone had a chance to look at Fusion?
	<pagameba>	so I'll try to write up something on how it will be integrated
	<jasonbirch>	Has anyone not had a chance to look at Fusion? :)
	<bdechant>	Yes :)
	<HarisK>	yes :)
	<bdechant>	My yes is for looking at it.
	<rbray>	Here is a better question.
	<Andy_Morsell>	I've looked at it, but haven't tried to integrate it with any of my stuff yet. It looks great, though.
	<rbray>	Is everyone in agreement that Fusion should be integrated as part of MGOS?
	<jasonbirch>	+1
	<bdechant>	Absolutely!!!
	<bdechant>	+1
	<pagameba>	+1
	<pagameba>	;)
	<pagameba>	note that it won't replace the ajax viewer at this point
	<HarisK>	instead of existing one or aside ?
	<pagameba>	they will co-exist
	<Andy_Morsell>	+1
	<HarisK>	I got my answear
	<HarisK>	+1
	<pagameba>	the intention being to deprecate the existing viewer in a couple of versions
	<rbray>	Any application written using the current AJAX or DWF Viewer will continue to work.
	<pagameba>	if everything goes well
	<rbray>	right
	<HarisK>	Is it possible to have a document what are differencies ?
	<rbray>	OK, then Paul I think my earlier answer is right. We document the integration strategy in the RFC and point folks to the preview for info on Fusion itself.
	<pagameba>	ok
	<pagameba>	perfect
	<rbray>	HarrisK: Yes I think we'll need something like that.
	<pagameba>	HarisK - everything will be different but it will all be the same, too ;)
	<rbray>	OK so this leads to the next discussion. Should the next release of MGOS with Fusion integrated be 1.3 or 2.0?
	<rbray>	This is a major new feature from my point of view.
	<jasonbirch>	It's a pretty large change, as is the support for JSON
	<rbray>	Along with ISAPI and an Apache Mod.
	<jasonbirch>	It's an API compatibility break too.
	<bdechant>	Because of Fusion and the other changes I think we should call it 2.0
	<jasonbirch>	From a JS perspective)
	<jasonbirch>	I agree Bruce
	<Andy_Morsell>	I agree, that would make sense. Should get some good press releases out of that too that will highlight the Fusion-ness.
	<rbray>	ok, next the timeframe.
	<pagameba>	+1 on 2.0
	<HarisK>	MapGuide will be open to other types of viwer I suppose ?
	<rbray>	Yes
	<rbray>	in many ways Google Earth is a viewer today.
	<rbray>	Lets vote on this. Motion: Next release with Fusion will be 2.0
	<HarisK>	we are using one based on Google Web Toolkit
	<jasonbirch>	Seconded, +1
	<Andy_Morsell>	Seconded, +1
	<pagameba>	+12
	<rbray>	+1
	<pagameba>	+1
	<HarisK>	+1
	<pagameba>	sorry, didn't mean to use all my votes on one thing ;)
	<rbray>	Wow, Paul gets 12 votes now :)
	<bdechant>	+1
	<jasonbirch>	I think that, like fdo, we might want to have a place for contributed code.
	<jasonbirch>	Like Haris' GWT viewer
	<rbray>	Harris, I would like to see a sample of yours at some point...
	<pagameba>	good point
	<jasonbirch>	My dorky little image catalogue script
	<jasonbirch>	etc
	<HarisK>	on FOSS4G :)
	<rbray>	OK :)
	<pagameba>	should fusion be integral to the mapguide svn or can it live its own live outside and be brought in on demand?
	<rbray>	I would argue for integration.
	<pagameba>	ok, I'll include that in the rfc
	<rbray>	Because we plan to replace the existing viewer with Fusion.
	<pagameba>	www/fusion/
	<pagameba>	?
	<pagameba>	I have to go in 5 mins
	<pagameba>	timing of 2.0 is of interest to me
	<rbray>	At some point we will depreciate the existing one is what I meant
	<jasonbirch>	I'd argue for adding fusion to the repository in advance of the RFC.
	<jasonbirch>	Same as we're doing in FDO for the tools.
	<rbray>	OK timing. I would like to shoot for code complete by End of Sept with a Beta in Oct.
	<jasonbirch>	It would be nice if we had something downloadable for foss4g... but I guess that's a bit tight :)
	<rbray>	It would be nice to release something for FOSS4G but that seems highly optimistic
	<rbray>	:)
	<rbray>	Paul since a lot of this is your work, you kind of have to help with scheduling. Is the end of Sept/early oct work for code complete?
	<pagameba>	yes
	<pagameba>	we are almost complete on integrating OpenLayers tiling engine for tiled map support
	<pagameba>	once that is in, there is not a lot left to do
	<jasonbirch>	YEAH BABY!
	<jasonbirch>	(was that out loud? sorry)
	<rbray>	oh yea, now that I gotta see
	<rbray>	Whens the demo?
	<jasonbirch>	Refactoring for the JSON support, I guess Paul?
	<pagameba>	that, ApplicationDefinition, internationalization support and a few widgets
	<pagameba>	ha
	<pagameba>	no demo yet
	<pagameba>	soon though
	<rbray>	OK, so Paul you will finish the RFC, we'll do the JSON RFC.
	<pagameba>	right
	<rbray>	and we'll shoot for a beta in Oct.
	<pagameba>	+1
	<pagameba>	ok, gotta run
	<rbray>	Thanks Paul, see-you later.
	<pagameba>	thanks all
	* jasonbirch	is hating this. Everyone is having coffee out on the deck outside his office. he's jealous.
	|<--	pagameba has left irc.freenode.net ()
	<rbray>	Other topics? That was the end of the set agenda.
	<Andy_Morsell>	Jason: you have a deck, outside your office? I'm jealous.
	<rbray>	Why are you not out there with your laptop?
	<jasonbirch>	Only one screen on a laptop.
	<jasonbirch>	I prefer the tan I get from my three monitors :)
	<rbray>	Ah, a true geek.
	<jasonbirch>	I had some comments on commit policy
	<jasonbirch>	but have since reconsidered
	<jasonbirch>	post-commit hooks would be a pain in the butt
	<rbray>	Yea I decided the same thing.
	<rbray>	FYI - I will work on updating the RoadMap with our decisions.
	<jasonbirch>	I would be happy to see a RFC URL or #123 in the comments though
	<jasonbirch>	Or some way of hacking trac so you could just say MapGuideRfc13 and have it link.
	<jasonbirch>	Right now, it ignores numbers in camelcase
	<rbray>	I think you can put a trac link in there and it will work.
	<rbray>	wiki:MapGuideRfc13 for example.
	<jasonbirch>	Oh...
	<jasonbirch>	That would be cool.
	<rbray>	But I have not tried it.
	<rbray>	We can probably test that and send out an e-mail to internals requesting that the ticket# or RFC be referred to in the submissions.
	<rbray>	I'll take that as an action and assign it to the guy who is not here :)
	<jasonbirch>	Just imagine what was on my plate when I got back from three weeks :)
	<rbray>	ok, anything else to discuss?
	<jasonbirch>	just a minute...
	<rbray>	I am slowly making more website changes. The two download pages have now been merged. Will work on the docs pages next.
	<jasonbirch>	Cool. Are you starting to get time to breathe too?
	<rbray>	No, but you know...
	<JamesCard>	Might I submit a request?
	<jasonbirch>	Go ahead :)
	<rbray>	JamesCard: You could
	<JamesCard>	I'm still agonizing through my first install of MGOS on Linux. The default install should probably include PHP support for unixODBC.
	<jasonbirch>	JamesCard, put in an enhancement request for that. Oh, that brings up a question I had forgotten about. Build system.
	<rbray>	Can you submit a ticket on that. That should just be a change to the PHP config.
	<JamesCard>	OK, will do.
	<rbray>	What build system?
	<rbray>	:)
	<jasonbirch>	Did anyone have a chance to look at cmake?
	<rbray>	Not yet.
	<jasonbirch>	I personally think that it would make life a _lot_ easier for us.
	<jasonbirch>	Apparently KDE and MySQL are using it.
	<rbray>	Know of any other open source projects that do?
	<jasonbirch>	And we have a volunteer to help :)
	<rbray>	Well now that is worth a lot.
	<jasonbirch>	I think there were a couple but it's been a while since I looked.
	<rbray>	Let me get some folks here (at Autodesk) on the buidl team to look at it and we'll report back.
	<rbray>	OK folks, I have to run.
	<rbray>	Shall we adjourn?
	<bdechant>	Sure
	<rbray>	Ok, thanks everyone.
	<Andy_Morsell>	Good meeting - bye all.
	<bdechant>	ttyl
	<jasonbirch>	bye all.
	<HarisK>	bye