...
Note | ||||
---|---|---|---|---|
| ||||
The very first and perhaps most important point of the meeting is to meet, to convene interested parties to discuss and achieve mindshare on goals, strategy, and tactics. I put some ideas for items for discussion on that wiki page. I'll update it with this verbiage. The topics for discussion at the meeting may best be understood in terms of the goal of the whole effort: make it easier and more easily understood how to CASify a uPortal. Goals are probably the first thing to discuss. What are these APIs trying to accomplish? What is the goal of the JA-SIG Java CAS Client's uPortal integration subproject? The meeting is to discuss which ICasSecurityContext APIs to standardize on, whether and which CasConnectionContext implementation to standardize on, and what to do about the various implementations – presumably make them implement whatever shared APIs are standardized on, but maybe to retire one or the other.
There are a plethora of options here. The meeting is to discuss their merits and arrive at a plan of attack. Also to discuss documentation – what documentation will be updated by whom. Improving the code to follow a well-defined plan won't be as valuable if we don't make it clear to would-be consumers. If we have time and aren't too exhausted, it could be worthwhile to discuss the prospects of embedding a CAS server instance in uPortal by default. That was discussed at the dev meeting and I think I'm starting to make inroads in people seeing this as not just a quickstart toy trick but a potential core feature of uPortal, to be using a CAS server under the hood. |