| 28 Feb 2024 |
 sbrl (Starbeamrainbowlabs) | so perhaps documenting this process would be worth doing? | 00:56:37 |
 Seth | In reply to @sbrl-57247531659847a7aff542b6:gitter.im
so perhaps documenting this process would be worth doing? It might be that I did a bad job, but I though I did this adequately on the README already. (The usage section.) Perhaps I should add an explicit note that client maintainers can run the commands to see which tests are failing. | 08:25:26 |
| Seth | In reply to @sbrl-57247531659847a7aff542b6:gitter.im
so perhaps documenting this process would be worth doing? * | 08:25:39 |
|  erlefloch joined the room. | 15:51:48 |
| sbrl (Starbeamrainbowlabs) | Yeah, I think that would help. | 20:15:33 |
| sbrl (Starbeamrainbowlabs) | reading it again I see what you mean now | 20:15:42 |
| sbrl (Starbeamrainbowlabs) | * reading it again with context I see what you mean now | 20:15:58 |
| sbrl (Starbeamrainbowlabs) | but at first glance it wasn't clear to me what I would achieve by following the Usage steps | 20:16:18 |
| sbrl (Starbeamrainbowlabs) | is there also some documentation on what tests are included as well somewhere? | 20:16:52 |
| 29 Feb 2024 |
|  DoronZ joined the room. | 07:54:44 |
| DoronZ | Hi :) I want to use this tool in an offline enviroment. What is the recommended way? | 07:55:24 |
| 1 Mar 2024 |
 K.B.Dharun Krishna | Seth: I triggered a new workflow run of test-clients in the test harness repo after updating the CI. Seems like there is an issue with docker validate part outputting something like "the input device is not a TTY" thus making all the badges to show failing. If possible can you check it out. | 09:11:39 |
| K.B.Dharun Krishna | Hi, sorry for the late reply. Most of our clients implement caching so you just need to view a tldr page for the first time after installing a client and all other pages are cached locally allowing you to view them offline in future. | 09:13:20 |
| K.B.Dharun Krishna | Also, some clients implement auto updating making the cache outdated after a certain, but depending on the client auto updating can be disabled too using an environment variable or by setting it to false in the configuration file. | 09:16:36 |
| K.B.Dharun Krishna | * Also, some clients implement auto updating making the cache outdated after a certain period of time, but depending on the client auto updating can be disabled too using an environment variable or by setting it to false in the configuration file. | 09:16:56 |
| Seth | In reply to @kbdk:matrix.org
Seth: I triggered a new workflow run of test-clients in the test harness repo after updating the CI. Seems like there is an issue with docker validate part outputting something like "the input device is not a TTY" thus making all the badges to show failing. If possible can you check it out. Thanks for the heads-up, fixed!
I think GitHub's cache is stalling the README update, but GitHub Pages does serve the correct badges again. | 10:03:32 |
| Seth | In reply to @kbdk:matrix.org
Seth: I triggered a new workflow run of test-clients in the test harness repo after updating the CI. Seems like there is an issue with docker validate part outputting something like "the input device is not a TTY" thus making all the badges to show failing. If possible can you check it out. * | 10:03:46 |
| 11 Mar 2024 |
|  @anubhab:one.ems.host joined the room. | 20:22:40 |
| 12 Mar 2024 |
|  @ayansinhamahapatra-5cc76f8ed73408ce4fbefcc4:gitter.im left the room. | 07:38:46 |
| sbrl (Starbeamrainbowlabs) | Best check each clients' features | 19:29:10 |
| sbrl (Starbeamrainbowlabs) | * Best check each clients' features :-) | 19:29:13 |
| 13 Mar 2024 |
| @anubhab:one.ems.host left the room. | 05:53:18 |
| 16 Mar 2024 |
| K.B.Dharun Krishna | Hi, as you guys know. I plan to make a new client specification release soon (https://github.com/tldr-pages/tldr/milestone/3).
The goal is to deprecate the current method of uploading/providing assets on the website with notification i.e. https://github.com/tldr-pages/tldr/pull/12452 (and fully remove it in the far future along with this change https://github.com/tldr-pages/tldr/issues/12048).
Instead, we replace it with assets uploaded to GitHub releases (https://github.com/tldr-pages/tldr/pull/12062) which uploads all the ZIP and PDF files to the latest release (and clients can download it with https://github.com/tldr-pages/tldr/releases/latest/download and the ZIP name).
Since it's a major change I want to finally clarify once again with you guys, does it look good to you?
Feel free to ask any queries (I will try to address them).
Once the client specification release is done, we can slowly start updating the clients in our Wiki to the new URL (while tracking progress similar to https://github.com/tldr-pages/tldr/issues/9628). | 06:22:48 |
| K.B.Dharun Krishna | * Hi, as some of you guys know. I plan to make a new client specification release soon (https://github.com/tldr-pages/tldr/milestone/3).
The goal is to deprecate the current method of uploading/providing assets on the website with notification i.e. https://github.com/tldr-pages/tldr/pull/12452 (and fully remove it in the far future along with this change https://github.com/tldr-pages/tldr/issues/12048).
Instead, we replace it with assets uploaded to GitHub releases (https://github.com/tldr-pages/tldr/pull/12062) which uploads all the ZIP and PDF files to the latest release (and clients can download it with https://github.com/tldr-pages/tldr/releases/latest/download and the ZIP name i.e. https://github.com/tldr-pages/tldr/releases/latest/download/tldr.zip).
Since it's a major change I want to finally clarify once again with you guys, does this look good to you?
Feel free to ask any queries (I will try to address them).
Once the client specification release is done, we can slowly start updating the clients in our Wiki to the new URL (while tracking progress similar to https://github.com/tldr-pages/tldr/issues/9628).
| 06:25:45 |
| 20 Mar 2024 |
| K.B.Dharun Krishna | Seems like there aren't any new queries, I will make a new client specification release later today. Will start drafting the changelog. | 08:42:02 |
| K.B.Dharun Krishna | Hi, I got a follow up mail from them a few hours ago, anything I should reply?
Hi Dharun,
Hope all is well! Following up regarding the above. Happy to announce Warp is now on Linux! Would you have interest in partnering with us for a github sponsorship?
Let us know and we can find some time to discuss further.
Best,
Tess
| 10:21:27 |
| K.B.Dharun Krishna | Hi guys, a new client specification release is out now. Feel free to check it out at https://github.com/tldr-pages/tldr/releases/tag/v2.2. | 15:47:53 |
| 22 Mar 2024 |
|  eb joined the room. | 08:21:15 |
| 24 Mar 2024 |
|  @0323pin:converser.eu joined the room. | 17:21:10 |
| 28 Mar 2024 |
|  okinea joined the room. | 18:48:47 |
