Community Meeting Recap (7 June 2022)

Welcome!

Openverse is a search engine for openly-licensed media. It is both a website where you can search, discover, and learn how to use and attribute media, as well as an openly accessible REST API.

The OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org. team builds the Openverse Catalog, API, and front-end application, as well as integrations between Openverse and WordPress. Follow this site for updates and discussions on the project.

You can also come chat with us in #openverse on the Make WP Chat. We have a weekly developer chat at 15:00 UTC on Mondays.

If you’re a new contributor, welcome! Have a look at our good first issues or our guide for new contributors.

Meeting Start (in Slack)

Meeting End (in Slack)

Takeaways

Done

71 PRs merged over the two-week period
We continue to receive and merge contributions from people new to OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org.

In progress

Needs review

Discussions

We had two agenda items to discuss.

Data refresh / API latency issue

This is an ongoing production issue that is blocking new 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. deployments. The problem appears to be a marriage of our infrastructure and new code deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. as part of 2.5.3 (which was an aggregate deployment of 2.5.1, 2.5.2 and 2.5.3).

Madison shared some difficulties with trying to reproduce the issue in staging. We discussed trying to test in production, but due to the risks inherent with that approach, we agreed to continue trying to make staging have 1:1 to parity with production and to even deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. a new production stack in another AWS region to test against (or use as a live back-up in the case of needing to test in the currently live production).

Thumbnail field in catalog/API

We discussed ongoing work to clarify the ways we wish to store thumbnail URLs consumed by our thumbnail proxy. We will continue to follow the strategy of all “generated” secondary artifacts (thumbnails, waveforms, etc.) to be handled by microservices that are heavily cached using Cloudflare. Furthermore, we agreed to move the thumbnail URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for audio out of the main data.