RBA functions with login

Assign routes to events - This was code-complete last month, and it has now fully rolled out.

• See June update for details.

Submit results - This has been implemented and fully rolled out.

• Event results can only be submitted by the respective logged-in RBA or an authorized deputy. The results submission landing page has been filtered accordingly.
• The event verification step (i.e. "Are you sure this is the right event?") has been consolidated into the subsequent workflow step. This process is significantly less error prone now that the event selection page is less cluttered and since you can only submit results for your own events.
• When submitting results for RUSAP, RUSAB, or RM events, you will now have the option to keep the calendared distance (default) or update the event to use the route distance. This provides parity with the route assignment tool.
• RUSAP events can now freely swap routes to any other populaire distance (matching the update to the route assignment tool).
• Fixed several cases where non-applicable routes were selectable, either due to an invalid distance or because the route doesn't support allure libre.

Submit event calendar - This has been implemented and fully rolled out.

• Event calendars can only be submitted by the respective logged-in RBA or an authorized deputy. The region selection dropdown has been filtered accordingly (no selection required if you're authorized for exactly one region).
• Got rid of the RBA # / ACP club # verification fields.
• Form validation is now additionally applied when confirming submissions. This will prevent duplicate calendar submissions when an RBA reloads the page after submitting their calendar.
• The fingerprint for "duplicate" calendar submissions has been relaxed to consider several more properties of events.

A few RBAs provided feedback on bugs/tweaks, and all inquiries have been addressed.

Logged-in indication on non-Drupal pages

Previously only certain website pages would show the logged-in indication in the top-right corner, providing links to the user's account or to log out. These items now appear on all website pages. There are some minor quirks with the current implementation, and there's a design on the backburner for improving it further.

On the radar

Add "back" functionality to some RBA tools to properly pre-populate form inputs, e.g. when fixing validation errors through the calendaring tool.

Self-service ability to configure social media links for each region and have these appear in the Regions list.

Restructure member services workflows to build in privacy.

Drupal updates

Made some progress on being able to update the Drupal environment, however the latest attempt resulted in a website outage overnight. We still don't have a safe/tested workflow for rolling out changes to the Drupal website, but we may have a strategy for cherrypicking updates to specific modules we care about. Lack of a safe deploy process is blocking rollouts for miscellaneous changes including login redirects and RUSA#-only website logins.

Bugzilla

Inconsistent results display for member (1100)

There was a discrepancy between results reported for an event vs what was reported on the rider's results page. This was fixed by deleting the result and adding it back. It's unclear how to reproduce the discrepancy.

Link to Seattle-San Francisco 1700K from RUSA home page appears to be broken (1099)

Drupal has problems with some links into the Seattle site. The link that loads isn't the same one that's configured in Drupal. Resolved by using a URL shortener.

Randonneuring.org and RUSA database integration (1097)

Collecting requirements for how to provide randonneuring.org (eBrevet) with fresher membership snapshots.

How to transition a waxed chain to non-waxed

Charlie demoed how to remove wax from a waxed chain so that it can be lubed with the lubricant of choice.