A Message about Scheduling and Inclusivity¶
This blog post is a little different from our usual updates, as we wanted to address an issue that came up on several occasions since we announced the dates for this year’s conference.
The short version¶
We are aware that this year’s Write the Docs Prague conference is in conflict with the Jewish New Year holiday. This conflict was known at the time of scheduling, but we had to make a very difficult compromise due to a combination of circumstances around these dates, such as school breaks, weather in Prague, global conference workflow, and conflicts with other holidays (details in the long version).
Even though we took the time to respond to questions sent to use by email or Slack since the announcement, we should have communicated a public accountability statement about the scheduling process and an explanation of this choice, at the same time that we published the dates.
While we cannot guarantee that future conference dates will never have any conflicts, we have taken the community feedback to heart and will continue to our best to make the dates as inclusive as possible, and to communicate clearly and on time in cases where we are unable to avoid scheduling conflicts.
The long version¶
The global Write the Docs team supports major conferences in both Portland and Prague, and also mentors smaller events throughout the year and maintains the community infrastructure.
Since we started organizing the Prague conference in 2015, September has been the month of choice, specifically around the middle of the month.
When we scheduled the conference dates for Prague we considered the following key factors:
- September is far enough from the Portland conference (which is held in May each year), which helps the team to load-balance preparation activities for both conferences.
- August (and the first week of September) conflicts with the school summer holidays, which would exclude attendees who have school-aged children.
- The only bank holiday in the Czech Republic that month is on September 28, and there are no other public holidays in neighboring European countries.
- Mid-September doesn’t conflict with any major European conferences in the region (primarily PyCons and open-source conferences).
- The weather from the end of September takes a turn for the worse in Prague (and in most of Europe), and we want attendees to have a good experience of the city and not just the conference venue.
- The global core team’s yearly offsite and retrospective happens immediately after the Prague conference, and we need to allow for enough time before the end of the calendar year to wrap-up and start planning for the following year.
What happened this year¶
When we looked at the calendar to choose the dates for the 2018 conference, we saw that the Jewish New Year holidays span most of September. This does not occur every year, but this year it was extremely difficult to decide on dates in September, since no matter which date we chose, it would conflict with one of the holidays.
When we weighed this problem against the key factors that we use to determine the dates each year, we knew that we had to make a decision that would exclude some people from being able to attend. We weren’t happy about this decision, but if we moved the conference to any other month, or even to the first weekend of September, we would run the risk of excluding different groups of people, or not being able to run the conference at all this year due to organizational meltdowns.
What could we have done better¶
Our failure to communicate the scheduling decision and conflict explanation at the time of announcing the conference dates led to multiple inquiries from portions of our community, who felt as if they might have been overlooked, or worse - not welcome at our events. This was absolutely not our intention, and we are sorry that our actions had this impact on parts of our community.
We owe it to our community to adhere to our philosophy of inclusivity in how we run our events, and if we are unable to choose the most inclusive option for our attendees, we should communicate about it promptly and transparently.
After we announced the dates, we received and handled several inquiries by email or Slack messages from community members who questioned the date selection and asked to reschedule, but by the time we announced the dates we already had the venue contracts signed so it wasn’t possible to make a change.
Regardless of the actual scheduling problem, the fact that we received inquiries should have been a warning bell for us, as we saw in the past that for every person who writes to us with a question, there must be dozens more who wouldn’t feel comfortable writing to us. Rather than keeping our responses in the private channels, we should have made this public accountability statement to address this much sooner.
What will we do better in the future¶
Firstly, we want to acknowledge that in 2019, the Jewish New Year holidays period begins in October, so there is no expected conflict with any dates we might choose in September. That said, we cannot guarantee that any future conference years (Prague, Portland, or elsewhere) will not conflict with anything ever again, as this is a long-term venture there are sure to be more difficult decisions that we’ll have to make down the line.
What we can promise is:
- if conflicts arise, to take our past conflicts into account so that we can prevent the same group(s) from being excluded during consecutive years
- to improve our transparency around our scheduling practices, so that if we must make another difficult decision in the future, we will inform you, the community, our documentarian family, of the process and considerations involved
Thank you for being you¶
We love Write the Docs because it’s where documentarians from all walks of life feel welcome. Sometimes we make mistakes that cause parts of our community to feel excluded, and it’s our responsibility to own these mistakes and learn from them.
We want to express our gratitude to the community members who took the time to discuss the impact of our actions (and inactions), and we hope that this blog post will help to shine some light on how and why we ended up with these conference dates this year for the benefit of folks in our community who might not feel comfortable reaching out and asking us directly.