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
  • Example structure
  • Day 2
  • Day 3
  • Day 4

Was this helpful?

  1. Organisers
  2. On-site editions: 4 weeks of well-organised serendipity

Hackathon day 2 — 4

Week 1 — Day 2 — 4

PreviousKick-off day 1 (or chaos day)NextBuild — week 2

Last updated 4 years ago

Was this helpful?

Example structure

  1. Teams prepare client meeting (day 1 and 2) - Get briefing from coach - Prepare questions and meeting

  2. Teams meet with client (day 2) - Ask questions, take notes, ask input

  3. Teams prepare hackathon (day 2) - Set up dev environment - Read up on briefing, study client - Prepare battle plan

  4. Brainstorm (day 3, but not for well-defined projects) - Only for projects that need brainstorming for their project

  5. Scope (day 3) - Define what you're going to build during the hackathon.

  6. Hack (day 3 for well-defined projects, day 3 and 4 for brainstorm projects)

  7. Present to other teams (day 4)

  8. Feedback from other teams (day 4, but not for brainstorm-type projects). Clients can see the result on the next client meeting.

A more detailed agenda can be found on the website.

Belgium: Spain:

Day 2

Day 3

Day 4

https://2019.summerofcode.be/practical.html
https://2019.summerofcode.es/whoweare.html
Example of day 2
Example of day 3
Example of day 4