<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><span style="font-family:Arial, Helvetica, sans-serif;font-size:medium"><pre style="font-family:monospace;margin-left:3em;font-size:12px">
It's clear to me from things Julian Fitzel has said that the Seaside maintainers will not be porting to Squeak. They plan to develop for Pharo exclusively. At the moment they are looking for a Squeak maintainer, somebody to convert what they're doing to Squeak. They may have found one already, I don't know. </pre>
<pre style="font-family:monospace;margin-left:3em;font-size:12px"><font class="Apple-style-span" face="arial"><span class="Apple-style-span" style="white-space: normal; font-size: small;"><font class="Apple-style-span" face="monospace" size="3"><span class="Apple-style-span" style="font-size: 12px; white-space: pre;"><br>
</span></font></span></font></pre></span></blockquote><div>In my understanding, they develop seaside as something that is easily portable across all smalltalk dialects. They don't develop excusively for Pharo, they develop on Pharo. So a squeak maintainer won't need to convert all what they are doing but only the platform specific stuffs that I think are well packaged. Moreover, I think right now, the "port" to squeak is straightforward and as they try to use standard stuff, there is no reason it changes in the future ! So yes, they ask for someone to ensure it works on squeak... as there is in gst, vw, visualage, etc ... If you're okay with 2.8.3 it's good for you but maybe other squeakers will prefer to have more recent version, bug fixes, improvements and tests... !</div>
<div> </div></div><br>-- <br>Cédrick<br>