Looking for Collaborators

[akinsho]

I'm looking for anyone(or multiple people) working with neovim in flutter regularly who is/are willing to help maintain this plugin. I've become increasingly busy with other plugins and work, and am actually not working with flutter in my day job any more (having changed roles).

So would be good to get some more people who are more up to date on developments to help pitch in. Is a new feature coming out? Has there been a change in the LSP spec or the LSP server

This plugin is fairly low effort since the number of nvim users working in flutter is not huge and the LSP spec doesn't move very quickly.

If you're interested, please leave a comment

[sonu405]

This isn't a place for asking this,Sorry. but anyways Please tell me why the flutter-tools not working like the commands don't work after installing it with packer and calling the setup function in init.lua. Flutter is also in the path as flutter commands run in the terminal. There aren't any proper guides on youtube or anywhere else about this plugin. I have also texted you on reddit so if you have a little bit of time reply me there.

[akinsho]

@Jetandarkumar Please do not post on this issue for config or setup issues, this is really not the correct place at all. I don't use Reddit for chat or very much at all, so that is also not a good place to contact me. As I have mentioned in this issue, I don't have very much time for flutter specific work atm. Please open a separate issue with a clear explanation of exactly what isn't working and how you have set up nvim, flutter and this plugin and maybe myself or someone else will be able to help you.

[Thesmader]

Hi @akinsho. I am interested in helping maintain this plugin. However, I have fairly less experience developing plugins for neovim. However, I am willing to learn if I can get some help getting started. I rely on this plugin for editing code at my job and for personal projects. Would be awesome to help maintain it

[akinsho]

@Thesmader that fantastic 👍🏿 thanks for reaching out. So I plan on writing a contributing.md that goes over how the plugin works internally, and I'll link to some guides for lua as well. As far as languages go, it's definitely simpler than dart, so shouldn't be hard to pick up. Probably knowing the nvim API is the most involved bit, but you don't have to learn that, you can always just search help and see what comes up.

I'll add you as a collaborator on the repo 🥇

[avatarnguyen]

Like @Thesmader I don't have any lua knowledge yet but would like to learn. Because I am using this plugin everyday now, would love to contribute and help maintain as well.

[akinsho]

@avatarnguyen this is great news I'd greatly appreciate the help. I'm on holiday atm but once I'm back I'll set up the contribution docs and get you set up 👍🏿

[rlch]

Hey @akinsho! I'm also strapped for time, but I would love to help out where possible. I interact with Flutter regularly for work, and have been tinkering with Lua for quite a while now.

[dphaldes]

I use flutter a lot and would love to help in whatever way possible!

[barungh]

@Thesmader that fantastic 👍🏿 thanks for reaching out. So I plan on writing a contributing.md that goes over how the plugin works internally, and I'll link to some guides for lua as well. As far as languages go, it's definitely simpler than dart, so shouldn't be hard to pick up. Probably knowing the nvim API is the most involved bit, but you don't have to learn that, you can always just search help and see what comes up.

I'll add you as a collaborator on the repo 🥇

If I get help and guiding document, I will help to maintain it. Thank You.

[sidlatau]

Hi, @akinsho, thanks for the great plugin! I am using flutter daily, so I am willing to help to maintain the plugin too :)

[akinsho]

@sidlatau @rlch I've added you both as collaborators as well as you've both contributed quite a bit over time 👍🏿. Huge thanks to everyone else that has stepped up 🙌🏿. I think in terms of people to add as collaborators, rather than adding 5-6+ people, I think this plugin would probably benefit most from people raising issues and then PRs to tackle things that they want to see added, my hope is that it gets to a point where changes aren't really dependent on me after a while as long as the solutions are well thought through and reviewed by collaborators.

I'm still trying to find the time to document how this plugin works and write up a contributing.md but things off the top of my head that people could help contribute would be

• Vim help docs, either written manually or generated using one of the many tools. I personally think handwritten is best, but the most time-consuming.
  * Re-factoring this plugin to use nvim-0.7 features (Largely done now)
  - Removing the autocommand workarounds and using the builtin API
  - Removing the command workarounds and using the builtin API
• Looking at the dart LSP spec and seeing if any new things have been added such as color presentation which was added and incorporated here a while ago.

[radiKal07]

Will you still add that contributing.md file? It would be really helpful for any future maintainers.

[akinsho]

@Tudor07 I plan to when I have some time, kind of spread way too thin across quite a few plugins, and still trying to do other non-neovim stuff in my free time so, never feels like there's a moment. I'll start the document and if anyone has interacted to bits of the plugin they can feel free to add some descriptive section on the bits they know such as the fvm feature which @rlch added a while back, tbh I still haven't ever really properly used fvm so that bit is still somewhat unknown to me