Takeover Vundle #608

gmarik · 2015-06-16T23:57:33Z

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:

Potential Volunteers

@btreeinfinity
@KamranMackey
@silfverstrom
@ryanoasis

Shougo · 2015-06-17T01:04:06Z

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

https://github.com/ctrlpvim

Shougo · 2015-06-17T01:08:51Z

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 · 2015-06-17T04:07:27Z

Thanks @Shougo, will do that!

Shougo · 2015-06-17T05:11:28Z

:-)

Shougo · 2015-06-17T05:20:08Z

I have announced it in my Twitter account.

opsroller · 2015-06-17T06:17:59Z

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

Shougo · 2015-06-17T06:59:37Z

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

gmarik · 2015-06-17T15:05:47Z

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

dvidsilva · 2015-06-17T17:52:11Z

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 · 2015-06-18T00:48:01Z

@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…

evelynharthbrooke · 2015-06-20T16:43:03Z

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

gmarik · 2015-06-23T18:28:01Z

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

evelynharthbrooke · 2015-06-23T23:23:33Z

@gmarik Alright. 😃

Openpalm · 2015-06-29T13:35:08Z

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 · 2015-06-29T14:27:38Z

@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 · 2015-07-02T14:43:11Z

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

ryanoasis · 2015-07-07T11:50:14Z

I have some interest in lending a small hand 😄

evelynharthbrooke · 2015-07-07T14:11:45Z

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

gmarik · 2015-07-08T15:52:58Z

@KamranMackey yeah looks like it!

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

evelynharthbrooke · 2015-07-08T16:08:57Z

@gmarik You're welcome. :)

ryanoasis · 2015-07-08T18:42:00Z

👍

gmarik · 2015-07-09T00:57:06Z

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

Post your feedback here in case of any questions.

ryanoasis · 2015-07-09T01:06:12Z

@gmarik cool thanks 👍

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 · 2015-07-09T01:10:15Z

@ryanoasis

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

gmarik · 2015-07-09T03:26:23Z

@KamranMackey master is now reset back to cfd3b2d.

Let's first figure out process we gonna work

silfverstrom · 2015-07-09T07:36:21Z

@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 · 2015-07-09T13:16:50Z

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

gmarik · 2015-07-09T14:13:05Z

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

wsdjeg · 2015-09-16T23:55:21Z

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

trygveu · 2015-09-17T05:54:26Z

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 ?

👍 @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 · 2015-09-17T13:20:11Z

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 · 2015-09-17T13:32:44Z

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 · 2015-09-21T12:40:29Z

@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" 😄

trygveu · 2015-09-21T15:51:41Z

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

ryanoasis · 2015-09-24T14:41:08Z

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

trygveu · 2015-10-10T20:22:41Z

@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 · 2015-10-17T18:26:21Z

which is better vundle or spf13?

vyp · 2015-10-17T20:51:24Z

@b232wang they are two different things

wsdjeg · 2015-10-26T01:31:02Z

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

gmarik · 2015-10-26T06:37:32Z

@wsdjeg please feel free to add a PR!

The `Vundle` project was moved into its own GitHub organization. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ref: https://github.com/VundleVim/Vundle.vim See also: * VundleVim/Vundle.vim#383 * VundleVim/Vundle.vim#608

davidlowryduda · 2018-01-26T17:59:43Z

Is there still a group of core people working on Vundle? If there is, then I will triage some of the issues and pull requests and recommend courses of action.

opsroller · 2018-01-26T20:21:13Z

Im still here, send em along!

ryanoasis · 2018-02-03T03:13:16Z

Still here doing what little I can (mostly triage and merging small things). I was gone for a bit but now back trying to triage and merge a few things.

ryanoasis · 2018-07-19T14:14:39Z

@gmarik I think @davidlowryduda has been fairly active and reached out to me about possibly being added to the Vundle org. As far as I can tell I have no ability to add anyone to the org.

The `Vundle` project was moved into its own GitHub organization. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ref: https://github.com/VundleVim/Vundle.vim See also: * VundleVim/Vundle.vim#383 * VundleVim/Vundle.vim#608

The Vundle project was moved into its own GitHub organization. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ref: https://github.com/VundleVim/Vundle.vim See also: * VundleVim/Vundle.vim#383 * VundleVim/Vundle.vim#608

fmoralesc mentioned this issue Jun 17, 2015

Plugin Package Manager neovim/neovim#247

Closed

gmarik mentioned this issue Jul 9, 2015

Help maintain Vundle #383

Open

trygveu mentioned this issue Sep 17, 2015

Think about how to collaborate with VAM/vim-pi/NeoBundle #387

Closed

ryanoasis mentioned this issue Sep 24, 2015

New Repo? #649

Closed

wsdjeg mentioned this issue Oct 8, 2015

Fix error on empty scope artur-shaik/vim-javacomplete2#107

Merged

hockeybuggy mentioned this issue Apr 26, 2017

Switch to dein hockeybuggy/dotfiles#20

Merged

Takeover Vundle #608

Takeover Vundle #608

Comments

gmarik commented Jun 16, 2015

Progress:

Potential Volunteers

Shougo commented Jun 17, 2015

Shougo commented Jun 17, 2015

gmarik commented Jun 17, 2015

Shougo commented Jun 17, 2015

Shougo commented Jun 17, 2015

opsroller commented Jun 17, 2015

Shougo commented Jun 17, 2015

gmarik commented Jun 17, 2015

dvidsilva commented Jun 17, 2015

gmarik commented Jun 18, 2015

evelynharthbrooke commented Jun 20, 2015

gmarik commented Jun 23, 2015

evelynharthbrooke commented Jun 23, 2015

Openpalm commented Jun 29, 2015

Shougo commented Jun 29, 2015

silfverstrom commented Jul 2, 2015

ryanoasis commented Jul 7, 2015

evelynharthbrooke commented Jul 7, 2015

gmarik commented Jul 8, 2015

evelynharthbrooke commented Jul 8, 2015

ryanoasis commented Jul 8, 2015

gmarik commented Jul 9, 2015

ryanoasis commented Jul 9, 2015

gmarik commented Jul 9, 2015

gmarik commented Jul 9, 2015

silfverstrom commented Jul 9, 2015

ryanoasis commented Jul 9, 2015

gmarik commented Jul 9, 2015

wsdjeg commented Sep 16, 2015

trygveu commented Sep 17, 2015

Shougo commented Sep 17, 2015

wsdjeg commented Sep 17, 2015

ryanoasis commented Sep 21, 2015

trygveu commented Sep 21, 2015

ryanoasis commented Sep 24, 2015

trygveu commented Oct 10, 2015

b232wang commented Oct 17, 2015

vyp commented Oct 17, 2015

wsdjeg commented Oct 26, 2015

gmarik commented Oct 26, 2015

davidlowryduda commented Jan 26, 2018

opsroller commented Jan 26, 2018

ryanoasis commented Feb 3, 2018

ryanoasis commented Jul 19, 2018