Create a LLVM discord channel for "lifetime-safety"

[usx95]

This came up in a couple of discussions, and we wanted to create a Discord channel for lifetime-safety in the LLVM Discord.
This can be similar to the fbounds-safety channel in the General category.

It would be great if we could create this channel.

My Discord handle is usx95.

@tstellar : I see you as an admin of LLVM Discord so assigning it to you. Feel free point me in the right direction if I should follow some other process.

Thanks.

[llvmbot]

@llvm/issue-subscribers-clang-temporal-safety

Author: Utkarsh Saxena (usx95)

This came up in a couple of discussions, and we wanted to create a Discord channel for **lifetime-safety** in the LLVM Discord. This can be similar to the [fbounds-safety](https://discord.com/channels/636084430946959380/1349963091432968287) channel in the General category.

It would be great if we could create this channel.

My Discord handle is usx95.

@tstellar : I see you as an admin of LLVM Discord so assigning it to you. Feel free point me in the right direction if I should follow some other process.

Thanks.

[llvmbot]

@llvm/issue-subscribers-infrastructure

Author: Utkarsh Saxena (usx95)

This came up in a couple of discussions, and we wanted to create a Discord channel for **lifetime-safety** in the LLVM Discord. This can be similar to the [fbounds-safety](https://discord.com/channels/636084430946959380/1349963091432968287) channel in the General category.

It would be great if we could create this channel.

My Discord handle is usx95.

@tstellar : I see you as an admin of LLVM Discord so assigning it to you. Feel free point me in the right direction if I should follow some other process.

Thanks.

[AaronBallman]

FWIW, we already have a memory-safety-wg which is going to seem confusingly related to lifetime-safety as well as fbounds-safety. Maybe we should combine them? fbounds-safety hasn't had activity in a week and before that it was over two months. The last activity in memory-safety-wg was about a month ago.

(I bring this up because I worry about how difficult it is to stay informed due to there now being so many topic-specific channels to try to keep track of. Maybe we should cull the little-used channels at some point?)

[usx95]

I think all these groups serve different purposes. memory-safety-wg serves for discussing high-level memory safety topics and overall activities in this space. lifetime-safety is a breakout group spun from memory-safety-wg.

The lifetime-safety channel would be focussed on lower-level implementation discussions and overall progress/direction. This is not meant for announcements for other members and I would be using the discourse RFC and other posts for posting higher-level updates. Therefore it might be too much noise or not too useful discussions to track for non-contributors if we merge it in other channels.
cc: @ymand

[AaronBallman]

I think the purposes all overlap fairly significantly and none of the channels have so much traffic that they'd be stepping on each other's ability to communicate if they were combined. That said, I certainly don't insist. I just know I've heard complaints about how difficult it is to actually stay informed on what's happening and the proliferation of Discord channels in particular was mentioned.

[ymand]

I vote in favor of a dedicated channel. While I understand the concern on staying informed, I think that's largely orthogonal. While you're right that memory-safety-wg doesn't have that much traffic, at times when conversations overlapped it was quite confusing (to me) and made it easy to miss important replies/comments.

Perhaps the larger issue is worth an in-person discussion at the dev meeting? I think we can find some simple, lightweight solutions that more directly address this concern. For example, a better map of channels and their purposes, WG quarterly updates, etc.

[mxms0]

I feel like threads should be the correct solution here, but they're kind of unnavigable across multiple topics and also auto-close after 3 days of inactivity :/

Happy with a dedicated channel, and also ok with reconsidering if we don't have enough activity to motivate it existing standalone :)