Community fork | Looking for maintainers?

[sebszyller]

There have been no commits to the project for half a year. The issues and PRs are piling up.

I don't blame @epwalsh, life gets in the way, interest wanes.

Nevertheless, it would be great to see this project continue. And as is today, it means either a community fork, or allowing more people to be core maintainers.

Thoughts?

[neo451]

Yes I would really like to see this get some motion, I just got into this plugin and obsidian and really likes the concept, it is sad to see PRs like the blink.cmp support that I need not merged, I would certainly help to maintain this project if possible.

[erratic-pattern]

I am currently building a patched obsidian-nvim as part of my nixpkgs overlay, with a few of the open PRs patched in to fix various bugs I've encountered. I'm happy to create a fork with those changes added, or if anyone else wants to create a fork I am willing to contribute with PR review or new features (I think a plugin/extension system would be very nice to have).

Ideally the best way to go forward would be to add maintainers to the existing repo, optionally moving the repo out to an org.

[BrendanMesters]

I love the plugin, but I do agree that some energetic active maintainers would be nice (Absolutely no shame to epwalsh btw, they've already done an amazing job).

Idk whats the best way to go about that (forks or more maintainers), kindof depends on what epwalsh wants, but if there are people who would like to do so that would be awesome (sadly don't really have much freetime myself either, classic)

[marcocofano]

Kudos to epwalsh for the amazing work. It would be nice to have some guide on future direction for the project so that the community could help growing it in ways that are compatible with the vision of the mantainer.

I could dedicate some spare time but it would be great to know what to expect.

I like the idea of an extension mechanism. This is one of the features that would benefit the most the project going forward.

[TheMeaningfulEngineer]

I also wouldn't mind helping out as well to keep it alive.
Shall we wait for a week to see if @epwalsh responds, and if not just agree who takes over fork?

[ffricken]

I also wouldn't mind helping out as well to keep it alive. Shall we wait for a week to see if @epwalsh responds, and if not just agree who takes over fork?

I think the week is over, right? And there are no responses, but a couple of new issues even, so i think a fork is in order. Any volunteers?

[guspix]

I do think that the ideal setup here would be moving the repo to an organization and adding several maintainers. Just to get the ball rolling I created an organization and forked the repo, plus made a couple of fixes so that the Github actions run successfully. That being said, I don't think I'm really the ideal person to maintain the fork since my Lua knowledge is pretty limited, so my plan would be to add some other owners to the organization, and even cede control completely if anyone with the know-how can commit to really giving this project the love it deserves. In the meantime I'm willing to triage issues and do some of the "office" work to get the fork off the ground.

So, any volunteers to help out with the fork? In this thread @neo451, @erratic-pattern, @marcocofano and @TheMeaningfulEngineer mentioned being willing to help. Looking at recent pull requests I also saw @adamtajti put in a lot of work to add blink.cmp support, I don't know if he might have any interest in helping maintain it.

And of course, if the great @epwalsh comes back at any point and wants to keep helping out, take over the project or whatever he prefers, I'll always be open to that.

[TheMeaningfulEngineer]

@guspix
Thanks for the initiative. The organisation approach looks great.
I'm a bit of the same as you on the Lua knowledge.
Just recently set up the lsp for lua and nvim and am somehow managing the nvimg config in lua but that's about it.
So also can't be the core maintainer.

But am willing to start understanding the codebase organically (and the vim lua api).
Open to help also by triaging issues and testing PRs.

Shall we wait a bit to see if someone feels at home with lua and nvim and is open to be the main code guy with the help of others on the periphery?

If that doesn't happen and there's enough of us who are willing to help (the ones you mention), we might as well see how it goes just by going through the issues and the PRs...

[guspix]

Yeah, that sounds great! Let's give it a couple of days and see who chimes in, then we can open an issue on the fork where we can continue this conversation and start triaging/merging/etc

[neo451]

@guspix
Thanks for your work, I think I can help as the "code guy" if nobody steps up. I have written quite a few thousands of lines lua, and have written a big plugin like feed.nvim.
But I do need more people to do the "office" work, for example I have no idea how to bring PRs to that fork, since I am just a self taught hobby programmer. I have only ever merge a few PRs, and I am certain I could mess something up if not careful.
So feel free to add me to the org, I will go ahead and get more understanding of the codebase and make some proposals for some small rewrites I have in mind, and meanwhile we can start testing and merging the big features like snacks.picker and blink.cmp support.

[guspix]

For anyone following this, I just opened a discussion for the next steps on the forked repo! Anyone is welcome. I'd love to hear your thoughts, whether you are thinking of contributing or are just following the discussion. @TheMeaningfulEngineer @neo451 we can talk there about roles and whatever we may need.

[neo451]

There have been no commits to the project for half a year. The issues and PRs are piling up.

I don't blame @epwalsh, life gets in the way, interest wanes.

Nevertheless, it would be great to see this project continue. And as is today, it means either a community fork, or allowing more people to be core maintainers.

Thoughts?

Hi, it would be helpful if the title of the issue is changed to something more clear and inviting like "A community fork of the repo is here!"

[neumachen]

@guspix I'd like to contribute to this patched repo, I actively use this plugin for my day to day notes.

[guspix]

@guspix I'd like to contribute to this patched repo, I actively use this plugin for my day to day notes.

That's great! Feel free to join the linked discussion on the other repo or open any issues or PRs you like, any help is welcome! If you're looking for a specific type of role (triaging issues, helping with docs, adding features) let me know!