This is a make-up meeting from the May meeting, and is especially in followup to the Jasig 2011 conference.
Logistics
6/14/11 noon Eastern. Using apetro Calliflower account. All steerers received individual invites.
Agenda
Minutes
Who's recording minutes? Bill
Tracking tasks
- CAS Steering action items now tracked in JIRA: https://issues.jasig.org/browse/CASST
- Tasks are assigned to cas-steer chair Marvin by default. Is this good enough, Marvin will triage? Important to be able to model tasks without an owner? Marvin, you cool with doing or delegating all tasks assigned to you?
Notes
- capture issues going forward, run in current issues that make sense
- review/discussion of CASST-1 (hashes on download artifacts) - agreement to follow up on cas-dev, 3.4.9 target for having hashs, Marvin to follow up with David Durham
Jasig 2011 conference followup
- BoF notes
- Presentation slides
- Lakshmi volunteerism
Notes
- cas-steer slides posted by Andrew
- BoF notes still need attendees
- Lakshmi (Oakland) volunteered to be CAS Client Liaison. Role is to coordinate between CAS Client projects to help with feature parity, release coordination. Bill will follow up Laskshi regarding volunteer role.
Bill volunteers as a community mentor for Lakshmi.
Documentation
- CASUM/docbook status update
- Roadmap
Notes
- Marvin: Strategy for completion. Porting from wiki to docbook. Add new content. Get docbook
stubbed out to get more help (Marvin). Non-blocker for 3.4.6.
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?
- Who owns making next call happen?
- July?
Release process
- Status of checklist
- (Pedantic) mechanism for executing checklist – wiki page per version release in which to check off items (discussed at Jasig)
- cas-dev committer votes for release?
Jasig demo site, CAS in
- Draft a cas-steer representative or other to serve on Jasig Demo Site Product Work Group?
- CASST-8 tracks getting back to Tim about this opportunity
Versions
- Evolve from tip of CAS-3-4-maintenance towards an evolutionary 3.5 in svn/cas3 trunk, moving revolutionary cas4 to svn/cas4?
CAS4
- Collaboration on? Increased involvement of Marvin/VT in?
- Prognosis / timeline?
- Status / prognosis for harvesting thoughts from jasig2011 exploratory branch into cas4 trunk?
Availability and commitments
Election
Don't we have an election coming up real soon?
Action items
Review any open action items not otherwise discussed. Capture new action items.