codefordenver / codefordenver/projects
transit desert map
- Dominant language
- No language data
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
[ ] pitched at code for denver
- [ ] The following has to be documented (briefly) in Code for Denver Google docs or on Waffle board card(s). The documentation can be slides, photos of white boards, documents, and/or one line answers to the criteria below, etc. Answers of Not Applicable (N/A) are acceptable. Shorter documentation is better than longer documentation.
- [ ] **Has to** fit C4D mission and vision (see below) https://docs.google.com/drawings/d/1k5xG6qdqwC0XFu2U5T2DhJtyXk13lh1hdsiIMUFVNNg/edit
(these need to be listed)
- [ ] Named Champion at Code for Denver
- [ ] Rough timeline
Description including
- [ ] What is it?
- [ ] Why is it needed?
- [ ] Why do you care (as champion)?
- [ ] Who does it help?
- [ ] What is the impact?
- [ ] Not something that has already been built
- [ ] Code of Denver has expertise or willing to build expertise
If partnered project,
- [ ] description of partner organization
- [ ] what will be provided by partner, what will be provided by Code for Denver
- [ ] Who is the stakeholder in the partner organization (name and contact info)
- [ ] What is mutual benefit (to partner and Code for Denver)?
- [ ] Passes "fist of 5 vote" at Code for Denver
Contributor guide
Assessment
This issue has not been assessed yet.