On Nov 25, 2010, at 9:54 AM, Kalle Korhonen wrote: > On Thu, Nov 25, 2010 at 9:27 AM, Les Hazlewood <[email protected]> wrote: >> But part of my delay is equally related to me thinking about how we >> manage our 'support' modules. With struts2 and wicket and maybe >> others, it seems like we should discuss how we handle this stuff in >> general and what (if any) our policy should be. > > I doubt we can make a clear-cut decision. It depends on the value of > the particular support module to Shiro core (you could argue that > maintaining Spring support has more value than struts2, wicket, etc.) > and committers' interest in maintaining the support module. It's > extremely difficult to convince committers to maintain support modules > for web frameworks they don't use themselves (been there, done that). > The safe bet is to put the new support modules on github or elsewhere. > They can always be migrated later to become part of Shiro.
Unless there is some kind of licensing issue there is no reason, from the ASF standpoint, to put new support modules on github or elsewhere. Regards, Alan
