Suggestions to improve communication in the project

[mats-nk]

Hi,
I have enjoyed that you (@widapro ) have got active again and brought the project forward.

And I have some suggestions:

1. Activate "Discussions", under settings there is an checkbox for Discussions. This is an alternative to issues and have issues for just that and "feature requests" in discussions.
2. Wiki. If you enable the wiki others can contribute with features or build instructions without touching the README.

And below is a list with issues that can be closed:

#4
#8
#10
#34
#54
#56
#58
#59

I'm unsure about the status on these, but I could check them if you wish.

#45
#46
#47

And I have also made a list with feature request that could be moved to “discussion” if you find that a good idea.

[mats-nk]

I wish I could help you, but the lack of communication is discouraging!
I have analysed the code and there is several changes that could be made to make it more stable, but I'm not going to work against you.
Can you please answer if you wish to get assistant or not!

[widapro]

Hi @mats-nk,
Thanks for reaching out, and I apologize for the radio silence. I understand how the lack of communication can be frustrating.

To answer your question directly: I would gladly welcome your help. My slow responses are simply due to limited free time, not a lack of interest in the project or your contributions.

I appreciate the effort you've already put in. Your recent PR was very useful, and it is great to hear you've been looking into code stability. Thank you also for the list of issues that can be closed—that saves me a lot of time.

Regarding your suggestions:

Wiki: I completely agree. We definitely need a dedicated space for build instructions outside of the README. I will enable the Wiki shortly.

Discussions: While it is a useful feature, my time to manage the project is limited right now. I don't have the bandwidth to moderate a separate section, so I'd prefer to keep feature requests and questions in the Issues tab for now to keep everything in one place.

I would be glad to have you continue contributing to the project. Let me know what you have in mind regarding the stability changes you mentioned.

[mats-nk]

Thanks for the answer and I suspected it was time constrains, rather than lack of interest.

And as I have been a "Arduino IDE" guy have this project forced me into "VS Code" and from dredging it I am actually liking it, so thanks!

And as of stability issues. I'm not a “programmer”, more a system guy. But to my understanding is the use of String one cause to memory fragmentation. Another issue I have seen is that one library hasn't support for the ESP32 S2... and guess what ESP32 variant I have ;-)

I could also offer you a small PCB that is just a carrier for a Wemos D1 Mini and make it easy to connect to a MAX7219. I will post details later.

[mats-nk]

Wiki doesn't work, and I think you are heading in the wrong direction by adding more features than focusing on stability.
Stability is the number one factor for success and a high WAF value, IMHO.