Hi Mychaela, On Wed, Sep 20, 2023 at 12:42:07AM -0800, Mychaela Falconia wrote:
> > Let me put it the other way around: Wouldn't you also feel weird if we > > suddenly started a "FreeCalypso2" project? > > Poor analogy: FC is a family of loosely related projects like Osmocom > (see footnote), not a single specific project like SIMtrace. I am not > claiming an "Osmocom2" project, am I? The point is that there is a well-established name/"Brand" that's around for 13 years now, and that it is always bad to try to reuse that brand for something else without coordination/agreement. Whether that's a "project brand" or a "product" brand" or whatevery you want to call it. But yes, I was trying hard (without spending time) to make an analogy. > Would it be OK with you if I call my project FreeCalypso SIMsniff in > formal naming contexts and simply SIMsniff in casual conversation with > Vintage Mobile Phone community members wondering why phone model ABC > mysteriously refuses to accept SIM card model XYZ? In formal naming > contexts the full names of the two projects would be Osmocom SIMtrace > vs FreeCalypso SIMsniff - it should be obvious that they are distinct, > [...] > Please confirm if my rename proposal is acceptable to you or not - Thank you for your offer to compromise and rename. It is none of my business to interfere with how you call your projects/products/software/hardware, just as long as there is no clash or overlap or easy misunderstanding with any of my/our projects. FreeCalypso SIMsniff IMHO has no resemblence to Osmocom SIMtrace or any other project I'm involved in, and hence it is completely up to you. For what it's worth: I personally do like the new proposed name. > renames are obviously disruptive, hence I will only make the rename > once the new name is approved by all parties. Yes, I fully understand the fall-out of name changes. Thanks again for considering our input here (as stated, it's not just me but several others had reached out privately). > Please also note that my alternative SIM-ME protocol tracer project > reuses existing SIMtrace FPC cables, [...] That is of course completely fine. It has no implication on product naming Anyone can use those designs and or the actual FPC cables. Please also note that we inherited that FPC connector and the principle of those adapter cables from RebelSIM. > the ones which you already offer > separately in your webshop - and one could regard these physical SIM > socket FPC adapters as the most important part of SIMtrace... FYI: I personally would consider the pySim-trace.py as the most useful part of SIMtrace (if one wants to count it as part of it). > Footnote: FreeCalypso began life in 2013 as an off-shoot of then-existing > free-falling remains of Openmoko community, and it is my understanding > that Osmocom is somewhat of a genealogical derivative of Openmoko too, > at least in terms of key people involved. By this logic, Osmocom and > FreeCalypso should be seen as siblings, with Osmocom as the big brother > and FC as the little sister. I see the relation between Openmoko and FreeCalypso. I don't really see it all that much regarding Osmocom. We started on the first projects that later became (and still are) the foundation of Osmocom (bs11_hack, openbsc, later osmocom CNI) 2 years before we started to work on OsmocomBB and hence anything calypso related. But honestly, I don't care too much about such prescribed relationship analogies. Let's get the naming resolved and talk about technology again. I guess we can all agree on that! -- - Harald Welte <lafo...@gnumonks.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
