2012.10.18 Weekly Check in - atlregional/OpenTripPlanner GitHub Wiki
13:30 <novalis_dt> Hello, everyone
13:31 <mele> hi
13:31 <demory> hey there
13:32 <demory> mele should we wait for Frank / Grant?
13:33 <mele> I think Frank is at something else this morning, I don't think he will be able to make it
13:33 <mele> Grant should be along shortly
13:33 -!- grant_h [d819d1f2@gateway/web/freenode/ip.216.25.209.242] has joined #opentripplanner
13:33 <mele> but we can probably go ahead
13:34 <mele> oh speak of the devil :)
13:34 <grant_h> just in time
13:34 <novalis_dt> I've spent the past week fixing misc bugs and adding features.
13:35 <demory> my update: have an authenticated version of the unified OTP endpoint w/ about 50 metros behind it. also getting ready to migrate the public deployer site to the new workflow, which has been in "test" mode for the last several weeks. And busy w/ the IDEA Analyst proposal
13:38 <novalis_dt> I also wanted to chat with Andrew and mattwigway about the reversing issue.
13:39 <demory> sure.. first, any other "general" updates?
13:39 <abyrd> I'm checking out the quality of Paris biking routes and the first public GTFS feed for Paris (regional rail), working on the IDEA grant with demory, and now merging the classes and methods used in map-tile-analyst with those used in batch-analyst
13:40 <mattwigway> novalis_dt, I actually have to jump off and go to class now
13:41 <mattwigway> I'll be back on around ~4pm ET
13:41 <novalis_dt> mattwigway, ok, chat with you then
13:41 <mattwigway> actually make that 4:30
13:41 <novalis_dt> sure
13:41 <abyrd> which should facilitate using analyst more flexibly via a web API
13:41 -!- mattwigway [[email protected]] has quit [Remote host closed the connection]
13:43 <demory> anything worth mentioning here from SotM?
13:44 <mele> it was awesome
13:44 <mele> that is all
13:44 <demory> good!
13:44 <grant_h> I concur
13:45 <grant_h> you can view all the talks on the osm wiki
13:45 <grant_h> they should be up in the next few days
13:51 <demory> looks like it's trying to read a stylesheet that no longer exists
13:52 <novalis_dt> Weird.
13:52 <demory> that's enunciate-generated, right?
13:52 <novalis_dt> yep
13:52 <novalis_dt> (BTW, I added a link to the slides)
13:52 <demory> thanks
13:53 <abyrd> I imagine this is due to changing the version of enunciate
13:54 <demory> ok. should i ticket it?
13:54 <abyrd> I'll ticket it and take a look at it.
13:54 <demory> ok, thanks
13:55 <demory> alright, anything else?
13:55 <novalis_dt> nope
13:55 <abyrd> one other thing:
13:55 <abyrd> do we have a target date for the 1.0 release?
13:56 <kpw_> abyrd, we should push 1.0 when we launch the api for the app
13:56 <kpw_> what's pending?
13:57 <abyrd> I was going through issues and closed out the old milestones, and was thinking about what should fall under 1.0
13:57 <novalis_dt> There are a bunch of bugs that I would like to squash
13:57 <abyrd> not sure exactly what we want in there, but anyone can move tickets in or out of 1.0
13:58 <demory> so, two larger things i'd love to see in 1.0 are: (1) the leaflet ui, and (2) expanded support for realtime locations
13:58 <abyrd> maybe we should all take a quick look through and triage a bit
13:58 <demory> i can handle (1), but that's at least a week of work, probably
13:59 <mele> and I'm sure Frank will want to talk to you about what that will mean for us
13:59 <mele> re: Leaflet UI
14:00 <demory> yeah, there needs to be some coordination on that. i know the folks in Poland are working on something too
14:00 <demory> for the record, i don't see the openlayers UI as going away, and i think we can have some shared code between the two
14:01 <mele> cool
14:01 <demory> but i do think we need a mobile-friendly ui for the next big release
14:01 <demory> let's chat more next time Frank is on
14:01 <mele> I agree, and I know Frank would like a mobile-friendly UI too, but I don't think he's anywhere close to switching to Leaflet for the main UI
14:01 <mele> yep
14:02 <demory> sure
14:03 <demory> anyway, abyrd, we didn't directly answer your question about a release date
14:03 <demory> kpw_, you have a target date in mind for the api
14:03 <demory> ?
14:03 <abyrd> well, I think no one is absolutely sure, but I thought we should stick a date on the milestone and tag a few important issues
14:04 <demory> abyrd, what do you think about including expanded support for realtime in 1.0 (i.e. supporting GTFS-RT)? how much work is left there?
14:07 <demory> well, i'll throw out a date: how about Nov 30? gives us about a month and a half..
14:07 <abyrd> basic support is just a matter of a) polling rather than streaming the data, which is trivial
14:08 <abyrd> and b) making a module that makes trip updates out of GTFS RT instead of dutch KV8. It will probably pose no problem, I just need a data source to test with.
14:09 <abyrd> I can ask the OpenOV guys to export me some GTFS-RT, I think they already have a converter.
14:09 <abyrd> I'll ticket this as well and put it under 1.0
14:09 <demory> ok, cool
14:10 <demory> btw, I was part of a hackathon team here recently that wrote a dummy GTFS-RT feed for the trains in Atlanta
14:10 <demory> I can expose that if it would be helpful for testing
14:11 <demory> (dummy in the sense that's it's just based on schedules -- there's no real realtime feed available)