plone.org: several tickets fixed, Github integration login to plone.org (awesomatic), carousel responsive, we are going to upgrade to Plone 5.

Javascript, patterns: we merged the tests of mockup into patternslib and they all pass, debugging an issue with modals (config of first modal overrides all other modals), working on toggle pattern, autofocus pattern.

Adjusting drop-down menus to Plone 5.

Started porting to Plone 5: PloneGlossary, loginlockout, PloneKeywordManager, sc.sociallike, collective.disqus, collective.geo (control panel is super magic, so we need help there).

Fixed i18n issues in CMFPlone, fixed link in Plone front page translations.

New installer has graphical user interface, screenshots in docs.plone.org. Cleanup DNS, infrastructure for upcoming plone.org.

Documenting basic dexterity usage with a screen cast.

Plomino 1 to 2 design migration.

docs.plone.org: include plone.app.event, new way for robot screen shots in CI with PhantomJS instead of Firefox (far less irritating: not having browser windows pop up all the time). Cleaning up posters, nice version in Illustrator. Role-up template (the standup posters).

Accessibility: several improvements; Max found out the reason why our toolbar was not working, basically we were using aria-hidden instead of expanded.

Marketing of Quaive (Plone Intranet).

plone.app.contenttypes custom migration changes for using on Plone 4.

plone.app.contentrules.

plone.app.multilingual on Plone 4 with Archetypes.

I once followed a white rabbit into the world of Plone, lost in Wonderland. Searching for the big picture. Now working on an organogram of how Plone works. Explaining Plone from the outside. Let us think of Plone as a business of cars: where do you get cars from, road, passengers, taxi drivers (editors), fleet management of several Plone Sites, salesmen, car companies. Which teams belong in there and which roles do they have? What is done for a new car/Plone version? Research for new content type frameworks.

Plone 5 upgrade guide is being worked on, please continue adding documentation or report issues. Document your troubles and your solutions.

Alec Ghica: I hope you enjoyed the event and your stay in Rumania. Thank you to our sponsors for making this happen. Thank you to my colleagues from all the web. Thank you all the trainers. Thank you Paul for your help organizing everything.

Paul: Thank you Alec! Tomorrow sprint. Coffee at 9:00. Finally: the board has received a nomination for organizing the conference of next year. Step forward Eric and Sally.

Eric and Sally: What do you think of when I say Boston? Red Sox. Patriots. Boston Celtics. Pilgrims. Brakers. Maybe Aerosmith. Blue Man Group. Symphony Orchestra. One of the oldest public libraries. Old North Church. Freedom trail. Boston massacre. USS Constitution tallship. Public gardens. Old cobble stone streets of Beacon Hill. Fall colors. Harvard university. MIT.

But we hope you will be thinking of Plone too. October 17 till 23, 2016, the Plone conference will be in Boston, US. Two venues: MIT Sloan school of management, and Microsoft New England research center. Important: inclusivity, community and collaboration. Power and flexibility of Plone. Strong outreach to new Plone users. Brought to you by Sally, Kim and me, Cris. B there!

The old saying: The cobblers' children have no shoes....

Our own website (Jazkarta) was so outdated, we had to fix it. Now we finally did an upgrade and went straight to Plone 5. There were multiple requirements: more imagery, have tiled landing pages, responsive. To get this together we got together and organised a sprint.

The ingredients for the new site: Dexterity types and behaviors. plone.app.imagecropping, collective.cover, collective.relatedslider and collective.isotope.

With Dexterity, we created two new content types: Projects and Team members. Projects store metadata on the projects with classifications like project type, technology, Location of the project customer. The team members capture the more personal feeling of our company, show who we are.

Critical Dexterity behaviors:

• Images: Use them on Images, projects and team members.
• Related items: for pages, projects and team members.
• The collection behavior was also installed on pages, projects and team members.
• A new behaviour related slider was added as well.

Jazkarta upgraded collective.cover for Plone 5. There's a branch to support it, but it still has to be merged.

collective.relatedslider piggybacks on the related items and collection behaviors to show a slider on the page. Manual items can be done through the related items. But you can add the collection behavior and enter criteria for selecting the items in the slider. relatedslider creates a viewlet below the content. JqueryTools Scrollable from plone.app.jquerytools then shows the image.

collective.isotope provides a new view for Folder and Collection types, using the Isotope Javascript plugin: http://isotope.metafizzy.co. It has an open source license. Demo: it is similar to a faceted search, but then for a smaller number of items with a nice animated behavior, filter on categories, sort by property. It provides vertical and tiled formats, uses the Catalog metadata for filtering and dynamic sorting is on the TODO list. To control the view there are site wide settings.

How to set up the site: define the crop sizes to fit the design. Then start adding content with images. plone.app.imagecropping then allows you to create different crops for every lead image, thumbs for the related sliders and isotope, but preview sizes for, for example, cover tiles. plone.app.imagecropping is awesome and should be in core, but it needs some work. You sometimes don't see when you remove cropping information you have set before and there are some caching issues. Lots of frustation while doing content editing.

Reflections on Plone 5: Nice editing experience with a few glitches. While doing content editing Sally hits view instead of edit and vice versa. And there are no icons visible for add-ons in the toolbar, like collective cover's compose and layout views. The new markup on the Barceloneta thema makes theming easier with less, modifying variables. But the new toolbar makes responsive editing a pain: a fourth column you have to take into account, for example with setting breakpoints.

Questions: About the break points, there are css classes you can use to set up the breakpoints, which you can use with Barceloneta.

[Thanks to Fred van Dijk for this guest blog.]

[I missed the first part. Lunch!]

Marketing and branding. Well done in Plone 5. Always room for improvement. Board will talk about this, but it is a community job. At Sorrento and later the Board talked about maybe hiring someone to do branding globally, but currently this is not done, we were busy with Plone 5. Sometimes people volunteer, but then do not follow up on it. There can be no one, global marketing message: every country or area has different needs, different ways of communicating what we are. You can edit the posters for your own country, see http://plone.org/foundation/marketing. The message we send out has become less technical and more humanized, which has been well received.

Paragon has just been revived, we will have a list of add-ons that of general interest, high usability, and Plone 5 compatible.

Diversity. Membership committee would like to have more diverse members of the Plone Foundation. Technical skills are not required to become a member. Good to give demos to various persons, so they can get addicted to our community. I head that the first two training days were very good for newcomers, but some then had problems following the talks by all these crazy technical people. But we had hardly any people registered for the web master and end-user training. Reach out to people: we want you here at the conference. You may get more local people for this part, for talks about basic Plone things, you may not travel half the world for that. Note that lots of developers don't know what they can do with Collections and just code it themselves using the catalog, they can benefit a lot from training. Having a 'better half' (family) track on conferences would be good.

Documentation: synchronization between Plone 5 release and documentation would have been good, even simply some notes that most add-ons will not be ready yet. For plips: require to add documentation. Plips should have a skeleton that already has this documentation. Sven and Paul cannot write everything.

Installers. For Windows it is hard. Steve is working on something. He can use help. A system sanity check would be good, at least for missing libraries that we cannot install ourselves in the installer. Maybe something like that is already in there. We have a big download button on plone.org, but having a button for the cloud would be good too. Sven says this is almost ready. Maybe have a distribution with several good add-ons on it, but who is going to maintain this list and the distribution?

Communication. http://plone.slack.com is available, as alternative for irc. Experimental. http://community.plone.com for community discussions and for example for team notes. Email is not really working there, at least not replying, currently. The developer mailing list is still there.

Enterprise search and ZCatalog. We recommend collective.solr. But alm.solrindex also works, right? And has for years. Can be on the recommended list as well, so create a pull request for the docs.

What is the next disruptive thing coming our way? Difficult to say: streaming video: yes. Apple Newton: wrong timing.

Interactive content could be the next thing. Viewers control the content and choose what to do (next).

Media assets, what do we have now? Text, images, audio, video.

The browser is a stage. Sliders, accordeons, carrousels. Timing matters, video is linear, only one thing to control.

Another example of new interactive content: the scrolling one-pager, where you scroll down a page and there's a parallax effect, scrolling animations, movies. etc. Java and flash enabled these kinds of things earlier but didn't catch on that much. HTML5 and javascript are stronger enablers.

Why is interactive content interesting for business? Offer all the overload of content in different representations. Multichannel publication is another thing: re-use content in different ways. Tell different stories, tell the same story in a different way.

Warning: keep your assets under control, the cloud is a dangerous place for your media. Have a media archive internally. Control metadata. EXIF can be corrupted by external (cloud services). Also usage and license tracking is difficult if not impossible with many cloud hosting services. The best future is now: the browser has become very powerful.

Digital signage: public screen, led walls, info screens. But you need a CMS as a backend to provide the data. Display devices have become powerful: PDF display, 3D, panoramic images. Audio/Video. And you can do this on mobile phones, tablets, pc sticks you just insert in the back of your TV.

Something else that's coming: gamification. Interactive solutions, touch is getting common to interact with content. Don't overdo control though, sometimes people want to relax and sit back to enjoy the content.

Panoramic views are quite old already: viewmaster toys, 3D stereo images with special goggles and the stereoscope. New VR technologies allow to give viewers an overview of an area or geography, but imaging showing an overview of content, documents, images on a virtual 3D wall in front of you. Or overlay reality with computer content.

Devices now: Google Glass, Oculus Rift. Expensive, but costs start to decrease. Google Cardboard. In 2016 the consumer version of Oculus Rift will be coming. VR viewers widen your horizon. A monitor only gives you a very small view angle. But a headset will scroll when you move your head, giving you the illusion of a huge view angle and it will become an immersive experience.

Navigation in 3D. New input devices: display control items as overlays in the virtual environment, when you look at control links you can jump to them. The CMSes will have to support these new controls and directives, with extra assets and application settings to control these 3D devices. 3D impresses: it's like being there, the context is always right and memorizing (the experience) is more intense.

Plone will need to adapt to make this future happen and support new approaches and integrate these technologies. There's more than the web. Plone already has a lot: secure base functionality, can deal with unstructured data, python to script a lot, workflow process control.

[Thanks to Fred van Dijk for this guest blog.]