[This is a mail to a Debian bug report. If you are not affiliated with Debian but somehow involved into engauge-digitizer we would appreciate any clarification about the different forks.]
Hi Stuart, I perfectly agree that it makes sense to maintain this package in the Debian Science team. I actually took the freedom to create a repository there[1] and granted Thomas owner permissions to have full access to the repository. I confirm that there are lots of forks of this project around and they seem to have in common that all have switched of issues. So my plan to open an issue for clarification about those forks failed. Available forks: 1. https://github.com/SerifeGitHub/engauge6 Mark Mitchell did some commits there in 2015 2. https://github.com/sj/engauge-digitizer-copy "Copy" not fork; last commit in 2018 --> https://github.com/sj/engauge-digitizer-copy/issues/1 3. https://github.com/TomDittrich1/engauge-digitizer Fork from 1. 1747 commits ahead 0 tags Last commit on Jun 27, 2023 4. https://github.com/alexdejong0304/engauge-digitizer Fork from 1. 1623 commits ahead 40 Tags, latest is v12.2.2 from Jul 12, 2020 Last commit: Mark Mitchel authored on Aug 14, 2020 5. https://github.com/jasonnicholson/engauge-digitizer Fork from 4. 1 commit ahead 41 Tags, latest is v13 from Aug 14, 2020 Last commit *today* 3h ago by Jason H. Nicholson 6. https://github.com/akhuettel/engauge-digitizer No fork information 43 Tags, latest is v12.9.1 from Jun 23, 2025 Regarding Qt6 this commit sounds promising: https://github.com/akhuettel/engauge-digitizer/commit/a03d6fadaa5b4e9c33a35e19e4d8d38dba6611fa Opened issue https://github.com/akhuettel/engauge-digitizer/issues/5 I guess this should be the packaging target. 7. Wrote issue to "Qt6 test" https://github.com/hoehnp/engauge_test_qt6/issues/1 I intend to base the packaging in Debian Science team on 6. Any comments are welcome Andreas. [1] https://salsa.debian.org/science-team/engauge-digitizer/ -- https://fam-tille.de
