[44net] Re: Update re: subdomains

This thread seems to have got a bit off topic from “subdomains” but to respond to some of the points brought up: 1. Having call signs “owned” by an organisation on the portal is not a scenario we envisaged during the design phase. However, it is a very good point and has now been added to the feature request list as a high priority. 2. In relation to point 1. How do we vet the person requesting access to use an organisation’s call sign? This is really only an issue for US based clubs as the call sign has a trustee listed on the ULS database, but it would seem, that person is not always able/willing/interested in creating an account on the portal to have the call sign verified. This certainly needs more thought. The ideal situation would be for the trustee to create an account on the portal, verify the call sign, then hand it off to another member in the organisation, i.e. once setup they do not have to be the POC for the call sign - is this really asking too much of someone who has already agreed to be the trustee, which arguably comes with such responsibilities? 3. The subdomain policy that is in progress currently will definitely include a workflow for non-standard subdomain formats. I expect (although bear in mind the policy has not been agreed upon yet, so is subject to change) that the policy will state that the preferred subdomain format will be callsign.ampr.org <http://callsign.ampr.org/> and that anything else will be considered on a case by case basis. The portal will currently automatically approve (and create) a subdomain based on the callsign.ampr.org <http://callsign.ampr.org/> format, provided that “callsign” is one of your own call signs that has been verified. Any other subdomain request will create a ticket for manual processing. If anyone wants to respond to any of the above points, please can they create a new thread with an appropriate subject as this one is getting very mixed up! Thanks & 73, Chris - G1FEF — ARDC Administrator Web: https://www.ardc.net