From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: sanjayamenon.mec@gmail.com
Subject: Re: [libre-riscv-dev] Contributing to the Libre-Soc Project
Date: Sun, 7 Jun 2020 00:13:02 +0100
Message-ID: <CAPweEDzP_ORjf5x7pmFN_GShYHhDN4NHUqX+=B4TiWNZeBKaSA@mail.gmail.com> (raw)
In-Reply-To: <CAE_rhwZK4FeFHDh4SNiUozji1vR1L4Xm=+BVBRuxHMw49CsMhQ@mail.gmail.com>
(hi everyone please do cc sanjay as i've just manually approved this
message and he is not yet subscribed to the list, so would not see
replies unless explicitly cc'd. sanjay, do subscribe to the list via
the interface at
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev)
On Sat, Jun 6, 2020 at 11:47 PM Sanjay Menon <sanjayamenon.mec@gmail.com> wrote:
>
> Hi,
>
> I am a budding VLSI enthusiast and open-source developer. I would love to
> work with the team in your goal to achieve a completely open source project.
good to hear from you.
one key thing to appreciate: this is a libre project, not an "open
source" one. the distinction is not immediately apparent or
well-known to people, and it comes down to this: a Libre project says
"no" when it comes to unethical practices, whereas an "open" one makes
no such declaration. "open source" projects *might* have people
contributing to it with the very best of intentions, however none of
them will have *actively* declared not to cross an ethical line.
> I believe that as a beginner in this area, I would be able to learn more
> from you guys as I contribute to this wonderful project.
well, one thing i love telling people the story is of how Cole Poirier
has gone from zero hardware knowledge to writing his own nmigen
modules. so there is room for everyone with all levels of experience.
> I thank Yehowshua Immanuel for introducing me to this project. Can't wait
> to start already. Hoping to hear from you soon.
so, congratulations on the first step - getting in touch (*tick*) :)
just go through the list on the "how can i help as a developer", in
your own time - https://libre-soc.org/
in particular you'll find the development workflow advice here:
https://libre-soc.org/HDL_workflow/
this is a combined page of best practices for collaboration, as well
as containing developer-style "getting started" instructions.
> To know more about me do checkout my LinkedIn
> <http://www.linkedin.com/in/sanjay-menon-91791815a> profile.
nice, i see you've done actual VLSI layout - we're using coriolis2,
this involves actually writing the layout *entirely as a python
program*:
https://bugs.libre-soc.org/buglist.cgi?quicksearch=coriolis2&list_id=826
if you'd like to do that, you're more than welcome (and can receive
donations from NLNet for doing so). there's plenty of other tasks as
well.
you have some cool projects on there, including implementing SHA256 in
hardware: did you do that at gate-level or in an HDL?
best,
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
prev parent reply index
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 22:29 Sanjay Menon
2020-06-06 23:03 ` Yehowshua
2020-06-06 23:15 ` [libre-riscv-dev] FHDLTestCase Luke Kenneth Casson Leighton
2020-06-06 23:22 ` Yehowshua
2020-06-06 23:27 ` Yehowshua
2020-06-06 23:45 ` Luke Kenneth Casson Leighton
2020-06-06 23:34 ` Luke Kenneth Casson Leighton
2020-06-06 23:45 ` Yehowshua
2020-06-06 23:49 ` Luke Kenneth Casson Leighton
2020-06-06 23:13 ` Luke Kenneth Casson Leighton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDzP_ORjf5x7pmFN_GShYHhDN4NHUqX+=B4TiWNZeBKaSA@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=sanjayamenon.mec@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git