I’ve made fixes long time ago before Ben left.
+ my change is in Pharo image.

Is this enough?

Uko

On 04 Sep 2014, at 11:39, Christophe Demarey <[email protected]> 
wrote:

> Yes, you should add a slice in the Pharo inbox with your contribution but ... 
> it depends under which license you first published your contribution. If it 
> was MIT, it is fine (and spec is out of law). If it was the double licensing, 
> we will not be able to integrate it into Pharo. We should re-implement this 
> functionality.
> I know these things are boring but we should take care to avoid potential 
> problems in the future.
> 
> Le 4 sept. 2014 à 11:13, Yuriy Tymchuk a écrit :
> 
>> Oh wow, it’s amazing how complicated things can get… What you I have to do 
>> to have fixes available in Pharo? Send a slice to Pharo inbox? I just want 
>> to use dark theme in pharo and don’t have ugly UI parts
>> 
>> Uko
>> 
>> On 04 Sep 2014, at 10:52, Christophe Demarey <[email protected]> 
>> wrote:
>> 
>>> 
>>> Le 3 sept. 2014 à 10:24, Torsten Bergmann a écrit :
>>> 
>>>> It is interesting that there is also a new Spec release [2] announced this 
>>>> week 
>>> 
>>> I can see in the announce:
>>> Adds SpecTableLayout, thanks @webwarrior-ws
>>> Removes hardcoded colors, thanks @Uko
>>> 
>>> Do the authors of contribution (or their company if the contribution is 
>>> done at work) agree on the new spec license?
>>> If not, it cannot be part of the new spec and could be integrated in Pharo 
>>> spec.
>>> If so, we won't be able to integrate these fixes in Pharo.
>>> 
>>> It woud be good that spec contributors clarify their position.
>>> 
>>> Regards,
>>> Christophe.
>>> 
>> 
> 

Reply via email to