From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 375] Finding new project members who can help with complex detailed work such as LDSTCompUnit
Date: Fri, 12 Jun 2020 14:16:06 +0000
Message-ID: <bug-375-13-fKBrcy4C7n@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-375-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=375
--- Comment #2 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #1)
> (In reply to Cole Poirier from comment #0)
> > I think it would very helpful if we had more project members who can help
> > work on the really complex pieces of the HDL,
>
> yes. right now i am basically left doing absolutely everything, which is not
> to say that everyone else's contributions are not valuable, it's just that
> they're between 10 to 100 times less productive.
Fair enough, you have been optimizing your productivity for the past 25 years.
What's less fair is you not having enough time to do everything, so I'll make a
concerted effort starting today to try to find you more help.
> >I am willing to try and recruit more people. Do you think this is a good idea?
>
> if we want to hit the target, then yes.
>
> > If so, do you have
> > any suggestions as to how I should go about this?
>
> mailing lists, talk to people. there's funding available.
Ok, this gives me some good ideas. I'll write up a little blurb derived from
some of your past mails to other developer mailing lists. Then I'll try and
find hdl mailing lists, probably reaching out to university computer
science/electrical engineering graduate/undergraduate registrars? If anyone
else has ideas for mailing lists I should target of seek out that would be very
helpful.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 23:40 [libre-riscv-dev] [Bug 375] New: " bugzilla-daemon
2020-06-12 10:42 ` [libre-riscv-dev] [Bug 375] " bugzilla-daemon
2020-06-12 14:16 ` bugzilla-daemon [this message]
2020-06-14 19:35 ` bugzilla-daemon
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=bug-375-13-fKBrcy4C7n@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/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