open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • What type of projects will I be working on?
  • Execution
  • Proof of concept
  • Surprise
  • Pairing

Was this helpful?

  1. Coaches & Student coaches

Projects

PreviousScreening studentsNextPartner Communication

Last updated 3 years ago

Was this helpful?

What type of projects will I be working on?

We have a wide range of interesting projects — from NPO's to universities, and from startups to big corporates. But they all have to be open source. Take a look .

There are three main types of projects:

Execution

The client has a clear idea in mind about the end result and the end user of the application. In that case the students will get the ball rolling during osoc.

Proof of concept

The client has pretty solid idea, but it still requires some finetuning. The client might be uncertain about the feasibility of a certain idea, concept or solution. In this case the students can provide some clarity by providing a new proof of concept. The students will exercise some creative freedom and will spend some time ideating.

Surprise

A client might not have specific guidelines or preferences? They might want the #osoc experience, but they're not sure about the expected end result. The students can take the lead and surprise the client with their creativity, enthusiasm and skills!

Pairing

We try our best to pair the right coach with the right project. You have a say in this a couple of months before osoc starts. Your job is to coach the team, to guide them to do a good job. You're not supposed to do their job — but it does help if you have some prior knowledge when it comes to the subject or the skills needed to complete the project. So do let us know what type of projects you like and what you're good at besides coaching (which is your primary skill).

You'll be working on one or two projects, alone or with an other coach, depending on the size of the project and your availability. See under attend.

last year's edition of Belgium
Half-time or full-time