Hi Alexandru,
Alexandru Mihail <alexandru.mihail2897@gmail.com> writes:
> After yet some more software archaeology, I've uncovered some more
> rusty HTML 1.0 documents which are of interest to our dilemma.
> Apparently, NCSA HTTPd Acknowledgements as of 7-14-95 state:
> "Thanks to:
> Robert McCool
> For developing NCSA HTTPd till version 1.3 and this documentation."
>
> https://web.archive.org/web/20090416132804/http://hoohoo.ncsa.uiuc.edu/docs/acknowledgement.html
>
> This is the time Robert left the project and the date (and license
> release - 1.3) probably aligns best with the code we have in mini-
> httpd. After extensive googling, it seems to me that the original mini-
> httpd-1.0.0.tar.gz source is lost to time, or at least is buried beyond
> my reach.
That's ok, you don't need to find the original version. Remember that
it's a fork and child relationship, so anyone, today, can fork httpd
(1.1-1.3, 1.4-1.14, 1.15, etc.) under the license terms specific to a
particular release. So, for a hypothetical case where the file[s] in
question are identical for the following versions ..:
1.1-1.3: "Do what you want but only on continental landmasses" license
|| \\
|| \=Possible fork point. If discriminating against islanders
|| is important, then fork from this point.
\/
1.4-1.14: "Non-commercial use only, except for fishermen" license
|| \\
|| \=Possible fork point. If privileging fishermen and
|| discriminate against everyone else is important, then fork
|| from this point.
\/
1.15: GPL3+
\\
\=Possible fork point. Only discriminates against those who
wish to keep their source private while also distributing their
fork. Fork from this point if that's important.
...then if httpd 1.15 is older then mini-httpd 1.30, you must choose
1.15. Meanwhile, Robert McCool's copyright still exists in 1.15 even if
he hasn't made a contribution since 1.3.
P.S. Please acknowledge: Have you read the DFSG yet, and do you
understand why it's important?
https://wiki.debian.org/DebianFreeSoftwareGuidelines
> I transitioned all debian mail-related services to Google, and am using
> a good MUA now (PGP signing properly). (BTW, does everything look all
> right on your end?)
I confirm receipt of your mail, and I see an attached signature. Where
can I download your public key?
> I've committed to salsa and uploaded to mentors a new .changes which
> reflects the change in Maintainer's E-Mail. Naturally, I changed the
> key and updated the changelog.
Thanks!
> Thanks and have a great day/night !
You too! :)
Regards,
Nicholas
Attachment:
signature.asc
Description: PGP signature