February 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] How can I add a contributor to one of my project on SmalltalkHub?

by stephane ducasse

because right now I do not see any button? Stef

Feb. 17, 2013

Re: [Pharo-project] Aout community organization under SHub?

by stephane ducasse

On Feb 17, 2013, at 9:29 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-02-17, at 21:21, StÃ©phane Ducasse <stephane.ducasse(a)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 I like extension. > pharo-contribution => stuff that goes on http://ci.inria.fr/pharo-contribution > => maintained by external people Ok It makes sense

Feb. 17, 2013

Re: [Pharo-project] Aout community organization under SHub?

by phil＠highoctane.be

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(a)gmail.com>: > > On 2013-02-17, at 21:21, StÃ©phane Ducasse <stephane.ducasse(a)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 > >

Feb. 17, 2013

Re: [Pharo-project] Aout community organization under SHub?

by Camillo Bruni

On 2013-02-17, at 21:21, StÃ©phane Ducasse <stephane.ducasse(a)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

Feb. 17, 2013

[Pharo-project] Aout community organization under SHub?

by StÃ©phane Ducasse

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? Do we create a new team called PharoEcosystem? Stef

Feb. 17, 2013

Re: [Pharo-project] Migrated SS/Growl to Pharo/Archive

by Mariano Martinez Peck

On Sun, Feb 17, 2013 at 2:56 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > > > > Stef, now that you are migrating everything to SmalltalkHub, are you: > > > > - putting a big text in the old repositories saying "PROJECT XXX WAS > MOVED TO YYY". Because then we run in problems where people refer/commit to > old repos > > - make old project repo read only > > I did it for all the projects that I administrate. > > Excellent :) -- Mariano http://marianopeck.wordpress.com

Feb. 17, 2013

Re: [Pharo-project] Migrated SS/Growl to Pharo/Archive

by stephane ducasse

> Stef, now that you are migrating everything to SmalltalkHub, are you: > > - putting a big text in the old repositories saying "PROJECT XXX WAS MOVED TO YYY". Because then we run in problems where people refer/commit to old repos > - make old project repo read only I did it for all the projects that I administrate. Stef

Feb. 17, 2013

[Pharo-project] RoelTyper -> SmalltalkHub

by StÃ©phane Ducasse

Just a notification that I migrated RoelTyper to SmalltalkHub. I added a configuration. Stef

Feb. 17, 2013

[Pharo-project] Moved FileSystem-Git to Smalltalkhub

by Max Leske

Hi guys. I just moved the sources for FileSystem-Git from ss3 to Smalltalkhub: http://smalltalkhub.com/#!/~MaxLeske/FileSytem-Git. Max

Feb. 17, 2013

Re: [Pharo-project] Migrated SS/Growl to Pharo/Archive

by Mariano Martinez Peck

Stef, now that you are migrating everything to SmalltalkHub, are you: - putting a big text in the old repositories saying "PROJECT XXX WAS MOVED TO YYY". Because then we run in problems where people refer/commit to old repos - make old project repo read only ? cheers, On Sun, Feb 17, 2013 at 1:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > since growl has been integrated to Pharo I migrated the SS project to the > Pharo/Archive one. > > Stef > -- Mariano http://marianopeck.wordpress.com

Feb. 17, 2013