From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paul Wise <pabs3@bonedaddy.net>
Cc: Krzysztof Opasiak <k.opasiak@samsung.com>,
Matt Porter <mporter@linaro.org>,
Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>,
linux-usb@vger.kernel.org
Subject: Re: proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation?
Date: Wed, 20 Jan 2021 16:19:30 +0100 [thread overview]
Message-ID: <YAhKAiz2U9KQWQPE@kroah.com> (raw)
In-Reply-To: <c38162833d1c8fede734e41eb5ce23cf393d6555.camel@bonedaddy.net>
On Wed, Jan 20, 2021 at 04:06:59AM +0800, Paul Wise wrote:
> Hi Greg, all,
>
> Right now all the Linux userspace USB gadget projects (libusbg,
> libusbgx, gt, gadgetd, cmtp-responder etc) are spread out across
> different GitHub organisations and user accounts.
>
> https://github.com/libusbg/libusbg
> https://github.com/libusbgx/libusbgx
> https://github.com/kopasiak/gt
> https://github.com/gadgetd/gadgetd
> https://github.com/cmtp-responder/cmtp-responder
If you can get the "owners" of these repos to agree, than sure.
But we should work out the libusbg and libusbx issue, which is really
the "latest" one?
> I would like to move each of these projects to the linux-usb GitHub
> organisation and add some more folks to the list of admins so that
> these projects can be more collaboratively maintained. The linux-usb
> GitHub organisation is currently solely owned by Greg Kroah-Hartman.
>
> https://github.com/linux-usb
>
> I don't propose to move maintenance of these projects to kernel.org
> since the issue and pull request databases for them are on GitHub and
> would need to be preserved.
If you are moving the repos, why do you care about the issue and pull
request database anymore? Will they just not end up going away?
I'm fine with keeping these on github, kernel.org is a great solution
for kernel developers to use, but that's about it :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-20 15:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210119200737eucas1p12bfb53d11543ee2ccb1a4bc2138f6535@eucas1p1.samsung.com>
2021-01-19 20:06 ` proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation? Paul Wise
2021-01-19 20:15 ` Krzysztof Opasiak
2021-01-20 11:58 ` Andrzej Pietrasiewicz
2021-01-20 15:19 ` Greg Kroah-Hartman [this message]
2021-01-20 15:34 ` Michael Sweet
2021-01-20 15:39 ` Paul Wise
2021-01-25 15:02 ` Michael Grzeschik
2021-02-05 23:35 ` Paul Wise
2021-02-06 13:14 ` Greg Kroah-Hartman
2021-02-06 23:28 ` Paul Wise
2021-02-14 2:17 ` Paul Wise
2021-02-15 9:53 ` Andrzej Pietrasiewicz
2021-02-15 10:07 ` Greg Kroah-Hartman
2021-02-15 10:31 ` Krzysztof Opasiak
2021-02-25 13:24 ` Paul Wise
2021-02-26 19:24 ` Mike Sweet
2021-02-27 1:08 ` Paul Wise
2021-02-27 1:54 ` Michael Sweet
2021-07-13 3:43 ` Paul Wise
2021-07-13 4:53 ` Greg KH
2021-07-13 5:40 ` Paul Wise
2021-07-13 6:37 ` Greg KH
2021-07-14 2:11 ` Paul Wise
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=YAhKAiz2U9KQWQPE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrzej.p@collabora.com \
--cc=k.lewandowsk@samsung.com \
--cc=k.opasiak@samsung.com \
--cc=linux-usb@vger.kernel.org \
--cc=mporter@linaro.org \
--cc=pabs3@bonedaddy.net \
/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).