Niko Matsakis
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Compiler team reorg ## Summary We will structure the compiler team as a set of **members** as well as a set off **elected officers**. **Membership.** The compiler team "members" and "contributor" levels are merged and simply called members; being a member gives you the same benefits as a contributor today (r+ rights, review privileges, membership in the rust org, etc) as well as the right to serve as an officer and to vote in officer elections. **Officers.** We have a number of officers with specific roles. These officers are typically elected from the set of compiler team members, though the leads may agree to permit a non-member in exceptional cases. One person may fulfill multiple offices but this is discouraged. The roles include: * **Team leads** (2): Overall team leadership * The **technical leads** (4): These are the people who decide on FCP requests and who make other sorts of contentious technical decisions. * The team leads are also included on FCP requests. * The **prioritization working group lead** (2): Leads of the prioritization working group, which judges which issues are important and prepares the agenda * The **performance triage leads** (2): Responsible for preparing weekly performance triage comparisons. * The **secretaries** (2): They create the minutes from design and steering meetings * They could also do things like run/organize Zoom meetings, post records of any meetings to the Youtube account, potentially handling scheduling for teamwide meetings, etc. * Other ideas * managing the review queue? **Rotation and outgoing officers.** Note that each office has an "even number" of people occupying it. The idea is that each election we elect one new person to the office, and they will serve for two terms. During the second term, they are termed the "outgoing officer", and they have the responsibility of mentoring and training the new officer (as well as helping out). In the case of the technical leads, there are two outgoing officers. ## Motivation ### Goals - Avoid leader burnout: - from doing the same job for too long - from doing too many jobs - Normalize leadership transitions. - We want to have many people on the compiler team that could step into a leadership position if required. - We want a regular cadence of transitions with overlapping coleads who can provide mentoring to the new colead. - Help the team decision making scale as our team grows - Provide more oportunity for individuals to recieve recognition for the work they do on Rust, not just the "writing code" activities. - For example: technical design and steering, code reviews, prioritization, etc. ## Elections and terms We hold elections every year. The term of office is therefore two years in total, with the second year being in "outgoing" capacity. ### How we hold elections The slate of candidates is selected via nomination. There is a 1 week nomination period in which members of the team can nominate other members for a particular office. The nominee must agree to the nomination. The same person can be nominated for any number of offices. Elections are held by "approval voting". This means that each member may vote for any number of candidates within a given election. The candidate with the highest number of votes wins. Ties are resolved via random selection or by mutual agreement of the candidates. If the same person wins multiple offices, then they will typically resign from all but one, and the next highest vote count will be selected as winner. -- what happens if there is no next highest vote in more than one election? ### Special elections In cases where an office resigns or is removed from office, we hold a special election. The procedure is the same as above except that the election is held for only one office. The winner will serve out the remainder of the term for the officer that they replaced. ## Term limits Outgoing officers are strongly discouraged from running for the same office again, but it is not strictly forbidden. This policy does not apply if the outgoing officer was voted into the office in a special election owing to resignation or removal of the previous officeholder. ??? -- should we forbid it, at least in cases where there is another candidate? Requires the team leads to sign off on it? Forbid it completely for team leads, perhaps? ## Resignation and removal Officers may resign at any time, in which case a special election is held to select their replacement. That replacement will serve out the remainder of their term and may then run again as normal in the ordinary elections. If an officer is removed from the compiler team because of Code of Conduct violations or any other reason, they are also removed from their post as officer and a special election is held to select their replacement. If the officer leaves the compiler team in an amicable fashion, however, the team leads may opt to permit them to serve out their term. XXX do we need a policy for removing an officer that is not tied to code of conduct? Maybe. If we see that someone is not doing their duty, I think we would first encourage them to resign. The question is what they refuse to do so but still continue not to do their duty. ## Rough ideas - Perhaps we have designated term durations with the possibilty of doing multiple terms in a row. Colead terms would be offset from each other so that we don't have two new coleads both starting at the same time. - Example policy: - Term lengths are 1 year - One colead starts 1/1, the other starts 6/1. - You can serve up to 3 terms in a row, no restriction on total number of terms served. - Downsides: - Making hard rules can cause issues down the line (what if we no one available to serve other than a person who's already done so 2 or 3 times in a row?) - It seems better to create a culture that wants the overall goals achieved rather than enforcing via fiat. - We could also define a series of recomendations that still align with our goals but are not hard rules. - To do this well, I think we would need to flesh out the goals we want to achieve and publish them. - Recomendations would be one path to achieve the goal but many such paths probably exist. .

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully