# Week 1 Day 1: Welcome to the Madness

## **First day: nice to meet you&#x20;*****live*****!**

We expect you to be there at 09:00 ✨*sharp*✨ on Monday morning.

### Location

BOSA – Simon Bolivarlaan 30, bus 1 WTC III 1000 Brussels – a 5 minute walk from the Brussels North station!

{% embed url="<https://www.openstreetmap.org/directions?engine=fossgis_osrm_foot&route=50.86037,4.36076;50.86072,4.35612>" %}

Be there on Mondays and Thursdays – for the first two weeks.

**Introduction**\
**– for everyone**
------------------

Welcome to open summer of code! You'll get an introduction about what osoc is about, what [**Open Knowledge Belgium**](https://openknowledge.be/) is, how we work ([**code of conduct**](https://help.osoc.be/global/code-of-conduct) & [**how we work**](https://help.osoc.be/global/way-of-work)), what our 4 weeks will be about and what you'll be ✨[**delivering**](https://help.osoc.be/global/how-to-deliver-like-a-pro) ✨.

**Get to know your team & your project** \
**– team only**
---------------

### Who’s who & what do you do?

* Icebreaker; get to know each other!
* Share your skills, talents hobbies, …

### What are we going to do?

* Study the briefing – You can find the briefing in your [**project site**](/osoc22/projects-partners/projects-partners.md)**.**
* Define the goal
* Compose list of questions for partner/client

  *-> Compose it together in the folder of your team under meeting minutes:* [*https://drive.google.com/drive/folders/10hWr4Tc4CnIka0XqHZ1FmJeOKryfCHKW?usp=sharing*](https://drive.google.com/drive/folders/10hWr4Tc4CnIka0XqHZ1FmJeOKryfCHKW?usp=sharing)

## Pick your talk

These talks will be live at BOSA. Meeting room in the calendar!

### \[optional talk] Dev 101 – Intro to Dev 001 by Chris / Dev for non dev / w\.. even is dev by Chris

Chris, 2-time student alumni and now second time coach shows the non-devs what devving really is. Want to expand your 🧠, extend your [**t-profile**](https://en.wikipedia.org/wiki/T-shaped_skills) and understand your teammates better? Grab lunch and attend this talk!

### \[optional talk] Git workshop by Clément

Working together on code and products can be hard. Git and GitHub make that easier! Clément will be happy to help you out.

## Partner meetings

### How

Mondays are always full of opportunities, and at osoc they present themselves as partner meetings.

To keep in mind for your first meeting:

* [ ] Present your team members (students and coaches)
* [ ] Check if you understood all needs and goals
* [ ] List all the questions you have
* [ ] Decide who does the talking
* [ ] Decide who takes notes

Some tips and tricks can come in handy if you've never attended a client meeting before:

{% embed url="<https://www.youtube.com/watch?v=SvO5EfTW6Hw>" %}
Tutorial: how to do a client meeting.
{% endembed %}

### When

Scroll down to see more days, scroll to the right to see more teams and their links!

{% embed url="<https://docs.google.com/spreadsheets/d/1NC3uATQqpqzZiJf1yiymdm4IPLrldd2_c541jWOb-wA/edit?usp=sharing>" %}

## Prepare for the *☄️* *H A C K A T H O N ☄️*

The hackathon starts tomorrow\... What will your team build in the coming two days?\
Check out [**day 2**](/osoc22/calendar/week-1-explore/week-1-day-2-meet-the-client-and-start-hacking.md) for more details 🥳


---

# 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://help.osoc.be/osoc22/calendar/week-1-explore/week-1-day-1-welcome-to-the-madness.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.
