- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo consortium agreement

by Sabine KnÃ¶fel

did you skip "individual golden","sponsors" and "normal" (see below) Message: 1 Date: Thu, 5 Jul 2012 11:19:02 +0200 From: St?phane Ducasse <stephane.ducasse(a)inria.fr> To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr>, A friendly place where any .... Hi pharoers Here is so far the state of replies I compiled. If I miss you or misclassified tell me. By end of July I will build a case to ask for INRIA support. So I will refresh this list and group mails to build a convincing case. Pharo2.0 is going in the right direction. With a mini core, vector graphics, ssh, it is starting to be a nice platform for new challenges. Thanks you all for your trust. Stef So far 4000 gold 8000 silver 5000 bronze 500 sponsor 2500 individual plus 480 individual -------------------- 20480 Euros Gold (4000) RMOD 4000 Silver (2000) 2Denker http://www.Synectique.eu Sanders Cameron company 2Rivers 8000 Bronze (1000) Andy bunnett company Eggermont company MAD-Environment www.FinWorks.biz netStyle.ch 5000 Sponsors (500) Caeasar Systems (May be IMUS)?? 500 Indivudual golden (100) Stephane Ducasse Marcus Denker Schmiedl Miguel Coba Alexandre Bergel Krish Brodbeck (may be bronze) Goran Vasic Guillermo Polito Norbert Harlt Mark Smith Lorenzo schiavina Daniel Galdames Leandro Caniglia Francois Stephany Sean De Nigris John O'Keefe Tudor Girba Luc Fabresse Florent Arrignon Lawrence Trutter Sabine Knofel Yann Monclair Henrik Johanssen Hernan Wilkinson (or bronze to be defined) 2500 Normal 40 Bill schwab Herve verjus Damien cassou McLeod Max Leske Phil Back (bronze may be) Yanni Chiu Andrea Br?hlmann Stefan Reichhart Niklaus Lutz Max Leske Simon Jakovina 480 On Tue, Nov 6, 2012 at 5:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Dear Pharoers > > Here is the result of the work we did around the consortium for Pharo for > about 2 years. We took into account all your remarks over the years > and we think that the result is good and corresponds to what the community > can support. > This consortium is important for Pharo's future and it will help us to > deliver a system to help you making business. > Our goal is to be able to collect fundings to pay at least one full time > engineer. > > The idea is that all the consortium members will sign the same agreement. > We will not handle modifications per partners. > Now since we are starting the process if you spot some glitches on the > form let us know. We can discuss and fully stabilize one version. > > We suggest to read the document. > - If you agree to sign it and send it to us (in two copies if you > do it by surface mail at > INRIA - S. Ducasse - Pharo, 40, avenue Halley, > Parc Scientifique de la Haute Borne, > BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, > France.), so that we sign it too. > - Don't forget to complete your legal mention on first page and > your contact details on article 14 before signing. :) > > We will launch soon two web sites: > - one for the Pharo user association and > - one for the Pharo consortium. > > > A side note: we will communicate about it later and separately but Inria > decided to support the consortium by paying one extra year to Igor Stasenko. > This is around 60 Keuros in addition to the year of Esteban Lorenzano and > previous years of Igor. > > I really want to thank Inria for the constant support and the work of S. > Karpf, P. Moreau and S. Perin. > > Stef > > > > > > > > ------------------------ > Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) > INRIA - USTL - CNRS UMR 8022 > stephane.ducasse(a)inria.fr > http://stephane.ducasse.free.fr > http://rmod.lille.inria.fr/ > **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 > > 40, avenue Halley, Parc Scientifique de la Haute Borne, > BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. > > > > > > > > > -- PS: Bitte Stimme fÃ¼r meine Schwester abgeben: http://www.sterne-des-handwerks.de/voting/wettbewerb/detail/teilnehmer/4678…

Nov. 6, 2012

Re: [Pharo-project] Pharo Kernel with Metacello

by StÃ©phane Ducasse

On Nov 6, 2012, at 2:06 PM, Pavel Krivanek wrote: > Hi, > > I created an experimental CI job that loads Metacello to the Pharo Kernel. > > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/job/Pharo-Kernel-2.… > Excellent idea :) I see where you are looking for and we are all looking in that direction Now the problem is that we should change our process and generate configurations when we integrate changes. But we want that :) Stef

Nov. 6, 2012

Re: [Pharo-project] [squeak-dev] Re: now that squeaksource is back...

by Frank Shearar

On 6 November 2012 16:55, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> > >> > That's already there. >> > Metacello can say: get this package from this list of possible >> > repositories. >> > Problem is that most of configurations are not aware of that. >> > >> > spec repositories: [ >> > spec repository: 'primary'. >> > spec repository: 'secundary'. >> > spec repository: 'etc...' ] >> >> That's not what I meant. I want the author to say "this piece of >> software contains these parts, and these are the canonical locations", >> and the user should be able to completely override those locations. >> > > #repositoryOverrides: > > self whateverVersion repositoryOverrides: (self whateverRepo); load I have actually tried to do these things. repositoryOverrides: is _insufficient_. It doesn't protect you from a transitive dependency's repository not being available. frank >> frank >> >> >> >> frank >> >> >> >>> On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano >> >>> <estebanlm(a)gmail.com> wrote: >> >>>> Hi, >> >>>> >> >>>> I strongly recommend all of you to move your projects into one of the >> >>>> alternatives: >> >>>> >> >>>> http://smalltalkhub.com >> >>>> http://ss3.gemstone.com >> >>>> >> >>>> the king is dead, long live the king! >> >>>> >> >>>> Esteban >> >>> >> >> >> > >> > >> > > > > -- > Mariano > http://marianopeck.wordpress.com >

Nov. 6, 2012

Re: [Pharo-project] [squeak-dev] Re: now that squeaksource is back...

by Mariano Martinez Peck

> > > > That's already there. > > Metacello can say: get this package from this list of possible > repositories. > > Problem is that most of configurations are not aware of that. > > > > spec repositories: [ > > spec repository: 'primary'. > > spec repository: 'secundary'. > > spec repository: 'etc...' ] > > That's not what I meant. I want the author to say "this piece of > software contains these parts, and these are the canonical locations", > and the user should be able to completely override those locations. > > #repositoryOverrides: self whateverVersion repositoryOverrides: (self whateverRepo); load > frank > > > >> frank > >> > >>> On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>>> Hi, > >>>> > >>>> I strongly recommend all of you to move your projects into one of the > alternatives: > >>>> > >>>> http://smalltalkhub.com > >>>> http://ss3.gemstone.com > >>>> > >>>> the king is dead, long live the king! > >>>> > >>>> Esteban > >>> > >> > > > > > > -- Mariano http://marianopeck.wordpress.com

Nov. 6, 2012

Re: [Pharo-project] [Pharo-consortium] Pharo consortium agreement

by StÃ©phane Ducasse

Apparently we need a physical mail with two copies so no electronic version is allowed. Stef On Nov 6, 2012, at 5:24 PM, StÃ©phane Ducasse wrote: > Dear Pharoers > > Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years > and we think that the result is good and corresponds to what the community can support. > This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. > Our goal is to be able to collect fundings to pay at least one full time engineer. > > The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. > Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. > > We suggest to read the document. > - If you agree to sign it and send it to us (in two copies if you do it by surface mail at > INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, > BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. > - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) > > We will launch soon two web sites: > - one for the Pharo user association and > - one for the Pharo consortium. > > > A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. > This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. > > I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. > > Stef > > <2012-11-06-consortium PHARO.pdf> > > > > > ------------------------ > Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) > INRIA - USTL - CNRS UMR 8022 > stephane.ducasse(a)inria.fr > http://stephane.ducasse.free.fr > http://rmod.lille.inria.fr/ > **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 > > 40, avenue Halley, Parc Scientifique de la Haute Borne, > BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. > > > > > > > > _______________________________________________ > Pharo-consortium mailing list > Pharo-consortium(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-consortium

Nov. 6, 2012

[Pharo-project] Pharo consortium agreement

by StÃ©phane Ducasse

Dear Pharoers Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years and we think that the result is good and corresponds to what the community can support. This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. Our goal is to be able to collect fundings to pay at least one full time engineer. The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. We suggest to read the document. - If you agree to sign it and send it to us (in two copies if you do it by surface mail at INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) We will launch soon two web sites: - one for the Pharo user association and - one for the Pharo consortium. A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. Stef ------------------------ Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) INRIA - USTL - CNRS UMR 8022 stephane.ducasse(a)inria.fr http://stephane.ducasse.free.fr http://rmod.lille.inria.fr/ **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.

Nov. 6, 2012

Re: [Pharo-project] [squeak-dev] Re: now that squeaksource is back...

by Frank Shearar

On 6 November 2012 16:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Nov 6, 2012, at 5:01 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> On 6 November 2012 15:56, Chris Muller <asqueaker(a)gmail.com> wrote: >>> If SqueakSource would be made read-only even for existing projects, it >>> could help "encourage" the transition to the new resources (ss3 and >>> hub). >> >> I can't speak for others, but I'd personally find that quite >> irritating (and I make sure I keep my ss3 repos in sync with the ss >> ones). > > what is irritating? having a r/o repository? or having a repository that crashes because is overflowed? > keeping in sync both versions unnecessary extra work, IMO. Better to move and clean the project... then you are also collaborating to the stability of the R/O repository (which I agree, should remain online for some time) Yes. It means that I _cannot_ keep the repositories in sync, which means that someone might well not be able to load ConfigurationOfControl correctly. >>> But the King still needs to remain available for some time yet -- to >>> preserve some of the diamonds in there which may not have a caretaker >>> at this time. >> >> More than that: Metacello has - as I understand it at least - coupled >> the notion of a project together with the source of that project. In >> other words, a ConfigurationOfFoo says "get these packages from this >> server". That means that unless you take care in how you write your >> ConfigurationOfs your source location is a single point of failure. >> >> Dale, how complicated would it be to separate out the notion of >> findability? In other words, to have the person _executing_ the >> ConfigurationOf to say "look for packages in these locations" with >> defaults set to {ss. latAm. ss3}? > > That's already there. > Metacello can say: get this package from this list of possible repositories. > Problem is that most of configurations are not aware of that. > > spec repositories: [ > spec repository: 'primary'. > spec repository: 'secundary'. > spec repository: 'etc...' ] That's not what I meant. I want the author to say "this piece of software contains these parts, and these are the canonical locations", and the user should be able to completely override those locations. frank >> frank >> >>> On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> Hi, >>>> >>>> I strongly recommend all of you to move your projects into one of the alternatives: >>>> >>>> http://smalltalkhub.com >>>> http://ss3.gemstone.com >>>> >>>> the king is dead, long live the king! >>>> >>>> Esteban >>> >> > >

Nov. 6, 2012

Re: [Pharo-project] [squeak-dev] Re: now that squeaksource is back...

by Esteban Lorenzano

On Nov 6, 2012, at 5:01 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 6 November 2012 15:56, Chris Muller <asqueaker(a)gmail.com> wrote: >> If SqueakSource would be made read-only even for existing projects, it >> could help "encourage" the transition to the new resources (ss3 and >> hub). > > I can't speak for others, but I'd personally find that quite > irritating (and I make sure I keep my ss3 repos in sync with the ss > ones). what is irritating? having a r/o repository? or having a repository that crashes because is overflowed? keeping in sync both versions unnecessary extra work, IMO. Better to move and clean the project... then you are also collaborating to the stability of the R/O repository (which I agree, should remain online for some time) > >> But the King still needs to remain available for some time yet -- to >> preserve some of the diamonds in there which may not have a caretaker >> at this time. > > More than that: Metacello has - as I understand it at least - coupled > the notion of a project together with the source of that project. In > other words, a ConfigurationOfFoo says "get these packages from this > server". That means that unless you take care in how you write your > ConfigurationOfs your source location is a single point of failure. > > Dale, how complicated would it be to separate out the notion of > findability? In other words, to have the person _executing_ the > ConfigurationOf to say "look for packages in these locations" with > defaults set to {ss. latAm. ss3}? That's already there. Metacello can say: get this package from this list of possible repositories. Problem is that most of configurations are not aware of that. spec repositories: [ spec repository: 'primary'. spec repository: 'secundary'. spec repository: 'etc...' ] > > frank > >> On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> Hi, >>> >>> I strongly recommend all of you to move your projects into one of the alternatives: >>> >>> http://smalltalkhub.com >>> http://ss3.gemstone.com >>> >>> the king is dead, long live the king! >>> >>> Esteban >> >

Nov. 6, 2012

Re: [Pharo-project] [squeak-dev] Re: now that squeaksource is back...

by Frank Shearar

On 6 November 2012 15:56, Chris Muller <asqueaker(a)gmail.com> wrote: > If SqueakSource would be made read-only even for existing projects, it > could help "encourage" the transition to the new resources (ss3 and > hub). I can't speak for others, but I'd personally find that quite irritating (and I make sure I keep my ss3 repos in sync with the ss ones). > But the King still needs to remain available for some time yet -- to > preserve some of the diamonds in there which may not have a caretaker > at this time. More than that: Metacello has - as I understand it at least - coupled the notion of a project together with the source of that project. In other words, a ConfigurationOfFoo says "get these packages from this server". That means that unless you take care in how you write your ConfigurationOfs your source location is a single point of failure. Dale, how complicated would it be to separate out the notion of findability? In other words, to have the person _executing_ the ConfigurationOf to say "look for packages in these locations" with defaults set to {ss. latAm. ss3}? frank > On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> I strongly recommend all of you to move your projects into one of the alternatives: >> >> http://smalltalkhub.com >> http://ss3.gemstone.com >> >> the king is dead, long live the king! >> >> Esteban >

Nov. 6, 2012

Re: [Pharo-project] now that squeaksource is back...

by Chris Muller

If SqueakSource would be made read-only even for existing projects, it could help "encourage" the transition to the new resources (ss3 and hub). But the King still needs to remain available for some time yet -- to preserve some of the diamonds in there which may not have a caretaker at this time. On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I strongly recommend all of you to move your projects into one of the alternatives: > > http://smalltalkhub.com > http://ss3.gemstone.com > > the king is dead, long live the king! > > Esteban

Nov. 6, 2012