<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Jim,</p>
<p>As a published author I'm going to jump in here and make a
correction you might think it small but it's extremely important.</p>
<p>Under WIPO and copyright law setout therein, facts ARE NOT
copyrightable. Powercom cannot dictate terms to us or to anyone
on how the the documentation they sent to us is used. Only
expressions are copyrightable.<br>
</p>
<p>I realize it may be hairsplitting to you. Let me illustrate:</p>
<p>The sentence:</p>
<p>"The AC Adapter runs off 60Hz power"</p>
<p>is not copyrightable. However, the sentence:</p>
<p>We recommend that the AC adapter be used on a power strip with
surge suppression"</p>
<p>is copyrightable because it's an expression.</p>
<p>In short, Powercom has no legal ability to exercise copyright
control because of any business requirement to make information
available - in short, they may want the old docs removed (so as to
enhance sales of new devices or any other reason) however they
have no legal authority to demand this.</p>
<p>Do not give them a legal power to do this by asking whether or
not we can keep the old docs up. Under copyright law they do not
have this power.</p>
<p>That doesn't mean we shouldn't be nice, they asked us to remove
the old docs, and while they have no legal authority to make that
request we can acknowledge that they have expressed that desire
and try to honor it as much as is reasonable by prominently
marking the old docs as obsolete. I'll assume their motivation to
take the old docs down is to prevent confusion among developers
when there is a conflict between the old doc and the new doc. I'm
just trying to explain we can't do that since we have to still
support the old gear, but we can eliminate that possible confusion
by being explicit on what is what.</p>
<p>Ted</p>
<div class="moz-cite-prefix">On 10/20/2021 12:04 PM, Jim Klimov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJYg8vK0Xk7w2HL9penae0ueH8vgM0jHnoiN25DQQLAZK=+Gjw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>Thanks Ted,</div>
<div dir="auto"><br>
</div>
<div dir="auto"> that echoes my thoughts: any HW supported by
NUT at some point and with a population of units physically
alive, whether marketed or supported by original vendors or
not, should better be documented.
<div dir="auto"><br>
</div>
<div dir="auto"> So if the old docs are in some way better
than new one, even if explaining quirks not relevant and not
documented for same-named models or firmware sold today, I
believe such docs should remain available (maybe marked as
old stuff, but ready for revision). After all, currently
shipped drivers probably correspond to that spec?..</div>
<div dir="auto"><br>
</div>
<div dir="auto">@Dinow: how strict is the business/etc.
requirement to make that older info truly unavailable? Can
we keep it visible but maybe marked deprecated? </div>
<div dir="auto"><br>
</div>
Jim<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Wed, Oct 20, 2021,
12:05 Ted Mittelstaedt via Nut-upsdev <<a
href="mailto:nut-upsdev@alioth-lists.debian.net"
moz-do-not-send="true" class="moz-txt-link-freetext">nut-upsdev@alioth-lists.debian.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><br>
</p>
<p>Thanks, Dinow,</p>
<p><br>
</p>
<p>I'm not a NUT admin but you posted this to a public
mailing list so I'm going to just send a response to
that list since it's a public posting.</p>
<p><br>
</p>
<p>The current documentation you sent is much sparser
than the older docs. So I think the older docs are
going to still be valuable for just that reason alone,
as an addition to the newer current documentation. I
do not know what the admins are going to do but I
would hope they merely mark the old documents as "Old"
and add this to them.<br>
</p>
<p><br>
</p>
<p>Unlike commercial software, open source software
projects usually do not have the luxury of removing
support for older hardware that is no longer in
production from the manufacturer.</p>
<p><br>
</p>
<p>As a NUT user I cannot thank you enough for
supporting open source software projects like NUT.</p>
<p><br>
</p>
<p>Ted<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div>On 10/19/2021 7:28 PM, dinow via Nut-upsdev wrote:<br>
</div>
<blockquote type="cite">
<div> </div>
<div>
<p><font size="4" face="Times New Roman">Good Day
NUT administrators </font></p>
<p> </p>
<p><font size="4" face="Times New Roman">AA. My name
is Dinow and the engineer of <strong>Powercom</strong>
corporation</font></p>
<p> </p>
<p><font size="4" face="Times New Roman">BB. Could
you help us to :</font></p>
<p> </p>
<p><font size="4" face="Times New Roman"> B1. <strong>Remove</strong>
the current list from Powercom >> <a
href="https://networkupstools.org/ups-protocols.html"
target="_blank" rel="noreferrer"
moz-do-not-send="true"><font face="新細明體">https://networkupstools.org/ups-protocols.html</font></a>:</font></p>
<ul>
<li><font size="4" face="Times New Roman">USB
information for BNT series</font></li>
<li><font size="4" face="Times New Roman">USB
information for IMPERIAL series</font></li>
<li><font size="4" face="Times New Roman">USB
information for SKP series</font></li>
<li><font size="4" face="Times New Roman">USB
information for WOW series</font></li>
</ul>
<p><font size="4" face="Times New Roman"> B2. <strong>Add</strong>
a item and its document</font></p>
<ul>
<li><font size="4" face="Times New Roman">USB
information for <strong>all</strong>
Powercom's UPS</font></li>
<li><font size="4" face="Times New Roman">Add
attached <strong>PDF</strong> as its document</font></li>
</ul>
<p><font size="4" face="Times New Roman">CC. Big
Thanks for your help</font></p>
<p> </p>
<p> </p>
<p><font size="4" face="Times New Roman">If you have
any questions, please don't hesitate to inform
us</font></p>
<p><font size="4" face="Times New Roman">Sincerely
yours truly, Oct. 20th</font></p>
<p><font size="4" face="Times New Roman">Dinow Hsieh</font></p>
<br>
<br>
</div>
<br>
<br>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Nut-upsdev mailing list
<a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">Nut-upsdev@alioth-lists.debian.net</a>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" target="_blank" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Nut-upsdev mailing list<br>
<a href="mailto:Nut-upsdev@alioth-lists.debian.net"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">Nut-upsdev@alioth-lists.debian.net</a><br>
<a
href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</body>
</html>