aboutsummaryrefslogtreecommitdiffstats
path: root/doc/bugs.bb
diff options
context:
space:
mode:
authorAndrew Manning <tamanning@zoho.com>2018-06-08 05:37:23 -0400
committerAndrew Manning <tamanning@zoho.com>2018-06-08 05:37:23 -0400
commit4feff1cf897918892e6555b431f0d069031a8597 (patch)
tree5684eddda15fd014cfda4d1737108191a8576cfc /doc/bugs.bb
parentdf2d18160212ec546ec640dd1d2152fecada5557 (diff)
downloadvolse-hubzilla-4feff1cf897918892e6555b431f0d069031a8597.tar.gz
volse-hubzilla-4feff1cf897918892e6555b431f0d069031a8597.tar.bz2
volse-hubzilla-4feff1cf897918892e6555b431f0d069031a8597.zip
Update github.com git repo URLs with framagit.org URLs
Diffstat (limited to 'doc/bugs.bb')
-rw-r--r--doc/bugs.bb2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs.bb b/doc/bugs.bb
index cc1ea3a20..f6e14b659 100644
--- a/doc/bugs.bb
+++ b/doc/bugs.bb
@@ -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://github.com/redmatrix/hubzilla/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 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.
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.