| CFP closed at | November 25, 2016 22:00 UTC |
| (Local) |
Community DevRoom: Call for Papers
tl;dr:
- Community DevRoom takes place on Sunday, 5 February
- Submit your papers via Pentabarf at https://penta.fosdem.org/submission/FOSDEM17 and PaperCall.io at
- Indicate if your session will run for 30 or 45 minutes, including Q&A. If you can do either 30 or 45 minutes, please let us know!
- Submission deadline is 25 November 2016 and accepted speakers will be notified by 12 December 2016
We are happy to let everyone know that the Community DevRoom will be held this year at the FOSDEM Conference. FOSDEM is the premier free and open source software event in Europe, taking place in Brussels from 4-5 February at the Université libre de Bruxelles. You can learn more about the conference at https://fosdem.org.
The Community DevRoom will take place on Sunday, 5 February.The purpose of the devroom is to provide concrete, useful advice on how to best enable contributors to be successful so more FOSS software gets written.
Why This DevRoom
Our goals in running this DevRoom are to:
- Connect folks interested in nurturing their communities with one another so they can share knowledge during and long after FOSDEM.
- Educate those who are primarily software developers on community-oriented topics that are vital in the process of software development, e.g. effective collaboration.
- Provide concrete advice on dealing with squishy human problems
CFP Description
Talk Topics
We are seeking proposals on all aspects of creating and nurturing communities for free software projects. Please submit a proposal on any topic of your choice, but here are some suggestions to help get your creativity engaged:
-
How to navigate the different cycles in the lives of contributors - What happens when you’re just feeling bored with what you’re doing or burn out in general? How can we plan for the natural ebbs and flows of contributor interest and availability?
-
Compensating volunteers - Is this important? How is it done well? Should we discourage people from “working for free”?
-
Career progression for community oriented professionals - How do you level up as a community manager? Developer Advocate? What skills do you need to best serve your community and how do you acquire them? How do we explain what we do all day so people value this work?
-
Community health metrics - How do you tell if your community is actually doing well? How do you gather real numbers to prove that your gut instincts are correct?
-
Conflict resolution - How do we continue working well together when there are conflicts? Is there a difference in how types of conflicts best get resolved”this code is terrible” vs. “we should have a contributor agreement”? We are especially interested in how tos / success stories from projects that have weathered conflict.