doc: remove links to wiki

Wiki is being obsoleted, so remove any links that might become dead
really soon.

Signed-off-by: Anas Nashif <[email protected]>

Author: nashif

boards/boards.rst

@@ -3,6 +3,8 @@
 Supported Boards
 ################
 
+To add support documentation for a new board, please use the template available
+under :file:`doc/templates/board.tmpl`
 
 X86 Boards
 **********
@@ -48,11 +50,3 @@ XTENSA Boards
    :glob:
 
    xtensa/**/*
-
-A list of additional supported boards can be found on the `Zephyr project wiki`_.
-
-To add a new board, please use the template available under
-:file:`doc/templates/board.tmpl`
-
-
-.. _Zephyr project wiki: https://wiki.zephyrproject.org/view/Supported_Boards

doc/README.rst

@@ -41,8 +41,6 @@ The project's documentation currently comprises the following items:
 * Script-generated material for kernel configuration options based on kconfig
   files found in the source code tree
 
-* Additional material on https://wiki.zephyrproject.org
-
 The reStructuredText files are processed by the Sphinx documentation system,
 and make use of the breathe extension for including the doxygen-generated API
 material.  Additional tools are required to generate the

doc/application/application.rst

@@ -502,7 +502,8 @@ depth is needed. The developer must supply a :file:`Makefile` for the
 Application-specific source code should not use symbol name prefixes that have
 been reserved by the kernel for its own use. For more information, see
 
-`Naming Conventions <https://wiki.zephyrproject.org/view/Coding_conventions#Naming_Conventions>`_.
+`Naming Conventions
+<https://github.com/zephyrproject-rtos/zephyr/wiki/Naming-Conventions>`_.
 
 
 The following requirements apply to all Makefiles in the :file:`src`

doc/contribute/code.rst

@@ -8,7 +8,7 @@ licenses, the naming conventions, the code submission infrastructure, the
 review process and the code documentation can be found on the
 Zephyr Project wiki.
 
-* https://wiki.zephyrproject.org/view/Collaboration_Guidelines
+* https://github.com/zephyrproject-rtos/zephyr/wiki/Contribution-Guide
 
 .. toctree::
    :maxdepth: 1

doc/drivers/drivers.rst

@@ -149,7 +149,7 @@ failures, etc., should be handled by assertions.
 
 When it is appropriate to return error conditions for the caller to check, 0
 should be returned on success and a POSIX errno.h code returned on failure.
-See https://wiki.zephyrproject.org/view/Coding_conventions#Return_Codes for
+See https://github.com/zephyrproject-rtos/zephyr/wiki/Naming-Conventions#return-codes for
 details about this.
 
 A driver implementing a particular subsystem will define the real implementation

doc/index.rst

@@ -44,7 +44,6 @@ Sections
    LICENSING.rst
    glossary.rst
 
-You can find further information on the `Zephyr Project Wiki`_.
 
 Indices and Tables
 ******************
@@ -53,7 +52,6 @@ Indices and Tables
 
 * :ref:`search`
 
-.. _Zephyr Project Wiki: https://wiki.zephyrproject.org/view/Main_Page
 .. _Zephyr 1.7.0: https://www.zephyrproject.org/doc/1.7.0/
 .. _Zephyr 1.6.0: https://www.zephyrproject.org/doc/1.6.0/
 .. _Zephyr 1.5.0: https://www.zephyrproject.org/doc/1.5.0/