Hello, I am thinking that some "getting started" info is a good idea for Pharo 1.0. As a first part, I have tried to compile various statements "about pharo" and what I read on the mailing list into a short text (see below). Does that capture what people doing the work are thinking about the project? Anything I should add? Anything you don't like? Cheers Matthias =About Pharo= The goal of the Pharo Project is to produce a clean and lean open-source Smalltalk for professional software development: * great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets * clean and lean image * works out-of-the-box, with clear ways to add functionality Starting from version 1.0, Pharo wants to be stable to make sure that we can produce ideas based on it. An important test for Pharo is that mission critical Seaside (http://www.seaside.st) applications should run on it. Pharo started from Squeak (http://www.squeak.org) [which version, 3.10?] but it is a fork: Do not expect Etoy/Nebraska to work in Pharo. We will try to avoid to reinvent the wheel but will change if changing is better. Pharo wants to take a fresh look at the Smalltalk philosophy and current implementations. Ideally by 2011 we would like to have a small kernel and some cool packages that we can load on top. The current focus is not to produce such a kernel but good packages. Everybody is welcome to contribute. You can find a wiki, bug tracker, and a mailing list via the Pharo home page at http://www.pharoproject.org ==License== [A few words about the code that is already there in Pharo, please] Any code developed and committed to the SqueakSource/Pharo and PharoInbox repository is by default under the MIT License.