For machines running Sparky, we can see but not post bugs at the Debian Bug Tracking System. When a problem comes up, and you have an idea what program is doing it, go there first and look for bug in the 900K plus numbers. Some day it will be in the 10 to the 6th. Nimbler minds and nimbler fingers might have already identified the bug and possibly some help. Also Sid-unstable is always at least 5 days prior for them to find the bugs.
https://www.debian.org/Bugs/
There is also an irc channel for testing- sid #debian-next. Again, lurk watch, , but if they ask for /etc/apt/.... repos, they will (usually) say nicely, "sorry, only support for Debian." Sparky has an irc for help. Myself, I was following some irc's back in Winnipeg MB days, but am way too busy these days.
The quickest things I would recommend learning is 1. how to cut and past from the terminal. 2. How to output machine info to post for help via the lovely program "inxi"
https://forum.sparkylinux.org/index.php/topic,4614.msg12231.html#msg12231
3. Use the "Sharp" button # to mark up machine output or data or code as code. It is in the row above the emoticons.
peace out.