@graesslin I propose this goal, IMO tiling window managers going to be more popular and used, having it, can attract some number of users to Plasma/KDE. Currently there are not many Wayland tiling wm, supporting it can be key in transition from X to Wayland. My intention with this goal is to define full-scale system, not to just list bunch of nice tiling features. I am not developer and I don't unterstand underlying system of KWin, so I meant that is possible to extend KWin with complete tiling, but from your words that is practically impossible. Your sugesstion to create new manager (KWin compatible), seems more realistic, but the problem is maintaining it compatible with upstream, similar problems with Kwin scripts.
Many of us dream of those features, to be integral and easy accessible under Plasma. From this conversation, I don't see any elegant solution to this goal. I'm just Plasma user, I would like to this goal be achieved, but I understand that is not that cricital, important or valuable.

@mart yes it is big goal, but it is solvable in step, bigest problem I see which make this complicated is X11/Wayland cross-support. But having nice Wayland tiling support can be great feature becouse currently there is not many tiling wm for Wayland, and be leader in that can be key in X11 to Wayland transition

If 'KDE is All About the Apps', do better incubation of third party applications is part of this goal? Making KDE more attractive and easier to third party applications developers, and how to KDE be more progressive to identify and approach good project to be part of KDE.

@jrioux Renaming anything is controversial task, and it is hard to have consensus how solve it, because renaming in start make users more confusing, but in long term can be correct. My suggestion is to rename KOrganizer to Kalendar, but I am not sure that everybody agree with my suggestion. And in the end, application name is important, but functionality is more important, renaming is waste of energy and time.

For me ecosystem means kde website, forum, wiki, communication platforms(irc, matrix, mailing lists), basically the whole surface exposed to community (including users, developers and general public). For platforms I mean, phabricator, gitlab, bugzilla, wikis, it doesn't matter is it for developers or for users/general public. So, platforms are parts of whole ecosystem, and ecosystem include connections/integrations between platforms.

Yea, it is good to have many applications, but that can confusing for general public, they wanna one tool that work, they don't care about minor/backend differences. IMHO, kde need promote and make KDE PIM as a first class kde applicatons, like Dolphin, Konsole or Kdenlive, Krita. For example, most of the linux distributions who ship Plasma, normally ship Dolphin, Konsole, Okular, but who ship Kmail, usually they ship Thunderbird. I know, it is not best example to compare file manager, with email client, but it is on the way what i wanna say. I think that kde ecosystem, or generaly linux/floss ecosystem need to improve in PIM niche, to be competitive against others OS. Maybe, the biggest problem with PIM is that most of users going full online(Gmail, GoogleDocuments, ChromeOS, Microsoft Office online), mobile usage come before native computer applications. How to position KDE PIM, is hard question, and harder to achieve success. But, it is clear that KDE PIM need improvements.

I think just saying "Improve KDE PIM" may be a too broad goal. There are many areas that need to be improved in order for Kontact to move forward, some more exciting, some less so, but the goal should IMO be more specific in this regards

I start using matrix, and i use Riot client. In may 5min research Riot is currently most completed, but it is electron app. Do KDE have any matrix client app? There some some numbers of Qt based clients, so if kde dont have matrix client app, maybe is time to incubate some.

I'd like to propose Sigil. It an ebook(epub) editor.

This is similar proposal as T11051, there I explanin a to need reorganization in platforms, tools, websites, here you focus more on applications. And in T11069, I propose to make better KDE PIM, where I list same/similiar problems in that application suit, your goal is more wider. So my goal is like subtask for this, work on improving PIM can be starting point.

@lavender Sorry if I write stuff on complicated way, my english is bad. To summerize, we can chose i3 as a clear goal, but we dont need to make 100% of i3 in plasma. We can implement some different tiling solutions/features to be better with plasma.

@lavender iIthink it is too much to expect that plasma support i3/sway configuration. Yes, most of i3 features need to be supported or have better solution, but it doesn't need to be exact i3 implementation. Should be kept in mind that plasma have many thing that i3 doesn't have natively, for example plasma have krunner, task switcher, additional windows handling features, complex taskbar, widgets, applications launchers. So it need to be extension/integration with current kwin/plasma not direct implementation of i3 on top of kwin. I have only i3 experience from tiling window managers, but maybe someone know different/better features from other tiling window managers that can be implemented.

@martinsotirov correct... all three propose (T11086, T11067 and T11057) are request for better tiling support...

This task is basically copy of my proposal T11069, where my going in wider solutions.

This task is basically copy of my proposal T11067, where my going in wider solutions.
@nicolasfella yea you are right but i think @Eiden wanna say this, currently plasma have some kwin scripts to support proposed features but that is hacky way because of conflicting and break on plasma updates. If kwin natively support that features that guaranties better support/maintenance.

@strobach In past i try some kwin scripts, and i never be satisfied (usually missing features, setup problems, bugs, break on update), so for me that is hacky way, but I will try your script. I know, if plasma implement native tiling mode, that add more complexity, and it is not clear that tiling wm-s is enough big niche to need support. I would like to to make some survey to check how may peoples use kwin tiling scripts or try simulate tiling wm on any other solution.

I make suggestion in T11067 to plasma implement better tilling window management. I am not sure does that help in term of Accessibility(for people with disabilities), but it certainly help in Keyboard navigation and Focus handling (and maybe help in voice inputting). So, it seems that my goal suggestion is sub-task for this goal.

I'm not familiar with internal kde organization and infrastructure. As normal kde user, for me it is hard to make any exact suggestion, I just saying my viewpoint and problems I encounter. Nevertheless, for me it is clear that this set of problems requires radical reorganization and that is scariest part. Some problems are solvable with partial solutions, but I think without clear picture of whole ecosystem it's hard to make correct decisions. My suggestions is to start from kde website, because it is starting point for every other platform. The website need to be integral part, not just links aggregator and pretty pictures. I don't know, do kde community have enough resources to solve those problems with clear strategy and vision. Someone (or small team) who know internal kde structure need to redesign and propose their core design in one document. The one person/small team need to work on this because if to many people work from start it is hard to have clear vision and it is easy wander off. Then when solution is presented, community can make suggestions.