Where should compositor and window manger groups be created?

[StudebakerGuy]

Compositors and window mangers are in various locations.

We have some groups like Graphical desktop/GNOME. Then we also have Hyprland at the root level.

[vuatech]

On the merge request I was thinking about about separating Graphical Desktop and application that belong to those desktops into subgroups then doing the same with Window Managers. My thought process is that someone on KDE will never need a wallpaper manager while subgroup of Window Manager could be utilities

[StudebakerGuy]

To clearify, you are considering graphical desktops the complete enviroment like gnome, KDE, or cosmic. You would then consider window mangers something like hyprland or awsome. Is that correct?

While I don't disagree with seperating the packages like this, I'm not sure the typical user would draw that disticntion or not? Of course, Hyprland is quickly heading towards a graphical desktop. There seems to be a new hypr whatever every month or so.

Should we solicate opions from more typical users on this?

[vuatech]

When looking at a complete environment I see many of those have a desktop shell or bar and a full host of utilities (one stop shop). Hyprland is not at that stage and I do not believe the developer is interested in providing a host of graphical utilities to cover every individual function. Besides the systeminfo (displays info only) and hyprpolkitagent packages, there is not a single gui utility (hyprgui is not official) that specifically gives configuration ability. He is very much in the "read the doc" mentality. I find that a lot of window managers share very similar view point.

It wouldn't mind getting outside opinions as they will be the people the groups are for.

[vuatech]

If you want to squeeze them in to the Graphical Desktop, I don't see an issue. I figured separating them would possibly lead someone unfamiliar with WM to google "what is a windows manager" then either say "neat" or "hell no"

[StudebakerGuy]

For me, it doesn't make much difference. I'm just trying to guess at how others might. For now, I say leave it how you have it. We can then raise the issue with the largerger group before we start make changes to packages. Does that seem reasonable?

[vuatech]

That is good, it would be good to have a wiki ready to be launched before we start the package changes also. I imagine all groups will be reviewed during that process to make things are understandable for new/current package maintainers.