From ec2ebe55ac3c1335fe5f549dcc7451ba9931a0be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ulises=20Gasc=C3=B3n?= Date: Sun, 2 Jun 2024 17:28:01 +0200 Subject: [PATCH] Update index.html --- index.html | 48 ------------------------------------------------ 1 file changed, 48 deletions(-) diff --git a/index.html b/index.html index 4063efe..12fa499 100644 --- a/index.html +++ b/index.html @@ -191,54 +191,6 @@

-
-
-

- Node.js Core update on 2024-05-27 04:17:32 -

-

Is there a possibility of this being updated for 2024, IMO it feels outdated

-

(This being the pinned discussion)

- -

- Mon, 27 May 2024 04:17:00 GMT -

- - read more - -
- - -
-
-

- Node.js Core update on 2024-05-27 20:09:26 -

-

Given that there has been nothing shared ~for almost a full year~ ever, maybe we can unpin this, close it, and remove it from the documentation?

- -

- Mon, 27 May 2024 20:09:00 GMT -

- - read more - -
- - -
-
-

- Node.js Core update on 2024-05-28 08:48:49 -

-

Delivering news from the Node.js project POV seems to be a perennial issue. Folks like Michael have made efforts to improve this, but it doesn't fit into anyone's workflow enough to really stick. It reminds me of when you have a question at work, CC several people in, and no-one replies because they assume someone else was going to. :) (No judgment, BTW. This stuff is hard! And maybe there's a lot going on that I am unaware of.)

-

This may not be the place for such a discussion, but does/could the Node.js project have one individual on the inside to handle outreach/press/public representation? I've seen the ambassador program, which might well be intended to cover this(?), but I worry that spreading the role across multiple people could have a similar diluting effect.

- -

- Tue, 28 May 2024 08:48:00 GMT -

- - read more - -