<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
First of all, it is a very good initiative. We need to lower the
entry barrier to Plone development in order to attract new people.<br>
<br>
But, even though something like plone-devstart is a good idea, I
might ask if it was the right move or even if this is what we needed
the most. <br>
<br>
Last night while talking to Clayton and Liz about the whole
ZopeSkel/Paster/Templer/Crushinator situation it became clear that
the story for new developers is a complete mess. <br>
<br>
There are good ideas, great developers and high expectations.
There isn't a working solution. Some people jumped on Templer, most
people still need to pin ZopeSkel <2.99 (damn local commands). <br>
<br>
This is bad, and having a new shinny thing that "eases" Plone
development just made the situation even worse -- as long as someone
must use it and then <zopeskel create> & <paster
addcontent>. <br>
<br>
Time to kill most of the available options, focus on **just
one** and have a compelling story to tell to newcomers. <br>
<br>
best,<br>
érico andrei<br>
<br>
On 10/03/12 14:15, Martin Aspeli wrote:
<blockquote
cite="mid:CAPN0AARxR0nSDT6o2UYQx3MmTCjKeX72CqS1HkFPoVMR=Fs0iQ@mail.gmail.com"
type="cite">Hi,
<div><br>
</div>
<div>Somewhat inspired by the goals of the ``plone.api``
initiative and based on the experience of seeing many, many
people struggle to get a "safe" Plone development up and running
due to problems with polluted system Python interpreters,
missing libraries and confusing buildouts, I have created a
script called ``plone-devstart.py``.</div>
<div><br>
</div>
<div>The idea is that you can use this to instantiate a new
development environment in a 'safe' way. It will perform some
checks on your environment to determine the likelihood of
success. It then installs a bunch of useful development tools, a
basic deployment configuration, and creates a simple
(non-reusable) package where you can put your custom Python code
and templates.</div>
<div><br>
</div>
<div>For now it lives here: <a moz-do-not-send="true"
href="https://github.com/plone/plone-devstart/">https://github.com/plone/plone-devstart/</a></div>
<div><br>
</div>
<div>It supports Plone 4.1, though I plan to add 4.2 support
shortly.</div>
<div><br>
</div>
<div>You can download the one file you need here: <a
moz-do-not-send="true"
href="https://github.com/plone/plone-devstart/raw/master/plone-devstart.py">https://github.com/plone/plone-devstart/raw/master/plone-devstart.py</a></div>
<div><br>
</div>
<div>I've tested as much as I can, but if this is to work out for
a broader audience, we need lots of people to test. If you have
a particularly messed up environment, I'd like to hear about it.
:)</div>
<div><br>
</div>
<div>Martin</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Product-Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Product-Developers@lists.plone.org">Product-Developers@lists.plone.org</a>
<a class="moz-txt-link-freetext" href="https://lists.plone.org/mailman/listinfo/plone-product-developers">https://lists.plone.org/mailman/listinfo/plone-product-developers</a>
</pre>
</blockquote>
<br>
</body>
</html>