Skip to content

docs(policy): Clarify that Expatriation applies to all categories #840

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
merged 1 commit into from
May 9, 2025

Conversation

epage
Copy link
Contributor

@epage epage commented Apr 25, 2025

The current wording makes it sound like Expatriation only applies to Intentional Artifacts but the Council recently clarified that it also applies to Experiments.

From zulip

Just to follow up here, the council discussed this today. Our
interpretation was that expatriation requires an rfc and council
approval regardless of its experimental or intentional status (and per
the policy, is generally discouraged). It may be possible to achieve
something similar by just forking the project and picking a new name,
but it sounds like you don't want to go down that route. Working on it
externally sounds like another alternative.

Rendered

The current wording makes it sound like Expatriation only applies to
Intentional Artifacts but the Council recently clarified that it also
applies to Experiments.

From [zulip](https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Crate.20Ownership.20Policy.20Clarification/near/513732109)

> Just to follow up here, the council discussed this today. Our
> interpretation was that expatriation requires an rfc and council
> approval regardless of its experimental or intentional status (and per
> the policy, is generally discouraged). It may be possible to achieve
> something similar by just forking the project and picking a new name,
> but it sounds like you don't want to go down that route. Working on it
> externally sounds like another alternative.
@rustbot
Copy link
Collaborator

rustbot commented Apr 25, 2025

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 25, 2025
Copy link
Contributor

@ehuss ehuss left a comment

Choose a reason for hiding this comment

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

I'm going to just go ahead and approve on behalf of the council based on the discussion in meeting-2025-04-25 that we believe this is just a clarification. cc @rust-lang/leadership-council

@ehuss ehuss merged commit 887206d into rust-lang:master May 9, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants