From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
Cc: Paul Wise <pabs3@bonedaddy.net>,
Krzysztof Opasiak <k.opasiak@samsung.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: Mon, 15 Feb 2021 11:07:59 +0100 [thread overview]
Message-ID: <YCpH/2PbQtrmUYhJ@kroah.com> (raw)
In-Reply-To: <e80a776a-5d05-8936-82c9-21180cd87e22@collabora.com>
On Mon, Feb 15, 2021 at 10:53:16AM +0100, Andrzej Pietrasiewicz wrote:
> W dniu 14.02.2021 o 03:17, Paul Wise pisze:
> > On Sun, 2021-02-07 at 07:28 +0800, Paul Wise wrote:
> >
> > > All the standard benefits of the GitHub organisations feature and
> > > collaborative maintenance in general
> >
> > Since the linux-usb GitHub organisation isn't yet available for
> > collaborative maintenance of Linux userspace USB gadget projects on
> > GitHub, we will create a linux-usb-gadgets GitHub organisation and can
> > move gadget projects to the linux-usb org when it becomes available.
> >
>
> Any prospects of it "becoming available"?
I still fail to see what this is going to help with here. Are usb
userspace projects going to somehow get loads of more developers
somehow this way? What is preventing that from happening today that
dumping them all in a single project going to change?
Am I now somehow the arbitrator of what is, and is not, a valid project
to join? We already have competing libraries scattered around, lumping
them all in a single location isn't going to change that problem from
what I can tell.
So, what problem would this solve that the added maintenance burden by me
and others would be worth it?
thanks,
greg k-h
next prev parent reply other threads:[~2021-02-15 10:08 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
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 [this message]
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=YCpH/2PbQtrmUYhJ@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=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).