Slides for the talk given at Plone Conference 2012. In the following collective package further explaination can be found about the tools discussed: https://github.com/collective/collective.exampledevtools
2. INTRODUCTION
• See collective.exampledevtools on github.com for examples
• https://github.com/collective/collective.exampledevtools
• The tools which can be used during development
• No elaborate code examples
3. Where to find help?
• Read collective.developermanual
• http://collective-docs.readthedocs.org
• Try searching duckduckgo/google, Stackoverflow, Plone mailing
list
• Ask your question on IRC (freenode, #plone) or Plone mailing
list
• Read Plone books: http://plone.org/documentation/books
13. Automate egg releasing
• Use jarn.mkrelease or zest.releaser
• Releasing a Python egg involves:
• Bumping the version number
• Updating history/changes file
• Tagging the release in version control
• Creating the egg
• Uploading the egg to pypi.python.org or a private egg server
14. Continuous integration
• Use Travis CI for opensource GitHub projects
• Use Jenkins for internal company projects
16. PHOTO CREDITS
• http://www.flickr.com/photos/davespencer/6212710431/
• http://www.flickr.com/photos/garnets1973/2771182195
• http://www.flickr.com/photos/lucid_nightmare/74316267/
• http://fschulze.github.com/mr.developer/xkcd-buildout.png
(Remixed by Matt Hamilton, original from http://xkcd.com/303)
• Thesauna.reload logo was originally the logo of Sauna Sprint
2011 and it was created by Vilmos Somogyi.
Notas do Editor
Explain who I am and what I do.\n
\n
Mention new colleagues\nPlone.org has outdated information\nPlone has a steep learning curve, I hope we can ease that curve. \nNabble for mailing list, excellent books available\n
Installing templer/zopeskel using pip/easy_install\nCreate buildouts, Python eggs, Plone CT/Theme etc.\nWhen creating a product (<-explain) we can use Templer to create the boiler plate code. \nExplain: what we can create and ... what local commands do.\nRefer to the talk given by Chris Ewing &#x2018;Zopeskel, the past present and future&#x2019;. Friday morning.\n\n
Buildout is slow, but it&#x2019;s getting better\nAllow-hosts, explain index servers\nMention how we split up buildouts (dev/live)\nLocal buildout cache, company egg mirror\n
Explain you&#x2019;ve got a buildout with src dir.\nBenefits of mr.developer:bulk update, checkout a package\n
Explain about the sauna.reload sprint (jealous!)\nHow we (plone) develop; restart zserver\n
Explain how buildout incorporates the Python eggs\nSome times you need to use the source\n
Explain how buildout incorporates the Python eggs\nSome times you need to use the source luke\n
Replaces the ZMI functionality (name which)\n
Explain briefly how old Plone themes work.\nExplain what Diazo does (html mock-ups, content, rules file).\nExplain what advantage this has (designer -> html2pdf servive -> integrator).\n\n
Explain about a frozen Plone instance, rss feed that was timing out.\nUse mr.freeze or products.signalstack. Explain how they can be used.\n
Releasing an egg properly requires a few steps. \n
We all write tests, do we?\nExplain CI\nFinally, explain plone.api (alpha, things can break)\n