AntiMicroX / Tickets / #5 Promoting AntiMicroX

Anonymous - 2020-08-28

Originally posted by: trymeouteh

I think by getting a Windows installer would definitely help. I am a Linux user and I am glad this is made for Linux DEB installer, however most gamers use Windows.

And if there isn't already, I hope this is in the AUR for Arch based distros.

I like how they renamed the project to make it less confusing.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-28

Originally posted by: trymeouteh

And what can help is to Star this github project

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-28

Originally posted by: OlegPopow

Forgive my impertinence, but I have to raise an aspect that is impossible to find information about here. You seem to be an undisputed champion of promotion and advertising. Cool, but... What about project development and fixing real problems? First of all, the question of future updates of the Qt. library. Probably you will have to make appropriate changes in the project to keep it working. There were also some unresolved bugs on the old repository. Are you going to do something about it or focus only on promotion?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-28

Originally posted by: pktiuk

@OlegPopow
I understand your curiosity (But I think, the next time you should just open new issue, that's the point of tag: question).
Currently, I want to finish, what I have started, when old repository was still active.
I want to provide good packages to allow users avoiding compilation.
I am also working on setting up and configuring this repository to make working with it easy (like for example: https://github.com/AntiMicroX/antimicroX/issues/10)
I am also going to make some cleanup in CMakeLists.txt

In terms of code development I want you to know I am not familiar with this code yet. There are a lot of classes in this project, almost none of them are documented at all.
For now, I have generated some docs using doxygen and I will start reading code to understand what is inside.
When I will briefly understand how it works, I will start fixing bugs, which I will be able to reproduce, and later I am going to move on to other bugs and adding features.
In terms of preparations for future releases of QT I can only say: I don't know I know C++, but I am not very experienced with QT, so it may take some time before I will start thinking about it.
Don't expect any rapid progress in this matter, because it is just my side project developed in free time next to full-time job and university projects.
I am thinking about keeping this project alive without losing traction gained by legacy AntiMicroX and the only help I have now is @gombosg.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-29

Originally posted by: OlegPopow

In terms of code development I want you to know I am not familiar with this code yet. There are a lot of classes in this project, almost none of them are documented at all.

To be honest, I haven't met too many Open Source projects in which classes would be documented. And to be even more honest, I don't recall that such a thing would be practiced too often even in KDE projects - and a large group of people work there. The previous maintainer has been developing the program on his own for two years, and for lack of anyone to help, he focused on fixing the bug. It's hard to expect one person to take care of absolutely everything, right? Anyway, in big companies, it also happens that a newly recruited employee is thrown to continue the project after the previous one and then you also have to reckon with the fact that such documentation will be either residual... or there will be no such documentation at all.

I am thinking about keeping this project alive without losing traction gained by legacy AntiMicroX and the only help I have now is @gombosg.

As above. I fully understand that your team is two people... but on the other hand it is twice as big as the previous one!

Don't expect any rapid progress in this matter, because it is just my side project developed in free time next to full-time job and university projects.

Of course, no one expects a miracle. The foundation for the program to be usable and build correctly on different versions of Qt. Qt 6.0 is coming, so good luck remains!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-31

Originally posted by: gombosg

@OlegPopow

Anyway, in big companies, it also happens that a newly recruited employee is thrown to continue the project after the previous one and then you also have to reckon with the fact that such documentation will be either residual...

Yeah, it's called 'legacy project maintenance', and that's a large chunk of work at any fairly large company. 🙂

Of course, no one expects a miracle. The foundation for the program to be usable and build correctly on different versions of Qt. Qt 6.0 is coming, so good luck remains!

Thanks for the suggestions.

@sirlucjan - after getting the previous repo archived

I simply don't understand all the finger pointing and blaming going around here in the previous repo, due to 1 (un)star.

I'd just use Hanlon's razor at this point: "Never attribute to malice that which is adequately explained by stupidity."

@juliagoda

The problem with archiving the repo without any contingency plan, links to forks is that existing users are now fairly cut off from further updates. They have to go through the hassle of finding actively maintained forks of a project that already went through several ones.

I believe that one core value of open-source is civilized collaboration, the fact that volunteers united together can create lasting value for users.

I appreciate all the useful work that you have done so far on the repo, and would like to do everything possible to keep a good relationship with you and previous antimicro maintainers, because this is what is the best for the users.

Kindly revert this commit or state some clear requirements towards us for listing forks in the README so that users know what options they have if they would like to keep using the software.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-31

Originally posted by: OlegPopow

@gombosg

You seem to be a jolly good fellow so I will share some advice with you. In this case, personal email contact would look much better instead of calling previous contributors to the board.

I simply don't understand all the finger pointing and blaming going around

Such matters are better handled privately. If you have any objections, just write an email and try to explain it outside the public space.

It is different to point out and report a bug that was not here. By the way, users often report bugs at the address they find in the "Help" menu in the application. You've already made some changes, just tag along and the problem will largely resolve itself.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-31

Originally posted by: gombosg

@OlegPopow

Such matters are better handled privately.

It was a public discussion originally, so I intended to continue it publicly.

Also, Github doesn't disclose e-mail addresses, so email is not an option, at least not initially.
Feel free to send me your e-mail address to gombosg at disroot dot. org, then let's continue the conversation there.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2020-08-31

Originally posted by: OlegPopow

I will give you a little tip. It is enough that you apply such a small trick:

https://github.com/AntiMicroX/antimicroX/commit/01bdca9179feb990c28a500dde38bdcb54b6d806.patch

And there you go. You know where to write an email. No further conversation is necessary, I am just an outsider.

May the Force be with you.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Promoting AntiMicroX

Program used to map keyboard buttons and mouse controls to a gamepads

Milestone

Searches

Help

#5 Promoting AntiMicroX

Discussion