-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vim's future #12728
Comments
There are two others in the Vim organization, they probably have commit access |
Now who can manifest the quality of Vim? |
I sincerely hope the 'benevolent dictator' model is revised and vim re-organizes its development. RIP Bram. |
If he already set the successor feature in GitHub, someone he chosed can move this repo to he/she's account or make it public archived. |
This is not a problem that is difficult to solve.The rest of the people in the organization can contact Github support to grant access and permissions to teams and members. R.I.P. Bram |
RIP Bram. |
Hope Vim's future will be no less impactful on IT sphere than its past. Vim has some great co-maintainers, so I don't think it's too much to expect. |
I imagine that the two others who are in the vim organization will step up and things will be more or less the same after a period of grieving over Bram's loss. I was so sad to hear of Bram's passing myself after having used Vim myself for years, he will be sorely missed, that is certain. RIP Bram, I'm sure you are programming something amazing in the afterlife. |
I don't know, but it can certainly be arranged; and in any case, if nothing else avails, the "master" repository can be moved to http://hg.256bit.org/vim i.e. the Mercurial clone maintained by @chrisbra which is already up to patchlevel 9.0.1677. The next patch exists, but only AFAIK as an email version: it can be brought in without too much hassle. For the rest, a solution shall be found, $DEITY willing. |
I’m sure it’ll work out, but it might take a little time for everything to get settled. Have a little patience. |
And is there something that we should consider? With the older generation contributors getting older, should we let the younger generation contributors participate in maintaining the open source repo? |
this is NOT the good timing to discuss this, please show your respect! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Given the tragic news about @brammool, is there anyone here with the commit access to the repository?
The text was updated successfully, but these errors were encountered: