1. Teams
1.1. Internationalization
1.1.1. Activity
1.1.2. Needs
1.1.2.1. Translation status report
1.2. Documentation
1.2.1. Activity
1.2.1.1. Feature documentation
1.2.1.1.1. Interviews with feature implementers
1.2.1.2. Improve existing documentation
1.2.1.2.1. Unification of existing docs on RTD
1.2.1.3. Update
1.2.2. Needs
1.2.2.1. Editing
1.2.2.1.1. Language cleanup for non-native English speakers
1.2.2.2. Writers
1.2.2.3. Developers to write/review docs
1.2.2.4. Improve developer.plone.org front page layout
1.3. Framework
1.3.1. Activity
1.3.1.1. Feature integration
1.3.1.1.1. Solicit
1.3.1.1.2. Review
1.3.1.1.3. Merge
1.3.2. Needs
1.3.2.1. PLIP Review checklist
1.3.2.2. Consistent leadership
1.4. Release Team
1.4.1. Installers
1.4.1.1. Activity
1.4.1.1.1. Windows installer
1.4.1.1.2. Better privilege seperation for root installs
1.4.1.1.3. Templer integration?
1.4.1.1.4. Vagrant
1.4.1.2. Needs
1.4.1.2.1. Good testing and bug reports
1.4.1.2.2. Build automation
1.4.2. Release Manager
1.4.2.1. Activity
1.4.2.1.1. Make releases
1.4.2.1.2. Ticket hit list
1.4.2.2. Needs
1.4.2.2.1. Time
1.4.2.2.2. Fewer packages
1.4.2.2.3. Writing help
1.4.2.2.4. Eyes on test failures
1.4.2.2.5. build.plone.org
1.4.3. Testing and Automation
1.4.3.1. Activity
1.4.3.1.1. Integration with FWT process
1.4.3.1.2. Tests on pull requests
1.4.3.1.3. Fabric scripts to set up new slaves quickly
1.4.3.1.4. Master has one core, lots of slaves, will make it easier to access main UI
1.4.3.1.5. Buildout failure is biggest cause of test failures
1.4.3.1.6. Responsibility is not to write tests, but to make testing easier
1.4.3.1.7. Robot/selenium
1.4.3.2. Needs
1.4.3.2.1. Needs a sysop
1.4.3.2.2. Public test results
1.4.3.2.3. Mr. Roboto
1.4.3.2.4. Slave VMs
1.4.3.2.5. Performance testing
1.5. Accessibility
1.5.1. Activity
1.5.1.1. Feature review
1.5.1.2. Accessibility guidelines
1.5.1.3. WCAG guidelines
1.5.1.3.1. Already WCAG 2.0a compliant
1.5.1.3.2. Working on ATAG compliance
1.5.2. Needs
1.5.2.1. Automated testing
1.6. Foundation
1.6.1. Activity
1.6.1.1. Sprint funding
1.6.1.2. New contributor agreements
1.6.2. Needs
1.6.2.1. Money
1.7. Security
1.7.1. Activity
1.7.1.1. Audits
1.7.1.2. Hotfixes
1.7.1.2.1. Estimate $40k worth of work put into most recent hotfix
1.7.2. Needs
1.7.2.1. Communications help
1.7.2.2. People
1.7.2.3. Sprint
1.7.2.4. Testers?
1.8. UI
1.8.1. Activity
1.8.1.1. Feature review
1.8.1.2. Best practices
1.8.1.3. Improve existing features
1.8.1.3.1. Content Rules
1.8.2. Needs
1.8.2.1. Designers
1.8.2.2. JavaScript developers
1.9. Marketing and Communications
1.9.1. Marketing
1.9.1.1. Activity
1.9.1.1.1. plone.com content
1.9.1.1.2. Why are you using Plone?
1.9.1.1.3. Selling Plone to your organization/institution
1.9.1.1.4. Fundraising
1.9.1.2. Needs
1.9.1.2.1. Leadership/organization
1.9.1.2.2. Market analysis
1.9.2. Communications
1.9.2.1. Needs
1.9.2.1.1. Identify
1.9.2.2. Activity
1.9.2.2.1. Interviews with interesting people
1.9.2.2.2. Updates from people working on important add ons and components
1.9.2.2.3. Team leader report
1.9.2.2.4. Provide editing capabilities for other teams
1.9.3. Website
1.9.3.1. Activity
1.9.3.1.1. plone.com
1.9.3.1.2. plone.org redesign
1.9.3.1.3. Planet.plone redesign
1.9.3.2. Needs
1.9.3.2.1. plone.com content
1.9.3.2.2. plone.org buildout
1.9.3.2.3. 4.3 upgrade
1.10. Admin & Infrastructure
1.10.1. Activity
1.10.1.1. Moved to Cloudflare CDN
1.10.1.2. planet.plone.org
1.10.1.3. github migration/maintenance
1.10.2. Needs