1

Hi. My idea is the following and is based on my actual needs. I tend to divide my work in activities (thanks plasma!) and work on both my laptop and the lab's computer. If I work on my laptop I have to sync all my documents, calendars, contacts to the labs computer. Kitchensync is not usable at the moment and since I have several activities this is a pain. My suggestion is to use Nepomuk to catalog/tag the documents, etc related to an activity as belonging to that activity. Both the activity and related information (PIM data, documents, etc) should then be synced with server X whenever I'm connected to network Y. This goes in line with the packaging of activities for easy sharing only even documents related to activities would be "packed". I guess this requires full awareness of the context and better integration of Nepomuk, Akonadi and plasma. Anyway, I give this to consideration.

Not sure if it is a good idea to start integrating such complex idea into plasma.
Complexity _always_ introduces bugs, reduces reliability and typically comes with a ton of settings.
In addition a ton of secondary questions arise the moment such approach is tackled: what about different plasma versions? Or even non plasma systems? What about applications that do _not_ work file/document based, so which cannot be synced that way? What about circuit breakers? What about versioning?

In my opinion syncing content should _not_ be part of the interaction layout used on a system.
If you want to synchronize content, then use an addition for that. This keeps the base system clean, crunchy and reliable.

I personally use nextcloud for such stuff. It works across network and system boundaries, allows access from foreign systems, sharing stuff and comes with a ton of other features, all concentrated in a single place. Synchronization works and is reliable. And although it has the term "cloud" in its name you can still have a setup where you keep your own data private.