"notrainingdates": "September 12",
"city": "London",
"tourism_url": "https://www.visitlondon.com/",
- "country": "England",
+ "country": "UK",
"country_adjective": "English",
"vat": "",
"nth": "1st",
],
"cfpmembers": [
+ {
+ "name": "Andreas 'ads' Scherbaum (chair, non-voting)",
+ "company": "Adjust",
+ "img": "andreas-scherbaum.jpg"
+ },
{
"name": "Chris Ellis",
"company": "Nexteam",
"img": "chris-ellis.jpg"
},
- {
- "name": "Karen Jex",
- "company": "Crunchy Data",
- "img": "karen-jex.jpg"
- },
{
"name": "Pavlo Golub",
"company": "Cybertec",
"img": "pavlo-golub.jpg"
},
{
- "name": "Tomas Vondra",
- "company": "EDB",
- "img": "tomas-vondra.jpg"
- },
- {
- "name": "TBD",
- "company": "TBD",
- "img": "unknown.svg"
+ "name": "Stefanie Janine Stölting",
+ "company": "ProOpenSource OÜ)",
+ "img": "stefanie-stolting.jpg"
}
],
"sponsors_ataglance": [
{
- "title": "Conerence endorsement",
+ "title": "Conference endorsement",
"levels": ["yes", "yes"]
},
{
"sidebar": true,
"hasdescription": true,
"cost": "£1,750",
- "maxuses": 5,
+ "maxuses": 8,
"signup_url": "partner",
"benefits": [
{
"level": "Supporter",
"sidebar": false,
- "hasdescription": false,
+ "hasdescription": true,
"cost": "£350",
"signup_url": "supporter",
},
{
"Q": "Can the governing law be changed?",
- "A": "We are bound by <a href='https://www.postgresql.org/about/policies/conferences/'>PostgreSQL Community guidelines</a> to treat every sponsor equally. This means that all sponsors sign the same contract, under British governing law."
+ "A": "We are bound by <a href='https://www.postgresql.org/about/policies/conferences/'>PostgreSQL Community guidelines</a> to treat every sponsor equally. This means that all sponsors sign the same contract, under governing law of England and Wales."
},
{
"Q": "Where can we see the data protection regulation?",
- "A": "The <a href='https://www.postgresql.eu/about/privacypolicy/'>Privacy Policy</a> governing every of our events is available on the PostgreSQL Europe website. Outside of that, since PostgreSQL Europe and the event are both in Europe, we follow the European GDPR."
+ "A": "The <a href='https://www.postgresql.eu/about/privacypolicy/'>Privacy Policy</a> governing every of our events is available on the PostgreSQL Europe website. Outside of that, since PostgreSQL Europe and the event are both in Europe, we follow the European GDPR and UK Data Protection regulations."
},
{
"Q": "How many visitors do you expect?",
<h1>About {{ confname }} {{ year }}</h1>
<p>
This year's conference is the {{ nth }} Annual {{ confname }}, and for this
- year we are going to {{ location }}. The conference is organised by Slonik Enterprises Limited
- on behalf of <a href="https://www.postgresql.eu/" target="_blank">PostgreSQL Europe</a>, with
- participation from most of the PostgreSQL user groups around Europe, and is intended
- to be an important meeting and cooperation point for users both in and out of Europe.
+ year we are going to {{ location }}. The conference is organised by Slonik Enterprises Ltd.
+ on a non-profit basis on behalf of <a href="https://www.postgresql.eu/" target="_blank">PostgreSQL
+ Europe</a>, and is intended to be an important meeting and cooperation point for users both in and
+ out of the UK.
</p>
<p>
- {{ confname }} is a unique chance for European PostgreSQL users and developers to catch up,
- learn, build relationships, get to know each other and consolidate a real network of
- professionals that use and work with PostgreSQL.
+ {{ confname }} is a unique chance for UK and European PostgreSQL users and developers to
+ catch up, learn, build relationships, get to know each other and consolidate a real
+ network of professionals that use and work with PostgreSQL.
</p>
<h2>Great content from <i class="fas fa-microphone"></i> to <i class="fas fa-mug-hot"></i></h2>
companies as well as large multinational corporations and government organisations,
all who run their businesses on PostgreSQL.
</p>
-<p>
- The conference will run multiple parallel tracks, covering the different technical levels
- to make sure there is always something interesting for everybody.
-</p>
<p>
…and let's not forget the all important hallway track full of caffeine infused discussions
- with interesting peers from the community. We also run after hours
- <a href="{{ link("social/") }}">social events</a> at which the hallway track lasts all night.
+ with interesting peers from the community, that will most likely spill over into local
+ restaurants and pubs after the event finishes.
</p>
<h2>Something for everyone</h2>
<p>
If you are interested in sponsoring the conference, you can
<a href="{{ sponsor_signup_base }}">sign up</a>
- directly on the site. You'll be able to get the process
- started for all sponsorship levels there, and for Bronze and
- Silver you will be able to complete the whole process within
- minutes. And as always, if you have any questions or comments
+ directly on the site. As always, if you have any questions or comments
at all, please <a href="mailto:contact@pgday.uk">contact us</a>!
</p>
<p>
If you have any questions regarding sponsorship and how attendee vouchers work
- with registrations, feel free to <a href="mailto:sponsors@pgday.uk">contact us</a>.
+ with registrations, feel free to <a href="mailto:contact@pgday.uk">contact us</a>.
</p>
{% endblock %}
</p>
<p>
<strong>The submission deadline is {{ cfp.deadline|datetimeformat("%B %-d, %Y") }}
- at 24:00 in {{ location }}</strong>. Selected speakers will be notified before
+ at 23:59:59 in {{ location }}</strong>. Selected speakers will be notified before
{{ cfp.notification_date|datetimeformat("%B %-d, %Y") }}.
</p>
</p>
<p>
Program committee members are — like every other position in the
- {{ confname }} organisation — an unpaid volunteer position. There are more
- than 250 talk submissions every year so spending just two minutes per
- abstract takes in excess of 8 hours, not counting sorting, comparing and
- grouping by same topic, etc.
+ {{ confname }} organisation — an unpaid volunteer position. There are many
+ talk submissions at every PostgreSQL Europe event so committee members
+ often spend many hours reviewing submissions.
</p>
<p>
The talks are then sorted by their average score and the final selection is
Do not keep secrets or surprises from the committee. If your abstract teases
the audience about some research or a new project you are planning to reveal
during the talk, make sure you tell the committee what that is in the
- submissions notes. Your secrets are safe with us, but we need to know what
+ submissions notes. Your secrets are safe with us, but we need to know what
the content of our conference is.
</p>
</p>
<p>
Submissions about a commercial service offering, or product demonstrations,
- are not good fits for the main tracks at {{ confname }}. They are however very
- good candidates for the Sponsor Track where we do allow these types of
- presentations. If you are interested in submitting to this track, make sure
- to sign up as a sponsor at the required level first as only confirmed
- sponsors can submit.
+ are not generally a good fit at {{ confname }}, as it is primarily focussed
+ on community PostgreSQL and it's ecosystem.
</p>
<h3>Speaker Profile</h3>
within the submission process. Although your followers on social media may
know you as <em>xyz</em>, that might not be true for all the members of the
program committee and/or the conference participants. If the speaker profile
- explains why your are the best speaker for the proposed topic, that is of
+ explains why you are the best speaker for the proposed topic, that is of
tremendous value. As the profile is published for all scheduled talks, that
may also help attendees select your talk when planning their day at the
event.
<p>
We are continuously monitoring the information from the {{ country_adjective }}
- authorities, as well as their EU counterparts. We are prepared to
- re-evaluate in case the public health situation changes, but at this writing
- we feel it’s looking promising.
+ authorities, and will react appropriately based on the advice given should the
+ situation change.
</p>
{% endblock content %}
<p>
{{ confname }} is financially supported by our generous sponsors and is
- underwritten by Slonik Enterprises Limited on behalf of
+ underwritten by Slonik Enterprises Ltd. on behalf of
<a href="https://www.postgresql.eu/" target="_blank">PostgreSQL Europe</a>,
the European PostgreSQL umbrella organisation for usergroups. {#The financial record of the
conference is publicly available in the <a href="https://www.postgresql.eu/about/ga/" target="_blank">
PostgreSQL Europe general assembly financial reports</a>.#} Any proceeds from the conference
- automatically belongs to Slonik Enterprises Limited in order to support the wider PostgreSQL
- community in the United Kingdom of Great Britain and Northern Ireland.
+ are returned to PostgreSQL Europe in order to support the wider PostgreSQL
+ community in geographic Europe.
</p>
<p>
No staff at {{ confname }} receives any payment for their work, except for free
- attendance and a staff dinner.
+ attendance and, if they are lucky, a staff dinner.
</p>
{% endblock %}
</p>
<p>
You can pay using <em>Credit Card</em> (Mastercard, Visa, or American Express),
- <em>PayPal</em>, <em>Trustly</em> or <em>IBAN Bank Transfer</em>. If you have a
+ via our payment provider <em>Stripe</em>, or by bank transfer. If you have a
company department making the payments, please see the section on
<a href="#otherpayment">paying somebody else's invoice</a>. If you plan to
register many attendees to be paid for by the same person, please see the
<h3>Your Data</h3>
<p>
When registering for the conference, we will ask for personal information
- such as name and address, but also dietary requirements and t-shirt size.
+ such as name and address, but also dietary requirements.
For information on how this data is stored and processed, see the
<a href="https://www.postgresql.eu/about/privacypolicy/">PostgreSQL Europe
Privacy Policy</a>.
no longer be changed, so make sure you validate that it has any required company
information on it. If it is incorrect, you can cancel the invoice, change the
details and generate a new one. Note that once an invoice has been <em>paid</em>,
- it can no longer be canceled or changed <em>in any way</em>.
+ it can no longer be cancelled or changed <em>in any way</em>.
</p>
<p>
Once your payment has completed, you will receive a PDF copy of your receipt
<h2 id="iban">Paying with bank transfer</h2>
<p>
- We generally recommend using one of the online payment methods available
- (Credit Card, Trustly or PayPal) as these payments complete immediately and have
- a fully automated workflow that makes it much harder for mistakes to happen.
- If necessary we do have the ability to accept payments using IBAN bank transfers.
- Note that this method of payment will be automatically disabled if the event is
- close to selling out, or if the waitlist has activated, due to the unpredictable
- delays of such payments.
+ We generally recommend paying with a credit card payment as these payments complete
+ immediately and have a fully automated workflow that makes it much harder for
+ mistakes to happen. If necessary we do have the ability to accept payments using
+ IBAN bank transfers. Note that this method of payment will be automatically
+ disabled if the event is close to selling out, or if the waitlist has activated,
+ due to the unpredictable delays of such payments.
</p>
<ul>
<li>The payment reference provided on the invoice or on the payment page
<strong>must</strong> be entered correctly on the transfer. In particular,
the payment reference must be used, and <em>not</em> the invoice number.
</li>
- <li>Payment must be made in exact amount of Euros. If you are making the payment
- from outside the Euro zone, make sure that your bank submits the exact Euro
+ <li>Payment must be made in exact amount of Pounds Sterling. If you are making
+ the payment from outside the UK, make sure that your bank submits the exact GBP
amount, with no rounding. If the amount is incorrect, the payment will
<strong>not</strong> be processed.
</li>
<h1>Social Event</h1>
<p>
- As with other events like this one, the {{ year }} conference in {{ city }}
- will have a community party.
+ The {{ year }} conference in {{ city }} will not have an official social event,
+ however we encourage attendees to meet with each other for drinks or dinner in
+ local establishments to continue the hallway track after the closing session
+ of the conference.
</p>
{% endblock %}
{% else %}
<p>
Wouldn’t your company logo look good here?
- For great exposure to the British PostgreSQL community, see our
+ For great exposure to the UK PostgreSQL community, see our
<a href="{{ link("become-sponsor/") }}">sponsorship opportunities</a>.
</p>
{%- endfor %}
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="PGDay.UK 2023">
<meta name="author" content="PostgreSQL UK">
- <title>PGDay.UK 2023</title>
+ <title>PGDay UK 2023</title>
<!-- JavaScript Bundle with Popper -->
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.2.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-kenU1KFdBIe4zVF0s0G1M5b4hcpxyD9F7jL+jjXkk+Q2h455rYXK/7HAuoJl+0I4" crossorigin="anonymous"></script>
id="elephant-outline"
sodipodi:nodetypes="cccccccccccc" /></g></g></svg>
<br>
- PGDay.UK
+ PGDay UK
</h1>
<p>London, England</p>
<p>September 12, 2023</p>
projects / pgdayuk.git / commitdiff
