Change the name.<p>Graphene for most of us here already means Graphene OS.<p>It feels off that as community members you either didn’t know this or just straight up chose ignore this or worse; chose to ride their brand; even if it’s technically allowed doesn’t mean everyone likes what your doing. It’s just mental overload with an avoidable namespace conflict.<p>TLDR; ask the LLM for a new name. Change it now when it’s low stakes.
> Graphene for most of us here already means Graphene OS.<p>And for the rest, it is probably the actual Graphene as in the material [1]<p>[1] <a href="https://en.wikipedia.org/wiki/Graphene" rel="nofollow">https://en.wikipedia.org/wiki/Graphene</a>
Agreed. When I read the headline I was wondering how this tied into the Graphene I knew.
I mean, in fairness these are two completely different domains. OS development and AI business intelligence are as far apart as one can get.<p>That being said, given the AI context, it does sound pretty shortsighted to choose an overly saturated existing name for your new product. AI agents or LLM chat bots will definitely be confused with prompts like "hey what's this graphene project?". Dunno how tthey missed that.
What? I thought graphene was a graphql python: <a href="https://graphene-python.org/" rel="nofollow">https://graphene-python.org/</a><p>Annnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnyways.
[dead]