1 What is an “Unconf” and why should YOU organize one?

What is an “unconference”?

An unconference is a very well-named event. The unconf takes the traditional highly structured conference format and turns it on its head. There are no expensive registration fees, formal abstract submissions, or time-limited talks. To quote one organizer of a large unconferece, “We invite a couple of hundred really interesting people for an event without a program, which emphasizes interaction between the participants rather than on prepared presentations” (O’Reilly 2018).

According to O’Reilly (2018) and Andrea Wulf, the first “unconference” was held back in 1828 in Germany. It was put on by Alexander von Humboldt, the Prussian Polymath. For this 19th century event,

“he invited hundreds of scientists […] to attend a conference in Berlin. Unlike previous such meetings at which scientists had endlessly presented papers about their own work, Humboldt put together a very different programme. Rather than being talked at, he wanted the scientists to talk with each other. There were convivial meals and social outings […]. Meetings were held among botanical, zoological and fossil collections as well as at the university and the botanical garden. Humboldt encouraged scientists to gather in small groups and across disciplines. He connected the visiting scientists on a more personal level, ensuring that they forged friendships that would foster close networks. He envisaged an interdisciplinary [coalition] of scientists who would exchange and share knowledge.”

This old idea is new again in the 21st century tech industry. Large unconferences attract web developers, data scientists, and other tech-minded folks. They often are similar to “hackathons” where developers and designers come together to create a functioning software product during a short period of time, usually only a few days.

What is the history of the R unconf?

The mother of the Chicago R Unconference and the Uncoast Unconference is the rOpenSci unconference, or #runconf. It began in 2014, and has been held every year since. It has also spurred the OzUnconf event in Australia, first held in 2016.

At these events, attendees create new R packages, make Shiny Apps, write documentation (like this book!), and contribute to existing packages. Check out some of the previous projects below:

• #runconf18
• #ozunconf18
• #runconf17
• #runconf16
• #runconf15
• #runconf14

This guide is a work in progress! If you’d like to contribute to the list above, please submit a pull request.

What can you expect at an unconf?

Why should you organize an unconf?

• You get to meet a lot of great people
• You get to learn a lot of new things

References

O’Reilly, Tim. 2018. “The True Inventor of the Unconference.” March 2018. https://www.linkedin.com/pulse/true-inventor-unconference-tim-o-reilly/.