Lightning talks Thursday
Lightning talks on Thursday at the Plone Conference 2016 in Boston.
- collective.fingerpointing: select which events to log, like who logged in, who created content, etc.
- collective.lazysizes: lazy loading of images, iframes and tweets, while you scroll down the page. We reduced initial load times with 80 percent.
- collective.liveblog: content type for micro updates, bit like twitter. Automatically refresh using ajax calls.
Unofficial Zope on Python 3 status: http://zope3.pov.lt/py3
Today I worked on the same for Plone packages. So:
Unofficial Plone on Python 3 status: http://gil.badall.net/py3
Everybody was sure that Somebody would do a job. Nobody realised that Anybody could do it. Etcetera.
That is decision paralysis, waiting for anybody else to do the job. That is why we have teams in Plone. Maybe we can use the teams more on github. If you start looking for things to do, there are hundreds of issues for Plone. Split by team, it is less daunting.
There will be sprints this weekend, in this room. It is when a group of people get together for a project. Timo will be leading and assisting the sprints. Find him if you have questions.
There is a list of things to work on, you can add more. Please put your name in as a leader if you are up for that.
Buy one, get one free!
Thank you, Plone community, for all the documentation.
At http://themeforest.net you can find and submit themes as plugins for various systems.
http://themes.quintagroup.com is already doing this for Plone.
Why doesn't http://plone.com have something to sell? That was always my question. The Plone Foundation could get a share of the sales.
Money is not everything. You get to involve developers from around the world.
How to grow the community with little time and no money.
We have a small percentage of the market. Don't wait for marketing to rescue Plone. What made you come to Plone? Most of you know and like Python. You tinker with code.
IndyPy User Group started very small, now hundreds of people, with at least forty people meeting each month. In a Python group like that you are going to find Pythoneers, thinkers, tinkerers, prime targets for becoming a Plone person. Sponsoring is cheap: buy pizza. There are 700 Python meetups in the world. We can spread the message about Plone there.
How about creating a demo leader board? A competition for who gives the most demos for Plone.
I gave my first Plone training in the Arnhem conference. In Bristol there were four trainings, Bucharest three, lots of people were there. In Boston we had 19 trainings, 22 trainers, over half the people of the conference attended the trainings.
Trainings are hosted on http://training.plone.org. For various audience and topics. If you use the trainings and spot an error in the code or in the language, please report it.
I use cookiecutter to create a new project. I copy some settings over. Then I use zappa to deploy it to lambda from Amazon, or update it.
Works with Django, Flash and Pyramid. May work with Plone, but I have not tried it. Only Python 2.7, not Python 3 currently.
This is a Pyramid sprint in my home town of Ljubjana, Slovenia. 5 to 9 December this year. It would be great to have Plone people there too.
IRC comes from Finland, just like Linux, SSH, and Angry Birds.
On IRC you invest in the community, and the community invests in you. Useful IRC channels are #plone, #pyramid, #python-friendly.
But IRC is dying. Other mediums are Stack Overflow chat.
Some thoughts on training. I moved from end user to consultant and trainer.
I tried to teach configuring Plone in four hours.
We forgot to buy coffee. The guy made us a blend of coffee after a few questions. I did the same during the training. The people I taught were older, more experienced than I am. Who was the newbie?
Structure the information that you are teaching. That gives them a map.
Progressive exposure, teach them more and deeper as you go along. Don't start too deep. But: when the people already know enough, then you can dive deep quickly.
You guide people on their learning path.
You can be a trainer too!
mr.docs helps you write documentation for you packages. From the source it creates nice html, without you needing to setup Sphinx yourself. It checks for typos. It knows names of PyPI packages and adds it to the dictionary, which helps. You can let it create a fresh config for you to edit.
Since last week, we have an official Docker image for Plone.
See also his talk earlier today: http://maurits.vanrees.org/weblog/archive/2016/10/alin-voinea-docker-and-plone
Me again with another experimental package. :-) See https://pypi.python.org/pypi/experimental.publishtraverse