Excerpts from LCD 47's message of Mon Feb 24 23:39:18 +0000 2014: > I actually like this project too. I'm just pointing out it's better > to think first and then do the work, rather than do the work then find > out you should have spent more time thinking first. *shrug*
If you have suggestions (what to think about first) create issues: https://github.com/neovim/neovim/issues/new We could try to focus on this view: - There is a programmer who got payed to work on Vim - He will work on Vim - Thus there is high chance that soon there will be two people who can review patches in the future - we still can influence what tarruda does - so maybe we should try to do so that his changes can be merged back, too Thus the vim community has two options - ignore - try to collaborate and emphasize on important things Maybe there is a chance to turn this into success for everybody. I'm pretty sure that he'll listen to comments. Important choices: Should neovim build up its own community (mailinglist etc) - or should they be allowed to use vim-dev and vim-use. There is a mailinglist which got added to the README recently. https://groups.google.com/forum/#!forum/neovim Its time to think about this *now*. If there are people on the mailinglist who think they know better than tarruda does - they should talk to him. He is listening. again - my 2 cents Marc Weber -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
