#MAPSERVER Log: 2016-10-13

00:37:11gener1c:ok so i have managed to compile mapserv with ruby python php and fastcgi support
00:37:21gener1c:finished the whole tutorial
00:37:40gener1c:but still cant find a good explenation on how mapscript connects to my httpd
00:38:38gener1c:Hello, kind reader. I am Tut, thank you for downloading me. I am sorry, but I am just a technical manual so I cannot answer any questions. The maintainer, a handsome, very nice and lazy guy according to what I saw from the other side of the screen,
00:38:42gener1c:ok
00:38:46gener1c:brb
00:38:54gener1c:need to read this
13:33:19-mapserver-bot-:[docs] geographika opened pull request #158: Set the theme explicitly so the relbar displays (branch-7-0...patch-1) https://git.io/vPVKH
13:34:14-mapserver-bot-:[docs] geographika closed pull request #158: Set the theme explicitly so the relbar displays (branch-7-0...patch-1) https://git.io/vPVKH
13:39:25-mapserver-bot-:[docs] geographika reopened pull request #158: Set the theme explicitly so the relbar displays (branch-7-0...patch-1) https://git.io/vPVKH
14:37:51mapslob:Testing...
14:44:57-mapserver-bot-:[docs] jmckenna pushed 2 new commits to branch-7-0: https://git.io/vPV7X
14:44:57-mapserver-bot-:docs/branch-7-0 50c9810 Seth G: Set the theme explicitly so the relbar displays...
14:44:57-mapserver-bot-:docs/branch-7-0 24f3270 Jeff McKenna: Merge pull request #158 from geographika/patch-1...
14:49:02-travis-ci-:mapserver/docs#353 (branch-7-0 - 24f3270 : Jeff McKenna): The build passed.
14:49:02-travis-ci-:Change view : https://github.com/mapserver/docs/compare/e43da00f78b1...24f3270ee4e6
14:49:02-travis-ci-:Build details : https://travis-ci.org/mapserver/docs/builds/167378663
15:00:05mdsmithf:good <insert time of day where you are> everyone
15:00:20jmckenna:Hi all. let us begin the PSC meeting :)
15:00:26jmckenna:agenda: https://github.com/mapserver/mapserver/wiki/PSC-Meeting-2016-10-13
15:00:27sigabrt:Title: PSC Meeting 2016 10 13 · mapserver/mapserver Wiki · GitHub (at github.com)
15:00:46jmckenna:and thank you for coming everyone!
15:01:14mapslob:guten Morgen
15:01:20jmckenna:please say hello now if you are a PSC member or even a user/dev anyone who is interested in attending now
15:01:29JukkaR:hello
15:01:30tbonfort:good afternoon :)
15:01:31tomkralidis:hello
15:01:32jmckenna:(I'll take minutes)
15:01:43EvenR:hello
15:01:47* dmorissette here for the meeting, but also multitasking in another teleconf meeting so my attention will be limited
15:02:01mdsmithf:hi everyone
15:02:05StephanMeissl:hi there
15:02:59woodbri:hi everyone
15:03:02Assefa:Hi all
15:03:15jmckenna:mapslob: sorry i don't know your full name, by your IRC nick
15:03:24jmckenna:steveL?
15:03:29mapslob:Steve L.
15:03:36jmckenna:ah yes! too long, ha.
15:03:39jmckenna:welcome everyone
15:03:58mapslob:thanks for organizing!
15:03:58mdsmithf:thanks for putting this together jmckenna
15:04:11jmckenna:roughly 8 PSC members here, out of 14
15:04:30jmckenna:mdsmithf: no problem
15:04:57jmckenna:i figure we can use the hour to discuss the project. agenda but nothing firm. let's start at the PSC
15:05:12jmckenna:item: PSC members, refresh (any additions etc)
15:05:31jmckenna:"PSC member status" http://mapserver.org/psc.html
15:05:32sigabrt:Title: Project Steering Committee MapServer 7.0.2 documentation (at mapserver.org)
15:05:36tomkralidis:nice page :)
15:05:38jmckenna:do we need to make any changes?
15:05:40jmckenna::D
15:06:19mapslob:do we want to consider a new chair - I've been negligent in my responsibilities
15:07:30mdsmithf:I'm fine with @mapslob continuing as chair
15:07:42woodbri:maybe a better Q is do you want to step down?
15:07:49woodbri::)
15:08:33mapslob:i've thought about that for some time now, if the project would be better off with some new leadership
15:09:41* nhv == Norman Vine
15:10:02jmckenna:ok, i that is how you feel. We sure all can respect that
15:10:13tbonfort:+1 for @mapslob to remain chair if he is willing to continue
15:10:27woodbri:+1
15:10:31jmckenna:I'm +1 to follow how mapslob feels
15:10:38dmorissette:+1 here as well. Even if not very active, he still is the spiritual leader
15:11:00jmckenna:great leader indeed
15:11:08mdsmithf:concur
15:11:13woodbri:agreed
15:11:22tomkralidis:+1/agree
15:11:30Assefa:+1
15:11:39StephanMeissl:+1
15:11:49JukkaR:+1
15:12:06mapslob:how about we table it and folks can think about it... IMHO the chair should be more active.
15:13:12jmckenna:activity is important, by the PSC, i am not sure that falls on chair's shoulders. this PSC meeting is great, and we will continue this momentum - i did not think we need chair refresh.
15:13:28jmckenna:team effort
15:13:42mapslob:thanks jeff...
15:14:07jmckenna:ok good. great though to discuss all that.
15:14:14jmckenna:(mark as fixed. ha)
15:14:39jmckenna:I meant it was great to discuss
15:14:48tbonfort:@jmckenna what was the bug?
15:14:55mapslob:rest of PSC membership looks ok, Perry is the only really inactive member
15:15:29colivier_:hop
15:15:36jmckenna:perry does vote, and still tries to contribute
15:16:53jmckenna:i was thinking of either if we need to add anyone, any power contributors or users, or if any here had internal thoughts of 'retiring' ha. but it sounds like we are all 'in', which is great! :)
15:17:41jmckenna:tbonfort: sorry that was my joke, for ending discussion :)
15:18:17jmckenna:let us close the PSC discussion, it seems like we are ok on that
15:18:22mapslob:+1
15:19:21jmckenna:next item: PSC activity. I'd like to hold this meeting once a month from now on. Just one hour here. Is that ok? obviously we all cannot attend every meeting, which is fine
15:19:35tomkralidis:1x/month is fine with me.
15:19:37mapslob:meeting frequency? i'd vote for monthly and bi-weekly during a release cycle
15:19:44mdsmithf:works for me
15:20:13JukkaR:+1
15:20:35StephanMeissl:+1
15:20:41dmorissette:no strong opinion here. having a predefined time window is great for planning, but then if there is too little to discuss then attendance will be low making the meeting less usaful
15:20:46woodbri:+1, I'm good with any frequency that fits our needs
15:21:04tbonfort:+0 . no need to meet if there is no agenda to discuss
15:21:46jmckenna:ok, let us try. let us see
15:22:48jmckenna:next item: big topic, Release plans (schedule, 7.2 release).
15:23:09jmckenna:i'd like to document a release cycle.
15:23:15dmorissette:Hopefully formal decisions will still be made on the mailing list and not in the meetings… similar to the board meeting decisions being reflected on the mailing list, otherwise some important decisions could be missed by lots of people if we end up with low-attendance monthly meetings
15:24:32dmorissette:by "document a release cycle", do you mean amendment to http://mapserver.org/development/rfc/ms-rfc-34.html ?
15:24:33sigabrt:Title: MS RFC 34: MapServer Release Manager and Release Process MapServer 7.0.2 documentation (at mapserver.org)
15:25:05dmorissette:The RFC already suggests: "MapServer uses a time-based release cycle, trying to aim for one release every 6 months."
15:25:09jmckenna:i think this push is about, getting momentum for the project etc, i'm more interested in that, than in the moment 'process', as daniel mentioned. i think those interested will find time for the project. those not, likely won't try to attend meetings.
15:26:16jmckenna:by release cycle, i am referring to actually creating a release cycle that we can follow
15:26:29jmckenna:that is known to users and developers
15:27:04woodbri:Doesn't that imply that we have some bigger long range goals that we need to achieve?
15:27:07jmckenna:less about a RFC, more about the current PSC agreeing on the timelines
15:27:44woodbri:like a roadmap
15:27:50jmckenna:I think we will get nowhere here if we try to build momentum, but point to existing process docs
15:27:55jmckenna:let's get it happening
15:28:37dmorissette:point taken
15:29:26jmckenna:if 'let's get it happening' is stuck on funding, well that is why we are here to talk also :)
15:29:45mapslob:does look like RFC 34 could use a refresh, if nothing else to reference git, etc...
15:31:15mapslob:maybe we should focus on what would justify a 7.2 release
15:31:51jmckenna:sure, great
15:32:14jmckenna:7.2 release plan wiki: https://github.com/mapserver/mapserver/wiki/MapServer-7.2-Release-Plan
15:32:15sigabrt:Title: MapServer 7.2 Release Plan · mapserver/mapserver Wiki · GitHub (at github.com)
15:33:10mapslob:I was thinking vector tiles would be a centerpiece, I'm not aware of any other major initiatives
15:33:17dmorissette:BTW, the way to initiate the release process and agree on dates used to be to (1) draft a release plan at https://github.com/mapserver/mapserver/wiki/ReleasePlans, then (2) propose it for discussion on the -dev list, and (3) get the PSC to vote on it. IMHO we just need a champion to initiate that process. I did it several times when releases were important to me, but unfortunately I do not have the time for that now
15:33:18sigabrt:Title: Home · mapserver/mapserver Wiki · GitHub (at github.com)
15:34:09jmckenna:yes, we will edit release plan for 7.2, if we decide here on changes, and then propose our schedule to -dev, exactly
15:34:30jmckenna:i have no problem being the release manager for 7.2
15:34:47mapslob:PHP 7 support could be another chunk of work
15:35:01jmckenna:yes indeed
15:36:07jmckenna:(see other agenda items in meeting agenda, lots of great stuff)
15:36:36jmckenna:include OS/X installer update (and 'certified' installer)
15:36:47jmckenna:lots of possible 7.2 release targets
15:37:08tbonfort:Are we not putting the cart before the horse here? Once php 7 support, vector tiles, insert_your_feature_here, are ready, then we can start talking about release plans?
15:37:09jmckenna:(background on 'certified installer' see http://blog.geoserver.org/2016/10/12/geoserver-2-9-2-released/)
15:37:10sigabrt:Title: GeoServer 2.9.2 Released GeoServer (at blog.geoserver.org)
15:37:53jmckenna:tbonfort: maybe, or talking and planning and finding what we need to get the release done is also good
15:37:56mapslob:tbonfort, yes... Really need to get the target list decided on.
15:38:48mapslob:can't talk timing or anything like that until those elements are defined and close to ready.
15:38:56jmckenna:if all we get out of this PSC meeting is a list of items, that is excellent.
15:39:54dmorissette:we don't necessarily need to agree on the list beforehand if we do a time-based release… we just release what's there at the agreed date. Doing a feature-based release without champions for some of the features will result in a 3 year release cycle
15:40:33jmckenna:dmorissette: well said. if we can agree on timeline, i will push 7.2 release as manager, and get things moving on a regular basis
15:40:39dmorissette:+1
15:40:53tomkralidis:I guess the other factor is drivers for features (funding)
15:41:17mapslob:we need some inkling of major elements though to justify major or minor release
15:41:54JukkaR:For a time based schedule there should be sort of continuous flow of new features and bug fixes at least if if releases are as frequent as in Geoserver https://github.com/geoserver/geoserver/wiki/Release-Schedule
15:41:55sigabrt:Title: Release Schedule · geoserver/geoserver Wiki · GitHub (at github.com)
15:42:17dmorissette:we should still document the list of features in the release plan, but this list is simply the list of features that are done or potentially done, not the result of a brainstorming looking for new ideas to make up a 7.2 … if it's only 3 or 4 key enhancements then so be it
15:42:37mapslob:personally for 7.2 I was targeting multi-line comments and expression handling improvements
15:43:05mdsmithf:oooh, multiline comment +1
15:43:31jmckenna:we could propose a date for 7.2 and vote here (I think we have 12 out of 14 PSC members here now)
15:44:05JukkaR:making a release proves that project is alive - what do we have about ready to be pushed out with 7.2?
15:44:08jmckenna:multiline comments wow!
15:44:40dmorissette:I'd rather agree on a plan here and still have the formal discussion/vote on the list … some power users or contributors may have meaningful contributions to any decision (not just this one)
15:44:41jmckenna:JukkaR: yes this whole meeting is about project 'alive'-ness, let us get things moving
15:44:48mapslob:no, vector tiles = wow, multi-line comments = what took so damn long
15:45:11EvenR:JukkaR: I think jpeg-png output format is in master only
15:45:31jmckenna:dmorissette: let us talk of timeline here. we are all here, we did it, we took time to be here, no need to wait to move to mailing list.
15:46:11jmckenna:point is, talk :)
15:46:15jmckenna:activity
15:46:58JukkaR:so, is vector tiles ready?
15:47:45dmorissette:here is an idea: to determine time, we'd need t know which devs have some code in the pipeline expected to be done in the next 1-2 months and how much time then need before feature freeze… anything beyond 1-2 months from now whold go to 7.4… then we can use that info to set a feature freeze in the next 1-2 months and the rest of the dates automatically follow from that
15:48:36tomkralidis:for planning, can we use GitHub and milestones as an option to help track progress? We can also use the new GitHub "Project option", or tie MapServer's GitHub issues to waffle.io and apply some stages
15:48:46dmorissette:or the other way around: let's propose an arbitrary feature freeze on Nov. 30 and see which devs find that this is too early and request for more time
15:49:08gener1c:hey
15:49:48gener1c:why are all the ifdefs comparing PY_VERSION_HEX to 0x03000000 ?
15:49:54gener1c:and not 0x03
15:49:58jmckenna:JukkaR: i'm planning on investing more on PHP 7 support
15:50:41gener1c:in the wrapper
15:50:47gener1c:mapscript
15:51:12tbonfort:nov 30 will be too early for vector tiles (I'll be off on vacation most of the time up to there)
15:51:28jmckenna:and may tackle the osx issues. seems that is a huge whole now. i'll ping William/KingKaos and work with him
15:52:08mapslob:tbonfort - since that's a key feature is there a date that makes sense
15:53:03mapslob:not to put you on the spot... ;-)
15:53:33dmorissette:I thought vector tiles were blocked by lack of funding … I guess we have the same issue for PHP 7 as well
15:54:03jmckenna:yes funding blocks a lot
15:54:09tbonfort:I should be more pro-active wrt to funding that feature to make it happen, but my timetable is rather full with other stuff right now
15:54:14jmckenna:i did add project funding as agenda item
15:54:19dmorissette:can't speak for tbonfort and jmckenna, but if it was me, I'd wait for funding before I could commit …
15:54:39gener1c:how do i set the PY_VERSION_HEX
15:54:45gener1c::|
15:54:50gener1c:cant find the assignment
15:55:08JukkaR:just png-jpeg output feels a bit lean for marketing a new version...
15:55:32EvenR:JukkaR: I agree. Was just mentionning what I know to be master only
15:55:57tbonfort:I've updated the wiki page with 2 other features in master
15:56:05mapslob:JukkaR, agreed. Maybe with PHP 7 but not by itself.
15:58:14dmorissette:Does this mean release is blocked by funding and we need to discuss funding now?
15:58:56jmckenna:i think release proceeds, i was not funded for any of my time recently
15:59:10jmckenna:but discussing funding here is great
15:59:46tbonfort:vector tiles could go in as an "unfinished" feature right now. finishing it would drive incentive for future releases :)
16:00:29gener1c:nope cant hit that 0x03 condition
16:00:41gener1c:keeps on compiling 2.7
16:00:51JukkaR:7.0.2 was just released which was pretty good for organizations like us who can only update to released versions. Without new cool features we do not need 7.2 so soon.
16:01:08jmckenna:JukkaR: thanks! great to hear it was helpful
16:01:31jmckenna:my plan is to keep that momentum going
16:02:06mapslob:kinda need vt or php7 then
16:03:18dmorissette:I don't think any individual should be expected to produce releases or features for free. However I also don't think the
16:03:40dmorissette:I also don't think the PSC can/should be involved directly in managing funding of features
16:03:50jmckenna:one hour mark of meeting. seems we are stuck on process etc. disappointing. for sure i guess i am committed to get things moving, takeaway from meeting is things will be happening. Team work.
16:04:16dmorissette:So my conclusion is that private entities around the table need to lead the funding efforts… i.e. seek funding as private contracts… the way business works
16:04:57mapslob:yup, it just means that a release will be dependent on the presence of certain features and will have to wait until they happen or others come along.
16:05:56jmckenna:before we start losing people in the meeting, let us decide on next PSC meeting: 17 Nov? http://www.timeanddate.com/worldclock/fixedtime.html?year=2016&month=11&day=17&hour=15&min=0&sec=0%2016.00UTC
16:05:57sigabrt:Title: Event Time Announcer (at www.timeanddate.com)
16:06:34jmckenna:if "PSC" meeting is not welcomed for some, please think of it was a "Project Meeting" instead. users, devs, PSC, everyone.
16:06:34dmorissette:worksforme
16:06:46tbonfort:+1 dmorissette. we need to get things done, not just talk about them
16:07:23StephanMeissl:I can't make the 17 but I didn't contribute too much anyway
16:07:56mdsmithf:works for me also
16:07:59* tbonfort can't make it till end of november
16:08:20* dmorissette needs to move to Europe to have more vacation :)
16:08:34* mdsmithf thinks so also
16:08:37woodbri:worksforme
16:09:01mapslob:works for too
16:09:21mdsmithf:1 hour earlier is better for me but this time works also if good for everyone
16:09:29JukkaR:ok for me
16:09:43StephanMeissl:not everyone in Europe has that much holidays ;)
16:10:09dmorissette:mdsmithf: The Nov 17 proposed time is 10am EST … which is 1 hour earlier than today.
16:10:15mdsmithf:But since it is Europe, everyone will just move to those places
16:10:26mdsmithf:dmorissette: that works for me very well
16:10:52mdsmithf:did we want to touch on Code Sprint 2017?
16:10:57gener1c:arg
16:11:34tomkralidis:+1 to discuss sprint
16:11:41tbonfort:+1
16:11:46dmorissette:mdsmithf: sure. FYI I've been talking to Steve Lehr offline about the potential for dong it in Daytona Beach … the hurricanes have slowed down our discussions
16:11:51mapslob:hoping for FL!
16:11:58jmckenna:we should mention the success of the QGIS Grant program - where proposals were submitted for funding for features, documentation, and packaging. The result was about 10k for packaging, 10k documentation, 20k features (on this round of grants). Imagine that for MapServer, or, imagine how we could someday get there
16:12:14tomkralidis:what timeline for sprint in DAB?
16:12:32jmckenna:sorry, sprint yes (I had that on agend too)
16:12:41jmckenna:ignore my comment
16:13:11dmorissette:tomkralidis: at this point my discussions with Steve Lehr are more about seeing if he has access to a potential venue with Internet and everything we need… a reality check before we can come up with a serious proposal for DAB since Steve may not know all the implications/requirements for a sprint
16:13:33tomkralidis:dmorissette: ah, ok.
16:13:44dmorissette:i.e. I'm trying to help him out and see if DAB is workable… if it works out then we'll share a plan
16:13:46mdsmithf:oher options are? TO? MN?
16:13:58mdsmithf:other
16:14:10dmorissette:and Jody proposed victoria
16:14:32mapslob:MN could be an option but I haven't sensed much interest from a local organizing group
16:14:34mdsmithf:victoria is nice but many hops for lots of people
16:14:34tomkralidis:TO is an option, but I gladly bow to DAB and leave TO for another time
16:14:42gener1c:i cant find anywhere in the wiki what cmake flag i need to use to choose the python version
16:14:43tbonfort:dmorissette: how probable is DAB? do we need to be discussing ither options?
16:14:48gener1c:i just see a binary option
16:14:52dmorissette:BTW, I heard rumors of Athens for 2018 when I was at FOSS4G … did I ever mention it?
16:14:53gener1c:with or without
16:15:12mdsmithf:+1 to Athens
16:15:19jmckenna:yes there will be a sprint at FOSS4G Europe in 2017, and talk of Athens in 2018
16:15:23dmorissette:tbonfort: at this point I'd say DAB probability is 50%
16:15:33jmckenna:maybe a sprint sooner in Athens as well
16:16:00gener1c:https://github.com/mapserver/mapserver/blob/master/INSTALL.CMAKE
16:16:01sigabrt:Title: mapserver/INSTALL.CMAKE at master · mapserver/mapserver · GitHub (at github.com)
16:16:25tbonfort:gener1c: cmake -DPYTHON_EXECUTABLE=/path/to/python
16:16:28gener1c:there is a mistake in the INSTALL.CMAKE diescription string
16:16:33gener1c:i already tried that
16:16:36gener1c:didnt work
16:16:46tomkralidis:if DAB doesn't come through I'm open to TO as an option again
16:17:11dmorissette:if anyone is interested in joining the discussions with Steve Lehr for DAB then let me know. I went offline to avoid disturbing the whole tosprint list with back and forth emails, but didn't mean to do it to control anything… just to help steer Steve
16:17:30mapslob:dmorissette - I'd be interested
16:17:36gener1c:tbonfort: directed it to my virtualenv install
16:17:41jmckenna:please include the list in discussions
16:17:52jmckenna:sure if it needs to be private please include me
16:18:19jmckenna:no disturbing and back and forth, we are open! :)
16:18:43tbonfort:gener1c: try with a clean build dir, cmake might be caching stuff
16:18:49gener1c:ok
16:18:53gener1c:cmake clean?
16:18:57tbonfort:i.e. rm -rf it
16:19:03dmorissette:jmckenna: not everyone has the same tolerance to noise on mailing list, so I'm trying to be list-friendly
16:19:25dmorissette:I'll CC jmckenna and mapslob … anyone else?
16:19:45jmckenna:noise? it's a mailing list setup to plan the one Code Sprint?
16:20:49jmckenna:we could setup a new mailing list if you need, let me know
16:21:06StephanMeissl:dmorissette: feel free to add me if I can contribute something valuable
16:21:06dmorissette:we're not planing the code sprint yet. I'm checking with Steve personally to ensure that he knows what he needs to provide to organize a sprint. If we find that he's got everything then we'll move to the list for the real planning. That's how we did it with others that we helped organize sprint in the past
16:21:22dmorissette:StephanMeissl: willdo
16:21:32StephanMeissl:I confirm that that happenee :D
16:21:59* StephanMeissl thinks of some ales somewhere in the states ;)
16:22:20dmorissette:StephanMeissl: I was thinking of you but didn't want to put you on the spot … I did the same with Angelos about Athens too
16:23:02* tbonfort was sure I heard angelos propose Athens on his own :)
16:23:20StephanMeissl::)
16:23:35dmorissette:he did propose it on his own … I just provided advice to help him confirm that he could do it :)
16:24:29tomkralidis:is the thinking for Athens in 2017?
16:24:42dmorissette:no, Athens 2018 … the Europe year
16:24:48StephanMeissl:no, 2018 following the usual cycle
16:24:49jmckenna:no but we are proposing that to him :)
16:26:21tomkralidis:kalxas: ^^
16:26:36jmckenna:haha
16:28:10dmorissette:I gotta leave for lunch now. Sorry and bye to all
16:29:33tbonfort:bye dmorissette
16:30:05StephanMeissl:bye, already at the evening beers here :)
16:31:22woodbri:bye and thanks all
16:32:50kalxas:hi all
16:33:23kalxas:lets say I proposed initially but dmorissette helped spread the idea :)
16:33:32jmckenna:great :)
16:33:51jmckenna:i was planting the 2017 idea, but if you are set on 2018 that is great too
16:34:14kalxas:isn't 2017 the north america year?
16:34:51jmckenna:yes
16:35:39jmckenna:the more the merrier
16:36:51jmckenna:maybe we can do a smaller meetup in 2017 there ha.
16:37:08tomkralidis:jmckenna: thanks much for kickstarting the PSC meeting today. Much appreciated.
16:37:22jmckenna:tomkralidis: thanks! so great to see everyone here
16:37:23tomkralidis:in my circles people always ask why MapServer is so quiet :)
16:37:31jmckenna:12 out of 14 members! really great
16:37:40jmckenna:been too long :)
16:37:46jmckenna:since our last one i mean
16:37:58tomkralidis:"it works that good" doesn't quite cut it :)
16:38:01jmckenna:not quiet anymore! hahaha
16:38:08jmckenna:true true ha
16:38:36jmckenna:i'll send minutes also to users list too, and dev
16:38:46jmckenna:just even visually this is a great thing, as tomkralidis said
16:39:06jmckenna:stability
16:42:50jmckenna:tomkralidis: do you think a poll or something would be useful, to show how MapServer is implemented? the word 'gallery' seems to always fail. Thoughts?
16:43:06jmckenna:hmm
16:46:30tchaddad:maybe gallery is a wrong word, but some examples of live sites, particularly with advanced cartography, would be pretty great
16:46:52tchaddad:could start by assembling a short list from those that have presented at various foss4g
16:46:57tomkralidis:case studies?
16:47:45jmckenna:good thoughts. (gallery seems to fail because it must be maintained)
16:48:01tchaddad:yes - that's better, I was thinking a rotating showcase
16:49:12jmckenna:i can think of the City of Buenos Aires who does great work there, as one case study
16:49:34jmckenna:case study including MapServer specs etc.
16:50:34jmckenna:tchaddad: should we start a wiki page with these ideas?
16:50:57tchaddad:yes. case study is nice because you can specify different kinds of angles: specs, sector (govt, ngo, private), cartography, services
16:52:38tomkralidis:our weather WMS will be operational Jan 2017 which IMHO will be a pretty high profile of delivering real-time mission critical national weather services via MapServer, so I could do a writeup at some point then
16:52:50jmckenna:wow, great
16:53:08jmckenna:i'll hold you to the Jan date! :)
16:53:33tomkralidis:please do!
16:53:53jmckenna:excellent
16:54:29tchaddad:very cool. I imagine a short-form template write up like that might be useful for many groups - a form of advertising for their work if done correctly
16:54:50jmckenna:template is a great idea
16:55:45jmckenna:tomkralidis: is there any public mention of that upcoming weather WMS release yet?
16:56:13jmckenna:just to point to it, to my contacts
16:56:21jmckenna:don't worry if not
16:57:05jmckenna:umm,,,or maybe i saw that mentioned on a mailing list? hmm can't remember ha. maybe i signed up for notices from you. It's a blur ha
17:02:58tomkralidis:jmckenna: we have an outbound announce only mailing list:
17:03:02tomkralidis:http://lists.ec.gc.ca/pipermail/geomet-info/
17:03:04sigabrt:Title: The GeoMet-Info Archives (at lists.ec.gc.ca)
17:03:08tomkralidis:relevant announcements:
17:03:12tomkralidis:http://lists.ec.gc.ca/pipermail/geomet-info/2016-June/thread.html
17:03:13sigabrt:Title: The GeoMet-Info June 2016 Archive by thread (at lists.ec.gc.ca)
17:03:24jmckenna:ah thanks! i was searching and searching. ah yes thanks
17:03:31tomkralidis:http://lists.ec.gc.ca/pipermail/geomet-info/2016-July/thread.html
17:03:32sigabrt:Title: The GeoMet-Info July 2016 Archive by thread (at lists.ec.gc.ca)
17:03:33tomkralidis:np!
17:04:48jmckenna:fancy canada.ca addresses :)
17:07:17jmckenna:(ah I had sent feedback on that beta in July!) hahaha
17:07:20jmckenna::D
17:07:23jmckenna:small world
17:09:22tomkralidis:yup, I fixed the legend issues ;)
17:09:39tomkralidis:should be released next week
17:15:31jmckenna:tomkralidis: wow, cool, I'll share this news internally
17:15:35jmckenna:thanks!
17:25:51jmckenna:tchaddad tomkralidis maybe we 3 can work together on a few use cases.
17:33:24tomkralidis:+1
17:34:16gener1c:ok this is kinda crazy
17:35:22gener1c:i removed the init_mapscript def from the mapscript/python/mapscript_wrap.c and after i run cmake and make , i do nm on the resulting .so and i still see the init_mapscript name
17:48:38jmckenna:tomkralidis: http://pasteboard.co/exXNHFtah.png :D also note the GetCapabilities response in bottom panel)...i'll look and see why it's not displaying the layer abstract (it should fetch the service and layer abstracts)
17:48:39sigabrt:Title: Pasteboard Uploaded Image (at pasteboard.co)
17:48:47jmckenna:legend looks great!
17:49:22jmckenna:i'll look into the abstract issue and report to your feedback link if it is a service issue
17:49:25jmckenna:thanks man!
18:00:47tomkralidis:thanks jmckenna!
18:01:03jmckenna:(layer abstract seems to be there, will examine my code!) :)
18:01:09jmckenna::D
18:06:22tomkralidis:VIOP
18:06:25tomkralidis:*VIP
18:06:32jmckenna:VIP
18:12:11gener1c:ok
18:12:39gener1c:i manually edited all the source code according to this patch https://github.com/mapserver/mapserver/issues/4748
18:12:40sigabrt:Title: Python3 support · Issue #4748 · mapserver/mapserver · GitHub (at github.com)
18:12:56gener1c:ran cmake with -DPYTHON_EXECUTABLE=python3
18:13:04gener1c:fixed all the issues i had along the way
18:13:13gener1c:after that went to the build dir
18:13:36gener1c:edited mapscriptPYTHON_wrap.c so all the >= 0x03 conditions will alwasy be true
18:13:40gener1c:fixed the errors
18:13:42gener1c:compiled
18:13:56gener1c:and nm _mapscript.so still gives me 2.7 names
18:14:18gener1c:and when i run it with python3 i get ImportError: dynamic module does not define init function (PyInit__mapscript)
18:14:33gener1c:which makes sense since the init is still a 2.7 name
18:14:39gener1c:i.e init _mapscript
18:15:07gener1c:should i fork push and show u?
22:58:58-mapserver-bot-:[docs] jmckenna pushed 1 new commit to branch-7-0: https://git.io/vPrs8
22:58:58-mapserver-bot-:docs/branch-7-0 f15de87 Jeff McKenna: test travis build [build_translations]
23:13:21-travis-ci-:mapserver/docs#354 (branch-7-0 - f15de87 : Jeff McKenna): The build passed.
23:13:21-travis-ci-:Change view : https://github.com/mapserver/docs/compare/24f3270ee4e6...f15de877d8a7
23:13:21-travis-ci-:Build details : https://travis-ci.org/mapserver/docs/builds/167503564