[libre-riscv-dev] RFC: Some Trivial Proposals

[Luke Kenneth Casson Leighton]

On Sunday, September 22, 2019, Michael Pham <pham.michael.98 at gmail.com>
wrote:

>
> the name of the project. Sometimes it is Libre RISC-V,


>
Correct.


>  or Libre-RISCV,


Wrong. See any, replace.


> or libre-riscv,


Website DNS name only.


>
> or libreriscv,


>
Wrong.  See any, replace.


> and probably more variations too. It is
> important to be consistent because
>
> * (1) it will consolidate our search engine results. In other words,
> when a user wants to know more about the project and searches "Libre
> RISC-V" in Google, the user will definitely get search results for
> "Libre RISC-V" but search results for the other variations such as
> "libre-riscv" might not show up in the same search. Same applies to
> the other variations.
>
> * (2) it will be easier for people to find us and refer to us in other
> places as well such as Phoronix or NLNet, reddit, emails, etc.
>
> * (3) it will be more professional at least agree on the name of the
> project.
>
> ## Drawbacks
> No significant drawbacks except for the fact that someone has to go
> edit all the names (maybe me).


Got git, and ssh, can use grep and sed or awk or mysqlclient "replace"
command. Send me ssh PUBLIC key.


>
> ## Alternatives
> We could also just ignore it. Like I said, it's a trivial proposal ;)


:)


>
> # Second proposal:
> Rename the Simple-V extension. Some more possible names I thought of
> are "Flexible Parallelism (abbr. as zflexpar)" or "Flexible
> Vectorization (abbr. as zflexvec)".


Yehhh more awkward, that.


>
> ## Motivation and Rationale
> As Luke said himself, "Simple-V" is not actually quite "simple".
> Moreover, the name is not really descriptive of what it does compared
> to other extensions. For example, when someone sees the name
> "ztrigpi", they immediately are able to guess that it has something to
> do with trigonometric functions involving pi. And it's easy as well to
> guess that "zfpacc" probably means "floating point accuracy". Also,
> I've seen "Simple-V" abbreviated as "SV" which might cause confusion
> in the RISC-V community because there is an "S" extension already and
> a "V" extension as well. I think I've also seen "sv" refer to
> something else but not sure.


shorter to say.


>
> Changing the name to "Flexible Parallelism" will mean a more
> descriptive name and the abbreviation "zflexpar" will certainly not be
> in conflict with anything else in the wider RISC-V community.
>
>
Messy right  now.


> ## Drawbacks
> The biggest drawback I can think of is that there has already been a
> lot of discussion using the name "Simple-V". If we rename, people
> might not realize they are the same. Also, when people are searching
> for discussions of "zflexpar" they might not be able to find the older
> discussions using the older name.


Exactly.


>
> We could limit the drawbacks by publicly announcing that we are
> renaming the "Simple-V" extension to "Flexible Parallelism" (or other
> name) and update the title of the "Simple-V" page to be "Flexible
> Parallelism (previously known as Simple-V)".
>
> ## Alternatives
> We could just keep the name as is. However, if it ever becomes a
> standard extension in the wider RISC-V universe, then we will have to
> live with the name forever and with the fact that it doesn't really
> match with the names of the other extensions.


Inclined to cross bridge when it happens.


>
> # Third proposal:
> Adopt a mascot and better logo for the project. We could adopt a
> turtle as our mascot and I could ask an artist I know to create new
> art assets for us (creative commons license of course).
>
>
I like the volcano. It's cute.  In a roasting, toasting kind of way.

Taglines: The Libre RISC-V SoC. Roasting proprietary hardware since 2018.

mwahaha




-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68