Skip to content
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

Change the "Token Negotiator" to "Brand Connector (Token Negotiator)" #87

Open
zhangzhongnan928 opened this issue Aug 29, 2022 · 3 comments
Assignees

Comments

@zhangzhongnan928
Copy link
Member

We will start sharing the examples with people who want to integrate Devcon ticket attestation.
We should use the name Brand Connector instead of Token Negotiator, or use "Brand Connector (Token Negotiator)" to have both names.

@BastianAlpha
Copy link

We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector

@zhangzhongnan928
Copy link
Member Author

We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector

My concern is Brand Connector is a good name for businesses and consumers, but may not be good for developers.

@BastianAlpha
Copy link

We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector

My concern is Brand Connector is a good name for businesses and consumers, but may not be good for developers.

The challenge i have seen, is that we refer to the product with 2 different names (sometimes in the same conversation). My view is that we should reduce this confusion. Maybe Brand Connector is not the right word for developers. Maybe it is Token Negotiator or (new idea) we call it Token Connector for developers so that it is closer to Brand Connector

I am not 100% sure what is best to be honest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants