Maintainer’s Call 14th December 2021

🧑🏿‍🤝‍🧑🏻 Meetings Maintainers
1

Logistics

:calendar: 2021-12-14T14:00:00Z → 2021-12-14T14:50:00Z

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

  • If you’d like access, send a message to the @maintainers group.

Agenda

  • :writing_hand: - Who will take notes? :raised_hands:

  • :speaking_head: Anyone needs any specific time to discuss ongoing work?

    • Eriol: Re Rosy’s message in Zulip re. ‘organization’ level or similar will be helpful. It’s definitely on the feature list that we’d like to build out at some point, or another solution to the problem of having multiple people from the same org working on an application.’
    • Slammer: Log4j question

  • :file_cabinet: Fredrik files (review of recent releases , active dev tasks/bugs)

    • Add here

  • :couch_and_lamp: Adoptor Maintainer Corner *(if we have multiple adopters in the call please keep updates on adoptor specific features as brief as possible! :bowing_man: )

    • Discussion on automatically updated/submissions and settings we have discussed adding, where do we want them (Fund, Round, Form, Global?), do we even want more (for many users, having too many settings is overwhelming).
    • we.HyphaDiscussion post: Pending

  • :art: UX Design Corner

    • Add here

  • :notebook: Documentation Corner / What’s up docs? :carrot:

    • Add here

  • :triangular_ruler: PM Corner / Bow and Eriol :bow_and_arrow:

    • Wishlist process pending
    • Roadmap update pending

  • :business_suit_levitating: Any Other Business or ‘Proposals ongoing’

    • Add here

:page_facing_up: Notes

  • Put notes here

Maintainer’s Call 14th December 2021

GMT 13.00 - 13.50 // CET 14.00 - 14.50 // EST 09.00 - 09.50 // PST 06.00 - 06.50

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

Attending: Di, Fredrik, Eriol, Slammer, Bernard, Blah, Emily

Apologies:

Agenda

  • Anyone needs any specific time to discuss ongoing work?

  • Log4j vulnerability

  • Eriol: Re Rosy’s message in Zulip re. ‘organization’ level or similar will be helpful.

  • Fredrik files (review of recent releases , active dev tasks/bugs)

  • minor bug fixes

  • Release 1.75.0 https://github.com/HyphaApp/hypha/releases/tag/untagged-c4e03a113cf85232e0a6 still in draft

  • A few active security notifications that we haven’t fixed but they’re only on dev but not explosed on production

  • Hypha does not code in Java,only Python

  • Adoptor Maintainer Corner *(if we have multiple adopters in the call please keep updates on adoptor specific features as brief as possible!)

  • What is the maintainer’s response to the recent log4j vulnerability? How is this decision made?

  • Example of what we can do is to have a short blurb on how hypha users are affected or unaffected, include a link or post from an outside source.

  • Distinguish how this vulnerability would impact hypha core as oppose to other instances

  • Who will maintain or triage this post and comments/questions from the community?

  • Slammer and Eriol will draft the first blog post/blurb/verbiage for the Hypha website, and develop a long-term strategy or approach late: Update: we.post located here: https://we.hypha.app/t/pinned-security-vulnerability-concerns-with-other-technologies-that-may-or-may-not-impact-hypha-instances/222/2

  • BT: Here’s an example of how the log4j thingy has been discussed and handled by an infrastructure software product’s forum: Log4j and log4j2 library vulnerability | Cloudron Forum

  • Discussion about automation will be on the next adopter’s agenda

  • UX Design Corner

  • Documentation Corner / What’s up docs?

  • The stages of workflows are hard coded and we want docs to show from the PM pov what stages are involved.

  • AP: Emily is documenting this process for how this is currently expressed in Hypha test and also how they go about setting up their own process.

  • Can see py workflow here: hypha/workflow.py at main · HyphaApp/hypha · GitHub

  • AP: Eriol will do screenshots of the process for Emily’s docs

  • AP: Eriol will also set up calls with other adopters to see what flows they have in their systems in order to document

  • Examples of workflow states hypha/workflow.py at main · HyphaApp/hypha · GitHub

  • PM Corner / Bow and Eriol

  • Pre-poposal ahead of governance discussions: Voting process, Wish list’ or ‘triaging needs’

  • Currently how issues get prioritised is based on the primary adopters that founded the OSS Hypha product. Their needs are balanced with newer adopters that do not ‘invest’ in Hypha but are as equal(?) stakeholders in the adoption of the tool. The implementation of a voting or wishlist process for adopters that can be prompted on a timed basis (e.g. quarterly etc.) can help us to understand mutual features and collaboration opportunities or where adopters need diverge and resources need to be balanced or increased.

  • Goal: To build a balanced process for all adopters can participate in the improvement of the tool we create together. Equality and ways of balancing needs should be priority vs. prioritisation via investment amount

  • Outcome: A trial vote or wish list process that can be tested and improved over time.

  • Eriol has new proposal on Hypha Roadmap. Other adopters rely on this roadmap to plan their next dev priorities

  • Any Other Business or ‘Proposals ongoing’

on collaborative applications: As an applicant, ability to submit collaborative applications with multiple people/entities · Issue #177 · HyphaApp/hypha · GitHub

Best Practices:

  • Use the draft function to copy and paste applications questions into another document as plain text

  • Other “hacks” outside of Hypha like using a shared email, user account, etc.

  • Quadratic voting/shared application feature request from olden times

  • Use ‘Partner’ for multiple users to access a single submission in Hypha

2

Done! I’m sending the adopter meeting requests along with a 2022 ‘round up’ email today :slight_smile:

1 Like