From: "Stephano Cetola" <stephano.cetola@linux.intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-announce] [RFC] EMEA Meeting Days / Times Change
Date: Mon, 20 May 2019 07:42:45 -0700 [thread overview]
Message-ID: <0ae4ce84-18d3-b8f8-6ce2-321fd4e13558@linux.intel.com> (raw)
In-Reply-To: <e77a3fa9-8382-0132-f523-aac130901ecb@redhat.com>
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
next prev parent reply other threads:[~2019-05-20 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <981d1fef-6641-80e6-3903-a79e2930b99f@linux.intel.com>
[not found] ` <ee2e46a5-c116-1f5f-692d-74344c3750d7@linux.intel.com>
2019-05-15 9:29 ` [edk2-announce] [RFC] EMEA Meeting Days / Times Change Laszlo Ersek
2019-05-17 9:40 ` [edk2-devel] " Ni, Ray
2019-05-20 14:42 ` Stephano Cetola [this message]
2019-05-20 15:03 ` Laszlo Ersek
2019-05-20 15:26 ` Stephano Cetola
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=0ae4ce84-18d3-b8f8-6ce2-321fd4e13558@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