- Clean up home page with only technical topics
  - Move of obsolete wiki pages to an archives folder
  - Incorporating Continuous Integration wiki pages
  - Incorporating newer versions on Guidelines and Policies

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

home.md

-# Welcome to the OpenAirInterface project
+<table style="border-collapse: collapse; border: none;">
+  <tr style="border-collapse: collapse; border: none;">
+    <td style="border-collapse: collapse; border: none;">
+      <a href="http://www.openairinterface.org/">
+         <img src="./images/oai_final_logo.png" alt="" border=3 height=50 width=150>
+         </img>
+      </a>
+    </td>
+    <td style="border-collapse: collapse; border: none; vertical-align: center;">
+      <b><font size = "5">Welcome to the OpenAirInterface project</font></b>
+    </td>
+  </tr>
+</table>
 
-EURECOM has created the _OpenAirInterface (OAI) Software Alliance (OSA)_, a
-separate legal entity from EURECOM, which aims to provide an open-source
-ecosystem for the core (EPC) and access-network (EUTRAN) protocols of 3GPP
-cellular systems with the possibility of interoperating with closed-source
-equipment in either portion of the network. In addition to the huge economic
-success of the open-source model, the Alliance will be a tremendous tool used
-by both industry and academia. More importantly it will ensure a much-needed
-communication mechanism between the two in order to bring academia closer to
-complex real-world systems which are controlled by major industrial players
-in the wireless industry. In the context of the evolutionary path towards 5G,
-there is clearly the need for open-source tools to ensure a common R&D and
-prototyping framework for rapid proof-of-concept designs.
+For general information on the Alliance, please access our official site at [http://www.openairinterface.org](http://www.openairinterface.org).
 
-The OSA's EPC software is known and _openairCN_ while the access-network
-software goes under the name of _openair5G_. OAI currently includes a
-standard-compliant implementation of a subset of Release 10 LTE for UE, eNB,
-MME, HSS, SGw and PGw on standard Linux-based computing equipment (Intel x86
-PC/ARM architectures). Openair5G is freely distributed by the OSA under the
-terms stipulated by a new open-source license catering to the intellectual
-property agreements used in 3GPP which allows contributions from 3GPP members
-holding patents on key procedures used in the standard. OpenairCN is
-distributed under an Apache V2.0 license, in order to ease with integration
-within an OpenStack environment. The team is working closely with ETSI to
-harmonize the software license with the intellectual property policy of 3GPP.
-The software can be used in conjunction with standard RF laboratory equipment
-available in many labs (i.e. National Instruments/Ettus USRP and PXIe
-platforms), in addition to custom RF hardware provided by EURECOM, to
-implement these functions to a sufficient degree to allow for real-time
-interoperation with commercial devices. Some industrial users have reported
-integration with commercial RF remote radio-head equipment.
+These wiki pages are for the RAN component of the OpenAirInterface project.
 
-The current major industrial users of OAI for collaborative projects are
-Alcatel-Lucent, China Mobile, TCL, Thales, National Instruments, Orange,
-Intel, TCS, Canonical, Ercom, Keysight, Telekom Malaysia, Telecom Italia,
-Swisscom, ARELIS (Thomson Broadcast). Leading research centers using and
-contributing to the software development include B-COM, Fraunhofer IIS,
-Frauhofer FOKUS, IMST, TNO, Winlab, Idaho National Laboratory, III, ITRI,
-INDT, Fundacion Sadosky and many top university labs worldwide.
+For details on the EPC component, please access the EPC GitHub Wiki at [https://github.com/OPENAIRINTERFACE/openair-cn/wiki](https://github.com/OPENAIRINTERFACE/openair-cn/wiki).
 
-You can also take a look at our official website: http://www.openairinterface.org
+# When starting: #
 
 * [OpenAirInterface Software Installation Support (START HERE)](OpenAirSoftwareSupport)
 * [Frequently Asked Questions (FAQ)](FAQ)
-* [How to ask questions on the mailing lists](AskQuestions) <- ```PLEASE READ BEFORE POSTING ON MAILING LIST```
-* [Alliance Projects Proposal for openairinterface5g](AllianceProjectsProposal)
-* [Use cases of OpenAirInterface](OpenAirUseCases)
+* [Mailing Lists](MailingList)
+* [How to ask questions on the mailing lists](AskQuestions) <- **PLEASE READ BEFORE POSTING ON MAILING LIST**
 * [Tutorials (Usage of OpenAirInterface)](OpenAirUsage)
 * [Features of OpenAirInterface](OpenAirFeatures)
-* [News & Events](OpenAirEvents)
-* [Releases and Changelogs](OpenAirReleases)
-* [Roadmaps, and how to contribute](OpenAirRoadmaps)
-* [Additional Documentation](OpenAirDocumentation)
-* [OAI Developer Calls (Meeting minutes)](MeetingMinutes)
-* [GitLab Workflow](GitLabWorkFlow)
-* [Mailing Lists](MailingList)
+* [Roadmaps](OpenAirRoadmaps)
+* [Contribution Policies, Guidelines and Workflow](oai-policies-home)
+* [OAI Developer Calls](OpenAirDevMeetings)
+* [5G NR development and releases](5g-nr-development-and-releases)
+
+# When testing: #
+
 * [Networks and UEs](NetworksUEs)
 * [OAI Test Setup@EURECOM](OAITestSetup)
 * Eurecom Internal 
     1. [Radio and Computing Equipment Information](EurecomEquipmentStatus)
-    1. [SIM Cards info](SIMInfo)
+    2. [SIM Cards info](SIMInfo)
 * [The T tracer](T)
 * [The configuration module](config)
 * [The shared library loader](loader)
 * [The embedded telnet server](telnetsrv)
-* [How to edit the wiki](WikiUsage)
-* [OpNFV Functest Pre-study](opnfv-functest)
-* [M-CORD Pre-study](m-cord-oai)
-* [5G NR development and releases](5g-nr-development-and-releases)
+* [Continuous Integration](ci/continuous-integration-home)
 
-Some old unformatted pages from the old twiki are listed [here](TODO).
+# Administration #
 
-# Outdated Pages
-* [Projects](OpenAirProjects)
-* [Critical Issue/Bug List](OpenAirCriticalIssues)
-* [GoogleSummerOfCode](GoogleSummerOfCode)
+* [How to edit the wiki](WikiUsage)
+* [Technical Committee](policy/project-roles)