On Wed, Jan 12, 2011 at 11:16:28PM +0100, Francesco Poli wrote:
On Wed, 12 Jan 2011 09:26:02 -0600 Steve Langasek wrote:
On Fri, Dec 10, 2010 at 04:16:46AM -0800, Don Armstrong wrote:
[...]
Unfortunately, there's no way that Debian can possibly comply with the
compliance specification
quim@nokia.com wrote:
Julian wrote:
* Package names contain meego everywhere. According to common
believe, they are not subject to trademark restrictions (that's
why we had a firefox compatibility package for
firefox-iceweasel transition). They are merely an
Hi, moving to meego-community from meego-dev and keeping the rest of CCs
Julian wrote:
There is libmeegotouch and a lot of stuff has meego in the package
names, we can't really change that without breaking compatibility.
There shouldn't be any problem if you port a library keeping its
2010/12/10 Walter Landry wlan...@caltech.edu:
Don Armstrong d...@debian.org wrote:
On Thu, 09 Dec 2010, Ibrahim Haddad wrote:
To start with, the goal is to avoid any confusion around what is and
what is not MeeGo. Anything that is or will become associated with
the MeeGo trademark has to be
Ibrahim Haddad wrote:
We would ask you to move away from using {M,m}-e-e-{G,g}-o or any subset of
those letters or sounds in that order, alone or in combination with other
letters, words or marks that would tend to cause someone to make a
reasonable connection of the reference with the MeeGo
On Thu, 09 Dec 2010, Ibrahim Haddad wrote:
To start with, the goal is to avoid any confusion around what is and
what is not MeeGo. Anything that is or will become associated with
the MeeGo trademark has to be in conformance with the compliance
program.
Unfortunately, there's no way that
Hello Didier,
I am responding to you in relation to your inquiry below. First, thanks very
much for sending the MeeGo Project these questions. We really do appreciate
it. The MeeGo Project members devoted quite a bit of time discussing these
questions to make sure the responses are fair and
7 matches
Mail list logo
