<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi Dan,<br>
<br>
Sorry I didn't see this sooner, it landed in my spam folder.<br>
<br>
Anyone can submit a license to the license-review list, it doesn't
have to be the license author. Not having the license author means
that all we can do is go/no-go, since the license can't be changed,
but this also looks like a license that isn't likely to entertain
any changes anyway.<br>
<br>
Pam Chestek<br>
Chair, License Committee<br>
Open Source Initiative<br>
<br>
<div class="moz-cite-prefix">On 12/30/2022 11:14 PM, Dan Mahoney
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4D5EFC60-3F45-4EBF-99EF-71CA3FEE4207@prime.gushi.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hello there,
<div><br>
</div>
<div>
<div>My day job is a sysadmin with ISC, but I also have a
part-time maintainership (as Github: TheGushi) of the Trusted
Domain Project’s software including OpenDMARC and OpenDKIM.</div>
<div><br>
</div>
<div>Several of these pieces of software are covered, at least
in part, by the sendmail license and even if we decided to
release any new work under a different license like the MPL,
the sendmail license would still apply to a great deal of our
code, as it was developed by Sendmail Inc. (i.e. the sendmail
license file would not go away).</div>
<div><br>
</div>
<div>In an interesting tom-sawyer quest, getting the license
recognized by Github requires getting it included at <a
href="http://choosealicence.com/" moz-do-not-send="true">ChooseALicence.com</a>,
which in turn requires it to show up on one of three sites (of
which yours is one). What would it take to make that happen?
It DOES have an SPDX entry.</div>
<div><br>
</div>
<div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0,
0);">This is an old license and while it’s not likely to be
used for many new projects (it’s not “in vogue”, and it has
bits in the license that apply specifically to the Sendmail
corporation), there’s a great deal of sendmail in a number
of open source operating systems, so things like Github
*should* be aware of it, especially as Github becomes an
archive location for legacy code that had previously lived
elsewhere.</span></div>
<br class="Apple-interchange-newline" style="caret-color: rgb(0,
0, 0); color: rgb(0, 0, 0);">
</div>
<div>So my question here, before I go through the whole
application process is: do I have enough “standing” as a
maintainer of code previously licensed under this license to
apply for it to be issued? Or is that a non-starter?</div>
<div><br>
</div>
<div>I’m not interested in wasting anyone’s time, but couldn’t
find an obvious contact method on the licensing page, without
submitting a full application. I apologize if this sidesteps
the normal process.</div>
<div><br>
</div>
<div>Looking at your proliferation page (<a
href="https://opensource.org/proliferation-report"
moz-do-not-send="true" class="moz-txt-link-freetext">https://opensource.org/proliferation-report</a>),
I would guess that the sendmail license is considered
“non-reusable” — but it’s certainly not retired in any sense.</div>
<div><br>
</div>
<div>I have also reached out to the FSF with similar questions.</div>
<div><br>
</div>
<div>Best (and happy new year)</div>
<div><br>
</div>
<div>-Dan Mahoney</div>
<div>ISC and Trusted Domain Project</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</body>
</html>