From: Johnathan Mantey <johnathanx.mantey@intel.com>
To: krtaylor <kurt.r.taylor@gmail.com>,
Joseph Reynolds <jrey@linux.ibm.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Action: OpenBMC community messaging survey
Date: Fri, 25 Sep 2020 08:02:37 -0700 [thread overview]
Message-ID: <121a2102-ce28-893a-122c-f1453a4faf77@intel.com> (raw)
In-Reply-To: <fc2dfb5a-2053-19c3-a228-214986283003@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1065 bytes --]
Kurt,
I occasionally watch the IRC channel, and I am not a particularly
competent user.
Things I like about continuing to use IRC vs "service z"
1. IRC is not proprietary
2. IRC can be accessed using a client of your choosing
3. I like that it isn't logged. People may be more willing to allow
their personality to be on display.
4. IRC permits private side-bands for private conversations.
5. My experience with IRC is when I need assistance with infrastructure
issues the key person/people have been readily available. That
may/may not translate to "service z". In addition, do we really need
to permanently record "The CI server doesn't seem to be working." ?
6. IRC doesn't collect data about me.
7. Freenode could disappear tomorrow, and the community would not be
impacted for long.
--
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey@intel.com <mailto:johnathanx.mantey@intel.com>
[-- Attachment #1.1.2: Type: text/html, Size: 1975 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-25 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 19:48 Action: OpenBMC community messaging survey krtaylor
2020-09-24 2:58 ` Joseph Reynolds
2020-09-24 13:45 ` krtaylor
2020-09-24 15:54 ` Matthew Singer
2020-09-25 15:02 ` Johnathan Mantey [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-all 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=121a2102-ce28-893a-122c-f1453a4faf77@intel.com \
--to=johnathanx.mantey@intel.com \
--cc=jrey@linux.ibm.com \
--cc=kurt.r.taylor@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).