Archive all clients except one official one #11504
Replies: 4 comments 8 replies
-
Will check this again later (and maybe provide some additional insights too). Overall, I too agree with archiving some clients but disagree on a centralized one. Just need to give an update about the Debian/Ubuntu package. I was in contact with the package maintainer a couple of months ago and the package has been marked transitional meaning it is being renamed from tldr to tldr-hs in the next Debian and Ubuntu LTS release, it has already been transitioned in interim versions of Ubuntu and Debian Unstable (Sid) , Experimental. |
Beta Was this translation helpful? Give feedback.
-
I do disagree on a centralised client. We certainly can't anticipate all possible platforms. For example, we have tldr clients for the cli, browser, and Android in our ecosystem! It is inevitable that people will come and go from the project, and having a single 'official' client - aside from the platform / environment issues - may fall to the same issues that the existing official clients are prone to I feel. I do understand where you are coming from with the number of official clients though. We probably need some kind of long-term commitment for supporting a client to try to avoid official clients from being completely abandoned. Having said this, I should note that the ecosystem of tldr clients we do have is a valuable thing. It means that tldr is available in every possible environment and OS imaginable - a tall task for an official client to accomplish. Ref packaging, we can definitely improve here. It would significantly help the user experience if we shipped an actively supported client for every distro that we currently have packages in. |
Beta Was this translation helpful? Give feedback.
-
Just a note apart of my specific comment about the case of If the tldr-pages organization finally decided to not have under the organization all the currrent tldr clients, but just one, please, before to archiving it, first notice the original creators or more recent maintainer about this move, give the notice a deadline (1 month) to answer and decide. If they agree with archiving the repository, archive them under the organization. If they doesn't response, archive them under the organization. If they prefer to take back the repository under their ownership, transfer back the repository to the owner or the interested one in maintaining it. I doesn't have many much to say about it, there is a long time I doesn't participate actively in tldr-pages, but I am totally agree with @sbrl's comment. |
Beta Was this translation helpful? Give feedback.
-
I actually came here to post something similar. As an outsider, I want to use tldr-pages, but I'm always stopped prematurely by the number of "official" clients. Given my lack of familiarity with the service, I'm unable to evaluate which one is "best", so I end up choosing none of them and don't use tldr-pages at all 🙁 |
Beta Was this translation helpful? Give feedback.
-
There's been a lot of motion around clients in the last few weeks:
Then there's to be the fact that installing "tldr" on different systems results in different things being installed (with varying degrees of "spec compliance"):
I think that tldr-pages should do two things:
tldr
to use that one client so that the official face of tldr is unifiedI don't think there's really any practical advantage of having 5 official clients given the nature of open source and how people come and go on things, as one or more will inventively fall into disrepair after the current big push to make them spec complaint, or fix all bugs or whatever. Additionally, the fact that depending on your platform, you'll end up with different things with some non "official" is creating confusion in the wild. We've already had many cases of people coming here for help with the haskell client, and is just creating a bad look for the org I think given it's essentially abandoned.
As a historical anecdote, I also remember that there was a conversation years ago on Matrix that someone had wanted to move their client under the
tldr-pages
umbrella and it was decided to not happen as the org didn't need more official clients maintained by one person, and that the wiki page was a sufficient place to list it. The addition oftlrc
andextldr
of course goes against that, and now it feels like "become a org member of tldr-pages, and then you too can have your own official client repo", which is just 🤷Beta Was this translation helpful? Give feedback.
All reactions