I'm pretty sure Scott wasn't suggesting a fork, but rather simply inquiring how to best engage the community on some significant contributions.
Once you see what he's done, I think you'll be pleased with the direction. I know I am, and as the original author of the Forms AuthN based CasAuthenticationModule, I'd be happy to see Scott take up leadership of that piece if he's up to it. That being said, I agree we should proceed normally as you suggest, open a couple of JIRA Issues, attach the patches, discuss. I'll be happy to manage any resulting commits for now. Best, Bill On Mon, Feb 15, 2010 at 9:03 AM, Marvin Addison <[email protected]> wrote: >> How should I contribute this--as a new library, as a modified version of the >> original library? > > Please, please, please do not fork this library at such an early stage > of development. > Although you claim that the changes you've proposed > are so significant that it might make sense to simply fork the > project, I'm not convinced. Let's start with the standard process for > feature requests and improvements to any open source project: open > issue, attach patch, discuss. I'm fully open to all the suggestions > you've made, but I can't fully evaluate them without code in front of > me. Issue tracker is here, http://www.ja-sig.org/issues/browse/NETC. > Please create separate issues for each of the changes you proposed, > which I believe distill down to two items: > > - Use cookies for ticket storage > - Use ASP.NET cache provider for ticket state tracking > > M > > -- > 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 > -- 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
