From: Paul Wise <pabs3@bonedaddy.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Krzysztof Opasiak <k.opasiak@samsung.com>,
Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>,
Matt Porter <mporter@kernel.crashing.org>,
linux-usb@vger.kernel.org
Subject: Re: proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation?
Date: Wed, 14 Jul 2021 10:11:51 +0800 [thread overview]
Message-ID: <acfda565cf77cf79bdf951ddccb64420c2fdf288.camel@bonedaddy.net> (raw)
In-Reply-To: <YO00rA8sTT2mrdOv@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Tue, 2021-07-13 at 08:37 +0200, Greg KH wrote:
> Ah, hopefully people actually realize this :)
GitHub makes it fairly obvious even in text based browsers, for eg:
https://github.com/codilime/veles
> I find it suprising that if these projects are really being used, and
> there are problems, that none of the companies using them are
> contributing back to the projects for these issues.
It appears Samsung is using them in Tizen and Collabora has some
interest in them, presumably for some of their customers and the commit
logs and bug reports show a few other companies. I expect that the
projects are mostly considered "good enough" infrastructure that they
don't have enough motivation to assign much work time to them.
> The technical things should be easy for those companies to help with,
> the "advocacy" is a different thing, and that you should be able to do
> today by submitting talks to conferences to get the word out. Almost
> all conferences have travel stipends for speakers that are not sponsored
> by companies to travel.
Of course, all of the work needed can be done by anyone volunteering in
their spare time or work time when no higher priority work needs doing,
but allocating funding towards these projects would make it easier for
this work to be prioritised.
> good luck!
Seems like luck will be needed indeed.
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-07-14 2:12 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
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 [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=acfda565cf77cf79bdf951ddccb64420c2fdf288.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=andrzej.p@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.lewandowsk@samsung.com \
--cc=k.opasiak@samsung.com \
--cc=linux-usb@vger.kernel.org \
--cc=mporter@kernel.crashing.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).