Hi,
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.
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.
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.
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).
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>.
Time to kill most of the available options, focus on **just one**
and have a compelling story to tell to newcomers.
best,
érico andrei
On 10/03/12 14:15, Martin Aspeli wrote:
Hi,
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``.
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.
For now it lives here: https://github.com/plone/plone-devstart/
It supports Plone 4.1, though I plan to add 4.2 support shortly.
You can download the one file you need here:
https://github.com/plone/plone-devstart/raw/master/plone-devstart.py
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. :)
Martin
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
