[App_rpt-users] App_rpt-users Digest, Vol 91, Issue 18

[Greg Thornwall]

I have done a lot of C coding years ago, now I use Java. I wish the code 
was commented better, it's hard to get a grasp on what's going on. For 
the projects I have worked on, we would have to comment every function 
and variables. That way it was easier to bring someone on board or if 
you went back to code that you hadn't looked at in a long while it was 
quick to figure out the code.

73 Greg


On 09/11/2016 01:06 AM, app_rpt-users-request at ohnosec.org wrote:
>
> Message: 3
> Date: Fri, 9 Sep 2016 16:31:11 -0700
> From: Stacy <kg7qin at arrl.net>
> To: Bob Brown - W?NQX <bbrown at byrg.net>
> Cc: Jim Duuuude <telesistant at hotmail.com>,	app_rpt mailing list
> 	<app_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] toy throwing time?
> Message-ID: <bda748d2-f702-5507-06ad-fca9557154dc at arrl.net>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Bob,
>
> You forgot all the additional restriction that the State of California
> puts on everything. :)
>
> Also, I had posted this to the list a while ago.  I did not want the
> code to be left stagnant/lost, and some people seemed to be interested.
>
> The only thing with open source, is that it takes a lot of time and
> effort to move forward.
>
> Both Jim Dixon and Steve Rodgers put a lot of work into the parts that
> are used for the AllStar Network.  (app_rpt is one example of the work
> done).
>
> I had an inkling for starting a port for a long time, and my initial
> attempts were not met with success (the DAHDI driver and a newer Linux
> kernel).  At first, I didn't have a lot of time to put into this.  It
> was only when I had started my transition/retirement from my previous
> job last October (20 years activey duty Navy, retired 1 Dec 15), that I
> had the free time to start on a project like this.
>
> I have since started a new job, so I do not have all the free time I one
> did to work on it.  One of the reasons why put it in a Github repository
> and posted the announcement here several months ago, was because I feel
> there is a desire to move things forward.  I saw this old thread today
> when cleaning up my inbox and decided to re-post the link to it.
>
> You are right, this isn't an official release-- yet.  As with any major
> step forward, testing will be required.  The only way to accomplish that
> is for the code to be picked up, used, poked at and fixed.  This is a
> lot for one person to do, especially since there are parts I can't test
> right now.  App_rpt will run, take/make calls and do its thing.   Does
> it have bugs?  Hell yes.  But is it is start.
>
> And as Jim said before, he loves open source.  That being said, the only
> person who can officially sanction this is Jim himself (see copyright in
> the headers of all the app_rpt and related module source code), and even
> he released it under the GPL.  Unless this plain crashes any of the
> pieces of the AllStar network, nobody will likely know you are running
> it.  I don't recommend trying to run it as a production node yet, but it
> still needs to be run in the environment it will be used in to test it
> out and shake the bugs out.
>
> -Stacy
>
> KG7QIN
>
>