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
  • Most important
  • 1. Make sure you ship something.
  • 2. Make sure your client can find & reuse that ship.
  • 3. Make the ship discoverable & traceable for interested audiences.
  • 4. Support future teams by giving them the 411 in advance.
  • The checklist
  • Some help
  • The Handover Dossier
  • Github Pages
  • The Other Deliverables
  • The Handover Email
  • We use the last week to get it done

Was this helpful?

  1. Tutorials

Deliver Like a Pro

We created osoc to give students and newly graduates a first relevant work experience. We'll help you with communicating and delivering like a pro.

PreviousHostingNextPublish a Github Page

Last updated 3 years ago

Was this helpful?

You and your other team members will create a lot of valuable things for the client in these 4 weeks. It's important that they get to see it, use and reuse it (we are open!).

That's why you, as a student, are responsible to make sure you gather and communicate about this!

Most important

1. Make sure you ship something.

Make it something you'll be proud of, and you can show off in your portfolio 😎

2. Make sure your client can find & reuse that ship.

Gather everything, document it well and make sure they can find out about where to find everything (in the team's deliverables folder) via a handover email at the end of osoc.

3. Make the ship discoverable & traceable for interested audiences.

4. Support future teams by giving them the 411 in advance.

Giving someone the 411 means you give them all context and updates they need to hit the ground running; to make sure that they are as informed as possible. It definitely is possible your project returns next year.

So if you are working on a project that has been around the year before, make sure you get your hands on that information!

The checklist

Step 1: Go to your project page and find the link under "File Storage"

Step 2: Go to Deliverables

Step 3: Find the deliverables checklist

Step 4: Start checking boxes!

Some help

The Handover Dossier

Gather all the knowledge of the team’s project in this dossier. This will help the client understand what kind ship the team has built, how they got to that ship, and where to find everything.

  • Find the template in your team folder

Github Pages

The internet is volatile. Things disappear. Your effort should not. We want to make sure the project remains findable & traceable even after it’s removed from its domain name, and is still legible by people that don't want to dive in the code.

The Other Deliverables

Contacting press, user tests, .. Not everything has a guide. But we have many coaches, student coaches and even students to help out. Get in touch!

The Handover Email

Write a clear, professional email with a link to your deliverables at the end of open summer of code – and a kind goodbye.

We use the last week to get it done

Yes, it’s a lot. This is why we have the last week available to do that. our team is not just to “code”, “write”, “business”. They are here to learn to see the bigger picture, create a project, to grow. It’ll help them do that!

Make sure your project can survive on the internet, and you can refer to it in your portfolio. A link that can won't suddenly be taken down, like for instance on , will help you here.

Find examples of the handover dossier here

Find out how to

Get access to a []

Github Pages
https://drive.google.com/drive/folders/16z6e39rb6t7AAgYl0InFLsG09o8BI3BC?usp=sharing
create a Github page
example
template
Showing something that works on the demo day is key.
It can only work when it’s well-documented, and when the vision is crystal-clear.
Portfolio; students, coaches & oSoc / Making sure the project doesn’t disappear.
Good documentation, assets & guidance help future teams.
We created a
deliverable checklist 
to help teams accomplish these steps.

Go to your project page; for example ABB
There's a folder called "Deliverables"
Find the excel with the expected deliverables!
There are some templates, examples & guidelines to help you out.