Change name to TK1 everywhere about tillitis-key1 HOT 8 CLOSED

The Go modules are still called "mkdf" and "mkdfsign" in tillitis-key1-apps. Do we change them even if it means we break some external software? We don't want to tag with a v1 for Go tagging reasons.

from tillitis-key1.

@mchack-work I think we should change them, and getting the new name somewhat right is more important that worrying about breaking (any) existing software.

We're building ourselves into the name tk1 now in general... but maybe that's ok, and the packages could be tk1 and tk1sign? Or just tk prefix? But I'm not sure of the benefit; the repo is tillitis-key-1...

from tillitis-key1.

I added a commit that renames the go pkgs to tk1 and tk1sign. Also changes the app internal names from mkdfFOOB to tk1 FOOB.

from tillitis-key1.

I think that leaves only hw/boards/ in tillitis-key1.

from tillitis-key1.

Using tk1 and tk1sign for the Go modules works for me. I agree we should change them. We should also probably warn people at least in the chat.

from tillitis-key1.

PRs:

• #35
• tillitis/tkey-ssh-agent#14

For qemu we would continue just using the tk1 branch: https://github.com/tillitis/qemu/tree/tk1

from tillitis-key1.

While we are discussing naming things - should it be "tk1", or "tk"? ;-)

The repos right now is for the current key, TK1. But will we create new repos for the next generation, or just continue, creating releases? Having a version in the names is ok, good? Clang, LLVM seems to think so. OpenSSL for example does not change the names of things. (The OpenSSL versioning scheme is another matter.)

"There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors."

from tillitis-key1.

We did it!

from tillitis-key1.