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 is expected of me as a client?
  • How do I brief my team of students?
  • How do I provide feedback?
  • What will be done with the work afterwards?

Was this helpful?

  1. partners

The Partner's Job

PreviousAttendNextProjects

Last updated 4 years ago

Was this helpful?

What is expected of me as a client?

Your organisation will need to take some time to write a good briefing, and have some people available for meetings and feedback sessions during osoc. In some cases, questions will be asked via email.

How do I brief my team of students?

Before open summer of code, it's important to create a good briefing with what you expect of your team. The better the briefing, the less questions will pop up, the better the project.

In the briefing you will outline what kind of project your organisation envisions and what features and functions your end-product shall contain. Based on your layout, osoc mobilises the student profiles required to make this vision come to life.

In case you have a very defined project, a prioritised list of features will help the students to define and create something valuable for you. But, if you want the students to experiment, provide a good vision and mission to the students so they'll have a good sense of direction.

How do I provide feedback?

At the beginning of osoc, a representative of your organisation will present your organisation and project briefing to the students. From then on you will meet with your team once a week to receive pitched progress updates and give feedback. The meetings will be arranged up front.

In those feedback sessions you'll provide feedback to make sure the students are going in the right direction (on development, design, product management, ...).

Preferably, we have a single point of contact that can make the decisions that need to be made during the development of the project. This person will brief the students at the beginning of the project, and will provide feedback in July.

What will be done with the work afterwards?

At the end of osoc, your project will be published under a free and open-source license, compatible with the and will be showcased at the osoc Demo Day, where students present the final product to you and the broad public. You will receive access to all documents, research, designs and code created at osoc, so that you can share it within your own or with other organisations.

Open Source Initiative