Where can/should I contribute to the project?

[jonstelly]

Related to #367 are there any specific areas where you could use some help, @feschber ? I'd be happy to help out but not sure where best to jump in... random thoughts:

• release process - happy to work on ci/cd and github workflows and builds if the current release process is burdensome and that's holding up more frequent releases?
• os installation - I see there's a windows MSI PR open, I'd love to see a winget install for lan-mouse
• configuration - I see the save config pr, not sure exact state of that, but the initial user workflow of configuring via the gui would be nice, just need to be able to save that config I think.

My goal is to reduce the workload of maintaining lan-mouse if that's something you're interested in? Maybe we could get some projects set up in github to coordinate?

[feschber]

Hi @jonstelly. Thank you for your interest in this project, I certainly could use some help in maintaining this project.
I've invited you to a project. For now its private, but I guess we can make it public as well.

[feschber]

Something that would also tremendously help would be clearing out some old issues that are no longer relevant in the newer version.

[feschber]

As for #280, my current plan is to build the .msi package without the vc-redistributable and tell users to install that seperately.
Other than CI integration, it is mostly in a useable state, I just need to find the build commands again.

[nbolton]

build the .msi package without the vc-redistributable

That's the route we chose with Deskflow, but it turns out Microsoft's recommended approach is to make a bundled .exe where you ship both MSI files (which installs one after another).

[jonstelly]

Sounds good, I checked out the project and will start getting up to speed.

I spun up a handful of PRs:

A small one
#371 - fix: remote key-up on triggered release

A few drafts for discussion/feedback:
#372 - feat: workflow and build updates
#373 - feat: windows service for uac+login support
#374 - chore: developer experience - pre-commit hook, ai instructions, yaml formatting

[benroose]

Hi @feschber, in a similar question to @jonstelly's original ask here:
There are some features/issues I'd like to work on. However, these would be specific to my work in Linux - Wayland/X11. I do not use, nor have easy access to test, MacOS or M$ Windows systems. Are you open to reviewing new pull requests which are specific to an operating system, i.e. Linux?
Cheers!

[feschber]

Hi @feschber, in a similar question to @jonstelly's original ask here: There are some features/issues I'd like to work on. However, these would be specific to my work in Linux - Wayland/X11. I do not use, nor have easy access to test, MacOS or M$ Windows systems. Are you open to reviewing new pull requests which are specific to an operating system, i.e. Linux? Cheers!

I'd like to keep the platform dependent backends as small as possible. So any features that don't need to be platform specific should stay out of there.
However if you want to implement something that requires changes to the emulation / capture backend (say cursor entering at the correct position which requires absolute cursor movement), its fine if you implement it for just some of the backends (e.g. X11), as long as it doesn't break the build on other platforms (might need a dummy implementation).

[benroose]

Thanks @feschber for the clarification and for all the work! I fully understand your position here.
I'll see within features I'm considering as to what would be Linux specific vs. platform independent prior to creating any pull requests. I wish you all the best with this project!!