I also hope it won't die. I think it's well worth supporting. I'm not in a great position to do that myself but will try to do something if I can.
I have been watching the project for a while, and think that the original developers burnt out (too many demands, not enough encouragement, not enough help) and that the reviewing was a major sticking point. I don't want to attach any blame there. I don't know whether it was a need for more reviewers, a lack of submissions, or what. Personally I didn't feel up to reviewing to the proper standards. I felt it was a project with very good standards and didn't want to compromise that. I think it could be revived and if we had written requirements for how it was to be reviewed I could be convinced to help. I'm not aware of any particular split or loss of people, tey just faded out of conversation one at a time. I don't know if any could be persuaded to return or even just advise on what was most needed. If we can't easily and with cooperation set up replacements for the organisation, I think a good idea might be to fork it. We can acknowledge the original work but admit we're a new team and that any failings are not due to the original codebase. I would not be happy unless it was clear the problems are due to a falling off of community support rather than historical failings. On Thu, Oct 9, 2025 at 2:16 PM Ladislav Laska <[email protected]> wrote: > 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. > > I think the community should offer a helping hand with the project and > offer at least some basic support in running the project. Depending on > how the original authors want to be involved, I think it would be a good > idea to appoint some community maintainers (ideally somebody who > contributed in the past) and give them enough privileges to merge PRs > and potentially release new versions. Alternatively, people could > volunteer to review & test PRs -- I'm up to looking into some, but it is > unclear if it would lead to something, since not even some simple ones > are being merged for around a year. > > What is the general sentiment about this? Is there a will to help keep > the project running from the community & current maintainers? > > I hope we won't let the project just die, since it's a crucial piece of > opensource software in the embedded engineer's toolbox. > > Best regards, > Ladislav > > > _______________________________________________ > sigrok-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sigrok-devel >
_______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
