Move all files to 2019/
This commit is contained in:
parent
f59a1843de
commit
0b536af737
94 changed files with 0 additions and 0 deletions
|
|
@ -1,24 +0,0 @@
|
|||
---
|
||||
layout: default
|
||||
twitter:
|
||||
url: https://twitter.com/drupalcampbris
|
||||
update_text: ~
|
||||
use: [sessions, speakers]
|
||||
---
|
||||
{% block content %}
|
||||
<div class="markup tw-w-full tw-max-w-2xl tw-mx-auto tw-my-12 tw-px-4" markdown="1">
|
||||
## DrupalCamp Bristol 2019 Cancelled
|
||||
|
||||
We’re incredibly sad to have to announce that we (the DrupalCamp Bristol organisational committee) have decided to cancel DrupalCamp Bristol 2019.
|
||||
|
||||
Our aim as a conference is to represent and appeal to the whole of the Drupal community. We set ourselves a high bar this year, in terms of attendee numbers and in the range and diversity of speakers and talks, and unfortunately we failed to reach that bar.
|
||||
|
||||
We have not taken this decision lightly, but we felt that cancelling rather than proceeding well below our own self-imposed standards was the right thing to do.
|
||||
|
||||
We want to say thank you to everyone who has been involved in DrupalCamp Bristol this year, especially to our sponsors - Acquia, Microserve, Proctor + Stevenson, Manifesto, and Drupalize.me, and to all of the speakers and volunteers who have given up their own time to be a part of DrupalCamp Bristol. We are extremely grateful for all your support and hard work.
|
||||
|
||||
We will be having a retrospective in the coming weeks to help us reflect on what we can learn from this year and what the future may hold for DrupalCamp Bristol.
|
||||
|
||||
If you have any questions, comments or feedback, please get in touch via {{ site.email }} or on Twitter <a href="{{ site.twitter.url }}">@{{ site.twitter.user }}</a>.
|
||||
</div>
|
||||
{% endblock %}
|
||||
Reference in a new issue