From: Patrick Williams <patrick@stwcx.xyz>
To: "Hawrylewicz Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Virtual Media repository request
Date: Wed, 8 Dec 2021 10:56:19 -0600 [thread overview]
Message-ID: <YbDjsxZYYtnNPsCK@heinlein> (raw)
In-Reply-To: <DM4PR11MB52476717C6A134B92BD62061B96E9@DM4PR11MB5247.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On Tue, Dec 07, 2021 at 03:50:47PM +0000, Hawrylewicz Czarnowski, Przemyslaw wrote:
Hello Przemyslaw,
Thank you for wanting to work at getting this code mainlined. I know there has
been quite a bit of interest from various people outside Intel.
> I would like to request for new Virtual Media service repository (based on the design document located here: https://github.com/openbmc/docs/blob/master/designs/virtual-media.md).
I know you've got a pending commit to update some pieces of this design. Since
none of the code has been submitted since the design was originally written, do
we need anyone to re-read it and see if anything has changed in the rest of the
codebase that needs design updates?
> The service itself is a reworked Virtual Media which early stage is available here: https://github.com/Intel-BMC/provingground.
>
What did you have in mind for maintainer structure on this? I'd ideally like to
see someone outside of Intel be a co-maintainer with you since:
- This code was initially written as experimental Intel-only repository
without any community feedback and
- The current code hasn't been touched in 2 years and best practices have
likely changed.
- You're not currently a maintainer on any other repositories.
> And additional question: is there anything to do in order to enable CI for this repo?
Once the repository is set up, Andrew G can enable CI on it fairly quickly.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-08 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 15:50 Virtual Media repository request Hawrylewicz Czarnowski, Przemyslaw
2021-12-08 16:56 ` Patrick Williams [this message]
2021-12-09 8:56 ` Czarnowski, Przemyslaw
2021-12-09 10:41 ` i.kononenko
2021-12-13 16:10 ` Patrick Williams
2021-12-13 19:44 ` Czarnowski, Przemyslaw
2021-12-14 2:11 ` Jeremy Kerr
2021-12-15 19:26 ` Ed Tanous
2021-12-17 9:28 ` Czarnowski, Przemyslaw
2021-12-17 9:45 ` Jeremy Kerr
2021-12-20 12:54 ` Czarnowski, Przemyslaw
2021-12-23 1:01 ` Czarnowski, Przemyslaw
2022-12-19 14:01 ` Czarnowski, Przemyslaw
2022-12-19 17:43 ` Ed Tanous
2023-01-03 5:36 ` Jeremy Kerr
2021-12-11 21:13 ` Ed Tanous
2021-12-13 19:17 ` Czarnowski, Przemyslaw
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=YbDjsxZYYtnNPsCK@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
/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.