Andreas:while I dislike the tone used by you on this and other threads, I agree that we have a huge problem with Plone 4.3, Dexterity 2.0 and Plone documentation.
this is not the first time I say this here, but seems to me it takes someone well respected on the community, like you (yes, I respect you a lot, and that's why I argue with you sometimes), to loud the voice for people starting worrying about the state of Plone development.
as someone who has been using Dexterity for more than 2 years and having suffered even worst experiences than you when following the documentation, I have to say that we need to fix this.
let's face it: we're not gonna fix it by ourselves; Mikko, Giacomo and other guys have done a really great job trying to do it, but the mess is so big that I think we need to act on a different way.
I have said before that we need to pay someone for this task, an expert on the field and best if this person came from outside the Plone community.
I will never buy a Plone book, but I will put $100 USD from my pocket for this.
I think this could be a solution because, as most of you, I have no time to work on this (I'm not even able to document my own packages) and we spend a lot of time (and money) trying to guess how things work.
I agree with Jens that we need to deprecate all documentation still living on plone.org and I think we should also tag it according to Plone's versions.
also, I believe no new release should be done if documentation is not fully updated and we need to start doing this soon... Plone 5?
having said so, we have to remember that, even as Dexterity is in Plone core now, as long as I understand it's not yet the preferred way of creating content types. You still have Archetypes and it will be there for long time.
best regards Héctor Velarde
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
