From: "Zimmer, Vincent" <vincent.zimmer@intel.com>
To: Kevin D Davis <kevin.davis@insyde.com>,
stephano <stephano.cetola@linux.intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Fri, 16 Nov 2018 17:56:32 +0000 [thread overview]
Message-ID: <76DE84138CBE89489874B70B432D8F9BC7EBA888@ORSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <3FEC98D0C33031D6.0465ECFF-1E41-4227-B64B-45BCF39396EA@mail.outlook.com>
https://slack.com/
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Kevin D Davis
Sent: Friday, November 16, 2018 9:35 AM
To: stephano <stephano.cetola@linux.intel.com>; edk2-devel@lists.01.org
Subject: Re: [edk2] [edk2-announce][RFC] Collaboration Software
If we get to vote, I’d vote against Google Groups. Their interface is very geared toward their internal work flow and seems to change on a whim. Thanks,Kevin
On Fri, Nov 16, 2018 at 11:08 AM -0600, "stephano" <stephano.cetola@linux.intel.com> wrote:
We are looking to augment our current communication methods (mailing list / IRC) with a modern solution for group collaboration. The goal is to allow folks to communicate effectively without interrupting the current patch review system, as well as enabling any future systems with more robust options.
Specific features we are looking for include attachments (currently blocked by the list), robust logging, modern chat, and integration with tools like bug trackers and source repositories (APIs, or better yet, pre-rolled plugins).
Our current contenders are Google Groups and Groups.io. This RFC is in hopes of finding other options to evaluate.
Cheers,
Stephano
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-11-16 17:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 16:59 [edk2-announce][RFC] Collaboration Software stephano
2018-11-16 17:35 ` Kevin D Davis
2018-11-16 17:56 ` Zimmer, Vincent [this message]
2018-11-16 19:13 ` stephano
2018-11-16 19:55 ` Kinney, Michael D
2018-11-16 20:46 ` stephano
2018-11-16 22:14 ` Philippe Mathieu-Daudé
2018-11-17 0:34 ` stephano
2018-11-17 0:37 ` Rebecca Cran
2018-11-17 1:36 ` stephano
2018-11-19 10:46 ` Tomas Pilar (tpilar)
2018-11-17 2:42 ` Sean Brogan
2018-11-17 4:58 ` Rebecca Cran
2018-11-17 19:01 ` stephano
2018-11-17 21:22 ` Rudra ठाकुर
2018-11-17 22:03 ` Rebecca Cran
2018-11-16 20:52 ` Rebecca Cran
2018-11-16 21:42 ` stephano
2018-11-16 21:51 ` Rebecca Cran
2018-11-17 0:22 ` stephano
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=76DE84138CBE89489874B70B432D8F9BC7EBA888@ORSMSX105.amr.corp.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