content(blog/events): Dublin collab summit 2024

[AugustinMauroy]

Description

Writting a blog post to summarize the summit.

The aim is to enable people who are not involved in the project to find out what's going on. And to make this post familiar in the way it is written.

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Nov 22, 2024 3:23pm

[JakobJingleheimer]

Awesome! Thanks for this. I'll try to flesh out my section in the next day or so.

[RedYetiDev]

Commit cotent -> content

[RedYetiDev]

Love it :-)

[AugustinMauroy]

Commit cotent -> content

BTW, we use squash and merge for pr so just the title is important 😄

[AugustinMauroy]

Joyee's feedback on slack:

While I appreciate the detailed notes, it seems a bit too lengthy for a blog posts to go into every “A asked something, B answered something, C pointed out something”…I would usually expect it to be “We discussed something and agreed something/We brainstormed ideas about something/we discussed something with notable highlights ABC..” and leave the more detailed back and forth in the notes for curious readers to dig into. If someone had the floor for many minutes about a point then it is good to highlight what they talked about, but it seems in quite a few points in the draft, the person only had the floor for a couple of seconds. Then IMO it is fine to leave out the details and just describe the conclusions we reached.

and

Also the diversity section has more details than I remember how it was done, it seems extended by some personal understanding instead of what was actually discussed at the summit (and to be fair we didn’t really discuss much in that session, it was only 30min and we spent most of the time distributing/writing/collecting/reading post-its without really digging into them). Like I remember Robin and James merely quickly went through the keywords on the post its, they never went into details about what “chaotic” “scrappy” means, only mentioned those keywords and moved on, and we never discussed what/why/how about those keywords (I remember myself googling “scrappy” on the spot because I didn’t know what that word means as a non-native English speaker and nobody explained or discussed it at the session to give me any clue, either, but somehow it has a spot in the draft explaining what it means which is pretty strange). The blog post IMO should merely reflect what happened, without adding additional details that were never discussed.

[bmuenzenmeyer]

normalized the names throughout per discussion, some slight cleanup, and resolved a duplication between the codemod and tooling discussions - thanks for helping put this together

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 99	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 100	🟢 92	🔗

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	90.5% (591/653)	76.06% (178/234)	94.35% (117/124)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
132	0 💤	0 ❌	0 🔥	5.197s ⏱️

[bmuenzenmeyer]

@AugustinMauroy removed the personal note via 856f262 in the interest of getting this ready to merge. otherwise we would need to solicit for more opinions. I like the spirit but agree it's a good sentiment to communicate personally on a blog or on social media, perhaps while linking to this report.

[AugustinMauroy]

Lgtm ! I am fine with it like this thanks Brian for giving energy in this

[joyeecheung]

I see that these explanations that were only added in based on personal understanding after the summit was still published. Personally (as one of the only two women, and the only female collaborator in the room) I feel very sad that the report pretended that we had some in-depth discussions about diversity when we in fact, did not, in that mere 30 minutes :(

[AugustinMauroy]

😅
Feel free to open a pr which changes the message.
Maybe review this part with Robin?

[joyeecheung]

I am too tired to edit it and I think the issue about diversity is now self-explanatory in this PR if it the question about the truthfulness of it from the only female collaborator there was simply ignored, and we needed the only two women in the room to go extra length to make sure that it is reflected truthfully in the report instead of being painted over. So leaving it as-is gives me a pointer for the future as well.

[ovflowd]

Was this maybe merged too early? Again, it is not up to us (website team) to write content, so I would have waited till everyone in the room was happy with the content 😅

[bmuenzenmeyer]

Apologies.

I should have reached for more consensus. My thought process at the time was a PR open for almost 2 weeks with the temporal nature of the summit content only growing.

It's not defensible on those merits alone but honestly thought the collaborator input from non-website maintainers was fully resolved. I see now that was untrue and will work to be more careful in the future.

[ovflowd]

All good! Technically speaking all requirements were correct and I also didn't say anything earlier (was so busy) -- but this sort of content is non-trivial and must be put in a way that effectively represents the storylines of the events.

No harm was done, happens, we learn. Let's just next time triple check and give proper time to all people involved on talks to consent with our narrative.

That's why IMO these articles must be impartial and not from someone's PoV :)

[ovflowd]

(Also no rush to put this content out, it's not like people are eager to see this content, the only time requirement is the one we put on ourselves here lol)