Humanitarian OSM Team/Working groups/Technical/meeting 2015-06-08
Jun 08 16:00:47 --> You are now talking on #hot-twg
Jun 08 18:01:49 xamanu_: hi
Jun 08 18:02:43 xamanu_: meeting?
Jun 08 18:03:11 BlakeGirardot: In an hour is my understanding
Jun 08 18:03:20 xamanu_: ah, great! :)
Jun 08 18:03:30 xamanu_: thanks, BlakeGiradot
Jun 08 18:03:35 BlakeGirardot: np, let me double check
Jun 08 18:03:51 BlakeGirardot: https://www.timeanddate.com/worldclock/fixedtime.html?msg=TWG+05.2015&iso=20150608T17
Jun 08 18:04:24 BlakeGirardot: Ya, so an hour
Jun 08 18:04:30 BlakeGirardot: see you then xamanu_
Jun 08 18:04:36 xamanu_: yep! :)
Jun 08 18:06:54 dodobas: yes, 1hour :)
Jun 08 18:07:42 dodobas: hopefully internet will not crap out on me
Jun 08 18:53:19 rekth: hello
Jun 08 18:55:12 mataharimhairi: hello rekth and arushi
Jun 08 18:56:00 rekth: mataharimhairi: hi :)
Jun 08 18:59:40 arushi: Hello everyone !
Jun 08 18:59:46 dodobas: hi arushi
Jun 08 18:59:58 arushi: hi !
Jun 08 19:00:04 brianohare: hi all..
Jun 08 19:00:23 dodobas: we might as well start
Jun 08 19:00:47 dodobas: i might drop out, internet connection is not to stable
Jun 08 19:01:14 dodobas: so we got some items on the agenda https://hackpad.com/TWG-Meeting-06.2015-JE12VBlrKJ5
Jun 08 19:02:01 dodobas: i will start with my report
Jun 08 19:02:16 dodobas: as we rmoved most of the locked tiles checks for the tasking manager, it has not crashed
Jun 08 19:03:16 pierregiraud: but it’s a temporary change, right?
Jun 08 19:03:22 dodobas: there was a missing maps mapathon that gotus up to 20req/s that produces no significant load on the server
Jun 08 19:03:49 dodobas: pierregiraud: zyes, until you create a better way, or we figure something out
Jun 08 19:03:56 mataharimhairi: hello everyone
Jun 08 19:04:07 dodobas: i saw you got some PR on the ay, did not look at it ...
Jun 08 19:04:10 pierregiraud: request has already been pulled in github
Jun 08 19:04:14 pierregiraud: OK
Jun 08 19:04:17 dodobas: ah.. good
Jun 08 19:04:49 dodobas: anyway thish is just a temporar change, that will be overwritten on the next release with much better solution
Jun 08 19:05:09 dodobas: moving on to the next item
Jun 08 19:05:29 dodobas: we need to move DNS registration/hosting for hotosm.org domain
Jun 08 19:06:15 dodobas: it's currently on the Kate's private DNS account
Jun 08 19:06:39 dodobas: do you maybe have a preferred DNS provider ?
Jun 08 19:07:00 pierregiraud: in France we use gandi a lot
Jun 08 19:07:16 pierregiraud: don’t know if it’s used elsewhere
Jun 08 19:07:38 dodobas: i ado know that amazon has its Route 53, but like with any cloud provider pricing might be a problem
Jun 08 19:07:52 xamanu_: Not preferred, but worked well for me: Amazon Web Services This is the only one I have used, besides having an own dns server running
Jun 08 19:07:57 brianohare: I'm using Route 53..
Jun 08 19:08:06 xamanu_: yes, AWS=Route 53
Jun 08 19:08:11 brianohare: works well..
Jun 08 19:08:21 dodobas: yeah, running our own it's not an option... :) we could but ...
Jun 08 19:08:34 dodobas: we do run our own for *.dev.hotosm.org
Jun 08 19:08:39 xamanu_: yeah, better getting a service. i agree
Jun 08 19:09:18 dodobas: so route 53 might be worth checking out...
Jun 08 19:09:50 dodobas: that is actuall my taks, i just wanted to gather some viable options...
Jun 08 19:10:03 dodobas: as there are way to many to rndomly choose
Jun 08 19:10:03 cristiano: +1 on route53, since we're already using other AWS services anyway
Jun 08 19:10:53 dodobas: my last item is export.hotosm.org update
Jun 08 19:11:09 dodobas: it was recently moved to a newer hardware
Jun 08 19:11:43 dodobas: which is still managed by geofabrik
Jun 08 19:12:28 dodobas: it has a bit more space and more memory
Jun 08 19:12:36 dodobas: *more free disk space
Jun 08 19:13:05 dodobas: that's my report if you don't have any questions
Jun 08 19:13:08 brianohare: but the aim is to move to HOT server, is that right?
Jun 08 19:13:35 dodobas: brianohare: yes,the plan is to shut the old instance down
Jun 08 19:14:04 dodobas: once we have something working
Jun 08 19:14:14 dodobas: xamanu_: do you want to continue?
Jun 08 19:14:20 brianohare: would be interested in knowing what the spec of that machine is?
Jun 08 19:14:26 xamanu_: ok
Jun 08 19:14:35 dodobas: brianohare: will get back to you
Jun 08 19:14:42 brianohare: ok thanks
Jun 08 19:15:23 xamanu_: One of our main approaches is: We want to make it easier, more understandable for visitors to the website to get envolved in HOT's activities. As one of the first steps, we restructred the content of the website: https://github.com/hotosm/hotosm-website/wiki/Content-structure
Jun 08 19:15:55 xamanu_: This restructuring included as well:
Jun 08 19:15:58 xamanu_: This restructuring included as well:
Jun 08 19:16:03 xamanu_: * New second level menu bar (grey)
Jun 08 19:16:10 xamanu_: * Project seperated by ongoing and types of projects: http://hotosm.org/projects btw, there are now the technical projects online!! :)
Jun 08 19:16:18 xamanu_: * Better texts "Get Involved", new "Emergency mapping" introduction page
Jun 08 19:16:23 xamanu_: * Updates (news) page nicer (with pictures at least)
Jun 08 19:17:00 xamanu_: * There is now a functionality to post jobs
Jun 08 19:17:06 pierzen: hi all, Is there log of the discussion?
Jun 08 19:17:15 xamanu_: Users:
Jun 08 19:17:41 xamanu_: * Users can be assigned and defined as staff, voting member, volunteer leads, board, etc..
Jun 08 19:17:49 xamanu_: * That's why we now cans see each other in the voting member view (http://hotosm.org/voting-members).
Jun 08 19:18:18 xamanu_: Thanks to Russel this is already showing all voting members. We need more pictures, please upload one, if you haven't already.
Jun 08 19:18:28 xamanu_: * New view for working groups (http://hotosm.org/working-groups)
Jun 08 19:18:28 BlakeGirardot: pierzen: Log so far: <rekth> hello
Jun 08 19:18:28 BlakeGirardot: <mataharimhairi> hello rekth and arushi
Jun 08 19:18:28 BlakeGirardot: <rekth> mataharimhairi: hi :)
Jun 08 19:18:28 BlakeGirardot: <arushi> Hello everyone !
Jun 08 19:18:28 BlakeGirardot: <dodobas> hi arushi
Jun 08 19:18:28 BlakeGirardot: <arushi> hi !
Jun 08 19:18:28 BlakeGirardot: <brianohare> hi all..
Jun 08 19:18:28 BlakeGirardot: <dodobas> we might as well start
Jun 08 19:18:28 BlakeGirardot: <dodobas> i might drop out, internet connection is not to stable
Jun 08 19:18:28 BlakeGirardot: <dodobas> so we got some items on the agenda https://hackpad.com/TWG-Meeting-06.2015-JE12VBlrKJ5
Jun 08 19:18:28 BlakeGirardot: <dodobas> i will start with my report
Jun 08 19:18:28 BlakeGirardot: <dodobas> as we rmoved most of the locked tiles checks for the tasking manager, it has not crashed
Jun 08 19:18:28 BlakeGirardot: <pierregiraud> but it’s a temporary change, right?
Jun 08 19:18:28 BlakeGirardot: <dodobas> there was a missing maps mapathon that gotus up to 20req/s that produces no significant load on the server
Jun 08 19:18:28 BlakeGirardot: <dodobas> pierregiraud: zyes, until you create a better way, or we figure something out
Jun 08 19:18:28 BlakeGirardot: <mataharimhairi> hello everyone
Jun 08 19:18:28 BlakeGirardot: <dodobas> i saw you got some PR on the ay, did not look at it ...
Jun 08 19:18:28 BlakeGirardot: <pierregiraud> request has already been pulled in github
Jun 08 19:18:28 BlakeGirardot: <pierregiraud> OK
Jun 08 19:18:28 BlakeGirardot: <dodobas> ah.. good
Jun 08 19:18:28 BlakeGirardot: <dodobas> anyway thish is just a temporar change, that will be overwritten on the next release with much better solution
Jun 08 19:18:28 BlakeGirardot: <dodobas> moving on to the next item
Jun 08 19:18:28 BlakeGirardot: <dodobas> we need to move DNS registration/hosting for hotosm.org domain
Jun 08 19:18:28 BlakeGirardot: <dodobas> it's currently on the Kate's private DNS account
Jun 08 19:18:28 BlakeGirardot: <dodobas> do you maybe have a preferred DNS provider ?
Jun 08 19:18:28 BlakeGirardot: <pierregiraud> in France we use gandi a lot
Jun 08 19:18:28 BlakeGirardot: <pierregiraud> don’t know if it’s used elsewhere
Jun 08 19:18:28 BlakeGirardot: <dodobas> i ado know that amazon has its Route 53, but like with any cloud provider pricing might be a problem
Jun 08 19:18:28 BlakeGirardot: <xamanu_> Not preferred, but worked well for me: Amazon Web Services This is the only one I have used, besides having an own dns server running
Jun 08 19:18:28 BlakeGirardot: <brianohare> I'm using Route 53..
Jun 08 19:18:28 BlakeGirardot: <xamanu_> yes, AWS=Route 53
Jun 08 19:18:28 BlakeGirardot: <brianohare> works well..
Jun 08 19:18:28 BlakeGirardot: <dodobas> yeah, running our own it's not an option... :) we could but ...
Jun 08 19:18:28 BlakeGirardot: <dodobas> we do run our own for *.dev.hotosm.org
Jun 08 19:18:28 BlakeGirardot: <xamanu_> yeah, better getting a service. i agree
Jun 08 19:18:28 BlakeGirardot: <dodobas> so route 53 might be worth checking out...
Jun 08 19:18:28 BlakeGirardot: <dodobas> that is actuall my taks, i just wanted to gather some viable options...
Jun 08 19:18:28 BlakeGirardot: <dodobas> as there are way to many to rndomly choose
Jun 08 19:18:28 BlakeGirardot: <cristiano> +1 on route53, since we're already using other AWS services anyway
Jun 08 19:18:28 BlakeGirardot: <dodobas> my last item is export.hotosm.org update
Jun 08 19:18:28 BlakeGirardot: <dodobas> it was recently moved to a newer hardware
Jun 08 19:18:28 BlakeGirardot: <dodobas> which is still managed by geofabrik
Jun 08 19:18:28 BlakeGirardot: <dodobas> it has a bit more space and more memory
Jun 08 19:18:28 BlakeGirardot: <dodobas> *more free disk space
Jun 08 19:18:28 BlakeGirardot: <dodobas> that's my report if you don't have any questions
Jun 08 19:18:28 BlakeGirardot: <brianohare> but the aim is to move to HOT server, is that right?
Jun 08 19:18:28 BlakeGirardot: <dodobas> brianohare: yes,the plan is to shut the old instance down
Jun 08 19:18:28 BlakeGirardot: <dodobas> once we have something working
Jun 08 19:18:28 BlakeGirardot: <dodobas> xamanu_: do you want to continue?
Jun 08 19:18:28 BlakeGirardot: <brianohare> would be interested in knowing what the spec of that machine is?
Jun 08 19:18:28 BlakeGirardot: <xamanu_> ok
Jun 08 19:18:28 BlakeGirardot: <dodobas> brianohare: will get back to you
Jun 08 19:18:28 BlakeGirardot: <brianohare> ok thanks
Jun 08 19:18:28 BlakeGirardot: <xamanu_> One of our main approaches is: We want to make it easier, more understandable for visitors to the website to get envolved in HOT's activities. As one of the first steps, we restructred the content of the website: https://github.com/hotosm/hotosm-website/wiki/Content-structure
Jun 08 19:18:28 BlakeGirardot: <xamanu_> This restructuring included as well:
Jun 08 19:18:28 BlakeGirardot: <xamanu_> This restructuring included as well:
Jun 08 19:18:28 BlakeGirardot: <xamanu_> * New second level menu bar (grey)
Jun 08 19:18:28 BlakeGirardot: <xamanu_> * Project seperated by ongoing and types of projects: http://hotosm.org/projects btw, there are now the technical projects online!! :)
Jun 08 19:18:28 BlakeGirardot: <xamanu_> * Better texts "Get Involved", new "Emergency mapping" introduction page
Jun 08 19:18:28 BlakeGirardot: <xamanu_> * Updates (news) page nicer (with pictures at least)
Jun 08 19:18:28 BlakeGirardot: <xamanu_> * There is now a functionality to post jobs
Jun 08 19:18:28 BlakeGirardot: <pierzen> hi all, Is there log of the discussion?
Jun 08 19:18:28 BlakeGirardot: <xamanu_> Users:
Jun 08 19:18:32 BlakeGirardot: gah, sorry
Jun 08 19:18:42 BlakeGirardot: so sorry
Jun 08 19:19:04 BlakeGirardot: That was supposed to be this url: https://gist.github.com/bgirardot/bb7a22b2569df4b8edce
Jun 08 19:20:52 pierzen: ok thanks
Jun 08 19:20:56 xamanu_: :)
Jun 08 19:21:10 xamanu_: so i continue?
Jun 08 19:21:39 dodobas: hopefully :)
Jun 08 19:21:39 pierzen: For Menu there was discussions 2 years ago. I suggested we should have a common Top menu bar on each HOT service TM, Hot Export included
Jun 08 19:22:46 mataharimhairi: That is a good suggestion! Could you log it as an issue in the hot-website repository?
Jun 08 19:23:03 mataharimhairi: https://github.com/hotosm/hotosm-website/issues
Jun 08 19:23:34 xamanu_: yeah, this would be good! as well to include in the redesign, i will mentionj in a few minutes
Jun 08 19:25:11 xamanu_: So we have two new user views
Jun 08 19:25:46 xamanu_: voting member http://hotosm.org/voting-members
Jun 08 19:25:57 xamanu_: and working groups http://hotosm.org/working-groups
Jun 08 19:26:10 xamanu_: And some good news: We have a new designer on board: Katja. She is already supporting with nice new icons and reviewing the whole website in order to start working on proposals for a redesign.
Jun 08 19:26:24 xamanu_: o/
Jun 08 19:27:02 pierregiraud: what do you mean by « on board » ?
Jun 08 19:27:16 xamanu_: she is volunteering and wants to help
Jun 08 19:27:22 mataharimhairi: Oh excellent. She has also been helping with collecting all the photos for Nepal.
Jun 08 19:27:27 xamanu_: she started to know HOT for the Nepal activation
Jun 08 19:27:29 mataharimhairi: Nice to see more people getting involved.
Jun 08 19:27:45 xamanu_: I just wrote to the mailing list and she lift her hand
Jun 08 19:28:38 xamanu_: she made already some icons: http://i.imgur.com/82m25H1.jpg
Jun 08 19:28:47 xamanu_: ok this was the report :)
Jun 08 19:28:52 xamanu_: not to things to discuss
Jun 08 19:29:00 xamanu_: s/not/now
Jun 08 19:29:10 xamanu_: * Just to let you know: TechWG related website issues have a certain tag ("infrastructure"): https://github.com/hotosm/hotosm-website/issues?q=is%3Aopen+is%3Aissue+label%3Ainfrastructure
Jun 08 19:29:20 pierregiraud: nice
Jun 08 19:29:23 xamanu_: * I really would like to have a TLS certificate. I think it is not very responsible to make people login to the website transmitting their passwords as plain text over their networks: https://github.com/hotosm/hotosm-website/issues/14
Jun 08 19:30:21 dodobas: xamanu_: i will 'reopen' the discussion on the SSL certificate
Jun 08 19:30:36 xamanu_: what does reopen mean, dodobas? :)
Jun 08 19:31:34 dodobas: we had previous discussions, that ended when we decided to look for an provider that provides free certificates...
Jun 08 19:32:12 xamanu_: there are no free certificates, as they are not included in common browsers
Jun 08 19:32:19 xamanu_: but there should be cheap ones
Jun 08 19:32:38 dodobas: IIRC, non of the providers that support 'open source' projects don't support wildcard certificates
Jun 08 19:33:21 dodobas: so we need to pay, or look for an programm that will support us
Jun 08 19:34:29 dodobas: so, I can 'reopen' the discussions, probably with current executive director Tyler...
Jun 08 19:34:46 xamanu_: ok. i would appreciate if we could push this further. can I do anything for it?
Jun 08 19:35:12 dodobas: look for an cheap reliable wildcard SSL certiciate :)
Jun 08 19:35:31 xamanu_: ok, i will. and send it to the techwg mailing list
Jun 08 19:35:40 xamanu_: so, two last tiny things:
Jun 08 19:35:43 xamanu_: * Russel asked me to get confirmation from you all to shutdown Google Analytics on the website. Piwik seems to be working fine:
Jun 08 19:35:54 xamanu_: any objections?
Jun 08 19:35:59 xamanu_: :)
Jun 08 19:37:50 dodobas: i have none
Jun 08 19:38:03 xamanu_: ok, thanks
Jun 08 19:38:08 mataharimhairi: me neither, if piwik is doing a fine job
Jun 08 19:38:24 cristiano: Does that run on the same server?
Jun 08 19:38:51 dodobas: yes
Jun 08 19:39:06 cristiano: I wonder if dodobas can make a ..map of all HOT infrastructure and services ;-)
Jun 08 19:39:34 dodobas: cristiano: it's on my todo list...
Jun 08 19:39:38 xamanu_: cristiano, dodobas: this would be very helpful.
Jun 08 19:40:19 dodobas: at least the ones i know of
Jun 08 19:40:21 mataharimhairi: +1 for infrastructure and services diagrams!
Jun 08 19:40:29 xamanu_: ok, the last thing: We have a problem upgrading the OS's packages on the server and I would like to ask you for a hand: https://github.com/hotosm/hotosm-website/issues/46
Jun 08 19:42:14 dodobas: that would be me (blush)
Jun 08 19:42:33 xamanu_: sorry, dodobas...!
Jun 08 19:42:45 xamanu_: it is a mounting problem
Jun 08 19:43:17 xamanu_: on one certain package which wants to update and blocks now all apt-get install/upgrade commands
Jun 08 19:43:49 xamanu_: please, let me know if I can help you with anything!
Jun 08 19:45:22 xamanu_: sorry, I have to run to a meeting now. But I will read the logs! Or is there any more question?
Jun 08 19:45:55 xamanu_: if not please continue with the agenda and I say goodbye :)
Jun 08 19:46:39 cristiano: Thanks xamanu_ - you are doing an awesome job with the website!
Jun 08 19:46:53 dodobas: mataharimhairi: export report ?
Jun 08 19:47:00 xamanu_: thank you!
Jun 08 19:47:12 mataharimhairi: thank you xamanu_
Jun 08 19:47:22 mataharimhairi: yes @dodobas
Jun 08 19:48:04 mataharimhairi: as everyone is aware, we are currently working on enhancing the export tool
Jun 08 19:48:28 mataharimhairi: brian o'hare is the main developer of the project
Jun 08 19:48:43 brianohare: hello everyone :-)
Jun 08 19:48:52 mataharimhairi: so I wanted to introduce him and let him lead the report on the current status
Jun 08 19:48:53 mataharimhairi: :)
Jun 08 19:49:07 mataharimhairi: sorry, go for it brian!
Jun 08 19:49:16 brianohare: thanks mhairi
Jun 08 19:49:21 brianohare: hi folks
Jun 08 19:49:35 arushi: hello brian !
Jun 08 19:49:45 brianohare: so, i started on 18th May.. so am three weeks into the process now..
Jun 08 19:49:51 brianohare: hi Arushi!
Jun 08 19:50:19 brianohare: the main focus of my work so far has been on the development of a set of api's for export creation
Jun 08 19:51:08 brianohare: I have a basic end-to-end process for creating export jobs and for configuring them with presets, translation and tranform files
Jun 08 19:51:50 brianohare: I'm also using a distributed task queue which I'm hoping will allow the application to scale in future.
Jun 08 19:52:17 brianohare: Currently, when a job is created it gets passed to the queue for processing..
Jun 08 19:52:50 brianohare: they're just dummy jobs at the moment but they can report their result status so the api can display the results
Jun 08 19:53:15 brianohare: you can see example api's at http://hot.geoweb.io/api
Jun 08 19:53:50 brianohare: The next focus will be on integrating the api with the export backend
Jun 08 19:54:09 brianohare: so that export tasks can acutally be run when a job is created
Jun 08 19:54:28 brianohare: I'll spend most of this week on this
Jun 08 19:54:48 brianohare: The idea is that the new User Interface will consume the new API's
Jun 08 19:55:05 brianohare: But other clients could also consume these api's in future..
Jun 08 19:55:40 brianohare: my initial thought was that there could be some closer integration with OSMAnd in future..
Jun 08 19:55:59 brianohare: possibly via a plugin..
Jun 08 19:56:24 brianohare: that's a general gist of what I've been up to.
Jun 08 19:56:40 mataharimhairi: thank you brian. i'm not sure if everyone got a chance to see the email that you sent round, but it contains a more in-depth report as well as attachments of the infrastructure and the development timeline
Jun 08 19:57:03 mataharimhairi: does anyone have any questions?
Jun 08 19:57:13 brianohare: yes, there's a diagram of the architecture there as well..
Jun 08 19:58:49 mataharimhairi: if there are no questions at this point in time
Jun 08 19:59:06 cristiano: Very cool Brian, I like the design. How do we plan to manage user permissions and duplication of tasks?
Jun 08 19:59:10 BlakeGirardot: Is there a specifications document for the export server?
Jun 08 19:59:52 brianohare: christiano: for user permissions, there will be session authentication via the browser
Jun 08 19:59:52 arushi: Is django framework being used ?
Jun 08 20:00:03 brianohare: api clients will use token authentication
Jun 08 20:00:20 brianohare: arushi: yes I'm using django 1.8
Jun 08 20:00:23 * pierregiraud has to leave, sorry, See my comments in the hackpad document Jun 08 20:00:36 BlakeGirardot: Is there a specifications document for the export server?
Jun 08 20:00:46 cristiano: OK, so then admins can set permissions for specific users to create e.g. larger jobs?
Jun 08 20:00:50 pierzen: hi brianohare Important aspects for users (Perspective from Activations - we are Funding via the Hewlet Fund) - Easier way to select then using the Presets, Important to have more flexibility offering Export products for Activation including this current Nepal - GPS garmin export that work, OBF OSMand format. Are they clear prioritires identified for this development phase?
Jun 08 20:01:27 brianohare: pierzen: yes the OBF is a priority..
Jun 08 20:01:47 dodobas: pierzen: garmin depends on the size of the area
Jun 08 20:01:47 cristiano: I am asking, because there will be a similar challenge with users in OAM asking to create large tile service jobs, and we are trying to think how to set those permissions, but still have the service as open as possible
Jun 08 20:01:48 brianohare: Mhairi and Arushi are investigating how preset configuration might work from a usabilty perspective
Jun 08 20:02:31 brianohare: the Garmin issues needs more investigation
Jun 08 20:02:56 mataharimhairi: yes pierzen, we will be following up brian's report with the usability questionnaire we have drafted for the export tool to address some of these concerns
Jun 08 20:03:08 brianohare: christano: yes that could be possible.. it has been a requirement so far but happy to discuss..
Jun 08 20:03:26 arushi: I have had a chance to talk with BlakeGirardot and cristiano on irc before,
Jun 08 20:03:26 arushi: during my proposal selection. Its nice to meet them here again ! :)
Jun 08 20:03:35 cristiano: = finding a balance between what we can offer and what users can requests without crushing the service or becoming unsustainable
Jun 08 20:03:56 brianohare: christiano: sure, especially if we add OBF!
Jun 08 20:04:08 brianohare: seems a memory hungry process..
Jun 08 20:04:12 dodobas: cristiano: that'sjust project manager gibberish :)
Jun 08 20:04:15 mataharimhairi: perhaps that question could be added to the usability questionnaire cristiano, to see what users might require in terms of size?
Jun 08 20:05:23 brianohare: the task queue should help with service stability as the queue can be configured to limit concurrent processes
Jun 08 20:05:28 mataharimhairi: we did briefly chat about setting a size limit - which is on the questionnaire
Jun 08 20:05:40 mataharimhairi: but needs to be expanded i believe
Jun 08 20:06:12 cristiano: cool - so that should answer my second question about duplication/overlapping of tasks :-)
Jun 08 20:06:29 brianohare: christiano: thats the idea :-)
Jun 08 20:06:50 BlakeGirardot: Is there a specifications or requirements document we coudl look at?
Jun 08 20:06:56 pierzen: Can you assure that both GPS Garmin / Better Usability for Tag selections / OBF will be delivered at the end of the project, or only analyzed?
Jun 08 20:07:36 brianohare: pierzen: can assure about usability and OBF, I can't say for certain about Garmin.
Jun 08 20:08:05 brianohare: I think dodobas investigated before.. I'd like to speak to him further about Garmin..
Jun 08 20:08:42 brianohare: BlakeGirardot: I don't have a specification or requirements doc..
Jun 08 20:08:54 cristiano: @BlakeGirardot: Brian sent an email to TWG last night with details
Jun 08 20:10:04 BlakeGirardot: cristiano: Ya, that was architecture, not really a requirements or spec doc. Which is fine, it would just save some back and forth if one existed if we could look at it, help with priorities and such.
Jun 08 20:10:11 mataharimhairi: the empty garmin file is an issue of high priority and we will attempt to address it https://github.com/hotosm/hot-exports/issues/65
Jun 08 20:10:55 BlakeGirardot: And help with knowing that stuff we think needs to be in there is already in there for consideration.
Jun 08 20:11:13 cristiano: I guess we should use the wiki and github issues for that https://github.com/hotosm/osm-export-tool2/issues
Jun 08 20:11:22 BlakeGirardot: It sounds like maybe that will come out of arushi and mataharimhairi project.
Jun 08 20:11:35 mataharimhairi: the deliverables are listed in the contract
Jun 08 20:11:50 mataharimhairi: which we could share if you would like to see it
Jun 08 20:12:35 brianohare: @BlakeGirardot: I'm aware of the outstanding issues listed in github
Jun 08 20:12:41 mataharimhairi: or i can create a requirement document and add it to the github wiki for the osm-export-tool2
Jun 08 20:12:41 BlakeGirardot: Ya, I think it might help so we don't suggest stuff that might already be specified and let us know whats coming that might be different. Just the deliverables part would be good.
Jun 08 20:12:43 cristiano: I think that's a good idea, and maybe it can be mapped out to issues and milestones in github repo
Jun 08 20:12:47 brianohare: the aim is to fix as many of these issues as possible
Jun 08 20:13:27 mataharimhairi: sure. i will create the wiki page with set deliverables, and those we would like to address if time permits
Jun 08 20:14:26 mataharimhairi: i can also add the other attachments, such as the architecture diagram and timeline to the wiki
Jun 08 20:15:03 mataharimhairi: okay, if there are no more questions I would like to move on to the usability survey as it is 2.15 am here! :)
Jun 08 20:15:26 mataharimhairi: and please, if there are any more questions, email brian and me
Jun 08 20:15:37 cristiano: tiny question: the previous tool was called hot-exports and this new one is hot-export-tool2. Any reason for the name change?
Jun 08 20:15:59 mataharimhairi: so i would like to introduce arushi vashist, our outreachy intern who is working alongside brian on the export tool
Jun 08 20:16:01 brianohare: christiano: I think that's just the name of the github repo..
Jun 08 20:18:05 mataharimhairi: hi arushi
Jun 08 20:18:15 arushi: hello !
Jun 08 20:18:22 mataharimhairi: would you like to introduce yourself to the technical working group :)
Jun 08 20:18:29 cristiano: welcome arushi!
Jun 08 20:18:35 brianohare: hi arushi!
Jun 08 20:18:45 arushi: Hello everybody ! I am doing a project regarding the HOT Export Tool with Mhairi. I have had a chance to talk with BlakeGirardot and cristiano on irc before,
Jun 08 20:18:45 arushi: during proposal selection. Its nice to meet them again here ! :)
Jun 08 20:19:24 arushi: Mhairi and me have been working for the past 2 weeks now..
Jun 08 20:20:38 arushi: We started out with listing the Export tool features..
Jun 08 20:21:04 arushi: and then creating a mockup of the UI
Jun 08 20:21:34 arushi: This week we spent time on creating a survey for the community members
Jun 08 20:22:13 pierzen: Hi arushi How is the response to the survey so far?
Jun 08 20:22:59 arushi: that will help us understand about which features are more important and how we can incorporate suggestions into our UI design
Jun 08 20:23:10 mataharimhairi: @pierzen, we haven't actually released the survey as we would like to share it with the technical WG for feedback on the questions we are asking
Jun 08 20:23:38 pierzen: Sorry, I thought this was the Nepal earthquake survey
Jun 08 20:24:11 mataharimhairi: we want to make sure we are asking the 'right' questions to ensure that we get the right information/stats on what we should base our UI design on
Jun 08 20:25:15 mataharimhairi: @arushi - would you like to share the survey link?
Jun 08 20:25:30 arushi: yes sure
Jun 08 20:25:56 arushi: its been updated
Jun 08 20:27:22 arushi: https://www.surveymonkey.com/s/N3TCCTF
Jun 08 20:27:47 arushi: this is the survey link
Jun 08 20:29:24 arushi: I will follow up with an email to the technical WG with the link requesting feedback over the next couple of days
Jun 08 20:29:36 arushi: so that we can incorporate it and hopefully release the official survey by the end of the week
Jun 08 20:29:49 arushi: I hope this should do
Jun 08 20:29:54 mataharimhairi: thank you arushi!
Jun 08 20:30:40 mataharimhairi: please do everyone read the survey and provide suggestions, as this is a very important step in ensuring we get the right information from the community
Jun 08 20:31:18 mataharimhairi: to enhance the export tool UI and make it efficient for both new users and experienced humanitarian mappers
Jun 08 20:31:43 mataharimhairi: does anyone have any questions for arushi and I?
Jun 08 20:32:31 cristiano: Is this the HDM being used? http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/HDM_preset
Jun 08 20:32:42 mataharimhairi: please note that this is just the draft
Jun 08 20:34:01 mataharimhairi: @cristiano - do you mean currently in the export tool?
Jun 08 20:34:02 arushi: Yes, we used this for one of our questions..
Jun 08 20:34:05 pierzen: HOT Export Coverage - Any plan to extend and cover Planet for areas not yet covered, Middle-East, Pacific, Asia ? Recently for the Vanuatu Activation, this area is not covered.
Jun 08 20:34:54 mataharimhairi: It would make sense for us to extend to all the regions we have activated for
Jun 08 20:34:59 pierzen: Caraibeans islands not covered either.
Jun 08 20:35:18 dodobas: HDM tile servers can be a bit unreliable
Jun 08 20:35:20 mataharimhairi: And I don't see why we shouldn't - unless there is a specific reasons this hasn't been done in the past?
Jun 08 20:35:51 brianohare: @pierzen: yes that should be possible.. the regions are now much more configurable and can be edited in django admin
Jun 08 20:35:52 pierzen: Do we have storage or technical problems that do not let extend the coverage?
Jun 08 20:36:18 dodobas: cristiano: they were, at least 6 months ago ..
Jun 08 20:36:32 mataharimhairi: @dodobas, how were the HDM tile servers unreliable in the past?
Jun 08 20:37:24 dodobas: not working :)
Jun 08 20:37:44 brianohare: @pierzen: I'm investigating the storage and technical issues this week
Jun 08 20:38:07 dodobas: or network bandwidth issues, they are hostedby osm-fr
Jun 08 20:38:17 pierzen: As I remember, OSM-fr hdm tile server is quite reliable. How long it was not available?
Jun 08 20:39:04 pierzen: I dont remember of major problems with it.
Jun 08 20:40:44 dodobas: every day during 2 months .... for at least few hours, last year in October/November
Jun 08 20:40:44 dodobas: wes using it for a base map on a service, swithced to osm.. HDM was just not working
Jun 08 20:41:24 pierzen: Did you investigate with OSM-Fr technical people?
Jun 08 20:41:42 dodobas: mataharimhairi: what-s nwxt on your agenda
Jun 08 20:43:03 mataharimhairi: that's it for me
Jun 08 20:43:12 dodobas: we should be moving along...
Jun 08 20:43:23 mataharimhairi: i will have to bid everyone good bye as well
Jun 08 20:43:34 mataharimhairi: thank you everyone
Jun 08 20:43:41 dodobas: mataharimhairi: good night
Jun 08 20:43:43 dodobas: :)
Jun 08 20:43:43 mataharimhairi: and thank you brian and arushi!
Jun 08 20:43:44 brianohare: thanks Mhairi
Jun 08 20:43:55 arushi: thanks Mhairi !
Jun 08 20:43:59 dodobas: it's 2 am for me also....
Jun 08 20:44:11 mataharimhairi: good night. i will read through the rest of the meeting notes tomorrow
Jun 08 20:44:19 mataharimhairi: oh yeah - bangkok time :)
Jun 08 20:44:26 mataharimhairi: adios
Jun 08 20:44:42 dodobas: yeah ...
Jun 08 20:45:07 dodobas: TM issues, BlakeGirardot ?
Jun 08 20:45:48 BlakeGirardot: Are we skipping github users?
Jun 08 20:45:54 BlakeGirardot: Mine is short
Jun 08 20:45:55 BlakeGirardot: I'll go
Jun 08 20:46:19 dodobas: that's was mhairi... but i-ll sum up after you
Jun 08 20:46:20 BlakeGirardot: Rekth and I went through all the open issues and marked the UI related items
Jun 08 20:47:13 BlakeGirardot: And then Rekth went through and grouped them, mostly by functional area, Project Management, frontpage, task selection
Jun 08 20:47:34 BlakeGirardot: Which we are going through again at the moment.
Jun 08 20:48:27 BlakeGirardot: This week we will get that finalized and work on some UI evaluation processes
Jun 08 20:49:22 BlakeGirardot: I think we talked about doing priotization as well on the issues
Jun 08 20:49:56 BlakeGirardot: which I will need to follow up with cristiano and mhairi on
Jun 08 20:50:21 BlakeGirardot: I have tried to clean up a few issues as well, I see one got closed during this meeting, yay
Jun 08 20:50:37 BlakeGirardot: but I still have about 1/2 to go through in detail.
Jun 08 20:50:58 BlakeGirardot: Thats about it for me and Rekth, more on the tech wg email list this week.
Jun 08 20:51:17 dodobas: github users... there are far to many, some of users are not really active, and most of the hotosm github users are project administrators
Jun 08 20:51:55 dodobas: which is not optimal, so we should reorganize users and groups on github to something more sensible
Jun 08 20:52:06 BlakeGirardot: rekth and I will remove ourselves after the next week or so.
Jun 08 20:52:28 BlakeGirardot: we just needed to be able to set labels, but I don't want collaborator status.
Jun 08 20:52:40 rekth: same here :)
Jun 08 20:53:07 dodobas: project and organizzation admins are really poverfull, and we don't really want to, ask questions later ...
Jun 08 20:53:27 dodobas: .. to be in a situation to ask questions later...
Jun 08 20:53:52 dodobas: anyway, that's something we should think about doing/
Jun 08 20:54:05 dodobas: cristiano: OAM ?
Jun 08 20:54:15 BlakeGirardot: i'd say remove them and add them back as requested :)
Jun 08 20:54:16 dodobas: what's AOB ? any other business ?
Jun 08 20:54:41 cristiano: I recommend reviewing and use groups more https://github.com/orgs/hotosm/teams
Jun 08 20:54:55 cristiano: or teams, whatever they are called ;-)
Jun 08 20:56:05 cristiano: Quick updates on OAM: we have a beta for the catalog out; we are defining requirements and design of the server component and we are working with Tassia (one of our Outreachy interns) on a QGIS plugin
Jun 08 20:56:06 dodobas: check everyone out and add as requested :)
Jun 08 20:57:18 cristiano: I added the links to the agenda. Feedback, comments, participation is appreciated, especially from this WG ;-)
Jun 08 20:59:07 cristiano: Any feedback or issue with the OAM Catalog browser should go here https://github.com/hotosm/oam-browser/issues
Jun 08 21:00:57 cristiano: Unless of any immediate comment on OAM, I added three quick items in AOB
Jun 08 21:01:12 dodobas: an AOB is ?
Jun 08 21:01:38 cristiano: Do you think it would be useful to have a TWG repo to track requests to HOT sysadmin and general technical tasks?
Jun 08 21:01:54 cristiano: AOB = any other business?
Jun 08 21:02:30 dodobas: sysadmin should not get any direct requests :)
Jun 08 21:02:49 cristiano: ahah
Jun 08 21:03:15 BlakeGirardot: :)
Jun 08 21:03:49 dodobas: hot as an orgznization already has a tool to track internal tasks
Jun 08 21:03:52 cristiano: I put in an example…. what would you recommend?
Jun 08 21:04:14 dodobas: not sure what would be genreal technical tasks?
Jun 08 21:04:33 cristiano: what if there's a request or feedback from non staff?
Jun 08 21:05:32 dodobas: maybe.. use https://github.com/hotosm/hotosm/issues
Jun 08 21:06:16 cristiano: oh! there you go, it already existed
Jun 08 21:06:54 dodobas: but... not really useful at the moment
Jun 08 21:07:17 dodobas: nor advertised as a general non staff issue tracking 'tool'
Jun 08 21:07:44 cristiano: Well, we should list it in our infrastructure map
Jun 08 21:07:52 cristiano: which we should make public btw
Jun 08 21:08:24 cristiano: and maybe we could also add a link on the website, for anyone wanting to report or propose ideas outside of a specific project repo
Jun 08 21:08:33 dodobas: cristiano: anything else?
Jun 08 21:08:35 cristiano: ideas/issues
Jun 08 21:10:44 cristiano: the other two items are self-explanatory, just wanted to push for adopting gitter as a more integrated chat platform
Jun 08 21:10:51 cristiano: and also check on other HOT AWS and how they are used
Jun 08 21:11:12 cristiano: (fyi - we have an AWS account specific to OAM)
Jun 08 21:11:27 dodobas: which is owned by ?
Jun 08 21:11:31 cristiano: but maybe it's something I should just discuss with you next week
Jun 08 21:11:41 cristiano: by HOT
Jun 08 21:11:49 dodobas: ok, next week
Jun 08 21:12:10 dodobas: the end :)
Jun 08 21:12:24 BlakeGirardot: Cheers, good night all.
Jun 08 21:12:33 rekth: bye everyone o/
Jun 08 21:12:35 brianohare: good night all!
Jun 08 21:12:43 cristiano: adios! thanks @dodobas
Jun 08 21:12:49 pierzen: Bonsoir
Jun 08 21:13:05 dodobas: see you next time, 6th July, im traveling on the 13th
Jun 08 21:13:21 dodobas: bye ...