Skip to content
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

Looking for a co-maintainer :) #202

Open
fdschmidt93 opened this issue Dec 18, 2022 · 3 comments
Open

Looking for a co-maintainer :) #202

fdschmidt93 opened this issue Dec 18, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@fdschmidt93
Copy link
Member

fdschmidt93 commented Dec 18, 2022

IMPORTANT: this does not mean telescope-file-browser.nvim dies. I have provided and will continue to do so critical maintenance on bugs. Mostly adding new features slows/slowed down materially.

E: For readers coming here later, I ended up using some of my Christmas time to actually end up getting started on some of the big features.. :D but let's see when they actually get rolled out ;)

E2: I'm always happy for more support, I might get back to telescope-file-browser more (finish big RFC + features) end of January / February

Hi there,

In case you (the reader) is unaware, I'm the original author of telescope-file-browser.nvim and (more used to be) a contributor to telescope.nvim.

During the pandemic, a lot of my free time was spent hacking in Lua on Neovim, learning about git etc etc in practice by contributing. These days, my focus (un-)fortunately is more on work, as I have a bunch of threads regarding my PhD I'm (afraid to say wrt the plugin) much more excited about than telescope-file-browser.nvim, that's from a practical standpoint largely feature complete for personal usage (#161 would be nice, tree-view would be nice -- spent quite some time here but it's quite tedious with ident guides).

I'm super grateful for the interest in and adoption of telescope-file-browser.nvim as an extension to telescope.nvim. At this point, however, I have to admit my lack of motivation mostly stemming from much less quality free time practically halted progress of the extension to a large degree.

That's why I'm looking ideally for a co-maintainer for ideally a prolonged time who has some prior experience in the Neovim lua, telescope ecosystem to co-maintain this extension with me, incl. replying to issues, tackling feature requests, etc. all of which I'm happy to provide guidance for.

Thank you for your consideration :)
FD

@fdschmidt93 fdschmidt93 added the enhancement New feature or request label Dec 18, 2022
@jamestrew
Copy link
Collaborator

Hey @fdschmidt93, I'd like to put my name in for consideration.
I've been following this plugin for a while occasionally submitting PRs and chiming in on other's issues and such. I have some minor contributions telescope as well few other plugins (often related to telescope extensions). I'm by no means an expert but I'm interested in continuing to learn more about telescope and neovim in general and some also interested in taking on more responsibility and to gain experience in maintaining OSS.

@fdschmidt93
Copy link
Member Author

Sure, very happy to have you aboard :) I'd just say dive in and attend issues/PRs, ping where required, and we'll take it from there.

If something doesn't work, we can always revisit later. My one rule these days is that we do our very best not to have breaking changes (as virtually almost anything the user could change for him/herself).

@jamestrew
Copy link
Collaborator

Thanks, sounds good 🚀
To me, this project feels mostly feature complete. There's still a pretty continuous stream of minor enhancements and options requests but I'll probably stick to encouraging and helping people customize their own configs over adding more and more options/actions.

In the meantime, I'll prioritize any bug fixes starting with any currently outstanding ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants