New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please, approve co-maintainer #124

Open
amerlyq opened this Issue Nov 27, 2015 · 11 comments

Comments

Projects
None yet
5 participants
@amerlyq

amerlyq commented Nov 27, 2015

I would like to ask you to share write/merge permissions to this repository with somebody interested in from the community. It would allow to boost currently stagnated development of this plugin.
Because your participation in project becomes less and less observable, amount of issues and forks exponentially increases. We need someone to put this in order and quickly respond to requests.

Of course, you could say, fork it and develop by itself. But. Everybody, and newbies especially, chooses trunk with most stars, which currently is yours. There are no distinguishable chances for any other fork to get that many stars in nearest future to outweight this.

I propose @albfan as co-maintainer, if he agrees.
Otherwise, anybody ready to tidy up issues list and revise forks will do.

@albfan

This comment has been minimized.

Show comment
Hide comment
@albfan

albfan Nov 28, 2015

many thanks but I disagree. With near thousand starts I bet ag.vim is a stable and useful plugin on it's actual shape for many people. @amerlyq let's see if we can organize my fork and persuade @rking about its features, and then let's think on next step.

I will stick on upstream plugin as much as I can, so changing

Plugin rking/ag.vim

to

Plugin albfan/ag.vim

must be an acceptable annoyance meanwhile

albfan commented Nov 28, 2015

many thanks but I disagree. With near thousand starts I bet ag.vim is a stable and useful plugin on it's actual shape for many people. @amerlyq let's see if we can organize my fork and persuade @rking about its features, and then let's think on next step.

I will stick on upstream plugin as much as I can, so changing

Plugin rking/ag.vim

to

Plugin albfan/ag.vim

must be an acceptable annoyance meanwhile

@losingkeys

This comment has been minimized.

Show comment
Hide comment
@losingkeys

losingkeys Dec 4, 2015

Collaborator

I haven't heard from @rking in awhile, and as far as I know I'm the only other maintainer (not sure how to check that) on rking/ag.vim. I've been meaning to get to the issues, but haven't found much extra time. I'm hoping to get to them more in the beginning of the new year, and we can discuss merging some forks then if you like.

Some other things this project needs (imo):

  • Code of conduct (not that anyone's done anything I've noticed, but it's good to have)
  • CONTRIBUTING.md to help codify direction, goals, and help out new contributors

Other than that we should discuss the other forks and see if we can make everyone happy without adding too much code 😄.

Collaborator

losingkeys commented Dec 4, 2015

I haven't heard from @rking in awhile, and as far as I know I'm the only other maintainer (not sure how to check that) on rking/ag.vim. I've been meaning to get to the issues, but haven't found much extra time. I'm hoping to get to them more in the beginning of the new year, and we can discuss merging some forks then if you like.

Some other things this project needs (imo):

  • Code of conduct (not that anyone's done anything I've noticed, but it's good to have)
  • CONTRIBUTING.md to help codify direction, goals, and help out new contributors

Other than that we should discuss the other forks and see if we can make everyone happy without adding too much code 😄.

@albfan

This comment has been minimized.

Show comment
Hide comment
@albfan

albfan Dec 4, 2015

Love the idea: lot of talk abd few code changes possible. That implies a lot of code review and some better comunication channel, so I added a room in

https://gitter.im/albfan/ag.vim

And added all of us. Let's see how it goes.

albfan commented Dec 4, 2015

Love the idea: lot of talk abd few code changes possible. That implies a lot of code review and some better comunication channel, so I added a room in

https://gitter.im/albfan/ag.vim

And added all of us. Let's see how it goes.

@amerlyq

This comment has been minimized.

Show comment
Hide comment
@amerlyq

amerlyq Dec 14, 2015

Alright, as for necessities, described in initial post on this thread.
I have reviewed all currently active forks, which have diverged/stagnated -- therefore will not be merged eventually, and listed relevant differences in albfan#53 to merge them by ourself.
Also, there was noticed rather often tendency to fork only to change buffer mappings.
Therefore, mechanics to change them will be provided, derived from #76.
I hope such improvement will lessen quantity of minor forks, at least in future.

amerlyq commented Dec 14, 2015

Alright, as for necessities, described in initial post on this thread.
I have reviewed all currently active forks, which have diverged/stagnated -- therefore will not be merged eventually, and listed relevant differences in albfan#53 to merge them by ourself.
Also, there was noticed rather often tendency to fork only to change buffer mappings.
Therefore, mechanics to change them will be provided, derived from #76.
I hope such improvement will lessen quantity of minor forks, at least in future.

@losingkeys

This comment has been minimized.

Show comment
Hide comment
@losingkeys

losingkeys Apr 10, 2016

Collaborator

Hmm... I'm not sure what to do here. I'd like to revive this discussion, but there's one thing I'm still confused about. I'm guessing @rking owns the copyright on the changes on this project since it was forked from https://github.com/mileszs/ack.vim, and various other maintainers own the copyright on some code. Because of this, I'm not sure who (other than @rking) is allowed to license this project.

I'm not a laywer, so it'd be nice to get some legal advice on this before adding a license and merging things. As a side note: ack.vim added a license to their project at the start of this year.

Collaborator

losingkeys commented Apr 10, 2016

Hmm... I'm not sure what to do here. I'd like to revive this discussion, but there's one thing I'm still confused about. I'm guessing @rking owns the copyright on the changes on this project since it was forked from https://github.com/mileszs/ack.vim, and various other maintainers own the copyright on some code. Because of this, I'm not sure who (other than @rking) is allowed to license this project.

I'm not a laywer, so it'd be nice to get some legal advice on this before adding a license and merging things. As a side note: ack.vim added a license to their project at the start of this year.

@albfan

This comment has been minimized.

Show comment
Hide comment
@albfan

albfan Apr 11, 2016

Well, then there's two sides for this issue. One is to contact @rking to get permissions to fork or change this codebase. and second (most important for me) is decide what features are interesting to merge (test suite, aggroup, api changes, support for X search native tool, compatibility with nvim)

I guess we can discuss second point meanwhile first point is being resolved.

albfan commented Apr 11, 2016

Well, then there's two sides for this issue. One is to contact @rking to get permissions to fork or change this codebase. and second (most important for me) is decide what features are interesting to merge (test suite, aggroup, api changes, support for X search native tool, compatibility with nvim)

I guess we can discuss second point meanwhile first point is being resolved.

@tplunket

This comment has been minimized.

Show comment
Hide comment
@tplunket

tplunket May 26, 2016

@rking hasn't had any activity on GitHub in nearly two years and the website that is listed in the user's profile yields a DNS error. I'm guessing that this person is no longer around.

tplunket commented May 26, 2016

@rking hasn't had any activity on GitHub in nearly two years and the website that is listed in the user's profile yields a DNS error. I'm guessing that this person is no longer around.

@losingkeys

This comment has been minimized.

Show comment
Hide comment
@losingkeys

losingkeys Jun 20, 2016

Collaborator

Hey everyone. I'm really sorry but there are a couple of issues that mean I'll be deprecating this repo:

  • Though I'm not a laywer, the licensing issues appear to mean this code is effectively not open source, though it's public
  • I haven't had a lot of time to maintain this lately, and pull requests and issues have sort of fallen by the wayside
    Because of these issues, I'm deprecating this repo. I think the best move going forward would be to re-open the pull requests in the original fork: https://github.com/mileszs/ack.vim, and to add this config to your vimrc:
let g:ackprg = 'ag --vimgrep --smart-case'                                                   
cnoreabbrev ag Ack                                                                           
cnoreabbrev aG Ack                                                                           
cnoreabbrev Ag Ack                                                                           
cnoreabbrev AG Ack  
Collaborator

losingkeys commented Jun 20, 2016

Hey everyone. I'm really sorry but there are a couple of issues that mean I'll be deprecating this repo:

  • Though I'm not a laywer, the licensing issues appear to mean this code is effectively not open source, though it's public
  • I haven't had a lot of time to maintain this lately, and pull requests and issues have sort of fallen by the wayside
    Because of these issues, I'm deprecating this repo. I think the best move going forward would be to re-open the pull requests in the original fork: https://github.com/mileszs/ack.vim, and to add this config to your vimrc:
let g:ackprg = 'ag --vimgrep --smart-case'                                                   
cnoreabbrev ag Ack                                                                           
cnoreabbrev aG Ack                                                                           
cnoreabbrev Ag Ack                                                                           
cnoreabbrev AG Ack  
@albfan

This comment has been minimized.

Show comment
Hide comment
@albfan

albfan Jun 20, 2016

Seems all we want to share a great ag vim plugin, but we are stagnated on this repo.

I'm pretty comfortable with this little mess, but would love to share it with others.

Count on me to collaborate in any fork about ag. As you suggest I will try to reopen an issue about group option on mileszs/ack.vim

mileszs#94 (comment)

albfan commented Jun 20, 2016

Seems all we want to share a great ag vim plugin, but we are stagnated on this repo.

I'm pretty comfortable with this little mess, but would love to share it with others.

Count on me to collaborate in any fork about ag. As you suggest I will try to reopen an issue about group option on mileszs/ack.vim

mileszs#94 (comment)

@ches

This comment has been minimized.

Show comment
Hide comment
@ches

ches Jun 20, 2016

I'm not a laywer, so it'd be nice to get some legal advice on this before adding a license and merging things. As a side note: ack.vim added a license to their project at the start of this year.

I just wanted to clarify FWIW: the issue referenced there was not when the license was actually added, I couldn't have made that decision unilaterally myself without clearing it with previous contributors. I just added an explicit complete LICENSE file for distribution packaging policy. ack.vim was licensed under the Vim license since its first commit.

Unfortunately ag.vim seems to have removed mention of any license from the help doc file at some point after the fork, thus some contributions have happened under no clear license. That is indeed an unfortunate sticky situation 😦

I'm happy to discuss co-maintainers on ack.vim, I'd invite you to open a new issue on the repo about collaboration to start discussion. It might take a bit of time to get help from Miles to make admin changes happen, but he's generally been responsive. I'm sure we can set up Gitter for the project if that makes discussion easier, perhaps even move the project to an organization so it's easier to share management responsibilities.

I will note: improving existing behavior and fixing bugs is most welcome, but ack.vim began as a light wrapper that showed how elegantly Vim's existing grep functionality could be extended, and I personally do not want to see it grow a lot of new features now, in fact after some time working on its maintenance I've developed the philosophy that it should have fewer features. I'm leaning toward using vim-grepper myself because it's very close to a more modular approach I wanted to take if I had made a fresh start before that project did. That said, if the community loudly demands such new features, I'm willing to yield, but I may be more likely to step down at that point if there is new blood helping to maintain the project. For now I have no intention to do that while I'm the only active maintainer.

Anyway, we can continue this sort of conversation in ack.vim's project context if that's a direction people want to pursue.

ches commented Jun 20, 2016

I'm not a laywer, so it'd be nice to get some legal advice on this before adding a license and merging things. As a side note: ack.vim added a license to their project at the start of this year.

I just wanted to clarify FWIW: the issue referenced there was not when the license was actually added, I couldn't have made that decision unilaterally myself without clearing it with previous contributors. I just added an explicit complete LICENSE file for distribution packaging policy. ack.vim was licensed under the Vim license since its first commit.

Unfortunately ag.vim seems to have removed mention of any license from the help doc file at some point after the fork, thus some contributions have happened under no clear license. That is indeed an unfortunate sticky situation 😦

I'm happy to discuss co-maintainers on ack.vim, I'd invite you to open a new issue on the repo about collaboration to start discussion. It might take a bit of time to get help from Miles to make admin changes happen, but he's generally been responsive. I'm sure we can set up Gitter for the project if that makes discussion easier, perhaps even move the project to an organization so it's easier to share management responsibilities.

I will note: improving existing behavior and fixing bugs is most welcome, but ack.vim began as a light wrapper that showed how elegantly Vim's existing grep functionality could be extended, and I personally do not want to see it grow a lot of new features now, in fact after some time working on its maintenance I've developed the philosophy that it should have fewer features. I'm leaning toward using vim-grepper myself because it's very close to a more modular approach I wanted to take if I had made a fresh start before that project did. That said, if the community loudly demands such new features, I'm willing to yield, but I may be more likely to step down at that point if there is new blood helping to maintain the project. For now I have no intention to do that while I'm the only active maintainer.

Anyway, we can continue this sort of conversation in ack.vim's project context if that's a direction people want to pursue.

@losingkeys

This comment has been minimized.

Show comment
Hide comment
@losingkeys

losingkeys Jun 20, 2016

Collaborator

@ches, @albfan: thanks for your comments. I tend to agree that smaller plugins are better. I might open a few PRs, but for the most part using ag with ack.vim hasn't been a problem. I guess we'll see what kind of features people want going forward. Forking again is always an option.

Collaborator

losingkeys commented Jun 20, 2016

@ches, @albfan: thanks for your comments. I tend to agree that smaller plugins are better. I might open a few PRs, but for the most part using ag with ack.vim hasn't been a problem. I guess we'll see what kind of features people want going forward. Forking again is always an option.

klutzy added a commit to klutzy/... that referenced this issue Jun 22, 2016

Taluu added a commit to Taluu/dotFiles that referenced this issue Jun 24, 2016

tomaszj added a commit to tomaszj/dotfiles that referenced this issue Jul 13, 2016

RossBarnie added a commit to RossBarnie/dotfiles that referenced this issue Oct 7, 2016

sfate added a commit to sfate/dotvimmy that referenced this issue Apr 5, 2017

ondrowan added a commit to ondrowan/dotfiles that referenced this issue Apr 14, 2017

belminf added a commit to belminf/dotvim that referenced this issue Jul 5, 2017

camelpunch pushed a commit to camelpunch/vim-config that referenced this issue Aug 11, 2017

Andrew Bruce
switch to using ack
The Ag plugin is in a quagmire of licensing issues: rking/ag.vim#124 (comment)

thorncp added a commit to thorncp/dotfiles that referenced this issue Nov 17, 2017

Use ack.vim instead of ag.vim
ag.vim has been deprecated for awhile and the maintainer suggests using
ack.vim.

rking/ag.vim#124 (comment)

overthink added a commit to overthink/dotfiles that referenced this issue Jan 23, 2018

joshukraine added a commit to joshukraine/dotfiles that referenced this issue Mar 11, 2018

chusiang added a commit to chusiang/vimrc that referenced this issue Mar 17, 2018

Replace the ag.vim with ack.vim
The ag.vim has EOL, so I start use the ack.vim .

* rking/ag.vim#124 (comment)

chusiang added a commit to chusiang/vimrc that referenced this issue Mar 18, 2018

Replace the ag.vim with ack.vim
The ag.vim has EOL, so I start use the ack.vim .

* rking/ag.vim#124 (comment)

joshukraine added a commit to joshukraine/dotfiles that referenced this issue Mar 27, 2018

justyns added a commit to justyns/jdotfiles that referenced this issue May 16, 2018

Remove ag.vim since it's deprecated
See rking/ag.vim#124 (comment)

The auther recommended using the original ack.vim that is what ag.vim
was forked from.  I also remapped :ag to :Ack and set :Ack to use the ag
command if it's available.

drn added a commit to drn/dots that referenced this issue May 24, 2018

localstatic added a commit to localstatic/vimrc that referenced this issue May 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment