[MeeGo-community] Using "meego" or similar in packages and distro names
awafaa at opensuse.org
Thu Dec 16 09:02:47 PST 2010
On 16 December 2010 16:36, <quim.gil at nokia.com> wrote:
> Bernd wrote:
>>> > when you append MeeGo to a package name, it would be very
>>> > reasonable to conclude that this is an official MeeGo package
>>> > coming from MeeGo.com
>> This is not always true.
>> It is perfectly reasonable to assume that a package file called
>> is packed *for* meego, not *by* meego.
> Very true. Still, and back to the point: if someone borrows a package packed *for* MeeGo and uses it in another distro without changing its name, keeping that "maemo" causes no harm to the MeeGo trademark, brand, public image etc.
> After some days trying to nail down the details of this polemic topic, no concrete polemics seem to be found. The remaining arguments talk about "attitude", "mindset", etc. Maybe the problem has been less on the response and more in the way the whole process has gone?
> MeeGo-community mailing list
> MeeGo-community at meego.com
I must say a big thank you to you for clarifying the issue on using
package names. This will make things somewhat simpler. Of course the
issue wouldn't have arisen if there was no bait and switch when MeeGo
was created, but that's another topic.
I am looking at alternatives for the MeeGo based DE in openSUSE to try
and comply with MeeGo's wishes for their trademark on names.
One major issue that distributions will have is that of MeeGo
trademarked artwork being littered in packages that are under LGPL or
other open license, mainly the meego-panel-* packages. If possible
could we get a list of which packages have infringing artwork and what
those items are? For instance where is the file located that provides
the welcome message when someone first sees MyZone?
openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
More information about the MeeGo-community