Merged PRs
API 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.
- #4229: Add management command to send api move announcement email
- #4249: Cache repeated thumbnail failures within configured TTL
- #4250: Update `openverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org.-attribution` with new features and improvements
- #4254: Alter Django Admin media views to surface content reports
- #4263: Add structured logging for the API
- #4267: Run checks for Python packages in CI
- #4274: Publish changelog for api-2024.05.06.19.44.35
- #4278: Tag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. API images with PDM content hash
- #4280: Expose provider in the API tags response
- #4281: Fix send email query
- #4287: Publish changelog for api-2024.05.07.23.56.36
- #4288: Remove sendapimoveannouncement management command
- #4292: Ignore `django-structlog` middleware logs in Sentry
Catalog
- #4260: Rename old data refresh to `legacy_data_refresh`
- #4276: Update Science museum urls
Documentation
- #4231: Initialize Provider store data, UI UI is an acronym for User Interface – the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. store and flags store from cookies in a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
- #4235: Convert `.stories.mdx` to `stories.js` for compatibility with Storybook v.8
- #4266: Migrate documentation to PDM
- #4296: Fix links to frontend unhealthy host alarms and move PRs template
Frontend
- #4231: Initialize Provider store data, UI store and flags store from cookies in a plugin
- #4235: Convert `.stories.mdx` to `stories.js` for compatibility with Storybook v.8
- #4265: Add storybook smoke test
- #4272: Storybook test changes to prevent flakiness from `sleep`
- #4283: Replace sample secret key for plausible with a more obviously safe value
- #4284: Publish changelog for frontend-2024.05.07.16.44.22
- #4294: Update pnpm
- #4299: Update Node to v.20
Ingestion Server
- #4307: Publish changelog for ingestion_server-2024.05.10.03.01.22
Management
- #4264: Bump tqdm from 4.64.0 to 4.66.3 in /utilities/dead_links
- #4267: Run checks for Python packages in CI
- #4271: Bump jinja2 from 3.1.3 to 3.1.4 in /utilities/project_planning
- #4277: Give up Pipenv cache to fix CI
- #4285: Make API image smaller by not including dev dependencies
Closed issues
API
- #1008: Reduce size of API production image
- #3432: API structured logging
- #3635: Create new content report Django admin table view
- #3742: Write and run management command to send email notifying registered API users of the new `api.openverse.org` domain
- #4024: Write docstrings to document API fields
- #4167: Run CI tests for Python sub-packages
- #4273: Expose provider information in the tags
Catalog
- #1488: XCOM pull shorthand function
- #3847: Add variable to disable removing SQL source files for ingestion workflows
- #4261: Some Science Museum records continue to have invalid URLs
Documentation
- #4038: Implementation Plan: Determine and design how machine-generated tags will be displayed/conveyed in the API
- #4138: Move “Contributing to Openverse” docs section to “General development guidelines” header The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.
Frontend
- #2219: Storybook smoke test does not catch if individual stories are broken
- #4217: Replace the sample string in a secret with a more obviously safe value
- #4230: Remove the `ssrRef` from provider store
- #4234: Convert Storybook stories to `stories.js` CSF format
Ingestion Server
- #1008: Reduce size of API production image
Management
- #777: Collect documentation inside Sphinx
- #3743: Write and publish Make post announcing switch to openverse.org for the API
- #4167: Run CI tests for Python sub-packages
Merged PRs
Frontend
- #877: Bypass caching on static frontend routes when cookies are present
Infra
- #866: Add golden image Packer build
- #871: Create indexer worker pools
- #876: Point UptimeRobot to api.openverse.org; use .org as canonical API domain; redirect .engineering API requests when header is present
- #881: Add TENCENT ASN to malicious list
- #885: Fix nuxt-preview deployment dispatch type
Ingestion Server
- #883: Grant permissions over catalog S3 bucket to the ingestion server
Management
- #882: Add script for running API management command
Closed issues
API
- #550: Thumbnail error responses not cached, even if we know they’re going to fail
Infra
- #585: Add workflow for running one-off ECS tasks
- #780: Update UptimeRobot monitors to point to `api.openverse.org`
- #843: Combine best of autoscaling group launch templates with Ansible
Management
- #585: Add workflow for running one-off ECS tasks
#openverse, #week-in-openverse