4 ms·

Who decides which issue gets mentioned in these announcements? Is there a vote among the Rust members?

burntsushi 4y ago
As a Rust team member, I have no earthly clue. Maybe it's the Core team? Or the blog author? Or the release team? Also no clue whatsoever as to the process for determining which cause to promote or even which causes are not allowed to be promoted (if any?). So now I'm curious... Let's look. The blog is on github, and this is the commit that added it: https://github.com/rust-lang/blog.rust-lang.org/pull/1043/commits/c2ff1c1fd83cb0daf3bc5b659c97e79b919778a6 https://github.com/rust-lang/blog.rust-lang.org/pull/1043/co... What is the "leadership chat"? See: https://blog.rust-lang.org/inside-rust/2022/10/06/governance-update.html https://blog.rust-lang.org/inside-rust/2022/10/06/governance...
- VancouverMan 4y ago
  Are there any publicly accessible transcripts or recordings of the discussions that this governance structure engages in? Can we see if any of the participants objected to the inclusion of this material, for example?
  - burntsushi 4y ago
    I believe the only publicly available output of this team has been whatever has been published to the Inside Rust blog. If you read the blog post I linked in my previous comment (their most recent one), it outlines their plans. For full disclosure, this leadership chat was created in the fallout of the mod team resigning (of which I was a member). And I think it's a good thing, because it's getting a bunch of people talking that weren't talking before. And, as the blog post outlined, they're working towards producing an RFC to revamp part of Rust governance. Which... I think is needed. It's just that... they are also making other decisions now. Whether that's beyond their mandate or not, I don't know. But it's certainly continuing the tradition of the Core Team, which started doing this a couple years ago. And whether they were within their mandate to do such things is also not clear to me.

As a Rust team member, I have no earthly clue. Maybe it's the Core team? Or the blog author? Or the release team? Also no clue whatsoever as to the process for determining which cause to promote or even which causes are not allowed to be promoted (if any?). So now I'm curious... Let's look. The blog is on github, and this is the commit that added it: https://github.com/rust-lang/blog.rust-lang.org/pull/1043/commits/c2ff1c1fd83cb0daf3bc5b659c97e79b919778a6 https://github.com/rust-lang/blog.rust-lang.org/pull/1043/co... What is the "leadership chat"? See: https://blog.rust-lang.org/inside-rust/2022/10/06/governance-update.html https://blog.rust-lang.org/inside-rust/2022/10/06/governance...

VancouverMan 4y ago
Are there any publicly accessible transcripts or recordings of the discussions that this governance structure engages in? Can we see if any of the participants objected to the inclusion of this material, for example?
- burntsushi 4y ago
  I believe the only publicly available output of this team has been whatever has been published to the Inside Rust blog. If you read the blog post I linked in my previous comment (their most recent one), it outlines their plans. For full disclosure, this leadership chat was created in the fallout of the mod team resigning (of which I was a member). And I think it's a good thing, because it's getting a bunch of people talking that weren't talking before. And, as the blog post outlined, they're working towards producing an RFC to revamp part of Rust governance. Which... I think is needed. It's just that... they are also making other decisions now. Whether that's beyond their mandate or not, I don't know. But it's certainly continuing the tradition of the Core Team, which started doing this a couple years ago. And whether they were within their mandate to do such things is also not clear to me.