Eric Huss

Results 150 issues of Eric Huss

cc @rust-lang/leadership-council

[RFC #1728](https://rust-lang.github.io/rfcs/1728-north-star.html) started a roadmap process that was carried out from 2017-2021. * 2017: https://rust-lang.github.io/rfcs/1774-roadmap-2017.html * 2018: https://rust-lang.github.io/rfcs/2314-roadmap-2018.html * 2019: https://rust-lang.github.io/rfcs/2657-roadmap-2019.html * 2020: https://rust-lang.github.io/rfcs/2857-roadmap-2020.html * 2021: https://rust-lang.github.io/rfcs/3037-roadmap-2021.html Should we continue...

S-needs-council

The core team previously started a process to establish charters for all teams. However, it wasn't finished. I would like to see a central place (my preference is the Forge)...

S-active
A-project-structure

We should formally create a group to resolve the trademark policy.

A-legal
S-needs-council

[RFC 3392](https://rust-lang.github.io/rfcs/3392-leadership-council.html) was not explicit on the requirements around alternates and affiliation limits. It might help to clarify that either alternates definitely must not tip the affiliation limit, or if...

S-needs-rfc

Support for licensing was previously owned by the core team. I think the Council should consider what strategy they want to take for supporting licensing questions and considerations for the...

S-needs-decision
A-legal

There are some open questions about what the appropriate set of top-level teams should be for the project. Some things to consider: * Find permanent homes for launching pad teams....

S-active
A-project-structure

This is a bit nebulous, but the overall idea is to: * Determine the overall shape of the project. * Determine who or which teams are actually part of the...

S-active
P-high
A-project-structure

The RFC recommends: > Establish proper procedures, and potentially teams, for handling issues which may have legal implications on the Project or Project participants. I don't know what that might...

A-legal
S-needs-council