-# Welcome to Libre-SoC ([provisionally renamed](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-January/003580.html) from Libre-RISCV)!
+# Welcome to Libre-SOC
+(formerly Libre-RISCV)
-The Libre-SoC project is an effort to develop a complete modern capability
-SoC (quad core, 800mhz, dual issue,
-GPU, VPU) that is libre to the bedrock.
+> We're building a chip. A fast chip. A safe chip. A trusted chip.
-Libre has a very specific meaning and guarantees, where "open" does not.
-See <https://www.gnu.org/philosophy/open-source-misses-the-point.html>
-for an explanation of the distinction, and for additional examples:
-<https://wiki.opensourceecology.org/wiki/Fake_Open_Source>
+> A chip with lots of peripherals. And a VPU. And a 3D GPU...
-This is a publicly editable wiki.
+> Oh and here, have the source code...
-All wikis are supposed to have a [[SandBox]], so this one does too.
+Sounds cool? Learn more about the [why](why_a_libresoc) behind Libre-SOC
+and [our mission](The_Mission).
-This wiki is powered by [[ikiwiki]].
+# Our Team
-This is the sitemap: [[sitemap]]
+We are proud of our talented and diverse [team](about_us).
-----
+# How Can I Help?
-# Contact
+If you would like to fund us, see [[funding]]. We currently have some
+funding and always appreciate more! If you are a Corporation or an
+individual you can donate tax-free to NLNet, and they can in turn gift
+our developers. Contact lkcl@lkcl.net for more information.
-The main contact point is the
-[mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev).
-If you need to contact the sysadmin please use webmaster@libre-riscv.org
+If you want to write code with us, keep reading. If you want to *learn* so that you can write code with us, see below.
-# Joining/Onboarding Process
-
-This process probably needs some improvement: the basic
-idea is to join the
+1. First, join the
[mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev),
introduce yourself, and read through
[recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
and the [[charter]].
-
-The next thing you should do is read through the [bugs
+2. The next thing you should do is read through the [bugs
list](http://bugs.libre-riscv.org) and see if there are any bugs that
pique your interest.
-
-We do have funding available (see [[nlnet]]) upon completion of issues -
+3. After that, go ahead and take a look at the resources section below.
+Try and clone a repository with
+``git clone https://git.libre-riscv.org/git/repositoryname.git``
+4. If you plan to do HDL work, you should familiarize yourself with our
+ [[HDL_workflow]].
+5. We do have funding available (see [[nlnet]]) upon completion of issues -
we are also working on procuring more funding which gets the project to
nanometre scale tapeout.
-
-After all this, if you feel that Libre-SoC is a good cause that
-you would like to contribute to, add yourself to the [[current_members]]
+6. After all this, if you feel that Libre-SOC is a something that
+you would like to contribute to, add yourself to the [current_members](about_us)
page, fill in some information about yourself, and join the mailing list
and say hello.
+Also note that you can edit this wiki. See the last section of this page.
+
+## How can I learn?
+
+The whole purpose of this project is to be a learning environment as well as an actual business. If you want to learn how to do ASIC design, with a view to contributing or starting your own ASIC business, start here: [[3d_gpu/tutorial]]. Yes, really: do not let anyone tell you that you can't learn this stuff too.
+
+Along the way, if you find any resources or links that you found particularly helpful, please add them to that page so that other people can also benefit.
+
## Needed Skills
Most labor is currently being applied to developing the GPU portion of
-the Libre-SoC.
+the Libre-SOC.
The highest priority needed at the moment is a c++ engineer to work on
a MESA 3D driver. This will begin life similar to SwiftShader however
-retaining the vectorisation and predication intrinsics as well as hardware accelerated opcodes (all of which SwiftShader lacks)
+retaining the vectorisation and predication intrinsics as well as hardware
+accelerated opcodes (all of which SwiftShader lacks)
Medium to long-term we need HDL engineers. Particularly those familiar
with nMigen or just python. Most of the techniques being used require
Also, individuals with experience in formal mathematical verification
are quite welcome.
-TODO: add a list of upcoming project tasks/milestones (link to
-bugtracker).
-
-# Resources
-
-* Mailing Lists <http://lists.libre-riscv.org> -
- Archives at <http://lists.libre-riscv.org/pipermail>
-* Git repositories <http://git.libre-riscv.org>
- may be cloned publicly with
- git clone https://git.libre-riscv.org/git/repositoryname.git
-* Bugzilla at <http://bugs.libre-riscv.org/>
-* Kazan (Vulkan driver) at <https://salsa.debian.org/Kazan-team/kazan>
-* Further Information [[resources]]
-
-# Main Pages
-
-* Libre-SoC [[charter]]
-* [[shakti/m_class]]
-* [[alt_rvp]]
-* [[3d_gpu]]
-* [[vpu]]
-* [[simple_v_extension]]
-* [[zfpacc_proposal]]
-* [[ztrans_proposal]]
-* [[simple_v_extension/specification/mv.x]]
-* [[simple_v_extension/specification/ld.x]]
-* Specifications and [[resources]]
-
-# Spike Emulator
-* [Set-Up Instructions][1]
-
-[1]: https://libre-riscv.org/3d_gpu/spike_sv/
+List of upcoming project tasks/milestones:
-# Current Members
+* [Upcoming tasks][1]
+* [NLNet Milestones][2]
-[[current_members]]
+[1]: http://bugs.libre-riscv.org/describecomponents.cgi?product=Libre%20Shakti%20M-Class
+[2]: http://bugs.libre-riscv.org/describecomponents.cgi?product=Libre%20Shakti%20M-Class