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
  • Partners
  • Coaches
  • Availability
  • Students

Was this helpful?

  1. Organisers
  2. How to set up oSoc for your country

Selection

How to select the right partners, coaches and students

PreviousPreparationNextPractical

Last updated 5 years ago

Was this helpful?

Partners

  • Plan initial meetup to define project(s)

    • You can use a template with pre-defined questions. to get your hands on it!

  • Confirm projects (optional: invoice 50%)

Coaches

  • Have an intake with potential coaches

  • Select coaches

    • Balance full and half-time

    • Balance skills (devs, designers, comms, ...)

    • Balance experience

      • Have first-timers participate as assistant coaches.

  • Brief first-time coaches

Availability

Availability means being there for key moments, when the team needs a coach. Depending on the size of the team and how hard the project is, a coach can handle one or two teams.

Big or hard projects

  • Scope Think a big or complicated web-application — or a medium project with a lot of students with different skills (for example hardware mixed with software or for instance exhaustive research / creativity required).

  • Size Usually has a lot of students (more than 8 team members)

  • Coach Needs a full-time coach, or two half-time coaches. This requires a lot of availability. A mini project on the side is possible but not required (for instance an easy website or a very experienced team with a student-coach).

Easy projects

  • Scope Think a website, maybe with an integration with a fixed design. A project that is well-defined or easy to scope along the way.

  • Size Minimum three students

Students

  • Select students (with coaches) based on CV and/or motivational letter

  • Call the ones you're uncertain of

Coach There is always a coach available to manage the smaller team and the client, but probably won't be occupied the entire time. It is possible that a coach (or two half-time coaches) is managing two small projects at the same time. The coach however, should be available for both teams to coach them whenever they need it — see "".

Contact us
The job