developer meeting experiment

[clux]

One of the few pieces of feedback that I personally think is sensible to take on-board from CNCF as suggestions, is having some form of less formal means of real-time communication.

We've never had this before, and we get by, but a lot of the more difficult issues on here can sometimes stagnate when:

1. collective maintainer bandwidth is limited (and we prefer solving the easy issue/qa of the week)
2. it can be hard to engage with issues that we don't feel like we have the full context of

And i think it's valid to be able to talk about issues and direction in a less formal and less daunting way than github issues, to get pointers on where to start and to maybe seek out an exploratory consensus without writing an RFC equivalent.

I also do think we have a lot of (potentially deteriorating) knowledge and assumptions on "what we'd like things to be like" that we don't always express because it's a lot of effort to write it all down and justify formally. Particularly since this is basically volunteer work.

Proposal

a meeting, fortnightly, with minutes, google doc for next session's agenda that we all can plop things into*. running it for a 3mo period as an experiment.

Intent: for dev related work and directional planning / exploration, not for issue Q/A ideally (there's enough channels for that and they benefit from searchability) - but some of that is also probably unavoidable.

basically; an optional maintainer-run thing for when time allows (if no-one can / or nothing in the agenda we cancel). I am happy to try to run during an initial experiment (with the caveat that it has to be during EU daytime for a while for me for a while).

would any one of you find that valuable, or would you consider joining this at times?

tagging @kube-rs/maintainers and @kube-rs/triagewrite to query interest
to be clear: none of you should feel compelled to do this. feel free to 👍 or 👎 without ceremony.

if you do find this valuable, please say so. will try to schedule based on our preferences or time constraints, but ideally we leave a resulting meeting open so that other people wanting to contribute / join in can.

[nightkr]

Didn't see this (sorry!) but it seems like a good idea to me.

[soenkeliebau]

I concur, sounds like a good thing to try!

[Dav1dde]

👍

[clux]

Have setup a google doc for meeting tracking it should link to a calendar event that you should be able to join in. Hope google stack is ok for this.

Have copied a template somewhere so far so there's access for people to add in stuff.

LMK access troubles / hard maintainer time conflicts (if you want to join). Plan on moving it a bit later come January anyway though.

EDIT: updated event into a new calendar that's public (hopefully works now)

[clux]

Supplying a calendar link seems to be a better way; so here is the kube-rs calendar.

[clux]

Based on requests have moved this to Thursdays same time.