search

vim-perl / vim-perl6

Vim runtime files for Perl 6 support. This has moved to the Raku organization.
https://github.com/Raku/vim-raku
17 stars 22 forks source link

Find new maintainer #25

Open petdance opened 4 years ago

petdance commented 4 years ago

vim-perl6 needs to be taken over by someone who will do whatever is necessary to convert to Raku.

Anyone interested in doing this? Please leave a note here on this ticket.

zostay commented 4 years ago

I'm interested.

jdv commented 4 years ago

I can "help/do it" if need be.

petdance commented 4 years ago

@zostay I can transfer it over to your account whenever. You'll need to talk to Bram when it comes time to send him Raku files for inclusion in vim.

zostay commented 4 years ago

@jdv Help would be great. I'm willing to take this on as a project lead, but I'm not sure I'd be the best lead developer on this one. I can make sure PRs get tested and merged. I'm willing to jump in and do what I can to the code too, but but my vim-scripting fu is more casual than comprehensive at this point.

@petdance I can't do much with it for a few days, but I can probably look into handling rename issues sometime before Christmas. Any time you want to transfer is fine.

I don't know anything about talking with Bram, so any pointers you have would be great. You can reach me via my CPAN email address or my last name at gmail.com or my first name at last name .com if you have any details you want to brain dump. Or, if not, I can figure it out.

Thanks so much for leading on this up till now, Andy. I have literally used the vim-perl6 plugin weekly or even daily for various hobby projects for the past 4 years.

Cheers.

petdance commented 4 years ago

I don't know what there is to do with it. @hoelzro is who's maintained the Perl 6 side of it all along. He split it out from the vim-perl into its own set of files.

petdance commented 4 years ago

As to talking to Bram, you can just email him. He'll probably want to know what should be done with perl 6 vs Raku.

zostay commented 4 years ago

I've begun making the raku renaming changes over on my fork:

https://github.com/zostay/vim-raku/tree/perl6-to-raku

At this point, I have done a little cleanup, renamed most references and variables containing perl6 to raku, and added support for .raku, .rakutest, and .rakudoc file suffixes.

From here, I think some of the keywords that have been added or updated since 6.c need to be updated. That should take care of all the low hanging fruit I already know about. After that, I can start thinking about other fixes.

petdance commented 4 years ago

Are you at the point where I can shut down the vim-perl6 repo here and point everyone to yours?

zostay commented 4 years ago

I decided I didn't like it being homed on my account. It now has a more permanent home at:

https://github.com/Raku/vim-raku

Feel free to shutdown here and point there.

Thank you so much, Andy! You rock.

petdance commented 4 years ago

What about the other 11 issues in the issue tracker? Should I transfer them over?

petdance commented 4 years ago

Have you made code changes to the repo yet? I'm thinking it might just be easier, and GitHub would handle the redirects better, if I transferred ownership of the repo entirely at once.

zostay commented 4 years ago

Code changes are done and on the master branch now. Transferring the issues is fine. I've already announced the transition on my blog and posted it to reddit.

petdance commented 4 years ago

Unfortunately, it looks like I can't transfer them outside of the vim-perl organization.

petdance commented 4 years ago

I'm going to archive the project now. The issues should still be available, just unchangeable, so you can copy them over manually if you want.