All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Taylor <kurt.r.taylor@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Community support - where do want to be in a year?
Date: Wed, 5 Feb 2020 18:02:01 -0600	[thread overview]
Message-ID: <CAG5OiwhNq55Om4=NU8F7SSebDqMQpKhHuhAC-aFz=QKBLM6Wig@mail.gmail.com> (raw)

The new year is well underway, and I have started thinking about more
that could be done to enable a stronger, more open community, and to
have a better developer experience.

I'd like to get your feedback, but please, this is not meant to be a
complaint platform, reply with ideas and solutions, or at least an
open mind for how we can fix it. I want to hear ideas!

I am looking to organize a prioritized list so I (and others?) can
focus on making things happen. I am hopeful that my downstream
responsibilities will be reduced in the coming months and that we can
start making real community progress.

Incomplete list (for priming the idea pump):
1) Existing (donated?) services - Gerrit/Jenkins hosting, email
service - what about hosting? what about disaster recovery/backups?
How can we improve?
2) Automate openbmc.org wordpress content/updates, current events?
meetups? blog planet?
3) Metrics - what would the community like to see?
4) Early development plans disclosure (new features),
charter/policy/culture changes for upstream plans, improving speed to
commit, review commitments?
5) Third-party CI testing/review reporting, supported platforms,
release testing commitments

What are *your* ideas for improving the community?

Kurt Taylor (krtaylor)

             reply	other threads:[~2020-02-06  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  0:02 Kurt Taylor [this message]
2020-02-06  0:55 ` Community support - where do want to be in a year? Andrew Jeffery
2020-02-07 15:00   ` krtaylor
2020-02-07 16:30 ` Patrick Williams
2020-02-07 17:58   ` krtaylor
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='CAG5OiwhNq55Om4=NU8F7SSebDqMQpKhHuhAC-aFz=QKBLM6Wig@mail.gmail.com' \
    --to=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 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.