Code of Conduct

The code of conduct applies to all students working on a project at open Summer of code, paid and non-paid, except for the enforcers (cf. rule 9). Please read these rules carefully, if you infringe on one of them, you must fulfil a task from the punishments section.

No worries, we also have an achievements section. When we think you did a great job, there are nice extras to earn.

§1 Location and work hours

We have strict rules for the location:

  1. Clean up your desk before leaving (aka the clean-desk policy).
  2. Do not leave anything precious when you are not around.
  3. Respect the building and area. Keep it clean, throw garbage in the bins, etc.
  4. If someone from the sponsors or partners enters the room and has something to say, you stop all work and listen (or at least, pretend to).
  5. You are at least 8 hours a day present at this location. You are welcome to fulfill these hours from 8am until 7pm.
  6. If you cannot work 8 hours during a certain day, you should mail at least 2 days in advance (cases of emergency excluded).

§2 GitHub

  1. Git is considered to be known.
  2. You will not commit a config file.
  3. You will use branches for development code you’re working on, as explained at the Git 101. You’re free to ask for extra help when doing it.

§3 Gear

  1. You bring your own laptop.
  2. You will not forget your battery charger. Ever.
  3. Everything you use or borrow, must be returned in the same state as before.
  4. You will lock your computer when leaving your desk.

§4 How to write #osoc18

  1. You must refer to our event as #osoc18 or “open summer of code”

§5 Programming

  1. You will document everything. All documentation has to be written in English.
  2. You will write code to the best of your efforts.
  3. Your work is, unless, in some very rare cases, otherwise stated, open source, and will be shared with your neighbours, working towards a best-effort cross pollination policy.
  4. Projects are copyrighted 2018 by Open Knowledge Belgium, the author is you. At the top of every file there should be a copyright notice and author notice, before committed to the GIT repository.
  5. All projects use 4 spaces indent (except when other coding standards apply). If you cannot configure this in your editor, you should start using another editor.
  6. Your code should not allow SQL-injecting, XSS-ing, etc.
  7. Whenever you’re about to write a 300+ line file, you first ask yourself whether you would need a rewrite and if you don’t think so, you ask the permission to commit the file from your project manager.

§6 You’re an ambassador

  1. During the event, interest(ing|ed) people (e.g., journalists, potential employers, experts) may enter the location. When they’re asking about your project, cease work and answer them in a best-effort way.
  2. Everyone in your team is an ambassador of the project, without exception (yes, also the back-end coder). You will explain your project with pride and will train yourself to pitch the project as if it was your start-up.
  3. The project doesn’t end at the last day of #osoc18. You should try to “design” your open source project that it becomes a win for you when you are asked to pitch your project later on, or when you’re contacted by journalists, asked to attend an event, and so forth.

§7 Communication

  1. All official communication, documentation and so on has to be done in English in any case. During work hours you are also expected to switch to English in all spoken communication. The only exception is when all of the project and location partners and students have the same first language.
  2. Our communication and project managers are responsible for the general management. When they ask you to do something, you drop all work and help them in a best-effort manner.

§8 Blog

  1. Your team should write several updates about the project you’re working on during the open Summer of code. Ask our communication manager to make you a WordPress login at
  2. As mentioned before, all communication happens in English, therefore also the blog will be in English. We don’t expect complete articles, a few paragraphs that explain the progress of your project is enough. Feel free to ask for help from our communication and project managers.
  3. People like pictures, don’t be afraid to take photographs or add some images to the blog post.

§9 Enforcers

  1. The board members of Open Knowledge Belgium and the freelancers are the enforcers of this code of conduct.
  2. The enforcers are above this code of conduct; they cannot be punished, unless they accept their punishment
  3. The board members of are free to change the code of conduct at any time. When changes take place, all open Summer of code members will be mailed.
  4. Project leaders, as mentioned in section ‘Your freedoms’ can enforce the code of conduct. If in doubt, you can contest charges from a project manager to someone of the board.


When you infringe on one of the rules, you must choose one punishment.
P1: The next morning you bring coffee and couques (Danish pastries) for your team.
P2: Buy beers for your entire team at the end of the day.
P3: Get ice cream for your team.

Infringing on one of the rules multiple times does not grant you remission at any time.


There are lots of achievements to obtain. They are to be found on this very website under the form of badges. Some need proof of accomplishment, some require a recommendation of a fellow student or project manager, others just need the enforcers approval.

  • GitWizard = Wizard of contributions & commits
  • Blog Minion = Mastering the digital written word
  • Tweet Royalty = Biggest Generation Y – Influencer
  • The Apprentice = Learner of skills and magic
  • The Dribbbler = Adobe, do you speak it?
  • Proactivator = Knows what to do before we do
  • The Flash = You work fast, very fast
  • Little Sunshine= Always look on the bright side of life
  • The Punisher = The only one not getting punished
  • Multilingual = You have 5 years of experience in Swift
  • Presenter = You are a true Erlich Bachmann
  • Early Bird = When are you not here?
  • Determinator = 4 weeks ≠ 16 days
  • Mr./Mrs. Clean = You reinvented the clean desk policy
  • Bingo! = Because Bingo
  • MVS – Most Valuable Student = We’ll recommend the s**t out of you afterwards
  • Badge Achievement = You come up with the achievements

Your freedoms

§1 Freedom to change projects

If you don’t feel at ease in your team or you feel the project you are on is not suited for you, you are free to change projects once. If this is the case, please send an email to or talk to Dries in person.

§2 Freedom of tools

Except for Git and SSH, you are free to use any software or hardware stack that you are accustomed to. Our servers run Ubuntu and are set up with a LAMP stack by default.

§3 Freedom to learn

You cannot know everything. You are free to ask questions to anyone on another project who seems to have the best expertise on that subject.
You are free to request any project’s source code.

§4 Freedom to work whenever you’re most productive

You are requested to attend open Summer of code 8 hours a day, which you are free to choose from the hours the location is open. As long as you are capable to deliver at every milestone, you’re safe.

§5 Freedom of speech

You are free to tweet, using the proper hashtag #osoc18, use facebook, use google plus, or use any other social network, whenever you want to say whatever.

§6 Freedom of information

Open Knowledge Belgium aims to be 100% transparent. Therefore you can request any kind of non-privacy-prone information about the not-for profit organisation and the open Summer of code event on the mailinglist

Skip to toolbar