13:59:26 <russdeffner> #startmeeting HOT Activation Working Group 3/30
13:59:26 <MeetBot> Meeting started Fri Mar 30 13:59:26 2018 UTC.  The chair is russdeffner. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:26 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:07 <russdeffner> #topic Activation Working Group 3/30
14:00:43 <hot_slack_bot> <russell.deffner> hi all, my irc client froze, one moment...
14:01:19 <russdeffner> ok, think I'm back up
14:01:28 <russdeffner> yeah!
14:01:52 <russdeffner> Welcome to the AWG meeting, Russell Deffner of HOT here
14:02:23 <russdeffner> Type a greeting if you want the bot to log you as here
14:02:24 <hot_slack_bot> <p.ulbrich> Hi all, this is Philipp Ulbrich, co-chairing
14:04:18 <russdeffner> #link https://trello.com/c/aG8SlkdK/22-previous-meeting-summaries - first agenda item - review previous minutes, thanks Philipp for putting those together on the card
14:05:03 <russdeffner> #commands
14:05:03 <MeetBot> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #rejected #restrictlogs #save #startmeeting #topic #unchair #undo #unlurk
14:06:10 <hot_slack_bot> <p.ulbrich> #agree
14:06:21 <russdeffner> I honestly haven't given a real good look at the ToR; been swamped
14:06:52 <russdeffner> Did anyone else have a look? Any suggestions, etc?
14:06:54 <hot_slack_bot> <p.ulbrich> I've had a quick look - looks ok to me
14:07:38 <russdeffner> Ya, I remember it being generally good, just not sure anything needs to be updated
14:08:26 <russdeffner> Unless there is concern, I think I can give it a look this weekend in time to let the Board know it's ready for review?
14:09:10 <hot_slack_bot> <p.ulbrich> maybe a gender related note (coming back to the point we briefly spoke about last time)
14:09:13 <hot_slack_bot> <p.ulbrich> Intentionally including local OSM community members in disaster-affected countries in HOT disaster response activities
14:09:52 <russdeffner> If anything does need updated/changed that makes any significant changes I will email the list
14:10:00 <hot_slack_bot> <p.ulbrich> maybe including Intentionally encouraging the participation of women and local OSM community members in disaster-affected countries in HOT disaster response activities
14:10:12 <hot_slack_bot> <p.ulbrich> something like this?
14:11:18 <hot_slack_bot> <p.ulbrich> #idea maybe including Intentionally encouraging the participation of women and local OSM community members in disaster-affected countries in HOT disaster response activities
14:11:53 <russdeffner> Just to clarify, you see that going in our ToR?
14:12:47 <hot_slack_bot> <p.ulbrich> yes, that would be my suggestion, to add to the emphasis on local OSM community members
14:12:49 <russdeffner> oh, I see where you're looking now
14:13:34 <hot_slack_bot> <p.ulbrich> sorry, should have clarified the para
14:13:35 <russdeffner> I think we could at that as a new 'line item' or...
14:13:58 <russdeffner> Maybe we can make that current line something even more broad?
14:14:43 <russdeffner> encouraging the participation of more local and more diverse OSM community members...?
14:15:00 <hot_slack_bot> <p.ulbrich> yes, sounds good
14:16:48 <hot_slack_bot> <p.ulbrich> oh and I'd agree to add the slack disaster channel to the default comm channels
14:16:55 <russdeffner> ok, since it looks like just us anyway; maybe now is a good time to just work through the ToR
14:17:12 <hot_slack_bot> <p.ulbrich> i think there is someone else?
14:17:19 <hot_slack_bot> <p.ulbrich> soundharya?
14:17:20 <hot_slack_bot> <soundharyabharatiya> Hi Philipp and Russell, I am Soundharya, working as the front-end engineer in Bangalore, India. I am looking forward to joining hotosm technical WG in the forthcoming days.
14:17:40 <hot_slack_bot> <soundharyabharatiya> Yup. Lol. It's me.
14:17:59 <hot_slack_bot> <p.ulbrich> Welcome Soundharya! It's great that you could join!
14:18:08 <russdeffner> Hi soundharya, glad to have you here
14:18:42 <russdeffner> I think the Tech WG still meets on IRC as well, so a bit of intro/practice
14:19:00 <hot_slack_bot> <soundharyabharatiya> That's cool. thanks. I am really interested with the idea of your projects which u ppl are doing.
14:19:03 <russdeffner> If you have any questions about Activation WG, feel free
14:19:42 <hot_slack_bot> <soundharyabharatiya> Oh. Activation WG is different from Technical WG? My bad!
14:20:07 <hot_slack_bot> <p.ulbrich> You are very welcome here as well! :$
14:20:11 <hot_slack_bot> <soundharyabharatiya> I am sorry for that!
14:20:47 <hot_slack_bot> <soundharyabharatiya> Can I know what's activation WG,btw?
14:21:25 <hot_slack_bot> <soundharyabharatiya> :slightly_smiling_face:
14:21:32 <russdeffner> no problem, we have 8 wgs and 2 sub-wgs, you can get more info here: https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team/Working_groups
14:21:56 <russdeffner> Activation manages the Disaster Mapping program for HOT
14:22:09 <hot_slack_bot> <soundharyabharatiya> Great, I will look into that.
14:22:14 <hot_slack_bot> <soundharyabharatiya> Thanks, guys!
14:22:58 <russdeffner> So we do training for disaster coordination; then do the coordination, documentation and more knowledge building and sharing
14:23:50 <russdeffner> so back to the terms of reference...
14:24:06 <russdeffner> there is this bit I don't 'like' anymore...
14:24:17 <russdeffner> "Anyone completing the course and assignment will automatically be added to the AWG after approval by any two group leads."
14:24:41 <russdeffner> really it's just been Blake and myself doing any course review, etc.
14:25:19 <russdeffner> so basically both Blake and I have had to do the AWG approvals
14:25:53 <hot_slack_bot> <p.ulbrich> you mean in terms of workload?
14:25:59 <russdeffner> in theory, Philipp will be doing this soon, and hopefully others but maybe one is sufficient
14:26:01 <hot_slack_bot> <soundharyabharatiya> So, you have a course for that?
14:26:27 <hot_slack_bot> <soundharyabharatiya> Great information.
14:26:33 <russdeffner> yep, courses.hotosm.org is where the training currrently lives
14:26:34 <hot_slack_bot> <p.ulbrich> yes, here is the platform
14:26:37 <hot_slack_bot> <p.ulbrich> http://courses.hotosm.org
14:26:55 <hot_slack_bot> <soundharyabharatiya> That's good.
14:27:32 <hot_slack_bot> <soundharyabharatiya> You train volunteer or student studying in educational institutions?
14:27:52 <hot_slack_bot> <p.ulbrich> anyone wants to participate
14:27:55 <hot_slack_bot> <p.ulbrich> who
14:28:10 <russdeffner> Blake and I trust each other enough to not 'really' need to verify someone; usually it's just a hey check out this new person, any particular opinion?
14:28:22 <hot_slack_bot> <p.ulbrich> so - should we change it to 1?
14:28:31 <russdeffner> and don't think we've ever 'rejected' someone
14:29:01 <hot_slack_bot> <soundharyabharatiya> That's amazing. Even in Bangalore, I am co-ordinating open source events in Bangalore.
14:29:31 <russdeffner> And we haven't built up the 'group leads' yet (i.e. this was to be those who complete the Activation Lead role training)
14:29:58 <hot_slack_bot> <soundharyabharatiya> So, it may roll on with that.
14:29:59 <russdeffner> In conlusion my idea is...
14:30:58 <russdeffner> #idea "Anyone completing the course and assignment will automatically be added to the AWG after approval by any working group lead."
14:31:11 <russdeffner> simplifies
14:31:29 <hot_slack_bot> <p.ulbrich> #agree
14:31:44 <hot_slack_bot> <soundharyabharatiya> I read something called "HOTOSM Voting members". But unfortunately that mail landed in spam. Still, do I have the chance to join that.
14:31:53 <russdeffner> really there is not much harm in someone joining the group
14:32:23 <russdeffner> soundharya - membership nominations are usually only once a year and we just finished the election recently
14:32:54 <hot_slack_bot> <soundharyabharatiya> Oh :(
14:32:56 <russdeffner> but you can always be talking to the existing members and let them know you're interested for next time
14:33:45 <hot_slack_bot> <soundharyabharatiya> Cool.
14:35:27 <samaila> HiRUSS, I need to join today's WG meeting
14:35:54 <russdeffner> ok, next step - any objections to that minor wording change for "at least" monthly meetings?
14:36:06 <russdeffner> Hi samaila
14:36:33 <hot_slack_bot> <p.ulbrich> no, "at least" sounds appropriate
14:36:53 <hot_slack_bot> <p.ulbrich> just would add the Slack disaster-mapping channel as it's become our default comm channel
14:37:05 <samaila> ok see you next
14:37:36 <russdeffner> yes, I was looking at that as well, it's both our non-response and response main channel
14:39:02 <hot_slack_bot> <p.ulbrich> HI Samaila, if you intended to join the activation WG, you are at the right place
14:39:49 <russdeffner> Ok, I added Slack, look ok?
14:40:52 <hot_slack_bot> <p.ulbrich> yes, and #idea also to "Tools"?
14:40:57 <russdeffner> oh, not to the tools section yet :)
14:41:53 <hot_slack_bot> <p.ulbrich> looks good #accept
14:43:11 <russdeffner> cool, also caught some URL changes, etc. in there
14:43:45 <hot_slack_bot> <p.ulbrich> also saw the addition regarding the private channels for incidents and topics
14:43:51 <hot_slack_bot> <p.ulbrich> is that email?
14:45:25 <russdeffner> No, just that we have the ability to say set-up a room just for the disaster coordination team to talk without the other 500 people in disaster-mapping
14:46:02 <hot_slack_bot> <p.ulbrich> ah ok :slightly_smiling_face:
14:46:44 <russdeffner> I thought we might need to during the Fall 2017 craziness, but never did
14:47:24 <hot_slack_bot> <p.ulbrich> the updates to AWG look good #accepted
14:48:16 <hot_slack_bot> <p.ulbrich> BTW - today is a holiday in the UK, which may explain the low attendance from this side
14:48:18 <russdeffner> Yes, I'm really happy with it now
14:48:35 <russdeffner> #accept ToR draft
14:49:25 <russdeffner> It's also just been a really busy week around HOT, so not too suprised (and our late notice :) )
14:50:27 <russdeffner> Ok, let's bust through a few more agenda items...
14:50:45 <russdeffner> #topic Current Activation/Imagery Coordination
14:50:48 <hot_slack_bot> <p.ulbrich> regarding the mtg platform for the AWG - I think the flow between slack/IRC and Trello seems to work
14:51:13 <hot_slack_bot> <p.ulbrich> sorry - for the next item
14:51:24 <russdeffner> ok, good; we can always adjust if you see something that can help improve
14:51:51 <russdeffner> So, it took 'a little while' to get the remaining Tonga imagery...
14:51:59 <hot_slack_bot> <ilasolthah> Thanks @p.ulbrich  I  already joined disaster_mapping channel
14:52:30 <russdeffner> Not looking to blame, but really need a better imagery request 'mechanism'
14:52:45 <hot_slack_bot> <p.ulbrich> in what way? what are issues?
14:52:50 <russdeffner> However, we seem to also have a 'bottleneck' on our side
14:53:18 <russdeffner> Biggest issue is there really is no 'process' or mech; it's just emailing the people we know
14:53:22 <russdeffner> On both sides
14:53:49 <hot_slack_bot> <p.ulbrich> so people at DG, Airbus etc?
14:53:54 <russdeffner> The scenario here was also hampered by it not being a 'big news type response'
14:54:27 <russdeffner> but I want a way to request imagery for any incident and get a yes/no (and delivery in reasonable timeframe)
14:55:57 <russdeffner> And, then when we have it; if it needs HOT imagery resources, I again need a yes/no and ETA not having to ping slack, emails and maybe phone someone to get that
14:56:11 <hot_slack_bot> <p.ulbrich> how could that be improved? We had quite some issues with getting imagery from DG for our project here, even though we were paying for it
14:56:42 <russdeffner> Well, it is two seperate questions I think...
14:56:52 <hot_slack_bot> <p.ulbrich> yes, on both sides, no?
14:57:16 <russdeffner> i.e. asking DG and other providers how to make a formal request and track that request
14:57:41 <russdeffner> and setting up a system for asking our folks to process/host/etc
14:58:44 <russdeffner> Probably not getting anywhere in the next minute, just want to document...
14:59:16 <russdeffner> #idea Need to formalize imagery request and coordination process both with external providers and internally around OAM
14:59:19 <hot_slack_bot> <p.ulbrich> not sure how this could be improved on the provider side
14:59:29 <hot_slack_bot> <p.ulbrich> on what basis do they provide it?
15:00:12 <russdeffner> well, in this case we knew exactly the 2 scenes we wanted and still took many weeks to get
15:01:11 <russdeffner> But I am still racing deadlines today, so need to leave
15:01:27 <russdeffner> any last thoughts before I end the bot
15:01:29 <hot_slack_bot> <p.ulbrich> i guess the main reason is that the paid services will always be prioritised
15:01:41 <hot_slack_bot> <p.ulbrich> nope
15:01:55 <hot_slack_bot> <p.ulbrich> we can add this to the agenda for next time
15:02:10 <russdeffner> I bet the next Gorkha earthquake style response we get imagery thrown at us
15:02:38 <russdeffner> it's unfortunate we all basically need to prioritize based on press coverage
15:02:45 <hot_slack_bot> <p.ulbrich> yes, very
15:03:10 <hot_slack_bot> <p.ulbrich> maybe twitter "lobbying" could help
15:03:45 <russdeffner> on that note, thanks for coming everyone and we'll keep doing our little parts until next time
15:03:52 <russdeffner> #endmeeting