[Pharo-project] Pharo name conflict
m.rueger at acm.org
Thu Jan 15 05:31:42 EST 2009
yes, that is unfortunate that we chose the same name around the same
time and both projects are already well known enough to not easily
But, as others already said, the projects are sufficiently different
to not be confused easily.
Maybe we could cross-link on the sites?
"if you are looking for the PHP Pharo project go here" and vice versa?
On Thu, Jan 15, 2009 at 10:15 AM, Stéphane Ducasse
<stephane.ducasse at inria.fr> wrote:
> Hi david
> We already communicated a lot on this project such as major
> conferences in our field (www.esug.org).
> Seaside (http://www.seaside.st) is developed using it and will start
> to communicate on that too.
> When we check in may it was clear that there was no other projects
> around and pharo is close to
> french so we expected that nobody else would take that name :)
> Now we got a professional designer for our logo and invested a lot in
> We will have two or three books coming out around Pharo and
> our community is active and growing. It also is a strong symbol for
> us. So we will stick with our name.
> On Jan 15, 2009, at 1:56 AM, David Hammond wrote:
>> Hi, I don't intend to cause a big fuss, but I have a concern about the
>> name of your project.
>> I first became aware of your project yesterday when I ran a Google
>> search for the word "pharo". This is the name I had chosen for my open
>> source PHP framework project back in January of 2008. At the time, the
>> Smalltalk-related Pharo project did not yet exist, and the Google
>> search results yielded nothing at all similar or relevant to the
>> project I wanted to start. I purchased pharo.org that month (with
>> trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in
>> active use) and made a teaser post about the project on my blog:
>> My intention is to release the Pharo PHP framework under a BSD license
>> and not profit directly from the project. I have no stakes in
>> preserving the exclusiveness of the "Pharo" name aside from avoiding
>> possible confusion. But I do believe that the name conflict is an
>> issue of concern, since both of our projects are directly related to
>> programming languages.
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev