aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorzotlabs <mike@macgirvin.com>2018-09-21 17:21:47 -0700
committerzotlabs <mike@macgirvin.com>2018-09-21 17:21:47 -0700
commit3b4a23c4a1341f537d4c1458e1e39c4bbf5686a5 (patch)
tree57b25e36d3618234e6fadf56654867e9fd229599 /doc
parentba49e6a5889ffbb91ce783a00334d2b6221c42b7 (diff)
downloadvolse-hubzilla-3b4a23c4a1341f537d4c1458e1e39c4bbf5686a5.tar.gz
volse-hubzilla-3b4a23c4a1341f537d4c1458e1e39c4bbf5686a5.tar.bz2
volse-hubzilla-3b4a23c4a1341f537d4c1458e1e39c4bbf5686a5.zip
doc cleanup
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs.bb4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/bugs.bb b/doc/bugs.bb
index f6e14b659..f773da025 100644
--- a/doc/bugs.bb
+++ b/doc/bugs.bb
@@ -1,5 +1,5 @@
[h2]Bugs, Issues, and things that go bump in the night...[/h2]
-[h3]Something went wrong! Who is charge of fixing it?[/h3]
+[h3]Something went wrong! Who is in charge of fixing it?[/h3]
[b]$Projectname Community Server[/b]
@@ -23,7 +23,7 @@ If you get a blank white screen when doing something, this is almost always a co
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.
-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 github.com 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.
+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.
Then you wait. If it's a high profile issue, it may get fixed quickly. But nobody is in charge of fixing bugs. If it lingers without resolution, please spend some more time investigating the problem. Ask about anything you don't understand related to the behaviour. You will learn more about how the software works and quite possibly figure out why it isn't working now. Ultimately it is somebody in the community who is going to fix this and you are a member of the community; and this is how the open source process works.