Well, -ext and -contrib would be more in line with the practice of other projects I think (and smaller to type). Phil 2013/2/17 Camillo Bruni <camillobruni@gmail.com>:
On 2013-02-17, at 21:21, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Hi guys
I would like that under the PharoTeam we only get projects that are used for Pharo "core" more or less. Then I think that it would be good to have a place to have Pharo projects such as XMLWriter, XMLParser, SOUP and other. What do you think?
yes I would love to see them more separated
Do we create a new team called PharoEcosystem?
Then we should name the teams accordingly, I suggest three levels which are mainly defined by who maintains the software:
pharo / -core => stuff that goes on http://ci.inria.fr/pharo => 100% maintained by rmod/pharo-core team
pharo-extension? -ecosystem? => partially maintained by rmod/pharo-core team
pharo-contribution => stuff that goes on http://ci.inria.fr/pharo-contribution => maintained by external people