openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Singer <msinger@twitter.com>
To: krtaylor <kurt.r.taylor@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Joseph Reynolds <jrey@linux.ibm.com>
Subject: Re: Action: OpenBMC community messaging survey
Date: Thu, 24 Sep 2020 08:54:14 -0700	[thread overview]
Message-ID: <CAK6+DXTFbiD-xmD65qJAwib-qu1KPnHcEYe1k2j29zLHtyEm1w@mail.gmail.com> (raw)
In-Reply-To: <fc2dfb5a-2053-19c3-a228-214986283003@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]

Hi Kurt,

I had similar feelings about the survey, it didn't quite capture my
sentiment.  For me, it's more that I have set up IRC, but the OpenBMC
project is my only use case for IRC.  With so many communication channels,
IRC seems to fall to the background.  It's also hard to review past
activity in IRC, other tools like slack make it much easier to look at
threads retrospectively.

Thanks!


On Thu, Sep 24, 2020 at 6:45 AM krtaylor <kurt.r.taylor@gmail.com> wrote:

> On 9/23/20 9:58 PM, Joseph Reynolds wrote:
> > 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
>
> Thanks for the question - I could have been more clear about "regular
> use", and in the survey I do say that a bit better.
>
>  From your description, I would say that you are not a regular user of
> IRC. That is, you do your work without periodically discussing it in
> IRC, and are not actively participating in others work and design
> discussions. Absolutely no judgement here, this is a common situation
> that we can hopefully address and facilitate for other developers.
>
> Please feel free to take the survey, the feedback will be very much
> appreciated.
>
> Kurt Taylor (krtaylor)
>
> > 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)
> >
>
>

[-- Attachment #2: Type: text/html, Size: 3213 bytes --]

  reply	other threads:[~2020-09-24 16:01 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 [this message]
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=CAK6+DXTFbiD-xmD65qJAwib-qu1KPnHcEYe1k2j29zLHtyEm1w@mail.gmail.com \
    --to=msinger@twitter.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).