Merge branch 'rust-lang:master' into remove-members

Author: marcoieni

content/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools.md

@@ -0,0 +1,50 @@
++++
+path = "2025/08/19/demoting-x86-64-apple-darwin-to-tier-2-with-host-tools"
+title = "Demoting x86_64-apple-darwin to Tier 2 with host tools"
+authors = ["Jake Goulding"]
+
+[extra]
+team = "the Infrastructure team"
+team_url = "https://www.rust-lang.org/governance/teams/infra#team-infra"
++++
+
+In Rust 1.90.0, the target `x86_64-apple-darwin` will be demoted to Tier 2 with host tools.
+The standard library and the compiler will continue to be built and distributed,
+but automated tests of these components are no longer guaranteed to be run.
+
+## Background
+
+Rust has supported macOS for a long time,
+with some amount of support dating back to Rust 0.1 and likely before that.
+During that time period,
+Apple has changed CPU architectures from x86 to x86\_64 and now to Apple silicon,
+ultimately announcing the [end of support][timeline] for the x86\_64 architecture.
+
+Similarly,
+[GitHub has announced][gha] that they will no longer provide free macOS x86\_64 runners for public repositories.
+The Rust Project uses these runners to execute automated tests for the `x86_64-apple-darwin` target.
+Since the [target tier policy][policy] requires that Tier 1 platforms must run tests in CI,
+the `x86_64-apple-darwin` target must be demoted to Tier 2.
+
+## What changes?
+
+Starting with Rust 1.90.0, `x86_64-apple-darwin` will be Tier 2 with host tools.
+For users,
+nothing will change immediately;
+builds of both the standard library and the compiler will still be distributed by the Rust Project for use via `rustup` or alternative installation methods.
+
+Over time,
+this target will likely accumulate bugs faster due to reduced testing.
+
+## Future
+
+If the `x86_64-apple-darwin` target causes concrete problems,
+it may be demoted further.
+No plans for further demotion have been made yet.
+
+For more details on the motivation of the demotion, see [RFC 3841][].
+
+[policy]: https://doc.rust-lang.org/stable/rustc/target-tier-policy.html
+[timeline]: https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon#Timeline
+[gha]: https://github.blog/changelog/2025-07-11-upcoming-changes-to-macos-hosted-runners-macos-latest-migration-and-xcode-support-policy-updates/#macos-13-is-closing-down
+[RFC 3841]: https://rust-lang.github.io/rfcs/3841-demote-x86_64-apple-darwin.html

content/inside-rust/electing-new-project-directors-2025.md

@@ -0,0 +1,66 @@
++++
+path = "inside-rust/2025/08/20/electing-new-project-directors-2025"
+title = "Electing new Project Directors 2025"
+authors = ["Tomas Sedovic"]
+
+[extra]
+team = "the Leadership Council"
+team_url = "https://www.rust-lang.org/governance/teams/leadership-council#team-leadership-council"
++++
+
+
+Today we are launching the process to elect three Project Directors to the Rust Foundation Board of Directors. This is the second round of slots, following from [last year's election](https://blog.rust-lang.org/inside-rust/2024/09/06/electing-new-project-directors/).
+
+We will briefly explain the goals and procedures here, but this is mostly copy-pasted from [last year's post](https://blog.rust-lang.org/inside-rust/2024/09/06/electing-new-project-directors/) and the [official process documentation][pde-process].
+
+We ask all Project members to begin working with their Leadership Council representative to nominate potential Project Directors. See the [candidate gathering](#candidate-gathering) section for more details. Nominations are due by September 18, 2025.
+
+[pde-process]: https://github.com/rust-lang/leadership-council/blob/main/policies/project-directorship/election-process.md
+
+## What are Project Directors?
+
+The Rust Foundation Board of Directors has five seats reserved for Project Directors. These Project Directors serve as representatives of the Rust Project itself on the Board. Like all directors on the Foundation board, the Project Directors are elected by the entity they represent, which in the case of the Rust Project means they are elected by the Rust Leadership Council. Project Directors serve for a term of two years and will have staggered terms. This year we will appoint three directors and next year we will appoint two directors.
+
+See the [role description] document for more details about what is involved in being a Project Director.
+
+The current Project Directors are Carol Nichols, Ryan Levick, Santiago Pastorino, Scott McMurray, and Jakob Degen. This year, Santiago Pastorino, Scott McMurray, and Jakob Degen's seats are open for election.
+
+We want to make sure the Project Directors can effectively represent the Project as a whole, so we are soliciting input from everyone on the team. The elections process will go through two phases: 1) candidate gathering and 2) election. Read on for more detail about how these work.
+
+[role description]: https://github.com/rust-lang/leadership-council/blob/main/roles/rust-foundation-project-director.md
+
+## Candidate gathering
+
+The first phase is beginning right now. In this phase, we are inviting the members of all of the top level Rust teams and their subteams to nominate people who would make good Project Directors. The goal is to bubble these up to the Council through each of the top-level teams. You should be hearing from your Council representative soon with more details, but if not, feel free to reach out to that person directly.
+
+Each team is encouraged to suggest candidates. Since we are electing three directors, it would be ideal for teams to nominate at least two candidates. Nominees can be anyone in the Project and do not have to be a member of the team who nominates them.
+
+The candidate gathering process will be open until September 18, at which point each team's Council representative will share that team's nominations and reasoning with the whole Leadership Council. At this point, the Council will confirm with the nominees that they are willing to accept the nomination and fill the role of Project Director if selected. Then the Council will publish the set of candidates.
+
+This then starts a period where members of the Rust Project are invited to share feedback on the nominees with the Council. This feedback can include reasons why a nominee would make a good Project Director or concerns the Council should be aware of.
+
+The Council will announce the set of nominees by September 19 and the feedback period will last until October 2. Once this time has passed, we will move on to the election phase.
+
+## Election
+
+The Council will meet on October 3 to complete the election process. In this meeting we will discuss each candidate and once we have done this the facilitator will propose a set of three to be the new Project Directors. The facilitator puts this to a vote, and if the Council unanimously agrees with the proposed set of candidates then the process is complete. Otherwise, we will give another opportunity for council members to express their objections and we will continue with another proposal. This process repeats until we find a set of nominees to whom the Council can unanimously consent. The Council will then confirm these nominees through an official vote delivered to the Foundation.
+
+Once this is done, we will announce the new Project Directors. In addition, we will contact each of the nominees, including those who were not elected, to offer feedback. For those who accept feedback we will follow up to tell them a little bit more about what we saw as their strengths and opportunities for growth to help them serve better in similar roles in the future.
+
+## Timeline
+
+This process will continue through all of September and into October. Below are the key dates:
+
+* Candidate nominations due: September 18
+* Candidates published: September 19
+* Feedback period: September 19 - October 2
+* Election meeting: October 3
+* First board meeting starting the new term: October 14
+
+After the election meeting happens, the Rust Leadership Council will announce the results and the new Project Directors will assume their responsibilities.
+
+## Acknowledgments
+
+A number of people have been involved in designing and launching this election process and we wish to extend a heartfelt thanks to all of them!
+
+We'd especially like to thank Eric Holk, Ryan Levick, and TC for helping to improve our process.

content/inside-rust/[email protected]

@@ -0,0 +1,59 @@
++++
+path = "inside-rust/2025/08/15/leadership-council-repr-selection"
+title = "Leadership Council September 2025 Representative Selections"
+authors = ["Eric Huss"]
+
+[extra]
+team = "Leadership Council"
+team_url = "https://www.rust-lang.org/governance/teams/leadership-council"
++++
+
+The selection process for representatives on the [Leadership Council] is starting today.
+
+Every six months, half of the council terms end.
+The following teams are up to choose their representative for the next year:
+
+* [Infra]
+* [Lang]
+* [Libs]
+* [Mods]
+
+We are aiming to have the teams confirm their choices by September 19, 2025, and for any possible new members to be ready to join the council meetings starting September 26th.
+
+[Leadership Council]: https://www.rust-lang.org/governance/teams/leadership-council
+[Infra]: https://www.rust-lang.org/governance/teams/infra
+[Lang]: https://www.rust-lang.org/governance/teams/lang
+[Libs]: https://www.rust-lang.org/governance/teams/library
+[Mods]: https://www.rust-lang.org/governance/teams/moderation
+
+## Criteria for representatives
+
+Any member of the top-level team or a member of any of their subteams is eligible to be the representative.
+See [candidate criteria] for a description of what makes a good representative.
+
+[candidate criteria]: https://forge.rust-lang.org/governance/council.html#candidate-criteria
+
+There is a limit of at most two people affiliated with the same company or other legal entity being on the council [^affiliates].
+During the selection process, the council will consider the affiliation of candidates to decide if all choices will be compatible with that constraint.
+
+Representatives may serve multiple terms if the team decides to choose the same representative again.
+There is a soft limit of three terms.[^limit]
+It is recommended that teams rotate their representatives if possible to help avoid burnout and to spread the experience to a broader group of people.
+
+[^affiliates]: See [Limits on representatives from a single company/entity](https://forge.rust-lang.org/governance/council.html#limits-on-representatives-from-a-single-companyentity)
+
+[^limit]: See [Term limits](https://forge.rust-lang.org/governance/council.html#term-limits).
+
+## What do Representatives do?
+
+A representative provides a voice on the council to represent the interests of their teams and contribute to the long-term success of the Rust Project.
+A detailed description of the role may be found at the [Representative Role Description][role].
+
+[role]: https://github.com/rust-lang/leadership-council/blob/main/roles/council-representative.md
+
+## How should teams make their selection?
+
+The Leadership Council has put together a [Representative Selection Guide][guide] with recommendations for teams on how to go about choosing a representative.
+It is not a requirement that teams follow this guide; top-level teams may choose their own process.
+
+[guide]: https://github.com/rust-lang/leadership-council/blob/main/guides/representative-selection.md