logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-07 16:43:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #30 from waku-org/weekly-updates

Browse Source
This commit is contained in:
fryorcraken.eth 2023-08-03 13:42:09 +10:00 committed by GitHub
commit 4bd375c805
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -18,7 +18,7 @@ The current reporting requirements are 2 folds:
#### 1. Weekly Reporting #### 1. Weekly Reporting
Weekly reporting by subteam of progress on milestones. See https://notes.status.im/waku-2023-report as the initiating document Weekly reporting by subteam of progress on milestones.
#### 2. Monthly Reporting #### 2. Monthly Reporting
@ -69,6 +69,21 @@ Note: GitHub `milestone` functionality is **not** used as part of this process.
**Weekly**: Report progress on each **active** _Milestone_ per subteam. **Weekly**: Report progress on each **active** _Milestone_ per subteam.
Every Friday, all team members must add a comment to the `Milestone` GH issue they worked on the past week or planned to work on next week.
The comment must have the following MarkDown format:
```md
**Weekly Update**
_achieved_: what was achieved last week; must remain on one line.
_next_: what will be worked on next week; must also remain on one line.
_blocker_: any blocking items.
```
Omit the lines which are not relevant.
On Monday, project lead or responsible person for report can run the [milestone-update](https://github.com/fryorcraken/milestone-update) script to generate a report and post it in the Logos Discord.
## Work Tracking per Year ## Work Tracking per Year
### 2023 ### 2023