Re: Proposal to manage documentation similar to (or along with) core software.
Alex Clark <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Organization | ACLARK.NET, LLC |
| Message-ID | <[email protected]> |
On 2010-04-15, Dylan Jay <[email protected]> wrote: > +10. All the manuals should have separate versions viewable with urls > that clearly state the major plone version to which it belongs. If > that means we no longer improve the plone3 user guide after plone 4 > comes out I think thats fine IMO. I don't know if versioning is built > into the new proposed UI for the manuals section. > I can;t see how KB content is going to be practical to have separate > versions so I guess it will have to keep the existing way of stating > which versions of plone the doc was written for. There is the PHC notion of version, which has not proven to be too useful over the years. > +1 to paying the release manager. It's a stressful job. But are you > sure it should be the same person making decisions? Yes :-) > for example > deciding that we need to concentrate on portlets documentation vs > workflow documentation on the plone 4 release? or deciding if we > should use the sphinx developer manual vs the current one in > plone.org? Is the release manager the right person for that job? it > seems to me the qualities of the enforcer vs the decision maker are > very different. It's a collaborative effort. The release manager relies on the expertise and advice of doc team members, but ultimately has final say. > >> >>> j. >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >> >> >> -- >> Alex Clark · http://aclark.net >> Author of Plone 3.3 Site Administration · http://aclark.net/plone-site-admin >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Plone-docs mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/plone-docs > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev -- Alex Clark · http://aclark.net Author of Plone 3.3 Site Administration · http://aclark.net/plone-site-admin ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs