Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONTRIBUTING.md: change weekly cadence to bi-weekly #1456

Merged
merged 1 commit into from
May 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,20 +221,20 @@ We have several reporting and communication practices within the Hydra project.
Becoming one of the core contributors of the project includes participation in
core communication processes.

### Weekly update
### Bi-Weekly update

At the end of each week, we provide updates to
At the end of every two weeks, we provide updates to
[cardano-updates](https://IntersectMBO.github.io/cardano-updates/tags/hydra),
which also serve as a basis for our monthly reports.

To write such an update:

1. Use the contributors tactical meeting agenda to collect bullet points on
- **What did the team achieve this week**: past tense summary of done things
- **What did the team achieve this sprint**: past tense summary of done things
(good: "Implemented..", bad: "Started working on.."); use the backlog and
calendars to collect

- **What are the goals of next week**: a short look-out onto the backlog and/or
- **What are the goals of next sprint**: a short look-out onto the backlog and/or
roadmap; ask each contributor what they would like to get done next week; always start from scratch and don't carry over things from last week.
v0d1ch marked this conversation as resolved.
Show resolved Hide resolved

2. Enrich the content with useful links and write a high-level summary. This
Expand Down