GitBook: [master] 82 pages and 15 assets modified

README.md

@@ -14,7 +14,7 @@ This wiki has been created as a _guideline_ for participants of osoc: students,
 ## What everybody should know before we start; students, coaches and clients alike!
 
 * [What we are like: the Code of Conduct](code-of-conduct.md)
-* [How we work: The Osoc Way of Work & Play](way-of-work.md)
+* [How we work: The Osoc Way of Work & Play](way-of-work/)
 
 You're always free to break the rules; as long as you're trying to make it a better experience!
 

SUMMARY.md

@@ -23,7 +23,8 @@
     * [Day 3: Delivery Day](calendar-remote-edition/week-4-deliver/day-3.md)
     * [Day 4: Demo Day](calendar-remote-edition/week-4-deliver/day-4-demo-day.md)
 * [Code of Conduct](code-of-conduct.md)
-* [The osoc Way of Work & Play](way-of-work.md)
+* [The osoc Way of Work & Play](way-of-work/README.md)
+  * [Working Together in a Remote Setting](way-of-work/working-together-in-a-remote-setting.md)
 
 ## Students
 

calendar-remote-edition/week-1-explore/day-1-welcome-to-the-madness.md

@@ -13,7 +13,7 @@ Welcome to open summer of code!
 * What is osoc?
 * What is Open Knowledge Belgium?
 * What’s [the code of conduct](../../code-of-conduct.md)?
-* How does [osoc work](../../way-of-work.md)?
+* How does [osoc work](../../way-of-work/)?
 * Calendar overview
 * Deliverables \[[tutorial](../../how-to-deliver-like-a-pro/)\]
 

tools/discord/managing-notifications.md

@@ -2,23 +2,35 @@
 
 On Discord, you have fine-grained control over which notifications you receive at which time.
 
+{% hint style="info" %}
 **Leave mentions for @everyone and @here on.** The only people who can use these are in the coordination and communication team, and it's what we'll use when we need to be sure you read a message.
+{% endhint %}
 
-**To only receive notifications when you're mentioned:**
+## **Only receive notifications when you're mentioned**
 
 ![](../../.gitbook/assets/notifications-all.gif)
 
+## **Channel-Specific Notifications**
 
-
-**You can get also enable channel-specific notifications for the ones you're interested in, such as your project chat:**
+For the ones you're interested in, such as your project chat:
 
 ![](../../.gitbook/assets/notifications-your-project-only.gif)
 
 To keep getting notifications without getting a notification sound or your operating system's notification message pop-up, you can [turn on Do Not Disturb mode](https://support.discord.com/hc/en-us/articles/227779547-Changing-Online-Status).
 
-**To hide channels and categories in the left-side panel that you are not interested in:**
+## **Hide channels and categories in the left side panel**
+
+For channels you are not interested in, and to de-clutter your side panel.
+
+### Step 1: mute the channel
+
+![](../../.gitbook/assets/screenshot-2020-07-11-at-10.27.07.png)
+
+### **Step 2: Right-click on "open summer of code" \(Channel name\) & click "Hide Muted Channels"**
+
+![](../../.gitbook/assets/screenshot-2020-07-09-at-17.26.17.png)
 
-\*\*\*\*
+You will now only receive a notification whenever people mention you.
 
-\*\*\*\*
+![](../../.gitbook/assets/screenshot-2020-07-09-at-17.25.55.png)
 

way-of-work/README.md

@@ -0,0 +1,102 @@
+---
+description: This is how we do it.
+---
+
+# The osoc Way of Work & Play
+
+## **How We Work**
+
+![Motivation & Hard Work!](../.gitbook/assets/screenshot-2019-06-18-at-15.11.32.png)
+
+### **§2 Gear \(for on-site editions\)**
+
+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.
+
+### **§3 Location and work hours**
+
+#### Remote edition
+
+1. During COVID19 remote will be the default. Work from home or a location that provides you with a good working environment. If there is no suitable working place available to you, please get in touch [[email protected]](mailto:[email protected]).
+2. We work 8 hours per day. We do not expect you to work more than that.
+3. You are welcome to fulfill these hours between 8am and 7pm.
+4. Make sure you attend planned activities with teams, clients and in group  \(such as streams, meetings and standups\) as communicated in the calendar and by your coach.
+
+If you cannot work 8 hours during a certain day, you should mail [[email protected]](mailto:[email protected]) at least 2 days in advance \(cases of emergency excluded\).
+
+#### On-site edition
+
+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 partner organisations 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 fulfil these hours between 8am and 7pm. If you want to work late let us know. Specific locations might require special badges or a supervisor in order to be able to work past 7pm.
+
+If you cannot work 8 hours during a certain day, you should mail [[email protected]](mailto:[email protected]) at least 2 days in advance \(cases of emergency excluded\).
+
+### **§4 Your work**
+
+1. You will document everything. All documentation has to be written in English.
+2. You will do your work to the best of your efforts.
+3. Your work is, unless, in some very rare cases stated otherwise, open source and will be shared with your neighbours, working towards a best-effort cross pollination policy.
+4. Projects are copyrighted 2019 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. If you find yourself stuck with a problem for more than 1 hour, you will ask for help.
+
+### **§5 You’re an ambassador**
+
+1. Only for on-site editions: 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 own start-up.
+3. The project doesn’t end at the last day of \#osoc20. 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.
+
+### **§6 Communication**
+
+1. All official communication, documentation and so on has to be done in English. You are free to speak your native language when talking to your neighbour. From the moment you’re in a group with someone who does not speak the same language, you switch to English.
+2. Our communication manager and coaches are responsible for the general management across and between the different projects. When they ask you to do something, you drop all work and help them in a best-effort manner.
+
+### **§7 What's in a name**
+
+1. You must refer to our event as \#osoc20 or “Open summer of code”
+
+### **§8 Blog**
+
+1. You are encouraged to write a blog post or vlog about the project you’re working on during the open Summer of code. Ask our communication manager about it.
+2. As said before, all communication happens in English, therefore also the blog/vlog. We don’t expect complete articles or movies, to 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 or online messages.
+
+## **Your Freedoms**
+
+![Freedom for everyone!](../.gitbook/assets/screenshot-2019-06-18-at-15.11.25.png)
+
+### **§1 Freedom to change projects**
+
+If you don’t feel at ease in your team, or you feel there’s a serious mismatch with your project, we will try to switch you with someone from another project who has a similar role and skill set. Please send an email to [[email protected]](mailto:[email protected]) or talk to Astrid 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.
+
+You are free to use any technology stack that is most suitable for your project and client.
+
+### **§3 Freedom to learn**
+
+1. 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.
+2. You are free to request any project’s source code.
+
+### **§4 Freedom to work whenever you’re most productive**
+
+You are requested to attend osoc 8 hours a day, which you are free to choose.
+
+Make sure you attend planned activities with teams, clients and in group  \(such as streams, meetings and standups\) as communicated in the calendar and by your coach.
+
+As long as you are capable to deliver at every milestone and you're there when your team or client needs you, you’re safe.
+
+### **§5 Freedom of speech**
+
+You are free to tweet, using the proper hashtags \#osoc20, use Facebook, Instagram, Snapchat, or any other social network, whenever you want to say anything about osoc. As long as you're not harassing or hurting other people. See [Code of Conduct](../code-of-conduct.md).
+
+### **§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 non-profit organisation and the open Summer of code event. Visit [be.okfn.org](http://be.okfn.org/) for more details.
+

way-of-work/working-together-in-a-remote-setting.md

@@ -0,0 +1,86 @@
+---
+description: A guide on how to work together in a remote setting.
+---
+
+# Working Together in a Remote Setting
+
+## 🎬 Where Do We Start?
+
+This is a new environment for all of us, so let's make the best out of it! Nobody knows _yet_ what the best way is, but we will find out together.
+
+![We're all doing this for the first time at osoc. Let's get started!](../.gitbook/assets/screenshot-2020-07-11-at-15.16.34.png)
+
+## 📣 Be Vocal
+
+We can't see or hear each other all the time \(which is the case in a live setting\). So nobody will know when you're in doubt, or in need of help – if you do not speak up.
+
+![](../.gitbook/assets/osoc-remote-talktome.gif)
+
+### Working Out Loud
+
+Keep your teammates up-to-date on what you're doing. Update your tasks in your project management tool \(trello, kanban, github, ...\), hang out in the voice chats, perform daily standups, ... Whatever works for the team, just make sure you know what your teammates are doing and how they are doing!
+
+![A nice habit that started organically in the \#urban-brussels team.](../.gitbook/assets/screenshot-2020-07-10-at-12.07.35.png)
+
+{% hint style="info" %}
+Find a way to stay in touch and on top of work with your team. Some teams like to hang out in voice channels and play a tune, some teams like to greet each other every day and check in now and then. Find what feels good!
+{% endhint %}
+
+![](../.gitbook/assets/doing.gif)
+
+### Ask for Help
+
+Don't stay stuck in a loop for longer than 20 minutes. [There's plenty of ways to ask for help](../tools/discord/remote-helping.md), don't be afraid to ask for it! \#osoc was built on helping each other out, so we encourage you to ask and give help.
+
+![](../.gitbook/assets/screenshot-2020-07-11-at-15.26.44.png)
+
+## 🎳 Team Play
+
+### Team Work Makes the Dream Work
+
+We've selected you and your teammates because we think you have the right skills to bring this project to life, and each and everyone of you has value to offer. _**That means your teammates need you.**_ Take initiative and show us what you got!
+
+Feeling a bit lost in your role? Speak up, ask for help! We are in this _together_.
+
+![When one of us shines, all of us shine. When you work together, magic happens.](../.gitbook/assets/dogs.gif)
+
+### Take the Wheel
+
+The team gets to make decisions, and we expect you to take initiative. Coaches are here to protect/help you when situations gets hard, and to make sure you don't steer into an iceberg; but you are in charge as a student.
+
+![](../.gitbook/assets/panda.gif)
+
+{% hint style="info" %}
+Take ownership, stand up! This project and its outcome is yours 🔥
+{% endhint %}
+
+## 👔⚖️⛹🏽‍♀️ Work-Life-Balance
+
+Working can be a lot of fun, and the team dynamics are exhilarating. However, it _is_ important to spend some time away from your screen; to reflect, recharge and give your brain some time to deal with the information throw at you every day.
+
+![Give your colleagues space to take a break, and make sure you turn off your notifications! ](../.gitbook/assets/al.gif)
+
+### Take Regular Breaks
+
+{% hint style="info" %}
+Regular breaks are a _must_. Make an agreement with your team on how you are going to take breaks. 👯‍♂️
+{% endhint %}
+
+### You Do Not Have to Overwork
+
+You don't have to be online, constantly chatting with your team, 24/7. _**It's fine to disconnect**_, it's encouraged and healthy.
+
+![Look out for each other ♥️it's okay to stop, especially on weekends and evenings!](../.gitbook/assets/screenshot-2020-07-13-at-15.10.04.png)
+
+### Work Smoothly
+
+Don't give 200% now, you'll be at 0% in the delivery week. Work at your own pace, so your colleagues can still count on you in the last week 🧘🏽‍♀️
+
+## 🌊💦🚰💧🧊 Stay Hydrated
+
+![Drink Water 👌](../.gitbook/assets/water.gif)
+
+{% hint style="info" %}
+Anything to add? Reach out to Miet on Discord.
+{% endhint %}
+