[kde-artists] Resolving icon naming conflicts

Jakob Petsovits jpetso at gmx.at
Sun Jun 1 22:38:30 BST 2008

On Sunday, 1. June 2008, James Richard Tyrer wrote:
> On Sunday, 1. June 2008, Aaron J. Seigo wrote:
> > in the case of icon naming, as Ken and Pinheiro have also both given you
> > their express approval and, indeed, support in this area, it only seems
> > logical that you would be the person to take maintainership of the icon
> > naming. doubly so since you have been doing the bulk of that work.
> This if fine, but what happens if the names chosen don't work with the
> icon loader code.  That is the concern where the developers need to be
> involved.

Cool, that might make a good fit as I'm a developer myself, have been involved 
with the icon loader code, and try to work together with the respective 
application developers when new icons should go into the core theme
(and subsequently, are in need of a proper name).

> > and as someone who was involved in that work as well prior to 4.0 (mostly
> > from the coding side though), you also have my support.
> Unfortunately, politics isn't going to result in a logically ordered set
> of new icon names, or good new names for old icons.

Please mind that I don't argue about this stuff because of politics or ego but 
because I care about the topic itself. If your suggestion is a net win for 
everybody then why should I try to get in your way? (Especially given the 
frustration that comes with such long-winded discussions.)

I have no intention to take away logical considerations, I just want a 
sufficient balance between logic, maintainability, application needs, 
usability and 3rd party themers. Just focusing on one of those will sometimes 
make life harder for others, so we need to weigh the benefits and drawbacks 
against each other.

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

Mmkay, I claim icon naming maintainership.
Any additional process, or does it just go like this?


More information about the kde-core-devel mailing list