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.
-- ingo
On 19-Sep-07 16:31, thomas wrote:
>> A couple of times, I have sent small patches or enhancements to authors of
>> VIM plugins listed on vim.sourceforge.net, only to receive no answer;
>> probably, those authors have moved on or changed email addresses.
>
> Spam filters are another option. Anyway, if the authors don't respond even
> after sending queries to the vim list and if people are willing to "maintain"
> the plugin for some time, people could create a fork version (assuming the
> plugin is licensed under gpl or similar). It would be nice of course to have
> a note on the original script/plugin page pointing to related/derivative
> plugins.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
