Hello Nicholas, No problem about the later reply :) >Also, you'll need to >say a few words about how you established copyright--a very short too >long didn't read version of this thread. Find out how to do this at >§5.1 of the following (read the short list of fields, and you'll see >which one it is):
debian/copyright: Files: htpasswd.c htpasswd.1 Copyright: 1993-1994 Rob McCool <r...@stanford.edu> Copyright: 1997 Jef Poskanzer <j...@mail.acme.com> License: NCSA Comment: htpasswd.c and htpasswd.1 contain significant portions of code from NCSA httpd (cgi-src/util.c, auth/htpasswd.c). RobMcCool's copyright was traced from a git repository which imported NCSA httpd (which was verified to be precise). Multiple commits by RobMcCool on HEAD show his contributions on the files specified here. The files are under the NCSA license which qualifies as DFSG compatible after inquiry (specifically, from the license text: "This code is in the public domain. Specifically, we give to the public domain all rights for future licensing of the source code, all resale rights, and all publishing rights" From DSFGLicenses's Q&A on DebianWiki: "Software placed in the public domain has all the freedoms required by the DFSG, and is free software." git repository: https://github.com/TooDumbForAName/ncsa-httpd/ debian-legal thread: https://lists.debian.org/debian-legal/2023/07/msg00001.html DFSGLicenses: https://wiki.debian.org/DFSGLicenses License: NCSA This code is in the public domain. Specifically, we give to the public domain all rights for future licensing of the source code, all resale rights, and all publishing rights. We ask, but do not require, that the following message be included in all derived works: Portions developed at the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign. THE UNIVERSITY OF ILLINOIS GIVES NO WARRANTY, EXPRESSED OR IMPLIED, FOR THE SOFTWARE AND/OR DOCUMENTATION PROVIDED, INCLUDING, WITHOUT LIMITATION, WARRANTY OF MERCHANTABILITY AND WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE. Is my TLDR still a bit TL ? I was trying not to leave out anything related to discussion on debian-legal or how we traced everything back to RobMcCool. Did i get the right field ? "6.6. Comment Formatted text, no synopsis: this field can provide additional information. For example, it might quote an e-mail from upstream justifying why the license is acceptable to the main archive, or an explanation of how this version of the package has been forked from a version known to be DFSG-free, even though the current upstream version is not. " Sounded like a good fit. Replying to previous untackled mail: >Wow, that's wonderful (and unexpected) news! I hope negotiations go well. Thanks, me too :) I'll have to complete the new maintainer process here (and actually have an upload by my mentor (you!) before I can discuss matters more firmly with higher-ups. There's no rush; your patience and attention to detail are very appreciated btw :) >My key is on both the Debian keyring and public servers > > https://wiki.debian.org/DebianKeyring > https://keys.openpgp.org/ > and maybe also here > http://pgp.mit.edu/ OK, thanks, I'll have to find a good place for my key too, then. I hope I haven't missed any points from the discussion here. Have a great day, Alexandru Mihail On Sat, 2023-07-15 at 16:17 -0400, Nicholas D Steeves wrote: > Hi Alexandru, > > Alexandru Mihail <alexandru.mihail2...@gmail.com> writes: > > > After a bit more research into how other projects treat NCSA bits > > I'd > > propose something along the lines of: > > > > debian/copyright: > > Files: htpasswd.c > > Yes, and htpasswd.1. > > > Copyright: 1993-1994 Rob McCool <r...@stanford.edu> > > Copyright: 1997 Jef Poskanzer <j...@mail.acme.com> ? > > Yes, and you would know the years better than I! Also, you'll need > to > say a few words about how you established copyright--a very short too > long didn't read version of this thread. Find out how to do this at > §5.1 of the following (read the short list of fields, and you'll see > which one it is): > > > https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#file-syntax > > > License: NCSA > > > > > > License: NCSA > > This code is in the public domain. Specifically, we give to the > > public > > domain all rights for future licensing of the source code, all > > resale > > rights, and all publishing rights. > > > > We ask, but do not require, that the following message be included > > in > > all derived works: > > > > Portions developed at the National Center for Supercomputing > > Applications at the University of Illinois at Urbana-Champaign. > > > > THE UNIVERSITY OF ILLINOIS GIVES NO WARRANTY, EXPRESSED OR IMPLIED, > > FOR THE SOFTWARE AND/OR DOCUMENTATION PROVIDED, INCLUDING, WITHOUT > > LIMITATION, WARRANTY OF MERCHANTABILITY AND WARRANTY OF FITNESS FOR > > A > > PARTICULAR PURPOSE. > > Looks good to me. > > > Also, looking into your concerns about public domain in other > > countries > > (specifically referring to NCSA's :"This code is in the public > > domain"): > > > > Excerpt from https://wiki.debian.org/DFSGLicenses#Public_Domain : > [snip] > > Thank you for looking into this, and for sharing this information. > > Regards, > Nicholas
signature.asc
Description: This is a digitally signed message part
