linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 13 Jul 2021 13:40:27 +0800	[thread overview]
Message-ID: <6be6edd3a30888ef7181735a1bbdac579578fd99.camel@bonedaddy.net> (raw)
In-Reply-To: <YO0cL+4gzLSyTY7f@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

On Tue, 2021-07-13 at 06:53 +0200, Greg KH wrote:

> What do you mean "archive libusbg"?
> 

GitHub repositories can be made read-only to indicate that they are no
longer being developed, this is known as "archiving".

https://github.blog/2017-11-08-archiving-repositories/


> What type of funding and for what specific development?
> What is lacking in the current projects here that needs to be
> resolved? And who have you asked for funding from so far?


The work needed is varied; the bugs/patches backlog, possibly porting
to newer library APIs, cleaning up build complaints, cleaning up static
and dynamic analysis complaints, integration with system software,
integration with mobile user interfaces, integration into distros,
automated testing with dummy_hcd, testing on devices, improving
documentation, promoting the tools, encouraging gadget authors to use
the tools, engaging with the user community, potentially additional UDC
drivers if any are missing, ongoing maintenance and anything else that
comes up during the course of that work.

I've mentioned the need for investment in the Linux userspace USB
gadget projects offlist to yourself, the other folks in CC, Bootlin and
a few other folks around the Linux ARM/mobile space.

-- 
bye,
pabs

https://bonedaddy.net/pabs3/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-07-13  5:45 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 [this message]
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=6be6edd3a30888ef7181735a1bbdac579578fd99.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).