I like the idea of team maintenance of runtime files. I don't see why we shouldn't just do it for all the runtime files. Just set up a Bitbucket or Github clone (or another Google Code project, but I don't see a good way to relate it back to the main Vim repository, and clones made on the Google Code site can only have a single committer) and give all current runtime maintainers commit access. If a file has a listed maintainer, that person would by default be the person to make the change; but if they become unresponsive and the change is straightforward enough, the team could step in.
-- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
