There are things you can do here. The higher the number, the more
complex it is:
0) create a github account.
1) Goto github.com, search the sigrok repository, and fork all the 14
repositories to your own account.
https://github.com/orgs/sigrokproject/repositories
2) Check if your github repositories are in sync with the official
github repositories, and sync them if they are not:
https://sigrok.org/gitweb/
3) Check if the github action for pulseview correctly creates a
installer, and fix that if it's not working:
https://github.com/sigrokproject/pulseview/blob/master/.github/workflows/build.yml
https://github.com/sigrokproject/sigrok-build/blob/master/.github/workflows/build.yml
4) Check what pull requests exist, and try if you can pull them into
your version of sigrok on your github account. You can find pull request
for libsigrok here:
https://github.com/sigrokproject/libsigrok/pulls
Finding the pull requests for the other 13 repositories is left as
exercise for the reader.
5) After pulling the pull requests, test sigrok/pulseview to see if the
pull requests are actually solving problems.
6) When the official version of sigrok changes, merge these changes into
your version, and re-test if everything still works.
7) Keep doing all this, and maybe get accepted in the official team of
sigrok.
On 10/11/25 2:46 AM, Alexandre Souza wrote:
That is a sad thing :(
But how can I help being a noob? I know no programming and I'm more in
the poor side than anything!?
73 de PU2SEX Alexandre
Em 09/10/2025 09:58, Ladislav Laska escreveu:
Hi all!
It's sad that sigrok is not receiving much attention and I understand
the original maintainer(s) might not have the time or interest to
continue development. However, the project still works great for many
use cases and there are a lot of PRs open on github, many of them
reasonably new - currently being ignored and authors demotivated.
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
