2026 CTO Budget Amendment: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
Sky Nova <br> |
Sky Nova <br> |
||
Andrew Locke |
Andrew Locke |
||
== Vote Results == |
|||
| ⚫ | |||
| ⚫ | |||
== Background == |
|||
| ⚫ | |||
| ⚫ | We made a typo in the [[2026 Q2-Q4 Budget Vote|2026 Q2-Q4 budget vote]], and accidentally assigned the proposed CTO budget to Gen Ops. Separately, there was an additional cost related to the wiki migration that we didn't plan for. Details on the plans for the $12,200 can be found [https://docs.google.com/spreadsheets/d/1IIj6tO%20ENivaaQUWQSF2BK1DQO1RGuVSNRdqtm2-PA0/edit?gid=1093179814 here] |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | Authorize the board to spend up to an additional $13,200.00 to cover CTO expenditures for the fiscal year of 2026 beyond the previously approved $5,500.00 in the 2026 Q1 Area and Annual Critical Infrastructure budget. The board assigns this spending authority to the CTO. This spending authorization goes into effect upon passing of the vote and expires 12-31-2026. |
||
| ⚫ | |||
== Schedule == |
== Schedule == |
||
| Line 45: | Line 53: | ||
'''[3/24/2026]''' |
'''[3/24/2026]''' |
||
== |
== Vote Results == |
||
| ⚫ | |||
| ⚫ | We made a typo in the [[2026 Q2-Q4 Budget Vote|2026 Q2-Q4 budget vote]], and accidentally assigned the proposed CTO budget to Gen Ops. Separately, there was an additional cost related to the wiki migration that we didn't plan for. Details on the plans for the $12,200 can be found [https://docs.google.com/spreadsheets/d/1IIj6tO%20ENivaaQUWQSF2BK1DQO1RGuVSNRdqtm2-PA0/edit?gid=1093179814 here] |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | Authorize the board to spend up to an additional $13,200.00 to cover CTO expenditures for the fiscal year of 2026 beyond the previously approved $5,500.00 in the 2026 Q1 Area and Annual Critical Infrastructure budget. The board assigns this spending authority to the CTO. This spending authorization goes into effect upon passing of the vote and expires 12-31-2026. |
||
| ⚫ | |||
[[Category:Votes]] |
[[Category:Votes]] |
||
Revision as of 16:19, 13 March 2026
Title
2026 CTO Budget Amendment
Sponsor
Nick Hawley
Co-Sponsors
Sky Nova
Andrew Locke
Background
We made a typo in the 2026 Q2-Q4 budget vote, and accidentally assigned the proposed CTO budget to Gen Ops. Separately, there was an additional cost related to the wiki migration that we didn't plan for. Details on the plans for the $12,200 can be found here
Synopsis
This vote corrects the typo by revoking $12,200 from GenOps (leaving GenOps with $20,250.00 from the Q2-Q4 budget and $29,023.00 from the 2026 Q1 Area and Annual Critical Infrastructure budget), and grants authorization for that $12,200 to the CTO and adds an additional $1k to cover wiki fees.
Language of the Vote
Authorize the board to spend up to an additional $13,200.00 to cover CTO expenditures for the fiscal year of 2026 beyond the previously approved $5,500.00 in the 2026 Q1 Area and Annual Critical Infrastructure budget. The board assigns this spending authority to the CTO. This spending authorization goes into effect upon passing of the vote and expires 12-31-2026.
Revoke $12,200 of the spending authorization mistakenly granted to the General Operations team in the Q2-Q4 budget vote.
Schedule
Proposal Date
Date this proposal was posted to the membership and a request for a vote date was sent to the Board.
[3/13/2026]
Member Input
Does the Sponsor choose to open the language of the vote for changes due to member input? (optional and can be modified at any time)
[X] YES [ ] NO
Vote Announcement and Beginning Date of the Discussion Period
The announcement date of the vote proposal is the beginning date of the seven-day (minimum) posting and Member discussion period. (Certain exceptional vote types have longer discussion periods. Check the Bylaws if you are unsure.) If the Sponsor has chosen to include member input, suggested edits can be made in a shared document or other collaborative vehicle until the language is locked. The sponsor can stop taking suggestions at any time.
[3/13/2026]
Language Lock Date and Start of Voting
Five days prior to the Day of the Vote, the vote language is locked, all edits are frozen, and the language of the vote is converted to a pdf file. Ballots that include the pdf are sent to the Membership, and electronic voting begins. Note that the minimum discussion period of seven days leaves only two days for changes before the lock takes place.
[3/19/2026]
Day of the Vote
Date the Board has assigned for the vote. The Day of the Vote is the day the vote closes.
[3/24/2026]
Vote Results
Quorum:[ ] Yea Votes: [ ] Nay Votes: [ ] Present or Abstain: [ ]