If you are not attending WCSF this year, you can ignore this post. If you are coming and planning to participate as part of the accessibility team, please click through and read it all. 🙂
Point Person
We need one person from each team to handle some general planning and communication around WCSF stuff so we can have one person per team to talk to as we confirm things or if there are any issues. It could be the team rep or any trusted team member with some time on their hands, who will be available if we need them during the event. Without wanting to discriminate based on accessibility issues (here of all places!), I will say that the point person should probably be sighted, since one of the things they’ll need to do is confirm we have the right printed signs in the right places during the contributor track on Sunday and during the community days. If y’all could figure out who will be on point as this contact person for the team around WCSF stuff, that would be great. Let me know who it’ll be by tomorrow if you can and I’ll start funneling communication through them.
Contributor Track
On Sunday, the downstairs room will be used for the Contributor Track. Think Contributor Day but with rotating spiels from each team on how to get set up to contribute and a quick overview of the projects you’re asking people to help with that day. We’ll split the room into two parts — the back part part will be partitioned off to be a little classroom for the how-to spiels (which we’ll capture on video for re-use at other events and online, but will not be livestreaming), and the front part where you enter the room will be all tables and chairs for people to sit together and work on contributions (like at last year’s Contributor Day) all day, with the exception of when Matt’s presenting the State of the Word. We’ll have table signs to identify where each team is gathered so people know where to go.
To figure out when to schedule each team’s how-to part and how to divvy up the tables we need to know:
– Does the short intro format work for accessibility? Can you give a general “how to get involved with this team” spiel that is useful without getting into specific details about specific accessibility things? The timing for these intros is very limited, so want to be sure we can do it for this team in a way that makes sense.
– If we do it, who will be giving the intro/how-to bit for accessibility team (, and how much time is needed for that part? Shorter spiels are better, because we have to fit in all the teams, and you can obviously go deeper with the people who need to learn when you’re at the tables with them.
– Is there anything participants should install at home before the event, or can they just turn up and start? The wifi is not going to like having people try to download software or checkouts — the livestream will get hiccuppy very fast if that happens — so I’d like to get a list of any/everything potential participants should download, install and/or gather in advance.
Team Meetup
I think you all may have already been talking about what you want to work on during the team meetup days. For the sake of tracking whether or not the summit/meetup format this year was successful, I need to collate all the goals/agendas in advance so they can be compared with the outcomes. I’d like the person chosen as the WCSF point person for the team to be responsible for getting me the final goals/agenda for the meetup days sometime this week.
Thanks!