8000 :newspaper: Add drafts and templates · djangocon/djangocon-us-docs@a8c4dae · GitHub
[go: up one dir, main page]
Skip to content

Commit a8c4dae

Browse files
willilnwilliln
committed
📰 Add drafts and templates
1 parent 8206866 commit a8c4dae

15 files changed

+395
-0
lines changed

‎docs/drafts/coc_about.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
layout: page
3+
title: CoC - About the Code of Conduct
4+
parent: Templates
5+
---
6+
7+
# Code of Conduct - About the Code of Conduct
8+
9+
## Subject: About the DjangoCon US Code of Conduct
10+
11+
Dear [name],
12+
13+
We are very proud to have a Code of Conduct for DjangoCon US [year] that covers the conference and any conference-related events. While we hope that all attendees have a safe and enjoyable time while at DjangoCon US, we recognize that we need to be prepared. We also include emergency numbers on our website in case something happens outside of our conference because we care about our attendees' well being.
14+
15+
If you witness or experience a violation of the Code of Conduct while at DjangoCon US, please contact [these people], who are prepared to respond to CoC violations swiftly and confidentially. More information about the Code of Conduct is on our webiste at [link].
16+
17+
If you have questions about our Code of Conduct, feel free to contact me at [email].
18+
19+
Warmly,
20+
21+
[Your name]
22+
23+
[Your title], DjangoCon US [year]

‎docs/drafts/coc_complaint.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
layout: page
3+
title: CoC - Complaint About the Code of Conduct
4+
parent: Templates
5+
---
6+
7+
# Code of Conduct - Complaint About the Code of Conduct
8+
9+
## Subject: Code of Conduct at DjangoCon US
10+
11+
Dear [name],
12+
13+
Thank you for contacting us. We are prepared in case the unforeseeable happens. We also include emergency numbers in case something happens outside of our conference because we care about our attendees well-being.
14+
15+
"This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate." -- [Django's Code of Conduct](https://www.djangoproject.com/conduct/). I would highly recommend you check it out Django's CoC because every Django-related event follows it.
16+
17+
Our tech events aren't the only places which cover CoC standards. For example, [reference venue conduct standards].
18+
19+
If you have purchased a ticket and you are bothered by our inclusion of a CoC then I am more than happy to refund your ticket.
20+
21+
Regards,
22+
23+
[Your name]
24+
25+
[Your title], DjangoCon US [year]

‎docs/drafts/coc_violation.md

Lines changed: 27 additions & 0 deletions
Orig 9E88 inal file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
layout: page
3+
title: CoC - Response to Code of Conduct Report
4+
parent: Templates
5+
---
6+
7+
# Code of Conduct - Response to Code of Conduct Report
8+
9+
## Subject: Thank you for reporting
10+
11+
This template shouldn't be just copied and pasted. Every Code of Conduct incident is unique and should be handled sensitively and compassionately, and not with a form letter. This example exists to provide you with some useful wording in the unfortunate event that you need to respond to a Code of Conduct violation because coming up with the right words when you know someone has been hurt can be difficult. But again, please don't treat this example as a fill-in-the-blank form letter. Treat this example as a jumping-off point from which you can craft the right response to someone who has trusted you by reporting a Code of Conduct violation.
12+
13+
Dear [name],
14+
15+
Thank you for contacting us. We take every complaint seriously and we appreciate your trust by contacting us. I wrote up a report tonight and submitted it to our CoC committee.
16+
17+
I [have taken XYZ action], and [there was ABC result]. Essentially, [summary which maintains confidentiality].
18+
19+
I want to assure you that [attendee who violated the CoC] will [not be back to the conference/not contact you for the remainder of the conference/other].
20+
21+
I'm sorry that this happened, and I would like to thank you for letting us know.
22+
23+
Regards,
24+
25+
[Your name]
26+
27+
[Your title], DjangoCon US [year]

‎docs/drafts/drafts.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
layout: page
3+
title: Templates
4+
nav_order: 9
5+
has_children: true
6+
parent: Drafts
7+
permalink: /drafts
8+
---
9+
10+
# Templates and Drafts
11+
12+
This section contains drafts of emails, blog posts, responses to emails, and other written materials that we might need from year to year.
13+

‎docs/drafts/email-tutorials-faqs.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
layout: page
3+
title: Program - FAQs about Presenting a Tutorial
4+
parent: Templates
5+
---
6+
7+
# Proram - FAQs about Presenting a Tutorial
8+
9+
Hello everyone,
10+
11+
DjangoCon US is {{tutorial_start_date|weeks}} weeks away and I wanted to go over a few things with everyone. My apologies for the delay.
12+
13+
A few of you have asked about tutorial fees and I thought it'd be best to discuss it with everyone. I built a FAQ-like format to get the ball rolling. Please ask me anything.
14+
15+
## How much are tutorials?
16+
17+
Tutorials are ${{tutorial_price}} a person and we pay *you* {{tutorial_speaker_percent}} of that.
18+
19+
## What does the ${{tutorial_price}} cover?
20+
21+
This covers access to your room, lunch, and snacks for the day for you and your students.
22+
23+
## Why did we pick {{tutorial_speaker_percent}}?
24+
25+
Our venue charges us ${{tutorial_venue_cost_per_day}} + tax *per person* and we know you are spending a lot of time to prepare for this. {{tutorial_speaker_percent}} is close enough. The conference does not want to make money on tutorial day, we just want to cover our basic costs or come close.
26+
27+
## Am I required to buy my own day pass?
28+
29+
No. That would be really crummy to ask you to pay to give a tutorial. The day is on us.
30+
31+
## May I donate the money to the DSF, DjangoGirls, etc.
32+
33+
The money is yours to do whatever you want with. Attending DjangoCon US is not free and we are sensitive to the fact that many of you are self employed and paying your own way into the conference.
34+
35+
## Are tutorials recorded?
36+
37+
No, based on your feedback. It's also price prohibitive without charging each attendee significantly more.
38+
39+
## Will tutorials be free next year?
40+
41+
We are learning a lot this year and venue management is high on our list. Next year we are already planning on adopting an open day format with both free and paid tutorials. We have two city proposals which are game changers compared to following the model that exists today.
42+
43+
## What is our classroom size?
44+
45+
We originally were capped at 25 attendees per room but we upgraded rooms. In theory you could have up to 50 students per room but we capped ticket sales to 30. If you want us to increase the cap on your sales please email me and I'll adjust it.
46+
47+
## How many attendees have signed up for my tutorial?
48+
49+
These range from 7 to 25, but we still have two+ weeks left to market them. Email me for an exact number.
50+
51+
## Can we promote our own tutorials?
52+
53+
Not only can you promote your own tutorials, we would really appreciate if you would promote your tutorial via Twitter and social media :)

‎docs/drafts/finaid_accepted.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
layout: page
3+
title: Financial Aid - Accepted
4+
parent: Templates
5+
---
6+
7+
# Financial Aid - Accepted
8+
9+
## Subject: DjangoCon US Financial Aid Decision
10+
11+
Dear [name],
12+
13+
We are pleased to inform you that you have been approved for the following financial aid grant to attend DjangoCon US [year]:
14+
15+
- [ticket to the conference, if applicable]
16+
- [dollar amount] to aid in your travel and accommodation costs
17+
18+
You can accept this grant, after having read this e-mail completely, by [taking an action].
19+
20+
Please respond by [date]; if we don't hear from you, we'll assume you are declining your grant.
21+
22+
If you have a US bank account, we'll issue you a check. Please send us your full legal name (as it is written on your passport or state-issued ID). If you are an international recipient and don’t have a US bank account, we'll issue a wire transfer, so please arrive with your bank details so our treasurer can perform the transfer onsite at the conference.
23+
24+
If you need an invitation letter to obtain a visa, please contact [name] at [email].
25+
26+
On behalf of all of the staff: we hope to see you at DjangoCon!
27+
28+
Warmly,
29+
30+
[Your name]
31+
32+
[Your title], DjangoCon US [year]

‎docs/drafts/finaid_rejected.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
layout: page
3+
title: Financial Aid - Declined
4+
parent: Templates
5+
---
6+
7+
# Financial Aid - Declined
8+
9+
## Subject: DjangoCon US Financial Aid Decision
10+
11+
Dear name,
12+
13+
Thank you for applying for the DjangoCon US [year] financial aid program. We had many deserving applicants, but unfortunately we were not able to provide grants to all who applied. We regret to inform you that you have not been selected for a grant.
14+
15+
We hope you're still able to attend DjangoCon US, and that we'll see you in [city]. Thank you very much for your interest in our program.
16+
17+
Sincerely,
18+
19+
[Your name]
20+
21+
[Your title], DjangoCon US [year]

‎docs/drafts/finaid_submitted.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
layout: page
3+
title: Financial Aid - Application Submitted
4+
parent: Templates
5+
---
6+
7+
# Financial Aid - Application Submitted
8+
9+
## Subject: DjangoCon US Financial Aid Application Submitted
10+
11+
Dear [name],
12+
13+
Your DjangoCon US [year] application for financial aid has been received. We hope to let applicants know our financial aid decisions by [date].
14+
15+
Until then, if you have any questions, feel free to contact me at [email].
16+
17+
Warmly,
18+
19+
[Your name]
20+
21+
[Your title], DjangoCon US [year]

‎docs/drafts/recruiting.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
layout: page
3+
title: Program - Recruit Speaker
4+
parent: Templates
5+
---
6+
7+
# Program - Recruit Speaker
8+
9+
## Subject: DjangoCon US CFP
10+
11+
Dear [Person],
12+
13+
I'm familiar with your talk [talk] that you gave at [other conference], and I think it would be a great fit for DjangoCon. I'd like to invite you to submit that talk (or any other talk you think would be valuable to our community) to DjangoCon before our CFP closes on [date].
14+
15+
A little about DjangoCon: We are a nonprofit conference with about 400 attendees. We're looking for diverse topics that represent the experiences of our community, not just talks on the Django web framework. We have a Code of Conduct with a response plan and financial aid is available if cost is a concern. Our CFP closes on [date]: [link to CFP].
16+
17+
If you have any questions, feel free to reach out to me. I'd love to see you speak at DjangoCon!
18+
19+
Warmly,
20+
21+
[Your name]
22+
23+
[Your title], DjangoCon US [year]

‎docs/drafts/talk_accepted.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
layout: page
3+
title: Program - Accepted
4+
parent: Templates
5+
---
6+
7+
# Program - Accepted
8+
9+
## Subject: Speaking at DjangoCon US
10+
11+
Dear [name],
12+
13+
I'm pleased to tell you that your talk [talk] has been accepted for DjangoCon US [year]. Congratulations!
14+
15+
We'll be announcing the list of accepted talks immediately, so if you can no longer give this talk, please contact me right away so I can find a replacement. **Please fill out this form** [link] to accept your speaking slot and indicate any scheduling needs you have. We hope to publish the schedule in the next few weeks.
16+
17+
We are proud to offer speakers a complimentary ticket to the conference. Please claim your ticket at [link] as soon as possible.
18+
19+
If you applied for financial aid, you will be notified about the decision shortly.
20+
21+
For assistance with visas or immigration documents, please contact [name and email]. If you have any other questions, comments, or feedback, please feel free to contact me or the conference chair, [name and email].
22+
23+
On behalf of the DjangoCon US organizing team, I want to thank you for your submission.
24+
25+
See you in [city]!
26+
27+
[Your name]
28+
29+
[Your title], DjangoCon US [year]

0 commit comments

Comments
 (0)
0