I think tons of companies battle with the limitations of "we should eat our own dog food." It tends to be a general rule, even when you as an organization have only
marginal overlap with your target market.
I applaud Greg Stein's response (Stein is the founder and VP who was against the move):
> The short of it is: the Apache Subversion project chose this. We want to get our stuff coded and released. For our backend, we don't need the super-huge repositories that Subversion supports. Our project stores some binaries, but we can make Git work for us. We have no need for Subversion's fine-grained authorization ... shoot. We allow ALL ASF committers access to our repository. There are no barriers to the migration here, and some of the stuff that Infra has done for integration with GitHub? Pretty cool. Positives, and only little negatives.
I love seeing this commitment to the community and developers.
Edit though for completeness on the whole "dogfood" issue, this is another comment Stein made:
>So I'll be able to use the svn client to check out from the ASF git repo? Awesome. (...) We can dogfood svn against our own repo.