Phabricator Project Organisation - Plasma

[Ben Cooksley]

Hi Plasma Folks,

The current structure of the Plasma project on Phabricator causes a
few issues with how we currently prefer to setup Herald rules. It also
means that people interested in subcommunities within Plasma aren't
able to selectively subscribe to those notifications.

This is because the majority of repositories are currently tagged with
the parent Plasma project - and parent projects inherit the membership
of their children. This means anyone subscribing to subprojects will
be notified of everything that happens in the Parent project.

This is why the KWin mailing list received all the Plasma reviews not
too long ago.

I also note that Plasma (as a collective effort, from my point of view
anyway) is related to or includes code which is currently located in
Extragear or Playground.

The easiest one from my perspective is to classify the Plasma:
Workspaces project as the "Release" project for Plasma (to match the
ones KDE Applications and Frameworks have) and retag all the
repositories which make up the release appropriately. A second
subproject would hold the tags for the other related repositories
which aren't part of the release.

Any comments, other suggestions?

Thanks,
Ben Cooksley
KDE Sysadmin