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 meetings
  • Communicating with partners
  • Partners on your Discord channel

Was this helpful?

  1. Coaches & Student coaches

Partner Communication

Partners meetings

Some partners might just become almost part of the team, while others will only meet 2 or 3 times.

We do have set days for client meetings. An example:

  • Every Tuesday, week 1 to 3

    • Week 1, Tuesday: briefing and questions

    • Week 2, Tuesday: presenting the result and findings from the hackathon

    • Week 3, Monday: presenting progress

  • The Demo day

    • See the end result!

  • If you need more meetings, feel free to plan them!

Communicating with partners

Apart from the meeting days (see previous topic), it's a good idea to keep the partner up-to-date. A partner in the dark can be a worried one.

  • You can email them the report of the meeting, to follow up

  • Email them progress every week, maybe with some questions (you decide the pace)

  • Email them before or after the demo day with the delivery document and relevant delivery information

Depending on your team, you can send out the email, or you can have the team send out te email. Set up a google doc, so everyone can read and comment, and then let a student send it from the entire team.

Partners on your Discord channel

Only make partners join the Discord if this is really needed, if they want to and if you feel the students are comfortable with that.

When your partner does join your Discord channel, it's recommended to create a separate room without your partner. This way you can discuss things internally when needed.

Do inform the coordinators of this decision up front, so we don't have any surprises.

PreviousProjectsNextPractical

Last updated 4 years ago

Was this helpful?