T76375: [DO NOT USE] New Labs project requests (tracking) [superseded by #cloud-vps-project-requests] should be replaced with a project.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T128300 Create custom Phab form for requesting a new Cloud-VPS project | |||
Resolved | bd808 | T136910 Replace tracking bug T76375 by new project "Labs Project Requests" |
Event Timeline
Definitivly not of Toolforge. I would propose a subproject of Cloud-Services. Other opinions?
A sub-project of Cloud-Services seems reasonable to me. I'd differ to @chasemp, @Andrew, and @yuvipanda as the ultimate deciders.
The important thing to understand about subprojects is that they have members, and parent projects do not. So the membership of parent projects is the union of all subproject membership.
That isn't really needed for this because essentially labs-project-requests will be used as a tag, not as a group.
So a standalone project is appropriate in this case.
Actually, upon further consideration, I think the most appropriate choice would be a milestone of labs - milestones get a column on the parent project's workboard and milestones to not have members.