**
*Hey Everyone,*
*
Below are some updates from this week regarding 44Net:
As of today,
*
About 54 new tickets are in the queue.
*
About 153 tickets are open and awaiting response.
o
50 are awaiting response from the user.
o
49 are awaiting response from an ARDC admin.
Since April 3, we have closed 926 tickets.
The next Regional Coordinators meeting is tomorrow, Saturday, July 27,
2024 at 10am PDT / 5pm UTC. If you’re a Regional Coordinator and would
like to attend, please RSVP using the Groups.io calendar of the subgroup
or email contact(a)ardc.net <mailto:contact@ardc.net>to receive the Zoom
link. You will also be able to find the agenda and other documents we’ll
be discussing at the meeting on the pinned message in the Coordinators
subgroup, ardc.groups.io/g/coordinators/topics
<http://ardc.groups.io/g/coordinators/topics>.
In response to a request to share our lessons learned from the portal
launch, Rosy sent an email out yesterday titled “Portal rollout lessons
learned,” which includes a cleaned-up summary from our internal
retrospective. Here’s the link on Groups.io if you’d like to take a
look:
https://ardc.groups.io/g/44net/topic/portal_rollout_lessons/107550598
<https://ardc.groups.io/g/44net/topic/portal_rollout_lessons/107550598>.
As many of you have asked about ways to help with the portal: if you
come across something in the portal documentation
(https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…
<https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>)
that’s not clear or intuitive, or if you have other feedback, please let
us know at newportal(a)ardc.net <mailto:newportal@ardc.net>.
As always, let us know if you have any questions!
73 and have a great weekend,
Rebecca
KO4KVG
*
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Hello all,
A few weeks ago, someone requested that ARDC share our lessons learned
from the recent Portal launch. In the spirit of transparency, please
find those notes below. They comprise a cleaned-up summary from an
internal retrospective that occurred just over a month ago.
Our retrospectives follow the following format:
* What worked well?
* What didn’t work as well?
* What can we do better next time? (These become action items / updates
to internal standard operating procedures)
The “lessons learned” notes are summarized in a similar format below.
As you can see, there’s a lot of room to improve, but the good news is
that we are learning a lot and actively working to improve it.
Feedback and questions welcome; as always, please be kind.
73,
Rosy
//
What worked well?
* Our pre-testing identified numerous bugs and UI problems, and we fixed
them pre-deployment
* We fixed bugs quickly, pre- and post- deployment
* We provided user-facing how-to documentation
* UI of new portal was vastly improved from old portal, including the
implementation of a new ticketing system
* ARDC internal team worked well together, ensuring team cohesion even
during the most challenging portions of deployment
What didn't work as well?
* The code was not developed in an open-sourced fashion, eliminating
opportunities for feedback and improvement pre-launch
* We were not sufficiently prepared for the initial call sign
verification volume (we expected 30-50 in the first 24 hours; we
received over 1000 in that time frame), and thus were not able to handle it
* Our DNS/Subdomain and Level of Trust policies were incomplete prior to
launch, resulting in confusion with our staff and volunteers, as well as
44Net members
* The initial / pre-launch communications to the mailing list did not
fully prepare users for the shift in procedure. As an example, we did
not specify major changes in workflow or policy from the user’s
perspective.
What can we do better next time?
* Engage all stakeholders (in this case, regional coordinators and
general 44Net users) in the design process
* Provide any new or updated policies well in advance of launch,
providing opportunities for feedback and discussion.
* Develop code in an open-source fashion, or at least share v1 code well
in advance of production-level deployment.
* Ensure that we have trained multiple administrators, so that we can
handle a potential overload of usage.
* In our communications, make sure that we are clear about what’s
changing and what’s staying the same, and speak to it from the user's
perspective. Also provide notice farther in advance (e.g. 2-3 months,
with reminders, rather than just 2-4 weeks)
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
Hello Everyone,
I do not know if this is the appropriate list to ask this question but I can not
find any other contact. So please ignore if this is irrelevant!
I am trying to connect to HamCloud VPN service. So far I have imported my LOTW
certificate to Mozilla Firefox 115.12.0esr and try to authenticate as a radio
amateur against https://vpn.hc.r1.ampr.org by clicking on "Login ARRL LoTW" in
order to get my credentials but the links do not seem to work!
Any help would be greatly appreciated!
Thanks
Apostolos, SV1LJJ
**
*Hey Everyone,*
*
Below are some updates from this week regarding 44Net:
As of today,
*
About 48 new tickets are in the queue.
*
About 139 tickets are open and awaiting response.
o
46 are awaiting response from the user.
o
45 are awaiting response from an ARDC admin.
Since April 3, we have closed 921 tickets.
The next Regional Coordinators meeting is next Saturday, July 27, 2024
at 10am PDT / 5pm UTC. If you’re a Regional Coordinator and would like
to attend, please RSVP using the Groups.io calendar of the subgroup or
email contact(a)ardc.net <mailto:contact@ardc.net>to receive the Zoom link.
ARDC is Hiring for an Administrative & Marketing Associate. If you’re
interested in applying, send a resume and cover letter to hr(a)ardc.net
<mailto:hr@ardc.net>and be sure to send all files (including a cover
letter) as a PDF attachment without spaces in the name (e.g.,
jane-doe-cover-letter.pdf). To learn more about the role, check out our
latest blog post:
https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/
<https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/>.
As many of you have asked about ways to help with the portal: if you
come across something in the portal documentation
(https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…
<https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>)
that’s not clear or intuitive, or if you have other feedback, please let
us know at newportal(a)ardc.net <mailto:newportal@ardc.net>.
As always, let us know if you have any questions!
73 and have a great weekend,
Rebecca
KO4KVG
*
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
**
*Hey Everyone,*
*
Below are some updates from this week regarding 44Net:
As of today,
*
About 19 new tickets are in the queue.
*
About 117 tickets are open and awaiting response.
o
70 are awaiting response from the user.
o
28 are awaiting response from an ARDC admin.
Since April 3, we have closed 918 tickets.
ARDC is Hiring for an Administrative & Marketing Associate. If you’re
interested in applying, send a resume and cover letter to hr(a)ardc.net
<mailto:hr@ardc.net>and be sure to send all files (including a cover
letter) as a PDF attachment without spaces in the name (e.g.,
jane-doe-cover-letter.pdf). To learn more about the role, check out our
latest blog post:
https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/
<https://www.ardc.net/ardc-is-hiring-administrative-marketing-associate/>.
As many of you have asked about ways to help with the portal: if you
come across something in the portal documentation
(https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…
<https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>)
that’s not clear or intuitive, or if you have other feedback, please let
us know at newportal(a)ardc.net <mailto:newportal@ardc.net>.
As always, let us know if you have any questions!
73 and have a great weekend,
Rebecca
KO4KVG
*
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
Dear 44Net community,
I think it’s safe to say that the past few months on this mailing list
have been, well, a lot. ARDC launched a new portal, which, we learned
post-launch, definitely had some major issues. Much of the frustration
around this rollout is more than reasonable.
Unfortunately, communications from a very vocal minority crossed a
threshold from expressing warranted and reasonable frustration and
shifted to hostility, flaming, and trolling. Harassment of some of our
employees occurred off-list.
It was at this point that ARDC’s Code of Conduct committee was brought
into the discussion. The Committee’s purpose is to confirm whether, in
fact, a dispute is simply a disagreement, or whether it is harassment,
trolling, or similar. Necessarily, the Committee must not include people
directly impacted by the dispute, so that they can, to the best of their
ability, respond impartially. At an even higher level, their job is to
uphold ARDC’s values – notably of respect, accountability, and fairness.
https://www.ardc.net/about/values/
In the case of this dispute – as a previous mail forwarded to these
lists described – the committee’s decision was to temporarily suspend
the accounts of one or more mailing list members.
Some mailing list members may not like this decision. Other mailing list
members have applauded it. Some mailing list members are so frustrated
by the entire situation that they are unsubscribing and/or relinquishing
their posts (which, to me, is disheartening but understandable).
In our decisions, we are not going to make everyone happy. It is the
nature of making decisions in an environment with a variety of opinions.
To maintain room for diversity of thought, our commitment must be, first
and foremost, to keeping healthy, supportive spaces for dialogue,
discussion, and learning. This means, at times, (ideally temporary)
removal of people whose behaviors significantly detract from those goals.
In the breathing room that has been created from the temporary
suspension, I hope that we may all get back to solving technical and
policy problems, and to engaging in open and respectful dialogue.
Thank you for your attention.
73,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
**
*Hey Everyone,*
*
It’s a short week here at ARDC, as we will be closed on Thursday, July 4
and Friday, July 5 in observance of Independence Day in the US. We will
return to the office on Monday, July 8.
Below are some updates from this week regarding 44Net:
As of today,
*
17 tickets have been received since June 29, bringing our total of
new tickets to 37.
*
About 288 tickets are open and awaiting response.
o
214 are awaiting response from the user.
o
37 are awaiting response from an ARDC admin.
Since April 3, we have closed 746 tickets.
As many of you have asked about ways to help with the portal: if you
come across something in the portal documentation
(https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…
<https://www.ardc.net/wp-content/uploads/portal-2.0-technical-documentation-…>)
that’s not clear or intuitive, or if you have other feedback, please let
us know at newportal(a)ardc.net <mailto:newportal@ardc.net>.
As always, let us know if you have any questions!
73 and have a great weekend,
**
Rebecca
**
KO4KVG
*
--
Rebecca Key - KO4KVG
Communicaions Manager
Amateur Radio Digital Communications (ARDC)
ardc.net
When I am in the Update Gateway page and trying to link gateway, I get http 500 error after click on “add new network”.
[cid:image003.png@01DACA57.43FF47E0]
Could anyone take a look at the portal?
Thanks
Kun
