7 Feb
2016
7 Feb
'16
2:30 a.m.
Rob,
Prior to flaming me, perhaps you should get your facts straight?
I have done several maintenance jobs and bug fixes on the Portal over the past couple of
years, as and when they are reported to me. I’m working on a new feature right now that
was requested.
If you have a problem you only need to contact me and ask for assistance, but I am not
good at reading minds I’m afraid.
As for the DNS code in the Portal, it has been ready for over a year now, but Brian wanted
me to hold off making it live until the current DNS can be cleaned up - hence this push to
do just that.
As to your other comments regarding how the portal operates, that’s your opinion, which
you are entitled to, but I originally wrote the code based on requirements and input from
other folk, I didn’t just “make it up” myself.
Of course, if you want to offer your time re-write some of the code, or add new
functionality then please lets talk, I’ve been asking for help on this for some time now,
but apart from Tom who kindly provided (and still provides) the Polish translation, no-one
else has done anything. And before anyone goes on about “open source” again, the code IS
open source to the amateur radio community, just not the general public as it doesn’t need
to be, if you want access to the code repository you only need to ask and it will be
provided.
Kind Regards,
Chris
On 7 Feb 2016, at 07:16, Rob Janssen
<pe1chl(a)amsat.org> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
No, expectation is that people getting AMPR
address space should
have the subnet they're in registered with the portal. That includes
non-connected hosts and /32s.
Is it really a good idea to base the cleanup on data in the portal?
I mean, the guy running the portal clearly does not have the resources (or the
motivation?) to do even minor maintenance on it, let alone finish work on features
like the DNS registration that have been in incompleted state for years.
Is it a good idea to make our entire network dependent on that?
I cannot remove a subnet that was erroneously added in the past (and where user
subnets where added inside) without deleting those, and a request to the maintainer
to do that outside the portal UI that I sent months ago is still not processed.
I also cannot add any regional subnets for which parts are already registered to
users. The whole implementation of subnet hierarchy and record ownership is much
too strict, it only works when everything is done "the correct way" on the
first try,
which simply is not realistic. Compare it to HamnetDB where you can simply reshuffle
the whole subnetting by inserting, deleting or editing existing records within the
existing hierarchy.