I'd like to think if one private party shared the build with another
private party it wouldn't be an issue - or built them a version to suit
them - but I'd hate to make more trouble for Wayne. I'd think it best
something to do quietly and not publicly. 73 jeff wk6i
On Fri, Oct 11, 2019 at 10:44 AM Alan Maenchen <ad6e@arrl.net> wrote:
> That's rather sad, but I suppose it was bound to happen. I've heard the GNU
> community will aggressively go after anyone trying to make $$ off of GNU
> licensed software. It doesn't seem like a violation the way Wayne put out
> DigiRite, but that's just my opinion.
>
> I gave up doing software when DOS died. It would probably be a good thing
> for my soul to go through this build process but it looks intimidating.
> Maybe a 3rd party can pick this up and do the build? Maybe I'm under
> estimating the process, but in the end one only needs the built files, the
> Visual Studio runtime stuff, and then run that register modifier. Is that
> the case? If a 3rd party offers those files (for free) then the legal
> issues are solved? I would have no problem putting the files in my Google
> cloud account as publicly shared. I have no connection with Writelog other
> than being a user. Would that help?
>
> 73, Alan AD6E / KH6TU
>
>
>
>
>
>
> > ---------------------------------------------------------------------
> >
> > Date: Wed, 9 Oct 2019 15:51:47 +0000
> > From: "Wayne, W5XD" <w5xd@writelog.com>
> > To: Writelog Forum <writelog@contesting.com>
> > Subject: [WriteLog] DigiRite 1.1.32 update. and a new way to
> > distribute it
> > Message-ID: <ad537ea1-0b02-2f79-94fc-98b5bb6d185f@writelog.com>
> > Content-Type: text/plain; charset=utf-8
> >
> > To users of WriteLog with DigiRite
> >
> > There is a new version of DigiRite available. But...
> >
> > Since the previous release of DigiRite, version 1.1.30, we have received
> > complaints from the WSJT-X copyright holders that the combination of
> > WriteLog with DigiRite violates their software license, the Gnu Public
> > License (GPL.) It is our reading that DigiRite does not violate the GPL,
> > but our opinion does not remove the threat that we would have to pay
> > lawyers to defend it. To reduce that threat to a level of risk we are
> > willing to take (it cannot go to zero--anyone can sue anybody for
> > anything in this country) we have removed the DigiRite installer kit
> > from writelog.com. The DigiRite sources remain open (which is the
> > primary requirement of the GPL after all) and are published on github
> > and there are some new features since 1.1.30 that might interest you.
> >
> > These features are in version 1.1.32:
> > ??? 1. fix a bug that poorly chooses the priority of which messages to
> > send to concurrent QSOs in progress.
> > ??? 2. Set the CQ message and the exchange to send in DigiRite dialogs
> > rather than fishing around in WriteLog's f-key memories. (That was not a
> > user-friendly choice in the first place, so its now fixed.)
> >
> > To get a running version of DigiRite 1.1.32, you have to build it
> > yourself (or get someone to do it for you). The software tools are
> > available for free download from Microsoft.? The details are at
> > http://writelog.com/digirite, which links to the build recipe here:
> > https://writelog.com/digirite-build
> >
> > Wayne, W5XD
> >
> >
> >
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
--
Jeff Stai ~ WK6I ~ wk6i.jeff@gmail.com
RTTY op at W7RN
Twisted Oak Winery ~ http://www.twistedoak.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|