Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

General discussion about AntiMicroX and further development #35

Closed
pktiuk opened this issue Sep 12, 2020 · 2 comments
Closed

General discussion about AntiMicroX and further development #35

pktiuk opened this issue Sep 12, 2020 · 2 comments

Comments

@pktiuk
Copy link
Member

pktiuk commented Sep 12, 2020

About

Issue for general discussion about AntiMicroX ant its further development.
Discussion about current state of app and its further development in general.

Current plans

This fork is a rather new, that's why we are currently focused on cleaning up the repository and preparing it for further development.
We are also working on making AntiMicroX easily available and updateable for users.
Then we are going to move on to fixing existing bugs
Later we will think about possible improvements and porting to QT6 (not released yet)

**Offtopic comments will be deleted/hidden to avoid spam.

@gombosg
Copy link
Collaborator

gombosg commented Sep 13, 2020

I totally agree about this. This is a feature-packed, well-functioning piece of software, ridden with bugs and codebase quality issues due to the long chain of maintainers.

IMO general priorities should be, considering our limited volunteer efforts as a bottleneck:

  1. Keep the builds green!
  2. Fix bugs for existing users, especially visible and ugly ones affecting basic functionality (like Wrong order for setting sets #6 and Right click - Turbo and Clear not working properly #7 😛).
  3. Reach a wider audience within existing OSes via consistent releases and more packaging (AppImage Submission #2, Flatpak packaging #9, Wayland support for keyboard emulation #32)
  4. Understand code base, and clean up. Remove dead code, refactor variable names, reformat syntax. This could open the project up for other people's PR submissions, too!
  5. Add more OS support (Restore Windows support #4, possibly also OSX though that may be a long shot) to reach even more users.
  6. IMO the lowest priority is adding new features, because adding new features is only worth the effort if we already have a considerable amount of users (unless it's some 'killer feature') and the codebase quality is good enough to make the feature easier to maintain.

@mhalano
Copy link

mhalano commented Nov 29, 2020

I would like to add my own issue to this discussion because it's quite aligned. The issue #100 I opened is to more Linux distros can use AntiMicroX. I saw a good discussion was started on #87 so antimicro becomes antimicrox on Debian and Ubuntu repositories.

@AntiMicroX AntiMicroX locked and limited conversation to collaborators Sep 11, 2021
@pktiuk pktiuk closed this as completed Sep 11, 2021
@pktiuk pktiuk unpinned this issue Sep 11, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants