-
Notifications
You must be signed in to change notification settings - Fork 38
Hypha development plan for 2023–2024
Fredrik Jonsson edited this page Nov 7, 2023
·
2 revisions
The main areas of work are:
- Long term maintenance. This is a permanent need to keep Hypha working and running securely.
- Submission side where applications are received and evaluated.
- Project side where contracts, invoices and reports are processed for approved application.
- Global functions like authentication, dashboard, tasks and notifications.
- Bug fixes, this falls under each of the above areas but can also be viewed as its own area.
- Hypha community. There are a number of organisations that use Hypha today. Some actively contribute new features as well as bug fixes.
This is ongoing and never ending work to keep the packages Hypha is built with updated.
This work is important for two reasons:
- We benefit from the improvements and new features added to packages. Especially true for core packages like Django and Wagtail.
- Keep Hypha secure by running versions that get security updates.
We are right now working on getting Hypha to Django 4 and Wagtail 5. The version that includes them will by Hypha v5.x.
We can count bug fixes under this area as well.
- n/a
- n/a
- Rework the pages and tables that list funds/labs/rounds/submissions/reviews/determinations etc. This is the result of the UX research done via interviews with PM:s as well as analytic data collected.
- Allow applicants to preview submissions before submitting.
- Allow staff to view submission/reviews while writing comments.
- Implement the design/UX ideas from the new project side to submissions where it fits.
- Overall UX improvements based on best practices, feedback and research.
- Allow staff to revert approved/dismissed states as well as invite for proposal state. Or add features to help staff make fewer mistakes.
- Replace Rich text editor field with Markdown throughout. Improve security, allow for autosave etc. Need a function to allow applicants to paste in from Word etc. and get it all converted to Markdown with tables etc. intact.
- Revamped version of the projects, built according to OTF requirements. With the help of strategic settings we believe it is suitable for other organisations as well.
- Doing reports as stream field forms so each organisation can add whatever fields they need to reports. It will be possible to use different report forms on a per fund/lab basis.
- Rework the pages and tables that list projects/reports/invoices etc. This is the result of the UX research done via interviews with PM:s as well as analytic data collected.
- When the new project features get used in production we expect a flow of bug reports and improvement requests.
- n/a
- Implement passwordless authentication with e-mail verification before submitting an submission.
- Implement a global task list that displays on each users dashboard informing them what tasks they need to do.
- Remove the public part of Hypha. This will simplify Hypha code base considerably.
- Make all notifications use e-mail as a default. Organisations can then opt in on using e.g. Slack as well. Users should have the option to turn e-mail notifications on/off.