I was thinking about a possible mission statement for Seaside that reads as following:<div><br></div><div>The goal of the Seaside project is to create a web development framework that makes</div><div>building both simple and complex web applications fun.</div>
<div><br></div><div>Just my 2 cents,</div><div><br></div><div>-Conrad<br><br><div class="gmail_quote">On Mon, May 18, 2009 at 4:51 AM, Sebastian Sastre <span dir="ltr">&lt;<a href="mailto:ssastre@seaswork.com">ssastre@seaswork.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">ok about the draft but it has not a mission on it. It has a description of what<br>
the artifact is.<br>
A mission is still missing.<br>
cheers,<br>
<font color="#888888">sebastian<br>
</font><div class="im"><br>
&gt; -----Mensaje original-----<br>
&gt; De: <a href="mailto:seaside-dev-bounces@lists.squeakfoundation.org">seaside-dev-bounces@lists.squeakfoundation.org</a><br>
&gt; [mailto:<a href="mailto:seaside-dev-bounces@lists.squeakfoundation.org">seaside-dev-bounces@lists.squeakfoundation.org</a>] En<br>
&gt; nombre de Lukas Renggli<br>
&gt; Enviado el: Monday, May 18, 2009 04:22<br>
&gt; Para: Seaside - developer list<br>
&gt; Asunto: Re: [Seaside-dev] What is our Mission Statement?<br>
&gt;<br>
</div><div><div></div><div class="h5">&gt; I started with an initial draft:<br>
&gt;<br>
&gt;    <a href="http://www.seaside.st/about/mission" target="_blank">http://www.seaside.st/about/mission</a><br>
&gt;<br>
&gt; Please feel free to comment, add, remove and change. It should reamin<br>
&gt; short and to the point though.<br>
&gt;<br>
&gt; Lukas<br>
&gt;<br>
&gt; On Sun, May 17, 2009 at 8:10 PM, Philippe Marschall<br>
&gt; &lt;<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>&gt; wrote:<br>
&gt; &gt; 2009/5/17 Sebastian Sastre &lt;<a href="mailto:ssastre@seaswork.com">ssastre@seaswork.com</a>&gt;:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; +1<br>
&gt; &gt;&gt;&gt; Examples:<br>
&gt; &gt;&gt;&gt; <a href="http://code.google.com/webtoolkit/makinggwtbetter.html" target="_blank">http://code.google.com/webtoolkit/makinggwtbetter.html</a><br>
&gt; &gt;&gt;&gt; <a href="http://wicket.apache.org/vision.html" target="_blank">http://wicket.apache.org/vision.html</a><br>
&gt; &gt;&gt;&gt; <a href="http://tapestry.apache.org/tapestry5.1/" target="_blank">http://tapestry.apache.org/tapestry5.1/</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; &gt; I am afraid, that if we try to satisfy everybody<br>
&gt; &gt;&gt;&gt; &gt; we become indistinct.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; It&#39;s not the indistinct that worries but we simply don&#39;t have the<br>
&gt; &gt;&gt;&gt; resources to do it and we&#39;d lose focus.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt; if we succeed in satisfying everybody we become plain<br>
&gt; mediocre not just indistinct. And as Philippe says, no<br>
&gt; resources to even try it.<br>
&gt; &gt;&gt; Also I found those examples mediocres. We should not<br>
&gt; benchmark those. I can&#39;t read more than the first line of any<br>
&gt; of those without having to puke due to technical stuff. I<br>
&gt; don&#39;t want it to happen to the &quot;seaside statement&quot;.<br>
&gt; &gt;&gt; I know Seaside has everything to be much more than that.<br>
&gt; &gt;&gt; Brutal truth: right now we suck because not only don&#39;t<br>
&gt; have one statment, we have like 3 to 6 rotating statments<br>
&gt; which, I&#39;m sorry to the one who created it, comunication<br>
&gt; skill sucks or it&#39;s a genious if the goal is to succeed in<br>
&gt; confusing people about what the product is about.<br>
&gt; &gt;&gt; The most powerful statement I&#39;ve found is the one from<br>
&gt; Yukihiro Matsumoto made for ruby.<br>
&gt; &gt;&gt; Matz said &quot;Ruby is designed to make programmers happy.&quot;<br>
&gt; &gt;&gt; No bullshit + big focus + no technical crap = huge spread<br>
&gt; capabilities.<br>
&gt; &gt;&gt; If a statement like that can be created for seaside we&#39;ll<br>
&gt; have chances of being marketed decently. Otherwise the<br>
&gt; mission statement will born and remain invisible.<br>
&gt; &gt;<br>
&gt; &gt; I disagree. In my view the missing statement is for us so<br>
&gt; that we can<br>
&gt; &gt; decide what should go in and what not.<br>
&gt; &gt;<br>
&gt; &gt; Cheers<br>
&gt; &gt; Philippe<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; seaside-dev mailing list<br>
&gt; &gt; <a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
&gt; &gt; <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Lukas Renggli<br>
&gt; <a href="http://www.lukas-renggli.ch" target="_blank">http://www.lukas-renggli.ch</a><br>
&gt; _______________________________________________<br>
&gt; seaside-dev mailing list<br>
&gt; <a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
&gt; <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>