Re: RFC: CCC Linux Kernel SIG

[James Bottomley <jejb@linux.ibm.com>]

On Thu, 2023-11-09 at 15:05 -0600, Dan Middleton wrote:
> On 11/9/23 11:22 AM, Carlos Bilbao wrote:
> 
> > On 11/7/23 19:24, Dan Middleton wrote:
> > > <snip>
> > > In addition to video meetings, the community will use an existing
> > > Discord channel for ongoing
> > > communication. No mail list is required at this time.
> > 
> > May I ask what Discord channel you're referring to? I'm assuming
> > it's
> > open access.
> > 
> https://discord.com/channels/1123803528377413762/1124090655707234334
> 
> I believe it is open.
> All CCC community forums zoom, slack, mail list, code are open.
> However, this is a pre-existing channel... see below.
> 
> On 11/9/23 12:38 PM, James Bottomley wrote:
> > Just on a personal note: I've had no end of trouble with Discord,
> > primarily around the verification requirements for my email address
> > preventing me from getting an account from the single gatekeeper,
> > so it
> > would be last on my list of useful systems for open conversations.
> 
> The CCC typically uses slack.

For slack like but open chat, most communities are coalescing around
matrix (it's what Linux Plumbers will be using).  The kernel community
does still like IRC, though.


> This discord reference is meant to accommodate kernel contributors
> who are already communicating there.

OK, I'm not actually aware of any kernel conversations going on in
Discord (but then the kernel is a huge community, so I'm not aware of a
lot of things ...).
 
>  We don't want to break anything that's working.
> Instead looking to bridge these different parts of the confidential 
> computing community who aren't in communication right now.

As I said in my reply: I'd start on the existing Mailing lists. 
Designate someone at the CCC to watch and report and then relay any
feedback or concerns.  At least that starts to get you input without
having to have everyone in the CCC exposed to the kernel community.

James