On Nov 29, 2010, at 1:37 PM, Les Hazlewood wrote: > I think Kalle's comments don't reflect a licensing issue, but rather > one of maintenance and longevity: Shiro developers (or any open source > development team for that matter) will maintain things that 1) has > high perceived value for the community or 2) the developers use very > frequently themselves in their own real-world projects. > > The idea is that while it's nice to see that a new support module is > being written (I think it's great!), there may not be enough evidence > that the module will be regularly maintained and kept up to date, > which would inevitably cause more headaches and maintenance time for > the team, which would in turn would reflect negatively on the > project's perceived health. > > So, one approach is to start up the support module on an external > hosting site (e.g. similar to 'wicketstuff') and see how much traction > it gets. If it gains and maintains momentum, then the community would > clearly benefit from it being in the core project. Kind of like a > mini incubator of sorts.
I've never seen contributions handled in this manner at ASF. It doesn't mean that they do not exist but I would like to see proof that this "vetting" procedure is kosher with respect to foundation projects. Regards, Alan
