...
- 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.69.
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...
~awp9Andrew Petro'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.
...
- Draft a cas-steer representative or other to serve on Jasig Demo Site Product Work Group /wiki/spaces/MARK/pages/103954394?
- CASST-8 tracks getting back to Tim about this opportunity
...
- Collaboration on? Increased involvement of Marvin/VT in?
- Prognosis / timeline?
- Status / prognosis for harvesting thoughts from jasig2011 exploratory branch into cas4 trunk?
Notes
- Marvin interested in a developer summit in NYC area this summer to focus on CAS4. Next CAS Meetup?
Tabled Items
Availability and commitments
...
Review any open action items not otherwise discussed. Capture new action items.