From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: linux.intel.com, ip: 134.134.136.100, mailfrom: stephano.cetola@linux.intel.com) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by groups.io with SMTP; Mon, 20 May 2019 07:42:46 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 May 2019 07:42:45 -0700 X-ExtLoop1: 1 Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.254.92.102]) ([10.254.92.102]) by fmsmga005.fm.intel.com with ESMTP; 20 May 2019 07:42:45 -0700 Subject: Re: [edk2-announce] [RFC] EMEA Meeting Days / Times Change To: Laszlo Ersek Cc: edk2-devel-groups-io References: <981d1fef-6641-80e6-3903-a79e2930b99f@linux.intel.com> From: "Stephano Cetola" Message-ID: <0ae4ce84-18d3-b8f8-6ce2-321fd4e13558@linux.intel.com> Date: Mon, 20 May 2019 07:42:45 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit I actually feel like we may need more lists rather than continuing to keep devel as our main discussion forum. I appreciate your feedback and hadn't thought of that solution, however here are my thoughts: On 5/15/2019 2:29 AM, Laszlo Ersek wrote: > - keep the announce list locked down (very small number of posters allowed) I want to encourage people from the community to give announcements if they feel it is pertinent to everyone. We have a rather mature, experienced group of engineers who I think can handle that responsibility. If I see this privilege being abused I can restrict posting to "approved posts", but I hope that isn't necessary. (new user moderation will catch "bots" and the like) > - when making an announcement, always CC the devel list as well, > - when consensus is reached, send *one* update (as the original poster) > in response to the original email, again to both lists. > > As a result: > > - the announce list will only contain the announcements, and (if > necessary) a consensus update. This will offer a very clean and > low-traffic overview to people browsing the announce list, and to those > that are subscribed only to the announce list > > - the community can engage in normal discussion hitting "Reply All" at > all times. The discussion will occur on the devel list, and will be kept > out of the announce list. If you (the OP) partake in the discussion, > you'll have to take care to remove the announce list from the address > list of your emails, as the address list would not filter you out (and > you wouldn't want to clutter the announce list with in-flight discussion). > I don't disagree that this would provide a way to comment on announcements while keeping the announcement list very clean. However, I feel like our devel list has become quite "messy" as a result of having only 1 list for many years, and I'd like to remedy that. I feel like your suggestion will only make the "mess" worse. For those of us using a MUA to filter our list, devel works very well currently. However, if community members want to get better use out of Groups.io, we need to ensure our conversations are formatted well for a web interface. This would mean both refining our lists to a specific purpose as well as taking advantage of hashtags. We discussed hashtags in our last community meeting: https://www.tianocore.org/minutes/Community-2019-05.html Your suggestion would indeed keep the "announce" list clean, however I fear that it would complicate the web flow quite a bit. Hopefully that came across as constructive. It's early and the coffee is still setting in :). Cheers, Stephano