Hi, let's see if we can move into specific details to find and fix whatever is 
problematic in this discussion about using anything close to "meego" in 
packages and distro names. 

About using "meego" or something similar to name a distro using MeeGo related 
components, the opinion of The Linux Foundation is clear. My simple 
interpretation of it is: thanks, but no thanks. Call it something completely 
different and off you go.

About package names, since they are open source (LGPL, Apache...) there 
shouldn't be any problems redistributing them with the same name, isn't it. If 
there is a problem with the name or license of a specific package please let's 
file a bug and let's discuss and solve it in the context of that specific 
problem.

I just took some time to compile the list of packages using "meego" currently 
in 1.1 trunk:
http://wiki.meego.com/MeeGo_in_package_names

What is really the problem? Apart from the fact that it is not good practice to 
carry the names of distros in package names of generic apps and libraries, it 
is not evident (at least to me) where the problems really rely.

Packages using the "meego" string in the MeeGo releases seem to fall in these 
categories:

    * Applications developed by the MeeGo project within the UX categories. In 
general it is not a good practice to tie an open source app with the name of a 
distro. Also the "MeeGo" word doesn't appear in the UX of these apps. Should we 
consider the renaming of those packages, removing "meego" from them?
    * Packages related with the MeeGo Touch Framework. The branding of this 
framework was discussed and agreed, causing the actual renaming of the 
components (previously libdui). There is no problem in other distros willing to 
use the MeeGo Touch Framework. Is it clear the situation of branding and icons, 
though? Are they in isolated packages?
    * Upstream packages with specific MeeGo version/configuration. Not a big 
deal, between not useful or not problematic for other distros.
    * Packages intrinsically related to the MeeGo distro (configuration, 
branding, devtools). Not useful in the context of other distros.

Progress in this discussion is measured in improvements to the current 
documentation and bugs filed/solved. If you file any bugs about this please CC 
me. Thanks!

--
Quim
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to