openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Kartashev <a.kartashev@yadro.com>
To: <openbmc@lists.ozlabs.org>
Subject: Re: Call for volunteers
Date: Wed, 13 Jan 2021 08:42:46 +0300	[thread overview]
Message-ID: <5d918861bb1549ff80894e0dc6d3ca4195c09568.camel@yadro.com> (raw)
In-Reply-To: <20210111220919.zwc727vbwc4itm7h@thinkpad.fuzziesquirrel.com>

Hi Brad,

Excellent initiative, I'm in.

On Mon, 2021-01-11 at 16:09 -0600, Brad Bishop wrote:
> Hello OpenBMC-ers!
> 
> Your TSC has been aware of the problem of fragmentation in our
> project for some
> time.  Fragmentation is a loose term - for the purposes of this note
> consider
> it to be any time contributor efforts in the community are duplicated
> without
> thought given to maintenance and/or compatibility.
> 
> To begin to address this issue the TSC is looking for volunteers to
> serve on a
> "repository review forum" to which the TSC will initially delegate
> its
> authority in the areas of:
> - new repository creation
> - placement of contributed new function into existing repositories
> 
> The TSC fully expects the scope of this forum to quickly grow into
> the role of
> a traditional TSC providing frequent, technical oversight to project
> contributors.  The current TSC will continue to serve the project in
> terms of
> governance, advocacy and industry exposure - and likely get a rename
> (OpenBMC
> Board? or OpenBMC Steering Committee?) in the process.
> 
> The new forum would meet periodically or at the demand of other forum
> members
> to:
> - raise the forums combined awareness of new function under
> development
>    (information exchange)
> - build a consensus within the forum on where the function should
> exist
> - inform the function contributor and the rest of the community of
> the decision
> 
> A successful forum would be a forum that can simultaneously encourage
> the
> contribution of new and innovative solutions to existing problems
> without
> introducing complexity to the project as a whole.
> 
> A successful forum member will have previously demonstrated a breadth
> of
> understanding of the upstream OpenBMC codebase through:
> - frequent participation in peer review, the mailing list, IRC, and
> Discord.
> - submission of high quality designs and code to upstream OpenBMC
>    (github.com/openbmc)
> - a history of working with and guiding less experienced OpenBMC
> developers
>    in a timely manner, enabling them to come up to speed quickly.
> 
> If you are interested in serving the project in this manner, please
> reply to
> submit yourself as a candidate.
> 
> -brad, on the behalf of the OpenBMC TSC
-- 
Best regards,
Andrei Kartashev



  parent reply	other threads:[~2021-01-13  5:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 22:09 Call for volunteers Brad Bishop
2021-01-12 16:55 ` Ed Tanous
2021-01-12 20:11   ` Gunnar Mills
2021-01-12 21:07 ` Patrick Williams
2021-01-12 22:47 ` Andrew Jeffery
2021-01-13  5:00 ` Thomaiyar, Richard Marian
2021-01-13  5:30 ` Deepak Kodihalli
2021-01-13  5:38 ` Lei Yu
2021-01-13  5:42 ` Andrei Kartashev [this message]
2021-01-13 15:28 ` krtaylor
2021-01-14 17:39 ` Vernon Mauery
2021-01-26 23:56 ` Benjamin Fair
2021-09-27 16:25 ` Brad Bishop

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=5d918861bb1549ff80894e0dc6d3ca4195c09568.camel@yadro.com \
    --to=a.kartashev@yadro.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).