From: Patrick Williams <patrick@stwcx.xyz>
To: "Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@linux.intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Virtual Media repository request
Date: Mon, 13 Dec 2021 10:10:08 -0600 [thread overview]
Message-ID: <YbdwYODNRJPuRady@heinlein> (raw)
In-Reply-To: <475ba120-3734-8bf1-868f-83f48f10ccac@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
On Thu, Dec 09, 2021 at 09:56:55AM +0100, Czarnowski, Przemyslaw wrote:
> On 08.12.2021 17:56, Patrick Williams wrote:
> > On Tue, Dec 07, 2021 at 03:50:47PM +0000, Hawrylewicz Czarnowski, Przemyslaw wrote:
> > 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.
>
> The code base exposed in provingground was under the development at that
> moment and actually shouldn't be submitted. The code is updated now
> (still needs some polishing I suppose) but I am ready to push updated
> sources and ask the community to review it.
>
> Right now I am the main person for VM in Intel, but actually I was
> thinking about some co-maintainership in case there are other parties
> willing to have contribution in the code. This could be worked out
> during review process.
This response feels like a bit of a chicken-and-egg. Who is going to review and
approve the commits to the repository that assign a maintainer to the
repository?
Maybe Ed's proposal of using an existing repository solves that. We would need
to make sure the current maintainer is accepting of whatever design direction
you've decided to go though.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-13 16:10 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
2021-12-09 8:56 ` Czarnowski, Przemyslaw
2021-12-09 10:41 ` i.kononenko
2021-12-13 16:10 ` Patrick Williams [this message]
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=YbdwYODNRJPuRady@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=przemyslaw.hawrylewicz.czarnowski@linux.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.