public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: stephano <stephano.cetola@linux.intel.com>
To: Rebecca Cran <rebecca@bluestop.org>
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2-announce] Community Meeting Minutes
Date: Mon, 14 Jan 2019 09:06:50 -0800	[thread overview]
Message-ID: <cdab59a0-5883-6bbf-6f5c-13f46a7b1171@linux.intel.com> (raw)
In-Reply-To: <39677800.F463k0L8Pm@photon.int.bluestop.org>

On 1/12/2019 7:59 PM, Rebecca Cran wrote:

> I wonder if we might want to have a separate mailing list for reviews?
> 
> I find it a bit overwhelming having both patches and more general discussions
> on the same list, since I only check it every few days.
> 

My original thought was to add "edk2-announce" as a separate mailing 
list and keep the number of lists at 2 until we determine that more 
granularity is needed. While we decide on a new platform it was agreed 
(at the steward's meeting) that simply appending "edk2-announce" would 
suffice for now.

I have been trying out Groups.io and so far things look very promising:

https://edk2.groups.io/g/main

I added 2 subgroups: announce and devel. This allows us to keep 
community wide announcements (like this thread) separate from patch 
discussions. If we think that more granularity is needed (e.g. 
"architecture" for design discussions) we can discuss those possibilities.

Cheers,
Stephano


  parent reply	other threads:[~2019-01-14 17:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 19:26 [edk2-announce] Community Meeting Minutes stephano
2019-01-13  3:59 ` Rebecca Cran
2019-01-14  9:28   ` Laszlo Ersek
2019-01-14 17:06   ` stephano [this message]
2019-02-07 17:52 ` Jeremiah Cox
2019-02-07 18:30   ` stephano
2019-02-08  6:41     ` Rebecca Cran
2019-02-08  9:01       ` Laszlo Ersek
2019-02-08 17:33         ` Rebecca Cran
2019-02-08 17:52           ` Andrew Fish
2019-02-22 11:52             ` Rebecca Cran
2019-02-08 20:33           ` Laszlo Ersek
2019-02-08 13:58   ` Ard Biesheuvel
2019-02-14 19:07     ` Jeremiah Cox
2019-02-14 20:27       ` Rebecca Cran
2019-02-14 22:13         ` Kinney, Michael D
2019-02-15  2:56           ` Rebecca Cran
2019-02-15 14:30             ` Laszlo Ersek
2019-02-15 17:55             ` stephano
2019-02-15  8:43       ` Ard Biesheuvel
2019-02-15 14:23         ` Laszlo Ersek
2019-02-15 19:54           ` Felix Polyudov
2019-02-15 22:53             ` Laszlo Ersek
  -- strict thread matches above, loose matches on Subject: below --
2019-02-20  6:23 stephano
2019-02-20  6:45 ` stephano
2019-02-20  7:49 ` Rebecca Cran

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-list 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=cdab59a0-5883-6bbf-6f5c-13f46a7b1171@linux.intel.com \
    --to=devel@edk2.groups.io \
    /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