From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=192.55.52.43; helo=mga05.intel.com; envelope-from=stephano.cetola@linux.intel.com; receiver=edk2-devel@lists.01.org Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2D744211B5A23 for ; Mon, 14 Jan 2019 09:06:51 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jan 2019 09:06:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,478,1539673200"; d="scan'208";a="106506569" Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.251.10.19]) ([10.251.10.19]) by orsmga007.jf.intel.com with ESMTP; 14 Jan 2019 09:06:51 -0800 To: Rebecca Cran Cc: edk2-devel@lists.01.org References: <39677800.F463k0L8Pm@photon.int.bluestop.org> From: stephano Message-ID: Date: Mon, 14 Jan 2019 09:06:50 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <39677800.F463k0L8Pm@photon.int.bluestop.org> Subject: Re: [edk2-announce] Community Meeting Minutes X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 17:06:52 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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