Takeover Vundle #608

Open
gmarik opened this Issue Jun 16, 2015 · 51 comments

Projects

None yet
@gmarik
Contributor
gmarik commented Jun 16, 2015

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:

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

Potential Volunteers

@Shougo
Contributor
Shougo commented Jun 17, 2015

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

https://github.com/ctrlpvim

@Shougo
Contributor
Shougo commented Jun 17, 2015

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
Contributor
gmarik commented Jun 17, 2015

Thanks @Shougo, will do that!

@Shougo
Contributor
Shougo commented Jun 17, 2015

:-)

@Shougo
Contributor
Shougo commented Jun 17, 2015

I have announced it in my Twitter account.

@opsroller
Member

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

@Shougo
Contributor
Shougo commented Jun 17, 2015

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

@gmarik
Contributor
gmarik commented Jun 17, 2015

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

@fmoralesc fmoralesc referenced this issue in neovim/neovim Jun 17, 2015
Open

Plugin Package Manager #247

@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
Contributor
gmarik commented Jun 18, 2015

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

@KamranMackey
Contributor

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

@gmarik
Contributor
gmarik commented Jun 23, 2015

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

@KamranMackey
Contributor

@gmarik Alright. 😃

@Shokodemon

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
Contributor
Shougo commented Jun 29, 2015

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

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

@ryanoasis
Member

I have some interest in lending a small hand 😄

@KamranMackey
Contributor

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

@gmarik
Contributor
gmarik commented Jul 8, 2015

@KamranMackey yeah looks like it!

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

@KamranMackey
Contributor

@gmarik You're welcome. :)

@ryanoasis
Member

👍

@gmarik
Contributor
gmarik commented Jul 9, 2015

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

Post your feedback here in case of any questions.

@ryanoasis
Member

@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
Contributor
gmarik commented Jul 9, 2015

@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
Contributor
gmarik commented Jul 9, 2015

@KamranMackey master is now reset back to cfd3b2d.

Let's first figure out process we gonna work

@silfverstrom
Member

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

@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
Contributor
gmarik commented Jul 9, 2015

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

@KamranMackey
Contributor

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

@ryanoasis
Member
@KamranMackey
Contributor

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

@ryanoasis
Member

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

@gmarik
Contributor
gmarik commented Jul 11, 2015

@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
trygveu commented Sep 16, 2015

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
Member

@trygveu I think this is a really good idea. 👍

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
Contributor
wsdjeg commented Sep 16, 2015

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

@ryanoasis
Member

@wsdjeg is that question meant for @Shougo ?

@wsdjeg
Contributor
wsdjeg commented Sep 16, 2015

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

@vyp
vyp commented Sep 16, 2015

@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
Contributor
wsdjeg commented Sep 16, 2015

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

@trygveu
trygveu commented Sep 17, 2015

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
Contributor
Shougo commented Sep 17, 2015

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
Contributor
wsdjeg commented Sep 17, 2015

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
Member

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

@ryanoasis ryanoasis referenced this issue Sep 24, 2015
Closed

New Repo? #649

@ryanoasis
Member

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

@wsdjeg wsdjeg referenced this issue in artur-shaik/vim-javacomplete2 Oct 8, 2015
Merged

Fix error on empty scope #107

@trygveu
trygveu commented Oct 10, 2015

@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
vyp commented Oct 17, 2015

@b232wang they are two different things

@wsdjeg
Contributor
wsdjeg commented Oct 26, 2015

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
Contributor
gmarik commented Oct 26, 2015

@wsdjeg please feel free to add a PR!

@alrra alrra added a commit to alrra/dotfiles that referenced this issue Jul 29, 2016
@alrra alrra [vim] Update `Vundle` related URLs
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
ab26909
@adsric adsric added a commit to adsric/dotfiles that referenced this issue Jul 29, 2016
@adsric adsric [vim] Update `Vundle` related URLs
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
0aadbb8
@wingy3181 wingy3181 added a commit to wingy3181/dotfiles that referenced this issue Aug 7, 2016
@wingy3181 wingy3181 [vim] Update `Vundle` related URLs
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
ae3a6f1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment