Hypha Meeting: 2023 January 17

:tv: Google meet room: https://meet.google.com/nuq-pztb-asu

:writing_hand: Who will take notes? :raised_hands:
To take notes, all’s you got to do is make a riseup note pad here: https://pad.riseup.net/

Today’s Riseup Pad

Attending (initials only): DL, JM, GM, AR
Apologies (initials only): SM, FJ


:open_file_folder: Fredrik files https://github.com/HyphaApp/hypha/releases/tag/v3.6.0)

Di demo some of the new features and enhancements

:mountain_snow: What’s on the horizon?
Description: Learn more about new Hypha development

We have not taken out the website. Hypha will no longer be supporting the website by Spring 2023

:spiral_notepad: Adopter Field Notes
Description: We would love to hear any updates from current and potential adopters

  • icipe

  • wants to return to hypha implementation this year, and contribute code to the project soon

  • had questions to OTS/ARDC about log-in for user accounts, apply-side, and new feature or enhancement related to putting review form side-by-side with the application

  • OTS - how to make account creation is configurable because for some adopters the account is secondary while for others they prefer all users set up an account straight away

  • Open Tech Strategies (ARDC, etc.)

  • bug fixes and Wagtail upgrade

  • upstream user account creation and other features in the next release or two

  • download all applications as CSV

  • developing a UI for writing a determination side-by-side with the application

  • OTF working on end-user documentation for the project page and Wagtail Admin (form creation, publishing funds, etc.)

  • provided a demo of ALL communication channels within Hypha

  • in-app notifications

  • email digest and how to configure this in the Wagtail Admin via each Fund or Lab

:people_holding_hands: Community Enagement
Description: Events, documentation, communication updates

  • Adding the new Hypha logo and favicons. Will be implemented later on. (#3078) @frjo
  • Moved Hypha documentation in to the main repo (#3077) @theskumar
  • Updated the sandbox db. (#3076) @frjo


  • Overaching challenge this upcoming year to to ensure end-users could bolt all the pieces of an application/fund/grant together. In other words, make it easier for users to put together everything to launch a fund and keep track of it in a way that makes sense

  • major pain point is default messaging (template) is 1) difficult for adopters or end-users to customize.

  • Adopter/implementer is forced to strip every message out of the code and cut and paste new messages as needed

  • anything that is configurable for users SHOULD be configurable

  • Developers are able to access files with automated messages in a central location, but this information is not clear in documentation. In addition, the end-user or sys admin could not easily gain access to these text files or request revisions to these messages

Today’s Questions

  1. What is status of user account creation – could adopters start using?

  2. what is best to integrate with Hypha? zulip, slack, or another messaging tool

  3. Is the type face, fonts, colors on Apply configurable? There is an API for adopters. While it is currently NOT configurable, OTS is developing customizations to the Apply side with style templates. Examples: DDP Grants Application Platform | Incident Emergency Fund (IEF)

  4. Is accessibility a consideration when developing Hypha? Unfortunately, we do not have a process for including accessibility into each feature and enhancement we design and develop. However, in 2019 we’ve completed an audit and plan to conduct another audit in 2023. This audit informs our design and development process. There is potential collaboration among adopters working to implement accessibility improvements in the future.

Wife’s birthday so will not join but please see the latest Hypha release: