> Supporting both APIs _and_ sending patches to the dev list seems > contradictory. If I made a version that supported both APIs, I wouldn't > expect that version to end up in a future mod_perl 1 or 2 release.
not exactly related, but are we really talking about a full-scale handoff? it seems odd to me to take part of what we've considered core and completely hand it off to a third-party, then rolling it back into future releases, all without current developer involvement. I think I'd really like to see several things decided via public discussion: o whether Apache::SizeLimit should support both mp1 and mp2 o whether future releases of mp1 and mp2 will include Apache::SizeLimit o whether the mod_perl project should continue to have oversight via svn (for example, make Apache-SizeLimit a separate repository and granting dave karma) or whether we're handing the code off completely (to be hosted going forward in dave's realm) I think the last bullet is important to consider, especially from an ASF-licensing pov - if the project completely relinquishes control then for each inclusion in future releases we'd need to vet whether the new code maintains the ASF license and didn't break it along the way. yeah, I know, and I hate that we need to think of things like that, but the code belongs to the ASF so... the simplest solution to this is probably keeping the code at svn.apache.org, granting dave the appropriate karma, and allow him to act as release manager for Apache-SizeLimit. once that's complete, I have a feeling the other concerns will fall into place in typical public forum style. --Geoff
