exa is unmaintained, please use the active fork eza instead about exa

[Freed-Wu]

Hey, any one know what happen about @ogham? If some accident happened, maybe github official can give some maintainer a higher priority to transfer this repo after contace with github, which can keep all original issues and pulls.

[kohane27]

Thank you so much for keeping us updated on the situation. I'm sure we all appreciate your effort to keep this project going! <3

[rugk]

You can archive this repository, to mark it as unmaintained. People then cannot submit PRs and there is a big warning that this is archived.

IMHO this would make it more obvious this is not maintained anymore.

Edit: Oh sorry just read your OP, forget it, you said that there already.

Anyway, thanks for maintaining it so long! 🤗

[Aehmlo]

Second occurrence of exa in the current title should probably read eza?

[ariasuni]

Second occurrence of exa in the current title should probably read eza?

Thanks, fixed the typo x)

[nikelborm]

I've no idea, honestly, if we can or not.

I'm not like somebody close to him or something, I'm just a random dude on the internet with somewhat proficient google skills.

During my shallow research I found 3 email addresses of him, one of which is dead and the other two are linked to his bsago.me domain. I wrote a mini letter to 3 of them with no response for now.

I didn't try to write to him on Twitter (he is not active, meaning he did not like or tweet anything recently, but that doesn't mean that he's not able to receive notifications on email, or to login to his account) or reddit or any other social media. You can write to him on Twitter (he's mentioned it in his GitHub profile contacts). But please be respectful and don't spam him (choose a specific person who will write to him on other social media and platforms (I am able to find more than just Twitter))

[nikelborm]

But from the ethical point of view I personally don't know. If the dude is tired of rust programming, I would rather not bother him too much and just leave him alone. Forks created for a reason.

[nikelborm]

@ariasuni just an idea: send unified instruction how to move PRs to new repo as comments of currently open PRs in this repo

[ariasuni]

I’m not really sure how I would that myself. It would probably mean adding several upstream to the same repository, but I remember it being not very obvious.

[ariasuni]

I honestly don’t know what happened to ogham, no activity since November 2021 and he didn’t answer to my e-mail from 2021-07-18.

[YDX-2147483647]

FYI, ogham's website published a post on 2022-09-15, according to https://bsago.me/tech-notes/feed.json. (sillysaurusx found it 4 days ago at Y Combinator) Therefore I guess ogham is fine but too tired…

[nikelborm]

His latest developer activity I was able to find was 12th June 2023

He's not dead, fortunately

But seems doesn't open github anymore, because that activity is not on github

Also looks like he changed his stack from rust (looks like the project is using rust) to go (i found many go projects of him with recent activity)

[Freed-Wu]

He's not dead, fortunately

So can we contact him to get the authorize to use the name exa?

[verheyenkoen]

Thanks for your work!

Could you maybe also archive this repo and/or add a message in the repo description and on the exa website about this? I've stumbled upon the deprecation via brew doctor but apart from the formula being marked as deprecated, I thought it was a bug at first as both this repo and the exa website don't seem to note this. Only after not finding a ticket with the word "deprecated" I noticed this pinned issue.

[nikelborm]

Thanks for your work!

Could you maybe also archive this repo and/or add a message in the repo description and on the exa website about this? I've stumbled upon the deprecation via brew doctor but apart from the formula being marked as deprecated, I thought it was a bug at first as both this repo and the exa website don't seem to note this. Only after not finding a ticket with the word "deprecated" I noticed this pinned issue.

README has clear header at the beginning about it. And below header there is the reason why it's not possible to archive or change info on the site