djangocon · drewbrew · Jan 11, 2025 · jefftriplett · Jan 13, 2025 · tim-schilling
@@ -48,10 +48,13 @@ nav_order: 3
 
 Update all social media with new branding and dates each year
 
-- [ ] Twitter
+- [ ] Mastodon
+- [ ] Bluesky
+- [ ] LinkedIn
 - [ ] Facebook
 - [ ] YouTube
 - [ ] Flickr
+- [ ] Attendee slack
 
 ## Other
 

@@ -14,20 +14,23 @@ Team Size: 1-3
 ## Responsibilities
 
 - Coordinate with other teams (program, opportunity grants, diversity and outreach, visas, venue, volunteer) to communicate necessary updates to conference attendees, proposal submitters, speakers, sponsors, etc.
-- Manage the Twitter account at @djangocon
+- Manage the Mastodon account at @djangocon@fosstodon.org
+- Manage the Bluesky account at @djangocon.us
+- Manage the LinkedIn account
 - Manage the Facebook account at facebook.com/djangoconus
 - Ensure that emails to hello@djangocon.us receive a response
 - Write, or assist with writing, blog posts, emails, any other written communications. Be the team red pen.
 - Manage Mailchimp email campaigns
 - Help teams publicize items at appropriate times
 - Write, review, and/or edit website copy
-- Manage Twitter account during the conference
+- Manage social media accounts during the conference
 - Create this year's conference attendee Slack channel
 - Write post-conference wrap up and coordinate with sponsors to make sure DSF, PSF, and DEFNA receive the post (as requested when they sponsor)
 
 | Site | Handle |
 | --- | --- |
-| Twitter | [@djangocon](https://twitter.com/djangocon) |
+| Mastodon | [@djangocon@fosstodon.org](https://fosstodon.org/@djangocon) |
+| Bluesky | coming soon |
 | Facebook | [djangoconus](https://www.facebook.com/djangoconus) |
 | YouTube | [DjangoCon US](https://www.youtube.com/channel/UC0yY6a79pPY9J0ShIHRf6yw) |
 | GitHub | [djangocon](https://github.com/djangocon/) (Not just US) |
@@ -40,9 +43,9 @@ For standard announcements (CFP open, tickets on sale, keynote announcements), w
 ## Resources
 
 - [Pablo](https://pablo.buffer.com/) for adding text and logos to images
-- [Flickr](https://www.flickr.com/photos/144080672@N05) for photos of past DjangoCon US's
+- [Flickr](https://www.flickr.com/photos/144080672@N05) for photos of past DjangoCon US editions
 - [Unsplash](https://unsplash.com/) for free "generic" photos
 - [Mailchimp](https://mailchimp.com/) for mailing lists; ask to be added to our group
-- [Tweetdeck](https://tweetdeck.twitter.com) for scheduling tweets; ask to be added as a contributor
+- Buffer for scheduling social media posts; ask to be added as a contributor
 - [Awesome acceptance letter](http://bridgetkromhout.com/blog/2016/04/06/tl-dr-your-talk-is-accepted/)
 - [Happiness Packets](https://github.com/erikr/happinesspackets/)
@@ -1,10 +1,10 @@
 ---
 layout: page
-title: Program - FAQs about Presenting a Tutorial 
+title: Program - FAQs about Presenting a Tutorial
 parent: Templates
 ---
 
-# Proram - FAQs about Presenting a Tutorial 
+# Proram - FAQs about Presenting a Tutorial
 
 Hello everyone,
 
@@ -14,7 +14,7 @@ A few of you have asked about tutorial fees and I thought it'd be best to discus
 
 ## How much are tutorials?
 
-Tutorials are ${{tutorial_price}} a person and we pay *you* {{tutorial_speaker_percent}} of that. 
+Tutorials are ${{tutorial_price}} a person and we pay *you* {{tutorial_speaker_percent}} of that.
 
 ## What does the ${{tutorial_price}} cover?
 
@@ -46,8 +46,8 @@ We originally were capped at 25 attendees per room but we upgraded rooms. In the
 
 ## How many attendees have signed up for my tutorial?
 
-These range from 7 to 25, but we still have two+ weeks left to market them. Email me for an exact number. 
+These range from 7 to 25, but we still have two+ weeks left to market them. Email me for an exact number.
 
 ## Can we promote our own tutorials?
 
-Not only can you promote your own tutorials, we would really appreciate if you would promote your tutorial via Twitter and social media :)
+Not only can you promote your own tutorials, we would really appreciate if you would promote your tutorial via social media :)
@@ -11,17 +11,18 @@ nav_order: 11
 
 - [ ] Make past DjangoCon US site static
 - [ ] Branding & design pass [PyCon example](https://github.com/PyCon/2015/wiki/PyCon-2015-Branding)
-- [ ] Create new website repository 
+- [ ] Create new website repository
 - [ ] Stand up new DjangoCon US site
 - [ ] Compile a wish-list of website improvements
 - [ ] Determine who will be making these improvements
 - [ ] Replace all references to past year with current year
 - [ ] Review all content to make sure it's current (red pen)
-- [ ] Branding files for: 
-  - [ ] Social media avatar 
-  - [ ] Facebook cover photo 
-  - [ ] Twitter cover photo 
-  - [ ] YouTube cover photo 
+- [ ] Branding files for:
+  - [ ] Social media avatar
+  - [ ] Facebook cover photo
+  - [ ] Mastodon cover photo
+  - [ ] Bluesky cover photo
+  - [ ] YouTube cover photo
 
 ## Swag
 
@@ -41,22 +42,22 @@ nav_order: 11
 
 ### Signage
 
-- [ ] Large panel banners: 
+- [ ] Large panel banners:
     - [ ] Two 3-panel banner sets for presentation rooms (with upper-tier sponsors)
     - [ ] Two single-panel banners for registration, etc.
-- [ ] Large foamboard signs on easels: 
-    - [ ] Two with WiFi information 
-    - [ ] Two with Code of Conduct policy 
-    - [ ] Two with Code of Conduct contact information 
-    - [ ] One with photo policy 
-    - [ ] One to label Quiet Room 
-    - [ ] One to label Speaker Room 
+- [ ] Large foamboard signs on easels:
+    - [ ] Two with WiFi information
+    - [ ] Two with Code of Conduct policy
+    - [ ] Two with Code of Conduct contact information
+    - [ ] One with photo policy
+    - [ ] One to label Quiet Room
+    - [ ] One to label Speaker Room
     - [ ] One for bathroom policy
 - [ ] 8.5 x 11 signage in standup sign holders:
     - [ ] 1 per each sponsor with a booth
-    - [ ] 1 per bathroom for bathroom baskets 
-    - [ ] 1 with wifi info for registration 
-    - [ ] 2 sets of speaker timekeeping (15 / 10 / 5 / 0) 
+    - [ ] 1 per bathroom for bathroom baskets
+    - [ ] 1 with wifi info for registration
+    - [ ] 2 sets of speaker timekeeping (15 / 10 / 5 / 0)
 - [ ] Order easels from the venue
 - [ ] Registration desk branding
 - [ ] Podium branding
@@ -66,7 +67,7 @@ nav_order: 11
 - [ ] Print sprint room sign-up board on foam core*
 - [ ] T-shirt signs (when unclaimed t-shirts will go on sale, etc)*
 
-* If doing 
+* If doing
 
 ### T-shirts
 
@@ -81,7 +82,7 @@ nav_order: 11
 - [ ] Badge Design
 - [ ] Lead retrieval considerations
 - [ ] Ribbons for attendee types (speaker, sponsor, "ask me", etc.)
-- [ ] Pronoun buttons 
-- [ ] Print extra blank badges for onsite registrants or spelling mistakes 
-- [ ] Lanyard -- if sponsored, coordinate with sponsor on who is ordering. 
-- [ ] Order lanyards in red/yellow/other color for photography policy 
+- [ ] Pronoun buttons
+- [ ] Print extra blank badges for onsite registrants or spelling mistakes
+- [ ] Lanyard -- if sponsored, coordinate with sponsor on who is ordering.
+- [ ] Order lanyards in red/yellow/other color for photography policy
@@ -13,25 +13,25 @@ permalink: /logistics
 
 The Django Software Foundation has published [guidelines](https://www.djangoproject.com/foundation/conferences/) for hosting an event that is branded "DjangoCon."
 
-The guidelines in these docs are specific to DjangoCon US, which is a two-track conference that takes place over six days in North America. If you'd like to start your own DjangoCon or other Django conference, feel free to reach out. We'll do whatever we can to help. 
+The guidelines in these docs are specific to DjangoCon US, which is a two-track conference that takes place over six days in North America. If you'd like to start your own DjangoCon or other Django conference, feel free to reach out. We'll do whatever we can to help.
 
-Some areas of responsibility come into play very early in the planning process. A website lead is needed very early on, for example. Other areas of responsibility only come into play at the conference itself, such as the registration coordinator.   
+Some areas of responsibility come into play very early in the planning process. A website lead is needed very early on, for example. Other areas of responsibility only come into play at the conference itself, such as the registration coordinator.
 
-The responsibilities for each area described here are meant to be comprehensive, but not necessarily exhaustive. Other to-do items will come up in the planning process; every year is different. All organizers are free to help other areas as needed. 
+The responsibilities for each area described here are meant to be comprehensive, but not necessarily exhaustive. Other to-do items will come up in the planning process; every year is different. All organizers are free to help other areas as needed.
 
 ## Tools
 
-| Tool | Usage | 
-| --- | --- | 
-| Bitbucket | Where we store private documents like Letter of Invitations and other sensitive documents | 
-| [GitHub](https://github.com/djangocon/) | Github is our main code sharing tool | 
-| [Google Drive](https://drive.google.com/) | We use one shared DjangoCon US folder to manage our files | 
-| [Google Hangouts](https://hangouts.google.com/)<br />BlueJeans | Services we use to hold organizer meetings | 
-| [Mailchimp](https://mailchimp.com/) | Used for mass emails to attendees, sponsors, speakers, and people on our informational mailing list. See [Mailing Lists](../communications/mailing_lists.md) for more information. | 
+| Tool | Usage |
+| --- | --- |
+| Bitbucket | Where we store private documents like Letter of Invitations and other sensitive documents |
+| [GitHub](https://github.com/djangocon/) | Github is our main code sharing tool |
+| [Google Drive](https://drive.google.com/) | We use one shared DjangoCon US folder to manage our files |
+| [Google Hangouts](https://hangouts.google.com/)<br />BlueJeans | Services we use to hold organizer meetings |
+| [Mailchimp](https://mailchimp.com/) | Used for mass emails to attendees, sponsors, speakers, and people on our informational mailing list. See [Mailing Lists](../communications/mailing_lists.md) for more information. |
 | Google Groups mailing lists | Used for internal communication. See [Mailing Lists](../communications/mailing_lists.md) for more information. |
-| [Slack](https://slack.com/) | Our realtime and async communication medium. We have public and private channels for a wide variety of conference topics | 
-| [Trello](https://trello.com/) | Our project management tool and todo list | 
-| [Tweetdeck](https://tweetdeck.twitter.com/) <br /> Buffer | Tools we use to schedule promotional social media posts |
+| [Slack](https://slack.com/) | Our realtime and async communication medium. We have public and private channels for a wide variety of conference topics |
+| [Trello](https://trello.com/) | Our project management tool and todo list |
+| Buffer | Tool we use to schedule promotional social media posts |
 
 ## Resources
 

@@ -5,16 +5,16 @@ parent: Logistics
 nav_order: 6
 ---
 
-# Organizers 
+# Organizers
 
-## Ongoing responsibilities 
+## Ongoing responsibilities
 
-- Reset/cull staff mailing list (hello@djangocon.us) at the start of a new cycle 
+- Reset/cull staff mailing list (hello@djangocon.us) at the start of a new cycle
 - Update staff page on the website
 - Schedule monthly staff meetings
 - Succession planning
-- Collect staff phone numbers before DjangoCon US 
-- Collect dates DjangoCon US organizers arrive/leave before DjangoCon US 
+- Collect staff phone numbers before DjangoCon US
+- Collect dates DjangoCon US organizers arrive/leave before DjangoCon US
 
 ## How to integrate a new team member
 
@@ -24,9 +24,9 @@ nav_order: 6
 4. Add to [Google Drive](https://drive.google.com/drive/u/0/folders/0B9CaqKMu3IDSckh2V3hERFo4NTQ)
 5. Add to [Trello](https://trello.com/djangoconus/members)
 
-## Where else to add people? 
+## Where else to add people?
 
-There are all on a case by case basis, depending on the area the organizer is helping with. 
+There are all on a case by case basis, depending on the area the organizer is helping with.
 
 - Add to:
    - [conduct@djangocon.us](https://groups.google.com/a/djangocon.us/forum/)
@@ -35,7 +35,7 @@ There are all on a case by case basis, depending on the area the organizer is he
    - [financialaid@djangocon.us](https://groups.google.com/a/djangocon.us/forum/)
    - [visas@djangocon.us](https://groups.google.com/a/djangocon.us/forum/)
 - Social media accounts
-   - [TweetDeck](https://tweetdeck.twitter.com/)
+   - Buffer
    - [Facebook page](https://www.facebook.com/djangoconus/)
 - Email marketing: [Mailchimp](http://mailchimp.com/)
 - [1Password Team](https://djangocon.1password.com/signin)

@@ -1,21 +1,21 @@
 ---
 layout: page
-title: Swag & Graphics 
+title: Swag & Graphics
 parent: Logistics
 nav_order: 10
 ---
 
-# Swag & Graphics 
+# Swag & Graphics
 
-## Responsibilities 
- 
-- Develop the visual brand for the conference together with the design team (outside hire) 
-- Ensure brand is uniformly applied across conference materials and online presence (website, Facebook, Twitter, YouTube, other social media) 
-- Ensure the following swag items are ordered and delivered: 
-    - Stickers and/or buttons 
-    - Necessary signage (banners and easel signs) 
+## Responsibilities
+
+- Develop the visual brand for the conference together with the design team (outside hire)
+- Ensure brand is uniformly applied across conference materials and online presence (website, Facebook, Mastodon, LinkedIn, Bluesky, YouTube, other social media)
+- Ensure the following swag items are ordered and delivered:
+    - Stickers and/or buttons
+    - Necessary signage (banners and easel signs)
     - Conference badges
     - Lanyards
     - Speaker and organizer gifts
-- Manage t-shirts, if doing (sometimes this is included with the conference ticket, sometimes this is a Teespring or similar campaign after the conference) 
-- Coordinate with sponsors team to ensure sponsor logos are delivered 
+- Manage t-shirts, if doing (sometimes this is included with the conference ticket, sometimes this is a Teespring or similar campaign after the conference)
+- Coordinate with sponsors team to ensure sponsor logos are delivered
@@ -27,15 +27,16 @@ nav_order: 2
 - [ ] Recruit speaker mentors
 - [ ] Publicize the existence of speaker mentors
 - [ ] Publicize the CFP and deadlines
-   - [ ] (what's left of) Twitter
-   - [ ] Mastodon
-   - [ ] Django Forum
-   - [ ] Django Discord
-   - [ ] PSF Community Mailing List
-   - [ ] DSF Members Mailing List
+  - [ ] Bluesky
+  - [ ] Mastodon
+  - [ ] LinkedIn
+  - [ ] Django Forum
+  - [ ] Django Discord
+  - [ ] PSF Community Mailing List
+  - [ ] DSF Members Mailing List
 - [ ] Review proposals
 - [ ] Provide proposal feedback
-- [ ] Draft & send the accept/decline emails
+- [ ] Draft & send the accept/decline/waitlist emails
   - In past years, we've used sendy to send the accept/decline/waitlist functions, but we can use pretalx to use the first two
 - [ ] Create form to collect speaker info (name, video preferences, pronouns, etc.)
 - [ ] Determine the talk schedule