I'm all for creating a slightly more formalized process. I think our previous "process" was possibly too ad-hoc. :-) I'm all for using Eric's module as the guinea pig for refining the process (sorry, Eric!).
One thing to consider would be going forward to apply this process and its criteria to existing core modules as candidates to either deprecate or move to the extensions module. Also, while extensions may have less stringent requirements than being in core, if they are still under the Jasig name, we have some standards to maintain. It would be a bad experience if people attempted to use Jasig-branded extensions and they consistently failed ;-) Cheers, Scott On Wed, Apr 4, 2012 at 1:01 PM, Marvin S. Addison <marvin.addi...@gmail.com>wrote: > 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/<https://source.jasig.org/cas-extensions/> >> >> and we opted to pull them into CAS server core. Are we reversing that >> decision? >> > > No. ClearPass naturally evolved from cas-extensions to core based on > community interest, design, features, and maintainer. I'm proposing that > we leverage GitHub to allow similar evolutions with Eric's work and others > that may arise in the future. There's no guarantee that it will evolve > into core, but hosting on GitHub under Jasig makes it available in the > spirit of incubation without the overhead of the formal Jasig Incubation > process. If it grows in terms of features and adoption, it will naturally > become a good fit for core like ClearPass and we can fairly easily > transition it into the cas repository. > > I think a cogent proposal by a respected community member like Eric goes a > long way here; I wouldn't recommend breaking ground with a contribution > from just anyone. I think we owe it to give a thoughtful code review and > move forward in some fashion if it passes muster. If there are alternative > recommendations, let's talk about them; otherwise, let's move forward with > what I offered. > > > 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
