Open joshsimmons opened 1 year ago
This is a fork of the nbpy policy (#3). The key differences are:
With that in mind, I propose the following grading:
I would agree with all of the levels listed aside from:
* **Tests**: No policy, could be increased to "efforts made" if the conference commits to providing tests to people with financial need
The Event Badging Standard v2023-01 states: No Policy: No mention of tests.
We have clearly included language around tests and testing. If the intention of PHP is to have conferences provide tests, then the language of the badging standard needs to be updated.
@altsalt per https://publichealthpledge.com/badging
The badging standard also states:
Efforts Made: Tests are made available and strongly recommended. No Policy: No mention of tests.
At the moment, the badging standard has no middle ground between "no policy" and "efforts made". The name "no policy" is somewhat unfortunate there. It should probably say "no enforceable policy" or something like that, to include cases like yours where clearly there's mention in the policy, but the policy doesn't provide a guarantee of (some level of) protection to attendees.
With that in mind, "no policy" means anything between "no mention of tests" and "tests are made available and strongly recommended". At the moment, you only "strongly recommend" tests, which is not enforceable.
In other badging discussions (e.g. #1), a commitment to provide tests for attendees with financial need was sufficient to meet the "tests are made available" criterion. This was to provide flexibility for events with budgetary constraints such as yours.
@altsalt @chrisjrn Thank you both so much! You two have spotted an opportunity for improvement with the badging standard itself.
Here's my proposed path forward: let's go through the motions of this process, issue an initial grade, confirm SeaGL as a pledge signatory, and leave open the possibility of updating the grade in light of (1) improvements w/r/t tests by SeaGL, and/or (2) the next version of the badge standard approaching this specific measure with more nuance.
And in terms of public comms – because we're not trying to make anyone who is putting in the effort look bad – if you'd like, we could limit our announcement posts to the status of SeaGL as a signatory, and wait on the badge announcement until after one or both parties here get a few additional ducks in a row.
How does that sound?
Generally sounds good to me, I just worry about being construed as having "no mention of tests" which is clearly wrong.
We will of course upgrade things if we receive a sponsor who is interested in supporting these measures.
Thanks for working through ways to make conferences more accessible and healthy.
@altsalt Heya, I'm beginning to take a different, lighter-weight approach to the Public Health Pledge – one with less process and gatekeeping, and more recognizing people and teams who are putting in the work.
Do you reckon you and the rest of the SeaGL team would be open to being recognized as a signatory to the pledge?
We are likely going to be changing our policy for this year. The lack of any sort or recognition last year was a bummer. I'll bring it up again and do think that SeaGL the org would be up for participating, but I know that there are individual organizers with reasons not to sign.
Understood, and I'm sorry for that. This is a one person operation and being laid off last year was a huge setback for all of my volunteer work. I understand that doesn't make things better, though.
Whatever it is you all decide to do, I hope that you maintain high standards to make the event as safe and inclusive as possible.
Event Name: SeaGL Link to the Event Website: https://seagl.org Point of Contact: Wm Salt Hale @altsalt
Signing the Pledge: Yes Links to Key Pages: https://seagl.org/health_and_safety_policy
Masking:
Vaccines:
Tests:
Ventilation:
Alternatives:
Reviewing against badging standard v2023-01