Moritz Wiesinger

My 2 cents since I can't join the community meeting today: The cool thing about our blog is that it's handled by a [plugin](https://squidfunk.github.io/mkdocs-material/plugins/blog/) and we don't need to do...

as discussed in the community meeting on april 17, @YashPimple will do some research on how we can add some automation to that page so that maintenance effort will be...

An option would be to take kubernetes prow and somehow put it into a composite github action https://github.com/kubernetes/test-infra/tree/master/prow There's also such a project out there already: https://github.com/jpmcb/prow-github-actions/tree/main

this ticket is still work-in-progress and not ready for development yet

Awesome that you want to apply! We're open for anybody to apply but keep in mind that you will not be the only one ;)

> 1. **Configuration**: Should the bot store the configuration inside workflow.yaml or something else? > We can pass the configs like `max_issue_per_contributor` and `max_pr_per_contributor` inside the workflow to interactively change...

`draft` is put on an issue manually when it's not ready for any other pairs of eyes yet. When an issue is done being described, the `ready-for-refinement` label is put...

We will refine the issue definition further and then get back to you with some more and better answers, hope that's ok :)

We refined the description of the issue again, please check if it makes sense. I hope that this will clear up some things.

As a result of the New Contributor Meeting on March 11th, I added some more information that was asked there. Specifically, information about the GitHub token needed for authorization and...