Renaming Zulip T-compiler WGs streams

[apiraino]

Proposal

As part of some changes in the T-compiler global structure, the formal grouping of people known as "Working Groups" will be phased out. The idea behind it (people getting together to work on a specific area of the compiler) still stands and people working on areas of the compiler can do so as always, as they prefer.

As part of this phasing out, we would like to rename Zulip streams removing the wg- suffix. The full list or renames as follows:

Old name	New name	Notes
#t-compiler/wg-debugging	#t-compiler/debuginfo
#t-compiler/wg-diagnostics	#t-compiler/diagnostics
#t-compiler/wg-llvm	#t-compiler/llvm
#t-compiler/wg-mir-opt	#t-compiler/mir-opts	"opts" instead of "opt"
#t-compiler/wg-parallel-rustc	#t-compiler/parallel-rustc
#t-compiler/wg-rustc-dev-guide	#t-compiler/rustc-dev-guide
#t-compiler/wg-incr-comp	#**z-archived-t-compiler/incr-comp
#t-compiler/wg-meta	#**z-archived-t-compiler/meta
#t-compiler/wg-nll	#**z-archived-t-compiler/nll
#t-compiler/wg-polymorphization	#**z-archived-t-compiler/polymorphization
#t-compiler/wg-profile-guided-optimization	#**z-archived-t-compiler/profile-guided-optimization
#t-compiler/wg-rfc-2229	#**z-archived-t-compiler/rfc-2229
#t-compiler/wg-self-profile	#**z-archived-t-compiler/self-profile
#t-compiler/wg-parselib	#**z-archived-t-compiler/parselib
#t-compiler/wg-pipelining	#**z-archived-t-compiler/pipelining

Mentors or Reviewers

I need the support of a Zulip member with proper permission: @davidtwco

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

[rustbot]

Important

This issue is not meant to be used for technical discussion. There is a Zulip stream for that.
Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Concerns or objections can formally be registered here by adding a comment.

@rfcbot concern reason-for-concern
<description of the concern>

Concerns can be lifted with:

@rfcbot resolve reason-for-concern

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

[davidtwco]

@rustbot second

[apiraino]

Closing as accepted (a bit earlier as the usual 10 days as this is a relatively small change and we don't expect new blocking concerns)

@rustbot label -final-comment-period +major-change-accepted