DjangoCon US 2018 in San Diego

We are pleased to announce that the DjangoCon US 2018 conference will take place in San Diego, California from October 14-19, 2018!

  • October 14: Tutorials (Paid)
  • October 15-17: Talks
  • October 18-19: Sprints

We have a lot of amazing things planned that we’ll announcing over the next few months. Until then, here’s what you can do to help!

  • Mark your calendars and help us spread the word!
  • Start thinking about topics for when our Call for Proposals is announced.
  • Follow us on @DjangoCon and @defnado on Twitter.
  • Sponsor the event!
  • Want to help by becoming an organizer?

Start working on those proposals, and we hope we’ll see you at DjangoCon US!

Call for Proposals for DjangoCon 2018 Website!

Updated: October 31st, 2017 to extend our CFP deadline.

Overview

Prior to 2017, DjangoCon US websites were built using Django. DEFNA decided to take a different approach for the 2017 conference. The website was built using the static site generator Jekyll and hosted on GitHub. There are a number of advantages to this approach:

  • Much of the website layout code can be reused from year to year
  • New designs can be implemented more quickly and easily
  • Website documentation is more easily maintained
  • The number of contributions and contributors has drastically increased

Technical Specifications

The 2017 DjangoCon US website currently uses the following software tools:

  • Hosted on Github Pages (using Jekyll static site generator)
  • Foundation responsive design framework
  • Sass CSS extension language
  • Gulp to compile for production
  • npm for installation of front end dependencies

Here is the link to the DjangoCon US 2017 website repo, including README documentation: https://github.com/djangocon/2017.djangocon.us/

GOING FORWARD

We want to build off what we started in 2017 but improve on what we have. Our main goal for 2018 (repo here) is to update our color scheme, logos, and style guide to fit the theme of the new city that we select.

We have all of our 2017 data to work with which includes all of our content along with our speakers and schedule (talks, tutorials, and sprint information) which can be used to verify and test with.

We’d also like your help finishing the layout for our Why DjangoCon US page which we use to help market to employees who wish to get their companies/bosses on board with attending DjangoCon US. See here: https://2017.djangocon.us/why-djangocon-us/

Finally, we'd like your help with our swag and art direction which includes our backdrops during the conference, videos, signage, along with special swag which we give out at the conference.

2017 Deliverables

DjangoCon US will need:

  • A configurable landing page with:
    • City and date information (This should also have a “coming soon” option)
    • A marketing teaser
    • Link to sponsorship info
    • Link to our code of conduct
  • Updated website design including city design, color scheme, logos, and updated style guide.
  • Ideas and art direction for our swag and signage

DEFNA WILL PROVIDE

  • City and date information
  • Sponsorship submission form hosted through third-party
  • Landing page copy
  • The 2017 website which shows a complete and working implementation of what we are looking for

2018 Deliverables

Delivery of the full website design

  • Responsive design that supports mobile, tablet, and desktop devices
  • Accessibility and usability features

DjangoCon US organizers and open-source community members will provide additional support for integration of the design.

Tentative Schedule

  • Landing page launch: December 2017
  • Website design complete: January 2018
  • Initial site launch: January 2018
  • Swag completion: February 2018

CFP Timeline

  1. Call for proposals opens: October 12, 2017
  2. Deadline to submit proposal: October 31, 2017 Extended to: November 14, 2017
  3. Decision: November 15, 2017 Extended to: November 28th.

Submission Instructions

Please provide an electronic copy of your submission to our email address hello@defna.org. You can also email any questions that you have to our email address.

We look forward to hearing from you!

The Joys of Catering, Part 1: Tickets Sold Does Not Equal Catering Count

The first challenge with conference catering is figuring out how many people you are actually going to feed. While ticket sales are part of that equation, there are actually a number of moving parts that will give you a final number that is unlikely to match the number of tickets sold.

While there is a certain mathematical component to figuring headcount, there's also an art that doesn't fit quite so neatly into a formula. Once you have done this a few times, or if you work with the same conference and/or caterer year to year, you develop an intuitive sense about how to adjust the headcount to fit the audience.

I'm going to use nice, round numbers for this example to keep the math simple. Substitute your own numbers as needed!

Adding up:

1. For our hypothetical conference, we've sold 450 tickets. Go, us!

2. If your conference sells tickets on the day of the event, add in your historical rate. If you don't know that number, use 2% of Tickets Sold.

3. Next, look at your ticket sales: does that number include conference staff/volunteers, the outside A/V team you've hired, or other people who are working the conference? If not, count them up, and add that number.

4. Some conferences do a "plus-one" ticket, which allows the spouse/partner/significant other of an attendee to partake of meals and breaks. If that number isn't included in Tickets Sold, add that in as well. If you do not offer such a ticket, you need to decide how to enforce the "attendees only" rule at breaks and meals. For the conferences I work, we require everyone to wear their badge when entering the food service area—pleasantly uncomplicated and efficient.

5. Ask the caterer what number they plan for. Most caterers buffer 2% - 3% so that they don't run out of food, but also don't end up with piles of leftovers.

6. Lastly, is there anyone else who is going to show up and expect to be fed? Perhaps the CEO of your Super-Premium-Top-Tier-Biggest Sponsor. Who "forgot" to register, and the company used all their tickets already. Are you really going to tell them they can't have coffee? (The answer here is "no", in case you were wondering.) This is where the caterer's overage comes in handy. You should have only one or two of these people. If you have more than that, take a look at your registration and sponsorship policies for next year—something is definitely out of alignment.

Subtracting out:

7. Most conferences have a 1% - 3% no-show rate. I've worked conferences where the no-show rate has been as high as 8% - 10%, but those are outliers. If you know the historical no-show rate for your conference, use that number; otherwise, use 3%.

8. There are always a few people who don't eat the conference food, no matter what is on the menu. They just don't. If you have historical numbers, go with that. Otherwise, 1% - 2% is a workable estimate.

9. If the venue has other food options, for example, the venue has a casual restaurant, or a great sushi bar, or a line of food trucks outside the front door, you're going to lose people to those other options. Additionally, if there's a treasured local eatery within two blocks of the venue, some people will go there for lunch. If you have any of these situations, take off another 3%.

Here's our hypothetical conference:

Tickets Sold: 450
Walk-Ins: 10
Staff and Volunteers: 5
Plus-One Tickets (if not included in Tickets Sold): 20
Unexpected Guests: 2
Total In: 487

No-shows at 3%: -15
Not eating at 3% -15
Other options at 3%: -15
Total out: -45

Total In - Total Out = Initial Adjusted Headcount: 487 - 45 = 442

If you quote the caterer a headcount of 442, and they plan a 3% overage, they will cater for 455.

If you're concerned about costs, you can make an additional headcount adjustment. Most caterers allot a generous amount of food per person, so you could adjust your total downward between 3% and 5% and come out alright. I've adjusted as much as 10% for some events, based on a decrease in ticket sales from the prior year.

Additional 3%: 442 - 13 = 429 headcount, caterer sets for 442, your original headcount

Additional 5%: 442 - 22 = 420 headcount, caterer sets for 432, 10 fewer than your original headcount, which is still a workable margin

Additional 10%: 442 - 44 = 398 headcount; caterer sets for 410. We're getting edgy here; I would go this low only if attendees had a number of other options, because you may end up taking a few people out for pizza or something if the food runs out.

For a real world example, a conference I ran a few years ago had a total adjusted headcount of 450. The caterer set a 3% buffer, so a headcount of 450 would be set for 463.

The conference had not kept records, so we had no historical numbers to compare. Purely on intuition, I gave the caterer a headcount of 420, which meant they set for 433. The actual count through the lunch area each day varied from 421 - 428; no one went hungry, and the caterer ran well under their 3% waste goal. So dropping the headcount that additional 6% worked out almost exactly. I don't have a solid reason why I chose the 420 as the final number; it just seemed right, and, as it turned out, it was!

Again, though it's not a hard science, the numbers are a solid start. The Initial Adjusted headcount can also be your end point as a more cautious approach, rather than going with the additional adjustments. If you're not sure where to start, use the formula above to derive the Initial Adjusted Headcount for the caterer, and then make adjustments each subsequent year, based on experience.

Welcome New Board Members

The DEFNA board is excited to announce our expansion and the addition of our four new board members. We are excited to see what our new members accomplish. Here is some information about each of them. Please help us in welcoming them!

Heather Luna

Heather Luna also affectionately known as Heats is the Sponsorship Chair for DjangoCon US. Her day job is a Systems Administrator at the Wharton School of Business. Heather fell in love with Python and Django after DjangoCon US came to Philadelphia in 2016. Her goal is now to combine her love of systems administration with her new love of development. She is committed to furthering and supporting women in technology and supporting diversity and inclusion for all.

Katherine "Kati" Michel

In addition to being the DjangoCon US Website Chair, Kati can often be found working on special projects for the United Methodist Church. She is a project manager, designer, and developer who enjoys following the latest tech trends, learning, and teaching others. In her free time, she enjoys traveling, eating good food, and listening to music.

Kojo Idrissa

A recovering former accountant with an MBA, Kojo taught accounting and MIS at the university level in the US and China. He's also worked for non-profits, two Big 4 Public Accounting firms and been a 1-person business.

After changing careers, he's currently doing QA for a startup on a web-based product. He's also trying to learn to be a better software engineer, Pythonista and Djangonaut.

He likes community building and outreach, improving inclusion, helping new members of the community "get comfortable" & make contributions, and generally being helpful.

Monique Murphy

Monique started using Django as a developer for the University of Texas at Austin. She is currently a developer for ApplyTexas (also in Austin). She has too many hobbies to list, but is a linguist and passionate foreign language enthusiast, karaoker, aspiring comic artist, and avid reader of any and all things words.

Two Weeks Left to Submit DjangoCon Venue Proposals for 2018 and 2019!

We wrote to you in May that we are accepting proposals for DjangoCon venues for 2018 and 2019 and that we need your help in making that decision! We are accepting proposals through the end of the month. The deadline is July 31, 2017. 

To recap, here's what you need to know and what we need to know, to consider your proposal:

We are looking at two possible ranges of conference dates: mid-July through mid-August or late-September (after Yom Kippur) through mid-October. We need to avoid major holidays like Labor Day and Yom Kippur, the start of the school year, and the busiest summer months.

We’re also considering having the conference location change every two years, instead of every year, to make planning travel easier for our attendees.

We need some information about your city, possible venues, hotels, and travel. Your proposal doesn’t have to be super-fancy, but it does need to be informative. If you are interested in submitting a proposal, please see our DjangoCon US: Call for Venue Proposal 2018 and 2019 for more details.

DjangoCon US: Call for Venue Proposal 2018 and 2019

We’re almost ready for DjangoCon US 2017, so it’s time to think about 2018 and possibly 2019! Where will we be next year? Where will be for the next two years? We need your help in making that decision!

So you want your city to host DjangoCon US! Hurrah! We’re delighted by your interest. Here’s what you need to know, and what we need to know, to consider your proposal.

We are looking at two possible ranges of conference dates: mid-July through mid-August or late-September (after Yom Kippur) through mid-October. We need to avoid major holidays like Labor Day and Yom Kippur, the start of the school year, and the busiest summer months.

We’re also considering having the conference location change every two years, instead of every year, to make planning travel easier for our attendees.

We need some information about your city, possible venues, hotels, and travel. Your proposal doesn’t have to be super-fancy, but it does need to be informative. The proposal should include the following:

Organizers

Names of organizers staffing the host city. While DEFNA will handle the business aspects of the conference, we need the help of a team of local volunteers to manage preparation and the onsite coordination of the event. We realize you won't have an entire team assembled, but let us know who the core organizers in your city will be.

Venues

A short list of possible conference venues (or just one, if you have found the Venue of Conference Dreams), with the following information:

  • Name

  • Location

  • Transportation options (how do people get there from the airport?)

  • Attendance capacity

  • Layout of function space:

    • Keynote room (also Sessions Track A) to accommodate up to 450 people, classroom style (tables with chairs)

    • Room for Sessions Track B to accommodate up to 200 people, classroom style (tables with chairs)

    • Optional: Room for Sessions Track C to accommodate up to 150 people, classroom style (tables with chairs)

    • Space for sponsors to set up exhibit booths/tables; at least 12, and up to 16, sponsors with either 6’ tables or 10’ x 10’ booth spaces. If more sponsor booth space is available, that's a plus.

    • Green room for speakers to prepare (generally a room that will seat 25 for a workshop is the right size)

    • Quiet room for giving attendees a place to get away from the conference noise (capacity 25 - 50). Set with tables and chairs; round catering-style tables are workable.

    • Location of registration tables

    • Location of meals and breaks with sufficient seating and tables. If serving and/or seating areas cannot accommodate 450 people at once, indicate the room capacity and timing to move 450 people through.

    • Location of supplemental beverage stations for daylong service.

    • Secure overnight storage for vendor booth supplies and conference registration desk items.

Catering

  • Tutorials day—100 people: Breakfast, morning break, lunch, afternoon break, and all day beverage service. (All day beverage service includes water stations, coffee, assorted black and herbal teas, and a variety of soft drinks.)

  • Main conference, 3 days—450 people per day: Breakfast, morning break, lunch, afternoon break, and all day beverage service.

  • Sprints, 2 days—75 people each day: Breakfast, morning break, lunch, afternoon break, and all day beverage service.

  • Catering must have options for vegetarians and vegans of equal quality and variety as main menu. Estimate 15% vegetarian and 5% vegan.

  • Catering must label food appropriately so that our attendees are aware of allergens. Attendees should not have to guess if a dish is gluten free or contains tree nuts.

Costs

We need costs for:

  • Function space

  • Catering

  • Audio-visual services

  • Any other fees or costs the venue requires.

  • Pricing breakdown for a one year contracts vs. a two year contract.

What makes a good conference venue?

A good conference venue is/has the following:

  • Easy to reach from the airport and the conference hotel

  • Free parking if a car is required for access

  • The ability to serve lunch to 350—450 people in a 90 minute window.

  • Most venues require use of their in-house catering service. If the venue does not offer catering services, check whether the venue restricts catering access to an approved vendor list, and what, if any, requirements they have for outside catering vendors.

  • Adjoins or within walking distance to a suitable hotel which can accommodate 350-450 attendees

  • Excellent Internet connectivity

  • Accessible to as many attendees as possible. Things to think about: gender-neutral restrooms, space to walk service animals, lactation rooms, step-free access from the parking lot to the presentation area.

  • Reasonable access to transit for sightseeing

The venue does not have to be a hotel or corporate conference center. Many universities offer conference services, and there are also municipal/county level event venues which can be likely sites for DjangoCon US.

Sprint Venues

A short list of possible sprint venues, which may be the conference venue, with the following information:

  • Name

  • Location

  • Transportation options

  • Attendance capacity

  • Cost of function space, catering, and audio-visual services. Sprints are often hosted by local companies as sponsorship of the event, which is preferable, as it saves the cost of renting a venue.

  • Pricing breakdown for a one-year contract vs. a two-year contract.

  • A good sprint venue is/has the following:

    • Easy to reach from the conference hotel

    • Free parking if a car is required for access

    • A room to hold 50-75 people, with work tables, chairs, power, and internet connectivity

    • See catering requirements above. Eating tables should be separate from work tables if at all possible.

    • Excellent Internet connectivity

    • Accessible to as many attendees as possible

Hotels

The ideal hotel is adjacent to the conference venue, or a very short walk away. For the hotel, we need:

  • Name

  • Location

  • Transportation options

  • The conference room rate (should be discounted from the standard rate)

  • A block of rooms starting the two nights before tutorials, and running through the last night of the sprints. The breakdown of the room counts would be estimated at:

    • Saturday: 15
    • Sunday Tutorials: 100
    • Monday Main Conf: 100
    • Tuesday Main Conf: 100
    • Wednesday Main Conf: 80
    • Thursday Sprints: 30
    • Friday Sprints: 15
  • The block should include the guaranteed ability to add 20% more rooms for any given night if needed without moving to an overflow hotel.

  • Concessions policy (comp room nights per actualized room nights)

  • Pricing breakdown for a one year contracts vs. a two year contract.

  • A sample contract showing the terms of booking the block of rooms. Again, do not sign any contracts. DEFNA will handle the business side of things. We just need to see the terms the hotel proposes for the group block.

Potential Sponsors

Provide a list of possible local and regional companies that may be interested in sponsoring DjangoCon US.

Everything Else

  • Provide estimates on costs associated with flights, accommodation, meals, ground transportation, etc. for an overview of total cost for attendees.

  • Information about what makes the city a good choice for DjangoCon US and an attractive destination for attendees.

  • Any additional ideas for making the event especially useful and/or memorable.

Since we are considering a number of proposals, no one from your group should sign a binding contract or make any kind of legal or financial commitment.

If DEFNA chooses your group's proposal, your group is responsible for putting DEFNA in contact with the venue management to finalize the event agreement.

Please submit your proposal no later than July 31, 2017.

Thanks so much! We look forward to hearing about all the fantastic places we can go next year!

DEFNA Board Member Recruitment: Join US!

Django Events Foundation North America (DEFNA) is looking for board members! If you're looking for a way to participate in the Django community, this may be what you're looking for!

DEFNA was founded to support Django professional and educational events in North America. Our main focus has been DjangoCon US, and we're looking to expand our support to smaller regional and local events.

To do this, we need additional people to help manage DEFNA. Our current board members (who are also the founding members) are Jeff Triplett, Craig Bruce, and Stacey Haysler.

Specifically, we need people to:

  • Attend the monthly board meeting
  • Manage DEFNA business: as a 501(c)(3) charitable organization and a registered California corporation, there are annual forms and filings to complete, monthly board records to maintain, etc. as well as the usual paying bills and other general business management tasks
  • Participate in the grant applications review process
  • Use DEFNA's social media channels to communicate about DEFNA
  • Come up with new and clever ways for DEFNA to fulfill our mission

The day-to-day running of DjangoCon US is handled by our amazing team of volunteers. The DEFNA board is not involved in the day-to-day business; our job is to select the venue, manage the contracts, and provide direction to the organizers' team. If you want to be part of the organizers' team, that's terrific—but it's not required.

Board membership takes, on average, about five hours per month. You can put in more time if you want to be more involved, of course!

If you'd like to be considered for the board, drop us a note at hello@defna.org, and let us know:

  • What interests you about being on the board
  • Your current/prior community involvement (it's okay if you're new—we need everyone to participate!)
  • Any particular interests you have (grants committee, corporate filings, etc.)
  • Any ideas you have for expanding DEFNA's reach in the OSS community
  • Anything else you'd like us to know about you as a potential board member

Please email your information to us by 6:00 PM Pacific Time on April 28th. We'll contact you if we need more details. We'll make our decisions and reply to everyone on May 12th.

Thanks for your interest, and your support of DEFNA!

DjangoCon US 2017 in Spokane, Washington

We are pleased to announce that the DjangoCon US 2017 conference will take place in Spokane, Washington from August 13-18, 2017!

  • August 13: Tutorials (Paid)
  • August 14-16: Talks
  • August 17-18: Sprints

We have a lot of amazing things planned that we’ll announce over the next few weeks. Until then, here’s what you can do to help!

Start working on those proposals, and we hope we’ll see you at DjangoCon US!

DEFNA Phase II

DEFNA is excited to announce further resources in its work to support the education and outreach of Django. We have established an annual fund to provide grants for local Django events in North America. The purpose of the grants is to allow organizers to increase awareness of their events to attract increased participation, and to be able to obtain the resources needed to put on a successful event. Whether you are doing a one day coding workshop, a half day introductory course, or a Django meet up, let us know what you are doing, and how we can help your event.

To apply for a grant, please send an email to contact (at sign) defna (dot) org with the following information:

Name of event

Date(s) of event

Name(s) of organizer(s)

Purpose of event

Grant amount requested

Purpose of grant

Please put “Request for Django Grant” and include the name of your event in the subject line of your email.

We look forward to furthering our work with the Django community!

DjangoCon US: Call for Venue Proposal 2017

We’re almost ready for DjangoCon US 2016, so It’s time to think about 2017! Where will we be next year? We need your help in making that decision!

So you want your city to host DjangoCon US! Hurrah! We’re delighted by your interest. Here’s what you need to know, and what we need to know, to consider your proposal.

For 2017, we are looking at moving the conference to dates in the first half of August. This removes the calendar conflict with Labor Day, and makes it easier on people who have to be mindful of the start of the school year when scheduling their conference attendance.

We need some information about your city, about the venue, the hotel, and travel. Your proposal doesn’t have to be super-fancy, just informative. The proposal should include the following:

  1. Names of organizer staff in the host city. While DEFNA will handle the business aspects of the conference, we need the help of a team of local volunteers to manage preparation and the onsite coordination of the event. We realize you won't have an entire team assembled, but let us know who the core organizers in your city will be.

  2. A short list of possible conference venues (or just one, if you have found the Venue of Conference Dreams), with the following information:

    • Name
    • Location
    • Transportation options (how do people get there from the airport?)
    • Attendance capacity
    • Layout of function space:

      • Keynote room (also Sessions Track A) to accommodate up to 450 people, classroom style (tables with chairs)
      • Room for Sessions Track B to accommodate up to 200 people, classroom style (tables with chairs)
      • Room for Sessions Track C to accommodate up to 100 people, classroom style (tables with chairs)
      • Space for sponsors to set up exhibit booths/tables; at least 12, and up to 16, sponsors with either 6’ tables or 10’ x 10’ booth spaces. If more sponsor booth space is available, that's a plus.
      • Green room for speakers to prepare (generally a room that will seat 25 for a workshop is the right size)
      • Location of registration tables
      • Location of meals and breaks with sufficient seating and tables. If serving and/or seating areas cannot accommodate 450 people at once, indicate the room capacity and timing to move 450 people through.
      • Location of supplemental beverage stations for daylong service.
      • Secure overnight storage for vendor booth supplies and conference registration desk items.
    • Catering:

      • Tutorials day—100 people: Breakfast, morning break, lunch, afternoon break, and all day beverage service. (All day beverage service includes water stations, coffee, assorted black and herbal teas, and a variety of soft drinks.)
      • Main conference, 3 days—450 people per day: Breakfast, morning break, lunch, afternoon break, and all day beverage service. (All day beverage service includes water stations, coffee, assorted black and herbal teas, and a variety of soft drinks.)
      • Sprints, 2 days—75 people each day: Breakfast, morning break, lunch, afternoon break, and all day beverage service. (All day beverage service includes water stations, coffee, assorted black and herbal teas, and a variety of soft drinks.)
      • Catering must have options for vegetarians and vegans of equal quality and variety as main menu. Estimate 15% vegetarian and 5% vegan.
    • Costs for:

      • Function space
      • Catering
      • Audio-visual services
      • Any other fees or costs the venue requires.

      A good conference venue is/has the following:

    • Easy to reach from the airport and the conference hotel

    • Free parking if a car is required for access
    • The ability to serve lunch to 350—450 people in a 90 minute window.
    • Most venues require use of their in-house catering service. If the venue does not offer catering services, check whether the venue restricts catering access to an approved vendor list, and what, if any, requirements they have for outside catering vendors.
    • Adjoins or within walking distance to a suitable hotel which can accommodate 350-450 attendees
    • Excellent Internet connectivity
    • Accessible to as many attendees as possible
    • Reasonable access to transit for sightseeing

      The venue does not have to be a hotel or corporate conference center. Many universities offer conference services, and there are also municipal/county level event venues which can be likely sites for DjangoCon US.

  3. A short list of possible sprint venues, with the following information:

    • Name
    • Location
    • Transportation options (how do people get there from the hotel?)
    • Attendance capacity
    • Cost of function space, catering, and audio-visual services. Sprints are often hosted by local companies as sponsorship of the event, which is preferable, as it saves the cost of renting a venue.

      A good sprint venue is/has the following:

    • Easy to reach from the conference hotel
    • Free parking if a car is required for access
    • A room to hold 50-75 people, with work tables, chairs, power, and internet connectivity
    • See catering requirements above. Eating tables should be separate from work tables if at all possible.
    • Excellent Internet connectivity
  4. Hotel. The ideal hotel is adjacent to the conference venue, or a very short walk away. For the hotel, we need:

    • Name
    • Location
    • Transportation options (how do people get there from the airport?)
    • The conference room rate (should be discounted from the standard rate)
    • A block of rooms starting the two nights before tutorials, and running through the last night of the sprints. The breakdown of the room counts would be estimated at:

      Friday Saturday Sunday Tutorials Monday Main Conf Tuesday Main Conf Wednesday Main Conf Thursday Sprints Friday Sprints
      1015100100100803015

      The block should include the guaranteed ability to add 20% more rooms for any given night if needed without moving to an overflow hotel.

    • Concessions policy (comp room nights per actualized room nights)

    • A sample contract showing the terms of booking the block of rooms. Again, do not sign any contracts. DEFNA will handle the business side of things. We just need to see the terms the hotel proposes for the group block.
  5. Provide estimates on costs associated with flights, accommodation, meals, ground transportation, etc. for an overview of total cost for attendees.

  6. Information about what makes the city a good choice for DjangoCon US and an attractive destination for attendees.

  7. Any additional ideas for making the event especially useful and/or memorable.

Since we are considering a number of proposals, no one from your group should sign a binding contract or make any kind of legal or financial commitment.

If DEFNA chooses your group's proposal, your group is responsible for putting DEFNA in contact with the venue management to finalize the event agreement.

In order for us to make a decision in time to announce next year’s venue at the end of the Philadelphia conference, please submit your proposal no later than July 10, 2016.

Thanks so much! We look forward to hearing about all the fantastic places we can go next year!

DjangoCon US 2016 in Philly

We are pleased to announce that the DjangoCon US 2016 conference will take place in Philadelphia, Pennsylvania from July 17-22, 2016 at The Wharton School at the University of Pennsylvania:

  • July 17: Tutorials
  • July 18-20: Talks
  • July 21-22: Sprints

We have a lot of amazing things planned that we’ll announce over the next few weeks. Until then, here’s what you can do to help!

Start working on those proposals, and we hope we'll see you at DjangoCon US!