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.]

Manual QA: install prereleases when Eric Steele announces them? Partially. Also: make sure people other than consultants can use it, so having updated documentation, if only a note that most add-ons have not been updated yet.

We had a Launch Team, with representative of other teams. Can we turn that into a QA team? Meeting say once a month, coordinating, checking if existing teams can handle things.

Isn't it then a Process Team? Another layer. Multiadapter.

Sounds a bit like a daily executive team.

No, the release team may say we are ready for a release. But then we need to check with other teams. The technical side has a process, but the non-technical side not really. With Plone 5 a lot of technical stuff has happening and the non-technical side was rushing along trying to catch up.

The hotfix was there, the community was informed. But then there were updates to the hotfix and the communications team was not informed.

For releasing, we may start doing real alpha, beta, release candidate releases, and then do an actual final release with only a version number change. That may also give you time to update other parts, like communication and docs. And you can tell the release team to hold off. For docs, we need to include the latest stuff, even if it is automatically, but we need a moment to check it.

Problem is when technical is moving along fast and other teams cannot catch up. Technical is used to just pushing on regardless.

Have email addresses for teams.

Changelogs: declare if something is a bug fix or feature or something else. Check this automatically if possible, see if it is declared. Have best practices. Have a CONTRIBUTING.rst file in each repo: this automatically ends up on github when creating an issue or pull request.

Make it visible if all teams are ready, whether manual or automatic.

For major releases, you can prepare better, because there should be plips.

What checklists do we need?

Communications team:

• Input: changelog, the interesting 'cherries'. Saying how to get to the new features (go here, check this box). For changes: is it a feature, a bug fix, is it for developers or end-users.
• Output: news item, newsletter, social media, progress report, update feature list on plone.com. What's in it for end-users, developers, that decides what output we need. How are the changes significant.

Everyone is welcome, only members of the Plone Foundation can vote.

There is a report of the last year. Together with other documentation, see https://plone.org/foundation/meetings/membership/2015-membership-meeting

Thank you to the membership committee, ambassadors, Google Summer of Code, including talk of student Prakhar Joshi today.

Some activities this year: Plone Symposium Tokyo, Strategic Summit Sorrento. Sprints funded: FourDigits Anniversary Sprint, Munich Theming Sprint. There were lots more sprints.

Launch of http://plone.com. Many thanks to many people!

We were present in PyCon, EuroPython. Hardly any marketing money applied there, more guerilla marketing, with lots of T-shirts at the right time.

Plone 5 launch, which we had nothing to do with, except that we launched a Launch Team for issues that are not code related. Much better than the Plone 4 release which was basically dumping a tarball on the website. Thanks!

CMS Garden Brochure with a section on Plone, working together with other open source CMSes. We are not each others enemies, we have other fish to fry. Thanks Maik, Armin, Christina.

Relicensing of Mockup to BSD.

Trademarks renewed or reissued, for another ten years.

New foundation members: Kees Hink, Sally Kleinfeldt, Guido Stevens, Alin Voinea, Christina McNeill, Peter Holzer, K K Dhanesh, Fred van Dijk, Roel Bruggink, William Fennie, Cris Ewing. You are very welcome to nominate yourself for membership, don't be shy, no impostor syndrome please. :-)

Nathan van Gheem is representative on TinyMCE user advisory board. OSI membership. Social media support by Christina.

Thank you to all our sponsors. New: university sponsors. The first is the University of Namur, Belgium.

Financial balance: we are more or less even.

Philip Bauer moves to approve the report. Cris Ewing seconds. Everyone says aye. Report is approved.

Now a new Foundation board of directors.

Cris and Steve are leaving the board. Nominees for the next board. Existing: Kim, Alexander, Paul, Carol, Chrissy. New: Philip, Victor.

Christina moves to approve the new board. Alexander seconds. All say aye. We have a new board.

Any pressing concerns that you want to ask?

Alexander moves to adjourn the meeting, Philip seconds. All say aye.

[I missed the first lightning talks.]

bin/hostout app01 docker