Maintainers wanted

[LoLei]

Hello all razer-cli users and friends,

since I am not in a position where I can spend much time on razer-cli, other than perhaps merging pull requests and publishing a new release, we're in dire need of new maintainers.

If anyone feels up for it, feel free to post it here.

Everyone is welcome to open pull requests and issues, but maintainers will have permissions to manage pull requests and issues, commit code directly, and publish releases.

[4kbyte]

In many ways, openrazer is the "upstream" project, with CLI operations mostly deferring to the daemon. Perhaps the openrazer org is open to taking in the project?

I don't intend to presume. I'm just triaging the bug tracker while I wait for polychromatic to compile on gentoo, meanwhile razer-cli is just one more Python package.

[FishyLines]

Not a bad idea but if someone needs to maintain here it can def be done, I'm not sure they feel like they wish to maintain these gui's and cli's tbh

[LoLei]

Thanks for the suggestion @4kbyte! I added the suggestion for openrazer here: openrazer/openrazer#2493

Also many thanks for responding to some of the issues currently open for razer-cli. If you're interested you could also take over some of the maintenance tasks of razer-cli yourself.

You'd get access as described here:

Maintainers will have permissions to manage pull requests and issues, commit code directly, and publish releases.

Perhaps the repo should also at some point be moved to a GitHub org and be accessible under razer-cli/razer-cli. But let's see what openrazer says.

[4kbyte]

I would post the first patch by PR, but would want to know: what's your preference in committing directly to mainline?

(And optionally posting a PR just to merge right away.)

Only a matter of time before I add pytest, too.

[LoLei]

I added you as a collaborator 🎉

You should get an invitation.

For PyPI, I'd need you account name there too to invite you.

Regarding commits, it's up to you, but I would recommend still creating PRs for increased visibility and tracking in the issues.

[4kbyte]

Accepted! 🎉

PyPI: 4kbyte

Hello, world! I've been operating on a low profile in recent years, so I'm linking a random sample of past contributions to establish my background as an open source maintainer: v, util-linux, jupyter, adding pytest.

It'll be great to have multiple maintainers under a long-running GitHub org. 🤝

[LoLei]

PyPI invitation is also sent ✅

[4kbyte]

Accepted! https://pypi.org/project/razer-cli/

[4kbyte]

Today:

• 13 issues triaged, with analysis.
• 9 issues closed.
• 4 issues remain, each "fundamental" product experiences to track over time.
• 2 new issues outlining architectural and maintenance issues.
  • Nonsense commands are successful (exit code: 0). #93
  • Improve Maintainer QoL #94
  • Ready for any maintainer to pick up.
• 1 PR to fix type annotations across the entire codebase.
  • Fix type annotations and call site inconsistencies. #92

[4kbyte]

Here's one more, a good first issue:
#95

Alias razer-cli help TOPIC to razer-cli -man TOPIC.

[FishyLines]

Hello all razer-cli users and friends,

since I am not in a position where I can spend much time on razer-cli, other than perhaps merging pull requests and publishing a new release, we're in dire need of new maintainers.

If anyone feels up for it, feel free to post it here.

Everyone is welcome to open pull requests and issues, but maintainers will have permissions to manage pull requests and issues, commit code directly, and publish releases.

I'd love to be a maintainer! How can I start? I've found this program useful for so so long, would love to help I have more freetime as I'm young.

[LoLei]

Hi @FishyLines, thanks for reaching out and your interest in maintaining this project!

You can start by looking through the open issues.

For example a good one would be: #94

See if you feel comfortable working on these things, and feel free to submit new issues and pull requests.

Once you have a couple of contributions under your belt, you'll be added as a maintainer to the repo, with push/release access, etc.

[4kbyte]

Hi @FishyLines, thanks for your interest. I'm a maintainer on the project and will be available for questions on issues and pull requests.