[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1466957501.2551.17.camel@decadent.org.uk>
Date: Sun, 26 Jun 2016 18:11:41 +0200
From: Ben Hutchings <ben@...adent.org.uk>
To: netdev <netdev@...r.kernel.org>
Subject: ethtool needs a new maintainer
I've become steadily less enthusiastic and less responsive as a
maintainer over the past year or so. I no longer work on networking
regularly, so it takes a lot more time to get into the right state of
mind to think about ethtool code, while I have other demands on my time
that tend to take priority.
So, I would like to find a new maintainer to take over as soon as
possible. Ideally the new maintainer would have previous contributions
to ethtool and an existing account on kernel.org so that they can push
to the git repository and the home page. But neither of those is
essential. Please reply if you're interested.
I was thinking of adding a TODO file to the repository, but it's really
for the new maintainer to decide what to do. So here's my list as a
suggestion:
* Add regression test coverage for all sub-commands with complex logic
* Internationalise output and error messages
* Build a libethtool that handles all the API quirks and fallbacks for
old kernel versions. This might help people writing language
bindings or other utilities that use the ethtool API.
* Provide a 'cleaned up' ethtool (under some other name) that has:
- More conventional sub-command syntax, i.e. no '-'/'--' prefix
- More consistent output formatting
Ben.
--
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists