[App_rpt-users] Allstar Node

Pierre Martel petem001 at gmail.com
Fri Dec 28 02:03:32 EST 2018


Am I the only one that feel like someone made a subcontract job then left?

If it is not, I appologize. But damn it sure look like one!

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Garanti
sans virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Le jeu. 27 déc. 2018 à 19:38, william howell <william-t2 at live.com> a écrit :

> Wow, I leave for the holidays and come back to over what appears to be a
> hundred or so  attacks, insults, threats of lawsuits, etc.... All this
> started just because I asked a question about sharing the source code and
> what the diff between the two modules and what have you are.
>
> Thank goodness I have all the knowledge and experiences I do with Asterisk
> Software there of. I'm also thankful I have over 30+ years in the two-way
> radio engineering, service/repair, and software development. Cause today I
> feel I no longer can be of use or want to be of use on this mailing list.
> Not that I had that much input as I was watching to see if I wanted to be
> part of this mailing list or not before I invested too much of my time for
> nothing more than this type of crap. That which I find happens in mailing
> list subs like this one.
>
> Maybe some day those of you that want to contiue slinging mud, calling
> people names and threats of lawsuits will get your crap together, learn to
> work together and realize you are only being destructive when you spew this
> crap in mailing list submissions like this one. It does no one any good and
> only makes quality people like myself want to leave and not look back. No
> doubt you asses will have something negitive to say about this email.
>
>
> Thank you for allowing me access to this email list, but I will be
> removing myself shortly.
>
>
>
> Have a great day,
>
> William R Howell, CEO
> Amphibicom, A Division of
> Amphibian Technologies & Solutions
> 20587 State Highway 19 South Suite #13
> Canton, Texas 75103
> Office: 903-287-0069
> Fax: 972-275-6069
>
>
> Consulting, Sales and Services that specialize in the areas of wire &
> wireless communications, EOC (Emergency Operations Center), PEOC (Portable
> Emergency Operation Centers), Dispatch Consoles & Software, Central
> Dispatch Communications Centers, and Call Center Equipment.....
> Installation, Maintenance, and Management.......
>
>
> Where Two-way Radios, Computers, Telephones, Telephone Land Lines, VOIP,
> Hardware & Software all come together........ Working together to make for
> better communications within our communities thru clubs and social
> networking....... A place where Commercial, Public Safety, GMRS, Amateur,
> Marine, Aircraft, and Military operators learn how to coexist together thru
> shared communications....... If it can be done ---- we can do it.....
>
>
>
> ------------------------------
> *From:* App_rpt-users <app_rpt-users-bounces at lists.allstarlink.org> on
> behalf of JJC <cummingsj at gmail.com>
> *Sent:* Wednesday, December 26, 2018 9:04 PM
> *To:* Users of Asterisk app_rpt
> *Subject:* Re: [App_rpt-users] Allstar Node
>
> So you are saying that you are attempting to protect Jim’s intellectual
> property in some way? That same intellectual property that was already
> released as opensource under the GPL?
>
> Incidentally, what you describe in #2 is precisely the spirit (and legal
> function) of the GPL to begin with.
>
> Sent from the iRoad
>
> > On Dec 26, 2018, at 18:14, David McGough <kb4fxc at inttek.net> wrote:
> >
> >
> > My reasoning is simple--if private intellectual property is
> > unintentionally released, which scenario is least damaging:
> >
> > 1. A binary blob that can't be easily reverse engineered and can only be
> > used in a very specific, limited scope way.
> >
> > 2. A source code file that once disclosed can be copied by anyone
> > in the future, for ever more. Something like:
> >
> >        void my_secret_spy_function() {
> >            //
> >            // patented or licensed algorithms
> >            //
> >            //
> >        }
> >
> >
> > I would argue that #1 would be the least damaging to an unknown owner's
> > intellectual property rights. At least an attempt has been made to limit
> > the damage to any intellectual property, while waiting for the dust to
> > clear.
> >
> > Twenty two months ago, I fully expected a new copyright owner to emerge,
> > once Jim's Estate was settled---easing many of my concerns.  Those were
> > the claims being made at that time.  Now, with the records of what has
> > actually transpired, I really don't know what to think.
> >
> >
> > It's pointless to argue semantics any further.
> >
> >
> > 73, David KB4FXC
> >
> >
> >
> >> On Wed, 26 Dec 2018, Willem Schreuder wrote:
> >>
> >>> On Wed, 26 Dec 2018, David McGough wrote:
> >>>
> >>> So, what happens if a supposed copyright owner shows up 10 years from
> now
> >>> and says:  "That code or function (or whatever) was never GPL2 and
> should
> >>> never have been released!" ---and they have reasonable proof?
> >>
> >> I'm not sure I understand the argument.
> >>
> >> Are you saying that it is not appropriate to share the source, because
> you
> >> are not sure that the it is covered under the GPL?  In that case, are
> you
> >> not opening yourself to greater liability by continuing to modify and
> use
> >> it, if you are not sure whether it is covered by the GPL or not.
> >>
> >> The whole point of the GPL is that once the code is released under the
> GPL
> >> that there is an explicit grant to EVERYBODY to do with the code as
> they
> >> see fit, the only restriction being that you must continue to share the
> >> source.
> >>
> >> It seems to me that if you comply with the GPL, you have a reasonable
> >> argument that you acted in good faith and you can claim innocent
> >> infingement, regardless of who the original copyright holder is.
> >>
> >> If on the other hand it is true that the GPL does not apply, you are
> quite
> >> right to worry about modifying and redistributing the code.
> >>
> >> I apologize if I misundertood your argument, but I am not following.
> >> -Willem
> >>
> >> ================================================================
> >> Dr. Willem A. Schreuder,  President,  Principia Mathematica
> >> Address:  445 Union Blvd, Suite 230,  Lakewood, CO  80228, USA
> >> Tel: (303) 716-3573   Fax: (303) 716-3575
> >> WWW: www.prinmath.com   Email: Willem.Schreuder at prinmath.com
> >> _______________________________________________
> >> App_rpt-users mailing list
> >> App_rpt-users at lists.allstarlink.org
> >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
> >>
> >> To unsubscribe from this list please visit
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email address and press
> the "Unsubscribe or edit options button"
> >> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
> >>
> >
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at lists.allstarlink.org
> > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> > To unsubscribe from this list please visit
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email address and press
> the "Unsubscribe or edit options button"
> > You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email address and press
> the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email address and press
> the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Garanti
sans virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20181227/57814eb8/attachment.html>


More information about the App_rpt-users mailing list