Re: Proposal to manage documentation similar to (or along with) core software.
John Schinnerer <john-/Gao9/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Aloha, >> We're working to keep manuals up-to-date and well tagged regarding the >> version(s) they apply to. If you find any manual with incorrect/outdated >> info, please open a ticket in the http://dev.plone.org/plone tracker, >> documentation component, or mail me directly, and we will fix it. > > But you wouldn't know, unless you knew. "Open a ticket if you find a > mistake" only applies to a very small subset of folks (i.e. us). Everyone > else going to /documentation expects to see… current documentation. Ditto, more or less...I'd file a ticket probably, and/or create a KB item if that seemed more immediately useful. People starting out with the platform, or more in end-user roles (e.g. site admin, etc.), may have a lower level of frustration and/or commitment. They may fuss and complain (or just give up) but not file a ticket (or even think to do such a thing). I've had more struggles with absent information than mistaken information. If I can find what I need and it is applicable to my version/context, it's usually correct. It's what I can't find (or do find but cannot tell if it's applicable without trial and error overhead) that I'm more concerned about. thanks, John S. > >> -- israel >> >> >> ------------------------------------------------------------------------------ > > -- John Schinnerer - M.A., Whole Systems Design -------------------------------------------- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [email protected] http://eco-living.net ------------------------------------------------------------------------------ _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs