Streamline this repository's description

[ryandesign]

Description of problem:

The att/ast GitHub repository's description reads:

This is the AT&T Software Technology ast software download site from AT&T Research. The AT&T AST OpenSource Software Collection provides an overview and Practical Reusable UNIX Software provides a historical perspective. You can join the ast and uwin mailgroups, or monitor the mail archives. There is also an AT&T internal talk. The man page inde…

Perhaps that can be streamlined somewhat. For example, I understand this repository now focuses on ksh and no longer on the rest of ast, and that the mailing lists no longer work. The number of times AT&T is mentioned might be reduced. Fitting the description within the number of characters GitHub will display without cutting it off with an ellipsis would also be good.

[krader1961]

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.

[cschuber]

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.

[jelmd]

"true" ksh is preferred. What's going on here is clearly a disaster/nightmare. IMHO there is no need/not worth to maintain the SW of this hijacked repo ...

[ghost]

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.

I made an issue for that specific topic:
#1447

[kdudka]

@cschuber I am not sure I understand your comment. Which of the following scenarios do you prefer?

1. You volunteer to maintain the upstream distribution of ksh93.
2. You will package ksh93 in case someone else volunteered to maintain it upstream.
3. You will maintain ksh93 in FreeBSD independently of any upstream.

[siteshwar]

@cschuber Kurtis's comment was about forking this repository on GitHub and not as a project.

[cschuber]

On December 9, 2019 12:54:40 AM PST, Siteshwar Vashisht ***@***.***> wrote: @cschuber Kurtis's comment was about forking this repository on GitHub and not as a project. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1441 (comment)

My comment was suggesting you fork the repo. I will create another FreeBSD port to track it.

…

-- Pardon the typos and autocorrect, small keyboard in use. Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://www.FreeBSD.org The need of the many outweighs the greed of the few. Sent from my Android device with K-9 Mail. Please excuse my brevity.

[hyenias]

All, I am willing to attempt to have this repository's description changed to a more streamlined version. However, I do not know exactly what that shorten version should be. Can I get a listing of possible repo description versions? Then, as a group, we rank the responses and finally decide on one. Next, I will attempt to have this repo's description changed.

[gordonwoodhull]

I've renamed it "AST - AT&T Software Tools". I think that adequately describes its original purpose.

I think it should be straightforward to fork this repo and create one specifically for ksh, if anyone wants to do so.