Skip to content

Project director update on Feb's board meeting #1538

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

Merged

Conversation

carols10cents
Copy link
Member

@carols10cents carols10cents commented Mar 27, 2025

@senekor
Copy link
Contributor

senekor commented Apr 3, 2025

Note that posts were moved to the content/ directory, sorry for the churn 🙂

@carols10cents carols10cents force-pushed the project-director-update-2025-03 branch from 02f767c to 445b6a2 Compare April 3, 2025 14:14
@carols10cents
Copy link
Member Author

Fixed! Could someone review this please? 🙏🏻

@senekor
Copy link
Contributor

senekor commented Apr 3, 2025

I don't review content, I'm just the janitor around here 😄

I think usually some team lead does the content review. If there is no obviously responsible person, maybe the team rust-lang/inside-rust-reviewers would be appropriate to ping for review?

@ehuss
Copy link
Contributor

ehuss commented Apr 3, 2025

@carols10cents can you update the date to today, and I'll merge it?
(It looks like you've locked out edits so I can't change it.)

We really should figure out a better process here so that it isn't always on Mark to do everything. Do your fellow board directors want to review these posts at all? Can we set up some system so one of them can approve?

@spastorino
Copy link
Member

spastorino commented Apr 3, 2025

As a PD, my take is that this shouldn't require any approval from us so it can land faster (maybe other PDs have a different opinion).
First because we trust what Carol writes that is basically a summary of our board meetings, also because she shares with us the PR on Zulip and gives us time in case we find something and last because it's on her name, is her idea and effort and its her summary with her perspective on what and how should be summarized.

@ehuss
Copy link
Contributor

ehuss commented Apr 3, 2025

As a PD, my take is that this shouldn't require any approval from us so it can land faster

My intent was to make it land faster. The idea is to somehow give ya'll permissions to merge. Then, when Carol posts this, she can just grab one of you to merge it right away. Otherwise, these PRs get posted, they aren't assigned to anyone, and we just have to hope that Mark sees it somehow and has the time to click a button. That's clearly not working well, so the idea is to spread the responsibility to those who are actually involved with the board and hopefully have the time to look.

@spastorino
Copy link
Member

spastorino commented Apr 3, 2025

@ehuss exactly and totally agreed. My point is, whoever see these PRs and has rights to merge, should just do a minimal review and merge.
If more people have rights to merge things, even better.

There's a separate discussion about who should have merge rights. I have a very relaxed opinion about this which is that probably every project member should be able to merge blog posts ;).

@carols10cents
Copy link
Member Author

@ehuss I've updated the date! Thank you!

@ehuss ehuss merged commit 476bc93 into rust-lang:master Apr 4, 2025
4 checks passed
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.

4 participants