-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename Allaki #396
Comments
@jbqubit What do you want me to do? I'll change the Wiki once the names are changed on the schematics. |
Can we pick a name that uses max 3 syllables? It sucks to have to type out something really long. |
I'm fine with ditching the name allaki in a future revision. I advocate for combining multi-word names with underscores. The intent is to emphasize that the name is a compound word and not an assembly of adjectives. If we are disciplined about this then it would be possible to search git for "sayma_afe_baseband" instead of allaki and "sayma_afe_upconverting" instead of nanoga. |
Let's leave this Issue open until next revision of the hardware and make the name in the wiki at that time. |
If you need underscores, you may well need a new name. How about: Basecard They are a bit suggestive to jog associative memory, and short, but don't try to say too much about what the product does. |
Base-mez and mix-mez? To emphasize that they're mezzanine daughter cards that plug into Sayma? |
Scratch that, dumb suggestion. I'd just stick with "baseband" and "mixer" ("full"/unique names "Sayma_AFE_baseband" and "Sayma_AFE_mixer" as @jbqubit suggests). Edit: plus, "basecard" sounds like a card that provides a base for something. Let's not try to be too clever here. Point is users just need to be able to say "I want Sayma with the baseband front-end" or "with the mixer front-end"). If there is a second upconverting card, e.g. for Yb, it can be "mixer_2" or "mixer_HF" (for high-frequency) or something of that ilk. |
I don't think we need to emphasize that in the name. I think we want a name that is suggestive enough to help associative memory, but doesn't try to say anything too precise about the thing.
Requiring a long name to distinguish between variants which share the same short name is a disaster. Each thing should have one name. I know that @hartytp has a number of properties, but I don't require them to be part of his name to know what they are. Short names only, please! And then if you make a new variant, come up with a new short name. |
You don't want to use names that are also regular words you would be using in the discussion. I want to be able to use the word "mixer" to mean what it means without generating confusion about whether I am actually referring to a particular hardware item. Basecard/Mixcard, or Basemod/Mixmod, or Basehat/Mixhat, or BaseAFE/MixAFE.... |
This is exactly the sort of discipline that we do not have, as evidenced by all of the BNC/SMA name variants. Make it easy! Pick a simple name and stick to it! Allaki and Nanoga are the right length as names, it'd just be nice to have something that helps a bit with associative memory. |
There's lots of things that plug into other things in the Sinara ecosystem and, in this case, variants of the thing that plugs. The idea is to have the name read like a path of sorts.
and
|
Glad there's so much interest in naming our children! Can we put this decision on hold until, say Q2, 2018? For me anyway, getting the hardware to work is a higher priority than putting a bow on it. |
I know. We literally spent about 1% this long naming our daughter. wtf? and, where are the bike sheds again? |
Sod it, for the up converting mezzanine v1.0 we'll go for "MixMod". For clarity though, I'm fine with naming the directory Sayma_AFE_MixMod. That's not a name people will use in conversation, but it's instantly recognisable and people will be able to find what they want, which is the important thing! |
Let's go for "BaseMod" and "Sayma_AFE_BaseMod" for Allaki. Please don't suggest anything else unless you really care about this. |
I like:
|
Directories in repository named according to this "file path" style are OK with me, but why not just use a directory called "Sayma_AFE" containing folders called "MixMod" and "BaseMod" and just have those be the names of the boards? It accomplishes exactly the same thing with less hassle, no double naming convention, etc. All you have to do is be creative enough to come up with a different name for each board. |
That's probably a better idea! Let's do that. |
@jbqubit the PCB silk should read Sayma_AFE/BaseMod if that's the directory you are putting it in, not with the two underscores. |
Or just ""BaseMod Upconverting AFE" as we're doing on MixMod. That's more readable IMO, and printing complete directory paths on PCB silk screen things like an odd and unnecessary thing to do IMHO. |
Let's just keep calling it Allaki. |
No. Please stop doing that. |
Agreed, let's stop doing that.
No thanks. I've talked to quite a few users now and everyone I've spoken to prefers BaseMod. FWIW, the up converting mezzanine will definitely be MixMod (we're making an executive decision on that as the funders of that board) so BaseMod would be more consistent than Allaki. It's pretty common with these projects to assign a code name during prototyping, which gets changed for the production version to something more user friendly by the "marketing department". |
I don't like nonsensical names such as Allaki. BaseMod is good. |
|
@jbqubit Still needs changes in a few other places: PCB silk, PCB schematics, PCB file names (think that's it). |
Maybe re-open, but remove the discussion label, and close once the other changes are made? |
I've created new Issues for @sbouhabib. |
tl;dr / "not another conversation about PCB names summary"
@hartytp said in #385
The text was updated successfully, but these errors were encountered: