Transcript

1.
Plone as aDevelopment Platform By[ a highly opinionated talk about the future of Plone from a Framework Team member, developer, project manager, consultant, loud mouth, and general advocate of change aka ] Elizabeth Leddy

2.
WARNINGAlthough this presentation seems to be filled with factoids, it is actally filledwith lazily validated stats, graphs that are extrapolated far beyondmathematical reason, and pirated imagery. It is highly likely that I havemisinterpreted historical results or became so blinded with anger aboutcertain things that I did not Google sufficiently or give good thoughts todecent alternatives. Except any statements about Grok. I’m confident there.More importantly, this is a very opinionated piece. Officially, much of this isaddressed by the Roadmap, which provides you with the important fluff youneed to sell Plone to your customers, clients, and neighborhood dentist. Inthe theoretical future, the roadmap will direct “official” processes andpeople will cheer and eat cake. For now: anarchy.In the meanwhile, I can only assume that I will firmly disagree with whatevercomes out of this because I am an asshole by nature and go full steam aheadwith the contents of this presentation. There is no intention to ruffle feathersor miscommunicate. I encourage all of YOU to get up and talk/blog/vlogyour vision for Plone, controvesy and all. Be loud, be proud, be Plone.

17.
In order to reach ‣ plone.org/roadmap where we are going ‣ Short Term Vectors of Inﬂuence for Plone 5 ‣ Improved calendaring and Community collections Realized Path ‣ Improved content development Excitement Direction experience (Roadmap) Beer TextMedium Term ‣ Dedication ‣ CMS-UI & Deco LiteBitterness Resistance to change ‣ WSGI & Ajax Plone 4 ‣ CMF forms -> Browser Views we must forgive where we have been Roadmap

18.
Does the steep learning curve pay off? Is this complexity still justified today? I need a platform. Customers need a CMS. You cant just start and say "If you want to see the complexity of Plone, you have to ask for it" when you dont know the system good enough to plan.Plone 3 Introduced Regression

23.
Using Recommended Practices:‣ Getting the site root‣ 6 ﬁles and 20 lines of code to add a new stylesheet‣ Touching so many ﬁles and modules: impossible to move quickly without referencing documentation constantly Hypoglycemia

26.
Developer Driven Development ‣ Think about the API ﬁrst ‣ Obsess about developer eﬃciency ‣ Use documented examples/ recipes to prove ease of use ‣ Contribute shortcuts from your everyday process and share them with coworkers and Make documentation less communityimportant with intuitive code!

28.
... makes hiringA thriving communityof happy developers... easier ‣ Plone will never be hip: move on ‣ Dangerously high levels of frustration in the blood ‣ Foster interest in long term career achievement ‣ At least it s not Java plone means getting hands dirty and drinking away your sorrows once you ﬁnish the day supton, #plone, January 2012

29.
‣ Plone developers cost much more than the competition because they are highly skilled + scarce ‣ Ramp up is too time consuming ($$$) ‣ Clients have the right to a saturated developer market should they move on to a diﬀerent company ‣ Developers have the right to feel prepared to move on within PLONE ‣ Diversity in quality of developers A large communityof happy developers... ... makes firing easier

31.
Who does Plone work for?"If you want a platform to be successful, you needmassive adoption, and that means you needdevelopers to develop for it. The best way to kill aplatform is to make it hard for developers to build onit. Most of the time, this happens because platformcompanies ... dont know that they have a platform(they think its an application)." Joel Spolsky

39.
Committing Not Just for Developers‣ Decide to commit to Plone the community. Too many people sitting on the fence results just leaves us with a busted fence.‣ Commit your project or company, no matter how small, to just 1 internal Plone culture improvement proposal this week. Can t code? Even better.

40.
Resolve to Initiate‣ Policy: All employees sign up for Plone on day 1 ‣ Paperwork: Contributor agreement, plone.org account ‣ Persist Plone culture (e.g. pre-install IRC)‣ Training: teach new developers how and when to ﬁle bugs and properly contribute ﬁxes‣ Mentorship: it s not just for ﬁnding the bathroom

42.
Resolve to Encourage‣ Test new versions of Plone. Stage, don t deploy. Upgrade and run your tests. Report back.‣ Make a policy to stop forking! It s a short term ﬁx with long term problems. Enforce it.‣ Set aside time for a company sponsored PLIP