I can do the set up in GitHub for a space under Jasig to hold these types of extensions. One question is do we want them to be individual, self-contained extensions, or do we literally want like a "cas-modules" project that can release them together?
Since each extension would likely not share any code or configuration with others, I think we could consider each one a separate project where each lives in its own git repository. Besides, GitHub repositories are cheap, searchable, and it's the model adopted for portlets, which seem conceptually similar.
Marvin, do you want to take a first cut of a draft document detailing what extensions is, what goes in there, how it moves out, etc.?
I'm happy to do it, but it will likely be beginning of next week before I can get to it.
M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
