From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Rust VMM" <rust-vmm@lists.opendev.org>,
"QEMU Devel" <qemu-devel@nongnu.org>,
virtio-comment@lists.linux.dev,
"VirtIO Dev List" <virtio-dev@lists.linux.dev>,
"Bill Mills" <bill.mills@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Matias Vara Larsen" <mvaralar@redhat.com>,
"Sergio Lopez" <slp@redhat.com>
Subject: Re: Central repo for VirtIO conformance tests?
Date: Mon, 31 Mar 2025 08:20:08 -0400 [thread overview]
Message-ID: <20250331122008.GA190936@fedora> (raw)
In-Reply-To: <Z-qHKUveoHc85koj@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Mon, Mar 31, 2025 at 01:14:33PM +0100, Daniel P. Berrangé wrote:
> On Mon, Mar 31, 2025 at 07:52:33AM -0400, Stefan Hajnoczi wrote:
> > On Mon, Mar 31, 2025 at 6:39 AM Alex Bennée <alex.bennee@linaro.org> wrote:
> > > So what do people think? Where would be a good place for common test
> > > repository to live?
> >
> > Maintaining the tests alongside the VIRTIO spec seems like a good fit
> > to me. Here is information on how to create a GitHub repo under the
> > OASIS VIRTIO Technical Committee:
> > https://www.oasis-open.org/open-repositories/
> >
> > I don't see a reason to maintain the tests under QEMU or rust-vmm
> > unless they provide some unique project infrastructure that an
> > independent project would lack or need to reinvent.
>
> IMHO opening that very link above illustrates the reason why *NOT* to
> host this under OASIS. Any potential contributor is faced with a 4 page
> long blurb of all sorts of rules & legal requirements, including
>
> "Each TC Open Repository shall be subject to a Contributor
> License Agreement (“CLA”) by which all persons making repo
> contributions into it are bound."
>
> Hosting anywhere else would be better from the POV of removing barriers
> to potential contribution.
I didn't notice the CLA requirement. I agree, it's better to host it
elsewhere.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-31 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 10:38 Central repo for VirtIO conformance tests? Alex Bennée
2025-03-31 11:52 ` Stefan Hajnoczi
2025-03-31 12:14 ` Daniel P. Berrangé
2025-03-31 12:20 ` Stefan Hajnoczi [this message]
2025-03-31 11:58 ` Stefan Hajnoczi
2025-03-31 12:36 ` Alex Bennée
2025-05-19 7:43 ` Manos Pitsidianakis
2025-05-19 7:54 ` Michael S. Tsirkin
2025-05-19 8:03 ` Manos Pitsidianakis
2025-05-19 8:15 ` Michael S. Tsirkin
2025-05-19 8:18 ` Manos Pitsidianakis
2025-05-19 12:30 ` Michael S. Tsirkin
2025-05-29 21:34 ` Michael S. Tsirkin
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=20250331122008.GA190936@fedora \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bill.mills@linaro.org \
--cc=david@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rust-vmm@lists.opendev.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@gmail.com \
--cc=virtio-comment@lists.linux.dev \
--cc=virtio-dev@lists.linux.dev \
/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.