Rename
from | to | sub-project of | status |
---|---|---|---|
labs | Cloud-Services | {{done}} | |
Cloud-VPS | {{done}} | ||
Toolforge | {{done}} | ||
Tools | {{done}} | ||
{{done}} | |||
VPS-Projects | {{done}} | ||
{{done}} | |||
Create
- {{done}} Data-Services as sub-project of Cloud-Services
- {{done}} Cloud-VPS (Project-requests) as milestone of Cloud-VPS
Update
Archive
Implementation notes
- Making existing top level projects into sub-projects requires manipulation of the Phabricator database. @mmodell has said previously on irc that this is not a highly difficult operation.
- Sub-projects do not currently appear on the parent project's workboard. This is the topic of T11036 upstream and will probably be fixed someday when they get to it. If this is a really big deal we could look into how much they would want to implement the feature out of priority order. For now I don't think it is a big deal because the sub-project tasks will still show on a search for the parent project tag.
- Because of the introduction of parent-child relationships we will be able to remove {H28}
Open questions
- Should LabsDB-Auditor be renamed and placed somewhere in this hierarchy?
- Answer: No, this project is not currently used in the Foundation production network, so putting it under the Cloud-Services umbrella project would be confusing more than anything else.
Finished hierarchy
LabsDB-Auditor (?)
- ...
- ...