Action Brainstorming

Based on our "what's working, what's not and what's working elsewhere" exercise, we brainstormed ideas for action across our five facets.

 

Installation & Out-of-the-box Experience

  • Make sure all installers are consistent and buildout-based
  • Buildout builder
  • Sector-specific distros, flavors
  • build an index/overview of buildouts
  • Ship more theme by default
  • Developer tool pack
  • Find and install add-on products TTW
  • Ship a caching solution OOTB +1
  • Ship Enfold Desktop by default
  • Sector specific demo content (installable) +2
  • Integrate customerize with @@manageviewlets + search support
  • Ajax KSSify widgets
  • Address Windows Access rule by killing it dead
  • Precooked content for prototypes
  • VM images and/or Live CD
  • TTW product install
  • Plone on demand software for hosters, universities and demo site to provide
  • Plone as service
  • Start/stop Plone controller cross platform + maintainer
  • Ship custom form generator with Plone
  • Ship page layout tool with Plone
  • Replace Zope Welcome page
  • Create Plone sites without ZMI
  • ZEO by default

 

Customization & Configuration

 

  • Ship TTW content types
    •    ... that are site admin friendly (ie GUI) and work well for developers
  • Promote more theme development
  • Make good page compositing in Plone4
  • Create contextaware deliverance theming
  • Restore TTW config for things lost (eg sane new templates)
  • Ship with Clouseau+DocFinderTab
  • Stripped down configuration (eg no Archetypes)
  • Generic setup: full coverage of ZMI changes
  • Write reference for Generic Setup
  • Improve QuickInstaller
  • GUI for portlet registration
  • Complete Generic Setup roundtrip +1
  • New product skeleton creation "approved"
  • Barebones skin/theme (easier to customize/transform)
  • Refactor AGX +1
    •    ... help catch some errors, better info on problems, add warnings, don't
  •    fail silently
  • Attach template names/filenames to rendered content in debug mode (enable Z3
  • support for this ?) > Plone Inspector
  • Regular communication with "real" integrators: review panel, integrator give
  • more feedback
  • Fix uninstall button in QuickInstaller
  • Build a general introspection tool
  • Unify 2 ways of customizing templates/resources
  • Write a "Pete and Amy" document for Customization + Configuration
  • Web services API for all content(OOTB) folderish and non folderish
  • Web services API for other page elements (OOTB) viewlets, portlets, navigation
  • TTW Forms
  • Remote deployment via Fabric
  • Pare down CSS

 

Deployment, hosting, performance

 

  •     Improve story for static deployment
    •    ... 1)just HTML for now
    •    ... 2)dynamic ala Entransit
  •     Do some profiling/continuous (buildbot)
  •     Buildout recipe index - how to find recipes (nginx, varnish, pound,...) +1
    •   ... new buildout recipes for various configurations
  •     Diagrams of common deployment configurations
  •     Better GS coverage for migration story +1
  •     Improve content import/export GSXML ? +1
  •     Evaluate repoze for production use +2
  •     Explore page element caching (memoize, ajax)
  •     Better virtualenv support
  •     Write a "Pete and Amy" for deployment
  •     Improve plone.net: feature Hosting providers
  •     Define/implement benchmark suite
  •     Outreach to ISPs (support, docs, mentoring, bribes)
  •     Call profiler NG
    •  ... do extensive profiling plus publish results
  •     Evaluate deploy docs to standardize (eg proxypass vs rewriterule)
  •     Bundle some static export/publish product Entransit/CMFDeployment
  •     Blob support
  •     Make it possible to cache (Varnish/Squid) while logged in by using SSI for dynamic elements
  •     Faster template language +1
  •     VMWare image of Ubuntu + Plone
  •     Write 'config mgmt' story
  •     Robust Import/export +1
    •    ... could solve 'migration sucks'

 

Documentation + Community Support

 

  •     Grouping by audience for starting docs
  •     Pruning (system?) for docs  (ratings?)
  •     Related docs links
  •     Add-on product ratings
  •     Browse/filter docs by version/compatibility (already on search)
  •     Topic coordinators (with mentors, if needed)
  •     Centralized videos & screencasts (jon: PloneTV?)
  •     Mentoring process (year round, both students and newbies)
  •     Newbie days on IRC
  •     Visual big picture diagrams of our stack
  •     Prominent best practices docs
  •     Improve conference selection process (jon: how?)
  •     Overall docs coordination team (IA, process, topics, audiences, etc.)
  •     Documentation comments with notification and collation
  •     Implement "editor" idea from Doccom sprint
  •     Documentation wiki (-3!)
  •     Contextual help
  •     Clone Joel ;-)

   

Community + Core Processes

   

  •     Make more screencasts
  •     Actively court CMF/Zope folks at events
  •     Focus sprints to appeal to CMF/Zope too
  •     Reconcile licensing amongst layers of the stack / liberalize licensing
  •     Announcing what is dead, and actually burying it.
  •     Improve maintenance of "core" addons (define "core")
  •     Marketing to university students, e.g. through career days?
  •     Updating framework team process
    •     Document best practices
    •     Review process scheduled
  •     More active delegation - match PLIPs and bugs to people
  •     Another PSPS (2009)
  •     Sprints (core focused)
  •     Assist/encourage local user groups to hold weekend sprints
  •     Network with Python user groups - educate and recruit
  •     Framework team blog (+1)
  •     Framework team roadmap
  •     Acively hep start & support user groups
  •     Speed up unit tets
  •     Encourage framework team to say no!
  •     Add-on product ratings & reviews
  •     Put integrators on framework team
  •     Participate in BarCamps
  •     Release process for collective & tools.