Readers/Structured Data

The Structured Data team in the Readers department at the Wikimedia Foundation builds features that use and allow creation of structured data associated with MediaWiki pages.

Projects
The team is currently focused on the Structured Data Across Wikimedia (SDAW) grant-funded program (also known as Machine-Readable Content Metadata). Previously, the team's main project (from August 2017 to Dec 2019) was Sructured Data on Commons.

Projects in the SDAW program include:


 * MediaSearch

We mostly work on the following extensions:
 * Wikibase MediaInfo
 * Upload Wizard
 * Machine Vision

Inactive and semi-active projects
Some members of the team were involved in development on these projects (when we were called the Multimedia team). They are not actively involved at the moment, but might be able to help if you have a question:
 * 3D file support
 * Media Viewer
 * FileAnnotations
 * Content Streams
 * Multimedia-related infrastructure (e.g. image scalers, video transcoding, etc.)

Team process/working agreements

 * We deliver features incrementally.
 * The Structured Data Backlog board is our primary backlog. It is managed by the Product Manager and Program Manager.
 * The Current Work board is for in-progress development. It is managed by the team as a whole.
 * Tickets are moved to the Ready for Estimation column when their design and acceptance criteria is complete and they are ready for work.
 * The team estimates the tickets in the Ready for Estimation column using t-shirt sizing.
 * Once estimated, tickets are moved to the Ready for Development column. By default, tickets are moved to the bottom of the Ready for Development column, unless they are urgent or high priority, in which case they go at the top.
 * When ready for new work, team each developer takes the top ticket from the Ready for Development column that is in their skill set.
 * If the acceptance criteria of a phab ticket change (for example as a result of discussion in the ticket's comments), the ticket description must be updated to reflect the change.

Code review
As a general guideline, developers ought to start the day with up an hour of code review.

When something is ready for review, add other devs as reviewers. If something is not ready for review, you ought to indicate that with a  tag or a

Chores

 * Readers/Structured_Data/Chore_list