From: Rebecca Cran <rebecca@bluestop.org>
To: edk2-devel@lists.01.org, "Knop, Ryszard" <ryszard.knop@intel.com>
Subject: Re: [edk2-announce][RFC] Collaboration Software: Microsoft Teams
Date: Wed, 09 Jan 2019 13:14:07 -0700 [thread overview]
Message-ID: <5096239.8gLySxXtyI@photon.int.bluestop.org> (raw)
In-Reply-To: <a3d83d3fb77713a2ca724a5fc3a434a329f0a862.camel@intel.com>
On Friday, 4 January 2019 03:09:02 MST Knop, Ryszard wrote:
> I think any solution like that should be publicly available for an
> unlimited number of users. As it stands now, mailing lists and IRC are
> open to all - if software like Microsoft Teams is to be used, it's
> pretty likely most communication would quickly become invitation-only
> to avoid paying $8 per user. This often happens with many projects
> moving from mailing lists/IRC to something like Slack and having
> essentially zero public or searchable communications. Perhaps someone
> admining the edk2-devel list could look up the amount of subscribers
> and chime in?
There _are_ open source alternatives to Slack and Microsoft Teams - for
example Mattermost (https://mattermost.com/), and Discord might also be an
option (despite it being aimed pretty strongly at gamers). There's also the
option of using IRC but having a Slack instance which uses the IRC bridge to
allow bidirectional communication (albeit a bit clumsily).
Personally, I'd recommend against using Microsoft Teams. I've talked to people
who've used it and it pales in comparison to Slack. I know teams who have
'gone rogue' and set up their own Slack to avoid using the official Microsoft
Teams instance.
--
Rebecca
prev parent reply other threads:[~2019-01-09 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 20:37 [edk2-announce][RFC] Collaboration Software: Microsoft Teams Jeremiah Cox
2019-01-04 10:09 ` Knop, Ryszard
2019-01-09 20:14 ` Rebecca Cran [this message]
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=5096239.8gLySxXtyI@photon.int.bluestop.org \
--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