(ugh, just noticed I didn't send his to the list, fathi sorry you're getting
this double)
Ok, read the meeting log [1] now, created the summary below, to those there
do speak up If I missed or misrepresented something.
There where items discussed:
1) How are we handling login screen, wallpapers and splash screens
2) Template images/guidelines for login screens, wallpapers and splash
screens
3) desktop-base or multiple source packages
4) Roadmap for Etch and Etch+1
Summation of each follows:
1) We have the following items to theme:
* xfce: wallpaper, splash (needs patch)
* gnome: wallpaper, splash
* gdm: loginscreen
* kde: wallpaper (uuencoded as patch today), splash, login screen
these are 'core' of our artwork initiative, let's us focus on that 1st
2) * Agreed that we need guidelines for at least 8 items named in 1)
* <stratus> will coordinate common guidelines efforts between the teams.
- lool, Np239 (pkg-gnome)
- fabo (pkg-kde)
- sTone_heAd, Corsac (pkg-xfce)
* first requires technical guidelines for the implementations
* guidelines targetted at pkg-$foo teams initially, but also at people
such as derivatives, or local sites which need an artwork / theme for
GNOME or KDE or XFCE
3)* general agreement for 1 common source package (desktop-base) building
multiple (per project) binaries
* requirement: the artwork packages should be parallel installable, even
mutliple artworks for same desktop at the same time
4) * generally inconclusive: let's see what we get done
* We want:
- have a common guidelines for at least 8 elements of our desktop
- use a common source package building multiple binaries.
* we can do work on guidelines and the '8 elements in desktop-base' for
Etch, we will have the infrastructure and organization to do more (eg:
icons, bootsplash and more) Such as, can I install multiple themes,
what happens if I install both KDE and GNOME themes how do I configure
the default theme for GNOME, for the system
* we need documented use cases
- CDD/derivatives
+ Np239 did to offer gconf overrides -- to my knowledge
+ what's 'expensive' in terms of CDD is handle tons of different
source packages.
-> USE CASE: be able to replace the aforementionned artwork items at
a single place
-> USE CASE: provide means to ship multiple artwork in Debian, and
even more in derivatives, installable at the same time
with some central logic to configure the global artwork
precendence
- we need a single source package to hold the *defaults* for Debian
[1]http://people.debian.org/~stratus/debian-desktop/artwork-meetings/1st-art
--
Cheers, cobaco (aka Bart Cornelis)
1. Encrypted mail preferred (GPG KeyID: 0x86624ABB)
2. Plain-text mail recommended since I move html and double
format mails to a low priority folder (they're mainly spam)
Attachment:
pgpOIhGbFJy35.pgp
Description: PGP signature