You can reach the organizers by emailing info@devconf.in. The official chat platform for communication is Matrix.

Yes, you can find a list of recommended hotels here.

No, due to the size of the MIT campus and the high daily foot traffic, we are unable to offer parking. If you plan to drive or ride a bike, please check for publicly available parking areas near the venue.

We cannot guarantee Wi-Fi access for all attendees at this time. However, we are working to provide connectivity in the conference rooms and will share updates as we receive more information from the venue.

As a speaker, you will have Wi-Fi access in the room where you are presenting.

DevConf.IN is primarily an in-person event with some virtual elements, such as conference chat and streaming of select sessions. However, all presentations must be delivered in person, and virtual presentations are not an option.

A talk is where you present, usually with slides and demos, to an audience. A talk 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 time slot for each talk and Q&A is 45 minutes (we recommend 30-minute talk and 15-minute Q&A and speaker connect). A talk has one primary speaker and, optionally, a secondary speaker.

Please note that this year all presentations will be delivered in person.

A lightning talk is 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 topics for lightning talks.

A lightning talk is 15 minutes long. A lightning talk has one primary speaker.

All lightning talks are delivered in person.

A workshop is a hands-on demo where you and other workshop leads interact with the audience with the goal 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.

A workshop is 75 minutes long. We allow up to 2 active presenters in a workshop.

All workshops are conducted live and are not recorded or streamed.

A booth is a staffed table at the event. Booths are open to all participants at all times, and they serve as a place for conversations about the project and interaction with contributors, users, and attendees.

There must be at least one person at the booth at all times and there must be at least two staff members registered. Preference is given to booths that will run on both days.

Each track/theme has a review committee of 3 - 7 members that are subject-matter experts. The process consists of multiple phases to ensure fair and thorough evaluation:

• Blind Review: Reviewers assess anonymized proposals based solely on content.
• Captain Review: Track captains prioritize talks, ensuring a mix of topics and experience levels.
• Final Selection: The CfP Committee makes final decisions, prioritizing sessions across all tracks holistically, and preparing speaker notifications.

Decisions are based on content quality, alignment with track themes, diversity in difficulty levels, and speaker experience. Since DevConf events are organized globally, we prioritize speakers from the same region as the event. For DevConf.IN, that includes Asia and the Pacific region.

During the review process, track captains may move your session to another track without prior notification. They can also contact you and suggest changing the session format, combining talks, or identifying potential keynotes.

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, and booths). If you are listed as a co-speaker on any submission, it will count toward your individual 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.

As a speaker, you will have Wi-Fi access in the room where you are presenting.

Yes, all talks (excluding workshops and meetups) will be recorded and made available on our YouTube channel after the event.

Yes, please upload your slides to our CfP platform by signing in and updating your session. We recommend publishing your slide deck and any other relevant materials before your session starts to ensure attendees can access them in advance.

No, your talk time already includes Q&A. For example, if you have a 45-minute session, plan to leave 5-10 minutes for audience questions. Once your time is up, even if Q&A was brief, you must leave the room to allow the next speaker to set up. Follow-up discussions can continue in the hallway.

Each room will have a volunteer to assist with timing. They will display countdown cards as you near the end of your talk and can introduce you if desired.

Yes, we will be providing meals for our speakers. Further details regarding speaker catering will be shared directly with them closer to the event. Please note that all meals served at the venue are indian vegetarian.

No, we do not cover travel or accommodation expenses for speakers.

DevConf conferences are Red Hat-sponsored events, and we do not accept external financial sponsorships or paid advertising. Our goal is to maintain a community-focused, non-commercial atmosphere that prioritizes open source education and collaboration.

While we do not offer paid commercial sponsorships, we provide two main non-monetary avenues for open-source projects, user groups, and communities to gain visibility:

1. Showfloor booths: We host a dedicated Showfloor at the venue specifically for showcasing open-source technologies, projects, and community initiatives. Projects can apply for a community booth through our CfP process to demonstrate software, engage with attendees, and share their mission in person.
2. 2. Digital Community Partnerships: Local user groups, meetups, student networks, and open-source communities can apply to become an official Community Partner. This promotional exchange offers website logo recognition, joint social media promotion across LinkedIn and Instagram, and inclusion in our year-round community network.

Much like our speaking sessions, booths are reviewed and accepted through our Call for Proposals. We welcome submissions from upstream projects, non-profit organizations, and community groups. Because space at the venue is limited, our committee reviews all proposals to ensure the content is relevant and valuable to our technical audience.

The most important rule is that booths must focus on open source technology and community engagement, not commercial products or sales pitches. Your proposal should outline what technology you will be showcasing and how you plan to interact with the attendees (e.g., live demos, hardware displays, or interactive tutorials).

Yes, booth proposals follow the same timeline as our session CfP.

A Community Partnership is a non-monetary, promotional collaboration between DevConf.IN and local tech communities, user groups, student networks, and open-source organizations. Our goal is to work together to amplify open-source initiatives, share knowledge, and grow the regional developer ecosystem.

As an official Community Partner, your group receives:

• Official Partner Kit: Ready-to-use graphics, banner images, social media templates, and email copy to make sharing effortless.
• Website Recognition: Your logo listed on the official DevConf.IN website as a Community Partner.
• Social Media Amplification: Dedicated shout-outs and cross-promotional posts featuring your community across our official LinkedIn and Instagram handles.
• Future Collaboration: Inclusion on our priority list for early outreach, CfP updates, and partnership opportunities for future DevConf events.

We ask our partners to help spread awareness about DevConf.IN within their networks by:

• Sharing event announcements (ticket registrations and call for proposals) across your communication channels (Slack, WhatsApp, mailing lists, or social media).
• Promoting DevConf.IN during your virtual or in-person events.
• Encouraging your members to attend and contribute to open source.

No, community partners are encouraged to participate, but there are no mandatory quotas for talk submissions or registrations.

Simply email our team at info@devconf.in with your group’s name, social links, and primary point of contact.

No. Community Partnerships are strictly promotional and awareness-driven exchanges. To maintain fairness for all community members and adhere to venue capacity limits, partnerships do not include guaranteed ticket allocations, reserved swag, or special onsite recognition. All partner members and leaders must register through the standard attendee registration process.

A Matrix server is a communication platform. It supports many methods of communication, including text, voice, and video streaming. Matrix is an open standard for interoperable, decentralized, real-time communication over IP. Learn more at https://matrix.org/faq/.

Open https://matrix.to/#/#2025.in:devconf.cz to get started.

Matrix servers are all federated. This means you can use another Matrix server account on the DevConf server. For this reason we don’t offer direct user registration.

Many online and open source communities host Matrix servers and offer accounts. You can also self-host. Here are some places to get an account:

• matrix.org - A server provided by the Matrix Foundation
• Your community's server if you plan to use the account as a contributor, not just during DevConf events (e.g. Fedora, Mozilla etc.)
• You can also find a potentially helpful list of public servers at https://joinmatrix.org/servers/
• Another option is to host or self-host your own server. For more information, visit https://matrix.org/hosting/ or https://github.com/spantaleev/matrix-docker-ansible-deploy

While creating an account, you will be asked to choose a client and you can choose the client based on your preferences. We recommend using Element because it supports all features we use at DevConf events, such as “spaces”, “threads” and “pinned events”.

Absolutely! DevConf rooms are public and federated, which means you can use your existing account to join. Open https://matrix.to/#/#2025.in:devconf.cz to get started.

The server will be online for the duration of the conference. We believe Matrix offers the best possible solution for mixing local and remote attendees, and we have already invested significant effort into its implementation. While we cannot guarantee its continued availability beyond the conference, we are committed to exploring Matrix as a long-term communication solution. Your feedback and experience will be valuable in shaping our future decisions.

Because Matrix is decentralized and users registered on other servers, you’ll remain able to connect with each other via direct messages and other chat rooms even if our server is taken offline.

In theory, any client should allow you to join the devconf.cz rooms. However, not all clients support all features, #2025.in:devconf.cz for example takes advantage of “spaces”, “threads” or “pinned events”. If your client does not support these features, you may not have the optimal experience. We recommend using Element, because it supports all features we use.

Admission to DevConf.IN is free and only requires that you register for a free ticket.

We use registration to manage several logistics issues around DevConf.IN.