IndiaFOSS 3.0 Documentation - Request for Volunteers Comment

@Ansh and I have worked on the detailed documentation of IndiaFOSS 3.0, and we invite all IndiaFOSS volunteers to comment in case we’ve missed any details or if there are any details that need correction.


This comprehensive documentation carefully details the planning, execution, and outcomes of IndiaFOSS 3.0. Organized into distinct sections, it covers various workgroups and areas of responsibility, highlighting both the preparatory phase and the actual event. Key areas such as Website Development, Community Outreach, Design, Diversity, Marketing & Communication, and Sponsorship are thoroughly reviewed, with insights into initial plans, achievements, and challenges faced. The documentation also delves into Phase II work-groups including Venue Management, Participant Management & Travel Desk, and Speaker Management, among others. Special attention is given to innovative initiatives like Low Waste Management and the anticipated FOSS Awards. This document serves as a valuable resource, providing a transparent and detailed overview of the event’s organization and management, and stands as a testament to the collaborative efforts of the team and volunteers.

Overall Manager

@mriya11 - Riya, the Overall Manager of IndiaFOSS 3.0, played a crucial role in the event’s success. She skillfully managed every aspect of the conference from start to finish. Her responsibilities included coordinating teams, addressing challenges, and ensuring smooth operations. She was actively involved in all the workgroups mentioned below.

We divided the roles and responsibilities for IndiaFOSS 3.0 into multiple workgroups, as follows:

Phase 1

Phase 1 of volunteering application was opened in the beginning of the conference planning which was in July 2023. Workgroups of Phase 1:

  1. Website
  2. Community Outreach
  3. Design
  4. Diversity
    • Outreach
    • Diversity Scholarship
  5. Marketing & Communication
    • Content
    • Social Media
  6. Sponsorship



@nikochiko, @Aldrin_Jenson, @adithyaanilkumar, @Andrew_Bastin

Initial Plan:

  • Work on a new homepage, assist other work-groups, create a schedule, list anonymized talk proposals, develop a ticket page with QR-based tickets, and help participants with ticket transfers.

What Went Right:

  • Volunteers quickly created web forms for outreach, diversity, volunteer, travel-desk, and other work-groups.
  • Successfully implemented a new UI for the homepage, ticket, and schedule pages.
  • Developed a conference check-in system using QR codes, aiding registration desk volunteers.


  • The new homepage design was delayed, affecting the development and launch timeline.
  • There were bugs in the check-in system, causing some check-ins to not be properly recorded in the system.

Community Outreach

Team: @ansh, @mangesh_x0

Initial Plans

  • It was observed that student participation was low in previous events.
  • Special efforts were decided upon to reach out to student communities and colleges to increase student attendance.
  • Additionally, reaching out to previous community partners who have helped promote the conference in their networks was planned.

What Happened Exactly

  • Targeted outreach was conducted via email and by reaching out to partners from previous conferences.
  • Received 63 Community Partnership applications.
  • Onboarded 23 communities as partners.
  • Multiple student community partners were involved, including Model Engineering College Kochi, Open Source Developers Club JIIT, Mukti (MSRIT), Indian College Network, Devfolio, SAIT (CUSAT, Kochi), Cybernity, and 12 FOSS Clubs.
  • 26 Community Partners were onboarded, some major ones being OpenStreetMap, SMC, Tech4Good Community, VGLUG Foundation, Hasgeek, Internet Freedom Foundation, SFLC, Women In Tech collectives, REAP Benefit, Open Data Kerala.

What Went Right

  • The student-professional ratio at the conference was 45:55 out of 1300 participants.
  • Community Partnerships were a success overall, playing a big role in the conference selling out two weeks before the event.
  • A good number of community partners were onboarded, including student communities.


  • Not all community partners adhered to the partnership prospectus.
  • It was challenging for volunteers to track whether the onboarded communities were actively promoting the conference or completing the minimum tasks mentioned in the prospectus.
  • Going forward, it may be beneficial to prefer communities that actively support our vision or have previously collaborated with FOSS United.
  • A volunteer should actively keep track of all activities to be done by partners.
  • Partnerships may be officiated only after certain outreach/promotion of the event is done by the partner.



@Ajzal, Jessica, Jeswin

Initial Plan:

  1. Create announcement posters (speaker, community partnership, sponsor, marketing).
  2. Design homepage and schedule page.
  3. Create mural design, banners, signage, and stickers.

What Went Right:

  • All designs were aesthetically pleasing.


  • Many designs were delayed due to requiring feedback from multiple volunteers.


Team: Priyanshi, @Ruchika, @ansh, @mangesh_x0, @wisharya

Initial Plans

  • Reach out to potential speakers through email, LinkedIn, and personal connections.
  • Assist them with proposal creation and submissions.
  • Ensure good diversity among conference participants.

Diversity Scholarships

  • The program was initiated to enhance diversity at the conference and support access.
  • A detailed report is available here.

What Went Right

  • 15 women speakers/panelists participated in the conference.
  • Over 40 proposals were submitted by women.
  • Rs 1.55 Lakh was raised for the initiative.
  • More than 60 diversity scholars attended the conference.


  • While having 9 speakers out of 60 is a good start, the aim should be to increase this number.
  • The complete amount raised for diversity scholarships was not utilized.
  • Open applications did not reach the target audience.

Marketing & Communication


@Anupama_Bara, @Muhammed_Yaseen, Noel Varughese, Riya Sabu

Initial Plan:

  • Create content for the website and social media, manage social media, send newsletters, and maintain communication through forums and Telegram.

What Went Right:

  • Effective marketing led to over 1300 participants.


  • Posts were not synchronized across all forums.
  • Delays in social media posts and newsletter distribution.


Team: @rahulporuri, Vishnu Ajith, @wisharya, Aman

Initial Plans

  • Talk to existing FOSS United industry partners and see if they’re comfortable with their current sponsor tier for IndiaFOSS 3.0. Try to upsell them to a higher tier, if possible.
  • Reach out to the community to gather personal/direct leads. Here, ‘community’ refers to Telegram and various social media channels, including individual city FOSS channels.
  • Cold call/email big names in the Indian SaaS industry.

What Went Right

  • The proposed budget was 35 Lakhs, with FOSS United planning to use 17 Lakhs from the annual budget.
  • Raised 7.5 Lakhs through sponsorships; the rest was obtained through other sources (see IndiaFOSS 3.0 budget report).
  • High interest among companies to sponsor the event.


  • No industry partner upgraded their sponsorship tier.
  • Our sponsorship deck did not clearly state that a talk slot is not guaranteed; one sponsor assumed it was and withdrew when their proposal was rejected (moving forward, talk slots should not be mentioned in the deck).
  • One sponsor were interested but had to cancel due to last-minute issues and inability to travel to the conference and set up booths.
  • One sponsorship was rejected because we do not accept money from outside India.

Feedback Received

  • Potential sponsors could not see a Return On Investment.
  • Some pointed out that there were a lot of students, who were not their target audience.
  • Sponsors wanted to capture participant details with QR codes, which we could not deliver.
  • Our offerings were considered lesser compared to other events of this scale.

Phase II Workgroup

Phase 2 of volunteering application was live on 24th September 2023. Workgroup of Phase 2:

  1. Venue Management
  2. Participant Management & Travel Desk
  3. Speaker Management
  4. Parallel Session Management
  5. Videography, Video Editing Photography
  6. Live-streaming
  7. Emcee
  8. Food & Beverage

Note that when we initially opened the application, there were multiple workgroup options. However, due to challenges in distinguishing between certain groups, we later merged a few of them for efficiency. Space Management and Venue Management were combined, as were Participant Management and Travel Desk. Additionally, we integrated specific roles into existing categories rather than having separate sections. This includes the roles of Mobile Logistics Coordinators, undertaken by Riya, Litto, and Vishal, Managing Adhoc Jobs by Riya, and Volunteer Manager by Litto. We want to express our gratitude for their significant contributions and adaptability during these changes.

Venue Management


Shreya, @wisharya, @realvinay, @vishnus, Mark, @adithyaanilkumar


  • Book the venue, coordinate with the venue manager, and arrange for tables, chairs, lighting, screens, projectors, and internet.

What Went Right:

  • Adequate space with multiple rooms and a spacious catering area. Successfully set up booths for sponsors, workshop rooms, and displays for parallel sessions.


  • Delays in finalizing requirements due to unstable numbers of parallel sessions.
  • Confusion over internet requirements for the entire space.
  • The first floor was less crowded compared to the ground floor; sessions there attracted less foot traffic.
  • Frequent entry and exit of participants through Audi 1’s door caused disruptions.

Participant Management & Travel Desk


@KaranGandhi, @glitchyi, Website Work-Group

Initial Plan:

  • Assist participants with various queries related to the conference, including tickets, travel, accommodation, schedule, and other information.

What Went Right:

  • Successfully managed 1300 participants, which was beyond expectations.


  • Delays in providing “how to reach the venue” information and accommodation list.
  • Last-minute ticket transfers created a rush.
  • Overwhelming interest led to delayed responses to queries after being sold out.

Speaker Management

Team: Mythili, Debarko, @Subroto_Banerjee, @Vishal_Kashyap

Initial Plans

  • Maintain constant communication with selected speakers.
  • Resolve queries via emails.
  • Appoint 4 Speaker manager coordinators, each coordinating with a separate set of speakers.
  • Receive all slides one week before the conference.

What Went Right

  • Most talk confirmations were received on time, and speakers’ queries were resolved.
  • The talks proceeded according to the schedule without major delays; communication with speakers was maintained on conference days.


  • Two of the volunteers were students and could not dedicate enough time; another volunteer fell sick, increasing the workload for one particular volunteer and those outside the workgroup.
  • Slides were not received well in time, which could have prevented the slight delays that occurred.
  • Lack of effective means to contact speakers; having their phone numbers was not useful due to connectivity issues at the venue.
  • A possible solution is to inform speakers well in advance and keep them up to date.

Parallel Session Management


Lance, Shashank

Initial Plan:

  • Host various un-conference sessions like workshops, build stations, project showcases, Linux booths, and open spaces.

What Went Right:

  • Participants gained knowledge from a variety of options, which were less technical and more accessible than some talks.


  • First-floor tables had less visibility compared to ground-floor ones.
  • Workshop rooms were too small.
  • Lack of awareness about workshop sessions.

Videography, Photography, Video Editing

Team: @Krutika_Thakkannavar, @Ajzal, Jins Varghese, Outsourced vendors


  • Photography on the first floor was not done, as the vendor was not informed about it.

Everything else went well, and we received a lot of great pictures.


Team: @Arya_Kiran, @KaranGandhi, @Suslime, @Muhammed_Yaseen

Initial Plans

  • Set up a livestream of the event in coordination with the AV vendor.

What Went Right

  • The livestream was successfully conducted, with only minor AV issues.
  • The design template for the stream was prepared well in advance and looked great.


  • The volunteers had to ensure the livestream worked fine in both auditoriums and coordinate with different vendors in each.
  • One volunteer fell sick and could not attend the conference.
  • Feedback from the team suggested starting the conference later to give volunteers enough time to set up the livestream.



@stalwartcoder, Kiran, Yuktha Reddy Sweta Tanwar

Initial Plan:

  • Plan to have four emcees, two for each auditorium. They would switch the next day. Each emcee pair would prepare by reviewing the speaker’s bio and talk description for their assigned hall.

What Went Right:

  • The emcees hosted the event smoothly and coordinated well.


  • The schedule delay led to late planning for hosting.
  • Emcees switched their auditoriums a day before the conference, causing some confusion.

Food and Breakfast

Team: @realvinay, @wisharya

Initial Plans

  • Ensure the menu is inclusive and diverse enough for all participants.
  • Accommodate the food within the budget of 13 lakhs.

What Went Right

  • Overall positive feedback on food.
  • Food was arranged within budget.
  • Adequate seating space during lunchtime.
  • Low food wastage.


  • The menu was not inclusive; vegan diets should be accommodated.
  • Tea and Coffee should be available throughout the event.

Additional Workgroup / General Category:

  1. Task Assignment to the Volunteers
  2. Finance & Accounting
  3. Talk Review Group (invitation based)
  4. Conference Day Volunteering
    • Registration
    • Audi Management
    • Food and Breakfast
    • Crowd Management
  5. Low Waste Management
  6. FOSS Awards

Task Assignment to Volunteers


@mriya11, @wisharya

Initial Plan:

  • Divide volunteer onboarding into two phases: initial phase for certain work-groups, and a second phase mostly for coordination and logistics.

What Went Right:

  • Similar tasks were grouped and assigned to specific work-groups, which coordinated among each other.


  • Managing a large number of volunteers was challenging.
  • In phase 2, guidance for volunteers, especially regarding conference-day tasks, was unclear.

Finance & Accounting


@wisharya, @Ansh

Initial Plan:

  • Coordinate with vendors and sponsors for payments, confirm sponsor payments with accounting, generate invoices, address payment failures or receipt queries from participants, and manage orders and reimbursements for various items.

What Went Right:

  • Most tasks were completed on time.


  • Delays in payments to some vendors and in sharing receipts with participants due to workload.

Talk Review Group


Mark, @knadh, @rushabh, @Venkatesh_Hariharan, @rahulporuri, @Aakansha_Doshi, @realvinay

Initial Plan:

  • Form a committee of experts to review talks, workshops, panels, and other sessions, and assist in scheduling.

What Went Right:

  • The committee reviewed around 210 proposals, including talks, and parallel sessions, dedicating significant effort over a month.


  • Delays and confusion in the review process and in determining the number of talks and sessions to accommodate. In future editions, plan to close the Call for Proposals (CFP) earlier to allow sufficient review time.

Conference Day Volunteering

Team: All IndiaFOSS Phase I/II Volunteers, Most of City Chapter volunteers and FOSS Club Leas

Initial Plans

  • Assign all volunteers into workgroups for major tasks.
  • Hold an orientation meeting to brief them about their tasks.
  • Volunteers for tasks requiring more attention (registration desk, swag setup, livestream, booths) were to arrive by 7am.

What Went Right

  • Most major requirements were taken care of with no significant hiccups.
  • There were enough volunteers for ad hoc tasks.


  • The in-person meet at NIMHANS on 27 was announced late, and most volunteers could not attend as they were traveling.
  • An online meeting planned for that night was also canceled due to other urgent tasks at NIMHANS.
  • It was decided all volunteers would arrive at NIMHANS by 7 am to be briefed about their tasks, but only a few could come on time.
  • As a result, many volunteers were unclear about their responsibilities.
  • A notable delay occurred at the registration desk; different people had to be instructed on how to register participants.
  • Minor technical issues with tickets from our end caused some rush. Later, a miscellaneous registration desk was set up for participants who had purchased tickets but were facing issues.

Low Waste Management

At IndiaFOSS 3.0, FOSS United attempted to make it a low-waste conference in partnership with “Let’s Be The Change (LBTC).”


@realvinay, @vishnus, @wisharya

Feedback and Insights from the Let’s Be The Change (LBTC) team


  • It was indeed a low waste event and we love the NO GIFTING culture at FOSS United.
  • Two things we could have avoided
    • Avoided the Bagasse plates for breakfast
    • Ensure that caterers do not use wooden spoons (they were used for desserts)
  • We could have connected with the caterers at least a week before to ensure they are aware about the low waste event and help them provide cutleries if needed.


  • The email and digital awareness campaigns helped people to avoid creating more waste.
  • Not providing any tissues was helpful. (However this is possible if all plates and cutleries are clean and hygienic)
  • We need to work with the caterers to ensure that excess food is given to the needy and food waste being sent to piggeries/as a feed to animals/for bio-methanation instead of composting by the municipality. Reason being the first 3 practices mentioned are way more sustainable that just composting.
  • Food waste was minimal during both the days. It was around 20 to 30 kgs and was way lesser than a conventional event for a similar crowd as told by the caterer.

What’s Next?

In collaboration with LBTC, FOSS United will:

  1. Utilize Cutlery Banks in various cities.
  2. Engage with caterers at least two weeks before the event to ensure the execution of our low-waste plans.
  3. Recruit zero-waste volunteers from different cities to assist at cityFOSS conferences.
  4. Develop incentives for zero-waste volunteers from various cities.
  5. Offer eco-friendly t-shirts and goodies at future events.
  6. Promote the use of public transportation and shared cabs.
  7. Train lead organizers in conducting low-waste conferences.

The above can be also found at separate thread- Making FOSS United Events Low-Waste.

FOSS Awards

Earlier we decided the open the nomination during IndiaFOSS but we had bandwidth crunch during the conference so we couldn’t open the nomination. To see update on the FOSS Awards, please follow this thread.

Once again, we invite all IndiaFOSS volunteers to comment in case we’ve missed any details or if there are any details that need correction.


As mentioned by you, this was initially developed by Faris from Frappe right ? We can include his name in the team too


Major take-away lesson: To ensure that all logistics and ground volunteers meet together prior ( online atleast ) and be thorough with their responsibilities.

This mapping ensures there are no confusions on the event day.

Second, we should take printed versions of important copies - schedule, speaker details, contact etc. Trusting digital copies can be bottleneck sometimes.

I don’t quite think website group was involved with core travel desk, except updating website with travel desk info.

I also feel there wasn’t quite a heavy merge between these workgroups. The participant management was still heavily on payment update queries, non-receiving of tickets, invoice requests, ticket transfer emails etc.

  • The option for downloadable tickets and provision of tax invoice along with confirmation email should be explored next time.

  • We will integrate it with the system and create a process for this.

It points back to the first need of a proper briefing too. After the first catchup call, the volunteers were unsure of how to take the case up. Had to keep separate calls with each work group a day after to provide idea for the processes and response especially for participant management, speaker management, parallel sessions management.

This caused the primary delay in set up on day 1 - due to lack of wifi availability, some of the volunteers getting late, as they didn’t know exact reporting time ( as they couldn’t make it to the briefing the day before I believe) - we couldn’t do an online call as well.

The workflow was also a bit confusing as the volunteers couldn’t get enough time to familiarise with the check-in process. This could be more optimised next time.

The wifi arrangement plans were done too last minute as well, despite the requirement coming up earlier.

Wifi arrangement mapping:

  • Priority for registration desk
  • Back stages + Conference area
  • Unconference Area and Workshops
  • Participant use ( if under budget constraints)

Riya Sabu too - managed LinkedIn posting, and then volunteered at registration desk.

Some of the engagement activities planned ( quizzes, shoutouts etc. ) couldn’t be executed due to time crunch.

The confusion part - I am not sure of this - the emcees handled the audi’s exactly as planned prior.

The change was due to an inconvenience on Day 2 2nd half , one of the emcees had to leave for something important which was handled with a replacement.

We should also ensure that important information should be conveyed on a first-person basis, if they have chances to miss.

Situation: Mails can be missed out. We missed an important speaker replacement request which wasn’t followed up until a few days before the conference - missing action for it by around 7 to 10 days.

Additionally we should also add:

  1. Arrangement of Tshirts, Stickers etc., and their Management and Distribution at the venue.

  2. Management of Panel Discussions ( I will write about the context behind Women in FOSS panel and it’s challenges.)