You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As many of you have noticed, I don't have much time to dedicate to this plugin, which is a shame because it deserves better.
I'm not abandoning it; I still use Gp.nvim many times a day. The project is just stable for my personal needs (although I have to admit I've been using it from a multi-provider branch for half a year now).
As can be seen from the example of multi-provider support, new features come slowly, partially because I don't want to break other people's setups and have certain standards to uphold.
The MIT license is there for a reason: if I drop dead tomorrow, anyone can pick up the flag and carry on. But there is another side to open source - the fragmentation into endless forks.
So, let's try a better way: making this a community project with multiple maintainers so I'm not the only one with the keys to the castle.
I am interested in merging my own things such as #125 and PRs I am interested in. I already contribute too much to FOSS but I have a good track (IMO) of not merging too crazy stuff.
@teto I've send you a collaboration invite (haven't played with this functionality yet). Btw. #125 has some pending comments to consider before merging.
The invite is expired or invalid, the link above doesn't work.
I'm just writing to tell you @Robitx that you have done a great job and the plugin is super useful. Thank you for open sourcing it.
I think your vision was great, no dependencies, the extensibility and features are just right. And stability is very important too, so I wouldn't sweat it if the plugin is evolving slowly. It is your vision what made it.
As many of you have noticed, I don't have much time to dedicate to this plugin, which is a shame because it deserves better.
I'm not abandoning it; I still use Gp.nvim many times a day. The project is just stable for my personal needs (although I have to admit I've been using it from a multi-provider branch for half a year now).
As can be seen from the example of multi-provider support, new features come slowly, partially because I don't want to break other people's setups and have certain standards to uphold.
The MIT license is there for a reason: if I drop dead tomorrow, anyone can pick up the flag and carry on. But there is another side to open source - the fragmentation into endless forks.
So, let's try a better way: making this a community project with multiple maintainers so I'm not the only one with the keys to the castle.
For starters, here's a Discord for anyone who wants to hang out and possibly help.
The text was updated successfully, but these errors were encountered: