openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: krtaylor <kurt.r.taylor@gmail.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Action: OpenBMC community messaging survey
Date: Wed, 23 Sep 2020 21:58:24 -0500	[thread overview]
Message-ID: <2fc9aa49-20d4-7fc3-86be-459ace8791da@linux.ibm.com> (raw)
In-Reply-To: <19c81092-8639-ce87-2515-c77ef7ae9001@gmail.com>

On 9/23/20 2:48 PM, krtaylor wrote:
> Hello everyone,
>
> I am doing a survey. If you DO NOT use IRC, would you start 
> communicating regularly with the community if we used a different 
> messaging platform? Maybe some other reason?
>
> I am not suggesting anything at the moment, just looking at ways to 
> remove any communication barriers and improve open designs and 
> development.
>
> If you DO NOT USE IRC regularly, please follow this link for a short 
> survey. It is completely anonymous and will remain open until 12:00pm 
> Central, Monday September 28th.

Hi Kurt.  Thanks for trying to improve communication within the OpenBMC 
community.

I was confused by the survey and did not submit my answers.  I use the 
IRC (per [1]) but sometimes go days without reading, and rarely 
respond.  I find IRC setup confusing, but easy enough to use.  And I 
would prefer to use slack features such as a full conversation history 
and threaded conversations.

- Joseph

[1]: https://github.com/openbmc/openbmc#contact

> https://www.surveymonkey.com/r/33BVDR6
>
> THANKS!
>
> Kurt Taylor (krtaylor)


  reply	other threads:[~2020-09-24  2:59 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 [this message]
2020-09-24 13:45   ` krtaylor
2020-09-24 15:54     ` Matthew Singer
2020-09-25 15:02     ` Johnathan Mantey

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=2fc9aa49-20d4-7fc3-86be-459ace8791da@linux.ibm.com \
    --to=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).