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

Bug#1025375: hydrogen-doc: documentation binary package is almost empty, should it be dropped entirely?



Control: forwarded -1 https://github.com/hydrogen-music/documentation/issues/73

Dear Francesco,

I've enjoyed reading and learning from your analyses on debian-legal,
and I'm happy it was you who noticed this issue and filed this bug!
[edit: sorry for the delay, it seems I forgot to send this draft 22 Dec
2022]

There is hope, and GPL2+ licensed docs are pending, but upstream may not
be able to meet our deadlines.  I suspect a statement of yours upstream
may expedite the process ;) tldr: It looks to me like the remaining two
old contributors contributed documentation under GPL2+ and that there
isn't any need to rubber-stamp the new documentation subproject, because
their contributions remain inherently GPL2+ licensed, because that
license could not have been legally stripped by moving their work from
the GPL2+ Hydrogen project to the accidentally license-less period of the
Hydrogen/Documentation subproject.

In terms of strategy/plan, a near-empty bin:hydrogen-doc in src:hydrogen
keeps the door open for this: In the event upstream is too slow, we
populate src:hydrogen's bin:hydrogen-doc with the new documentation from
the upstream "Hydrogen/Documentation" subproject during the freeze.  If
upstream moves quickly enough then it may be possible to for a
src:hydrogen-documentation upload to experimental that takes over
bin:hydrogen-docs to clear the NEW queue; after that, it would be
possible to drop bin:hydrogen-docs from src:hydrogen package in
unstable.

To be honest, I'm not sure if there will be enough time for an ideal
solution, and I'm not convinced that a separate NEW
src:hydrogen-documentation package would be ideal, but I preemptively
filed an RFP (with context) in case someone preferred[s] this solution
and wanted[s] to start work on it:

  https://bugs.debian.org/1020936

I'd be totally OK with you (or someone else) taking up the baton for
these two interrelated bugs. (1025375 and 1020936)

Cheers,
Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: