From: "Kevin Hilman" <khilman@baylibre.com>
To: Remi Duraffort <remi.duraffort@linaro.org>,
Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
Cc: Antonio Terceiro <antonio.terceiro@linaro.org>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Corentin Labbe <clabbe@baylibre.com>,
"kernelci-tsc@groups.io" <kernelci-tsc@groups.io>,
"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: Moving lava-docker out of the KernelCI GitHub organisation
Date: Sun, 04 Sep 2022 04:01:42 -0700 [thread overview]
Message-ID: <7hv8q3h089.fsf@baylibre.com> (raw)
In-Reply-To: <CANJfhHfPWEmTkvXW1fNeQ7H2p4teOYTU9Dt26D-S1ZdPogD6_Q@mail.gmail.com>
Remi Duraffort <remi.duraffort@linaro.org> writes:
[...]
> With Antonio we agreed that we can host the lava-docker project along with
> lava if that's what the maintainers want.
I think it makes sense to be under the LAVA as long as it's OK with
whoever maintains that.
> But keep in mind that we (Antonio and myself) don't have time to make any
> changes/maintenance on this project.
That's OK. BayLibre will continue to maintain it. If you don't want it
under the main lava org, we can put it under ours too.
> If lava-docker is moved into the lava namespace, maybe the project
> should be documented into the lava official documentation.
OK. lava-docker is already using the base images provided by your team
already, we just build on that to make configuing a full LAVA env easier.
> We are planning to migrate the lava project from a self-hosted gitlab
> instance to the gitlab.com instance soon. If lava-docker is moved into the
> lava namespace it would be better to wait for the migration to gitlab.com
> (to avoid two migrations).
That makes sense,
Kevin
prev parent reply other threads:[~2022-09-04 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 14:05 Moving lava-docker out of the KernelCI GitHub organisation Guillaume Tucker
2022-08-25 14:37 ` Alice Ferrazzi
2022-08-26 18:40 ` Antonio Terceiro
2022-08-29 6:18 ` Alice Ferrazzi
2022-09-01 14:56 ` Remi Duraffort
2022-09-02 4:33 ` Alice Ferrazzi
2022-09-02 12:07 ` Corentin Labbe
2022-09-04 11:01 ` Kevin Hilman [this message]
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=7hv8q3h089.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=antonio.terceiro@linaro.org \
--cc=clabbe@baylibre.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci-tsc@groups.io \
--cc=kernelci@groups.io \
--cc=remi.duraffort@linaro.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).