Skip to content

Consider adopting process and platform into the flutter/packages repository #130915

@stuartmorgan-g

Description

@stuartmorgan-g

Currently process, and its dependency platform, are hosted in individual google-org repositories, and published as "unverified uploader". The repos don't have any clear maintenance policy, contribution management, security stance, etc.

process is very heavily used in flutter/flutter; mostly tests, but also the tool. Given that, it seems like we should consider bringing them into flutter/packages so that they are managed, reviewed, published, etc. via our normal process. While they aren't Flutter-specific, flutter/packages seems like the natural place for them to live since we are maintaining them specifically for Flutter tooling. (We could move them into the google.dev publisher, but that only addresses the publisher permissions, not the maintenance aspects.)

[Edit: process is now google.dev rather than unverified]

Metadata

Metadata

Labels

P2Important issues not at the top of the work listpackageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions