krischik wrote:
> On Sep 19, 5:49 pm, Ingo Karkat <[EMAIL PROTECTED]> wrote:
>> That's exactly my point. Forking on vim.sourceforge.net is painful and
>> confusing to all the users ("what, three versions of
>> MyFavoriteScript.vim?!").
>> If the original author finally decides to merge in someone's changes, more
>> email
>> exchange and redirection of VIM script pages is needed (as IMHO scripts still
>> cannot be deleted).
>> These things would be handled much better by a version control system, where
>> users could list all available branches and see the contributing authors and
>> fork history in one place.
>
> Indeed. So one question is left:
>
> 1) vim-scripts.sourceforge.net
> 2) vim-scripts.googlecode.net
>
If your goal is to improve the collaboration aspect of script
development, you should also consider using distributed version
control systems such as Git, Mercurial, Bazaar or Darcs. They were
created especially to facilitate collaboration and provide many
additional benefits over centralized systems, especially in projects
forking and merging.
I know of 2 sites which offer hosting for distributed projects:
https://launchpad.net/ (for Bazaar)
http://repo.or.cz/ (for Git)
but perhaps it would feasible to install such service at vim.org?
Regards,
Santhalus
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
