­

One Year from now...
-fewer, but better "core" docs
-thriving community docs
-nothing but green on our section assessments
-more active doc list/more active contributors





Manage our content better
    enforce our guidelines on both community and core docs
        further define said guidelines - mostly done, still need fine tuning
        ­topic selection on new docs is mandatory - when plone.org is switched over to plone 3
    update manuals with every new plone release - due just in time with each release
    Documentation Section Assessment
        complete one for your section - by end of 2008
        identify missing docs - May 2009
        find content for those missing docs elsewhere online(6 ft up, weblion, etc) - May 2009
    Doc page UI
        New Design implemented- second quarter 2009
        add buckets for docs that apply to each plone version - second quarter 2009
        divide wild docs vs core docs - second quarter 2009
            comments ok on community docs
            comments not ok on core docs- file ticket in dev.plone.org/plone  Trac instead
            ­Sort formal docs into manuals - end of April 2009
­            designate which docs go into knowledge base­­ ­- end of April 2009
   Establish some kind of metrics for all of this - third quarter 2009
        IRC bots??


Manage our Team better
    create standard process for getting newbies started - asap - started draft here
    Editors
        need 3 more- Joel, Darci, ??
        Implement by EOD 10-12
        set up Public page on who editors are, what they do, etc. - end of october - Ready, waiting to publish when plone.org moves to p3
        create editor's email list - EOD 10-12
        set up auto notify on doc add or submit on plone.org docs- when plone.org is switched over to plone 3
        editor's report on work every 3 weeks to editor's mailing list- doc list is updated with summary. - first one due 3 weeks after sprint summary is posted to doc list
        minimum 1 doc team only sprint a year with all editors