Page MenuHomePhabricator

TEC13:O1.1:Q1 Goal - Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page)
Closed, DuplicatePublic

Description

Today the Developers/Maintainers page is the primary source of data for things that are deployed into production, including maintainers, code stewards, repositories, and phabricator projects. One of the challenges is that it is manually maintained and doesn't necessarily reflect what's deployed in the production environment.

This task is focused on investigating and proposing changes necessary to have a record of origin (authoritative source) for things deployed into production and any relevant information about those items.

Event Timeline

Jrbranaa renamed this task from Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page) to TEC13:O1:O1.1:Q1 Goal - Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page).Jul 10 2018, 5:24 PM
Jrbranaa renamed this task from TEC13:O1:O1.1:Q1 Goal - Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page) to TEC13:O1.1:Q1 Goal - Investigate and propose record of origin (ROO) for deployed code (currently Developers/Maintainers page).Jul 10 2018, 5:30 PM

After some initial thought and discussions regarding this goal, it seems that a closely coupled area of concerned is that of the Review Queue (the process by which extensions are reviewed prior to initial deployment).

As an authoritative source of what is in production, this list should be built from the output of the review process vs from what's in production at any given moment. This list can be used then by deployers to insure that what they've been asked to deploy has actually been fully reviewed.

To that end, I'm planning to spin up review queue work to help augment the current review process as well as support the creation and maintenance of the roo.