I want to see male/female open/masters/and all category records

There is no obvious way to log into the site. I'm already logged in on another computer, but on a fresh computer I can't see how to login. I tried going to /race_editions, as that was a link that starts admin stuff, but just got "page not found"

It's currently possible for someone to enter a birthdate from any year. So for example a person might enter "3/15/08" and the system would interpret this as March 15 of the year 0008.

Birthdates should be analyzed and interpreted as being in the 1900s or 2000s as appropriate.

We're a couple of Rails versions behind at the moment. It would be good to get up to Rails 7. We are also a version behind on the Heroku stack. We are using Heroku-20, but Heroku-22 is now available. Heroku-22 requires Ruby 3.1, so the upgrade path needs to reflect that ordering. The Heroku article does not indicate that Ruby 3.1 is required, but I was not able to get OST up to Heroku-22 without first upgrading to Ruby 3.1.

Path to completion:

• Bump Rails to the latest security patch (#138)
• Upgrade Rails to 6.1 (#139)
• Use Rails 6.1 configs (#140)
• Upgrade to Ruby 3.0 (#146)
• Upgrade to Ruby 3.1 (#151)
• Convert to Heroku-22 stack
• Upgrade to Rails 7 (#161)
• Use Rails 7 configs

This is so that I can send a personal email out to the signed up racers. Yes, an email service might be in our future, but we don't need it just yet.

It would be good to force HTTPS access on the production site.

The Friendly Id gem has a nice History feature that keeps track when slugs are changed and redirects to the new slugs. We should add this feature before changing any of our slugs.

Path to completion:

• Migration to add a friendly_id_slugs table
• Rake task to add existing slugs to the table
• Add :history extension to Race and RaceEdition models

See readme for some initial design ideas

This is course maps, description, elevation profiles, etc.

Currently, I just have to remember this URL:

http://www.rattlesnakeramble.org/race_editions/rattlesnake-ramble-trail-race-on-2019-09-14/racer_emails

The #enter action appears to be a leftover from an earlier version of the site. I do not believe it is needed.

We should consider removing the action with its associated route and view.

There are a few good admin gems out there that would allow us to make changes to records without getting into console. The one I'm most familiar with is Madmin.

The site is a few years behind for both Rails and Ruby. It would be good to get these upgraded to recent versions and do a full dependency audit.

The goal for before the 2020 race should be Rails 5.1.7 and Ruby 2.5.
The goal for before the end of 2020 should be Rails 6.0 and Ruby 2.6 or 2.7

It would be helpful to have GitHub CI set up. This service is free.

This is so people do not have to click the "back to merchant" link in PayPal

Things like:

• 2-time finisher
• Defending champion
• Past champion
• First time Rambler!

Currently, the only way we can list race entries is to access a /race_entries index that shows all race entries from all years.

We should have a way to show a race entries list scoped by a single race edition, using /race_editions/:id/race_entries.

The links on the home page for the 2021 race are leading to pages that don't exist. It would be nice to make these dynamic so they start working when the new race edition is created.

My suggestion would be:

1. Check the most recent race edition
2. If we're past the date, don't provide sign-up links. Maybe link to the most recent race report instead.
3. If we're not past the date, provide sign-up links.

To comply with health regulations during the pandemic, we need the ability to schedule runners with variable start times to allow them to go off in smaller waves.

• Migration to add scheduled_start_times column to race_entries table (#62)
• Use the scheduled_start_times column when serializing records to send to OST (#59)
• Migration to add default_start_time_female and default_start_time_male to race editions (#59)
• Remove male_offset and female_offset code (#59)
• UI for entry of default start times for race editions (#75)
• UI for entry of scheduled start times when bib numbers are assigned (#76)
• Remove male_offset and female_offset database columns (#80)

Should be similar output to previous email issue

This is for future wave starts, which I liked. Not exactly sure what I want to do with waves going forward, though.

This is for next year - we don't want them creating a duplicate racer.

This only works for www.rattlesnakeramble.org now.

The Heroku stack we are using (heroku-16) is deprecated and will go out of service on May 1, 2021. We need to push a change to trigger a redeploy onto the newest stack (heroku-20). Any change will do, even a tweak to the README file as is proposed in #107.

I want to see total number entered in each category.

We need to add a JSON endpoint to make it easy for OST to pull data in for a specific race.