mirror of
https://github.com/feschber/lan-mouse.git
synced 2026-05-15 14:15:52 -06:00
[GH-ISSUE #370] Where can/should I contribute to the project? #196
Labels
No labels
Xorg
documentation
enhancement
macos
pull-request
question
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/lan-mouse#196
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jonstelly on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/370
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:
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 commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 4, 2026):
Something that would also tremendously help would be clearing out some old issues that are no longer relevant in the newer version.
@feschber commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 4, 2026):
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 commented on GitHub (Feb 5, 2026):
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!!
@feschber commented on GitHub (Feb 6, 2026):
btw @jonstelly is there a way I can contact you?