How is the project organised?

[lars18th]

Hi @hknet ,

The "original" KiTTY fork was structured with a manual patch basis. Please, describe you current approach to maintain patches over the main PuTTY source code. It's your objective to simplify this task?

[hknet]

Hey @lars18th,
thx for asking - you find the main guidelines in the https://github.com/hknet/KiTTY/blob/kitty-0.84/PORTING.md file, that being said it should be a much more straight forward process than the previous kitty-way-of-things.
Yet, the proof will only come with the next putty-release...

My main objective for the first round is to have a stable more secure kitty (putty updates and passwords stored using Windows DPAPI) and a more feature rich key-agent and kitty-launcher (already done) along with some cosmetics (remember window positions and sizes on multi-screen-high-dpi, etc).

Still in the early phase of figuring things out, might end up in a full second porting turn once the whole migration items are done and the smoke has cleared.

Kindest Regards, hk

[lars18th]

Thank you, @hknet, for the description.

You have a huge effort to do. In the meantime perhaps you want to consider creating a list of MOD_ defines. This list can include a short description of the feature and the current status (release, work-in-progress, disabled, removed, legacy, etc.).

What you think?

[hknet]

No worries, I got the list of (currently) 27 MODs that are put in the source, will create the public docs as we're going forward.

[lars18th]

Hi @hknet ,

Since this fork is currently active and under development, I suggest a few minor changes to improve the organisation of the code slightly:

• Move all new directories and files to the \kitty path: Directories like \doc, \screenshots, etc. are not in the original PuTTY source code. If you move all new stuff to this main directory then it will be more easy to trace changes. Anyway perhaps you want to maintain some files in the root (i.e. KNOWN-ISSUES.md) but in this case I suggest to change the names adding _KiTTY_ at the begin.
• Remove in the ABOUT section of the GitHub repository the link to https://www.9bis.com/kitty. Or almost try to say something like "A fork from www.9bis.com/kitty".

I hope you want to consider these suggestions.
Regards.

[hknet]

Thx for your thoughts.

Yet that's not how forwardporting works here.

Granted it's a bit of a mess if you just look at it, that's kind of the point in merging old patchwork onto the new codebase.

Granted some weeks into this effort it might have been a better idea to mingle everything onto putty proper but then again this isn't the last take on migrating the featureset in fact the beta and probably some further more stable updates will incur the learnings and refactoring.

Might even happen that we diverge on some cases from the putty project. I'm especially looking at some connection handling but that's another story for the tcp nerds.

Anyhow thanks for your support and involvement. Until the beta gets in a feature complete state including latest security updates (which it already carries all I know) don't expect much change on file structures as this will be based on the idea how to forward port updates from putty upstream the easiest and if the kitty project isn't revived by cyd01 we will at some point break the heritage and no longer call it a fork but something that stands on its own.

Give it time ;)

[lars18th]

Nice! Please, take your time. 👍