-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
Repository name #639
Comments
Hmm, you can make it be descriptive with a workable abbreviation/acronym, like uh... Custom Iron Firmware Ecosystem (CIFE). It's also usually just called the"TS100 Ralim Custom Firmware" or some mix of those words, so something as simple as RalimCFW could work too. Or you can name it with a completely irrelevant name, like Marlin, Klipper or Cura that you just happen to like, if the idea of branding an open-source project with your name feels too narcissistic. Another that came to mind is GadgetBridge, which is a unified app to handle wearable devices. From that I got SolderBridge. Maybe SolderBridgeCFW to make it slightly clearer, I 'unno. |
For the reasons you've explained I think that changing name to the repository would make sense. Regards |
@federck |
I just got my TS80p in and I was confused finding TS80 info in the TS100 repo. So as a newcommer I'd say it's deviniatly good to change the name to minimize confusion. I like the UNIRE and SolderBridge idea. But is this repo support really going that wide as those names suggest? Ie. will it also support other solder irons like the Pine's one (https://www.pine64.org/2020/07/15/july-updatepmos-ce-pre-orders-and-new-pinephone-version/). If not, maybe a name as simple as TSxxx will suffice. Edit: D'OH! I just re-read the post on the pine, and ITS YOU WHO ALREADY WROTE SOFTWARE FOR THE PINE PENCIL!! HERO! Ok, yea then let this be the general soldering iron firmware to rull the world then! |
@AntonMadness Indeed it is this repo thats most likely the firmware for Pinecil at this point. There will be more news on that front soonish @federck I am leaning towards Sort of leaning away from using |
Hello, @federck here, I had a problem with my previous account. What do you think about it? |
How about
|
Stylizing it, such as using UnIrE or UNire or UnIRE etc would fix the misreading problem. Though there's also the issue that googling UNIRE will result in finding "Unione Nazionale Incremento Razze Equine", the Italian National Horse Breeding Union :) |
Another late night thought I had was to use "Ferrocerium" inspired by @sreichholf 🤔 |
If I had to choose, I would probably go with UnIrE, like @federck & @JohnEdwa suggested. And the logo could look something like this: Maybe someone has a better taste for font (something more 'tech-ish') or another image for the iron. By the way: It is shorter and thus easier to remember (Maybe due to the very fact @ItsMeAubey mentioned.) compared to "Ternecerium" and the like. |
Thought about FreeSolder in echo to Free Software :) |
Alrighty, going to stir this up again 🤣 So the list looks like:
To get a feel for shortening this list, I've added an emoji next to these, please react we emoji's as appropriate to vote for the ones you like :) |
Welp looks like IronOS is a far bigger winner than all the rest :) Any complaints against this being the new option perhaps? |
H.E.A.T.S. |
IronOS sounds very good. I like opensolder but it sounds like it’s an open solder joint. |
This comment has been minimized.
This comment has been minimized.
Hi @Urus74 |
@Ralim Can you close this issue please, now that it's decided? Thanks! |
Hi Ralim, |
Currently thinking that adding support to this code base for other soldering irons in the future feels highly likely to occur. (#634)
As well as ts100 being a bit odd since the TS80 is also supported now as well.
So, opening the floor for anyone's ideas of what to rename the repo to.
OR
Do i leave the name as is and just make things more clear in the readme?
Open to ideas 🤔
Note that if I do change the name GitHub will redirect all old links etc so they shouldn't break.
The text was updated successfully, but these errors were encountered: