Logistics
Time: Thursday, February 4 @ 10:30 am Eastern (9:30 am Central)
Conference Bridge: (641)715-3200 640123#
Attendees: Marvin, Scott, Benn, Andrew, Jonathan, Eric
Note Taker:
Agenda
- Roll Call; Choose Note Taker
- Review Old Action Items:
- CAS Roadmap
- Inspektr
- Apache 2 License
- Volunteer Positions
- Identifying other Clients to bring under the Jasig umbrella
- CAS participation in exciting Jasig social networking, social media initiatives
- Developer Days at Conference
Notes
2010-02-04 Conference Call
Notes
Roll call
All present
- Markow
- Battaglia
- Pierce
- Addison
- Oshrin
- Petro
Note taker
Petro
Review past action items:
Developer list roadmap timeline.
Release procedures of sub-projects
Documenting release procedures of sub-projects.
Scott may do this on Friday during a riveting flight.
Roadmap
Big changes in 3.X releases. Is this okay? Are they really big?
CAS 3.4 release changes Spring Web Flow version from 1 to 2. If CAS adopters have not changed their login web flow (most common case), they will experience no pain from this change. If CAS adopters have changed their login web flows, then
Marvin Addison to take point on documenting this.
CAS user manual versioning
Scott wonders about managing the CAS user manual versioning. Fork the manual wiki space for major version changes?
Identified as a major decision point needing more discussion. Andrew has some strong feelings about not forking the manual. Certainly there are some advantages to be had in version-specific manuals. Scott points out example of Spring Security managing doco in SVN and making it more of a shippable artifact rather than a wiki. Consideration of barrier to entry in adopters contributing to documentation.
Petro took action item to review what other projects are doing for documentation.
License
On CAS roadmap, CAS 3.4 will be change from "Jasig license" to "Apache 2 License". Pushed this to CAS 3.5.
Getting contributors to submit the contributor agreement.
JJM recommends consulting with JLewis on executing the change of license since he's the resident expert on licensing.
Scott gave self action item to reach out to 3 people who he'd most like to sign the contributor license agreement.
JJM on releases
The Board has asked each of the projects to put on the website a combination strategy/roadmap/direction document that would be dated for a particular point in time. The idea is that the strategy get revisited periodically, the roadmap gets revisited periodically, but anyone who comes to website can see the direction and roadmap.
This roadmap is a good start for the roadmap. Next we need the strategy statement. JJM drafted this for uPortal but feels less comfortable doing this for CAS.
JJM to show Scott the uPortal one, Scott will then draft a CAS doc.
JJM advocates for broad dates on roadmap.
Scott hopes 3.4 out by time of Jasig conference. Beginning of March 2010.
Inspektr library
JJM asks: Are we wed to it? Dependent on it? Want to remain dependent on it? What's its status as a project? Do we have confidence in it?
Scott: You can have confidence in this project based on confidence in Scott's efforts. Scott's working on a 1.0 release which addresses some of the current shortcomings of the prior .7 releases. This has to be done before 3.4 release. We did replace part of the project with Perf4J. Instead of using Inspektr for stats instead using Perf4J because it seems a decent library. Would like to craft Inspektr stats module as extension to Perf4J or even better contribute directly to Perf4J project.
Over-arching issue of "What is Inspektr"? It was stats, is it just an auditing library now? What is the scope?
JJM: If Scott's working on it, and Marvin's working on it, have no immediate concerns. Where are we in long run?
Further discussion of Inspektr
Need to continually audit dependencies.
Scott identifies: Followup needed: process for continually checking the health of our dependencies.
Developer days at conference
Scott describes the tremendous opportunities of developer days.