I think it is problem that the name of "vim" is taken by someone
already on github.
https://github.com/vim

Could we request to concede that "vim" name
if we deside to move to github?

And we should ask bitbucket same thing.
https://bitbucket.org/vim

2015-03-14 8:38 GMT+09:00 Mislav Marohnić <mislav.maroh...@gmail.com>:
> Hi, GitHub employee here. I'm not here to talk anyone into using git over 
> anything else, but to provide a bit of perspective as both long-time open 
> source maintainer[1] and huge Vim fan[2].
>
> On Friday, March 13, 2015 at 4:54:03 AM UTC-7, Bram Moolenaar wrote:
>>
>> Despite all the popularity of github, it doesn't seem to be able to do
>> something as simple as sending a user a message.  Do I need to fork a
>> repostitory and send a pull request just to get someone's attention?
>
> It's easy to get attention of any GitHub user by @-mentioning their name in 
> any issue thread, pull request review conversation, commit message or commit 
> comment.
>
> I think a switch to a host such as GitHub or any alternative is a question of 
> much more than just picking a version control systems. I agree with others on 
> this thread that both git and hg are perfectly viable solutions, each in its 
> own way. But project management and maintenance is much more than doing 
> operations on the command-line.
>
> My suggestion is that the decision about new project home for Vim should fall 
> on Bram and few other people that are most heavily involved in maintaining 
> the project (if there are any), based on which tool they want to look at 
> day-to-day when they are triaging issues and reviewing code contributions & 
> their CI status. In my experience, these are sometimes even more 
> time-consuming tasks than actually writing the code. Therefore, feel and 
> feature set of an online code collaboration tool is important regardless of 
> the particular VCS that sits below it.
>
> Our support staff spent weeks helping make the transition of the Go project 
> to GitHub[3] flawless and with minimum disruption to their flow. If you do 
> decide to move to GitHub, give us a heads-up and we can tweak our migration 
> tools to your needs. Thanks!
>
> [1]: https://github.com/mislav
> [2]: http://mislav.uniqpath.com/2011/12/vim-revisited/
> [3]: https://github.com/golang/go



-- 
MURAOKA Taro <koron.kaor...@gmail.com>

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui