Folks, Based on ScottB's feedback and some discussions off-list, I believe we have a reasonable path forward for the .NET Cas Client, which is enumerated below. It would be helpful if all the current Committers (Marvin, Catherine, Bill, ScottH) and any other interested parties (especially if you have cycles to help us get to a 1.0 release) would weigh in on it.
1. The .NET Cas Client will be a full-fledged Jasig project. Which means that it must: a. Be properly packaged (or the .NET equivalent) b. Be properly licensed with the appropriate contributor license agreement c. Follow the appropriate voting and meritocracy rules d. Have a well-published road map and statement 2. The current Committers will work together to put together a Roadmap for 1.0 in the Jasig wiki prior to the Jasig conference. This will help coordinate work and drive issues into JIRA, where Committers will pick them up as they can. 3. Target the Jasig conference for some kind of release, Milestone or Release Candidate, with a 1.0GA hopefully soon after. 4. Establish defined and agreed upon Roles (aka volunteer opportunities) similar to other Jasig projects. - Committer A committer is a developer who has write access to the code repository and has a signed Contributor License Agreement (CLA) on file. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project, creating and picking up JIRA issues, and committing code under the Commit-Then-Review (CTR) process. (meaning no votes before commits, but an objection could be raised post commit that will call for discussion and resolution). Major or sweeping changes to the code base will be subject to Review-Then-Commit (mostly likely with work being done on branch). - Release Manager Tag, version, package and distribute releases. Ensure JIRA is consistent before a release. Initiates votes on package releases. Marvin has volunteered to be the first Release Manager. - CAS Steering Committee Rep Currently, Marvin is on the CAS Steering Committee and has volunteered to report on project status. 5. Adopt the Jasig Release Strategy http://www.ja-sig.org/wiki/display/UPC/Release+Strategy 6. Establish separation of responsibilities with regards to the code base. Code module "maintainer" is the original author unless specifically delegated or abandoned. Module "maintainers" are responsible for the integrity of that code base. However, as ScottB points out that doesn't mean total control, as some consensus decisions may go against you. Here's is a proposed break out based on work/merit: * Authentication (Cas Domain Model) - Bill * .NET Patform Integration (CasAuthenticationModule) - ScottH * Protocol Support: Cas 1.0 & 2.0 - Bill * Protocol Support: SAML - Catherine/Marvin * ExampleWebApp - ScottH * Documentation - Marvin Regards, Bill -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
