Start here — where to ask, and what to expect #2346
laurentiu021 Admin
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
One thing to say first, because it is the first thing you will notice. Almost every discussion in this repository is an automated release announcement. Those are posted by the release workflow, not by a person, and they only cover feature releases — patch releases stopped getting one because a post per patch buried everything a human wrote. So the wall of "SysManager X.Y.Z released" is a robot, not a crowd, and Q&A being empty means your question will be the first one rather than the hundredth.
Where to ask
SUPPORT.md is the same table plus more detail, and it is the version kept up to date.
You do not need to be technical to report something
If a tab looked wrong, said something confusing, or did nothing when you clicked, that is worth reporting exactly as you experienced it. "The cleanup tab said it freed 4 GB but my disk looks the same" is a good report. You do not have to work out why.
Two things make a bug report land much faster, and both take a few seconds:
%LOCALAPPDATA%\SysManager\logs\, one file per day. Attach the one from around when it happened. Your Windows user name is scrubbed out of them before they are written.What to expect
This is one person's hobby project, so honestly rather than aspirationally: bug reports get a first look within a few days, and a reproducible one with logs usually gets a fix or a workaround within a week. Feature requests are all read and a fraction are implemented — the more specific the request, the better its odds. Questions belong here rather than in issues, because issues are for trackable work.
Two things people hit before the app even starts
All reactions