Re-hashing this previous discussion because I think it's still very relevant...

> Then he goes a lot into how there can only be one CMS left standing (very
> highlander) and how that can be Drupal etc etc. I can start to see where
> these drupal people get their zeal from now :)

yes, in his DrupalCon keynote this year, he said that Drupal/Joomla
and Wordpress would be the only OSS CMS to survive and all others
would fade away.

> Thankfully Plone's UI seems to be in great hands. The simplification of the
> framework side of plone has had some great noises made but IMHO we seem to
> have a great process for adding features and frameworks but it's unclear how
> that process works for simplifying the framework.

Yeah, the framework, for all its benefits, has turned away a lot of
would-be Plone people because it is too complex and unapproachable.
We need to focus on making it more approachable if we want to continue
to attract new people to Plone.

> We have awesome demos of deco and its easy for all of us further down the
> chain to see where we are headed UI wise,

I found it very interesting that Dries was in Limi's talk about Deco
at CMSExpo. I think Dries realizes that Drupal could learn a few
things about Plone's simple and unified UI.

This is also a very telling post comparing Django to Drupal.
http://birdhouse.org/blog/2009/11/11/drupal-or-django/

The 87 comments are also very telling.

> but what would be the equivalent
> of a vision outlining a simplified framework for developing with plone?
> Limi highlighting 25% less code in plone 4 is pretty cool. Wouldn't it be
> great to see 50% less concepts needed to learn plone in plone5?

Yes, I agree.

>> 7) They are still, out-of-the-box, a great blogging platform, and if
>> you're using Drupal as a "news to the home page site" with a few static
>> pages, it's easy and fast to configure.
>
> Dries talks about Distributions which isn't something we've done much with
> in Plone. Drupal seems to be advertising its out of the box intranet
> distribution on drupal.com and Plone doesn't have one and yet Plone is a
> better match.
>
> The points Dries makes about distributions are also really interesting.
>
> "There is a risk involved with distributions as well, which means that we
> need to approach them the right way. The risk is fragmentation, and it is
> why I feel it is important that distributions build on the usability
> patterns set by Drupal core. "

I think distributions is something we should seriously look at within
the Plone community. See this blog post I wrote back in 2007 about
creating Plone distros.
http://piktipi.wordpress.com/2007/06/03/natea-creating-easy-to-install-plone-distributions-with-buildout/

We currently have Plinkit (for libraries) and Plumi (for video
portal). Where is the PloneEdu distribution, or the PloneGov
distribution. Where is the distro for newspapers or media
organizations?

For building a social networking site, Wordpress has BuddyPress
(http://buddypress.org) and Drupal has DrupalGardens
(http://www.drupalgardens.com/) for building marketing sites,
OpenPublish (http://openpublishapp.com/) for publishing industry and
OpenPublic, a Drupal distribution for open government.
http://www.phase2technology.com/press-release/phase2-technology-announces-openpublic-drupal-distribution-federal-agency-use-satisfy-

I think if we were to nurture smaller subsets of communities within
the larger Plone community around these distributions, we could start
to see more penetration into these markets. The PloneEdu efforts that
Mike Halm at PSU is leading is a step in the right direction. Let's
hope that this serves as a model for others to follow.
http://weblion.psu.edu/ploneedu

Nate


-- 
// Learn the easiest way to theme Plone! //
http://plone-theming-with-deliverance-natesig.eventbrite.com/

Nate Aune - [email protected]
http://www.jazkarta.com
http://card.ly/natea
http://tungle.me/natea
+1 (617) 517-4953
_______________________________________________
Evangelism mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/evangelism

Reply via email to