That was always my plan on the subject, as I touched on briefly here
How does http://syntax.emeraldeditor.com/
(Note, this link does not work, the subdomain has not been set up!)
In answer to your point about SVN: yes, we could store the syntaxes in SVN, I feel that if we grow to storing thousands of syntaxes, developers aren't going to want to checkout the entire branch to cope.
I have to admit, though, I didn't originally plan on having an SVN backend for that actually, but I hadn't figured out exactly how I was
going to set it up. SVN just doesn't seem quite right to me, although technically it is more than capable of handling it.
The only thing is, I'd much prefer a web-based uploader which pre-parses the syntax file(s) and verifies that their own internal syntax is correct. Perhaps we could have an "incoming" section which is checked by the maintainers (and I would be happy to look after syntax files, as I know I'd be writing quite a few), and where applicable merged into existing files, or replacing them, so that those available through the syntax repository would always be the latest and most definitive. This is especially important in cases such as PHP where new functions are added through libraries on a quite regular basis (at least, that's my perception of it)
Anyone else have any ideas?