Transfer plugin to asdf-community

[canterberry]

It's been quite some time since I have used Yarn, so my personal need for this plugin has subsided and with it, my attention.

If you don't want (or just don't have time) to maintain this plugin anymore can you please consider transferring it to community ? https://github.com/asdf-vm/asdf-plugins?tab=readme-ov-file#asdf-community

Originally posted by @kroleg in #36 (comment)

I would ask for maintainers/contributors here, but now that asdf-community exists, transferring this plugin to asdf-community seems to be the right move.

So, whoever wants to take the lead, here's how to proceed:

1. Fork this repo into the asdf-community org.
2. Create a PR in asdf-vm/asdf-plugins to change the URL/repo for this plugin to its new home in asdf-community, and feel free to reference this issue for confirmation/consent.
3. Create a PR in this repo to update the README and/or scripts to notify users of the new repo home.

Thanks, in advance, to whoever takes the torch from here! Cheers!

[ab-dauletkhan]

Hello!

I'm new to open source and contributing, so I want to make sure I'm on the right track. If I understand correctly, I should submit a pull request to asdf-community's infrastructure as if I were the maintainer, right?

[kroleg]

there are instructions in asdf-community repos https://github.com/asdf-community/.github/blob/master/GUIDELINES.md and they are a bit different from what @canterberry suggests (repo transfer instead of forking). Here is shortened version of guide:

Submit a PR to the infrastructure

Once the PR is merged, you will be invited to the organisation and then transfer the repository to the organisation.

Submit a PR to the infrastructure repository to put the repository under Terraform control.

Is it possible to do it? I mean do maintainers have time for it. If not i will start a discussion in asdf-community repo on how else can we move plugin there

[ab-dauletkhan]

Hi, @kroleg

I have submitted a PR to asdf-community/infrastructure and included your username as well, because I have found that you have been also contributing to the project.

[kroleg]

@ab-dauletkhan you and i are not maintainers, so we can't be maintainers in asdf-community (like you did in PR). @canterberry is also not interested in maintaining. So we need to find somebody (preferable from asdf core team) who will take on maintaining

[ab-dauletkhan]

Sure, I've deleted the branch

[kroleg]

@canterberry would it be possible to transfer this repo to asdf-community (that's their recommended way) or they only way is to fork it there?
asking this because if i ask them to fork it might take a while (ex: request to move asdf-flutter is 1 year old https://github.com/orgs/asdf-community/discussions/56)

[canterberry]

There may be other reasons why the completion of asdf-flutter has been so delayed (e.g: it does not have a "champion" pushing it through). Here, it looks like we have some momentum with at least two people (hooray!) will the motivation to see such a transfer through.

If y'all get the process started, I'll cooperate with anything you need on my end to get it completed.

[ab-dauletkhan]

Good morning, @canterberry!

Could you please check this guideline, seems like we have to find further maintainer

[canterberry]

Consider this issue #37 a PSA and Call for Maintainers.

I defer to the present maintainers and stakeholders in asdf-community, asdf, and Yarn, for selecting, sourcing, and/or vetting candidates, and invite anyone with the motivation and interest to consider volunteering.