Openverse contributors discussed priorities for April in this meeting. View the full notes here and a summary below.
Meta discussion
We had some meta discussion about the project process and documentation:
- We discussed making addendums to project planning documents and created a new issue for handling such changes.
- We confirmed that we should create issues for implementation plans, and @zackkrida created a PR to update the project documentation with a reminder: Add documentation for creating implementation plan issues #2010
- It would be useful to update project thread issue bodies with the docs.openverse.org links for project plans and implementation plans after the PRs are merged. The generated docs are easier to read and will be up to date with any addendums. Issue created here.
- A question was raised by @olgabulat with regards to the consent decisionmaking process: How do proposal authors know that the clarification round is over?
- @aetherunbound suggested that the best heuristic is when all questions and comments from the assigned reviewers have been marked as “resolved” in the GitHub UI.
Finally, we discussed the fact that we didn’t feel like there was availability to start new projects this month. There was general consensus that we currently have too many open projects. This was primarily attributed to some smaller projects lingering. We speculate that this was related to much of the meta work that emerged from the monorepo move and our efforts to rapidly improve https://docs.openverse.org. Both valuable, but unaccounted for, efforts.
The approach we would like to take here is to continue working on open projects with the intention of closing as many of the smaller projects as possible. Some examples being:
- Core UI improvements
- Usage Analytics
- Search relevancy sandbox
- Popularity calculation optimizations
After that, we should be in a much better position to balance working on our larger initiatives and starting new projects at the same time.
At next month’s priorities meeting, if we do not feel that we made sufficient progress on closing open projects, we will begin to discuss taking action to adjust our expectations for the year, things like:
- Rescheduling projects
- Putting some projects on hold until 2024
Open Projects
We discussed open projects at length. Please, check out the notes for a description of each open project, but I’m going to pull out action items and highlights here:
- @olgabulat intends to share an update on the Data normalization #430 project explaining some dependencies/blockers for that work
- Regarding Usage Analytics #394, @olgabulat is working on the remaining launch events and I (@zackkrida) have created a discussion for addressing the opt-out user interface.
- Core user interface improvements #415
- Some buttons are still pending design work:
- Clear/Close buttons
- Audio play, “load more”, and the “content link” buttons
- We’ll expand the scope of the project a bit to include these button changes
- Action Item: @fcoveram will create a new issue for each button; add to the list of issues on the project thread
- @olgabulat confirmed that this small scope increase shouldn’t delay the project
- Some buttons are still pending design work:
- Filter and blur sensitive results by term matching #377
- Action Item: @dhruvkb will write: Implementation Plan: Blurring sensitive results · Issue #938
- Search relevancy sandbox #392
- @aetherunbound will start some development work on the staging DB portion of the project
- @krysal will write Implementation Plan: Staging Elasticsearch reindex DAGs for both potential index types #1987
- Sensitive Content Reporting Flow Guidelines #383
- @aetherunbound will write the Implementation Plan: Copy updates
mature->sensitive#1965 document - Folks are interested in contributing to this planning. Consensus that the plans cannot happen in serial and need to be parallelized by multiple authors. Felt that there would be more resources to devote to this, beyond the
mature => sensitivecopy changes, closer to the end of this month or next month.
- @aetherunbound will write the Implementation Plan: Copy updates