Although I find @Dzahn's reasoning already convincing, I think it is worth a discussion.

Problems in production and problems in Labs are similar, but they are different, because the impact and the permissions to fix them differ. This is why i.e workboards in Labs looking ugly could be Low in Phabricator applying the same scale of priorities, but it could be Normal or High in a pure #Phabricator-Labs context. However, I can also totally see how having two different projects will only help to have a harder separation in our minds.

As long as we have pipelines of new users and new features, Phabricator Labs will be relevant. If we share this understanding, then we can keep Labs specific problems here, and from time to time a Labs problem might get a Normal-High priority if the current context deserves it.

We had a real precedent this week, when phab-01 would have JS problems hour before a demo with the mobile team. I commented in some task, and @mmodell acted upon quickly, but it would be more useful to have the phab-s better integrated here.

If there is agreement on this, we will include Phabricator Labs tasks here and we will not create any specific project.

How about having a project called 'labs', and then we can apply that project as well to similar tasks?

Phabricator projects + Labs tag sounds like a good solution indeed. It is kept within the Phabricator project, but then people focusing also in Labs can query these tasks specifically.

Wikimedia-Labs-General is coming, and we might want to edit that project and make it a plain "Labs" tag.

I will decline this task unless someone comes with better ideas.

Note that Bugzilla has a "Tool labs tools" product already which will get imported. If we had stayed with Bugzilla this would have ended up as a component under that product: https://bugzilla.wikimedia.org/describecomponents.cgi?product=Tool%20labs%20tools