Thanks for sharing this work with the community.
Reading through it, some thoughts and questions come up: - I'm delighted to see that accessibility and WCAG is considered. - What is the intent of the Level Of Trust value? Is this about allowing some centralized administrative actions, or does this represent something that community members can earn and level up? - In addition to GDPR compliance considerations, you might also consider California's similar CCPA. - What is the intention of requiring maidenhead locators? I'm mostly just curious how the information gets used, though I suspect it would be useful to map country-granularity call signs to actual geographic areas where the subnets are assigned.
In general, this seems like a really straightforward list of requirements that all make sense in context. Looking forward to experimenting and trying out something new.
Cheers and 73, jof / K6BGP
On Tue, 27 Sept 2022 at 14:37, Rosy Schechter - KJ7RYV via 44net < 44net@mailman.ampr.org> wrote:
Hello 44Net!
For quite some time, y'all have heard rumblings of a new portal, which Chris has been working on bit by bit. Realizing that it's likely a larger project than we initially thought, earlier this year the TAC took on the task of writing a feature requirements document. This has been the bulk of their work this year so far, and I'm really proud of the results, which were completed just a couple weeks ago.
I'm writing on behalf of the TAC to share this document with you and to request comments and comments:
https://www.ampr.org/wp-content/uploads/2022-09-Portal-Features-Requirements...
Ideally, please share your thoughts in this channel rather than emailing directly, though of course we will read any feedback you send. Pierre, the TAC Chair, will be watching the list and answering any questions that may come up.
Note that this document is a feature requirements document - which outlines the features that the portal needs to have before it's considered "done." By definition, it's *not* an engineering document; we've purposefully not specified the exact technology we'll use to build this out. We have, however, specified that it will be released as an open source project as soon as we have a functional version, likely without all features present. Ultimately this will be a project managed by our new Director of Technology (who starts on Monday; will introduce after he starts) and the team he assembles to carry out the build. Thus, information like timelines, project plans, and database specifications, etc., will follow his review of this document and any comments from this group.
And with that, I say - happy reading! And thank you so much for your thoughts and questions.
Looking forward, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org