-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WFRC bikeways map - phase 2 #371
Labels
paying
This issue earns $$
Comments
nathankota
changed the title
WFRC bikeways map - next steps
WFRC bikeways map - phase 2
Mar 26, 2024
nathankota
added
the
carried forward
This task was carried forward into the next quarter
label
Jun 3, 2024
stdavis
added
paying
This issue earns $$
and removed
carried forward
This task was carried forward into the next quarter
labels
Sep 9, 2024
Questions:
|
stdavis
added
the
status: blocked
This issue or pull request has an unmet prerequisite
label
Jan 21, 2025
I have a meeting with Bert on Friday at 11:15. Let me know if you want to
join.
…On Tue, Jan 21, 2025 at 11:19 AM Scott Davis ***@***.***> wrote:
@leault <https://github.com/leault> Have you been able to make any
headway with Bert about these questions above? Maybe @eneemann
<https://github.com/eneemann> has thoughts about the question about us
hosting the data? I don't feel like I can do much more work on this project
until we sort out the direction for this app.
—
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BK3H5GDBZC4W4IX32KQQJFD2L2FTPAVCNFSM6AAAAABFJQPSICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBVGQ2DANZRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
FY25 Q3 Sprint 2
|
chriswnek
removed
the
status: blocked
This issue or pull request has an unmet prerequisite
label
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefit
Acceptance Criteria
Notes
We have around 200 hours (PRJTASK0614068) (as of 12/23/24) on their general technical service contract left for this FY.
Risks
The text was updated successfully, but these errors were encountered: