-
Notifications
You must be signed in to change notification settings - Fork 38
Roadmap
Below is are the projects objectives by time first and then by theme.
Approx. next month
See progress by reviewing priority tickets for the current milestone (2019-Q3) and/or todo list on the main project board.
From priority tickets within the current milestone (2019-Q3 +priority)
- Complete discovery and scoping for summer sprints
- Creation of summer sprint tickets that focus on post approval workflows (project approval forms, contracting, payment requests, and regular project reporting)
- Deploy API access for both users and projects
- Deploy ability for staff to apply labels to submissions (meta)
- Deploy first set of automation functions
- Performance and bug fixes always
From non-priority tickets in the current milestone (2019-Q3 -priority)
- Harmonize the viability definitions and implement the same options for comments, reviews, and submissions
- Introduce an optional survey for applicants to complete post final-determination
- Allow users the ability to see and set their notification preferences in their profile
- Expose useful meta-data (avg amount approved, type of project, etc) from the API on internal and external pages (ie round and fund pages)
- Improve the listing of projects, fellows, and other results on the public facing pages
- Begin offering the ability to associate a Signal number to receive and respond to notifications
- Ability for users to submit bug or feature requests from within the app or on error pages
- What could the API/metadata inform us about current and future programming?
- What can we infer and what can we deduct from information we have at hand? Do we have complete picture and what are the gaps?
Approx. next 3 months
Items from the current milestone (2019-Q3) not included above or from the approaching milestone (2019-Q4).
[todo, need to move items from above down here as is right and go through later milestone and creating high-level summaries]
- Introduce and test post approval features such as PAF, invoice, monthly report, creation/management
- Review and refine as needed the current responsible data policy
- Conduct a responsible data audit
- Change the repo name to an standalone project/app name and release a website highlighting the app itself
- Create a security information page outlining the security/privacy features of the app along with our ongoing guidelines for future features
- What are tangible outcomes from having better access to submission information? What materials do we need to meet objectives? Do we have sufficient capacity to implement activities?
- What further internal or external UX/UI exploratory sessions should we conduct and how best to share feedback with team, applicants, and the public?
- What additional information and communication do applicants need (ie guidance, messages/comms) and how do we improve our ongoing feedback loop with them?
Approx. next 6 months
Items not above from the next two or three milestones.
[todo, still need to go through these milestones to create high-level summaries like above]
- Should we import all the manually created PAF's into the app for a PAF central database?
- What additional tools or resources do for applicants to navigate various funds, see #697?
- Training and how-to materials for external stakeholders
Approx. next 12 months
Items not above from the next three or four milestones.
[todo, still need to go through these milestones to create high-level summaries like above]
- What are our goals one year from now?
The Following Progress page outlines how one can observe, watch, or follow the progress towards the above goals.