-
Notifications
You must be signed in to change notification settings - Fork 4
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
Roadmap discussion #11
Comments
30 Nov is the deadline for v1, right? The stuff listed there now is very achievable. Can I confirm that nice snapping tools for routes / areas are not needed in the next month? They're harder, so if they're necessary, I need to rejuggle other stuff |
I don't think snapping routes/areas is needed for v1. Could be good to have a development deployment for testing new features, and those are indeed really cool features that serve an important purpose by highlighting the direction of travel. But not needed for v1 IMO. |
Deployment for v1 is a great question. Are we rolling this out to a few authorities to test, or is this going to everyone in a month? If the latter, I would raise the standards and not just deploy to github. We can at least put a stable build on S3 or something (for literal cents in cost for our tiny scale). |
This is now largely captured in https://github.com/acteng/atip/milestones but worth keeping this open for any ideas/questions. |
I don't want to directly edit the v2 milestone that's there now because there's not really change tracking on it, so discussing here first. I would vote to strike I'd also like to defer undo/redo support; it's too complex to rush by May 1 and not as valuable as other things. Instead, I'd say we start trying out something real for #69. We could aim at least for very easy metrics (like speed limits) and add OSM amenities, categorized in whatever way Inspections finds useful. And a meta question: what's the source of truth for v2's scope? Is it issues tagged, https://github.com/acteng/atip/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2? Or the checklist at https://github.com/acteng/atip/milestone/2? Having both is confusing; can I remove the checklist from the milestone description? And maybe mention the intended audience of v2 is Inspections dogfooding things |
👍 to that, forgot about this place to discuss the roadmap and glad to see it being used. I think it will be good if we keep the top level summary more-or-less up-to-date and with links to issues. To that end I've created #116 which corresponds to one of those v2 bullets and will set it to v2 with a label. |
All open v2 issues now tracked in issue tracker. I've shifted the data layer one to v3 for now as it will take a long time to define/build/integrate them and not a priority, yet, although this is hugely important for the long term aim of making ATIP a one stop shop for active travel planning. So would be open to making this v2 again: #120 |
v1
This will be a small and simple open tool. The main purpose will be to generate quick and consistent geographic data representing planned area, route and crossing interventions. We could add another 'other' category of interventions but this has not been firmed up.
v2
To be developed when more developer time allocated to project. Focus will be on improving user experience and supporting good designs.
Below issues are just a sketch for discussion. See issues for the single source of truth on v2 roadmap: https://github.com/acteng/atip/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2 and source of truth on planned timeline: https://github.com/orgs/acteng/projects/1/views/1
v3
Collaboration possibilities are the key feature here. This stage represents a big step up in terms of scale of the project because of authentication issues.
v4
Think spelling autocorrect but for street design. The features here would discourage common mistakes in design and move towards auto-evaluation withing the platform.
v5
Advanced features that would require most time to develop.
Not decided
The text was updated successfully, but these errors were encountered: