Page MenuHomePhabricator

Phab PM: Document why not to only use team project tags but also codebase project tags
Closed, ResolvedPublic


I consider this an anti-pattern in public open source projects:

Teams sometimes get reorg'ed or disbanded or responsibilities shift, while codebases often remain active.
I haven't seen many teams spending time to sort and split all their open "team" tasks (across several code bases) when such reorgs happened, so tasks become an unhandable pile of misc things across code bases.

It is impossible to contribute to a project if there is no way to find the tasks for that project - it's not about some team's internal needs only, but also about allowing contribution from outside of teams.

Furthermore, codebase tags allow differentiation and communicating that your team does not plan to work on a specific task. In that case the team tag shouldn't be associated to a task, but the code project tag should remain.