Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
daisylb committed Jun 2, 2024
2 parents e8520fe + 0a338de commit 39b31c2
Show file tree
Hide file tree
Showing 5 changed files with 147 additions and 70 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ jobs:
name: Build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3.3.0
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "22.2.0"
- uses: pnpm/[email protected]
Expand Down
53 changes: 0 additions & 53 deletions src/content/pages/attend/_assistance.mdx

This file was deleted.

49 changes: 49 additions & 0 deletions src/content/pages/attend/assistance.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
title: Financial Assistance
order: 9
---

import Button from "../../../components/Button.astro"

# Financial Assistance

Thanks to the support of our sponsors, we have budget set aside for providing financial assistance to PyCon AU speakers who might otherwise find it difficult to attend.

Financial assistance grants take the form of reimbursement for expenses incurred in getting to and presenting at the conference. These expenses can include:

- Flights or other transport to Melbourne
- Accommodation costs
- Other costs associated with attending such as a support worker, child care or a substitute teacher.

Please ask only for what you need in order to be able to present at the conference and highlight any opportunities you would use to save costs, such as finding cheaper accommodation further from the city (public transport provides easy access to the venue).

## Application

To apply for financial aid please fill out the application form linked by the button below. Applications will be approved progressively so please apply early and your application may be approved early. If the budget has not been exhausted the application process will be reopened.

To ensure equal consideration, please submit your application by **1 August, 2024**.

Submissions received after this date may still be considered if there is additional available funding.

<center>
<Button
type="chonk"
href="https://docs.google.com/forms/d/e/1FAIpQLSf3AHcZajFVnz-4WSHeBI6qNmmJTe1PgPRM6i-soEDiyJQ5lA/viewform"
>
Apply for financial aid here
</Button>
</center>

## Reimbursement process

If granted assistance, you will still be expected to organise and purchase travel and accommodation yourself and await reimbursement. You will be given a maximum amount of reimbursement based on the assistance you requested. Once assistance is granted, you can start making bookings and sending us your receipts.

If you have any questions about financial assistance please contact us at [[email protected]](mailto:[email protected])

## Financial assistance for attendees

We are hoping to provide financial assistance for attendees who might otherwise find it difficult to attend. If we are able to provide it, attendee financial assistance would include either a free conference ticket (at the enthusiast level) or a conference ticket plus additional reimbursed expenses as described above.

Note that we will only be able to consider applications for attendee financial assistance if you are travelling from within Australia, or from a location in the Pacific/Oceania region that does not have a more appropriate local PyCon.

Our ability to provide this will depend entirely on how much [sponsorship](/sponsor/) we receive, and we will announce the availability financial assistance along with instructions on how to apply if and when we are able.
31 changes: 17 additions & 14 deletions src/content/pages/program.md → src/content/pages/program.mdx
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
---
title: Program
# layout: "../layouts/Page.astro"
---

<!-- import Button from "../components/Button.astro" -->
import Button from "../../components/Button.astro"

# PyCon AU call for proposals

Expand All @@ -17,9 +16,11 @@ The PyCon AU call for proposals (CFP) is open from June 1, 2024 until the end of

You can submit your proposal through our online portal, Pretalx. A large button linking to the portal in a calming, brand-appropriate green colour will appear on this page when the call for proposals opens.

<!-- <Button type="chonk" block href="https://pretalx.com/pyconau-2024/cfp">
Submit to the PyCon AU CFP!
</Button> -->
<center>
<Button type="chonk" block href="https://pretalx.com/pycon-au-2024/cfp">
Submit to the PyCon AU CFP!
</Button>
</center>

**If you can't afford to attend PyCon AU or don't have an employer that will sponsor your travel, please submit anyway! PyCon AU will have a financial aid program to assist attendees who otherwise couldn't make it to the conference, and we will prioritise speakers in that process.**

Expand Down Expand Up @@ -50,25 +51,27 @@ This year, PyCon AU is partnering with the [Journal of Open Source Software (JOS

_Academic abstract submission will not increase your chances of having your talk selected for presentation at PyCon AU._ This is intended as a way for participants to further engage with the conference and build their academic track record. If your proposal is accepted as part of the PyCon AU program, we will work with you to handle the JOSS submission, and upon acceptance it will become part of a new PyCon AU collection.

Your academic abstract submission must fulfil basic requirements for publication in JOSS:
* Your submission must describe open source software ([as defined by OSI](https://opensource.org/osd))
* Your software must have an obvious research application
* You must be a major contributor to the software
Your academic abstract submission must fulfil [basic requirements for publication in JOSS](https://joss.theoj.org/about#submitting):

- Your submission must describe open source software ([as defined by OSI](https://opensource.org/osd))
- Your software must have an obvious research application
- You must be a major contributor to the software

Additionally, any submissions must comply with the PyCon AU [Code of Conduct](/conduct), as with their accompanying presentation.

For this academic submission, you must provide:
* A title
* Authors names and affiliations of all authors
* Academic abstract text itself, up to 500 words.

- A title
- Authors names and affiliations of all authors
- Academic abstract text itself, up to 500 words.

You do not have to worry about adding references at this stage (although a few key references might help us evaluate the work - we may not have a reviewer on hand who works in your field).

If your proposal moves forward, members of the PyCon AU academic program committee will work with you to develop your academic abstract submission into a JOSS paper that complies with the journal standards.

We will also help with review and editorial tasks to speed up the progress of your submission.

Our goal is to have all PyCon AU papers in press by the time the conference kicks off, but obviously this is subject to many factors.
Our goal is to have all PyCon AU papers published by the time the conference kicks off, but obviously this is subject to many factors.

Please make sure you provide the names and academic affiliations for all authors on the submission. This is important for us to evaluate conflicts of interest and maintain the integrity of the review process.

Expand Down Expand Up @@ -269,4 +272,4 @@ or

> This talk contains images and brief mentions of bushfires and other natural disasters.
Content warnings don't exempt you from the code of conduct. They exist to warn audiences of things that comply with the code of conduct, but might be distressing anyway.
Content warnings don't exempt you from the code of conduct. They exist to warn audiences of things that comply with the code of conduct, but might be distressing anyway.
80 changes: 79 additions & 1 deletion src/content/pages/safety/covid.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,82 @@ PyCon AU 2024 is a primarily in-person event being held in a period where COVID-

We all have a responsibility to keep each other safe, including the people in our community who are at higher risk than us. The PyCon AU 2024 organisers take the risk of COVID-19 seriously, and expect all attendees to do the same.

We will have more to announce about our COVID-19 policy soon. For now, take a look at the [2023 COVID-19 policy](https://2023.pycon.org.au/safety/covid/); this year's is likely to be similar.
## Why we have this policy

At PyCon AU, we're applying a policy that goes above and beyond the legally required minimum. We're doing this for a few reasons.

One is that **conferences like ours are uniquely high risk**. We're coming from all over Australia and the world, and gathering together indoors in a large group for the entire day, across multiple days. This means that the risk is much higher than a quick trip to the grocery store.

The second reason is that **not everyone faces the same risk from COVID**. There are valued members of our community who are more likely to catch COVID, or more likely to experience severe outcomes from a COVID infection. Those people have every right to participate in events like ours, and **they're relying on us&mdash;all of us&mdash;to keep them safe**.

The final reason is that **there is no single perfect mitigation for COVID**. Many of us will be familiar with "defence in depth", the practice of layering multiple imperfect protections against something, with the result being stronger than the sum of its parts. That's why we're requiring mask wearing **and** encouraging vaccination **and** doing the best we can to provide well-ventilated spaces, rather than just relying on any one of those factors in isolation.

## Key terms used in this document

- **Commitment** is something that we are promising to you.
- **Requirement** is something that you will need to do in order to attend the event. Requirements form part of the conditions of sale of your ticket. Attendees who break these requirements may be asked to leave the event without a refund.
- **Recommendation** is something that we won’t enforce, but we strongly suggest you do.
- **Attendees** include the core team, specialist track organisers, volunteers, PyCon AU AV team members and volunteers, speakers, sponsor representatives, regular ticket holders (paid or unpaid), and anyone else present on site (except venue staff and subcontractors).

## Mask wearing & physical distancing

**Requirement:** all in-person attendees must wear masks indoors, except when:

- actively eating or drinking - you may briefly raise your mask to bite or sip, but please replace it when you are done with that action
- presenting on stage
- communicating with somebody who needs to be able to see your mouth, for instance because they are deaf or hard of hearing. If you are in this situation, please ensure that you maintain any appropriate physical distance from the person to whom you are communicating, as per the distancing requirement below.

The mask policy applies to all conference days, including the developer sprints and workshops running on the Monday and Tuesday of the event.

Please note: we have requested that event staff employed or contracted by the venue also wear masks, but we cannot enforce this for those people.

**Requirement:** Masks must be fitted, and cover the nose and mouth.

Wearing a mask that doesn’t fully cover both your nose and mouth does not offer any protection. For this reason, wearing a mask improperly will be treated the same way as not wearing a mask at all.

**Recommendation:** We recommend using a mask that is tested against AS/NZS 1716:2012 P2 or international equivalents.

**Recommendation:** We recommend wearing a mask in public indoor spaces wherever possible travelling to the event, during your stay in Melbourne, and travelling home.

**Requirement:** You must respect your fellow attendees’ boundaries if they ask that physical distancing be maintained.

## Vaccination and testing

**Recommendation:** We encourage all non-exempt participants to be up-to-date with COVID-19 vaccines, as it is the best way to reduce the impact of COVID-19 should you be infected during your time travelling to and attending the conference.

**Recommendation:** We strongly recommend that attendees perform a rapid antigen test (RAT) before attending the event, especially if you are aware you have recently been exposed to COVID-19, or if you have recently been unmasked in a group setting.

## Exemptions to these rules

**Commitment:** Exemptions to individual requirements will be provided for attendees who have a genuine medical need for them.

If this is you, please contact us at [[email protected]](mailto:[email protected]), and we'll sort something out for you. If you've already purchased a ticket, include the 5-character order confirmation code in your email to us.

Some attendees may have non-contagious chronic or acute conditions with symptoms that resemble those of COVID-19, colds, or the flu. In particular, allergy symptoms can resemble COVID symptoms.

**Requirement:** We expect you to respect your fellow attendees’ privacy. In turn, we ask all attendees that you take appropriate precautions during the event so that you can be confident that you are protecting your fellow attendees.

## Remote participation options

PyCon AU 2024 is an in-person event. However, we know that some members of our community might not be able to attend in person for a variety of reasons.

**Commitment:** We will provide an online ticket tier, which will provide access to live streams of talks, as well as an online space to communicate with fellow attendees. Please note that PyCon AU is not a hybrid conference, and does not have the resources to ensure that the remote participation experience will be equivalent to the experience of attending in person. By providing a remote participation option, we hope to ensure that our community can still benefit from the content presented at the event.

## Displaying symptoms or testing positive

**Requirement:** We require you to not attend the conference if your presence would create a risk of exposure to communicable diseases (such as COVID-19) to your fellow attendees. Risk factors include:

- Experiencing known COVID-19 or flu-like symptoms, in ways that are unusual to you
- Testing positive to COVID-19 during the conference, or before the conference without subsequently testing negative (for example, by 2 non-positive rapid antigen tests taken 48 hours apart, or a negative PCR test)
- Experiencing extended close contact with someone who has tested positive to COVID-19, influenza, or other communicable respiratory infections

**Requirement:** If you test positive, or you’re displaying symptoms of COVID-19 in ways that are unusual to you, you may not attend the event in person.

**Commitment:** If you test positive, or you’re displaying symptoms of COVID-19, we’ll refund your ticket, or convert your ticket to online attendance and refund the difference.

## Changes to this information

**Commitment:** All of the **commitments** from us, and **requirements** we expect from you and your fellow attendees, will only be changed if it is to increase protections.
The exception to this is if circumstances outside our control require us to loosen protections. If this happens, we’ll let all ticket-holders know. If you no longer feel comfortable attending as a result of such changes, contact us ([email protected]) and we’ll refund your ticket, or convert your ticket to online attendance and refund the difference.

Portions of this document are based on the [North Bay Python Health and Safety Policy](https://2024.northbaypython.org/health-and-safety-policy).

0 comments on commit 39b31c2

Please sign in to comment.