aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMario <mario@mariovavti.com>2019-03-04 09:50:12 +0100
committerMario <mario@mariovavti.com>2019-03-04 09:50:12 +0100
commite074d02714db4722384431e68bb8c26d3b3caf99 (patch)
tree745159b3c443a350eb4c2ed8156d8626a1a08a30
parent7dc3835a54cbbf418f0b446b0464b8e37a4da485 (diff)
parente26de9c1d11dc8175ea520be091f0437d99ea5e0 (diff)
downloadvolse-hubzilla-e074d02714db4722384431e68bb8c26d3b3caf99.tar.gz
volse-hubzilla-e074d02714db4722384431e68bb8c26d3b3caf99.tar.bz2
volse-hubzilla-e074d02714db4722384431e68bb8c26d3b3caf99.zip
Merge branch 'dev' into 'dev'
Addressing new 'support@zotadel.net' support forum instead of old 'support@gravizot.de' See merge request hubzilla/core!1539
-rw-r--r--doc/bugs.bb4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/bugs.bb b/doc/bugs.bb
index f773da025..3bf2a0e29 100644
--- a/doc/bugs.bb
+++ b/doc/bugs.bb
@@ -21,7 +21,7 @@ If you get a blank white screen when doing something, this is almost always a co
[h3]I'm stumped. I can't figure out what is wrong.[/h3]
-At this point it might be worthwhile discussing the issue on one of the online forums. There may be several of these and some may be more suited to your spoken language. At this time, the 'Hubzilla Support' channel (support@gravizot.de) is the recommended forum for discussing bugs.
+At this point it might be worthwhile discussing the issue on one of the online forums. There may be several of these and some may be more suited to your spoken language. At this time, the 'Hubzilla Support' channel (support@zotadel.net) is the recommended forum for discussing bugs.
If community members with software engineering training/expertise can't help you right away, understand that they are volunteers and may have a lot of other work and demands on their time. At this point you need to file a bug report. You will need an account on framagit.org to do this. So register, and then visit https://framagit.org/hubzilla/core/issues . Create an issue here and provide all the same information that you provided online. Don't leave out anything.
@@ -29,4 +29,4 @@ Then you wait. If it's a high profile issue, it may get fixed quickly. But nobod
Other people working to fix the problem may need to find out more, so do your homework and document what is happening and everything you've tried. Don't say "I did xyz and it didn't work." That doesn't tell us anything. Tell us precisely what steps you took and what you expected the result to be, and precisely what happened as a result. What page/URL were you looking at or what form were you filling in? If there were any error messages, don't say "there was an error message". Tell us exactly what the message said. Also tell us what hub you are using, what software version you're running and any other details that may be unique about your site configuration. It is understood that you might wish to keep some information and your connections private, however if you aren't willing to share the information other people need to reproduce/fix the problem, it may not get fixed.
- \ No newline at end of file
+