To help w/scheduling, here are the scheduling meeting notes from 3/20 and 3/22, which have more details in them.
team meeting notes 3/22 re: next build
Build 2 (4/5)
-Itinfo
- preview individual file
- preview the site
- deal w/transforming links (requires understanding what we want for a URL, which depends on web app )
- requirements for IS&T web app
- investigate LifeRay portal 
-forms/templates
- identify a subset
- peel apart orig file into xml
- import & attach aspects
- preview & edit
- figure out structure of files
- separate xml from html, separate deployable from undeployable
-Workflow
- from Janet's email:
Fix: commit documents when workflow is complete
Fix: disappearing documents - show the docs under review in the workflow
Add: the comment aspect
Add: pretty labels
Alfresco: enquire about workflow audit trails
For this round I'm focusing on aspects and the mechanics of
presentation. I'll create a very simple workflow, which happens to be
the same as CSS's proposed "pubs internal review". If CSS keeps the
workflow as they finalize their needs, bonus -- that task will be
crossed off.
-Joe
- help w/file struct
- polish up preview (some generalizations for Prod Info)
- start work on certs, due for Build 3
- give some thought to install/deploy issues
- pull the build together
-Sys Admin
- need to look at config mgmt & deploy system (some kind of diff)
- Alf is broken because all the config is in one file (Hunter will Jira)
- build new servers
- get CS7 up to be used
- start clustering CS1 & CS2, see about DNS
Sched meeting notes from 3/20 w/more details:
Workflow
add aspects (comments, bug number, etc)
send emails to out of system users
LEARN: grab URLs for docs being reviewed
ISSUE: auditing/reporting on workflow, overall
FIX: editorial review not committing
FIX: make all labels nice
LEARN: how to assign multiple groups of reviewers (editorial, prod, etc)
LEARN: roles/user groups for workflow
Finalize CSS process
Build workflow process (complicated basic case)
Build workflow process (fasttrack)
OOB way to move tasks along (cancel, auto-approve, etc based on time-out or other conditions (cancel, unstick)
REQUEST: WF details (be able to see status of WF items that you have sent out)
user testing of WF, and revisions
REQUEST: Recall document button, reassign reviewer
ITinfo
tasks on Wiki. Break down into sections:
Migration of Stock Answers
Migration of Product Info
Migration of Articles
Proto Prod Info (M2)
Delivery of info (see wiki)
Requirements of IST Web app for (M2)
ISSUE: help desk has a wiki/knowledge base for themselves; they've copied the stock answers & extended it
NEW: preview individual page (as html)
NEW: preview web project as a website
deal with links inside the existing Itinfo content (part of transformation)
Figure out
structure of xml/html/generated files
usability study re: structure
how do we split up IS&T into different web projects?
what kind of URL do people put in, if they are linking to a dynamic page? How do you point to another document?
Froms/Templates
meeting w/Alison to get current prototypes for new website
better labels for x-forms (possibly related to how xml gets organized)
expanding forms to include current layouts (2 col, etc)
tables in forms
forms in forms? How do we handle forms? Recommend external solution
allow people to put externally edited html pages into a web project as a piece of content
Transforming existing content to XML
step 1: organized by current page & current layout
step 2: CSS make new pages out of old pages, then xform that
step 3: pull out all the content into xml fragments and let them build pages from that
questions: what about IS&T wikis?
questions: about old stuff? Layouts, journal pages, etc.
ISSUE: GET HTML BUTTON in ALF 2.0
ISSUE: searching
Other:
AuthN
Link Mgmt - get together w/Jon Cox
LM: validate links, figure out what we have to do now
Deployment
Eyestreet tool?
do what???