On Monday, December 13, 2010, Martin Gräßlin wrote: > > Btw: you all should probably figure out what you want your repository > > names to be, if not you'll get names like "kdebase-workspace". > > Following a short discussion on IRC I propose to use the name "Plasma" for > kdebase-workspace.
i'm not 100% sure (but not 100% unsure, either) about that for a few reasons: * it's a brand name, and history has shown those shift every so many years; i'd like to think plasma will stick around for a long, long time, but for a technical artifact, kdeworkspaces (or even kdebase-workspace) would be a safer term. or maybe i'm just being a pussy on this and should support a firm commitment to the name :) * we have libplasma in kdelibs, plasma components in kdebase-runtime. kdebase- workspace is not the only place for plasma components. the reason for putting items in kdebase-runtime is because applications not in the workspace package are using them if the concern is that "kdebase-worspace" is too long or hangs on too much to the old modularization (which i would probably agree to :), perhaps we can just make it kde-workspaces or kdeworkspaces? or something similarly non- branded? if we do think that "plasma" is a better term for the module, i would at least like to see it made specific to the workspaces to differentiate it from the rest of the plasma work that resides elsewhere. plasma-workspaces, e.g. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
