Openverse is a search engine for openly-licensed media.
The OpenverseOpenverseOpenverse 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, APIAPIAn 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 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.
During the meeting we follow along our GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ backlog board, looking at ‘done’, ‘in progress’, and ‘completed’ work. In fourth and final part of the meeting, we review any open agenda items. This should be handled as efficiently as possible with an emphasis on unblocking ongoing work and scheduling new work.
Each item here has an approximate timestamp and duration. This guide assumes the meeting starts at 15:00 UTC. The actual time may differ based on the time of year. Follow these time guidelines as best as you can; some of the most critical parts of the process happen toward the end of the meeting! Note that just even though the facilitator moves on and starts the next section, contributors can still participate in earlier conversations and threads as-needed.
[15:00-15:05] Done column on the Project board. Ask contributors to highlight recently-completed work! Sharing this work keeps everyone informed about recent successes and helps others share their pride in their work. If there’s not much activity, you can either breeze past this information or choose some items you’re excited by to share. Items should be posted as standalone messages, not as part of a thread, so that a thread can be created per-item if any discussion is needed. These issues in the “Done” column should be archived in GitHub after the discussion. See above for what the GitHub UI looks like to archive the cards.
[15:05-15:15]In progress column on the project board. Ask contributors to share any blockers on their current work or work that is ready for PR review. There’s typically deep technical conversation here, with long threads to discuss the implementation of various features.
Use this view to see PRs needing review, sorted from oldest to newest.
[15:15 – 15:30] To Do / Backlog. Here, ask the community to share issues they would like to work on; or issues they think are important to get assigned. This view is useful for seeing in progress tasks by assignee.
Additionally (in particular for high-priority issues) ask meeting participants to review the list and confirm the priority of issues, especially high-priority issues that are older than two weeks.
[15:30 – 15:45] Address any items in the agenda, recently opened discussions, and ask if anyone has something else to comment or ask that did not have a place in the previous points. If a resolution or decision was reached on an agenda item (e.g. an issue was assigned), please denote the result on the agenda (example from 2022-09-20).
At the end of the meeting, it’s common to send a message containing </meeting>, along with however you’d like to say goodbye.
Suggestions and advice for running the meeting smoothly.
If new issues, bugs, or problems come up in conversation, encourage contributors to create a new issue. Contributors will often react to the issue request with an emoji, like a checkmark, once they’ve made the issue.
It’s really common for contributors to conduct code reviews for each other during the meeting. You might see a lot of PRs changing status rapidly.
Feel free to @ contributors directly if you have specific questions about their work, need a PR review from them, or other concerns.
After the meeting, a recap post should be posted to make.wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//openverse. The recap post should have the link to the first and the last Slack messages of the meeting, and a recap of the Agenda discussions (if any). Here are examples. It is easiest to duplicate a past recap post using the “New Draft” button and fill in the new information. The Site AdminURLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org can be useful for this.