- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo name conflict

by Michael Rueger

Damien Cassou wrote: > On Thu, Jan 15, 2009 at 11:31 AM, Michael Rueger <m.rueger(a)acm.org> wrote: >> 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 >> switch names. >> 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? > > What about http://code.google.com/p/pharo/? > Looks good to me :-) Michael

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by StÃ©phane Ducasse

we keep it :) > >> 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 >> switch names. >> 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? > > What about http://code.google.com/p/pharo/?

Jan. 15, 2009

Re: [Pharo-project] Big problem with the implementation of traits

by StÃ©phane Ducasse

No we check and this is strange. What is the hash of a trait? Stef On Jan 15, 2009, at 12:08 PM, Adrian Lienhard wrote: > Confirmed. I created http://code.google.com/p/pharo/issues/detail?id=443 > Not sure how it is possible that this IdentitySet can get into that > state. Any ideas? > > Adrian > > On Jan 15, 2009, at 11:01 , Damien Cassou wrote: > >> Hi, >> >> if you load the latest version of Collection package in PharoInbox >> and >> evaluate the following, you will see a problem: >> >> TCreationWithTest users ===> an IdentitySet(SetTest >> OrderedCollectionTest ArrayTest) >> >> TCreationWithTest users size =====> 5 >> >> >> Depending on your image, the results may vary but will probably still >> be incorrect. >> >> Bye >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Damien Cassou

On Thu, Jan 15, 2009 at 11:31 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > 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 > switch names. > 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? What about http://code.google.com/p/pharo/? -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 15, 2009

Re: [Pharo-project] Big problem with the implementation of traits

by Adrian Lienhard

Confirmed. I created http://code.google.com/p/pharo/issues/detail?id=443 Not sure how it is possible that this IdentitySet can get into that state. Any ideas? Adrian On Jan 15, 2009, at 11:01 , Damien Cassou wrote: > Hi, > > if you load the latest version of Collection package in PharoInbox and > evaluate the following, you will see a problem: > > TCreationWithTest users ===> an IdentitySet(SetTest > OrderedCollectionTest ArrayTest) > > TCreationWithTest users size =====> 5 > > > Depending on your image, the results may vary but will probably still > be incorrect. > > Bye > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Michael Rueger

Hi David, 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 switch names. 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? Michael On Thu, Jan 15, 2009 at 10:15 AM, StÃ©phane Ducasse <stephane.ducasse(a)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 > it. > 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. > > Stef > > > 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: >> http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… >> >> 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(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2009

[Pharo-project] Big problem with the implementation of traits

by Damien Cassou

Hi, if you load the latest version of Collection package in PharoInbox and evaluate the following, you will see a problem: TCreationWithTest users ===> an IdentitySet(SetTest OrderedCollectionTest ArrayTest) TCreationWithTest users size =====> 5 Depending on your image, the results may vary but will probably still be incorrect. Bye -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by StÃ©phane Ducasse

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 it. 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. Stef 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: > http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… > > 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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2009

Re: [Pharo-project] Pharo name conflict

by Serge Stinckwich

2009/1/15 David Hammond <dhammond(a)webdevout.net>: > 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: > http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… > > 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. Hum, yes a bit annoying. Thank you David for your report. The name Pharo was selected at the end of april 2008/beginning of May 2008. Look here in this old archive : http://lists.gforge.inria.fr/pipermail/sapphire-devl/2008-May/thread.html I think that the two Pharos are sufficiently distinct not to confuse them. Maybe we could rename our Pharo to "Pharo Smalltalk" and yours "Pharo PHP Web framework" ? BTW, you could use Seaside (http://seaside.st) to switch to Pharo Smalltalk in order to implement Pharo framework ;-) -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 15, 2009

[Pharo-project] Pharo name conflict

by David Hammond

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: http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… 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.

Jan. 15, 2009