Fork repo or make new repo

[ghost]

As seen here:
#1441
There are benefits to making a new repo, including being able to change some text that currently isn't changeable. That's the problem described in issue 1441.

The att/ast GitHub repository's description reads:
[snip]
Perhaps that can be streamlined somewhat.

Sadly, this too is not something any of the current contributors can change. @siteshwar, I'm wondering if it isn't time to talk again about forking and changing the README.md of this project to point people at the fork.

As a downstream package maintainer, forking is preferred. I'm open to maintaining a "true" ksh along with ksh-ng, or whatever you want to call it.

That would also be a good opportunity to rename this shell to something else which more accurately describes it:
#1444

[krader1961]

This is not constructive.