-
Notifications
You must be signed in to change notification settings - Fork 303
Add post on opening up the Core Team agenda #657
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
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
39 changes: 39 additions & 0 deletions
39
posts/inside-rust/2020-07-24-opening-up-the-core-team-agenda.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
layout: post | ||
title: "Opening up the Core Team agenda" | ||
author: Pietro Albini | ||
team: the Core Team <https://www.rust-lang.org/governance/teams/core> | ||
--- | ||
|
||
The Core Team works on project-wide policy questions on all sorts of matters, | ||
as well as generally monitoring the overall health of the project. While some | ||
of the discussed topics are sensitive (related to personal issues, finances, or | ||
security) and can’t be shared outside the Core Team, a lot of them are not. | ||
|
||
Much of the activity of the Core Team happens during weekly “triage” calls, | ||
where we discuss and make decisions on the items brought to our attention. Last | ||
year, we started opening up those calls by recording the parts where | ||
non-sensitive topics are discussed and uploading the videos [on our YouTube | ||
channel][yt]. While the videos provide the full context and nuance of the | ||
discussion, they take a good amount of time to watch, and referring to parts of | ||
the discussion is not always practical. | ||
|
||
Continuing with the effort of opening up our meetings, we’re happy to announce | ||
that the public agenda of those calls is now recorded in [issues inside the | ||
rust-lang/core-team][issues] repository! Each discussed topic will have its own issue, | ||
and we will provide updates each week with a summary of what we discussed | ||
during the call. | ||
|
||
We hope this setup will allow people to easily follow what’s on the Core Team’s | ||
plate by subscribing to either all the activity in the repository or just to | ||
the issues you care about. We will still continue to publish recordings of the | ||
calls for the people who care to listen to the whole discussion. | ||
|
||
We’ve decided at this time to limit permissions to post on the issues to the | ||
Core Team only, and possibly invited collaborators as relevant to particular | ||
topics. If you have an item you’d like us to discuss or if you have thoughts on | ||
an existing topic, please email [[email protected]]. | ||
|
||
[yt]: https://www.youtube.com/playlist?list=PL85XCvVPmGQjmo8ivhTMipwQRFl4ZW2cZ | ||
[issues]: https://github.com/rust-lang/core-team/issues | ||
[[email protected]]: mailto:[email protected] |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Historically we have used
I like the addition of the link, but maybe for consistency's sake we should make the text the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steveklabnik note that this will show up as "Pietro Albini, on behalf of the [Core Team]", as any other Inside Rust post. Do we want to change that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I did not see that on Inside Rust! Seems fine :)