#meta 2024-11-12
2024-11-12 UTC
# 
gregorlove.com created /Category:IndieWebCamp_Berlin_2024 (+102) "Created page with "<span class="p-summary">Pages for [[2024/Berlin|IndieWebCamp Berlin 2024]].</span> [[Category: 2024]]"" (view diff)
# GWG gRegor: I read the updated policy. You are missing something. If someone tests positive within 5 days of the event, did we discuss how notification should work?
# gRegor The testing section has "We encourage you to inform close contacts, should you test positive during or after the event, so that they can take appropriate precautions." which I guess we could make "organizers and close contacts" to be more clear.
# gRegor Let me know what you think will make it more clear
# gRegor I can see some ambiguity between that and the Before and After Event section
# GWG I think organizers after the event so they can advise attendees without disturbing anyone's privacy. As in, "We have been informed an attendee tested positive for COVID at our recent event. Please take appropriate precautions."
# gRegor Sounds good to me. [Joe_Crawford], any thoughts on that? ^
# gRegor what is sitedeaths
# Loqi Site deaths are when sites go offline, taking content and permalinks with them, and breaking the web accordingly https://indieweb.org/sitedeaths
[KevinMarks] joined the channel
# [Joe_Crawford] [gRegorLove] I think it’s appropriate to make someone responsible for an after action report/contact tracing. A material statement that the organizers will be as transparent as possible about sharing appropriate notification information.
claudinec, [capjamesg], [snarfed]1 and [morganm]1 joined the channel
[qubyte] joined the channel
# [tantek] gRegor++ https://indieweb.org/2024/SD#Health_and_Safety is looking quite good in general. Only two (minor) suggested improvements.
# Loqi gRegor has 59 karma in this channel over the last year (137 in all channels)
# [tantek] 1 Since the policy is quite long now (which is fine tbh, I think the details provided are helpful), I think it would help readability a lot if we simplified the "sternness" of the statements to say 3-4 verbs that have clear(er) distinct meanings. E.g. "required" is good, as in, if you don't follow this, you will be asked to leave. In addition, I think "request" could be good to indicate "should"-like things where it is strongly recommended
# [tantek] but not required. And lastly "recommend" for additional precautions we think are a good idea but no one is going to be pressuring or checking.
# [tantek] Alternatively, simplifying to just "required" (MUST) vs. "recommended" (optional) would be even easier to read. And then bolding each instance to make it clear which sentences/paragraphs are which.
# [tantek] The words / phrases to replace with one of those 2-3 include "can", "should", "asked to", "encourage you to", "no circumstances should you" for example
# [tantek] 2. "We encourage attendees to test 5 days after the event." <-- this is good summary advice. From what I have read on various health guidelines websites, the guidance is a bit different if symptomatic, anywhere from test immediately if symptomatic, to test 2d after symptoms arise, or both if you have enough tests. If you only have one test and you're symptomatic, I've seen general guidance to wait 2d and then test.
# [tantek] Not sure how to best add this to the current text but thought it was worth mentioning as a possible area for improvement (testing sooner if you are symptomatic the evening, day, or two days after the camp)
# [tantek] of these two, the first (1) is more important IMO. The clearer the language around what's required vs recommended, the greater chance of successful well-intentioned compliance in my experience.
AramZS, gRegorLove_, gRegorLove__, [manton], [mattl], aelaraji9, barnaby, sebbu2 and jimw joined the channel
# sarajaksa.eu edited /2022/Düsseldorf/Demos (-18) "/* Unknown 2 */ add my name to my demo" (view diff)
# sarajaksa.eu edited /writing (+74) "/* Homebrew Website Club - Writing Edition */ Adding the link to the writing HWC that James was hosting" (view diff)
# sarajaksa.eu created /cocreating (+638) "Creating a quick page about cocreating in response to our session this weekend" (view diff)
# sarajaksa.eu edited /2024/Berlin/collab (+31) "/* See Also */ Adding some wiki links to the Berlin 2024 session" (view diff)
# tantek.com edited /Planning (+231) "/* Dusseldorf */ maybe Trivago, other past venues" (view diff)
# gRegor Thanks [tantek], will take a closer look later today. At the risk of making the section a bit longer, maybe a definitions section like https://2023.northbaypython.org/health-and-safety-policy. Specifically looking at "require", "expect", and "encourage"
[aciccarello] joined the channel
# loqi.me created /indieweb_newsletter (+38) "prompted by [aciccarello] and redirect added by [aciccarello]" (view diff)
# [mattl] I do really like the NB Python policy. Josh and Chris have been very prominent in pushing for safety at events.
# [tantek] In hindsight I should have made a separate subpage for the IWC Berlin Health policy because it did get quite long
# tantek.com edited /email (+95) "/* mailbox.org */ link to a separate article for creation, based in Germany, Wikipedia link" (view diff)
# tantek.com edited /email (+216) "/* Email Services by Type */ incorporate indieweb examples under each service, sort by number of IndieWeb examples and recommendations thereof" (view diff)
gRegorLove_ joined the channel
# [tantek] capjamesg[d]++ 🙂
# Loqi capjamesg[d] has 23 karma in this channel over the last year (207 in all channels)
[tw2113] and [pfefferle] joined the channel
# tantek.com edited /CCPA (+310) "/* IndieWeb examples */ split into Service examples, call for IndieWeb Examples of use of CCPA deletion requests" (view diff)
# kaja.sknebel.net edited /User:Kaja.sknebel.net/upcoming-hwcs (+178) "update from events.indieweb.org" (view diff)
# [mattl] [tantek] I have attempted to put some of the grand email strategy on here.