# Hypha Meeting: 2022 June 7th **URL:** \ **Category:** Maintainers\ **Created:** [June 5, 2022, 5:21pm UTC](https://we.hypha.app/t/hypha-meeting-2022-june-7th/366 "2022-06-05T17:21:53Z")\ **Posts on this page:** 4\ **Page:** 1

**Author:** ![dluong](https://yyz2.discourse-cdn.com/flex036/user_avatar/we.hypha.app/dluong/32/22_2.png) [@dluong](https://we.hypha.app/u/dluong)\ **Post date:** [June 5, 2022, 5:21pm UTC](https://we.hypha.app/t/hypha-meeting-2022-june-7th/366/1 "2022-06-05T17:21:53Z")

Hypha Meeting: 2022 June 7th CET 15.00 // EST 9 // PST 8 Google meet room: [https://meet.google.com/bnj-yvrx-ybn](https://meet.google.com/bnj-yvrx-ybn) Or dial: ‪(GB) +44 20 3873 3170‬ PIN: ‪466 905 402 5442‬# More phone numbers: [https://tel.meet/bnj-yvrx-ybn?pin=4669054025442](https://tel.meet/bnj-yvrx-ybn?pin=4669054025442) 🖊 Notes: [Riseup Pad](https://pad.riseup.net/p/8qybREpPLiXQ2yi7GDqu) Attending: Apologies: Latest Adopter digest: [Adopters Newsletter #2 Q2 2022 · HyphaApp/hypha Wiki · GitHub](https://github.com/HyphaApp/hypha/wiki/Adopters-Newsletter-%232-Q2-2022) - Please add your updates directly to the newsletter or share updates here Agenda Does anyone needs any specific time to discuss ongoing work? Fredrik files (review of recent releases ([Releases · HyphaApp/hypha · GitHub](https://github.com/HyphaApp/hypha/releases)) active dev tasks/bugs) - Revamping password reset password - bug fix: draft applications show up in some circumstances, but it has been taken care of now - increased usability of 2FA setup workflow 🏔 What’s on the horizon? _Description: Learn more about new Hypha development_ ARDC/Open Tech Strategies Scoping Review: > > > \*\*Is your feature request related to a problem? Please describe.\*\* > > We have a …few (known) places where the universal lack of underlines in links is causing confusion. The first is in the footer text -- if the site is configured with a link that link has no indication it is clickable. For instance in this screenshot "Giving" is a link but you would never know: > > \

> > \*\*Is your feature request related to an existing functionality? Please describe.\*\* > > There are existing links across Hypha that appear the same as non-link text; this applies to all of them. > > \*\*Describe the solution you'd like\*\* > > A lot of links in Hypha would be more legible with an underline. For instance clickable elements in the submissions table, and even in-page navigation such as "Show All". > > Might we consider making underline the default for all links and explicitly removing the underline for \`.button\` based links (e.g. the log out button) > > \*\*Describe alternatives you've considered\*\* > > Color alone doesn't do the trick since (A) not everybody can see color and also (B) the blue is used in other places on non-clickable text. > > We could instead apply underline just to identified concern points, but I'm worried that will create inconsistency. > > \*\*Priority\*\* > > \- Medium (slowing you down) > > \*\*Affected roles\*\* > > \- Staff > \- Applicants > \- Reviewers > \- Partners > \- General public > > \*\*Ideal deadline\*\* > > We'll make this change locally on our own timeline, so no major urgency. > > > \*\*Is your feature request related to a problem? Please describe.\*\* > > ARDC wants… to link to documentation from the text above their application form fields, but the documentation is not in the form of a help guide, so they want to control which words are linked in the help text. Sometimes there are multiple links. > > \*\*Is your feature request related to an existing functionality? Please describe.\*\* > > Application form fields can define help text and a separate link to a "help guide." This would allow links on arbitrary text as opposed to a separate link. > > \*\*Describe the solution you'd like\*\* > > To do this, I changed the help text to a rich text field and controversially did away with the separate help guide link: > > \ Screen Shot 2022-06-06 at 1 36 27 PM

> > \

> > \*\*Describe alternatives you've considered\*\* > > ARDC could learn to love the separate link approach and we could rename that link to something other than "help guide" with a locale. > > \*\*Additional context\*\* > > I have a patch for this. > > \*\*Priority\*\* > > \- Medium (slowing you down) > > \*\*Affected roles\*\* > > \- Staff > \- Applicants > > \*\*Ideal deadline\*\* > > No deadline. > > > \*\*Describe the bug\*\* > > The "Roles" > > \*\*To Reproduce\*\* > > Go to edit a user's …"Roles" -- the checkbox labels are not aligned with the checkboxes. > > \*\*Expected behavior\*\* > > The labels should appear next to checkboxes. > > \*\*Priority\*\* > > \- Low priority (annoying, would be nice to not see) > > \*\*Affected roles\*\* > > \- Staff > > \*\*Screenshots\*\* > > \

> > \*\*Desktop (please complete the following information):\*\* > - OS: MacOS 12.4 > - Browser: Firefox > > \*\*Additional context\*\* > > In order to fix this in Hypha we need to add a hook to wagtail admin to load custom CSS on admin pages. > > From there I want to note that simply adding float left to the checkbox doesn't do the full trick because of the way Wagtail checkboxes are rendered in Fun and Exciting ways. In particular they used a \`-5px\` top which messes with vertical alignment. That has \[since been changed\](https://github.com/wagtail/wagtail/commit/5996c5dd29200090948edefafa825c4b7ac43f5a#diff-e1bd478fcf7bc69d113aabd3a6a1cb0e3294cb6bd28aba916f8c21a9c7f9be47L199) though there is still a 2px \`top\` which might still cause a pixel of net awkwardness. > > I'll have a PR for this soon. - WISYWIG potentially presents errors for many users Potentially update WagTail in the future to version 3, waiting for LTS OTF’s Communication Month! - Email as default for users to select communication preferences (ie email, slackc, signal, zulip, etc.) - MVP in-app notification for users beyond slack - Inbuilt solution within Hypha for messages to Slack, Zulip (contributed by ARDC/Open Tech Strategies), Signal, etc. 🧑‍🤝‍🧑 Community Enagement _Description: Events, documentation, communication updates_ - Documentation - ARDC will start to use fully in July, would like to contribute documentation, in particular for system admin (yay!!!) - **Move Tuesday meetings to 9am PST/11am CDT/12pm EST/18:00 CEST?** - We will table moving the time, keeping it at 8am CDT/9am EST - Adopters prefer to attend meetings to engage with other platform users, less focus on development and other technical aspects of the platform - OTF creating new training curriculum for staff to troubleshoot applicant questions about Hypha (ie 2FA setup, password reset) - Hypha summit (more discussions over the next few months to gauge from adopters on their preferences) 🗞 Adopter/Maintainer News _Description_: _We would love to hear any updates from current and potential adopters_ - Small screen testing and issues with filters that could be fixed - Accessibility issues - Improvements to default columns on submissions page (ie Round, Reviews, etc.) that do not align with ARDC’s needs. - Completed/Assigned in column makes more sense to ARDC users - Moving to GitHub for more visability - Zulip integration - Improvements to UX – look forward to great feedback soon! - Help text in particular settings because WagTail is current vague 💡 Ideation _Description: New designs, wireframes, work in progress to share_ Any Other Business or ‘Proposals ongoing’ ---

**Author:** ![jimmcgowan](https://yyz2.discourse-cdn.com/flex036/user_avatar/we.hypha.app/jimmcgowan/32/156_2.png) [@jimmcgowan](https://we.hypha.app/u/jimmcgowan)\ **Post date:** [June 6, 2022, 2:49pm UTC](https://we.hypha.app/t/hypha-meeting-2022-june-7th/366/2 "2022-06-06T14:49:54Z")

A 15:30 GMT meeting start will be at 08:30 CDT / 06:30 PDT. ---

**Author:** ![dluong](https://yyz2.discourse-cdn.com/flex036/user_avatar/we.hypha.app/dluong/32/22_2.png) [@dluong](https://we.hypha.app/u/dluong)\ **Post date:** [June 6, 2022, 3:25pm UTC](https://we.hypha.app/t/hypha-meeting-2022-june-7th/366/3 "2022-06-06T15:25:03Z")

Hi @jimmcgowan I’m sorry for the confusion. The meeting starts at 8 CDT/9 EST every other week on Tuesdays for now. We may change this time relatively soon to accommodate West Coast hours. Best, Di ---

**Author:** ![system](https://canada1.discourse-cdn.com/flex036/uploads/hypha/original/1X/dc5b9c3ca4a0ab281b6df04a91c48eb8e8b6af02.png) [@system](https://we.hypha.app/u/system)\ **Post date:** [June 20, 2022, 6:00am UTC](https://we.hypha.app/t/hypha-meeting-2022-june-7th/366/4 "2022-06-20T06:00:09Z")