Freezing Saddles Technology – 2020 Thread
- This topic has 66 replies, 19 voices, and was last updated 5 years, 3 months ago by
.
-
Topic
-
For the 2nd year running, I’m declaring an official Freezing Saddles Technology thread.
This year we’re again managing the Freezing Saddles software (hosted on GitHub) through GitHub issues and a GitHub Project Kanban board. I plan on communicating with the technology team primarily through a Freezing Saddles Slack chat system. I’m leading the team this year again and have been doing most of the programming and almost all of the operations, but I’m eager to teach others what they need to know. I’m hoping that @jrenaut will continue to help as he has in previous years (again! thank you!) and I’m looking forward to getting more active contributions from potential technology team members.
With that in mind, I’d like to call for volunteers, please post here if you want to contribute, even if you are not sure you have either the skills or the time to contribute.
I’d like to host a series of scheduled drop-in Freezing Saddles development sessions in Arlington and DC and (gasp) maybe even Maryland if we have any tech volunteers who live in points north. Getting started with developing on this system can be a bit intimidating but I’d like to help ease that transition. Please pipe up if you think this would encourage you to contribute.
If you have a problem with the Freezing Saddles web site, you can post about it here, or add a note to the board or to the freezing-web issues.
Last year we made excellent progress in maintaining and extending the system, after some initial hiccups in transition. @hozn originally wrote software that runs the freezingsaddles.org site using Python, Flask, SQLAlchemy, Alembic, and some other frameworks, and last year we had our first full year of running through Docker. It is currently running on a Digital Ocean droplet that hozn is graciously footing the bill for, but we may complete a move away from that system to a new home this year.
The main challenges we are going to have this year:
* Altering the scoring so that the new declining-points system
* Getting more than just me, @jrenaut and @hozn to contribute
* Fixing a whole bunch of bugs we found last year
* Getting weather data back online after the demise of the Weather Underground API
* Getting distributed logging and more performance metrics back online
* Moving the system to a more robust hosting arrangement
-
@LhasaCM 195668 wrote:
There’s a 10 point bonus per ride day.
Sent from my SM-N975U1 using Tapatalk
I already figured that in, with the “base” total of 65 for the first ten miles, per the FAQ (see below). It seems like the scoring system is awarding one additional point for each mile, not one additional point for each mile over ten as described above.
Cheat Sheet for the Mathematically Challenged
Miles = Points
1 = 20
2 = 29
3 = 37
4 = 44
5 = 50
6 = 55
7 = 59
8 = 62
9 = 64
10 = 65
11 = 66…Take my current score of 196, covering two days of riding, total of 66 miles. 65 + 65 + 66 = 196.
Does any of this really matter? Maybe I should just go for a ride and forget about the forensic accounting.
@arlcxrider 195674 wrote:
Does any of this really matter? Maybe I should just go for a ride and forget about the forensic accounting.
The scoring system will get straightened out before it matters. Go ride.
@arlcxrider 195674 wrote:
I already figured that in, with the “base” total of 65 for the first ten miles, per the FAQ (see below). It seems like the scoring system is awarding one additional point for each mile, not one additional point for each mile over ten as described above.
Take my current score of 196, covering two days of riding, total of 66 miles. 65 + 65 + 66 = 196.
Does any of this really matter? Maybe I should just go for a ride and forget about the forensic accounting.
Yes – a bonus 10 points for you. All subject to change, and no, it doesn’t really matter.
- You must be logged in to reply to this topic.