All of lore.kernel.org
 help / color / mirror / Atom feed
From: krtaylor <kurt.r.taylor@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Community support - where do want to be in a year?
Date: Fri, 7 Feb 2020 11:58:16 -0600	[thread overview]
Message-ID: <c35f31e6-29fc-223b-08f1-7357457f813e@gmail.com> (raw)
In-Reply-To: <20200207163045.GA38734@patrickw3-mbp.dhcp.thefacebook.com>

On 2/7/20 10:30 AM, Patrick Williams wrote:
> On Wed, Feb 05, 2020 at 06:02:01PM -0600, Kurt Taylor wrote:
> 
> One interesting thing the #yocto channel has on IRC is a bot that
> posts links whenever someone opens a Stack Overflow with a 'yocto'
> tag.  I think we need a better mechanism to help with "drive by"
> questions.

Yes! maybe a variant of the meetbot functionality to monitor SO - may 
require channel logging, we'd need everyone to be comfortable with that.

Thanks, I'll add that to the list...

https://docs.google.com/document/d/1QCFRGCRofcR3K8clSLtJHw10-Cu9zkp0dvwXPWzQSCc/edit?usp=sharing

Kurt Taylor (krtaylor)


> This was pointedly said in the IRC and I certainly agree with it:
> 
>      ------: I realize ------ is asking a lot of basic questions that most
>      of us would normally answer by reading the code and experimenting.
>      They are highlighting major gaps in documentation though
> 
> We often have introductory questions on IRC and mailing list that go
> unanswered.  So, having a Stack Override bot wouldn't do anything if
> people don't take turns answering.
> 

  reply	other threads:[~2020-02-07 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  0:02 Community support - where do want to be in a year? Kurt Taylor
2020-02-06  0:55 ` Andrew Jeffery
2020-02-07 15:00   ` krtaylor
2020-02-07 16:30 ` Patrick Williams
2020-02-07 17:58   ` krtaylor [this message]
2020-02-07 20:41     ` Patrick Williams
2020-02-14 15:24 ` Johnathan Mantey
2020-02-14 16:29   ` Brad Bishop
2020-02-14 16:33   ` Brad Bishop
2020-02-14 16:55     ` 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=c35f31e6-29fc-223b-08f1-7357457f813e@gmail.com \
    --to=kurt.r.taylor@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.