Skip to content

feat(blog): pride #7888

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat(blog): pride #7888

wants to merge 2 commits into from

Conversation

vcarl
Copy link

@vcarl vcarl commented Jun 23, 2025

Description

Add a blog post for Pride 2025 ✨

Validation

Yes, please

Related Issues

n/a

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@Copilot Copilot AI review requested due to automatic review settings June 23, 2025 19:09
@vcarl vcarl requested a review from a team as a code owner June 23, 2025 19:09
Copy link

vercel bot commented Jun 23, 2025

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

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jun 23, 2025 7:13pm

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new blog post for Pride 2025, presenting a personal narrative on open-sourced identity and how evolving labels reflect personal and professional growth.

  • Introduces a new Markdown file for the 2025 Pride post
  • Provides thoughtful content linking change in coding practices to personal identity

@avivkeller
Copy link
Member

@nodejs/tsc @nodejs/marketing

Co-authored-by: Copilot <[email protected]>
Signed-off-by: Carl Vitullo <[email protected]>
@avivkeller
Copy link
Member

As a reminder to organization members, adding a pride blog post(s) was voted for in the leading candidate during the organization-wide vote we recently held.

@avivkeller avivkeller changed the title Create 2025-pride.md feat(blog): pride Jun 23, 2025
Copy link

codecov bot commented Jun 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.47%. Comparing base (65026c0) to head (5ef05c4).
Report is 3 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7888      +/-   ##
==========================================
- Coverage   75.49%   75.47%   -0.02%     
==========================================
  Files         101      101              
  Lines        8311     8311              
  Branches      218      218              
==========================================
- Hits         6274     6273       -1     
- Misses       2035     2036       +1     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@avivkeller avivkeller requested a review from a team June 23, 2025 19:20
@ljharb
Copy link
Member

ljharb commented Jun 23, 2025

This is beautifully written; thanks @vcarl!

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

Copy link
Member

@AugustinMauroy AugustinMauroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOVE it

@avivkeller
Copy link
Member

avivkeller commented Jun 23, 2025

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

"Publish a series of blog posts outlining contributions from voluntary LGBT+ contributors."

One could argue that contributing a blog post itself is a voluntary contribution. Additionally, this blog post features a quote from npm's co-founder, whose contributions to the ecosystem have been immense.

One could also point out that a blog post like this will inspire more LGBTQ contributors to contribute to the project, perhaps we can mention in the blog post that we are looking for LGBTQ contributors to write posts, and this will act as an introduction to the series?

>
> We need to be sure you know you're not alone.

Happy Pride.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we mention that we are looking for LGBTQ contributors to publish blog posts outlining their contributions. We can use this post as an introduction to the initiative.

On that note, if we change this blog post to include the additional information, it's canonically different than the one linked, so that can be removed

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, happy to add something but not sure precisely what the plan for a subsequent series is so I'm not sure what copy would be best to add. Won't fight too hard on canonical rel, but it would be neato to get a backlink of some variety for whatever SEO juice that contains 😇 but that's not the point of this, not highly important to me

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to what Aviv said. With the new addition, if this blog helps in encouraging LGBTQ contributors to participate in sharing about their Node.js contributions that they'd like to see outlined, that's good.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vcarl Perhaps something like

"As part of Pride Month, we’re launching a series of blog posts highlighting the voices and work of LGBTQ technologists. If you identify as part of the community and want to share your journey, your projects, or how your identity has shaped your perspective and contributions, we’d love to hear from you. Reach out and help us celebrate the diversity, creativity, and brilliance that make our field stronger."

(Obviously, you can workshop it however you'd like)


About the canonical link — I strongly recommend we remove it. This article includes additional content, making it meaningfully different from the original. If we set the canonical to your site, search engines may not index our version, which would reduce its visibility.

@MattIPv4
Copy link
Member

The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While Carl may not be a core contributor to the code powering Node.js, they absolutely have contributed to Node.js as a whole, most recently with the launch of our official Discord server, which is definitely making a difference to the project by giving the community a new space to engage.

@bmuenzenmeyer
Copy link
Collaborator

My understanding of the blog post idea (from @benjamingr if I recall correctly) was quite different. The idea of the blog post series to highlight the technical contributions done by LGBTQ+ people, showing how much they made a difference to the project.

While I like this specific blog post, I don’t think it fits our blog.

FWIW, this style of post was exactly the kind of post I was envisioning

@avivkeller
Copy link
Member

avivkeller commented Jun 25, 2025

Adding to the agenda for @nodejs/tsc visibility, feel free to remove after the meeting today.

@avivkeller
Copy link
Member

Missed the cutoff, sorry.

@avivkeller
Copy link
Member

@nodejs/TSC I would love if this was merged before July, as to make it merged during Pride Month, so please review when you get a chance.

@mcollina Given the additional comments, would you mind taking a second look 🙏?

Thank you all!

@avivkeller avivkeller requested a review from mcollina June 25, 2025 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants