Write a Great Talk Proposal
We held two copies of "Writing a Great Talk Proposal," led by Red Hat's Josh Berkus. If you would like to see the slides you can find them here. We will post a video recording as soon as it is available.
If you have specific questions or would like someone to review your proposal, please join us on Freenode in the #deconf channel. If you aren't really an IRC person, check out the Freenode web interface. On the login page, give yourself a nickname and then put #devconf in the "channels" box.
We would like to enable attendees who have not been to many conferences or would like to come up to speed on one of the topics covered at DevConf.us to have a supported experience by being paired up with more experienced attendees. Everyone is encouraged to sign up as either a coach or an apprentice during registration and indicate the track topic based on which they would like to be paired up. Roughly speaking, if you have had three or more years of experience with one of the track topics and have been to five or more conferences, you would make a great coach for the event. If you would like to learn more about one of the conference topics, are interested in career advice, and/or have not attended many conferences in the past, you should consider signing up as an apprentice. We will match people up and will send out mentor / apprentice introductions ahead of the conference.
One of the rooms on the third floor will be designated as a Coaching Room for exclusive use by people participating in the Coaching Program. The overall time commitment is about 4 hours and it’s the coach’s responsibility to schedule the activities below:
- Meet in person or via a video call ahead of the conference to exchange introductions, answer any questions the apprentice has as they prepare to attend the conference, learn about apprentice’s career goals, and review the conference schedule together. Plan to attend some talks together.
- Meet on Friday during lunch or at any other convenient time. You can make this time your own, and for example, review the code base for a project of interest and ways to contribute or talk about what the mentor’s work entails and how they deal with challenging situations.
- Do a short check-in meeting on Sunday to discuss takeaways from the conference and any next steps.
- The coach and the apprentice can stay in touch as desired, but there is no expectation for them to do so.
Inclusion at DevConf.US
Inclusion is a priority for DevConf.US. We are making an effort to accommodate the needs of people who want to attend. We are also setting expectations for inclusive behavior through our code of conduct and media policies, and are prepared to enforce these.
Read on for more information about the inclusion features we are offering and let us know if there is anything else that would make it possible for you to attend the conference or would make it a better experience for you.
The conference will include coffee breaks in the morning and a sandwich/salad bar lunch on Friday. Vegetarian and gluten-free options will be available.
DevConf.us is held on the second and third floors of the George Sherman Union at Boston University. As you enter the building, there is a cafeteria on the left, where you can find an elevator that will take you to the conference floors. Registration is on the second floor.
One of the rooms on the third floor will be designated as a Quiet Room, where conversation and interaction are not allowed. All attendees may feel free to use the Quiet Room as needed.
One of the rooms on the third floor will be designated as a Nursing Room for attendees who need a private space for breastfeeding or pumping. Please ask for a key at the registration desk.
One of the restrooms on the third floor will be designated as an all-gender restroom for attendees who feel more comfortable using those facilities.
Travel information will be launched as soon as it is finalized!