Stream: social
Topic: Hiring practices
Grahame Grieve (May 28 2019 at 22:15):
Most interesting: https://www.sachajudd.com/one-direction
.. how to broaden the types of people involved here...?
Eeva Turkka (May 29 2019 at 06:30):
Oo, this brings back so many memories, I actually made one of my first webpages back in the 90s about a boyband :). And was involved in the fanfic community.
Lloyd McKenzie (May 29 2019 at 13:09):
My take-away is that there are two things we need to do:
1. increase discoverability of the FHIR community to a broader set of demographics
2. ensure the community is (and is perceived to be) welcoming of those demographics
I hope we're doing ok for #2, though we have a challenge in that our connectathons are often reflective of the relatively poor diversity of the tech sector rather than the world at large. That said, I'm part of the 'typical demographic', so I might not be aware of unwelcoming cues we're giving off unintentionally that may be barriers to some participants.
For #1, I'm not sure what to do - but we'd certainly welcome ideas/suggestions
Brian Kaney (May 30 2019 at 15:44):
@Lloyd McKenzie for #2, one idea is to consider being more outward with an inclusive code of conduct (e.g. summarize a code of conduct at the start of the event, put a markdown file in project repositories). Here's an example for an event: https://confcodeofconduct.com , and here's a guide for projects: https://opensource.guide/code-of-conduct
Lloyd McKenzie (May 30 2019 at 16:44):
We have a formal code of conduct (http://wiki.hl7.org/index.php?title=FHIR_Code_of_Conduct). However the notion of starting meetings (conference calls, connectathons, DevDays, etc.) by pointing people to it and saying "if you choose to stay and participate, you're agreeing to abide by it" is certainly something we can do. And putting it in a blurb alongside our reference to the FHIR license as part of our various Git projects is something that would be doable too. @Brian Kaney Thanks for the suggestion. @Grahame Grieve Do you see any issues with us actioning this?
Grahame Grieve (May 30 2019 at 21:20):
hard to see us mentioning the code of conduct every committee meeting. But I would like the code of conduct to be mentioned more in HL7 meeting materials and DevDays guides
Grahame Grieve (May 30 2019 at 21:21):
and it would be good to consistently mention the code of conduct in the readme files. I don't know if anyone wants to volunteer to pursue that one
Lloyd McKenzie (May 30 2019 at 22:14):
Could the IGPublisher (when run in 'HL7 mode') check for the presence of a standardize blurb in the root readme file?
Lloyd McKenzie (May 30 2019 at 22:17):
In terms of DevDays and other meeting materials, @Rien Wertheim @David Johnson - is this something we could do in the meeting brochures? (David I poked you because Mary-Ann apparently isn't cool enough to be on Zulip yet ;>)
David Johnson (May 30 2019 at 23:08):
I've shared this chat with Mary Ann. I know she's on chat.hl7.org but I don't think she's seen the yummy-goodness of dual chat sessions in the zulip app.
Mary Ann Boyle (May 31 2019 at 13:20):
I am here now @Lloyd McKenzie I want to be a cool kid too!!
Mary Ann Boyle (May 31 2019 at 13:22):
I think we could for sure add something to the brochures. it is too late for DevDays, as they have already been printed, but maybe @Rien Wertheim it could be added to the online agenda?
Lloyd McKenzie (May 31 2019 at 13:29):
We always knew you were @Mary Ann Boyle :) We should probably move the content to Confluence before linking to it in hard-copy. I thought there had been an intention to generify the FHIR code of conduct to something HL7 wide. @Grahame Grieve do you know where things are with that?
Also: GF#22641 to add this into the core spec
Grahame Grieve (May 31 2019 at 13:58):
I'm not sure the HL7 code of conduct is - there was work on one after we did ours
Lloyd McKenzie (May 31 2019 at 15:03):
@Wayne Kubick do you know?
Wayne Kubick (May 31 2019 at 15:12):
I've been wanting to update the code of conduct since I arrived, but haven't gotten to that. So it hasn't changed in 3.5 years. We adapted the acceptable use policy from FHIR. https://confluence.hl7.org/display/HL7/HL7+Acceptable+Use+Policy
Lloyd McKenzie (May 31 2019 at 15:15):
Is this something we could have in place for the next WGM?
Rien Wertheim (Jun 04 2019 at 07:51):
We'll add a code of conduct to the DevDays website for the next edition. That won't solve the problem of course. Rather try to make the DevDays speakers gallery more inclusive. That's something we try to do better every edition.
Abbie Watson (Jun 12 2019 at 22:04):
$0.02 - A lot of people find the parliamentary procedures and balloting and processes to be burdensome; but I think it's by far one of HL7's strongest strengths when it comes to inclusivity. Compared to other tech communities, it really helps temper the bad impulses that create toxic culture. That, and the overall maturity and professionalism of leadership.
Abbie Watson (Jun 12 2019 at 22:30):
I think there's a case to be made that HL7 processes ensure that there's a space for the self-educated, minority interests, non-technical, and other stakeholders to be heard.
Lloyd McKenzie (Jun 13 2019 at 00:59):
Yes - though we still have challenges performing outreach to those communities and conveying the value of taking advantage of that space. Openness to engagement doesn't necessarily automatically result in engagement - at least not in the numbers we'd ideally like to have.
Last updated: Apr 12 2022 at 19:14 UTC
