Re: Plone 5 Installer/Skeleton plans

Cris,

What can we do/organize to make this happen? Should we suggest that templer
and templer templates be the topic for an emerald/cioppino sprint?

Our goal should be to have this ready to go as Plone 5 reaches beta.

Steve


On Tue, Aug 6, 2013 at 7:59 PM, Cris Ewing <cris-pc0DtrlmWl/[email protected]> wrote:

> I've got a paster-free version of templer functioning with full
> localcommand support.  I'd like to use that, but would ideally be able to
> rip out the dependency on Cheetah templates as well.  That introduces
> compiled code, and without it templer can be installed without needing any
> compiled dependencies.
>
> Ideally we'd undertake reviewing the present template set along with the
> process of converting form Cheetah to something like Jinja2.  I need to
> investigate the possibility of creating a Cheetah->Jinja2 coverter and
> figure if that would be more work than just hand transforming all the
> templates.  If the idea is to bring existing templates "up to code" then
> it's probably a better idea to do them from scratch then transform the
> existing bits.
>
> c
>
>
> On Aug 6, 2013, at 6:17 PM, Steve McMahon wrote:
>
> Hi installers team!
>
> It's time to start working on what we hope to accomplish for Plone 5. Your
> thoughts are welcome!
>
> Here's what I've been thinking about:
>
> 1) Integrating the work that Sven, Alessandro and helpers have been doing
> on smart dependency installation for common platforms (
> https://github.com/collective/install.plone.dependencies);
>
> 2) Have a testing suite for major platforms that will either create
> virtualboxes or spin up cloud machines to test the installers on common or
> troubled platforms;
>
> 3) Integrate a successor to ZopeSkel. This should include skeleton
> generators for all the projects that newbies need to start (dexterity,
> diazo themes, portlets ...).
>
> Ideally, we'll find a way to get the skeleton generator to work with
> buildout so that it can (optionally) add the new package to the buildout.
>
> What I'd like to see here is something close to zero friction in the
> common procedures like: 1) install plone; 2) add a dexterity skeleton
> package; 3) add a content type skeleton to the package skeleton. The output
> should match (as closely as possible) our tutorials for the matching
> procedure. I.E., the dexterity skeletons should match the dexterity
> documentation. New packages should be ready to test with our best, current
> practices. People who do regular training should be very happy to use this
> in their training.
>
> One of the goals for Plone 5 will be to have much more of the core code be
> good examples of the right way to do things. We should ask the same of the
> installers and the associated skeleton generator.
>
> So, there's my set of goals. I know that some of you are already working
> on these projects. Where are you at, and what more (or less) do you want to
> do?
>
> Steve
>
>
>  Cris Ewing
> --------------------------------------------------
> Principal, Cris Ewing, Developer LLC
> http://www.crisewing.com
> cris-pc0DtrlmWl/[email protected]
> 1.206.724.2112
>
>

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk

_______________________________________________
Plone-installers mailing list
Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-installers