An AUP is needed for the private server.
Items to be considered;
Users must be identifiable ( no generic appointments )?
Email addresses must be those registered on the national database?
RAYNET members only ( what happens if someone tries to put radio club members on etc. ‘because they could help’ )
Users accountable for causing any loops
Service to a user can be terminated if they cause loops or other anti-social behaviour.
Service terminated one month after their membership expires ( to allow for renewal issues ).
Would need extension for groups who eventually run their own servers more locally to get resilience and bridge back into the main network.
Should this be the DMR server only or try and do something that covers all digital services?
An AUP is needed for the private server.
Items to be considered;
- Users must be identifiable ( no generic appointments )?
- Email addresses must be those registered on the national database?
- RAYNET members only ( what happens if someone tries to put radio club members on etc. 'because they could help' )
- Users accountable for causing any loops
- Service to a user can be terminated if they cause loops or other anti-social behaviour.
- Service terminated one month after their membership expires ( to allow for renewal issues ).
- Would need extension for groups who eventually run their own servers more locally to get resilience and bridge back into the main network.
Should this be the DMR server only or try and do something that covers all digital services?
M7GUY
g0dub
An AUP is needed for the private server. Items to be considered;
Should this be the DMR server only or try and do something that covers all digital services?
… and the obligatory privacy notices etc. for the server for GDPR….