A
...
concise bi-weekly community report, inspired by the Scrum of Scrums.
The layout is supposed to be dynamically adapted to the different topics, focus areas and successes we choose and create. The target audience are people who are interested in yunity, and who want to keep as up-to-date as possible, without immersing themselves into yunity completely.
| Panel | |||
|---|---|---|---|
| |||
Here you can find the work-in-progress file for the next issue:
|
...
|
Every
...
second and
...
fourth Sunday (in calendar);
- Until
...
- 19:00 -
...
| Info | ||
|---|---|---|
| ||
Cross-team communication has been a recurrent topic, being mentioned in some form or another in every project-wide retrospective/reflective to date (Retrospective - WuppDays #1, Retrospective - WuppDays #2, WuppDays #6 retrospective, Rotterdam reflective, Sprint #6 (WD7-S1) Retrospective). Cross-team communication was attempted at the beginning of the project by the Coco - this lasted for about two months but then died. The notes from the Coco meetings and suggested reasons that led to the abandonment of the Coco can be found here. The short and regular SoS format aims to provide a manageable and sustainable way to achieve the communication needed to help identify where help is needed and avoid work duplication. It could be motivating for current contributors and the rest of the world to see what is being achieved even before the webapp is online. It could help bring in new contributors by letting them know we need help (and specifically what type) and also by providing a current status for those corresponding with applicants to refer to. |
...
| title | meta |
|---|
...
- Everybody can add info to the template and discuss the content in #heartbeat on Slack.
- At 19:00 - The heartbeat gets published as a blog post on this wiki.
- At 20:00 - The wiki blog post gets published over the yunity account on facebook.