...
6/14/11 noon Eastern. Using apetro Calliflower account. All steerers received individual invites.
Agenda
Minutes
Who's recording minutes?
Tracking tasks
- CAS Steering action items now tracked in JIRA: https://issues.jasig.org/browse/CASST
...
- CASUM/docbook status update
- Roadmap
Tracking tasks related to documentation
- Too many JIRA queues? Exactly the right number of JIRA queues and need to use them effectively? Not looking to make a mountain out of this molehill, but trying to get to better clarity...
~awp9's suggestion:
- Use CAS (cas-server) queue to track tasks/issues related to the DocBook documentation. This documentation is in SVN with the cas-server source code, versioned, tagged with it. Therefore tagging and releasing cas-server tags and releases documentation, and it's meaningful to be able to talk about the documentation tasks completed for and the documentation defects in CAS 3.4.9, e.g. Use "Documentation" Component to track these issues.
- Use CASW to track CAS "documentation" (website, wiki) issues other than in the formal, versioned-with-CAS-server docbook, since it doesn't make sense to talk about these tasks in terms of defects in a particular cas-server release version, their being continuously pursuable outside the context of specific relases. Rename this queue to CAS Website rather than CAS Documentation to help make the distinction clear.
Community Call?
Release process
...
Don't we have an election coming up real soon?
Action items
Review any open action items not otherwise discussed. Capture new action items.