Updates

Bug 1027 - Ease of joining permanents program

The membership services page now links to information about registering for the permanents program.

Work in Progress

Bug 1077 - Membership join/renew workflow

Usability feedback on the membership signup flow was collected at the Philadelphia Bike Expo. We'll ask the membership team to take a first pass and provide feedback, particularly for some of the data format considerations. Should the website just auto-capitalize, reformat dates, reformat phone numbers, etc?

Bug 1074 - Add validation to calendar submission

Calendar submission tool is not currently behind authentication. Brevet coordinator has gotten some spam from someone submitting empty calendaring requests.

Calculator Updates

Charlie and Osvaldo are working to update the time calculations, including the near 200km / 400km point for brevets, so that folks don’t get less time for a 202km or 401km brevet than for a 200km or 400km brevet (RUSA brevets). Jake has made updates to his calculator, and RUSA plans to phase out the legacy calculator in favor of that. Other coordination with Chris Nadovich is required before rolling out additional changes.

Other inquiries

Bug 1068 - Add results submission via API

Concerns:

• Compatibility issues with API clients when the results submission format is updated. E.g. after gravel was introduced, by default third-party software would not be submitting gravel distances, and riders would not get credit. Likewise for if/when elevation credit or other features are introduced.
• Unclear that there's sufficient value add on top of the current CSV upload.

Bug 1070 - Display current P12/R12 streak on results page

Concerns:

• Confusion/panic due to unsubmitted results. There still is not consistent timely results submission across all regions, and this will cause it to appear as though people lost their streak. This can be complicated if there's a submitted result for the subsequent month.
• Confusion due to foreign results. These gaps will make it appear as though people lost their streak.
• Ability to concisely explain the above in a manner that won't result in additional inquiries to the web team.

2025 Web Team Goals

This is for inclusion in the 2025 Board Goals. We can add more detail in our own notes, but for the Board goals, the idea is something succinct that covers each point.

• Cumulative Climbing - Continue rollout work, including support for Alaska and point-to-point routes.
• Authentication-Required Functions - Move certain functions behind user logins (e.g., joining / changing membership, calendaring events and submitting results, viewing volunteer contact info) for security and privacy.
• Gender Designation, Aggregation, and Display - Implement Board’s policy, when it is finalized, on member’s gender options, and for where gender is displayed. 
• Improve membership signup, renewal and data change - 
• Renew perm program registration and membership at the same time?
• Process payment immediately even if an address update is requested.
• Complete Time Calculation Algorithms - … and publish on a common web page. Requires coordination with third parties (Jake, Chris)
• Server upgrade - Upgrade production to newer versions of Debian, Drupal, and PHP.