I agree that some type of contributable portal code would be helpful. I'd certainly contribute. Perhaps we just throw up a repo on github for non-critical code (read: security related) with one or two folks at the help to review pull requests.
I think this would help 1) decrease TODO list workload for Chris/Tom 2) increase portal features 3) quick bug fixes 4) still allow control over the project and avoid arbitrary code pushes
Thoughts? I wouldn't mind help getting everything setup for this
-Andrew Kc2LTO
On Thu, Feb 26, 2015 at 1:14 PM, Rob Janssen pe1chl@amsat.org wrote:
(Please trim inclusions from previous messages) _______________________________________________
Subject: Re: [44net] Portal From: Tom Hayward esarfl@gmail.com Date: 02/26/2015 08:06 PM
To: AMPRNet working group 44net@hamradio.ucsd.edu
I think if you were to open source the portal you would get more volunteers. I, and many other open source developers, tend to wait to jump in to a new project until we have an itch that needs scratching. When a bug affects me, I'll look to the source to see if I can squash it. If I can, the project maintainer can expect a patch from me. If the source isn't public, I'll send a bug report to the developer. I presume you would prefer patches to bug reports.
I agree with that. I have submitted several reports and explained my requirements to Tom SP2L but as I have no access to the code I cannot have a glance to see how quickly some of my immediate requirements can be built in, let alone do the work and submit it.
I still get "DNS requests" from users who apparently do not see the big red print on top of the DNS page, and I cannot edit the subnet structure in the system to match reality. I submitted it in text form to Chris long ago but it was not inserted.
We are currently building a HAMNET similar to what has been done in Germany and Austria, and we really need a working system some time. I fully understand that time is not always available, but some way has to be found to keep the day-to-day operations possible, maybe with a lower level access to the data when writing code for the userfriendly web frontend is the bottleneck.
Rob