Humanitarian OSM Team/Working groups/Community/2015-01-10

From OpenStreetMap Wiki
Jump to: navigation, search

Meeting of the HOT Community Working Group on Saturday, 10th January, 2015 at 13:00 UTC


  • Finalising Terms of Reference bullet points
Blake raised one last question about the diversity statement and said he would make a suggestion on the talk/discussion page.
Note these are now at Humanitarian OSM Team/Working groups/Community/TOR and ready to be shown to the community and board
The functionality for these is now in place.
  • HOT Announce only email list
Created, soon to be launched by Communications WG
  • 2014 Contributor Thank You blog post
Need to get contributor info from the the Tech WG
Suggested maybe we list literally every 2014 contributor on a wiki page for part of the thank you - "2014 Contributor Wall"
  • Other info about new community members from the TM
Welcome letter Training WG wrote, suggested we send jointly from Community and Training WGs
Should let Tech WG know what sort of member info we would like to have for Community WG follow up with new contributors.
  • Determine regular meeting schedule, suggested every 2 weeks


Jan 10 14:01:13 BlakeGirardot: Hi all.
Jan 10 14:02:35 heatherleson: morning
Jan 10 14:04:39 BlakeGirardot: Hi heatherleson I am here for the meeting, just finish up a quick thing here locally so I will be a little behind for the first few minutes
Jan 10 14:06:23 heatherleson: me too
Jan 10 14:06:25 heatherleson: Hi blake
Jan 10 14:06:30 heatherleson: Looks like Harry is a bit late
Jan 10 14:06:39 heatherleson: Anyone else here for the community meeting>
Jan 10 14:07:14 BlakeGirardot: I know Russ mentioned he was going to try to attend as well
Jan 10 14:07:27 heatherleson: here is our wiki page -
Jan 10 14:07:29 heatherleson: all good
Jan 10 14:07:31 heatherleson: the agenda
Jan 10 14:07:40 heatherleson: 1. TOR - approved? I think so
Jan 10 14:08:14 heatherleson: 2. fyi on the Resolution process which the Board and Russ plus community reviewed
Jan 10 14:08:23 heatherleson: gotta go look at Harry’s note for the other items
Jan 10 14:08:23 heatherleson: sec
Jan 10 14:11:18 heatherleson: 3. Member profiles on the website -
Jan 10 14:11:51 heatherleson: 4. other business
Jan 10 14:12:12 BlakeGirardot: Ok, cool. I am just catching up with the resolution process quickly
Jan 10 14:12:15 heatherleson: Blake - you have been doing such a tremendous job with the training and mentorship on the mailing list. This is so great
Jan 10 14:12:17 heatherleson: nod
Jan 10 14:13:17 heatherleson: if you are here for the HOT community meeting, we are reviewing the following links
Jan 10 14:13:25 heatherleson:
Jan 10 14:13:30 heatherleson:
Jan 10 14:16:45 heatherleson: the page that needs a refresh -
Jan 10 14:17:33 heatherleson: Blake, I would be happy for any input /edits on the resolution process
Jan 10 14:19:10 BlakeGirardot: I don't have any at the moment, my only comment so far is: Really nice
Jan 10 14:22:54 heatherleson: thank you. we spent so much time on that. Hopefully we never have to use it but if you encounter a time where you think it might help, please feel free to share
Jan 10 14:22:58 heatherleson: ok next
Jan 10 14:23:16 heatherleson: The Terms of reference is likely firm by now, but can you take a look at it.
Jan 10 14:23:17 BlakeGirardot: Yes, I really feel better knowing it is there.
Jan 10 14:24:21 BlakeGirardot: I like our ToR as well.
Jan 10 14:25:12 heatherleson: ok great
Jan 10 14:25:22 BlakeGirardot: Well actually, I would reopen just a couple of things in our ToR
Jan 10 14:25:43 heatherleson: next topic. The wiki and website have membership profiles which are not really used
Jan 10 14:25:56 BlakeGirardot: I'm sorry, can I raise just one issue
Jan 10 14:25:59 BlakeGirardot: on the ToR
Jan 10 14:26:13 heatherleson: of course, please
Jan 10 14:26:17 BlakeGirardot: "and growing the diversity of our community (in terms of gender/age/location) "
Jan 10 14:26:38 BlakeGirardot: the list of things, gender/age/location is leaving some people out
Jan 10 14:26:55 BlakeGirardot: I am mostly thining of the whole of LGBTQ
Jan 10 14:27:02 heatherleson: yes, I think you are right. can you edit it
Jan 10 14:27:27 heatherleson: hm
Jan 10 14:27:42 heatherleson: I was thinking about the standard canadian phrase
Jan 10 14:27:50 BlakeGirardot: I do not really know the best way to fix it and be as inclusive as we really are
Jan 10 14:27:52 heatherleson: about inclusion
Jan 10 14:29:18 heatherleson: how about “HOT is a diverse community. We aim to grow in an inclusive manner in terms of gender, age, location, and diverse lifestyles”
Jan 10 14:29:19 heatherleson: hmm
Jan 10 14:30:38 BlakeGirardot: I am going to have to think about it, as long as we are ok with revisiting it we can move on to the next item.
Jan 10 14:31:26 heatherleson: ik
Jan 10 14:31:29 BlakeGirardot: lifestyle feeds into the "it's a choice" trope so I would avoide that, like we do with "sexual preference"
Jan 10 14:31:37 heatherleson: yeah
Jan 10 14:32:03 heatherleson: I feel a bit awkward writing ‘sexual preference’ on the OSM wiki (holds back the jokes)
Jan 10 14:32:41 BlakeGirardot: Well, we are a welcoming and safe place, we haven't been shy about mentioning all of that with the OPW program on the wiki
Jan 10 14:32:57 heatherleson: kk
Jan 10 14:32:59 BlakeGirardot: and I am proud of being in a community like that :)
Jan 10 14:33:06 heatherleson: next topic
Jan 10 14:33:12 BlakeGirardot: Aye, next topic.
Jan 10 14:33:23 heatherleson: how to surface the membership and community on the website
Jan 10 14:33:46 heatherleson: I know that Harry wanted to talk membership profiles on the site (something mikel and the web team created)
Jan 10 14:33:56 heatherleson: but I would like to kick it up a bit larger
Jan 10 14:34:17 heatherleson: there were over 2500 unique contributors to the ebola response (according to the last data that Pierre pulled)
Jan 10 14:34:40 heatherleson: I know that Maning was considering how to reach out after Hagupit to thank people
Jan 10 14:35:00 heatherleson: I think that recognition and thanks parade needs to happen differently
Jan 10 14:35:16 heatherleson: maybe we could do a light touch (this is where I need some guidance)
Jan 10 14:35:50 heatherleson: maybe we should pull the data from TM2 for all the edits /contributors in 2014 and just write a thank you blog post for all their work supporting hOT
Jan 10 14:36:14 BlakeGirardot: Hmmm.
Jan 10 14:36:43 BlakeGirardot: That is a good idea.
Jan 10 14:37:04 BlakeGirardot: I like the idea of getting more data about new mappers from the TM
Jan 10 14:37:29 BlakeGirardot: Training WG was working on a welcome letter for the first time anyone checks out a task square
Jan 10 14:37:31 heatherleson: me too
Jan 10 14:37:37 heatherleson: i love that!
Jan 10 14:37:47 heatherleson: it was something that came up in the community sprints last year
Jan 10 14:38:10 BlakeGirardot: I wrote one that they agreed with.
Jan 10 14:38:38 BlakeGirardot: it has my name in it, but that can be removed, it was an attempt to make it more personal, I added it in late to the revision process
Jan 10 14:38:40 heatherleson: ok, so back to the thank you hotties blog post. would you be able to get that data? Since Harry is not here, I would want him to be ok with it. Is there anyone else we should consult
Jan 10 14:38:46 heatherleson: *reading*
Jan 10 14:39:01 BlakeGirardot: And it is a little focused on training, info for new mappers
Jan 10 14:39:40 heatherleson: I love this letter and it should be personal
Jan 10 14:39:54 BlakeGirardot: And we could send it jointly from training and community wg
Jan 10 14:39:56 heatherleson: It is super important that people feel like there are humans in a community
Jan 10 14:39:59 heatherleson: sounds great
Jan 10 14:40:40 BlakeGirardot: And the language is a little stilted because I wanted to make it easy for translation
Jan 10 14:40:44 heatherleson: more thoughts on personalization - Creative commons and Mozilla send personal notes all the time. I love it. (yes, I know the folks, but I love it)
Jan 10 14:40:50 BlakeGirardot: so simple shorter sentences.
Jan 10 14:41:22 heatherleson: Yes, it is super important to write clear language -
Jan 10 14:41:30 heatherleson: It is so important, so thank you
Jan 10 14:41:47 BlakeGirardot: So the blog post thank you
Jan 10 14:41:49 heatherleson: ok, so back to the thank you blog post. I think it will start the year off right to thank all the contributors in 2014
Jan 10 14:42:09 BlakeGirardot: Do you think a "wall of contributors" wold be ok? I mean literally list every user who edited in 2014
Jan 10 14:42:12 heatherleson: Mozilla used to do this for all the releases. Ubuntu has a dedicated page
Jan 10 14:42:18 heatherleson: I love it!
Jan 10 14:42:41 heatherleson: I think if we make it a blog post and then ask the tech working group to make it a page, then we are grand
Jan 10 14:43:03 heatherleson: One question - do you think some people would not want their OSM name on a website or a blog post
Jan 10 14:43:09 heatherleson: I want to be respectful.
Jan 10 14:43:24 heatherleson: I suppose if someone did not want it we could remove it
Jan 10 14:43:27 BlakeGirardot: I do too. Their OSM name is already on a lot of web pages
Jan 10 14:43:43 BlakeGirardot: And for sure we could take it down if they objected
Jan 10 14:43:58 heatherleson: Though, now that i think of it. instead of an HOT webpage, let’s just make it a wiki page on the osm site
Jan 10 14:44:07 BlakeGirardot: Oh thats a good idea
Jan 10 14:44:09 heatherleson: this is a bit better as it is a reference that people can edit
Jan 10 14:44:27 BlakeGirardot: In case they want another name besides their osm name, they can put it on there.
Jan 10 14:44:31 heatherleson: action list for the community call (blake and heather)
Jan 10 14:44:33 heatherleson: nice
Jan 10 14:44:53 BlakeGirardot: So, one thing about the TM
Jan 10 14:44:55 heatherleson: action 1: Tor and resolution process reviewed. Recommend firm with minor edits.
Jan 10 14:45:24 heatherleson: action 2: get the OSM contributors from TM for 2014 and write a blog post/create a wiki page with thanks
Jan 10 14:45:28 heatherleson: tell me
Jan 10 14:45:54 BlakeGirardot: pgiraud mentioned that we need to work on some
Jan 10 14:46:00 BlakeGirardot: long term directions for development
Jan 10 14:46:11 BlakeGirardot: in other words if we need things from the TM we need to get some
Jan 10 14:46:18 BlakeGirardot: of those request together
Jan 10 14:46:26 BlakeGirardot: so he can guide development in a sensible way
Jan 10 14:46:42 BlakeGirardot: so if we would like info about new users
Jan 10 14:46:50 BlakeGirardot: we need to let the TechWG know
Jan 10 14:46:58 BlakeGirardot: so they can consider it as they make longer term
Jan 10 14:47:02 BlakeGirardot: development plans
Jan 10 14:47:27 BlakeGirardot: Like maybe a report each week about new users or something so we can be sure to follow up or welcome again or something
Jan 10 14:47:39 BlakeGirardot: But not really specifics as much as "this is the sort
Jan 10 14:47:45 BlakeGirardot: of info we might like
Jan 10 14:47:49 BlakeGirardot: to have"
Jan 10 14:48:19 BlakeGirardot: So we might want to think about that and communicate it to the Tech WG
Jan 10 14:48:40 heatherleson: that is so great
Jan 10 14:48:59 heatherleson: action 3 -talk with Tech WG about the thank you parade process
Jan 10 14:49:07 BlakeGirardot: Perfect :)
Jan 10 14:49:28 heatherleson: ok, since it is just us. I am going to pull these notes and write back to the mailing list.
Jan 10 14:49:47 heatherleson: I recommend that this meeting happen every 2 weeks. Not everyone likes saturday morning.
Jan 10 14:49:56 BlakeGirardot: I like every 2 weeks
Jan 10 14:50:18 heatherleson: I personally could do late afternoon 4pm est or so as it does not cut into my work day, but this is not condusive for europe and africa/asia
Jan 10 14:50:25 BlakeGirardot: There is some adjustment for WG meeting days happening
Jan 10 14:51:01 heatherleson: action 4 - determine the best time/date for the Community Wg. it should happen every 2 weeks as we have much to do
Jan 10 14:51:26 BlakeGirardot: Do you want me to put the irc log up for this?
Jan 10 14:51:42 heatherleson: I will take action 2 and 4
Jan 10 14:51:47 heatherleson: can you help with 3?
Jan 10 14:51:50 heatherleson: yes please
Jan 10 14:52:06 BlakeGirardot: Will do on TWG and 3
Jan 10 14:52:19 BlakeGirardot: I mean on the irc log and 3
Jan 10 14:53:26 heatherleson: got it. great
Jan 10 14:53:27 BlakeGirardot: Also, do we want a Community Google Email group? Communications and Training have been using one to move some traffic off of the main hot email list. I am of mixed feelings on it, but generally think it is a good idea
Jan 10 14:53:33 heatherleson: hm
Jan 10 14:53:44 heatherleson: I am unsure that it is a good idea at this time
Jan 10 14:54:00 BlakeGirardot: It would just be for internal WG communications
Jan 10 14:54:10 heatherleson: disclosure - i think that too many sub emails fracture the community and lessen the possiblity for new folks to get involved
Jan 10 14:54:17 BlakeGirardot: For example: If I made suggestions on the TOR
Jan 10 14:54:26 BlakeGirardot: disclosure - I agree 110%
Jan 10 14:54:36 BlakeGirardot: :)
Jan 10 14:54:42 heatherleson: As well, the community has finally started to turn a corner. we need to keep the trust
Jan 10 14:55:01 heatherleson: decision - no new community channels at this time
Jan 10 14:55:02 heatherleson: :)
Jan 10 14:55:05 BlakeGirardot: But, I do recognize that
Jan 10 14:55:21 BlakeGirardot: if I would like to have discussions with others in the community wg about details on something
Jan 10 14:55:32 BlakeGirardot: I guess we do it at the meeting
Jan 10 14:55:37 heatherleson: I want it blue not yellow
Jan 10 14:55:37 BlakeGirardot: ok, cool
Jan 10 14:55:38 heatherleson: :)
Jan 10 14:55:53 heatherleson: it could be an email rabbit hole which would tick people off. yes
Jan 10 14:56:05 heatherleson: I try to send as little email as possible
Jan 10 14:56:35 BlakeGirardot: Hmm... I do too, but I have a different definition of "little as possible"
Jan 10 14:56:46 BlakeGirardot: than a lot of people
Jan 10 14:56:53 heatherleson: You post invaluable things
Jan 10 14:57:07 heatherleson: i am a fan of productive emails
Jan 10 14:57:09 BlakeGirardot: And i want to make sure we never discourage anyone from posting to the HOT list by even having discussions about "is this too much traffic" etc
Jan 10 14:57:17 heatherleson: exactly
Jan 10 14:57:26 heatherleson: a thriving community
Jan 10 14:57:33 BlakeGirardot: Because I know people are intimated now
Jan 10 14:57:45 heatherleson: I discourage myself from posting yellow vs blue emails
Jan 10 14:57:49 BlakeGirardot: Oh, well good news is there is now an announce only HOT list
Jan 10 14:57:51 heatherleson: (software thing)
Jan 10 14:57:57 BlakeGirardot: I do not know what that means :)
Jan 10 14:58:01 heatherleson: oh. I should join that
Jan 10 14:58:28 BlakeGirardot: It should be announced soon, Communications WG has an action item to describe and announce it
Jan 10 14:58:55 heatherleson: Blake, I want the website to be yellow not blue and while you are at it can the button be a little to the left. really, I have difficulty understanding why someone would think to put it offcenter. Oh, and can you make (XXX) type of yellow
Jan 10 14:59:01 heatherleson: that is what I mean
Jan 10 14:59:20 BlakeGirardot: Oh I see. Ooops. Ok, good point
Jan 10 14:59:21 heatherleson: did it enhance your life? do you feel included in my yellow vs blue email
Jan 10 14:59:23 heatherleson: :0
Jan 10 14:59:25 heatherleson: :)
Jan 10 14:59:41 heatherleson: i try to use this example whenever a conversation goes off the railes
Jan 10 14:59:45 heatherleson: anyway
Jan 10 15:00:10 heatherleson: we have actions. I am super happy to talk with you. Glad to hear about the announcement of the announcement email to be announced
Jan 10 15:00:11 heatherleson: :0
Jan 10 15:00:27 heatherleson: have a great day!
Jan 10 15:00:29 BlakeGirardot: Yes, it was a pleasure as always to see and speak with you Heather.
Jan 10 15:00:39 BlakeGirardot: Thank you very much!