Logistics

Time: Monday, December 27 @ 12:00 pm Eastern
Rescheduled to Tuesday Jan 4, 2010 @ 1200EST

Attended: Marvin Addison, ScottS, SusanBramhall, Jonathan Markow, Andrew Petro, William G. Thompson, Jr.

Agenda

Roll call, choose note taker
Meet Up Next Steps - Let's Choose a Day!
CAS4 status update
Documentation Status Update
CAS Presence @ Jasig Conference
CAS Accreditation
Plan for Jan Community Call (no topic at present) Ideas on wiki: Presentation Topics

Notes

Andrew Petro as notetaker

Meetup

@ Columbia
Last 2 weeks in March? March 24th? March 17th is St Patrick's day. Scheduling difficulties on certain days due to recurring committee meetings. Thursdays preferable.

Logistics. 20-25 people?

ACTION ITEM: ScottS to follow up with Columbia to pick a date

Other meetups to queue?

Florida?

ACTION ITEM: ScottS to follow up with Eric Pierce @ USF

How about Virginia? Marvin sees opportunity in Raleigh metro area in terms of draw.

ACTION ITEM: Marvin Addison to consider Raleigh area schools which may be suitable

Is there a wiki page for coordinating meetups?

ACTION ITEM: Andrew Petro Hunt down and ensure spiffy wiki page for coordinating possible CAS meetup locations.

Phoenix CAS meetup idea. Potential in combined Sakai-CAS meetup? Potential in scheduling a CAS meetup on the day of a Phoenix JUG meeting and getting a CAS speaker on the schedule of that JUG meeting.

ACTION ITEM: Andrew Petro to poke Unicon internally about hosting a CAS meetup in Phoenix.

University of Michigan? Sakai-CAS combined meetup potential.

ACTION ITEM: Jonathan Markow to introduce CAS-latching-on idea into Sakai meetup planning process.

CAS 4 Update

Scott updated committee on progress:

XML configuration -> @annotation based configuration, virtues of
Storage --> JPA, cleaning up JPA, needs locking strategy

Next tactical technical steps:

Clean up storage code
Make CAS protocol implementation stable
Cut an M1 / Tech Preview 1 as a result

Marvin renews commitment to leadership on services management, intent to resurrect email thread

ACTION ITEM: Marvin to resurrect Services Management email thread, otherwise revitalize Services Management Improvements in CAS 4 thread of effort

Discussion of how JIRA represents CAS 4 versions.

ACTION ITEM: Andrew Petro to start cas-steer thread following up on what JJM was seeing and not seeing in highlighted versions, how to help CAS community to see CAS roadmap via JIRA, etc.

ACTION ITEM: ScottS to clean up JIRA versions

Expected version sequence is 3.4 to 4.0, skipping 3.5. 4.0 is a recognition that 3.5 was going to be too revolutionary.

Documentation

Marvin Addison believes outline is stable for new CAS manual / CAS documentation.

Discussion of combining or splitting CAS 3.4 and CAS 4 manuals.

Consensus that two spaces necessary, separating these documentations for least confusion, despite the additional resource costs in producing and maintaining two documentations.

William G. Thompson, Jr. sage words weighing challenges and costs of a revolution, a 4.0 release, guidance from prior revolutions (uPortal 3, Sakai 3). Clarifies this isn't opposition to CAS 4 so much as urging having good reasons and being able to clearly articulate those resources and respecting the significant cost. (Andrew Petro paraphrasing very loosely here)

Jonathan Markow inquiry as to when CAS 4 might be released.

Documentation is part of CAS 4 deliverable. CAS 4 features as not considered complete w/o docs and tests.

Andrew Petro, perhaps tilting at windmills, urged CAS 3.4 documentation efforts be allowed to be as great as they can be, even if they raise expectations for CAS 4.

Remote meeting of CAS developers in 2 weeks?

ACTION ITEM: Marvin Addison to follow up on making a CAS developer virtual meeting happen and to establish rhythm for this, whether via call, IRC, etc.

IRC channel, Freenode, Jasig IRC->Confluence Logger bot.

ACTION ITEM: ScottS to set up such an IRC channel with appropriate features.

Marvin Addison suggests all work on CAS documentation.

ACTION ITEM: EVERYONE to work on CAS documentation

Community call

ACTION ITEM: Marvin Addison to start thread on community call

Skip January call and focus on making February happen? Mostly consensus on this.

Jonathan Markow asked when the Feb call is, what the recurrence rule is (a question also on at least Andrew Petro's mind. Fortunately, since JJM asked, he can draw the action item of

ACTION ITEM: Jonathan Markow to fix website, wiki, Bedework whatever is necessary to make it clearer that the recurrence rule is 2nd Wednesday of each month, 12-1pm Eastern, so that the CAS community can better be aware of and plan to attend these calls.

Isn't there a Bedework calendar for this?

ACTION ITEM: ScottS to get into Bedework and work out CAS presence in it.

ACTION ITEM: Andrew Petro to harass JJM about / otherwise look into Bedework -> Drupal integration, helping Jasig to get any value out of content in Jasig Bedework.

CAS presence at Jasig conference

ACTION ITEM: ScottS to start cas-steer thread on CAS conference presence

Summary of action items

Owner	Action
ScottS	Follow up with Columbia to establish date for CAS meetup
ScottS	Follow up with Eric Pierce at USF to progress queueing a Florida CAS meetup
Andrew Petro	Ensure spiffy wiki page for collaboration on possible CAS meetup locations
Andrew Petro	Poke Unicon about a Phoenix area CAS meetup
Jonathan Markow	Introduce CAS-latching-on idea into Sakai meetup planning process
Marvin Addison	resurrect Services Management email thread, otherwise revitalize Services Management Improvements in CAS 4 thread of effort
Andrew Petro	start cas-steer thread following up on what JJM was seeing and not seeing in highlighted versions, how to help CAS community to see CAS roadmap via JIRA, etc.
ScottS	Clean up JIRA versions
Marvin Addison	make a CAS developer virtual meeting happen and to establish rhythm for this, whether via call, IRC, etc.
ScottS	Establish cas IRC channel(s)
ALL	Work on CAS documentation
Marvin Addison	Start thread coordinating February community call
Jonathan Markow	fix website, wiki, Bedework whatever is necessary to make it clearer that the recurrence rule is 2nd Wednesday of each month, 12-1pm Eastern, so that the CAS community can better be aware of and plan to attend these calls.
ScottS	get into Bedework and work out CAS presence in it.
Andrew Petro	harass JJM about / otherwise look into Bedework -> Drupal integration, helping Jasig to get any value out of content in Jasig Bedework.
ScottS	start cas-steer thread on CAS conference presence

Browser not supported