Takeover Vundle

[gmarik]

Hey guys,

Please comment below if you're interested in taking over Vundle.

I've not been involved and it's hurting the project. If you're interested in taking the lead - let me know and we'll discuss transition.

Thanks!

PS: please share/RT

Progress:

• [x] Create an organization: VundleVim
• [x] announce at /r/vim
• [x] Transfer The Repo to The VundleVim
• [x] Invite everyone
• [x] Describe team process:

  Potential Volunteers

• @btreeinfinity
• @KamranMackey
• @silfverstrom
• @ryanoasis

[Shougo]

Hi, I think you should create the github organization for Vundle like ctrlp.

https://github.com/ctrlpvim

[Shougo]

You or other people should post the anounce in vim_dev or vim_use or reddit/vim, ... Vundle is major plugin manager, I think the supporters are coming.

[gmarik]

Thanks @Shougo, will do that!

[Shougo]

:-)

[Shougo]

I have announced it in my Twitter account.

[opsroller]

I'd be willing to take over, and amp it up, but only with community support and input!

[Shougo]

Yes, you don't have to fix VimL code :-)

[gmarik]

@btreeinfinity awesome! Would be nice to have several ppl onboard as it's not sustainable for one person(unless hardcore OSS-er) IMO.

[dvidsilva]

can you list the main things a new maintainer/person/thing/ has to do? Maybe there's people that would be interested but are too scared to take over such a project.

edit: also tweeting about it :)

[gmarik]

@dvidsilva everyone can find something for oneself: take a look at issues and it could be from helping ppl with advice, testing, fixing a bug to implementing a feature…

[evieluvsrainbows]

@gmarik I'd be willing to take over Vundle with @btreeinfinity as well. I don't mind! :smiley:

[gmarik]

@KamranMackey I don't mind, as long as it makes users happy ;)

[evieluvsrainbows]

@gmarik Alright. :smiley:

[Openpalm]

Vundle now returns an error when it's handling itself - are we on this branch still?

Error:

You are not currently on a branch. Please specify which branch you want to merge with See git-pull(1) for details.

and i'd be willing to pitch in too - but i'm a noob and would like some mentoring when it comes to the code. do we have an IRC?

[Shougo]

@Shokodemon This is not user Q/A issue. You should explain the issue in other place.

It seems you just change the branch manually. You should reset it with git checkout master command in the repository.

[silfverstrom]

I would also be willing to maintain the project, as long as @btreeinfinity and @KamranMackey doesn't mind the extra help=)

[ryanoasis]

I have some interest in lending a small hand :smile:

[evieluvsrainbows]

@silfverstrom I wouldn't mind. :smile: @gmarik Is this enough volunteers now?

[gmarik]

@KamranMackey yeah looks like it!

Will migrate the repo to the organization and configure rights for you guys later today. Thank you!

[evieluvsrainbows]

@gmarik You're welcome. :)

[ryanoasis]

:+1:

[gmarik]

Hey guys! You're now part of the team.

Post your feedback here in case of any questions.

[ryanoasis]

@gmarik cool thanks :+1:

• How involved do you see yourself now going forward (from what I have read I take it not very involved) ?
• Is it up to the team to figure out and decide the next steps?
• It seemed like there were/are more potential volunteers going forward?

[gmarik]

@ryanoasis

1. /cc me if you'd like to have my input, i'll be following along to get/help the team going
2. Yes
3. Even better! We'll add more people as they decide to join in.

[gmarik]

@KamranMackey master is now reset back to cfd3b2d.

Let's first figure out process we gonna work

[silfverstrom]

@gmarik @ryanoasis @KamranMackey @btreeinfinity I took the liberty to create a gitter room. If you think it is a good idea, we could keep the discussion as to what the next step is in that room. https://gitter.im/silfverstrom/vundlevim

[ryanoasis]

@silfverstrom :+1: I even had the same thought last night (especially after the notifications :smirk: ) but I think this would be better: https://gitter.im/VundleVim/Vundle.vim/maintainers thoughts?

[gmarik]

@silfverstrom there's existing general gitter room https://gitter.im/VundleVim/Vundle.vim @ryanoasis separate maintainers room :+1:.

[evieluvsrainbows]

@gmarik May I please have my permissions back? I'm sorry for the mindless PR merging. I won't do it again.

[ryanoasis]

@KamranMackey :+1:

[evieluvsrainbows]

Since @gmarik won't respond, @ryanoasis may I please have my collaborator permissions back?

[ryanoasis]

I don't think we have that power. Did you try the maintainers chat?

[gmarik]

@KamranMackey sorry man, permissions will have to wait a bit. In the mean time you could be helpful in other ways like helping people figure out issues and stuff like that.

[trygveu]

Hi, I can lend a hand once in a while with responding to issues. There are numerous issues that have been inactive for a long time, and many of these can probably be closed. What is the preferred way to close an issue?

I would like to be able to do this, without adding extra burden on the project maintainers, and give you a bunch of extra notifications top attend.

1. Ping the OP and encourage them to resolve or close the issue.
2. If no response in 1-2 weeks, ping one of the maintainers, and present a set of reasons for closing the issue.

Is that an okay sequence?

[ryanoasis]

@trygveu I think this is a really good idea. :+1:

Maybe require 2 maintainer votes for closing instead of 1?

Also I think it would be helpful for us to have a maintainers page or something in the wiki to keep track and refer to the rules we decide on

[wsdjeg]

why do you create a new plugin neobundle, i hope all of the vundle neobundle etc. combined into one

[ryanoasis]

@wsdjeg is that question meant for @Shougo ?

[wsdjeg]

@randymorris yes So many plug-in management tools that I can not choose

[vyp]

@wsdjeg If I recall correctly, gmarik preferred to keep Vundle simple, but Shougo wanted more features, hence another plugin manager. That's the great thing about free software, we are allowed to have more choices if someone is technical enough to hack on it.

If you are having a hard time choosing, I suggest either start with Vundle (this) or vim-plug. And if you find out later that you want more features, try neobundle.

[wsdjeg]

yeal i am using neobundle to lock the plugin to a commit

[trygveu]

I feel that you are a bit off-topic @wsdjeg. How Vundle relates to other vim package managers is interesting, maybe we can take that in #387 ?

:+1: @vyp, I think you are touching upon an important point here. Vundle is simple and not very complicated, it has a large user-base and it seems like the functionality fits most of them perfectly fine. I believe we should let the principle simple guide Vundle in the future as well.

@ryanoasis, about the wiki-page. Should I just draft one and mark it as "work in progress". What should the title be?

[Shougo]

If you are having a hard time choosing, I suggest either start with Vundle (this) or vim-plug. And if you find out later that you want more features, try neobundle.

I think vim-plug is medium complex plugin manager. It is not simple like Vundle. Yes, neobundle is most complex plugin manager.

[wsdjeg]

complex does not mean not simple,it just means simple + plus. such as operating system,engineer and the general user use the same system! general user alse can use neobundle like vundle just to install plugin without other function

[ryanoasis]

@trygveu For the wiki good question. I am not really sure. Maybe something like Collaborators or better yet Project Maintainers section?

Also I am one for the philosophy of "perfect is the enemy of good" :smile:

[trygveu]

@ryanoasis Here's a start: https://github.com/VundleVim/Vundle.vim/wiki/Project-Maintainers-Section

[ryanoasis]

@trygveu That looks really good (especially for a first version)!

[trygveu]

@ryanoasis Hi, I discovered I had cluttered the wiki a bit. There is an existing Development-Workflow page that partly described the issue handling.

I allowed myself to change the new page to Handling-issues and linked to it from the existing page. I also added an open point on Testing on the Development-Workflow page related to #619.

I guess we need to have some working tests up and running before we can finish on describing team process.

[b232wang]

which is better vundle or spf13?

[vyp]

@b232wang they are two different things

[wsdjeg]

hi @gmarik many people ask me how to use this plugin to manager their plugins,all of then use the old chinese post from the internet.i think it's better to add a file name readme/ch_zn.md ,and i can finish it with PR