Event call for paper submission forms differ: Some require 1000 character abstracts, others prefer shorter biographies, or require you to fill in the talk learning goals. The Developer Evangelism team uses Google docs for maintaining CFP abstracts, @dnsmichi also uses a doc for the biography and headshot URLs as SSoT.
Every year, developer evangelism prioritizes some key events in our ecosystem for which we run the conference proposal (CFP) process.
The event engagement with lightning talks, CFP submissions, etc. is organized in issues which are linked and summarized in the strategy epic. You can also find a calendar view of our events below:
Past submissions for CFPs are stored in the CFP Library.
To request that a Developer Evangelist submits a CFP to your event, please:
developer-evangelist-request template, and fill out the External Request section.CFP label.For every CFP process we are participating in, a CFP issue is created with details about the event, requirements for CFP submissions and any other relevant information that might be useful to potential speakers. The issue template contains guide on the necessary steps needed to ensure we keep track of all the submissions for each CFP.
Once a submission has been submitted, the author should add it to the CFP Library. This will allow us to repurpose CFPs efficiently.
All submissions, accepted talks, feedback and other result tracking happens in the CFP issue. The CFP workflow uses scoped labels to transition the issues through different stages. Please follow the CFP workflow handbook to apply required labels accordingly.
All issues with the CFP label appear on the dedicated CFP Issue board.