linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Middleton <dan.middleton@linux.intel.com>
To: Carlos Bilbao <carlos.bilbao@amd.com>, linux-coco@lists.linux.dev
Subject: Re: RFC: CCC Linux Kernel SIG
Date: Thu, 9 Nov 2023 15:05:53 -0600	[thread overview]
Message-ID: <0743a815-e567-4273-8e13-bf8372c7ee71@linux.intel.com> (raw)
In-Reply-To: <22966e1b-dd7f-4eb2-ac5d-5988cc6687b6@amd.com>

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.

This discord reference is meant to accommodate kernel contributors who are
already communicating there. 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.

Thanks for the feedback and questions so far!


Regards,

Dan Middleton



  reply	other threads:[~2023-11-09 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  1:24 RFC: CCC Linux Kernel SIG Dan Middleton
2023-11-09 17:22 ` Carlos Bilbao
2023-11-09 21:05   ` Dan Middleton [this message]
2023-11-09 21:17     ` Dionna Amalie Glaze
2023-11-09 21:22     ` James Bottomley
2023-11-09 18:38 ` James Bottomley
2023-11-09 22:27   ` Dan Middleton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0743a815-e567-4273-8e13-bf8372c7ee71@linux.intel.com \
    --to=dan.middleton@linux.intel.com \
    --cc=carlos.bilbao@amd.com \
    --cc=linux-coco@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).