knative / knative/community

Improve the visibility of which TOC meeting will include a WG update for which WG

Open
#1,062 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
292
Forks
254
Avg merge
18h 11m
Merged PRs (30d)
1

Description

New contributors to Knative as well as users who would like to keep a close pulse on areas of Knative they are interested in don't have a clear way to know that we have regularly scheduled update meetings.

Currently, the schedule with the upcoming meetings for each WG update is [listed in a file ](https://github.com/knative/community/blob/main/mechanics/TOC-REVIEW.schedule)in the `community` repo. This is quite a hard to find place for those of us who even know this schedule exists.

In addition, this scheduled is added to this file manually. Supposedly there is a script (I'm [trying to find it](https://knative.slack.com/archives/CU9DGL4FM/p1652378429892979)).

It would be great if this workflow could be improved by using our [existing infra](https://github.com/knative-sandbox/knobots#adding-new-automation) to:
- automatically generate this output, on a periodic schedule
- propagate this output over multiple channels for greater visibility. Please see the proposed [list of distribution channels](https://github.com/knative/community/issues/1061).

Note: there is an [awk command](https://github.com/knative/community/blob/main/mechanics/TOC-REVIEW.schedule) that generates a list with dates for each event, but it is currently out of sync with the output on the page itself, likely because the recent change in daylight savings time.

Contributor guide

Open the contributing guide

Research direction

Start with mechanics/TOC-REVIEW.schedule and compare its awk-generated dates with the schedule output described in the issue. Read the knobots automation guidance and issue 1061 for the proposed distribution channels. Done means the schedule is generated periodically and made visible through the agreed channels without daylight-saving discrepancies.

Written by the indexing model from the issue text.

Assessment

Tech stack
awk
Domain
documentation, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.