Folks, I agree wholeheartedly that the facility is there already for respected contributors to feed back comments that are handled well by the development team within the JT software development ranks.
The issue will be the “wombats” (as we term them here in Australia) that suddenly see more signals that they cannot decode – the “wombats” that are not up to date or have had systems set up by other Amateurs. Yes I can foresee a period of chaos as I see that many are also expressing concerns about. We are ALL on these forums going to have to be VERY TOLERANT with regards to posts on these forums too ... There is going to be a lot of repetition (and there is already). Tolerance. Think abot what and how you respond, if you respond. No “you are a wombat” postings ... These are not good for progressing AR... The Github and Sourceforge processes are more than adequate for regular contributors and direct communication/attention of the Development team. Yet there are the vast majority that do not contribute or are not on these lists. It is now time for ALL of us here to openly start talking with others about changes and promoting change and upgrades. This means adjustments to our web pages / QRZ.COM etc. Pages, talks at our clubs, comments on radio nets that we participate in. It also requires any of us that have ever assisted other Amateurs with the JT software to have “how are you going” discussions with other Amateurs and advising them that a significant change is on the way. Many Amateurs have environs that just work and will be resistant to change. This is the hardest type of Amateur to convince that change is necessary. HAM – Help All Mankind. Amateur Radio being for People and about People in a technical, regulated environment. People. We need to work heavily and promote - leaving these priority channels here clean for serious issues that will arise. Note that we have not seen the so-called Windows 1809 (and its successor) rolled out en-masse yet ! Egad ! 73 Steve I VK3VM / VK3SIR Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: Brian Moran <[email protected]> Sent: Saturday, November 24, 2018 5:37:44 AM To: WSJT software development Subject: [wsjt-devel] State of the Art Weak Signal Modes vs. State of the Art Issue Tracking WSJT-X represents current state of the art for weak signals in Amateur Radio communications, but using 'email as a bug database' to keep track of issues decidedly does NOT represent the state of the art in anything. Asking everyone to read all of the emails to see if their issue is represented before sending their own email has repeatedly been shown to not work. There are plenty of tools<https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems> (e.g. JIRA, Github Issues<https://guides.github.com/features/issues/>, even the one built into Sourceforge<https://sourceforge.net/p/forge/documentation/Tickets/>) that can keep track of a project's list of known issues, priorities, progress towards fixing, etc. and I'd expect the WSJT-X developers must already use something like that. Why that facility is not exposed for at least read access by the hoi polloi is known only to them. If everyone were able to see the list of issues, then it would even be a matter of just replying to the Nth "hey, I get an SSL library issue on startup" message with the URL of the issue. It might even expand the population of people able to contribute to the project in a positive way<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=690b0543a813b0ecfc51b0374c0ce6c8275435f0>. It might help offload this type of 'support' task from the developers. Some issue trackers even prompt the bug reporter to look through the open and resolved issues before filing their issue. The popular tools might require logging into a tool's website, but I would expect that anyone that can configure WSJT-X for Fox-Hound operation on a non-standard frequency should also be able to figure out how to file an issue in a bug tracker. I truly believe that using modern, purpose-built tools for issue tracking tasks would benefit everyone. Are there reasons why we are not doing so? Brian N9ADG
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
