Important dates

• CfP opens: September 10, 2026
• CfP closes: November 8, 2026
• CfP notifications: November 30 - Dec 6, 2026
• Schedule and registration: December 14-20, 2026
• Event dates: February 26-27, 2027

General information
The event will be held at MIT World Peace University (MIT WPU) in Pune, India. We expect all speakers to present in person at the venue. All talks, presentations, and workshops will be conducted in English.

Please note that we do not cover any speaker expenses, including accommodation or travel.

There is no admission or ticket fee for DevConf.IN, but all attendees and speakers must complete a free registration to attend.

Session types

• Talk: A presentation, usually with slides and demos. It should be bite-sized and focused on a certain topic. This means that you should not expect to be able to cover multiple broad areas in one talk. The default talk slot is 45 minutes (we recommend 30-minute talk and 15-minute Q&A and speaker connect).
• Lightning talk: A short presentation focused on getting people interested in something new. The goal of the lightning talk is to convey key information in a clear and concise manner. Smaller technical topics, project introductions, and research/thesis topic introductions are great ideas for lightning talks. The default lightning talk slot is 15 minutes.
• Workshop: A hands-on demo where you interact with the audience to share your knowledge and experience on a particular bite-sized topic. The goal of a workshop is to teach or practice a skill. As a result, workshops should be actionable and goal-oriented. The default workshop slot is 75 minutes.
• Booth: A staffed table for conversations about the project and interaction with contributors, users, and attendees. All booths are technology-focused and need to go through the CfP review process. We do not accept any financial sponsorships for having a booth at a DevConf event. Booths remain open throughout both days of the conference.

Submission limit

To ensure high-quality proposals and efficiently streamline the review process for our CfP Review Committee, each individual is limited to submitting up to three proposals in total. This limit includes all submission types (talks, lightning talks, workshops, meetups, activities). If you are listed as a co-speaker on any submission, it will count toward your individual limit.

Two-speaker limit

To ensure a high-quality schedule featuring a broad range of topics and speakers, we are setting a limit of two speakers per submission. This limit includes all submission types (talks, lightning talks, workshops). For booths, you can only submit up to two contact people in your proposal. However, it is allowed and expected that there is a larger number of staffers onsite. Exceptions may be considered for panel discussions or other collaborative formats. If you require more than two speakers, please provide the reason in the "Notes" section of your proposal.

While developing your proposal, consider the following:

• All material should be presented in English
• You can submit more than one proposal
• You can edit your proposal(s) after submission (until the CfP Closes)
• Submissions don't need to include completed slides

• Make sure the submission is relevant to the DevConf.IN audience:

  1. Is the content original or the way the content is presented original? Avoid overview sessions. Focus on technical, community project-oriented content. Talks with a lot of audience interactions and demos are encouraged.
  2. If the session focuses on a product, is it about technical aspects? Avoid all marketing and sales presentations, product pitches are received poorly.
  3. Does the talk cover new/planned work and ideas or does it review previous work? New and upcoming work generally increases the chance of acceptance. We'd like to see emerging topics that might hit engineering in 1-2 years.

• Before hitting enter, ask yourself:

  1. Does the content match the level of difficulty and the duration?
  2. If you were to attend your talk, would you feel excited?
  3. Why should people attend your talk instead of another session?
  4. What would the audience gain from your talk?