Add automation for interacting with Tekton calendar via gitops

Open
#38 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
devops

Research direction

Start by reading the calendar reference in contact.md#calendar and the issue's description of the desired GitOps workflow. Determine how the expected Tekton calendar state would be represented in this repository and how changes would be reflected in Google Calendar. Done means contributors can update the committed calendar state and those updates synchronize reliably.

Written by the indexing model from the issue text.

Description

lifecycle/frozen

We have a shared Tekton calendar at https://github.com/tektoncd/community/blob/master/contact.md#calendar but at the moment only a couple of people can edit it, so when folks want to reschedule meetings (like @hrishin for the observability working group!), they have to find someone with access to the calendar.

What would be really great is if we could have the expected state of the Tekton calendar committed to this repo, and updates to it would be reflected in the Google calendar.

(And even better, it could be implemented with Tekton itself!)

p.s. this was actually @dlorenc 's idea

Dominant language
Python
Stars
406
Forks
242
Avg merge
23d 20h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tektoncd/community

All issues in tektoncd/community

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.