During the Plone Conference, as usual, I made summaries. You can see them all by checking the ploneconf2014 tag. I do this for you, with pleasure, but also for myself. Now I can read my own notes and gather my thoughts and remember what I actually heard.

Here are a few highlights.

• Plone 5 is coming. I would be very surprised if a final release is done this year. I would be even more surprised if it did not happen in 2015. I may want to try to redo my own website with the next alpha of first beta version.
• Transmogrifier can be a good way to migrate sites. I have some experience with it already. I may want to use collective.jsonify to migrate my current Plone 2.5 site...
• The new Plone 5 theme is called Barceloneta. It uses Diazo. It uses the new resource registries that you can configure in the Plone UI, replacing the old portal_css and portal_javascript. Your custom Plone 5 themes should do that too.
• A lot is happening in Javascript for Plone. The conference gave food for thought on AngularJS and json. A json api on top of Plone is being worked on, which can help in creating a completely different UI if your website needs it, or it can make showing Plone content in a completely different framework possible. Mockup should be the basis for your widgets or other Javascript work. Quote: We have to get the whole community into thinking 'Javascriptish', really push it into the head of more developers.
• Documentation is (as always) being worked on, including versioning. Using five.grok in code is not officially recommended practice (it should work fine, but too many people in core development do not like its 'magic'), so the documentation that uses it is being copied to a grok-only part and edited in the original location to use best practices.
• The Plone Intranet Consortium is working on improving Plone as an intranet. Several companies are banding together, with online sprints each Wednesday. The plan is to give the license of the code to the Plone Foundation. But for the moment development is tightly controlled so that effort is focused, with a design first approach. Contact us if you want to join.
• The Plone Roadmap team talked about the roadmap and vision for Plone in 2020. Most important is what we want to keep, which is first and foremost: the community. Particularly, the Roadmap Team is the community, which means you. Favorites for changing: have one canonical way to do something (practical: improve plone.api); create a json api to help enable new stuff; improve end user experience.

I had a great time. Thank you, each and every one. Hopefully see you next year in Bucharest.

See list on https://titanpad.com/5oi4wTa0oP

p.a.contenttypes: working on custom type migration, Topic migration, portlets, working on broken diffs for various content types

Mosaic: lots of bug fixing, field tiles are working, tomorrow application tiles.

Working on theming editor so it works on Plone 5. Showing people how everything works together. Plans on improving stuff.

Clean Diazo theme. Slimmed Mockup repo. Resource Registry is tricky, migration.

plone.api: work on getting PLIP out for inclusion in core. Adding new modules. We ate the chocolate.

Heroku: some stuff got pushed. Idea for demo pack for the paragon add-ons.

plone.login: password strength as pattern, wrapping forms to make it easier to customize, control panel to indicate where it should be redirected to after login.

Plone testing: migrating Products.contentmigration to plone.app.testing.

CI/Jenkins: setting pipelines to get a quicker response.

Documentation: no more magic in the repo, working versioning, docs for Plone 3.3 now look like Plone 3.3, busy killing grok examples, 12 or 14 new contributors today.

Plone training: came up with plan to improve the story, plan for automated screen shots. Maybe reintroduce the old theme editor from David Glick, as for now that is easier.

Themes on docs.plone.org. Version and language switcher.

Rapido: fighting with mockup theme editor. New field type for Rapido.

Plone control panels: figuring out how to fix loose ends, work underway.

PloneEDU: new folder at https://plone.org/edu. Docs on configuring, case studies.

Intranet: getting everyone up to speed, get buildouts running, code and communications, patternslib intro, migrating Plone Intranet to Plone 5a2, updated documentation, design driven approach is a bit different than people are used to so we talked about that, investigating how we can best use Plone's form handling mechanisms with forms that are completely defined in an html design, checking our conceptual thinking, looking at switching between Diazo themes on the fly.

Japanese bugfixes: quite a few mugs were fixed, see you next year in Tokyo.

Existdb: making integration possible.

Installers: providing moral support to Eric as he was releasing, documentation driven development, ansible build kit documentation nearing completion at https://github.com/plone/ansible-playbook, docker documentation at https://github.com/plone/plone.docker, please read those and give us feedback telling us if it is clear and makes sense.

RESTful json api. Added notes from open space, rough description of Hydra, work on json api for news items and folders, and for search which is really hard to do.

Ecosystem KGS, add-ons installing through the web: getting information, looks promising.

2020 discussion: Sally is gathering all the sticky notes that people wrote.

Plone releasing: releasing packages, people: please add changelog entries for changes that you do.

Thank you to the hotel, video and sound guys, our sponsors. Thank you Netsight team. Astra has arranged all the logistics and organized me. Thank you Scott or Wifi. Thank you to my wife, who felt very welcome.

Audience: "Thank you Matt!"

Thank you Plone community.

Not the end. Sprints tomorrow.

Looking forward to next year. What about 2015?

Alex Ghica. http://eaudeweb.ro. We will do the next Plone conference in Bucharest in Romania. Part of Europe, EU, NATO, so all is safe. :-) Venue is a five star hotel, city center, well connected. International airport. Ticket from London if you book it now is 20 euro. 12 to 18 October 2015. Thank you Elena Melis. Thank you Maurizio Delmonte as Sprint manager. Thank you Plone Foundation.

Present: Alexander, Andy, Cris, Érico, Paul, Steve from the board, plus lots of foundation members.

Paul opens the meeting. Everyone is welcome, only members can vote.

Items on the agenda: the old board leaves, new board enters, annual report.

Thank you ambassadors. We had new members, let's give them an applause. Thank you sponsors. Thank you sprint organisers and sponsors. The Foundation sponsors sprints, but that is only a beginning amount to help start things off.

We made a slight loss, we are not super rich, but we are secure. We have seen that the more money we spend the more money comes in, so I recommend to continue that.

Steve moves acceptance of the annual report, Philip seconds. Motion passes unanimously.

New board: seven nominations for seven positions, so no elections needed. If you prefer elections, run for the board, we love it.

Steve moves to appoint the board. Érico seconds. Motion passes unanimously.

Thank you to the outgoing board members, Érico, Andy, Spanky.

Welcome new board members: T. Kim Nguyen, Chrissy Wainwright, and Carol Ganz, who join Paul Roeland, Alexander Loechel, Steve McMahon, and Cris Ewing.

Officers will be appointed in the board meeting next week.

Chris C. moves to adjourn the meeting, several people second. Unanimously approved. Meeting is adjourned until next year. Place is hardly a secret, but will be announced later today.

More info on the Plone Foundation can be found at https://plone.org/foundation