--nextPart12512455.oehnWvDRsz
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 26 May 2008, Jakob Petsovits wrote:
> I ask you, "immediate supervisors" (quote JRT) to take a look at this

urg. we're immediate team members, not immediate supervisors =3D)

> kdelibs? handles icon loading and the technical side of icon fallbacks.

kdelibs really has nothing to say about the names of the icons, just the=20
mechanism for loading an icon given an arbitrary name.

> oxygen? is what i work on, but also affects other themes.
> kdebase/runtime? has oxygen just as a "minor" part amongst other large
> pieces of concrete code.

oxygen is a project of the kde artwork project, and it seems that icon nami=
ng=20
as well would fall within the kde artwork project scope.

as for how to bridge it over to the developers, this is something that affe=
cts=20
application developers. in one sense it's kind of like writing a library 3r=
d=20
parties depend on: you have to keep compatibility going forward so as not t=
o=20
break other people's work that they've already done. so the effort towards=
=20
develpers is probably pretty low, other than to document additions as they=
=20
happen (changes are probably verboten?) and to work with k-c-d members who=
=20
work on KIcon* to keep that infrastructure working.

> So who's responsible for this area?

given how it usually works in kde, this seems fairly obvious to me: the peo=
ple=20
doing the bulk of the work, the people responsible for the design going=20
forward, etc. that would seem most naturally to me to currently include Ken=
,=20
Pinheiro and yourself; there are certainly others involved with oxygen,=20
artwork and icons, but responsibility lies with those doing and directing t=
he=20
work.

in the case of icon naming, as Ken and Pinheiro have also both given you th=
eir=20
express approval and, indeed, support in this area, it only seems logical t=
hat=20
you would be the person to take maintainership of the icon naming. doubly s=
o=20
since you have been doing the bulk of that work.

and as someone who was involved in that work as well prior to 4.0 (mostly f=
rom=20
the coding side though), you also have my support.

it sucks to not have a recognized and active maintainer in a project, so if=
=20
you want that role it seems to be yours for the claiming =3D)

> It also doesn't help that the
> kde artists module doesn't have an official maintainer listed at
> http://techbase.kde.org/Projects/Release_Team#Coordinator_List .

indeed; perhaps you could decide amongst yourselves who that could be and a=
dd=20
such an entry. note that co-maintainership is fine as well.

=2D-=20
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 Trolltech


--nextPart12512455.oehnWvDRsz
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBIQdba1rcusafx20MRAuSBAKCNjUU2Kd4R+4SC+KTsc24NxL1oGQCcDNLC
Vlxvm5APeYVEylyXWOfEoeU=
=EpTL
-----END PGP SIGNATURE-----

--nextPart12512455.oehnWvDRsz--