On Monday 05 January 2009 18:26:20 Albert Astals Cid wrote:
> > So there are a couple of options for those "out of cycle plasmoids":
> > - So create its own module (kdeplasma-out-of-cycle-addons)?
>
> Eh? when is kdeplasma-out-of-cycle-addons released? It surely needs to have
> a "release schedule" on its own so it can't be out-of-cycle at all, maybe
> more like kdeplasma-very-short-cycle-addons but are you going to be the one
> that packages/releases kdeplasma-very-short-cycle-addons each ¿month?
>
> > - Put them into kdeplasma-addons and live with lacking translation
>
> This lack of consideration for translations makes me sad.
>
> Translations should be an integral part of the process, not an afterthough.

I fully agree. I didn't note it as the best solution, but naming it and the 
possible conferences, independant of their problems.

> Translators do a very important job to make sure our products are available
> to a wide range of users. Treating them as second citizens saying missing
> translations are ok is not a good idea.

I'm not saying missing translations are OK. It is part of the bigger issue of 
maintaining quality of what we release. (That includes also docs, bugfixes and 
such.)

> > - Put them into extragear and clutter it up that way
>
> Extragear is there for those:
>  * Specialized programs that don't belong to core modules
>  * Programs that don't want to follow the official KDE release schedule
>
> For me it's obvious that applets that were not done when they should have
> been to enter kdeplasma-addons belong into extragear. Note that releasing
> them in extragear without any time for translators to catch up is also a
> bad idea in my opinion, but in this case is the applet coder that
> misconsiders translators work, not the whole KDE.

Effectively, it's still bad...
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9