The actionable results from the Strategic Planning Summit are here!

I expect people will expand on these when they start mailing the list
as champions, but I'll offer an overview and some definitions:

What it means to be a champion:
- A champion is the person responsible for moving a focus area
forward, and reporting progress.
- Champions should have come up with a plan for how to proceed and
posted that plan to the development mailing list no later than
February 18th, 2008.
- Being a champion does *not* imply that he/she is going to do the
actual work — it's about being the responsible person for that focus
area. Of course, there are cases where the champion is in fact the
person that implements the solution too.

What it means to be a proxy:
- When people were identified as possible champions that were not
present at the Summit, we assigned the responsibility to contact that
person and/or look for a champion to a person that was.

All issues exist in Trac, and you can add yourself to CC there if
you're interested in tracking the progress on a particular issue. Trac
will be used to indicate ownership and keep a running log of progress.

A permanent overview report exists here:
http://dev.plone.org/plone/report/10

It's now your responsibility to:
- Contact the champion if you can offer development help or any other
form of assistance.
- Give feedback and suggestions once the champions start announcing
their intentions to the list.
- If you are a champion or proxy: Make sure there is an email to the
list within a week that outlines the current plan.

The focus areas
============

# Create a process to research, collect and report end-user interface
issues to the UI Team.
Champion: Kurt Bendl
http://dev.plone.org/plone/ticket/7810

# Document integration story for non-Plone development, e.g. use Grok
and integrate auth + theme when Plone is not appropriate
Champion: Martin Aspeli
http://dev.plone.org/plone/ticket/7811

# Add user-configurable ratings support to Plone.
Champion: Alec Mitchell
http://dev.plone.org/plone/ticket/7812

# Make sure the "strategic integration" story with other systems is
visible and documented, e.g. "Plone does CRM via Salesforce
integration".
Champion: Andrew Burkhalter
http://dev.plone.org/plone/ticket/7813

# Make it easy to enable and disable features of core Plone (e.g.
portlets, content rules) through the Plone control panels, and improve
the add-on install experience.
Champion: Hanno Schlichting
http://dev.plone.org/plone/ticket/7814

# Integrate add-on ratings in PSC, so products on plone.org can be
sorted by rating — as well as self-certification of major areas like
unit testing, i18n support, etc.
Champion (suggested): Alex Clark
Proxy: Matt Bowen
http://dev.plone.org/plone/ticket/7815

# Improve Framework Team process: Framework team blog, include
integrators on the team, peer-review the PLIPs.
Champion: Matt Bowen
http://dev.plone.org/plone/ticket/7816

# Improve release procedures for add-ons on plone.org: document a
release process, and create release tools for packaging and uploading
products from the command line.
Champion (suggested): Tarek Ziade
Proxy: Lennart Regebro
http://dev.plone.org/plone/ticket/7817

# Create a working, repeatable organizational structure for working
groups / SIGs that will promote Plone in specific Foundation-blessed
markets.
Champion (suggested): Chris Calloway
Proxy: Kurt Bendl
http://dev.plone.org/plone/ticket/7818

# Create material that teaches people how to do screencasts and put
them up on plone.tv.
Champion: Nate Aune
http://dev.plone.org/plone/ticket/7819

# Create a plan to help local user groups market Plone and Python to
local university students — talks, mentoring, publicize internship
opportunities, university sprints.
Champion: Matt Hamilton
http://dev.plone.org/plone/ticket/7820

# Nightly benchmarking scripts and reports for Plone
Champion: Jarn
http://dev.plone.org/plone/ticket/7821

# Make standard file content types use ZODB BLOB support.
Champion: Andi Zeidler
http://dev.plone.org/plone/ticket/7822

# Finish Plone eggification.
Champion: Hanno Schlichting
http://dev.plone.org/plone/ticket/7823

# Experiment with alternative template languages, produce benchmarks
and numbers if there is reason to believe significant speed-ups can be
accomplished.
Champion (suggested): Helge Tesdal
Proxy: Hanno Schlichting
http://dev.plone.org/plone/ticket/7824

# Create a buildout for Repoze + Plone.
Champion: Chris McDonough
http://dev.plone.org/plone/ticket/7825

# Improve Plone's import/export story, investigate dump and reload as
alternative migration strategy.
Champion: Raphael Ritz
http://dev.plone.org/plone/ticket/7826

# Create and maintain a VMWare image of Ubuntu running Plone for
evaluation and demonstration purposes.
Champion: David Glick
http://dev.plone.org/plone/ticket/7827

# Create a collections of Personas to represent common use cases for integrators
Champion: Eleonora Borelli
http://dev.plone.org/plone/ticket/7828

# Make Kupu more powerful and capable of handling rich media, make the
overall experience better
Champion: Alexander Limi
http://dev.plone.org/plone/ticket/7829

# Fix low-hanging bugs in ArchGenXML based on list of common newbie mistakes.
Champion: Joel Burton
http://dev.plone.org/plone/ticket/7830

# Improve keyword management and tagging interface.
Champion: Brian Gershon
http://dev.plone.org/plone/ticket/7831

# Put together a team to produce a plan for the refactoring or
move-to-Z3 aspects of Archetypes
Champion: Tom "Spanky" Kapanka
http://dev.plone.org/plone/ticket/7832

# Create a "Start Here" newbie page for documentation area. Create a
process for — and execute — a way to user-test documentation to
evaluate whether it is suitable and effective.
Champion (suggested): Darci
Proxy: Donna Snow
http://dev.plone.org/plone/ticket/7833

# Documentation: Create diagrams of the Plone stack and a focused API overview
Champion: Martin Aspeli
http://dev.plone.org/plone/ticket/7834

# Documentation: Add support for — and identify — topic owners in
documentation area.
Champion: Steve McMahon
http://dev.plone.org/plone/ticket/7835

# Documentation: Come up with a suggested Information Architecture for
the documentation (including topic/version/task)
Champion: Laura Trippi
http://dev.plone.org/plone/ticket/7836

# Investigate options for static HTML deployment of Plone sites
Champion: Ken Wasetis
http://dev.plone.org/plone/ticket/7837

# Create a "minimal Deliverance theme" which demonstrates Plone themed
using Deliverance. Should be suitable for a base to start from when
doing this on customer sites.
Champion: Chris McDonough
http://dev.plone.org/plone/ticket/7838

# Create a cross-platform Plone Controller that uses web pages running
in a separate process to provide the controller functionality.
Champion: Andy McKay
http://dev.plone.org/plone/ticket/7839

# Create an index/overview/repository for available buildouts
Champion: Tom "Spanky" Kapanka
http://dev.plone.org/plone/ticket/7840

# Newly installed Plone sites should have thumbnails + links to
quality alternative themes
Champion: Joel Burton
http://dev.plone.org/plone/ticket/7841

# Support an official and complete web services API (REST)
Champion: Sally Kleinfeldt
http://dev.plone.org/plone/ticket/7842

# Get rid of access rule on Windows, and supply detailed instructions
of the various ways you can make Plone answer on port 80 instead.
Champion (suggested): Sidnei
Proxy: Alan
http://dev.plone.org/plone/ticket/7843

# Improve membership and memberdata handling. (e.g. either addable and
editable properties, Membrane as part of core, or similar)
Champion: Wichert Akkerman
http://dev.plone.org/plone/ticket/7844

# Unify/simplify template/view/image/CSS customization, and make it
clear when to do this, and when to use Deliverance
Champion (suggested): David Convent
Proxy: Alexander Limi
http://dev.plone.org/plone/ticket/7845

# Create a group of "integrator liasons" that actively seek integrator
feedback to encourage more testing of alpha and beta releases,
especially regarding upgrade issues.
Champion: Donna Snow
http://dev.plone.org/plone/ticket/7846

# Support through-the-web creation of content types and forms with
possibility to continue development on file system.
Champion: Martin Aspeli
http://dev.plone.org/plone/ticket/7847

# Ship with more themes OOTB, possibly organize theme sprints if/when
Deliverance is delivered ;)
Champion (suggested): Veda Williams
Proxy: Jon Stahl
http://dev.plone.org/plone/ticket/7849

# Create a "Plone Inspector" that unifies and integrates various
developer tools to make it easier to "peel back the layers" of Plone
development.
Champion: Lennart Regebro
http://dev.plone.org/plone/ticket/7850

# Create a strong page compositing story for Plone
Champion: Calvin Hendryx-Parker
http://dev.plone.org/plone/ticket/7851

# Promote Deliverance as the branding/"corporate ID" mechanism
Champion: Paul Everitt
http://dev.plone.org/plone/ticket/7852

# Make sure all installers use Buildout as their base, and are
consistent across platforms. Create a story for integrating Buildout
recipes.
Champion: Steve McMahon
http://dev.plone.org/plone/ticket/7853

--
Alexander Limi · http://limi.net

Thanks PSPS folks for getting all the stuff typed in.  Considering the
amount of material produced, it is no small effort to get all those Trac
issues entered and visibility provided.  And thanks, Alex, for sending
out this overview mail to help crankstart the engine.

Jon asked each champion to send a short "I'm here" email when they
returned.  I'm the champion for 7852:

   http://dev.plone.org/plone/ticket/7852

What's this one about?  Since the word "theming" has also been used to
mean "skinning" and "templating", I'll temporarily use the word
"sitetheming" to avoid overlap.

Sitetheming will tackle:

- A very narrow part of the UI process

- Focused only on global site design

- Intended to make things significantly simpler for non-Plonistas or
fledgling Plonistas to weave their alistapart kungfoo.

While Deliverance will be used as a starting point, this PLIP will be
more about a sitetheme engine in general.

I started drafting a PLIP already.  However, I think there are still
questions about what "sitetheming" means in general.  So I plan to write
a series of blog posts, gradually introducing the motivations.

--Paul

On 2008-02-12, Alexander Limi <l...@plone.org> wrote:

Here is a brief summary of the current state of PSC:

- Some of this work has already been done, and will hopefully make
    it into the Plone 3 plone.org.

- I'm planning to attend the Paris sprint, where I will work on PSC (semi-)exclusively
    with help from Tarek ZiadÃ.

--
Alex Clark (http://aclark.net)

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

[cut]

Basically, the task will consist of:
- pushing the patch I have made into distutils for a muliple server .pypirc
file, for pyhon 2.6
- releasing in it as a Python 2.4 and 2.5 extension
- finishing the Pypi branch for PSC
- write a guide on how to release and promote a Plone product
- write a guide on how to set up a private and a public PSC (the idea here
is to demonstrate
  how a Plone company can work the same way with private and public
packages)

An extra guide I would also like to write is a buildout guide that would
explain how
to play with several pypi like servers.

Alex, if you can make it in Paris it is a great news, as we will be able
to synchronize our work.

++
Tarek

--
View this message in context: http://www.nabble.com/Strategic-Planning-Summit%3A-Next-Steps-tp15431...
Sent from the Core Developers mailing list archive at Nabble.com.

http://tarekziade.wordpress.com/2008/02/13/plone-strategic-summit-imp...

Regards

Tarek

--
View this message in context: http://www.nabble.com/Strategic-Planning-Summit%3A-Next-Steps-tp15431...
Sent from the Core Developers mailing list archive at Nabble.com.

I accept http://dev.plone.org/plone/ticket/7818 as requested.

I will submit a detailed plan to this list on Monday the 18th.

--
Sincerely,

Chris Calloway
http://www.secoora.org
office: 332 Chapman Hall   phone: (919) 599-3530
mail: Campus Box #3300, UNC-CH, Chapel Hill, NC 27599

- email to the list
- develop a timeline
- what does success look like?
- etc

--

~Spanky

I am not sure what to do next on my task :)

Tarek

--
View this message in context: http://www.nabble.com/Strategic-Planning-Summit%3A-Next-Steps-tp15431...
Sent from the Core Developers mailing list archive at Nabble.com.

1. Within one week, email plone-dev and announce yourself as a champion
2. Define the task, the deliverables and what success looks like
3. Put forward an action with a timeline
4. Solicit engagement and action

--
Alexander Limi · http://limi.net

Wichert.

--
Wichert Akkerman <wich...@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

Champions should put the key information and decisions into Trac so that
we can follow it. I think the initial flurry is more accessible on
plone-dev, but (for example) I am keeping my Dexterity notes in line
with the discussion and will update Trac when I've solicited a few more
inputs.

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

Wichert.

--
Wichert Akkerman <wich...@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

:jon

-----
---------
Jon Stahl
ONE/Northwest
www.onenw.org
--
View this message in context: http://www.nabble.com/Strategic-Planning-Summit%3A-Next-Steps-tp15431...
Sent from the Core Developers mailing list archive at Nabble.com.

http://plone.org/events/2008-summit

Let me know if you think otherwise! :-)

:jon

-----
---------
Jon Stahl
ONE/Northwest
www.onenw.org
--
View this message in context: http://www.nabble.com/Strategic-Planning-Summit%3A-Next-Steps-tp15431...
Sent from the Core Developers mailing list archive at Nabble.com.

--
Alexander Limi · http://limi.net

I can already see the galvanizing effects from your strong follow-through.

And... all you champions: you are the real heroes!  Keep up the great work!

best,
jon

cheers,

andi