<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-17 14:15 GMT-03:00 Hernán Morales Durand <span dir="ltr"><<a href="mailto:hernan.morales@gmail.com" target="_blank">hernan.morales@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra">Hello Johan,<br></div><div class="gmail_extra"><br><div class="gmail_quote">
2014-02-17 3:54 GMT-03:00 Johan Brichau <span dir="ltr"><<a href="mailto:johan@inceptive.be" target="_blank">johan@inceptive.be</a>></span>:<div class=""><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br>
On 17 Feb 2014, at 07:26, Hernán Morales Durand <<a href="mailto:hernan.morales@gmail.com" target="_blank">hernan.morales@gmail.com</a>> wrote:<br>
<br>
> I would be willing to merge my changes to a neutral repository.<br>
<br>
</div>Oh... really?<br>
Seaside team is 'hostile territory' ?<br>
<br></blockquote><div><br></div></div><div>No, I don't think so. Nothing personal here or against Seaside.<br></div><div>It is just I am not part of the Seaside team. But see below.<br></div><div class=""><div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
After forking Grease into your private repo, you did the same for Kom, messed up the metacello version history and removed all platforms but Pharo3 from the config.<br></blockquote><div><br></div></div><div>Kom was created as an independent project before Seaside, and it is used by Iliad too. For those reasons, I think that the right thing to do is to have it in its own separate repository and to maintain it there. Do you think is that a problem?<br>
</div><div><br></div><div>About Grease, I didn't knew it was forbidden to fork it in a private repository.<br></div><div>It is prohibited to fork Grease? What's the license of Grease?<br></div><div><br>The thing is, every time I have checked the Grease version from the
Seaside repository, always had problems. That's why I have my own copy
of Grease which worked for my projects for weeks before anyone noticed it existed. So as you can see it's not intended for public consumption. But as I said in a previous mail, if I find the Grease copy to work properly for me, then I will happily remove the fork. I will check later and let you know.<br>
<br></div></div></div></div></blockquote><div><br></div><div>I have checked yesterday and still didn't found a working Configuration for Grease in the Seaside repository for Pharo 3 (the current stable version is loading packages for Pharo 2.0). So, if license is MIT I will keep my copy until anyone can provide something better.<br>
</div><div><br></div><div>Cheers,<br><br>Hernán<br><br></div></div></div></div>