Repository ownership

[bmish]

Continuing the discussion from here: https://discord.com/channels/688543509199716507/1085655150691102751/1323092132227059844

@platinumazure has expressed interest to transfer ownership of the repository.

Options include:

• https://github.com/eslint-community (@voxpelli @MichaelDeBoey)
• https://github.com/qunitjs (@Krinkle)
• Myself (@bmish) as one of the primary maintainers since 2020

I'm open to all of these options, but I'd suggest we consider if one of those organizations is interested in owning it first, ideally the qunit organization with the subject-matter experts.

I have tagged relevant people from each organization for comment.

[voxpelli]

👍 I would let the qunitjs org get the first chance to host it (due to being subject-matter experts) and if they don't I think we can host it in eslint-community

[Krinkle]

I'd be happy to host eslint-plugin-qunit in the QUnit org. If you transfer the repo and send me a list of names, I'll create a team with y'all in it and grant it write+maintenance access to the repo.

[bmish]

Great! I believe it's just @platinumazure and myself who would need access. There haven't been any other regular contributors in recent years.

[voxpelli]

@Krinkle Great! I also got an invite now, but I will not have to join, I'm just here on behalf of @eslint-community 🙂

[platinumazure]

I've transferred the repository to qunitjs. Please let me know if there's anything else I need to do here. Thank you @Krinkle for agreeing (on behalf of qunitjs) to take this on!

[Krinkle]

You're welcome. I've created the @qunitjs/eslint team, added this repo, and added coverallsapp/github-action to the allowed list of actions. That should be it in terms of access and CI. Let me know if you need anything else!

You can also find me in https://app.element.io/#/room/#qunitjs_qunit:gitter.im.