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
  • 09:00 [all teams] Week overview
  • 09:30 [team only] Deployment day
  • 13:00 [optional workshop] Handover Dossier input: How to make your projects Live Long & Prosper 🖖
  • 13:00 [team only] Deployment day
  • 14:30 [all teams] SYSTEM STRESS TEST
  • 1. Jitsi stress test + chance to scream
  • 2. Mic test
  • 17:00 have a nice day 🥳

Was this helpful?

  1. Organisers
  2. On-site editions: 4 weeks of well-organised serendipity
  3. Calendar Example Remote Edition (BE)
  4. Week 4: Deliver

Day 1: Ship ship ship

Make sure your project is live and stable!

PreviousWeek 4: DeliverNextDay 2: Pitch pitch pitch

Last updated 3 years ago

Was this helpful?

This is an example of the remote edition fo 2020. Go to the website of your specific edition if you want to figure out what's happening now!

09:00 [all teams] Week overview

Let's go over the week together

09:30 [team only] Deployment day

Make sure your project is stable and shipped!

13:00 [optional workshop] Handover Dossier input: How to make your projects Live Long & Prosper 🖖

It's DELIVERY week, and we all know that everything is...? ON FIRE 🔥!

But before you set stuff on fire, think about what happens after this last week, and especially what happens to your "baby"? Longevity of the project depends on how you define your and team dynamic looking forward.

13:00 [team only] Deployment day

Make sure your project is stable and shipped!

14:30 [all teams] SYSTEM STRESS TEST

We want to make sure Jitsi will hold up when we are doing the project breakout rooms, and your mics will hold up during the demo day

1. Jitsi stress test + chance to scream

2. Mic test

Check if your interviewees and hosts will make a good appearance on the demo day stream;

  • Limited background noise

  • Stable microphone

And update the project description sheet with hosts and interviewees for the Demo Day.

17:00 have a nice day 🥳

This workshop will give you input for your .

We all meet in 1 , with our cams on and... scream, sob, complain, laugh hysterically, swear, sing – for 1 minute ^^ Don't have a mic or a cam? Come over anyways! Every extra test is a good one 👌

Handover Dossier
jitsi room
http://meet.openknowledge.be/ventmeet.openknowledge.be
This is the meeting room where we'll vent