Vundle.vim: Help maintain Vundle

[gmarik]

UPDATE(2015-07-08): see #608

Previously #241 it was moved here because of number of unrelated posts which were derailing conversation. Please only posts that are related to the subject.

Here we go again:

Hi everyone!

If you have some time to spare cleaning up Issues and PRs let me know!

Current number of issues/PRs (24/85) is overwhelming and far beyond my OSS capacity.

Things that would be helpful:

• sorting out features/bugs
• responding to /closing/ dealing with user issues
• reproducing issues
• testing PRs

Some of you already doing that and I really appreciate it, but this time you'll become an official maintainer! )

You'll get commit rights if necessary.

Comment below if interested!

Thanks all!

PS: please share with anyone who'd be interested!

[marlun]

I would also like to help. Not sure what I'll be able to do yet but I'll try to take look at the issues and get involved in bringing them down.

I also made som modifications to the docs, not sure if it's something that you like @gmarik but I sent a pull-request.

[gmarik]

@marlun cool!
Thanks for volunteering!

[gmarik]

Some ideas:

• organize people into groups by OperatingSystem so we can have atleast 1person taking a look. Is there a way to group people and then mention a group? How about http://gitter.im
• or create test suite for each OS. Have no idea how to do it yet, but it's probably much better option…

[starcraftman]

Hi @marlun thanks for helping. If you need any issues closed/tagged ping me with an @.

@gmarik gitter seems interesting, though I find it a bit disconcerting they require full write access to my github profile. That seems like an oversight on GitHub's part. I am otherwise not aware of a way to group users on GitHub natively so they can be bulk notified.

An alternative is we could make an IRC channel on Freenode. Could double for dev chat and some difficult support/collabs with non-regular contributors. Still a reliable easy way to communicate, and has a web interface at: http://webchat.freenode.net for those not at a unix machine.

Edit: I have to admit gitter.im looks much better than IRC, also with GitHub integration. I think I'm willing to overlook my paranoia if you want to use this. Only advantage I see IRC having is not requiring github, people can just log onto a channel with no sign up and talk. I guess we'd use gitter just for internal chat.

[starcraftman]

@gmarik I forgot, GitHub does have organizations, don't know if that is what you are looking for. See https://github.com/blog/674-introducing-organizations

[marlun]

On Mon, Feb 10, 2014 at 06:48:02PM -0800, starcraftman wrote:

@gmarik I forgot, GitHub does have organizations, don't know if that is what you are looking for. See https://github.com/blog/674-introducing-organizations

An organizations seems a little bit excessive for a single vim plugin :)

[jalcine]

An organization would be a bit extreme :crocodile: but I can understand why delegating control would be nifty. However, for the sake of keeping it a quasi-meritocracy of sorts, it may be required. It's not like @gmarik is always going to be by his laptop to give people access. That also doubles up on the frequency of said additions.

Side-note: I'm so :+1: for http://gitter.im. It rocks.

[Shougo]

or create test suite for each OS. Have no idea how to do it yet, but it's probably much better option…

I tested current Vundle test script. But it is too hard to execute in Windows environment.
It should be improved.

[starcraftman]

@marlun I guess. Just thinking out loud with keystrokes.

@jalcine @gmarik I just tried gitter.im, when I logged in and gave it access to my github all I see is my own repos listed. I see my fork of Vundle but not gmarik/Vundle. I believe @gmarik you must log in to the system first to actually create the rooms to your repos. To share th link go to top right gear icon and share the link for gmarik/Vundle with us. I tried just changing starcraftman for gmarik but got 404.

As a test, you guys can try to post on my forks gitter address. https://gitter.im/starcraftman/vundle

Edit: You should probably put the gitter.im link on the main page for convenience.

[jalcine]

Whomever has push access can create the link, I think.

[starcraftman]

@jalcine Sure I could, but the link doesn't work until gmarik logs into gitter and gives them authorization to use his github account. You can try it yourself by going to https://gitter.im/gmarik/vundle

[marlun]

Just curious, what does gitter.im improve compared to having the discussions in issues? In issues if someone wants you to take a look at a message they just @marlun you, will that work with gitter or will it become just another thing that you have to put time into keeping up with? I know I might sound a little negative but I'm onestly just curious if it will really help or if it's just the new cool? :)

[starcraftman]

@marlun Damn accidentally deleted my response.

Basically, it is like an IRC room attached to github repos. Over IRC it supports github markdown wiki syntax and @/# references. It also persists. I guess the only reason to use it is to avoid posting in issues all the time like this help thread (which we use as general discussion). In that sense, I don't see any major functional improvements to our flow. It is quite nifty though.

[marlun]

Well if it supports @ references and sends e-mail notifications it's better then I thought it was.

To get back to the main issue about all the Vundle issues, has there been anything decided about how we should deal with very old issues and pull-requests?

[Shougo]

To get back to the main issue about all the Vundle issues, has there been anything decided about how we should deal with very old issues and pull-requests?

I think this:
If it is old bug report and it is not occured now, it should be closed.
If it is feature request, duplicated request should be closed.
If it is pull request, it should be reviewed and tested. It is not easy...

[gmarik]

to be clear i was thinking about gitter only _so we can do group notifications_ (if it's available, i've not checked it out yet) Like when we want people to test a Windows bugfix we do

@vundle_win please take a look at #0

and everyone on "Windows Vundle Users" receives the message to test if possible.

Automated test-suite is far better option but it's a long-term solution which is not available right now.

So

• gitter only for group notifications(if available)
• automated test-suite is preferred though.

I think this:
If it is old bug report and it is not occured now, it should be closed.

Yes, something like this. feel free to add your idea…

[gmarik]

Dealing with issues drafted in wiki

Let's come up with something that works well for everyone…

[Shougo]

I think this:
If it is old bug report and it is not occured now, it should be closed.

Yes, something like this. feel free to add your idea…

Thanks. I think most of issues user information is not enough.
But we cannot contact with the users who created issues if the issues are old.
So, I think they should be closed.

[amar-sanakal]

I am interested to help here. I'm not sure how I can do it but I'll take a look at the open issues and see which ones I could tackle.

[marlun]

While wrapping my head around the Vundle source-code I might have some questions about it and I'm just wondering if anyone is up for answering some e-mails? I feel it would be better to do it over e-mail instead of creating issues about it?

[gmarik]

@amar-sanakal cool! Thanks for stepping up! Let us know when you need help with anything…

@marlun how about just creating a single issue like "questions-dev"? Could be helpful for others too…

[marlun]

@gmarik a single issue or a single label? I'm just asking because "questions-dev" sounds more like a label :)

[Shougo]

@marlun how about just creating a single issue like "questions-dev"? Could be helpful for others too…

Yes, I think issues are better than E-mails.
If it is issue, other people can join with it.

[gilligan]

Sorry for reactivating this month old thread, but I wanted to suggest the use of http://waffle.io for vundle. It creates a nice issue board that makes it much easier to see which issues are open or in progress and if so by whom. Any thoughts on this ?

[berryp]

:+1: for http://gitter.im/. Just checked it out. It's very lightweight and seems to fit the bill perfectly. IRC is great for open discussion - especially where you want to keep issue comments clean - but is not useful for notifications.

With regards to contributions, I see there are a number of very old tickets for minor bugs or feature requests that could probably be closed as wontfix in favor of opening a new issue if and when someone actively calls for it. A lot of projects suffer from a long list of issues that are hard to keep on top of and a lot of the older ones are either no longer valid or are just never going to be looked at. I think it's OK to just accept that and have them closed. The same could go for pull requests, but that's not as straightforward.

[gilligan]

@gmarik I would like to help cleaning up issues & pull requests (Thing is I just got chickenpox from my son so I'm locked up at home for ~10 days which means i could dedicate some time to this) Running vim on mac&linux. Only windows I can't test.

[jdevera]

@gmarik could you please create a gitter room for vundle? Even if you choose not to use yourself, it could be left open for other who would wish to. I think it would have made recent conversations held in PR's and issues much more painless.

Gitter now does not require write access, only readonly access to user and email.

cc @starcraftman

[gmarik]

@jdevera done!

[whatyouhide]

@gmarik Hey there, I'm willing to help cleaning up issues and PRs. I saw there are a lot of open but resolved issues, I'm mentioning the authors and asking them to close the issues but most of them don't answer.

[jalcine]

@whatyouhide maybe in another issue, we could list those issues (issue-in-issue, hah!) and let people with the ability to close the repo mark them as resolved. Or we could write them here.

[whatyouhide]

@jalcine That's a good idea. Maybe listing them here isn't too clean and we risk they'll get buried, but I feel opening another issue just for listing issues (as much as I love how meta it is) kind of defeats the purpose? :) Maybe let's wait what @gmarik has to say?

[lucc]

I think it is redundant to have an issue to list issues that can be closed. It is also an extra step of work. And it is not really an issue with Vundle.vim if there are unclosed issues on Github.

If you feel that some issue needs to be closed the best way in my opinion is:

1. comment on the issue and let the owner close it
2. call a team member with @example and request them to close it, something like

@example close?

[whatyouhide]

@lucc Ok, will do :+1:

[luochen1990]

I'm an heavy user of Vim and Git, and had written some Vim plugins myself. I found there is a lot of works to do here, and maybe I can help :)

[gmarik]

@luochen1990 please take a look at #608

[PeterDaveHello]

@gmarik I can help sorting out features/bugs, reproducing issues, testing PRs.

[ryanoasis]

@PeterDaveHello that would be great!

I have been trying to get PRs merged in when I can but haven't had time to do much testing on the non-trivial PRs.

[PeterDaveHello]

@ryanoasis so should I do anything else to be invited in VundleVim?

[ryanoasis]

@PeterDaveHello Sure well I think just trying to contribute without being part of the organization is a start and then I could see you being granted permissions after that.

per gmarik:

Things that would be helpful:

• sorting out features/bugs
• responding to /closing/ dealing with user issues
• reproducing issues
• testing PRs

I am a bit wary about inviting more right now because I think we had some good intention but breaking changes from a team member who had good intentions but maybe was a bit overzealous.

That being said whatever gmarik does or decides can overrule anything I have said :stuck_out_tongue:

[PeterDaveHello]

@ryanoasis hmmm ... so how can I sorting out features/bugs? I thought I should label them, close the duplicated issues, hope I didn't think it wrong, thanks.

[ryanoasis]

@nfischer

Thanks. Yeah you should try to ping @gmarik for permissions, maybe he will grant some more now. Yeah alternative for now is all we can do I guess :blush:

wrapping up unfinished PRs

Yeah that'd be cool, I just am trying to help out starting with small stuff and slowly increasing into larger items here..

@PeterDaveHello

Sorry most of the items I told you about do require organization permissions.

Unfortunately without organization permissions you cannot apply labels or close issues.

The one thing you can do is follow up on issues and/or try to replicate issues to see if they are or are not still actually issues.

[akinjide]

Hi @gmarik I read stumbled on your blog post and this issue, I would love to contribute to this project.

[ryanoasis]

@andela-abankole Would love to see more contributors

[tetreault]

Hello - I'm new to vim and spend most of my time in javascript-land. That having been said, I have been using VIM only for 2 months now and Vundle is great. Any way for a developer (mostly web and some mobile) and vim newbie to help out? Any low hanging fruit I could tackle?

[ryanoasis]

@tetreault Awesome thanks. Yes and yes. Low hanging fruit? Mostly just following up on issues.

We had been working on 0.10.3 but ran into some errors on the branch :disappointed: ... and I think those involved have been busy. I have since then merged a few low impact PRs to master and followed up and/or closed issues. I have been away for a while from this project but I want to get back into contributing. Perhaps if there was a strong core of members wanting to get active I would be even more inclined to jump back in when I am free :smile:

[tetreault]

Awesome thanks for the reply @ryanoasis. I'll do my best to try getting involved! This weekend I'll sift thru the issues some more. Vundle has been awesome, I want to give back!

[reyreaud-l]

Hey @gmarik, started using vundle for some time now and I just read your blogpost about the issues of the project, would love to contribute! Will start answering issues if I can or look into them!

[tetreault]

@gmarik do you mind posting the blog post? would be interested in reading it.

[ryanoasis]

It is fairly easy to find.. but here it is: http://www.gmarik.info/blog/2014/why-i-stopped-contributing-to-vundle (at least I think this is the one you are referring to)

[tetreault]

@ryanoasis it was also fairly easy to link to in that person's comment :)

[ryanoasis]

@tetreault I didn't get you :stuck_out_tongue: . I hope I didn't come across negatively (not my intention)

[wsdjeg]

hello, as a old contributor, may I Join the vundle github org?

[ryanoasis]

I've been away too but as I get more time I'll be trying to help out more. Would love to have @wsdjeg join

[wsdjeg]

@ryanoasis who is the ower of this org? please send me an invite link.