You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/logistics/logistics.md
+13-16Lines changed: 13 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -11,36 +11,33 @@ permalink: /logistics
11
11
12
12
## About organizing DjangoCon US
13
13
14
-
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 conference chair(s) are selected very early in the process.
15
-
16
-
The list of responsibilities for each area is 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; organizers are not territorial about their areas.
17
-
18
14
The Django Software Foundation has published [guidelines](https://www.djangoproject.com/foundation/conferences/) for hosting an event that is branded "DjangoCon."
19
15
20
-
The guidelines in this GitBook are specific to DjangoCon US, which is a two-track conference that takes place over six days in North America.
16
+
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.
17
+
18
+
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.
21
19
22
-
Some unpublished rules about hosting a DjangoCon will vary depending on the location of the DjangoCon; for example, in the United States, we are required to host our event a specific amount of time away from PyCon US and DjangoCon Europe. If you would like to host a DjangoCon or another Django event, please contact the DSF for more information.
20
+
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.
23
21
24
22
## Tools
25
23
26
24
| Tool | Usage |
27
25
| --- | --- |
28
26
| Bitbucket | Where we store private documents like Letter of Invitations and other sensitive documents |
29
-
| GitHub | Github is our main code sharing tool |
30
-
| Google Drive | We use one shared DjangoCon US folder to manage our files |
31
-
| Google Hangouts<br />BlueJeans | Services we use to hold organizer meetings |
32
-
| Mailchimp | Used for mass emails to attendees, sponsors, speakers, and people on our informational mailing list. See [Mailing Lists](docs/communications/mailing_lists.html) for more information. |
27
+
|[GitHub](https://github.com/djangocon/)| Github is our main code sharing tool |
28
+
|[Google Drive](https://drive.google.com/)| We use one shared DjangoCon US folder to manage our files |
29
+
|[Google Hangouts](https://hangouts.google.com/)<br />BlueJeans | Services we use to hold organizer meetings |
30
+
|[Mailchimp](https://mailchimp.com/)| Used for mass emails to attendees, sponsors, speakers, and people on our informational mailing list. See [Mailing Lists](docs/communications/mailing_lists.html) for more information. |
33
31
| Google Groups mailing lists | Used for internal communication. See [Mailing Lists](docs/communications/mailing_lists.html) for more information. |
34
-
| Slack | Our realtime and async communication medium. We have public and private channels for a wide variety of conference topics |
35
-
| Trello | Our project management tool and todo list |
36
-
| Tweetdeck <br /> Buffer | Tools we use to schedule promotional social media posts |
32
+
|[Slack](https://slack.com/)| Our realtime and async communication medium. We have public and private channels for a wide variety of conference topics |
33
+
|[Trello](https://trello.com/)| Our project management tool and todo list |
34
+
|[Tweetdeck](https://tweetdeck.twitter.com/) <br /> Buffer | Tools we use to schedule promotional social media posts |
37
35
38
36
## Resources
39
37
40
38
-[The Less Obvious Conference Checklist](https://github.com/mxsasha/lessobviouschecklist)
41
39
-[Handbook for open-source software community conference organisers](https://github.com/evildmp/conference-handbook) by [Daniele Procida](https://github.com/evildmp)
42
40
-[List of well designed conferences](https://github.com/olasitarska/pretty-conferences) by [Ola Sitarska](https://github.com/olasitarska/pretty-conferences)
0 commit comments