Members of the Openverse 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. find Openverse at https://openverse.org. community met over video and audio today to discuss Openverse priorities for the month of October. We discussed three major things (you can read the raw notes here):
- Status updates of current projects
- What we’ll be working on this month
- New projects we’re excited to start
The need for better project documentation
One of the first things we mentioned was the need for deeper project documentation in Make. There isn’t one easy place to view current projects at a glance. @beccawidom mentioned how useful the Dag Status page is and how it could be a good model for a projects page.
The project is ongoing and progressing quickly. Development is well underway and can be viewed on the staging site with the
?ff_new_header=on flag enabled. Here is an example link.
@olgabulat completed the mobile version of the ‘recent searches’ feature today. There are a few open PRs in need of review:
and more needing to be started:
Provider DAG Refactors
This project is also ongoing and advancing nicely. The tracking milestone has the latest updates and assignments. The project continues to reveal issues with existing DAGs, from faulty logic, to unhandled errors, to data integrity concerns.
There’s ongoing work to switch to a single load balancer for all applications.
Browse and Insert Openverse Media in WP Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
This project began serendipitously from a community PR to add Openverse browsing to Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. Since then there’s been more discussion and some designs created.
We talked about this project a lot and decided we should devote time to planning this month. @krysal plans to share a draft of a plan to help clarify the scope and goals of the work.
We discussed how the iFrame removal project won’t have much active development work in the coming weeks, so it would be a good time to start planning for other projects. We identified two:
- The session state cookie milestone would be great to prevent 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. pop-in and for future storage of user state.
- @zackkrida also wants to start Analytics and will kick off the project with an RFC for frontend event collection.
We also discussed the Content Safety project at length. It’s very important work but we don’t have a clear lead for that project yet. As @aetherunbound mentioned, it would be worthwhile and possible this month to start scoping out this project. Examples Madison gave are to gather and create issues, and write an RFC for the project.
Finally, we decided on some next steps to keep work moving.
- @krysal: Share a draft of the Data Normalization plan
- @aetherunbound: Create a new DAG Stability and Bugfixes project and kickoff post
- @zackkrida: Create a new Analytics project
- @zackkrida: Write a frontend event collection (analytics) RFC
- @zackkrida: Create and RFC request for handling removed images/dead links
- All: Identify a lead for the Content Safety project