Community Meeting Recap (Feb 22nd)

Announcements

• Next week’s meeting will be hosted by @stacimc, as we continue our hosting rotation amongst the sponsored OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org. developers.
• SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. was having an ongoing outage during the course of this meeting, which caused some delays in communication.

Takeaways

Done

• TSV loading is now performed at the end of provider APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. DAGs [ref]
• Audio waveforms are now cached in the API database after being computed [ref]
• Lots of movement on the frontend to remove dead code and general cleanup [ref]
• A new VLink component which will help wrap internal and external links [ref]
• Testing guidelines for the frontend! [ref]
• Browser back button now behaves as expected [ref]

In progress

• Numerous RFCs in need of review [ref]
  • 3D Model Support
  • Visual regression testing
  • UI state cookie
• A refactor of Media Services in the frontend [ref]
• Changes to catalog DAG timeouts and retries [ref]
• Improvements to E2E testing in the frontend [ref]
• Slack completion message after a provider API DAG completes [ref]
• Removing all external styles (some upcoming changes to this PR as well) [ref]
• Decoupling waveform generation from the API by moving it out into a separate service [ref]
• Native TypeScript support [ref]

Upcoming work

• Catalog milestone v1.1.0 is very near completion [ref], and v1.2.0 will be underway soon [ref]
• Improvements to automated accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) testing via Vuetensils [ref]
• A new RFC + milestone for application monitoring [ref]
• Some discussion around moving openverse-frontend into the openverse repository as the first step towards a monorepo [ref]

✨ That’s all for now ✨

#openverse-weekly-community-meeting

#openverse, #openverse-weekly-community-meeting