FOSS Club SRM - Updates thread

simply sharing the planner sheet. Will be sharing the feedback form results here soon.

The event photos are available here (future events we use ente dw)

https://drive.google.com/drive/folders/1t1aU4bMLf4dgqjVy0Fh8Sw9OuUHJNkAg?usp=sharing

Planning Kickstarted, in the below thread. further event related public updates and post event planners will be posted in the below thread.

Let’s hope this month long format yields crazy good projects!
Happy Hacking to all : )

Hello,

All preparations for tomorrow’s hackathon have been completed and the event is fully set from our end.

Event responsibilities:

  • Registration Desk: Tushar, Azam and Sourav
  • Snacks: Ayush, Anish, Adhwaith and Antony
  • Crowd Work: Team FOSS Club SRM-KTR

Looking back, around one and a half months ago the idea of organizing this hackathon was still uncertain and seemed quite challenging. Since then, with consistent planning and coordination, things have steadily come together, and we now stand ready for the inauguration tomorrow.

Finally, we are all set for tomorrow’s event.

1 Like

Hey everyone, I’m Adwaith from FOSS Club SRM-KTR. I was in the organizing team (POC) for the Frappe Workshop, and it was the Open Source Hands-on Session held on 6th May 2026. Sharing a quick overview and GBU of how it went, from an organizer’s perspective.

Event Intro
The Frappe Workshop was an online, hands-on session organized by FOSS Club SRM-KTR, featuring Immanuel Raj, who’s a SysOps Engineer at RtCamp as the speaker. We saw participation from students and also working professionals, all of them seemed genuinely curious about open-source tech. Thorough details regarding the session, technical content, and participant engagement are mentioned in the report attached below.

The FOSS Club SRM’s ā€œFrappe Workshopā€ turned out to be very successful in terms of content and participation.

Good :

  • High level of participation by all participants
  • Nice balance of students and professionals attending the event
  • Live coding made the workshop more interesting and easy to follow
  • Insights on the industry provided by Immanuel Raj of RtCamp

Bad :

  • The workshop started at little past the scheduled time
  • Some participants were unable to replicate the process locally due to moving from Doppio box to the presenter’s laptop

Ugly :

  • As this was an online event, there was some lag in connecting and setting up the environment for the live coding sessions.

In summary, the workshop served its purpose well in introducing Frappe and infrastructure tools used by it in open source projects.


EventReport.pdf (537.6 KB)

Hey Folks,

I’m Sachin Prasanth, I’ll be starting my new position as a club lead of FOSS Club SRM.
Few things about myself:

  • Researcher in Trustworthy Machine Learning
  • Researcher at IIT Madras and Massachusetts Institute of Technology
  • Led the Technical Team and conducted two talks - Zero to One Machine Learning and an Introduction to Docker environment.

I’ll be leading the club for the next few months and will be recruiting new members. Will be announcing the core members soon!

1 Like

Hey everyone, I’m Adwaith from FOSS Club SRM-KTR. I was part of the organizing team (POC) for the ā€œZero to One: GoLangā€ session held on 27th June 2026. Sharing a quick GBU (Good, Bad & Ugly) of how the event went from an organizer’s perspective.

Event Intro

The Zero to One: GoLang session was an online beginner-friendly workshop organized by FOSS Club SRM-KTR in collaboration with FOSS United, featuring Harsh Patel as the speaker. Harsh is a Software Developer with industry experience in Go, backend development, automation, and large-scale web platforms, making him well-suited to introduce participants to Go and its ecosystem.

The session focused on helping beginners understand GoLang fundamentals, its syntax, development workflow, and practical use cases. Students from different years attended the workshop with an interest in learning a language that is widely used in cloud-native development, backend engineering, and open-source projects. Thorough details regarding the session, technical topics covered, and participant engagement are mentioned in the report attached below.

Overall, Zero to One: GoLang successfully achieved its objective of introducing participants to Go programming through practical explanations and real-world insights.

Good :
Strong participation throughout the session, with attendees actively engaging in discussions and asking questions.
The session was beginner-friendly, making it accessible even for participants with little or no prior experience in Go.
Harsh shared practical industry experiences alongside language concepts, helping participants understand where Go is used in real-world development.
Live demonstrations and code walkthroughs helped attendees better understand Go’s syntax and workflow.
Participants appreciated the interactive nature of the workshop and the opportunity to clarify doubts during the session.

Bad:
A few participants required additional assistance while setting up the Go development environment before following along with the coding examples.
Some topics had to be covered at a quicker pace towards the end due to time constraints, leaving limited time for advanced discussions.

Ugly :
Being an online event, a few attendees experienced occasional internet connectivity issues, causing them to miss parts of the live coding demonstrations.
Minor delays occurred while resolving setup-related issues for some participants, which briefly interrupted the flow of the session.

Summary

The Zero to One: GoLang workshop successfully introduced participants to the Go programming language and provided a solid foundation for those looking to explore backend development, cloud technologies, and open-source contributions. Harsh Patel’s industry experience and practical approach made the session engaging and informative, and participants left with a clearer understanding of how Go is used in modern software development.

1 Like

Hello everyone,
I am officially out of college and stepping down from the FOSS club. I am going to share a few of my learnings and points with each of the future organisers of the clubs that they can follow.

I was very happy to get help of @Sachin_Prasanth when things got very busy and helping the club sustain. Currently the organiser position has been passed on to vaibhav who will also assisted by pranav from the FU Coimbatore chapter who is currently in SRM for masters. Thanks to you pranav as well to jumping in an sinking ship ASAP to help.

First explore Event Planning Guideline for Conferences - FOSS United Knowledge Base, https://docs.fossunited.org and then just read through below points

Basic things before the below procedures:

  • Every opinion matters
  • People are human, forgive them and help them learn
  • Families first, studies then and then club (ps: my opinion)

Procedures involved, all steps and progress ideally document in the forum:

  1. Discussion meeting discovery event meet to discuss on when and what to do
    1. what we are doing this in event is FOSS related
    2. CFPs has to be listed always minimum two weeks before the event
    3. When we are doing try not to clash with CT’s
    4. also don’t clash with Aarush, Milan or any flagship event of any clubs
  2. go to club coordinator
    1. get event approval, with sign
    2. get venue approval, with email - SRM-SHBF
    3. get Dr. V tirumurugan get his sign campus life sir, you need his permission to do promotional activities in SRM, with sign
    4. So if you SRM reimbursement always let SRM know 1 year prior
    5. if you want FOSS reimbursement submit it in forum event
  3. Once approved with above stuff, post confirmation in forum
    1. start posting in social media
    2. get 2-3 posters
    3. start doing C2C , build an internal schedule with team to facilitate this
    4. if extra people are there also setup an helpdesk to get more reach
    5. parallely ask our club coordinator that we can send promotional event email to our full dept with HOD approval
    6. if the event is after 6pm / late event you need to send permission request to all hostel wardens for late permissions, esp for girls without fail.
  4. Pre-event checks:
    1. venue coordinator number - basic utility issues
    2. PoC keep two people to attend event related query calls
    3. do dry run of the event - what roles are given? what is the timeline?
    4. CoC rules (Code of Conduct) explain Team members must adhere to the code of conduct, and when a violation occurs, specific steps must be taken. If a participant or club member reports an issue - such as misconduct or inappropriate comments, they should immediately be directed to involve a neutral third party. This could be another participant, yourself, or a lead maintainer from the club. In this scenario, the lead acts as the primary contact, while you provide assistance. The core principle is to always involve this neutral ā€œturnoutā€ party to handle the situation directly rather than escalating it immediately. For urgent matters, there is a 24/7 code of conduct violation hotline mentioned here Code of Conduct
    5. check AV and AC systems one day prior
    6. get an print out participant list with having name, email (email compulsory for srm folks) and two field to do the signature before event compulsory, after event (not needed but beneficial)
    7. Keep the feedback form ready
  5. On the day of event:
    1. have two people for photos and videos
    2. one of those two people will actively post stories / posts
    3. get signatures for check-in of participants, scan it, share it to sir and get that sign from club coordinator and then stamp seal from HoD Office. this is officially an regular OD proof.
    4. if possible, get an group photo of the event at the end
    5. lastly, share the feedback form to the participants.
  6. Post event:
    1. events Postmortems - Good, bad, ugly to be posted in forum within 14days, Post-Event Reporting - FOSS United Knowledge Base (use club letter head)
    2. if possible, also share responses of feedback in the end of event postmorterm pdf.
    3. you can also share photos publically in our ente album
    4. for club members Present OD, get a list of members who have helped for event, form an email with letterhead requesting present OD give to club coordinator for approval, once approved share withs FA’s … While collecting information of the students for present on duty. Always get the name, email, registration number, faculty name, faculty email, and what degree course they are doing.

As always, happy hacking, keep learning, growing.

3 Likes

RAGForge: Build Your Own Local AI Knowledge Assistant

Hey everyone, I’m Vaibhav Gupta, Head of FOSS Club SRM-KTR. We recently organised ā€œRAGForge: Build Your Own Local AI Knowledge Assistantā€, a hands-on workshop focused on Retrieval-Augmented Generation (RAG) and building a local AI knowledge assistant. The event was held on 31st August 2026. Here’s a quick GBU (Good, Bad & Ugly) of how the event went from an organiser’s perspective.

Event Intro

RAGForge: Build Your Own Local AI Knowledge Assistant was a hands-on technical workshop organised by FOSS Club SRM-KTR at SRMIST, Kattankulathur.

The workshop was designed to introduce participants to the fundamentals of Large Language Models (LLMs), Retrieval-Augmented Generation (RAG), embeddings, vector databases, semantic search, and document processing through a practical, beginner-friendly approach.

Participants were introduced to tools and technologies such as Ollama, Qwen, ChromaDB, and Streamlit. The session went beyond theory, guiding participants through the complete process of building a functional local AI knowledge assistant — from uploading and processing documents to generating embeddings, retrieving relevant context, and generating responses using an LLM.

We also encouraged participants to fork the project repository and build upon it by creating their own applications, such as research-paper assistants, documentation chatbots, campus knowledge assistants, or completely new ideas.

Overall, RAGForge successfully achieved its objective of helping participants move from understanding the concepts behind RAG to actually building and experimenting with a working application.

Good

  • Strong participation throughout the workshop, with attendees actively engaging in discussions and asking questions.
  • The session made complex concepts such as RAG, embeddings, vector databases, and semantic search approachable for beginners.
  • Hands-on implementation helped participants understand the complete RAG pipeline rather than learning only through theory.
  • Participants gained practical exposure to local AI tools such as Ollama and Qwen.
  • Live demonstrations of document processing, chunking, embedding generation, retrieval, and context augmentation helped participants understand the workflow.
  • Participants were encouraged to fork and modify the repository, promoting experimentation and open-source collaboration.
  • The interactive environment allowed participants to clarify their doubts and experiment with the project.

Bad

  • A few participants faced difficulties setting up the required tools, dependencies, and local AI environment.
  • Some participants required additional assistance during the initial setup and troubleshooting process.
  • Due to time constraints, some advanced RAG concepts and optimisation techniques could not be explored in depth.
  • Participants had varying levels of technical experience, making it challenging to maintain the same pace throughout the hands-on session.

Ugly

  • Setup and dependency-related issues occasionally interrupted the flow of the practical session.
  • Some participants experienced system-related difficulties while running local AI models.
  • Internet connectivity and installation issues caused minor delays for a few attendees.
  • Managing the technical flow of the workshop while simultaneously addressing individual participant queries presented some organisational challenges.

Summary

RAGForge: Build Your Own Local AI Knowledge Assistant successfully introduced participants to the fundamentals and practical implementation of Retrieval-Augmented Generation.

The workshop provided hands-on exposure to LLMs, embeddings, semantic search, vector databases, document processing, and local AI models, while encouraging participants to experiment and build beyond the provided project.

From an organiser’s perspective, the event was a rewarding experience that allowed us to create a space for students to learn, build, experiment, and explore the possibilities of open-source AI.

The ultimate goal was simple: **move participants from ā€œWhat is RAG?ā€ to ā€œWait… I just built this.ā€