Why forking the original repo ?

theniceboy / coc-flutter-tools

Rich Flutter development experience for (Neo)vim

64 stars 5 forks source link

Why forking the original repo ? #21

Closed AdrienLemaire closed 2 years ago

AdrienLemaire commented 2 years ago

Arriving on your github repo, I see

This branch is 73 commits ahead, 62 commits behind iamcco:master.

Your description implies that coc-flutter is not being maintained anymore and you took over, but that doesn't seem to be the case. Wouldn't it be in the best interest of the flutter coc.nvim community to concentrate the efforts on one repo ?

I'm confused as to which plugin I should go with :)

theniceboy commented 2 years ago

Hmmmm I'm not how you got the message that coc-flutter is not being maintained and I took over... but anyways, FYI

coc-flutter is still being maintained with great efforts.
coc-flutter-tools is an active fork of coc-flutter with some of the features that are immature to be merged to the main branch.
If you're plugin searching, you might want to look at https://github.com/akinsho/flutter-tools.nvim as well :)

AdrienLemaire commented 2 years ago

@theniceboy thank you for the quick and detailed reply! I see I made some wrong assumptions and am glad to have cleared this out.

Can I take it that you will keep your fork up to date with the main branch ? that your plugin is kind of an alpha release with new features that we can hope to see later in the main branch ?

And now, you just gave me another option, I didn't know about flutter-tools.nvim ^^ Strikken by FUD, don't know which one to go with. I wonder how many flutter developpers are on vim, I thought we were a minority.