Update osd description (#164)

* update osd

* minor update

* minor fix

* minor update

Author: tsolakoua

talent/open_source_days.md

@@ -2,7 +2,7 @@
 # Open Source Days
 
 Developers at source{d} dedicate 10% of their development time to Open Source projects of their choice.
-This is accomplished with Open Source Days (OSD), which happen on the first Monday of each sprint.
+This is accomplished with Open Source Days (OSD) every two weeks, on Mondays.
 
 ## The Rules
 
@@ -17,16 +17,8 @@ on OSD should be driven exclusively by your interests. While you can work on a s
 [go-git](https://github.com/src-d/go-git), we also encourage you to work on something not related
 to your daily job.
 
-### Demo
-
-Whatever you do, you must demo it to your colleages. We prefer actual demos, not slides or code
-walkthroughs.
-
 ## How To
 
-1. **Prepare.** Get to the office before 10:30 a.m. and prepare your work for the day.
-2. **Share your plan.** At 10:30 we do the OSD planning meeting. You should briefly explain what you are going to do and what do you expect to accomplish by the end of the day. This should be just 1 or 2 minutes per person. Explanations about the project you're going to contribute are done in the `#osd` slack channel.
-3. **Do it.** Execute your plan for the day and push it!
-4. **Demo.** At a time agreed by the team, usually at 17:30, the demo starts. Everyone presents their work to others in 5-15 minutes.
-
-
+1. **Share your plan.** You should briefly explain what you are going to do and what do you expect to accomplish by the end of the day. Explanations about the project you're going to contribute are done in the `#osd` slack channel, in the beginning of the day.
+2. **Do it.** Execute your plan for the day and push it!
+3. **Presentation.** At the end of the day, everyone presents their work in the `#osd` slack channel with the corresponding source code and description.