16. June, 2007
• ZopeSkel is now 1 year old
• Provides nine templates
• Seven contributing authors
• nouri, davconvent, hannosch, optilude,
brcwhit, justizin, pelle
• Version 1.0 tagged September, 2007
17. Late 2007
• Archetype template added (pjesi)
• Recipe template for buildout recipes (tarek)
• Hosting buildout template (wichert)
• Version 1.3 in December, 2007
24. archetype (from ZopeSkel#archetype)
-----------------------------------
title The title of the project
default: 'Plone Example'
namespace_package Namespace package (like plone)
default: 'plone'
package The package contained namespace package
(like example)
default: 'example'
zope2product Are you creating a Zope 2 Product?
default: False
version Version
default: '0.1'
description One-line description of the package
default: ''
long_description Multi-line description (in reST)
default: ''
author Author name
default: 'Plone Foundation'
author_email Author email
default: 'plone-developers@lists.sourceforge.net'
keywords Space-separated keywords/tags
default: ''
url URL of homepage
default: 'http://svn.plone.org/svn/plone/plone.example'
license_name License name
default: 'GPL'
zip_safe True/False: if the package can be
distributed as a .zip file
default: False
34. • Local commands need a package to be in
the working set
• This means that paster must ‘install’ your
new package
• Your package must also depend on
PasteScript (which depends on PasteDeploy
and Paste)
43. Goals
• Clean up templates
• Improve questions
• Wrap `paste create -t` to improve
interactions
44. Outcomes
• bin/zopeskel script
• hides `paste create -t`
• provides inline validation of answers
• provides inline help for questions
• provides ‘classes’ of questions
• gives good feedback, and provides hooks
for feedback from new templates
46. Outcomes
• A plan to break up ZopeSkel
https://github.com/collective/ZopeSkel/blob/2.x-maintenance/SPLITTING-PROPOSAL.txt
47. Anti-Outcomes
• Failure to publicize the outcome sufficiently
• Failure to fully document the plan
• Failure to clean up existing docs still
advising ‘the old way’ (paster create -t)
51. • Goal to ‘break up’ monolithic ZopeSkel
• Work starts in early 2010
• Provide templates in packages of related
functionality.
• Keep it working ‘the same’ for newcomers
53. templer.core
• vars (questions)
• base templates
• control script (wrapper of `paster create`)
• structures
• ‘docs’ for eggs
• licenses
54. What are Structures?
• paster templates that you don’t ‘run’
• shared filesystem layout
• reduce repetition
• allow injection of files and folders in
response to questions