Claudio Wunder

Your "anyways I hope we can find a way forward" feels a bit off, since what’s being proposed here comes across more as a directive than a discussion. For context,...

I don’t see the merit in revisiting agreements that were already reached. The current structure was agreed upon by both the CPC and the TSC, so I’m struggling to understand...

> This point actually came up during the original discussion in a few places: > > [Comment 1](https://github.com/nodejs/admin/issues/872#issuecomment-2160404205) > > [Comment 2](https://github.com/nodejs/admin/issues/872#issuecomment-2156428381) > > It was also noted that the...

I want to be clear that I’m not taking this personally. I’ve been sharing what I believe are valid arguments for why this concern feels misplaced. I’m also not trying...

I assume this can be closed? Since it is solved? Wdyt, Matteo?

> The Pride post would likely fall jointly under both Foundation and Project Announcements. Right now posts can only be under one category (just a technical FYI that we can...

> We split the social media presence on each platform into two distinct account handles, e.g. something like `@nodejs` for the marketing content and `@nodejs-dev` for the technical content. From...

> > Personally, I’d be okay with the Website team being formally chartered, but it does raise important considerations. For instance, the Web Infra team owns several pieces of key...

> Here are the default issue types:  I feel we should have some based on the core labels we have? Not sure Task and Enhancement make sense. Bug, Feautre,...

Let me bump that issue. Apologies it taking so long!!