[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#966701: Driverless printing in buster via ipp-usb

Brian Potkin
>>> Justin B Rye wrote:
>>>> Hang on, is this to go in "What's New"?  If so, it's competing with a
>>>> version that was added a couple of days ago -
>>>>  https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef
>>>> Have you seen that version?
>>> Doesn't that concern driverless scanning?
>> Ah, phew.  But shouldn't they both be under a heading "Driverless
>> Printing and Scanning in Bullseye", with a subsection on printing and
>> a second subsection starting "Similarly..." on scanning?
> Printing and scanning involve completely [^different] processes, so I have an
> aversion to lumping them together. Two many users start off an
> issue description with "My scanner works but my printer doesn't."

If we were documenting the internal implementation details, this would
make sense, but the Release Notes are for users who have absolutely no
reason to care about that.  The thing that matters to owners of
printer/scanner hardware is that they should expect similarly improved
functionality for both these processes.

Certainly there are differences in how CUPS and SANE achieve
driverless operation, but in each case the user-visible changes boil
down to "by pulling in new protocol-handling dependencies" (and in
fact ipp-usb comes into play for both).

> I don't see anything to be gained with a composite section.

Well, for a start, we don't want to make users read through two
separate competing explanations of what driverless operation is when
they only need to read one.  We should try to pull out as much
repeated material as possible from the two sections and say it in an
introductory paragraph; and for that to work, they have to be in a
joint "Printing and Scanning" section.
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package

Reply to: