Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-20 Thread webwarrior
So now we stil have 2 subissues, that need discussion. They break backwards compatibility (basically it's about using Spec models instead of morphs in some methods). However it's not clear if these methods are widely used. So maybe transition will be painless, maybe not so much. We need to

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Marcus Denker
> On 02 Nov 2015, at 16:30, webwarrior wrote: > > https://pharo.fogbugz.com/f/cases/16725 > > Almost a month has passed > yes, there are 600 open issues… Marcus

[Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread webwarrior
https://pharo.fogbugz.com/f/cases/16725 Almost a month has passed -- View this message in context: http://forum.world.st/Case-16725-why-no-reaction-tp4858968.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Nicolai Hess
2015-11-02 16:49 GMT+01:00 Nicolai Hess : > > > 2015-11-02 16:30 GMT+01:00 webwarrior : > >> https://pharo.fogbugz.com/f/cases/16725 >> >> Almost a month has passed >> >> > - there are many other things to do > - we don't have a real spec maintainer > -

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread stepharo
Benjamin forced us to react and the Inria lawyers did their job. Then he wrote this funny sentence. I asked the inria laywers to stay calm when they saw this sentence. You know they laugh one minute and after they want to attack. So I would ignore anything related to Benjamin because the spirit

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Nicolai Hess
2015-11-02 16:30 GMT+01:00 webwarrior : > https://pharo.fogbugz.com/f/cases/16725 > > Almost a month has passed > > - there are many other things to do - we don't have a real spec maintainer - the issue has milestone "Later" - ~ 300 for milestone pharo 5 if you can create

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Peter Uhnák
> > - ~ 300 for milestone pharo 5 >> > and 18 for Spec (although some look stale) "After I realised that the Pharo board was not able to consider the concept > of *copyright infringement*, and that stealing a project was far from an > issue to them, I decided to give up and to give away the code

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Peter Uhnák
On Mon, Nov 2, 2015 at 5:31 PM, stepharo wrote: > Benjamin forced us to react and the Inria lawyers did their job. Then he > wrote this funny sentence. > I asked the inria laywers to stay calm when they saw this sentence. You > know they laugh one minute > and after they want

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread Stephan Eggermont
On 02-11-15 16:57, Nicolai Hess wrote: "After I realised that the Pharo board was not able to consider the concept of *copyright infringement*, and that stealing a project was far from an issue to them, I decided to give up and to give away the code since I do not want to fight with people not

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread stepharo
+ 1 :) 2015-11-02 16:30 GMT+01:00 webwarrior >: https://pharo.fogbugz.com/f/cases/16725 Almost a month has passed - there are many other things to do - we don't have a real spec maintainer - the issue has milestone "Later" - ~ 300

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread webwarrior
Split into subissues; 2 of them are ready, another 2 need discussion On 02.11.2015 18:30, Peter Uhnák [via Smalltalk] wrote: > On Mon, Nov 2, 2015 at 5:31 PM, stepharo <[hidden email] > > wrote: > > Benjamin forced us to react and the Inria lawyers did their job. > Then he wrote this

Re: [Pharo-dev] Case 16725: why no reaction?

2015-11-02 Thread stepharo
Thanks! Also btw having a real name instead of webwarrior can improve my trust :). Stef Le 2/11/15 14:25, webwarrior a écrit : Split into subissues; 2 of them are ready, another 2 need discussion On 02.11.2015 18:30, Peter Uhnák [via Smalltalk] wrote: > On Mon, Nov 2, 2015 at 5:31 PM,