Hi Marc, I'm sorry, but long emails like yours scare me and I did not have time to read AND think about a response until today.
The next things to do for vim.org/scripts: * summarize the requirements[1] * get Bram to love the summarized requirements * start a Design page in the wiki and propose a design: Programming language, framework, ... * I'd very much like to implement the new VIM site with eZComponents[2], but it will get february until I'll get some free time for this * I'm very convinced, that it would make sense to use GIT as the storage backend for a new vim.org/scripts site. Old crufted CVS heros may use a webinterface to upload new versions. Parallel to the new vim.org/scripts site I propose the following: Start to collect high quality vim scripts from vim.org and put them on github.com (or alternatives). It would be nice to also have the version history of the scripts in the repositories, but that's not so important. It's much more important to get the licence informations right so that distros don't have problems to include the scripts. It would be great if we could convince vim script authors to publish their scripts in GIT repos. [1] http://vim.wikia.com/wiki/Vim.org_relaunch [2] http://ezcomponents.org Best regards, -- Thomas Koch, Software Developer http://www.koch.ro Young Media Concepts GmbH Sonnenstr. 4 CH-8280 Kreuzlingen Switzerland Tel +41 (0)71 / 508 24 86 Fax +41 (0)71 / 560 53 89 Mobile +49 (0)170 / 753 89 16 Web www.ymc.ch --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
