[libre-riscv-dev] [Bug 180] New: Decide how to spell Libre-SOC
Jacob Lifshay
programmerjake at gmail.com
Sun Feb 16 08:28:16 GMT 2020
CCing the mailing list so others can see your spelling preference.
On Sat, Feb 15, 2020 at 11:58 PM Michael Pham <pham.michael.98 at gmail.com>
wrote:
>
> Hi Jacob,
> Long time no see! Sorry I didn't respond earlier, I've been crazy busy
> with school. If it's not too late, I prefer LibreSOC.
Yeah, school can be a *lot* of work.
Are you ok with using Libre-SOC? Nearly everyone else either is leaving it
up to the rest of us to decide or prefers Libre-SOC with the hyphen.
> Also how are things going with the project? I haven't been paying too
> much close attention to the mailing lists (only quickly skimming some
> emails here and there) because my course work is killing me so I'm
> trying to minimize distractions. Any news of what happened to the
> OpenCL proposal and the LibreSOC version of the Raspberry Pi?
Last I heard, the OpenCL proposal was withdrawn:
https://libre-riscv.org/nlnet_proposals/
I don't recall what happened with the plans for a RPi-like computer based
around Libre-SOC, but it sounds like a good idea that we'd probably need
anyway for testing purposes once we have the ASIC built.
>
> Michael Pham
>
> On Fri, Feb 14, 2020 at 4:30 PM Jacob Lifshay <programmerjake at gmail.com>
wrote:
> >
> > Making sure everyone sees this
> >
> > On Fri, Feb 14, 2020, 13:19 <bugzilla-daemon at libre-riscv.org> wrote:
> >>
> >> http://bugs.libre-riscv.org/show_bug.cgi?id=180
> >>
> >> Bug ID: 180
> >> Summary: Decide how to spell Libre-SOC
> >> Product: Libre Shakti M-Class
> >> Version: unspecified
> >> Hardware: Other
> >> OS: Other
> >> Status: CONFIRMED
> >> Severity: enhancement
> >> Priority: ---
> >> Component: Specification
> >> Assignee: lkcl at lkcl.net
> >> Reporter: programmerjake at gmail.com
> >> CC: libre-riscv-dev at lists.libre-riscv.org
> >> Deadline: 2020-02-26
> >> NLnet milestone: ---
> >>
> >> We need to make a decision if we are going with Libre-SOC, LibreSOC, or
> >> something else. In order to have a central location to keep track of
everyone's
> >> opinions, I figured we can have a check list of people in the top
comment here.
> >>
> >> If you can't edit the top comment, post a comment asking someone (Luke
and me
> >> can, idk about everyone else) to edit it for you.
> >>
> >> Remember that we operate on unanimous decision making, so, having a
majority
> >> doesn't automatically mean that option wins.
> >>
> >> Previous discussion:
> >> http://bugs.libre-riscv.org/show_bug.cgi?id=179#c4
> >>
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-February/003701.html
> >>
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-January/003564.html
> >>
> >> Not yet entered (names from mailing list discussion):
> >>
> >> * Cole Poirier <colepoirier at gmail.com>
> >> * Hendrik Boom <hendrik at topoi.pooq.com>
> >> * Immanuel, Yehowshua U <yimmanuel3 at gatech.edu>
> >> * Luke Kenneth Casson Leighton <lkcl at lkcl.net>
> >> * Michael Nolan <mtnolan2640 at gmail.com>
> >> * Michael Pham <pham.michael.98 at gmail.com>
> >> * yg <whygee at f-cpu.org>
> >>
> >> Libre-SOC:
> >>
> >> * Jacob Lifshay <programmerjake at gmail.com>
> >> * add your name here
> >>
> >> LibreSOC:
> >>
> >> * Jacob Lifshay <programmerjake at gmail.com> (prefer Libre-SOC)
> >> * add your name here
> >>
> >> Leaving it to everyone else to decide:
> >>
> >> * add your name here
> >>
> >> <add other options here>
> >>
> >> --
> >> You are receiving this mail because:
> >> You are on the CC list for the bug.
> >> _______________________________________________
> >> libre-riscv-dev mailing list
> >> libre-riscv-dev at lists.libre-riscv.org
> >> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
More information about the libre-riscv-dev
mailing list