I've been talking to Matt about give svn access to a few more people within the Ignite community. We might be able to put the community plugins into the same svn repository.  Would you be interested in doing that (assuming we can work through all of the permissions issues with our it guys)?

So kind of you, Jay.

I think, to the community, it doesn't matter much where the physical svn storage is. What's more important is that it appears within Ignite Realtime space. It's more like issues of community members' motivations, one-ness/singleton (whatever you may call it) and the like. If you don't mind about your server 'hiding' behind Jive, then like you said, one way to do this is via svn:externals.

There's however some things that perhaps need considerations like what kind of infra, arrangement, setup etc. that you could offer to ensure sustainability, reliability etc. As of now, we can always blame Jive for anything ;-). I don't think they want to assume responsibilities of things beyond their control.