Skip to content

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

Closed
spinets opened this issue Aug 5, 2023 · 12 comments
Closed

Vim's future #12728

spinets opened this issue Aug 5, 2023 · 12 comments
Labels

Comments

@spinets
Copy link

spinets commented Aug 5, 2023

Given the tragic news about @brammool, is there anyone here with the commit access to the repository?

@pistasjis
Copy link

There are two others in the Vim organization, they probably have commit access

@nyngwang
Copy link

nyngwang commented Aug 5, 2023

Now who can manifest the quality of Vim?

@ebits21
Copy link

ebits21 commented Aug 5, 2023

I sincerely hope the 'benevolent dictator' model is revised and vim re-organizes its development.

RIP Bram.

@FHU-yezi
Copy link

FHU-yezi commented Aug 5, 2023

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.

About this: https://docs.github.com/en/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories

@oozeRyze
Copy link

oozeRyze commented Aug 5, 2023

Given the tragic news about @brammool, is there anyone here with the commit access to the repository?

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

@yesudeep
Copy link

yesudeep commented Aug 5, 2023

RIP Bram.

@xaizek
Copy link

xaizek commented Aug 5, 2023

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.

@wbpayne22902
Copy link
Contributor

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.

@tonymec
Copy link

tonymec commented Aug 5, 2023

Given the tragic news about @brammool, is there anyone here with the commit access to the repository?

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.

@mikl
Copy link

mikl commented Aug 6, 2023

I’m sure it’ll work out, but it might take a little time for everything to get settled. Have a little patience.

@Dawei-Simayi
Copy link

Dawei-Simayi commented Aug 6, 2023

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?

@Shane-XB-Qian
Copy link
Contributor

this is NOT the good timing to discuss this, please show your respect!

@vim vim locked and limited conversation to collaborators Aug 6, 2023
@k-takata k-takata converted this issue into discussion #12736 Aug 6, 2023
@k-takata k-takata pinned this issue Aug 6, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests