Skip to content

Commit f01be71

Browse files
authored
Merge pull request #1456 from input-output-hk/biweekly
CONTRIBUTING.md: change weekly cadence to bi-weekly
2 parents cb5a8c8 + 573588a commit f01be71

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -221,20 +221,20 @@ We have several reporting and communication practices within the Hydra project.
221221
Becoming one of the core contributors of the project includes participation in
222222
core communication processes.
223223

224-
### Weekly update
224+
### Bi-Weekly update
225225

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

230230
To write such an update:
231231

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

237-
- **What are the goals of next week**: a short look-out onto the backlog and/or
237+
- **What are the goals of next sprint**: a short look-out onto the backlog and/or
238238
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.
239239

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

0 commit comments

Comments
 (0)