So we essentially had that for interesting/useful modules that didn't necessarily have a huge number of deployers: https://source.jasig.org/cas-extensions/
and we opted to pull them into CAS server core. Are we reversing that decision? On Wed, Apr 4, 2012 at 11:49 AM, Marvin S. Addison <marvin.addi...@gmail.com > wrote: > > - Should each "niche" module live in it's own repository (maintained by >> the module devs themselves) and we add a page to the CAS wiki as a >> module >> directory - similar to Resque ( >> >> https://github.com/defunkt/**resque/wiki/plugins<https://github.com/defunkt/resque/wiki/plugins> >> ) >> > > +1 > > This follows the existing model of uPortal portlets hosted under the Jasig > organization on GitHub. I propose we create repositories named > cas-server-extension-X after a cogent proposal, code review, and vote. I > think Eric's given us enough background here to constitute a proposal, and > Janrain Engage is clearly a product with a wide enough audience to justify > an integration module. Let's take a week for code review, then vote to > create a repository for it. How does that sound for this case as well as a > plan for future features like this? > > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/**display/JSG/cas-dev<http://www.ja-sig.org/wiki/display/JSG/cas-dev> > -- 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
