Saving the world from Plone agonyHosted by: Mikko OhtamaaPlone is not exactly popular and the recent development is driving away new adopters. This is a wake up call for the community to express some concerns and offer a plan for actions we should focus on to make Plone more attractive. A growing community is a healthy community: otherwise the last one of us shall turn off the lights on the last remaining Plone site. |
Event Details
This is not criticism towards people, but towards processes and goals.
Though Plone people do things right, they might not always do the right things. The core development focus solely on new features and infrastructure has left a gaping hole on the other end of the spectrum: how to have a soft start to actually adopt Plone for your software project.
I have been consulting hardcore Python development house whether they should use or not Plone for a problem where Plone would be a good solution. Eventually they decided to abandon the project, not because of the lack of Python skill, but because things are a mess and new mess is poured upon the old mess. The same pattern repeats on IRC #plone support channel every day. So sad.
Stop coding and think doing something which actually matters for Plone in long run. If you have a written a single line code for Plone you are in the audience of this talk.
One person cannot change the course of the things. This talk offers some advices what core developers and other high profile stakeholders in Plone community (you) should think on the future roadmap and sprint topics. Where are PLIPs which make Plone more fun?
We must focus on the users of Plone the project, not Plone the product. Because eventually if the developers lose interest adopting Plone due to many years of unsolved, but easily solvable, issues with the adoption we all die alone for the old age. It would be sad this to happen just because everyone was busy doing some other thing.
- People are interest building their own websites. We should focus doing changes making this easy as possible, beginning at the click of the link "Download Plone".
- Understanding that documentation is a method of communication and the responsibility of the author of the code. New PLIPs hurt Plone if developers and end users need to themselves figure out how to deal with new features. NO ONE is coming to write documentation for you.
- Improving the developer experience of Plone out of the box: How we can build together a path which will guide become from end users to developers to contributors
Please watch this introduction video of building your site on Plone by Sean Kelly from years ago and think how many things we have lost in Plone since those days.
View the slides
Event Info
Session time: 45 min
Back to the complete talk list