# Communications & Branding

## Short Description

Make osoc and its partners ✨ *shin*e ✨ ! \
Show potential future students, partners and coaches why they should participate in open summer of code.\
\
What the comms team is responsible for? 💪\
You'll be doing internal communications, write project Highlights, take photos of all the teams and students, make buzz towards the outside world during #osoc22 (social media, blog, videos, photos), do the promo for the demo day. \
In addition to this, you are encouraged to rethink and set up a new branding strategy for open summer of code 2023 and think of new ways to promote osoc to participants (students, coaches, partners, sponsors) next year.

## Project

Project template: <https://cloud.openknowledge.be/s/mT42qn9ykfKqezp>

*Your partner will give you a nice introduction as well on the first partner meeting!*

### Resources

* *About the partner*\
  Open summer of code is a 4-week summer programme during which innovative open source projects are made by incredibly motivated students, coaches & organisations.&#x20;

  Osoc is powered by Open Knowledge Belgium, a non-profit supporting a world where knowledge creates power for the many, not the few.\
  The osoc [website](http://osoc.be)\
  The [Open Knowledge Belgium](http://openknowledge.be) webside\
  The [Open Knowledge international](https://okfn.org) website
* *Style components*\
  [FIGMA](https://www.figma.com/file/94fo7Pl97dmlQxPv4UJkDV/Design-Project-socials-\(Copy\)) #osoc21
* [Partner package ](https://cloud.openknowledge.be/s/BGmKK3GGZSkdGQM)for 2022
* [Partner deck](https://cloud.openknowledge.be/s/4t7kHQ9kzkqAMwz) for 2022

### GitHub

Example:

* Team: <https://github.com/orgs/osoc21/teams/the-floof-fighters>
* Repository: <https://github.com/osoc21/RoadBase>

### **Discord Channel**

\#osoc-comms

## File storage

*For collaboration & storing files. Add the root folder to your drive:* [*https://drive.google.com/drive/folders/1D08v4bgtmXnukuTmZKsI7lpz3uWxLNW0?usp=sharing*](https://drive.google.com/drive/folders/1D08v4bgtmXnukuTmZKsI7lpz3uWxLNW0?usp=sharing)

{% embed url="<https://drive.google.com/drive/folders/1D08v4bgtmXnukuTmZKsI7lpz3uWxLNW0?usp=sharing>" %}

## Team

### Coaches

#### Lead

Niels Dewelde

#### Support

Lotte Goyens

### Students

Britt Vanzegbroeck (student coach)\
Guilherme Chuna

### Specific councillors

Miet Claes

## Logo's

![Logo osoc SVG](https://1076799073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDYgKzDptfv6QWUDRXzYS%2Fuploads%2FNPQbNyNbxsie2QszDWFD%2Flogo-osoc.svg?alt=media\&token=63e50288-1dd9-4ca3-9c7a-f1a6edf85e2c)


---

# 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/projects-partners/osoc-comms.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.