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

Goal: resolve Kwil and Truf branding issue #74

Open
zolotokrylin opened this issue Mar 7, 2024 · 5 comments
Open

Goal: resolve Kwil and Truf branding issue #74

zolotokrylin opened this issue Mar 7, 2024 · 5 comments
Milestone

Comments

@zolotokrylin
Copy link
Contributor

zolotokrylin commented Mar 7, 2024

Problems:

@zolotokrylin
Copy link
Contributor Author

As we know we will need to rebrand Kwil into TSN at least at the places where our interface the product. These users might include:

  • Data Consumers
  • Developers
  • Data Providers
  • Node Operators
  • ... ?

@brennanjl
Copy link
Collaborator

brennanjl commented Mar 8, 2024

Have discussed this with Cameron quite a bit. What we have come to is:

  • Kwil will provide the ability to custom brand all three developer tools (the binary, admin tool, and main CLI). Truflation will be able to build and distribute these with custom names and root commands. Nested commands and documentation that are not related to the root command will remain unchanged; this would impose a very high maintenance burden on the Truflation team. We should have this doable in 1-1.5 weeks, with our v0.7.1 release.
  • Truflation should wrap the JS SDK with their own SDK. I would highly encourage this, as it allows you to conform to your own terminology, developer experience, and release cycles.
  • Truflation will adopt Kuneiform. This is also primarily for maintenance reasons; we are constantly improving it, so you can simply leverage our documentation as it evolves.
  • Truflation is free to use Kwil's other tooling as-is (IDEs, database explorers, etc.). You're welcome to fork it and make it Truflation branded (AFAICT everything is open source).

@zolotokrylin
Copy link
Contributor Author

Thank you, Brennan, for the memo. I have created problems so that we can manage each issue separately.

@zolotokrylin
Copy link
Contributor Author

@brennanjl : aprrox. middle of May 2024

@zolotokrylin
Copy link
Contributor Author

zolotokrylin commented Jul 17, 2024

@zolotokrylin a related question: if you are onboarding other nodes, do you need the binary to be Truflation branded? e.g. right now, when you run the binary, you run

kwild ...

Previously, we discussed making this customizable, so that you could do:

tsnd ...

This got put on the back burner by Cameron, but will this become a priority?

Originally posted by @brennanjl in #393 (comment)

We already have this thread, so let's continue here.

I don't think it is as important and urgent as the following things, where I would like your help first, please:

After these issues are resolved, we can come back to this Goal.

Thank you 🙏

@zolotokrylin zolotokrylin changed the title Goal: resolve branding issue Goal: resolve Kwil and Truf branding issue Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants