From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 379] New: Create wiki page for recruitment letter to Universities (& etc.) to point to
Date: Fri, 12 Jun 2020 16:09:10 +0000
Message-ID: <bug-379-13@https.bugs.libre-soc.org/> (raw)
https://bugs.libre-soc.org/show_bug.cgi?id=379
Bug ID: 379
Summary: Create wiki page for recruitment letter to
Universities (& etc.) to point to
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Conferences
Assignee: lkcl@lkcl.net
Reporter: colepoirier@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
Cole Poirier:
> > Will also work on a blurb for soliciting new members, and research some
> > possible methods of publicising our search for memebers.
lkcl:
> my partner marie has a contact at HK University, please do point her at it
> when you have it written. (a short wiki page is great).
Will do, thanks this is a great place to start. Also will be contacting U of T,
my sister is a 3rd year ECE student there. Planning on contacting as many CS
and ECE listservs as I can find. Is this permitted? Are there any procedures,
regulations, or recommendations when it comes to cold contacting mailing list
registrars with a request to share our letter informing students (and faculty?)
of the opportunity to "work on complex and interesting libre hardware/software
and receive tax deductible charitable donations for their contributions?"
After university engineering and computer science mailing lists, maybe I should
try tech and hardware forums? Perhaps both the professional and enthusiast tech
forums, because people like Jacob and I watch things like Gamer's Nexus on
youtube, so there may be others that we can find there?
> we have something on the front page already however it is embedded *in* the
> front page and so is not really clear.
I agree. I'll write something up and post it on the wiki, will post the link
here when its up.
> we also cannot call it "jobs" because sigh that implies salaries, per-hour
> payments, employment, that we will cover their insurance costs, holidays
> and so on. wark-wark.
Don't worry, I got on that same page... months ago? It's hard to forget when
it's been discussed so many times on list.
--
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 reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 16:09 bugzilla-daemon [this message]
2020-06-12 16:25 ` [libre-riscv-dev] [Bug 379] " bugzilla-daemon
2020-06-12 16:51 ` bugzilla-daemon
2020-06-12 16:56 ` bugzilla-daemon
2020-06-12 17:09 ` bugzilla-daemon
2020-06-12 17:09 ` 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-379-13@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