Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" , we should make a pharo team and put all the repos there so people can find them in one place

On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:

Hi,��

not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella)..��

pharo-project -> core pharo

pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends.

pharo-graphics -> block/brick and upcoming graphical cool stuff

pharo-gtools -> gtools + glamour, etc.

pharo-nosql -> voyage family��

pharo-? -> I don���t know, whatever

in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be ���subtrees��� of pharo-core so is good to have them well organised.��

of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :)

(and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository).

Esteban

On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:

esteban do we have a naming convention on github?

pharo-xxx?

Stef

On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

As part of our work for release, I changed the home of Iceberg into his own place:�� https://github.com/pharo-vcs/iceberg

So, now to install you will need:

Metacello new
�� baseline: 'Iceberg';
�� repository: 'github://pharo-vcs/iceberg:dev-0.4';
�� load.

I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, so you can load while
doing the transition.