On Jul 7, 2019, at 2:59 PM, Tim Sawyer <tisawyer@gmail.com> wrote:
I asked Todd to comment on this. He has done so here: History of Zapata Telephony, Asterisk, Allstar and app_rpt open source
On Sun, Jul 7, 2019 at 9:56 AM Tim Sawyer <tisawyer@gmail.com> wrote:
Zapatelephony predates both app_rpt and Asterisk. Asterisk and app_rpt are based on concepts presented on the Zapatelephony web site. This bit of history is not well understood but Todd Lesser (who's name in on that site and is a current AllStar board member) was there through it all. That Zapatelephony site is about the circuit board. Read the whole http://zapatatelephony.org web site, not just the one page taken out of context.
The Zapatelephony circuit board was released under public domain to lower the cost of PBX creation. Asterisk and app_rpt have been open source since day one. There is no question about that any "proof" to the contrary is plainly wrong.
On Fri, Jul 5, 2019 at 3:11 PM David McGough <kb4fxc@inttek.net> wrote:
Joshua,
I am now restating FACTS which have been presented multiple times. While
various persons will quickly try and dispute these statements, to this
date, NO ONE has provided ANY LEGAL PROOF that this information isn't
truth. There continues to be plenty of hearsay and "oh, it's all GPL2"
comments.
The fact is that I firmly believe that app_rpt and some related software
are dedicated to the public domain, as is stated in this document which
was on the "official" Zapata Telephony website from 2005 through 2016.
See the fine print at the bottom of this document:
https://web.archive.org/web/20160315124205/http://zapatatelephony.org/Rpt_Flow.pdf
AllStar Link Inc (ASL) is an organization which formed after Jim Dixon
died INTESTATE (he had no will). I have not been presented with any PROOF
that ASL has LEGAL ownership of *ANYTHING* related to Jim Dixon's estate.
While various persons will quickly dispute this statement with hearsay, NO
ONE has provided ANY LEGAL PROOF that this information isn't truth.
If you wish to lookup Jim Dixon's probate case, the case number is:
17STPB08347
Go to this website and search for the case number:
http://www.lacourt.org/casesummary/ui/index.aspx?casetype=probate
As a matter of record, no HamVoIP code comes from any ASL source (e.g.
github). Our codebase pre-dates ASL's existence.
So, there isn't any "face to lose." The HamVoIP team has done nothing
wrong. My earlier post, which is at the bottom of this message, is simply
a response to the stupidity of implications being made by others.
Enough said, I've got other more important fish to fry. Now let the flames
(hearsay) fly.
73, David KB4FXC
On Fri, 5 Jul 2019, Joshua Nulton wrote:
> John don't go so far as to lose the dignity. Many of us in both aisles
> respect you both as developers even though we don't agree with this move.
> You're now making jokes about something serious and most who understand the
> deeper issues know it is not a laughing matter, as a developer you know
> this too.
>
> I am not bashing you guys. I know you guys have good intentions. Doug too
> is a good man. You have made Pi specific improvements, you know VoIP
> networking very well (probably better than the ASL team) and your team
> offers TONS of support to the public. But those of us who know software
> (yourself included) also know you are not doing the right thing.
>
> Forking software is one thing, and is acceptable, but that is not what was
> done. You can not take open source software and brand it as your own
> proprietary product, released as a package or not. I am sure you feel a
> deep connection to it after all the years you've put into it, but it was
> not yours to foster in the first place. Worse than that you are trying to
> fork the entire community. It is getting ugly and you could fix it all so
> easily. Your improvements are good, so commit it to master, take the credit
> for it and be done with what could get nasty. Don't lose face on this. It
> was a gift to all of us on the condition that it remain open, it really is
> that simple. Have some respect for Jim and the team that gave us this gift.
> Please just do the right thing and let's put this behind us.
>
> On Fri, Jul 5, 2019, 2:49 PM Robert Ruddy <bob@ruddy.net> wrote:
>
> > 100% agree with everything you said.
> >
> > Bob
> >
> > On Fri, Jul 5, 2019, 13:37 Steve L <kb9mwr@gmail.com> wrote:
> >
> >> I won't go so far as to suggest there could be something nefarious in
> >> the compiled hamvoip code. That is something that really on concerns
> >> me with big corporations like Sony Rootkit scandal. Here we just have
> >> two groups of people who don't see eye-to eye.
> >>
> >> The bigger problem is the folks (user base/end users) that don't see
> >> the benefit of open source
> >>
> >> Well I will share the reason I moved to Allstar (or more specifically
> >> App_rpt at the time, because I think the Allstar branding came later)
> >> from the IRLP platform was IRLP suffered the same lack of source
> >> issues. And I am no appliance operator. I can only be satisfied so
> >> long being and end user. I wanted to modify things, change things
> >> that that the closed IRLP platform wouldn't allow me to. Allstar
> >> became the answer to my prayers.
> >>
> >> Sure Hamvoip can be a good place to start, but if you are like many
> >> you will be unsatisfied at some point later. Then there is the whole
> >> what happens if some dies (like Jim did) or pulls the plug? In an
> >> opensource environment, the project can live on, like it has. In the
> >> closed source case, not so much.
> >>
> >> Same reasons I moved away from DD-WRT (no source code) and favored Tomato.
> >>
> >> Same reason AMBE bugs the heck out of me...
> >>
> >> Aside from a good number of documents that the Hamvoip guy have out
> >> there, I don't see how the project gives back to the community, other
> >> than by providing something geared for appliance folks.
> >>
> >> Ham radio is and always has been a work together thing.
> >>
> >>
> >> On Wed, Jul 3, 2019 at 10:07 PM David McGough <kb4fxc@inttek.net> wrote:
> >> >
> >> >
> >> >
> >> > You forgot to mention that "secret spy" software included in the HamVoIP
> >> > release is designed to dampen the Sun's double-oscillator, throwing it
> >> > completely out of phase. With each new HamVoIP node deployed, the effect
> >> > becomes more pronounced, ultimately causing a Maunder Sunspot Minimum.
> >> > This, of course, is to the HamVoIP advantage, since no sunspots means
> >> even
> >> > more hams will need AllStar for communications. Which, in turn, dampens
> >> > the Sun even more.
> >> >
> >> > A movie is already in production. In this remake of the classic 1962
> >> > thriller "Dr. No," SPECTRE is replaced SPARKY, AKA: John David McGough,
> >> as
> >> > the Arch villain (running Arch Linux, of course). In a twist of the plot
> >> > from the original movie, SKYNET is accidentally created by huge
> >> Raspberry
> >> > Pi cluster, leading to world domination.
> >> >
> >> >
> >> > ....LMAO....
> >> >
> >> >
> >> > 73, David KB4FXC
> >> >
> >> >
_______________________________________________
App_rpt-users mailing list
App_rpt-users@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.
--
Tim WD6AWP
--
Tim WD6AWP
_______________________________________________
App_rpt-users mailing list
App_rpt-users@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.