There is a Wiki entry <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> on the subject.
I think I was a little flippant when I wrote it. It overemphasizes the importance of including a log, but doesn't mention your other points. Perhaps you want to take a try at revising it? Regarding Google translate, if the user is really uncomfortable using English, I think I can speak for both Matthew and myself, that the user should post in his/her native language *without using idioms or colloquialisms*. Then *we* use Google translate. By starting a bit farther up in the language chain, it's easier to figure out what the user was trying to say. I've also noticed that Gary, the author of the tool wee_debug, has deemphasized its use. Perhaps because of the bug you uncovered? -tk On Wed, Oct 11, 2017 at 5:15 PM, Vince Skahan <vinceska...@gmail.com> wrote: > We're once again getting a 'lot' of questions, problem reports, and > perceived bug reports from new users who provide us: > > - skeletal at best problem descriptions > - with no log entries > - and no config file snippets > - unfortunately, frequently seemingly via google translate as well > > > Do we need a more formal 'how to report a bug' form and perhaps try to > enforce that approach a little more strongly and universally ? > > Gary (I think) wrote wee_debug a while back to obfuscate things enough to > permit providing much of the right information. Given that most folks > seem to be trying a reasonably current version of weewx, should/can we try > to enforce "no detailed debugging of questions without the user providing > at least a wee_debug output, and perhaps some logfiles" ? > > >
