I concur with Mariano and wonder why Stéphane wants a smaller dev image? Right now there are two images, the core and the dev. As the core is promoted for deploying, the size of the dev isn't an issue. At least in terms of deploying. Now the dev image is currently targeted to new users, so I think that it should have everything that is know to work in Pharo loaded, so that the users doesn't have to cope with the installation issue of new packages. This also means that tutorials and documentation can be straightforward. Just showing what they want to teach, and not explaining what to do to install some random package. So this will help document and promote Pharo. Now maybe the name dev is misleading. It says development although the image is for everyone that is not deploying some application. On the other side, there isn't officially a dev image, only PharoCore and Pharo. So maybe we need to create a official PharoDev image targeted to the developers but this is also very subjective as what packages made a development environment, it is upon the developer. So maybe this make no sense at all. So the options are: 1. Refer to Pharo dev as Pharo, the official name and officially make it targeted to new users and so include everything under the sun (like the fun images of Edgar, that can show off the capabilities of Pharo) 2. Create a PharoDev, with a list of common dev packages, also officially supported TL;DR; Pharo is for new users and should include everything preloaded. PharoCore is for deploying and the developer install just what he wants. Maybe a PharoDev is needed targeted directly to developers. Cheers -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx