Re: [WG: WG] Proposal: Working groups working group

> Responsibilities I like the idea of reporting somehow regularly. I found Rust team works well in this area (meetings [1], updates [2]). A more complicated example is Rust's Async WG [3]. Mainly, the goal of a WG, status quo and what it wants to resolve/improve, then keep the progress updated. I

Re: [WG: WG] Proposal: Working groups working group

>> I just want to make these things more discoverable > please feel free to jump in and make an infra ticket to move/mirror that to > GitHub If discoverable is an object, I suggest we use GitHub, at least as a mirror and accept issues and discussions. It's also easier to share over social media.

Re: [WG: WG] Proposal: Working groups working group

> On Feb 7, 2024, at 11:22 AM, Rich Bowen wrote: > > * Where to we want to track WG status? I would propose that we create > GitHub.com/apache/community for stuff > like this, to mirror GitHub.com/kubernetes/community >

Re: [WG: WG] Proposal: Working groups working group

Hi Rich, I strongly agree with your proposal for forming working groups. As a newcomer to the Apache Community without the technical background, I have always hoped to have more opportunities to contribute to the ASF beyond participating in the community building of my own project, but often didn'

[WG: WG] Proposal: Working groups working group

Proposed: A Working Group to help define Working Groups No, I’m not suggesting a top-down governance of working groups. What I’m suggesting is a group to discuss what a working group looks like and what kind of tools and processes we want to put in place to make sure that each WG isn’t inventin