From: Patrick Williams <patrick@stwcx.xyz>
To: John Wedig <johnwedig@google.com>
Cc: John Broadbent <jebr@google.com>,
bradleyb@fuzziesquirrel.com, openbmc@lists.ozlabs.org
Subject: Re: eStoraged repo
Date: Wed, 27 Oct 2021 08:59:18 -0500 [thread overview]
Message-ID: <YXlbNoBeD/yE/bg/@heinlein> (raw)
In-Reply-To: <CACejXs+LALZsTbVazgLjOP-K2d89sgTT0jVLpTKiFECfZdcYjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Tue, Oct 26, 2021 at 12:49:26PM -0700, John Wedig wrote:
Hello John,
> Now that the eStoraged
> <https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/46573> design doc is
> reviewed and merged, can you create a new repo for this? Or what's the
> next step?
Yep, now that we have an agreed-to design I think it is reasonable to get a repo
made for it. Do you have someone in mind that could be the initial maintainer
of it? Since you're new to the project, I'd like to have someone shadow you
initially, with the intention that after the initial bulk of development is done
you'd take over as the primary maintainer.
You could start with someone at Google who has been maintainer on a few
repositories already or someone from the TOF (or it doesn't have to be someone
at Google if there is interest from someone else in the community).
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-27 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 19:49 eStoraged repo John Wedig
2021-10-27 13:59 ` Patrick Williams [this message]
2021-10-27 23:38 ` John Wedig
2021-10-28 12:02 ` Patrick Williams
2021-10-28 13:58 ` 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=YXlbNoBeD/yE/bg/@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=jebr@google.com \
--cc=johnwedig@google.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.