madires / transistortester-warehouse Goto Github PK

Hi! this is an amazing project and I want to contribute to it by giving some advice on how to structure it to improve accessibility, maintenance and encourage more people to contribute, using the logic behind GIT and GITHUB. Right now I'm seeing 3 potential projects:

1. one to maintain the original k-firmware
2. one to maintain the new m-firmware
3. one to maintain the hardware

Instead of having an archive file for every version it would be better to have the source code (no archive) and use git tag's system to mark every version. This project could even consider to have a branch for each "flavor" of hardware and use the ISSUE an PULL REQUESTS capability of GITHUB or GITLAB in order to document bugs, improve access and encourage more people to contribute to it.

I know there is a thread in the EEVBLOG where all the improvements and bug's related to the transistor-tester are being made, but it is hard to find the information and follow the subject. A blog is good for conversation, asking for help, an the like, but it's not as good as GITHUB to document the development of this kind of projects.

If you have any interest in this suggestion, I'm working to separate the project as above-mentioned and I would be happy to help to implement this idea. If needed I could give you access to my repo to see how it looks like.