Docs: Updated URLs

AUTHORS

@@ -142,6 +142,7 @@ The following submitted code, packages or analysis, and deserve special thanks:
   Paul J. Fenwick
   Michael Neumann
   Mark Scannell
+  buhtz
 
 Thanks to the following, who submitted detailed bug reports and excellent
 suggestions:

DEVELOPER.md

@@ -18,7 +18,6 @@
                                          # Alternately 'export MAKEFLAGS=-j 4'
 ```
 ## Running Test Suite:
-
 ```
     $ cd tests
     $ make VERBOSE=1                     # Shows details
@@ -117,9 +116,10 @@
 
 ## Tests needed
 
-  * Take a look at the bug database (https://bug.tasktools.org) and notice that
+  * Take a look at the bug database (https://github.com/GothenburgBitFactory/taskwarrior/issues)
-    many issues, open and closed, have the "needsTest" label. These are things
+    and notice that many issues, open and closed, have the "needsTest" label.
-    that we would like to see in the test suite, as regression tests.
+    These are things that we would like to see in the test suite, as regression
+    tests.
 
   All new unit tests should follow the test/template.t standard.
 
@@ -153,5 +153,4 @@
   * Current development branch no plans yet.
 
 ---
-
 2018-05-13 Updated for 2.5.2

NEWS

@@ -54,6 +54,8 @@ Removed Features in 2.5.2
 
 Known Issues
 
+  - https://github.com/GothenburgBitFactory/taskwarrior
+
 Taskwarrior has been built and tested on the following configurations:
 
   * macOS
@@ -69,11 +71,11 @@ Taskwarrior has been built and tested on the following configurations:
 While Taskwarrior has undergone testing, bugs are sure to remain.  If you
 encounter a bug, please enter a new issue at:
 
-  https://bug.tasktools.org
+  https://github.com/GothenburgBitFactory/taskwarrior<Paste>
 
 Or just send a message to:
 
-  support@taskwarrior.org
+  support@GothenburgBitFactory.org
 
 Thank you.
 

README.md

@@ -33,11 +33,12 @@ For support options, take a look at:
 
 http://taskwarrior.org/support
 
-Please send your code patches to:
+Please use pull requests, or send your code patches to:
 
-support@taskwarrior.org
+support@GothenburgBitFactory.org
 
-Consider joining bug.tasktools.org and participating in the future of Taskwarrior.
+Visit https://github.com/GothenburgBitFactory/taskwarrior and participate in
+the future of Taskwarrior.
 
 ---
 

doc/man/task-color.5.in

@@ -321,7 +321,7 @@ The official site at
 
 .TP
 The official code repository at
-<https://git.tasktools.org/scm/tm/task.git>
+<https://github.com/GothenburgBitFactory/taskwarrior>
 
 .TP
 You can contact the project by writing an email to

doc/man/task-sync.5.in

@@ -173,11 +173,11 @@ The official site at
 
 .TP
 The official code repository at
-<https://git.tasktools.org/scm/tm/task.git>
+<https://github.com/GothenburgBitFactory/taskwarrior>
 
 .TP
 You can contact the project by writing an email to
-<support@taskwarrior.org>
+<support@gothenburgBitFactory.org>
 
 .SH REPORTING BUGS
 .TP

doc/man/task.1.in

@@ -1324,13 +1324,13 @@ The official site at
 
 .TP
 The official code repository at
-<https://git.tasktools.org/scm/tm/task.git>
+<https://github.com/GothenburgBitFactory/taskwarrior>
 
 .TP
 You can contact the project by emailing
-<support@taskwarrior.org>
+<support@GothenburgBitFactory.org>
 
 .SH REPORTING BUGS
 .TP
 Bugs in Taskwarrior may be reported to the issue-tracker at
-<https://bug.tasktools.org/>
+<https://github.com/GothenburgBitFactory/taskwarrior/issues>

doc/man/taskrc.5.in

@@ -1531,14 +1531,13 @@ The official site at
 
 .TP
 The official code repository at
-<https://git.tasktools.org/scm/tm/task.git>
+<https://github.com/GothenburgBitFactory/taskwarrior>
 
 .TP
 You can contact the project by emailing
-<support@taskwarrior.org>
+<support@GothenburgBitFactory.org>
 
 .SH REPORTING BUGS
 .TP
 Bugs in Taskwarrior may be reported to the issue-tracker at
-<https://bug.tasktools.org/>
+<https://github.com/GothenburgBitFactory/taskwarrior/issues>
-

test/README

@@ -91,8 +91,8 @@ If you wish to contribute tests, please consider the following guidelines:
     test script, such as filter.t, export.t, whichever is appropriate.
 
   * Tests created after bugs or feature requests should (ideally) have an entry
-    on https://bug.tasktools.org/ and should include the issue ID in a
+    on https://github.com/GothenburgBitFactory/taskwarrior/issues and should
-    docstring or comment.
+    include the issue ID in a docstring or comment.
 
   * Class and method names should be descriptive of what they are testing.
     Example: TestFilterOnReports