Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a trusted maintainer to continue development #521

Open
3ter opened this issue May 28, 2024 · 8 comments
Open

Find a trusted maintainer to continue development #521

3ter opened this issue May 28, 2024 · 8 comments

Comments

@3ter
Copy link

3ter commented May 28, 2024

Since the last release nearly 3 years ago there have been 0 actual code changes, only translations (v0.9.11...master). Someone needs to go through the PRs and approve or reject them.

Surely someone from the contributors can be dedicated to be a maintainer. Unfortunately I've got no time 😆 . And I haven't been active here at all. I just think the app is a blessing in writing Umlauts on an English keyboard and some other nice stuff (like soon™).

@Solomon1732
Copy link

To support your stance, there are some PRs like #459 which are no-brainers to check and accept or reject. Yet the PR in question has been sitting around since late February 2022. Why? It's not the only one in a like state.

@3ter
Copy link
Author

3ter commented May 30, 2024

@samhocevar I forgot to notify you to make sure you're aware of the topic. Thank you for your consideration.

@Solomon1732
Copy link

If he still won't answer any time soon then a would be maintainer may wish to fork the project.

@MartinBonner
Copy link

wincompose is not nearly such a popular download as liblzma - but we still need to exercise a modicum of caution if a "helpful" new maintainer comes along.

@Sax388
Copy link

Sax388 commented Aug 29, 2024

Last PR merged by @samhocevar is from 2022-02 (https://github.com/samhocevar/wincompose/commits?author=samhocevar).

I think the community should move on to a fork. Unfortunately there are only two promising ones right now as I can see:

  • A very small one containing a nice change though (allowing any compose key except for esc)
  • A larger one also containing some dependency updates

Unfortunately the one from @arm32x says in a note at the top that they don't intend to (publicly) maintain the fork.
I don't know if @Elyviere would be interested in taking up the torch.

@Elyviere
Copy link

Unfortunately I no longer use wincompose so I'm afraid I won't be maintaining my fork either.

@Solomon1732
Copy link

@Elyviere Do you use an alternative or do you use nothing?

@Elyviere
Copy link

I use a keyboard with qmk firmware, so I've added all the characters I frequently use in different layers instead. This way I'm not reliant on installing third party software. I do have wincompose bound to a key on that layer as well (which is why I needed my fork, I have weird keys on that layer), for the rare case where I need a weird character, but I go weeks without using wincompose even once at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants