Add myst variable substitutions for COLA values #170
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jdangerx
approved these changes
Jan 2, 2025
docs/policies.md
Outdated
| **For a more comprehensive example: [see this spreadsheet](https://docs.google.com/spreadsheets/d/1bwzw7_GcWNSTBNeUFrWe8BzEyIA2Cw7HnjEwg6TueiY/edit#gid=867743421)**. | ||
|
|
||
| **Expenses:** will be reimbursed on a month to month basis as they are incurred. They do not result in a potential future liability for the member (unlike asset purchases) since they’re being consumed continuously. This is meant to cover things like membership at a co-working space, improved home internet service for work purposes, an off-site backup service for your computer, enrollment in online courses for continuing education, etc. Monthly expense reimbursements to a member shall be limited to the total per-member reimbursement budget divided by the number of months in the rolling reimbursement period. Given the current limits of $3,300 every 36 months this works out to 2\*($3,300/36 mo) = **\$183.33/mo**. If a member has an expense greater than this amount, they can get reimbursed for it in installments over multiple months, so long as they remain a member. | ||
| **Expenses:** will be reimbursed on a month to month basis as they are incurred. They do not result in a potential future liability for the member (unlike asset purchases) since they’re being consumed continuously. This is meant to cover things like membership at a co-working space, improved home internet service for work purposes, an off-site backup service for your computer, enrollment in online courses for continuing education, etc. Monthly expense reimbursements to a member shall be limited to the total per-member reimbursement budget divided by the number of months in the rolling reimbursement period. Given the current limits of {{ tech_stipend }} every 36 months this works out to 2\*({{ tech_stipend }}/36 mo) = **\$183.33/mo**. If a member has an expense greater than this amount, they can get reimbursed for it in installments over multiple months, so long as they remain a member. |
Member
There was a problem hiding this comment.
Since this is being substituted using Jinja, we can calculate this $183.33 value too.
... to 2\*({{ tech_stipend }}/36 mo) = **\${{ (tech_stipend.replace('$', '') | float / 36 * 2) | round(2) }}/mo**.
Or, alternatively, we could make all the numbers in the dictionary actually numbers - and then format them with {{ "{:,}".format(var_name) }} instead of doing some parsing BS. I think that's probably the nicer way to handle this.
Contributor
Author
There was a problem hiding this comment.
Great idea! Just pushed the fix. I tried to create a custom Jinja filter to apply the formatting logic so but couldn't figure it out 🤷
bendnorman
commented
Feb 6, 2025
Comment on lines
+57
to
+66
| myst_substitutions = { | ||
| "healthcare_stipend": 175, | ||
| "tech_stipend": 3400, | ||
| "cat_meetup_stipend": 230, | ||
| "solo401k_match": 0.15, | ||
| "solo401k_employee_max": 23_500, # Update with info from this site: https://www.irs.gov/retirement-plans/one-participant-401k-plans | ||
| "solo401k_employee_max_over_50": 31_000, | ||
| "solo401k_total_max": 70_000, | ||
| "current_year": 2025, | ||
| } |
Contributor
Author
There was a problem hiding this comment.
The final inflation number was %2.9.
I grabbed the new Solo 401k numbers from here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add MyST variable substitutions for COLA values so it's easier to update the them each year.