Plone Open Garden 2014

Get Started. It's Free
or sign up with your email address
Rocket clouds
Plone Open Garden 2014 by Mind Map: Plone Open Garden 2014

1. Generational relay

1.1. "Open Advice"

1.1.1. Turnover in commuinty

1.1.1.1. Common across all long running projects.

1.1.1.1.1. Debian: 7 years

1.2. Poor planning for succession

1.2.1. Loss of leadership

1.2.1.1. Limi

1.2.1.1.1. Figurehead, rallying point

1.2.1.2. "The open source world does many things brilliantly, but one thing it does badly is planning for leadership succession." - Glynn Moody, Learning from Diaspora

1.2.1.2.1. Cultivating that next generation of community leaders

1.2.1.3. Accountability

1.2.1.3.1. No team operates on an island

1.2.1.3.2. Not producing, we find new leadership

1.3. Change in community

1.3.1. Expansion

1.3.1.1. Active core contributors has increased by 16% over the past 12 months

1.3.1.1.1. Losses have been replaced by a larger number of contributors

1.3.2. Atrophy of "soft skills"

1.3.2.1. We've placed so much emphasis and praise on the idea of the"core committer" that we've lost sight of all those non-code contributions we need to survive.

1.3.2.1.1. Let's go with "Core Contributor" instead

1.3.2.1.2. Stop diminishing (unintentionally) non code contributions

1.3.3. Community is larger and more diverse than ever

1.3.3.1. Geographically

1.3.3.1.1. Expanded from traditional European and US roots

1.4. Bringing in new users

1.4.1. Evangelism

1.4.1.1. "Whenever we hire someone new, I show them one of [Sean Kelly's videos](http://plone.org/documentation/movies) so that they know just how great this system is and they say 'Wow, Archetypes is outstanding!' and then I have to try to explain everything that's changed since 2006."

1.4.1.2. David Bain's Diazo demo

1.4.1.3. Timo Stollenwerk: Typo3 vs Plone debate

1.4.2. Turning users into contributors

1.4.2.1. Increasing involvement

1.4.2.1.1. Situated Learning

1.4.2.1.2. Peripheral Access

1.4.2.1.3. Identity Construction

2. Impostor syndrome

2.1. Denise Paolucci: "Kicking impostor syndrome in the head"

2.1.1. Plone suffers, not just on an individual level, but on a community/project level

2.1.1.1. Denise's Recommendations

2.1.1.1.1. Positive psychology

2.1.1.2. Part of this is our culture of extreme pragmatism

3. Teams

3.1. Internationalization

3.1.1. Activity

3.1.1.1. Translation of

3.1.1.1.1. Core content

3.1.1.1.2. Documentation

3.1.1.1.3. Newsletters/releases

3.1.2. Needs

3.1.2.1. Translation status report

3.2. Documentation

3.2.1. Activity

3.2.1.1. Feature documentation

3.2.1.1.1. Interviews with feature implementers

3.2.1.2. Improve existing documentation

3.2.1.2.1. Unification of existing docs

3.2.1.2.2. Style guide for add-ons

3.2.1.3. Update

3.2.2. Needs

3.2.2.1. Editing

3.2.2.1.1. Language cleanup for non-native English speakers

3.2.2.2. Writers

3.2.2.3. Developers to write/review docs

3.3. Framework

3.3.1. Activity

3.3.1.1. Feature integration

3.3.1.1.1. Solicit

3.3.1.1.2. Review

3.3.1.1.3. Merge

3.3.2. Needs

3.3.2.1. PLIP Review checklist

3.3.2.2. Consistent leadership

3.4. Release Team

3.4.1. Installers

3.4.1.1. Activity

3.4.1.1.1. Windows installer

3.4.1.1.2. Better privilege seperation for root installs

3.4.1.1.3. Templer integration?

3.4.1.1.4. Vagrant

3.4.1.1.5. Third-Party Installers

3.4.1.2. Needs

3.4.1.2.1. Good testing and bug reports

3.4.1.2.2. Build automation

3.4.2. Release Manager

3.4.2.1. Activity

3.4.2.1.1. Make releases

3.4.2.1.2. Ticket hit list

3.4.2.2. Needs

3.4.2.2.1. Time

3.4.2.2.2. Fewer packages

3.4.2.2.3. Writing help

3.4.2.2.4. Eyes on test failures

3.4.2.2.5. build.plone.org

3.4.3. Testing and Automation

3.4.3.1. Activity

3.4.3.1.1. Integration with FWT process

3.4.3.1.2. Tests on pull requests

3.4.3.1.3. Responsibility is not to write tests, but to make testing easier

3.4.3.1.4. Robot/selenium

3.4.3.2. Needs

3.4.3.2.1. Performance testing

3.5. Accessibility

3.5.1. Activity

3.5.1.1. Feature review

3.5.1.2. Accessibility guidelines

3.5.1.3. WCAG guidelines

3.5.1.3.1. Already WCAG 2.0a compliant

3.5.1.3.2. Working on ATAG compliance

3.5.2. Needs

3.5.2.1. Automated testing

3.6. Foundation

3.6.1. Activity

3.6.1.1. Sprint funding

3.6.1.2. New contributor agreements

3.6.2. Needs

3.6.2.1. Money

3.7. Security

3.7.1. Activity

3.7.1.1. Audits

3.7.1.2. Hotfixes

3.7.1.2.1. Estimate $40k worth of work put into most recent hotfix

3.7.2. Needs

3.7.2.1. Communications help

3.7.2.2. People

3.7.2.3. Testers?

3.8. UI

3.8.1. Activity

3.8.1.1. Feature review

3.8.1.2. Best practices

3.8.1.3. Improve existing features

3.8.1.3.1. Content Rules in 4.3

3.8.2. Needs

3.8.2.1. Designers

3.8.2.2. JavaScript developers

3.9. Evangelism

3.9.1. Marketing

3.9.1.1. Activity

3.9.1.1.1. plone.com

3.9.1.1.2. Why are you using Plone?

3.9.1.1.3. Selling Plone to your organization/institution

3.9.1.1.4. Selling Plone outside of your organization

3.9.1.1.5. Fundraising

3.9.1.2. Needs

3.9.1.2.1. Leadership/organization

3.9.1.2.2. Market analysis

3.9.2. Communications

3.9.2.1. Needs

3.9.2.1.1. Identify

3.9.2.2. Activity

3.9.2.2.1. Interviews with interesting people

3.9.2.2.2. Updates from people working on important add ons and components

3.9.2.2.3. Team leader report

3.9.2.2.4. Provide editing capabilities for other teams

3.9.2.2.5. Mailing list

3.9.3. Website

3.9.3.1. Activity

3.9.3.1.1. plone.org redesign

3.9.3.1.2. Planet.plone redesign

3.9.3.2. Needs

3.9.3.2.1. Developer, integrator help

3.10. Admin & Infrastructure

3.10.1. Activity

3.10.1.1. Moved to Cloudflare CDN

3.10.1.2. planet.plone.org

3.10.1.3. github migration/maintenance

3.10.2. Needs

4. Releases

4.1. Plone 5

4.1.1. Features

4.1.1.1. New folder contents structure

4.1.1.1.1. Batch operations

4.1.1.1.2. Better Drag & drop

4.1.1.1.3. Simplify the management of large volumes of content

4.1.1.1.4. Filtering

4.1.1.2. TinyMCE 4.0

4.1.1.2.1. Cleaner

4.1.1.2.2. Faster

4.1.1.2.3. Mobile friendly

4.1.1.2.4. Clear upgrade path

4.1.1.3. New theme

4.1.1.3.1. Diazo based

4.1.1.3.2. Out-of-the-box

4.1.1.3.3. CSS font icons

4.1.1.3.4. Fewer CSS/JS files

4.1.1.3.5. Bootstrap

4.1.1.3.6. Tested!

4.1.1.4. plone.app.contenttypes

4.1.1.4.1. All the content types you know and love, but backed by the more efficient Dexterity engine

4.1.1.5. FormWidgets

4.1.1.5.1. Modernize our form widgets

4.1.1.6. Chameleon

4.1.1.6.1. 15-20% Faster page rendering

4.1.1.7. plone.app.toolbar

4.1.1.7.1. Diazo integration without the editing interface headache

4.1.1.8. Development "paradigms"

4.1.1.8.1. JavaScript

4.1.1.8.2. CSS

4.1.1.8.3. plone.api

4.1.1.9. portal_skins deprecation

4.1.1.9.1. Clear up old tickets (no one wants to touch)

4.1.1.9.2. Standardize

4.1.1.9.3. Testable

4.1.1.9.4. All of the actual CMS functions that we've been ignoring for years because they mostly work

4.1.1.10. Login revamp

4.1.1.11. plone.app.events

4.1.1.11.1. Recurring events

4.1.1.11.2. Time zone support

4.1.1.11.3. Modern date input widget

4.1.1.12. Core package consolidation

4.1.1.12.1. Makes me happy

4.1.1.12.2. The number of packages is TOO DAMN HIGH

4.1.2. Themes

4.1.2.1. Core sets best practices

4.1.2.2. Clean up, move on

4.1.2.2.1. Optimized, leaner code means easier customizations and faster experience for end users

4.1.2.3. Externalize/modernize js/CSS

4.1.2.4. Faster to spin up new developers, back and front end

4.1.3. Achievable

4.1.3.1. This is a set of things that we can do

4.1.3.2. And it's still pretty sexy

4.2. Future

4.2.1. "Plone 2020"

4.2.1.1. Stagnation of Zope 2, move to Python 3

4.2.1.1.1. Choices

4.2.1.2. Plone 5's increased separation from backend

4.2.1.2.1. Allows us to make larger changes while minimizing impact on existing sites

4.2.1.3. No concrete action on this yet, but we're discussing it