2022 Roadmap

OpenverseOpenverse Openverse is a search engine for openly-licensed media, including photos, audio, and video. Openverse is also the name for the collection of related code repositories that make up the project. contributors have identified three primary user-facing goals for the year and others around infrastructure and stability improvements:

Goals

  1. Expand the uses of Openverse: We’ll get more users interacting directly with Openverse through our WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. integration, browser extensions, and other tools in the ecosystem, such as requiring Openverse images in the pattern and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. directories.
  2. Add new media types: We will add support for Video and 3D models in Openverse, giving users access to hundreds of millions of new openly-licensed media items to use and remix.
  3. Improve result quality and relevancy: Openverse will make significant improvements towards showcasing high-quality, relevant results, in order to increase adoption by new users and encourage existing users to come back.
  4. Infrastructure Improvements and Metrics: Openverse will make strides to improve the deployment story and ease of maintenance of the applications. We will add monitoring and alerts so that the current status of the system is never a mystery.

Top ↑

1. Expand the uses of Openverse

  • WordPress Core Integration [Q2] There’s a FSE Outreach program focused on media to get some community suggestions.
  • Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Community Development / Contributor Program [Q2] Not started yet
  • Media ProvenanceProvenance A term that comes from archival sciences, Provenance is the history of ownership and use of a creative work. For Openverse, this might mean the original uploader and url of a CC-licensed image, but also the history of urls where the image has been displayed; or a record of remixes/community edits of the image. & Creator Micropayments [Q4] Under discussion
  • User Research Sessions [Q2] Not started yet

Top ↑

2. Add new media types

  • 3D model support [Q2] Under discussion, frontend RFC here, issue here
  • Video support [Q3] Not started yet

Top ↑

3. Improve result quality and relevancy

  • Explore existing Rekognition data from Creative Commons [Q2-Q4] Not started
  • Refine/expand popularity metric acquisition & calculation [Q4] Not started
  • Use image resolution and other metadata to improve relevancy [Q3] Not started
  • Reduce visually similar / ‘identical’ results [Q1] Not started
  • Translate search queries to improve localized search results [Q3-Q4] Not started
  • Explore using an automated method for flagging images/audio [Q4] Not started

Top ↑

4. Infrastructure Improvements and Metrics

  • Automated infrastructure deployments [Q1] Implemented on the front-end, not yet deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.. Other modules need to be planned.
  • Restore the Common Crawl pipeline to ingest images from CC providers [Q3] Not started
  • Implement monitoring, tracking, logging and reporting of the whole stack [Q1-Q2] In progress, Sentry has been implemented for the 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. and front-end.
  • Internal quality assessments, user metrics, and data introspection [Q2-Q3] Not started

Last updated: