Susan Brooker-Gross and Kim Homer are to work on the text of the www.pki.vt.edu/pdc website so it is appropriate for anyone. Once completed they will let Frank Galligan know. Frank will then link the www.pki.vt.edu/pdc website from the www.pki.vt.edu website.
We need to continue to promote to end users that the "one stop shopping" for IT information, including information on digital certificates and signatures, is http://www.computing.vt.edu. Computing pages that refer users to PDC documentation can link to information in the KnowledgeBase or on the www.pki.vt.edu/pdc website. All links on the www.pki.vt.edu/pdc website to the KnowledgeBase for user documentation should duplicate what is on computing. In other words there should not be unique content on the www.pki.vt.edu/pdc website.
A tentative procedure for moving documentation from the www.pki.vt.edu/pdc website to the KnowledgeBase is:
1. Kim Homer's team will write/edit and test content and send to Frank Galligan to review and post on the eProv development web server.
...1.1 Help with readability and testing of procedures is available from the VTOC operators and should be requested through Rob Sprague.
2. Documentation will be reviewed by the PDC Documentation and Communication project team as needed.
3. PDC Documentation & Communications team co-chairs, Mary Dunker or Greg Kroll will approve the content for publishing.
4. Frank will post it on the www.pki.vt.edu/pdc website and notify Betsy Blythe that it is there.
5. Betsy and the KnowledgeBase team will format it for the KnowledgeBase and notify Mary and/or Greg when finished and ready for KB publishing.
6. Mary or Greg will approve publishing of content in public KnowledgeBase.
7. Once published in the KnowledgeBase Mary or Greg will notify Frank to replace the content on the www.pki.vt.edu/pdc website with a link to the same content in the KnowledgeBase.
Publicizing organization codes.
As organization codes are added for distribution of PDCs a checklist needs to be completed so the org code is added to (1) TAS, (2) ITA (for RTE software), (3) PKI/PDC website for scheduling and (4) to the digitally signed online leave report and workflow system.
See tentative procedures above.
THE REMAINING AGENDA ITEMS BELOW WILL BE ROLLED OVER TO NEXT WEEK'S MEETING.
Create a "rolling agenda" for the PDC documentation/communication group. The agenda would carry over from one week to the next, so that as issues arise, they can be posted to the agenda for a future meeting, whether it's the Wednesday just after a meeting when the issue arises or the Monday before.
There could be standing categories for the meeting. Mary said that the pki.vt.edu website would be one. Perhaps there are others.
An initial topic for each meeting would then be to prioritize "today's" agenda based on urgency and importance (taking no more than a couple of minutes—Mary and you 'rule' in case of disagreement).
I would think you and Mary would make decisions about cancelling meetings anyway if the only agenda items remaining were small (short length of discussion needed, low importance, low urgency), and we'd save them for another day to make the time worthwhile.