Certain Updates regarding the club direction:
The club core members have been sitting down with @Siddharth_Shivkumar and @rahulporuri to align the direction of the club for the '26–'27 academic year with FOSS United’s vision.
Two sessions have been conducted so far: the first on July 29th, followed by another meeting with Siddharth and the faculty in-charge of the club at SIT on August 11th. Below are the minutes from each session.
Minutes of Meeting (MoM) — FOSS Club Discussion
Meeting Overview
Date & Time - July 29, 2026
Context / Topic - FOSS Club Direction, FOSS United Collaboration, & Strategic Shift
Attendees - Siddharth Shivkumar, Rahul Poruri, Soham Kulkarni, Girish Sharma, Sreevals Nair, Ishan Sinare, Chahat Patel, Parul Kolhe
Key Agenda & Discussion Points
1. Introductions & Core Team Engagement
● Attendees engaged in round-table introductions.
●The FOSS Club core team members were formally introduced to @Siddharth_Shivkumar and
@rahulporuri to establish rapport and clarify leadership responsibilities.
2. Perception & Philosophy of FOSS
● Siddharth actively sought to understand how club members perceive Free and Open Source Software (FOSS) and what values drive their engagement.
●The team discussed current student awareness, highlighting both the alignment with open-source principles and areas where guidance is needed to foster true open-source ethos.
3. Strategic Shift: From Event-Centric to Contribution-Centric Model
● Institutional Constraints & Student Engagement: Discussed the college’s stance on events, current scope, and challenges regarding timing conflicts and low student attendance/turnout (“student inertia/laziness”).
● Reframing the Club Culture: Agreed on transitioning the primary focus of the club away from holding frequent event-heavy schedules and toward building a sustained contribution-centric culture where students regularly contribute to real open-source projects.
●Retrospective (What Worked vs. What Didn’t): Evaluated past initiatives to pinpoint operational successes and identifying areas of improvement in event planning, student retention, and follow-through.
4. FOSS United Initiatives & Summer/Season of Code (SoC)
●Student Development Program (SDP): Explored the possibility of bringing in an expert or representative from FOSS United (FOSSU) to host workshops and mentor students for the Student Development Program.
● Newsletter Collaboration: Proposed integrating and collaborating local editorial efforts with the official FOSS United newsletter to amplify reach and highlight local contributions.
Important Resources & Communication Channels
Category Link / Channel Description / Purpose
Communication Telegram: View @fossclubs Primary Telegram channel for ongoing communication, coordination, and network updates.
Resource / Guide Contribution Ideas - FOSS United Knowledge Base FOSS United reference documentation for club contribution ideas and project execution frameworks.
Action Items & Next Steps
●Communication Setup: Ensure all core members are active on the main Telegram channel (Telegram: View @fossclubs).
●Contribution Framework: Review the FOSS United contribution ideas documentation to draft a contribution roadmap tailored for club members.
● Newsletter Outreach: Connect with the editorial lead to explore content-sharing or cross-publishing with the official FOSS United newsletter.
● SDP Speaker Planning: Reach out to FOSS United representatives regarding speaker/mentor availability for upcoming development sessions.
Meeting Minutes
Date: August 11, 2026
Attendees: Mayur, Siddharth, Girish, Sreevals, Ishan, Chahat, Parul
Summary of Discussion
1. Introductions & Mentorship
● Mayur introduced himself to Siddharth and discussed ongoing support and mentorship
for open source initiatives.
● Addressed why individuals often feel lost in the FOSS ecosystem when overly fixated on
GitHub alone. Discussed ways the club can better guide members.
2. Open Initiatives & Scope of Events
● While the club aims to lean toward technical events, there is an opportunity to
incorporate non-tech open-source initiatives (e.g., translating documentation into
regional languages to improve accessibility).
● Explored how the club can inspire the community through open initiatives.
● Highlighted October as Open Hardware Month, discussing potential collaborations with
makerspaces for an integration event where makerspace members can utilize club tools.
● Mayur noted that all proposed initiatives are entirely feasible, provided there is a
designated "resource person" to oversee them.
3. Audience Engagement & Polling Strategy
● Proposed sending out polls to gauge member interest and filtering for commitment by
nudging respondents toward a "good first issue" in their chosen domain before tackling
complex, real-world problems.
● Recommended structuring future polls around broader domains/interest areas (e.g.,
"Data-Related Projects," "Design") rather than standard tech stacks (e.g., web
development, AI/ML, cloud) to keep options exclusive and distinct.
Action Items
● Create a detailed plan for how to make all events planned more specific and engaging
for the audience.
● Collect member interest through targeted polls.
. The team was able to take care of everything independently, even though I was completely AWOL due to medical issues.
,