USA switched to DST between this meeting and the last. EU won't switch until the end of March.
No plans to change the time of the meeting (i.e: still 17:30 GMT), but it can be changed if anyone is inconvenienced post-DST switches.
Permalinks / client-side routing (URL-routing, not navigation-routing) needs to be fixed as it's currently the way that the client stores state, or something?
HTTPS: need to exclude HTTP-only routing services to avoid "mixed content" warnings.
gravitystorm was looking for some help analysing contribution rates (e.g: ) to see whether there are any lessons we can learn.
The ohloh graphs seem incorrect - but can get the same information from git logs.
17:36:31 <zere> so the floor is wide open: anyone have anything they'd like to discuss?
17:36:55 <RichardF> worth following up anything from the hack weekend?
17:37:35 <zere> yup, thanks pnorman. the 17:30 GMT time won't change unless we decide it should - in other words, we don't correct for anyone's DST automatically.
17:37:55 <zere> but if the "new time" proves a hassle, please feel free to bring up a change of time.
17:39:41 <zere> RichardF: sure - i think you're close to having routing merged? any help you'd like with anything outstanding on that?
17:44:54 <TomH> do all the backends support https, and do we use it when we were loaded over https?
17:47:47 <zere> all the state of the UI now needs to have a permalink?
17:49:47 <zere> i suppose it must be the new Rails way.
17:51:41 <zere> so each backend needs a flag to filter it out when the site is in https.
17:52:03 <zere> so each backend needs a flag to say whether or not to filter it out when the site is in https.
17:52:55 <RichardF> that's doable. does mean anyone who views the site as https will only get Mapquest, but their choice.
17:54:11 <zere> or indulge requests to add special-purpose, or small-scale routing engines, as mentioned on the PR comments.
17:54:56 <zere> as they say, these are "Version 2" features.
17:55:51 <zere> well, whatever. but it's a "perfect is the enemy of good enough" situation.
17:58:58 <RichardF> but, well, it's up to us to what we accept, so we can say "sorry, suspected nightmare, no thanks"
18:02:37 <zere> yup. it should be the same as the tile layer list; people are welcome to propose anything which meets the minimum criteria, but OWG will have to make a final determination of whether it's feasible, worthwhile and adds more value than the problems it creates.
18:03:56 <RichardF> https://github.com/systemed/openstreetmap-website/commit/23ffdadb565be5ccc4ae9fad9647bdf0fa9b8683 "Don't show http-only routers to users on https"
18:06:04 <zere> anyone feel like volunteering to help RichardF with it?
18:13:11 <gravitystorm> So my topic is measuring EWG effectiveness, more or less. But my question is more specific. Has anyone tried measuring stats on our "core" projects e.g. active contributors per month?
18:13:51 <gravitystorm> And as a related question, does anyone have any suggestions for tools that I can use on each git repo to produce useful progress metrics?
18:15:37 <zere> "the number of contributors is spiky"
18:20:51 <pnorman> there's probably something out there - and isn't ohloh open to some degree?
18:21:33 <zere> well, if it's just number of unique contributors per month, then that's trivially easy to extract from `git log`.
18:28:26 <zere> was there any other business anyone wanted to discuss?
This page was last edited on 17 March 2014, at 16:40.