# History of Campus Community

Back in 2014, something awesome happened at the CUSAT campus in Kochi. It all started with a "Maker Party Kochi" event that brought together a bunch of people who were crazy about tinkering and creating.

{% embed url="<https://youtu.be/xyyKzKckbxE?si=zgF06IivaAAJvdE0>" %}

Little did they know, this was just the beginning of something huge that would impact the lives of tons of students. They were all inspired by the Mozilla Foundation and the Mozillians community, and that's when the idea of TinkerHub was born – a place where innovation and curiosity would thrive. The gang found their hangout spot at CITTIC within the CUSAT campus, and that's where everything kicked off. Their WhatsApp group became their virtual hub, where they'd chat, swap ideas, and welcome new members.

One person, Gopi Krishnan, had a big dream and made it happen by starting the first TinkerHub campus chapter at RIT in 2017. After that, TinkerHub exploded like a wildflower, with campus chapters popping up all over Kerala. Each chapter added its own flair to the mix, creating an awesome landscape of knowledge, collaboration, and growth.

By 2021, TinkerHub had grown into a network of 75 campus communities, reaching over 50,000 students and making a real impact. It all started with that little spark at CUSAT and grew into a massive source of inspiration, guiding students towards a future full of creativity and innovation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.tinkerhub.org/campus-community/campus-communities/history-of-campus-community.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
