An extension "Need Support" in gui would be great.

[AndreasLMeg]

An extension "Need Support" in gui would be great.

Why ?

• Many users have no Linux knowledge
• allsky installations are increasing - this also increases the support effort

How can they be helped?
HTML page: Need Support

• Text field: Description of the problem -> description.txt, allsky.log, config.sh, settings, Raspi Info, ... -> support.zip
• Selection: problem with timelapse, selection day -> ls -la from the daily directory, mpeg -> support.zip
• Selection: problem with keogram, selection day -> ls -la from daily directory, keogram.jpg -> support.zip
• Selection: problem with startrail, selection day -> ls -la from the daily directory, startrail.jpg -> support.zip
• Button for file selection -> support.zip

Save support.zip (PC)

The user can provide this file with a request (issue).
Caution data protection / security !!! do not zip files with access data

[EricClaeys]

@AndreasLMeg,
Just so I understand, you're suggesting having a "Need Support" link on the WebUI page that would prompt the user for various things. It would save the description in a file and would prompt the user for a selection of common issues (e.g., timelapse, keogram,...) and would gather information on the selected item (your "ls -la). The web page would save all that information to "support.zip".

Is that basically what you're suggesting?
I like that idea.

I'd want to treat questions differently from problems/Issues. I'm trying to limit the Issues list to problems we need to fix, and use the Projects link for enhancements and the Discussions for questions. At least for now. If we get to the point where we don't have many bugs or enhancement requests then using Issues for everything would probably be ok.

The only "private" information I can think of is latitude, longitude, ftp username, ftp password, and ftp host. Can you think of anything else?

[AndreasLMeg]

@EricClaeys,
yes, that is my idea / wish. Experience shows that most problems can be seen and / or solved with allsky.log. (But not all have access to this file or cannot load it onto the PC)
Therefore no bug report should be made without allsky.log.

FAQ or a link to the wiki page would also be a good introduction to the bug report.

Yes, latitude, longitude is privat, but it's your own fault if you give the GPS coordinates of your open front door!
I hope everyone just gives their hometown coordinates - that should be accurate enough.

ftp access data are really security-relevant.

[AndreasLMeg]

git status and git diff will also give some answers in case of problems

[AndreasLMeg]

At github there is the possibility of templates. To avoid bug reports, a description and instructions can be made here.
e.g. https://github.com/raspberrypi/firmware/tree/master/.github/ISSUE_TEMPLATE

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
https://github.com/thomasjacquin/allsky/community