Call for Proposals (CFP)
To help encourage the open collaboration, discussions, and debates necessary to help JS Interactive be successful, we invite developers, industry thought leaders, and technical experts to submit a proposal to speak.
First Time Submitting? Don’t Feel Intimidated
JS Interactive is an excellent way to get to know the community and share your ideas and the work that you are doing. You do not need to be a chief architect or long-time industry pundit to submit a proposal, in fact, we strongly encourage first-time speakers to submit talks for all of our events. In the instance that you aren’t sure about your abstract, reach out to us and we will be more than happy to work with you on your proposal.
Consider the following as you write your proposal:
1. How will the audience benefit from your presentation?
2. Why should YOU be the one to give this talk? You have a unique story. Tell it.
There have been sessions covering a wide range of topics supporting users and contributors of the JaveScript ecosystem, and we encourage you to “think outside the box” to come up with your own unique topics.
A great talk weaves a story — it can address issues that developers struggle with, break down and explain complicated topics, and cover new ground in technology. All breakout presentations will be 30 minutes. We are framework agnostic. We also accept panel proposals. You can indicate your format in the CFP submission.
If you choose to submit multiple talks, please do so with the understanding that they should all represent your current passions and interests. These should be submitted as separate talk topics as you can muster. Multiple talks do not necessarily increase your chance of being selected.
Dates to Remember
- CFP Open: January 31, 2018
- CFP Close: Friday, April 20, 2018 11:59PM PT
- CFP Notifications: Wednesday, May 30, 2018
- Schedule Announced: Week of June 4, 2018
- Slide Due Date: Monday, October 1, 2018
- Event Dates: October 10-12, 2018
How to Submit Your Proposal
We have done our best to make the submission process as simple as possible. Here is what you will need to prepare:
1. Choose a submission type (Presentation*, Panel^^, Hands-On Workshop).
* 30-minute presentations will be limited to one speaker; no co-speakers.
^^ If you are proposing a panel discussion, please make sure that you list all of your potential panelists (4 maximum) in your abstract. We will request full biographies for each if a panel is accepted.
Note: New for 2018: All panels are required to have at least one female speaker.
2. Choose one or more topic(s) for your proposal:
- Building and evolving APIs
- Community Building
- Diagnostics(performance, debugging)
- Emerging use cases(AI, Big Data)
- Frameworks(lessons in selection, considerations, migration, comparisons)
- Front-end engineering with Node.js
- Node.js project
- Operations(Serverless, Containers)
- The Case for Node.js
Note: Final tracks for the conference will be based on accepted submissions.
3. Provide a biography, including your previous speaking experience (900 characters maximum).
4. Who is your target audience? (Web Developers, New Developers, Enterprise, DevOps).
5. Provide us with an abstract about what you will be presenting at the event (900 characters maximum)
6. Describe who the audience is and what you expect them to gain from your presentation (900 characters maximum)
8. Select the experience level (Beginner, Intermediate, Advanced, Any)
9. List any technical requirements that you have for your presentation over and above the standard projector, screen, and wireless Internet.
Your abstract will be the cornerstone of your proposal.
This is your chance to *sell* your talk to the program committee, so do your best to highlight the problem/contribution/work that you are addressing in your presentation. The technical details are still important, but the relevance of what you are presenting will help the program committee during the selection process.
This is the abstract that will be posted on the website schedule, so please ensure that it is made up of complete sentences (and not just bullet points) and that it is written in the third person (use your name instead of “I”).
Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): How can our code be faster? What does faster mean? In this journey we would walk through different performance optimization techniques you can apply to your code. We will see the start from –v8-options, and we will discover how to leverage what v8 tells us to optimize our code. We will discuss hidden classes, function optimizations and deoptimizations, and inlining. We will discuss the tools and the libraries you can use to do perf analysis on your code. In this journey, we will discover that the main villain is Lord GC, and we will fight him to reclaim our memory! At the very end, we would reach a point where even allocating a callback is too slow: Ludicrous Speed.
Describe who the audience is and what you expect them to gain from your presentation.
Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): The audience is a backend developer looking for ways to improve the overall performance of their code. This talk will highlight all the different optimization techniques to make their code run faster.
*Note: We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation is just as important as the content.
Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): These techniques can be applied to any code. Moreover, most OSS libraries might gain huge benefits from even a small bit of performance optimization.
Speakers will receive a complimentary pass for the event. Please note that 30-minute presentations are limited to one speaker; no co-speakers.
For panel discussions, all panelists and the moderator will receive a complimentary event pass; maximum 4 panelists plus the moderator.
All speakers are required to review and adhere to our Code of Conduct.