DevRelCon is back in San Francisco for two days of developer relations, developer experience, community management, developer marketing, and more.
This year our theme is around the two sides of metrics of dev rel: how do you measure developer relations and how do you measure developer productivity?
We're excited to receive talks on other dev rel, DX, community topics too! See more in our blog post: https://devrel.net/events/2020-devrelcon-sf-cfp-is-open
Guidance on a successful submission:
Our CFP this year reaches out to two potential types of practitioners:
A. You're in a DevRel, DX, community team or you do DevRel-type of work in your role. Share topics that pertain to your daily work as someone on a DevRel team or similar. How do you measure success, build strategies, partner with other orgs, engage with your communities, perfect documentation, etc.?
B. You're in an Engineering team where your role is to study and advise what dev tools to use. You may be measuring whether your choice of tools has improved "dev productivity" and how to measure that. Share your experiences, challenges, and how you have tried to measure "dev productivity." Our DevRelCon audience of DevRel/DX practitioners would love to hear your solutions and challenges.
1. Make sure to clarify the personal/professional experiences that you plan to share as part of your talk. This is a practitioners' conference where we want people to openly share their challenges, the solutions that they are testing, metrics, and results in progress. Make sure that if you are sharing advice (tips and tricks, pitfalls to avoid, etc.) that the advice is grounded in actual hands-on experience.
2. You don't have to be an expert or have completed your "experiment" to offer a valid talk. If you are in the process of trying out a new solution to a challenge, we welcome your sharing how things are going even if you feel that you don't have "final conclusions." As a practiioners' conference and a place of sharing experiences, we welcome your using your talk to solicit advice from the audience after the talk.
3. Details! We thoroughly read all submissions, so the more detail the better. A 1-2 sentence submission that stays very high level will not have a strong chance of getting accepted. As mentioned above, please be clear about your planned topic, the problems you are helping to solve, your personal/professional experiences and use case of the challenge, what steps you've taken to solve it, and toward what metrics for success.
You can use the "DESCRIPTION" section for the abstract that you would post publicly and use the "NOTES" section to add as much detail as possible: your specific use case/business model, your specific challenges/solutions in progress/ongoing questions, etc.
At DevRelCon, we prioritise submissions that:
Our talks are usually 20 minutes long and we'll consider lightning talks too.