Difference between revisions of "Working Group Minutes/EWG 2014-12-15"

From OpenStreetMap Foundation
(Created page with "== Attendees == {| class="wikitable" style="font-size:0.9em;" |- ! IRC nick ! Real name |- | pnorman || Paul Norman |- | zere || Matt Amos |- |} == Summary == * splitting t...")
(No difference)

Revision as of 17:25, 22 December 2014


IRC nick Real name
pnorman Paul Norman
zere Matt Amos


  • splitting the website up
    • zere outlined some ideas to an empty room


17:35:01 <zere> minutes of the last meeting: http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/EWG_2014-11-17 please let me know if anything needs changing
17:35:28 <zere> i've only got one item for the agenda tonight, which is; splitting the website up.
17:35:34 <zere> #topic splitting the website
17:36:08 <zere> the idea here is that it would be easier to run & manage services if they were smaller in scope.
17:37:07 <pnorman> yes
17:37:43 <zere> for example, the GPS track stuff is only 'joined' to the website via the users <-> gpx_files tables.
17:38:35 <zere> so (although we probably want to do this for the API at some point) it might an easier path to try it out on the GPX stuff first.
17:39:18 <zere> basically, it seems like we'd need to extract the user auth stuff into some sort of internal service, which then gets called by the API & GPX code to track sessions and/or OAuth tokens.
17:39:57 <zere> as far as i can see, we only support 3 forms of auth: cookies, OAuth & (yuvk) http basic
17:42:45 <zere> so it should be pretty easy to forward the tokens for that on to the service. the only real question is how much effort/logic is worth putting into the using services (e.g: caching, oauth verification, etc...) to save round-trips to the internal auth service.
18:19:38 <zere> there is a deafening silence. i assume that's because everyone's waiting for santa to bring them ponies? ;-)
18:33:15 <zere> hmm... okay. thanks for coming, and hope to see more next week.