(no commit message)

[libreriscv.git] / index.mdwn

diff --git a/index.mdwn b/index.mdwn
index 47540247827b9961f37f6e86d1783429469e14c7..d304b08da82d45551013310b4b37cb9c6dc1fdd7 100644 (file)
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,52 +1,53 @@
-# Welcome to Libre-SoC!
+# Welcome to LibreSoC

 
 

-The Libre-SoC project is an effort to develop an completely 
-SOC 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 gpu. And an AI accelerator...

 
 

-This is a publicly editable wiki.
-
-All wikis are supposed to have a [[SandBox]], so this one does too.
+> Oh and here, have the source code...

 
 

-This wiki is powered by [[ikiwiki]].
+Sounds cool? Learn more [here](who_we_are)

 
 

-This is the sitemap: [[sitemap]]
+# Our Team

 
 

-----
+We are proud of our talented and diverse [team](current_members).

 
 

-# Joining/Onboarding Process
+# How Can I Help?

 
 

-This process probably needs some improvement, but 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]].
 
 [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.
 
 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.
 
 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
+6. 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]]
 you would like to contribute to, add yourself to the [[current_members]]

-page and fill in some information about yourself.
+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.

 
 ## Needed Skills
 
 Most labor is currently being applied to developing the GPU portion of
 
 ## Needed Skills
 
 Most labor is currently being applied to developing the GPU portion of

-the LibreSOC.
+the Libre-SoC.

 
 The highest priority needed at the moment is a c++ engineer to work on
 
 The highest priority needed at the moment is a c++ engineer to work on

-a MESA 3D driver. This will begin life as similar to SwiftShader however
-retaining the vectorisation and predication intrinsics.
+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)

 
 Medium to long-term we need HDL engineers. Particularly those familiar
 with nMigen or just python.  Most of the techniques being used require
 
 Medium to long-term we need HDL engineers. Particularly those familiar
 with nMigen or just python.  Most of the techniques being used require


@@ -63,14 +64,14 @@ bugtracker).
 
 # Resources
 
 
 # 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]]
+| Resource | Link |
+| --- | --- |
+| Bugs and Tasks | <http://bugs.libre-riscv.org/> |
+| Mailing Lists | <http://lists.libre-riscv.org> |
+| Archives | <http://lists.libre-riscv.org/pipermail> |
+| Git repositories | <http://git.libre-riscv.org> |
+| Kazan (Vulkan driver) | <https://salsa.debian.org/Kazan-team/kazan> |
+| Further Information | [[resources]] |

 
 # Main Pages
 
 
 # Main Pages
 


@@ -91,6 +92,12 @@ bugtracker).
 
 [1]: https://libre-riscv.org/3d_gpu/spike_sv/
 
 
 [1]: https://libre-riscv.org/3d_gpu/spike_sv/
 

-# Current Members
+# Wiki Structure

 
 

-[[current_members]]
+This is a publicly editable wiki.
+
+All wikis are supposed to have a [[SandBox]], so this one does too.
+
+This wiki is powered by [[ikiwiki]].
+
+This is the sitemap: [[sitemap]]