12/24/2022, 4:59:30 PM - gitter-badger (The Gitter Badger) made future room history visible to anyone. 12/24/2022, 4:59:31 PM - gitter-badger (The Gitter Badger) changed the power level of @moderation:gitter.im from Default to Admin. 12/24/2022, 4:59:32 PM - gitter-badger (The Gitter Badger) changed the room avatar. 12/24/2022, 4:59:45 PM - igorshubovych (Igor Shubovych) joined the room 11/25/2015, 9:16:50 PM - igorshubovych (Igor Shubovych): Anybody here? 12/24/2022, 4:59:47 PM - waldyrious (Waldir Pimenta) joined the room 11/26/2015, 2:06:59 AM - waldyrious (Waldir Pimenta): @igorshubovych I got a notification by email, not sure if everybody gets it or if it depends on personal configurations (I have this room starred in gitter) 11/26/2015, 2:10:45 AM - igorshubovych (Igor Shubovych): ok. i’ve just found out that this chat room was created for more than a year, but not used 12/24/2022, 4:59:49 PM - rubenvereecken (Ruben Vereecken) joined the room 12/1/2015, 8:11:13 PM - rubenvereecken (Ruben Vereecken): Hi guys. Hi igor, thanks for shooting me an email 12/1/2015, 8:11:34 PM - rubenvereecken (Ruben Vereecken): I've been really busy lately and a bit slacking on tldr's part, so it's good I getprodded into some action 12/1/2015, 8:11:45 PM - rubenvereecken (Ruben Vereecken): TLDR could be in a better shape indeed :) 12/1/2015, 8:11:55 PM - rubenvereecken (Ruben Vereecken): Poke me when you want to have a chat so we can go over some things. 12/1/2015, 8:12:05 PM - rubenvereecken (Ruben Vereecken): Or tell me if you want to stick to email, though I feel we shouldn't 12/1/2015, 11:17:10 PM - igorshubovych (Igor Shubovych): tada http://tldr-pages.github.io/ 12/1/2015, 11:17:41 PM - igorshubovych (Igor Shubovych): let me know what you think 12/1/2015, 11:29:04 PM - igorshubovych (Igor Shubovych): @rubenvereecken, IMHO one of the most critical thing is to add more people to content approvers. Currently only @rprieto, you and me have power to apply pull requests. As we are often out of time, many pull requests are left unmerged 😟 . I have no ability to add new team members. I wonder if you, Ruben, can do it. Meanwhile I reached Romain in Gitter, email and Twitter, waiting for his reply. 12/2/2015, 7:14:04 AM - igorshubovych (Igor Shubovych): i have some progress on travis 12/2/2015, 7:14:07 AM - igorshubovych (Igor Shubovych): https://github.com/tldr-pages/tldr/issues/336#issuecomment-161145197 12/2/2015, 4:59:13 PM - rubenvereecken (Ruben Vereecken): Hey, nice static site 12/2/2015, 5:00:14 PM - igorshubovych (Igor Shubovych): I am accepting ideas and pull requests :) 12/2/2015, 5:00:36 PM - rubenvereecken (Ruben Vereecken): I like having the zip uploaded to a static site (never though of it), are there any big gains? 12/2/2015, 5:01:02 PM - rubenvereecken (Ruben Vereecken): Ah yes travis would be great for creating the index.json 12/2/2015, 5:01:44 PM - rubenvereecken (Ruben Vereecken): Hmm which it already does at the moment? 12/2/2015, 5:02:20 PM - rubenvereecken (Ruben Vereecken): Indeed, I can't add new content approvers. But I'm sure there are some very willing 12/2/2015, 5:11:46 PM - igorshubovych (Igor Shubovych): >> I like having the zip uploaded to a static site (never though of it), are there any big gains? - it is 30-40 Kb less because i exclude several files (screenshot is the biggest) - it seems that Github generates this zip on the fly and i am not sure that they cache it. in ideal world we should put it on S3 and distribute via CloudFlare/MaxCDN. Maybe one day they will offer us small free hosting. 12/2/2015, 5:12:36 PM - igorshubovych (Igor Shubovych): > Hmm which it already does at the moment? Yes, it regenerated. 12/2/2015, 5:34:15 PM - rubenvereecken (Ruben Vereecken): So we could easily have Travis generate an index without contributors doing so 12/2/2015, 5:34:17 PM - rubenvereecken (Ruben Vereecken): That'd be great 12/2/2015, 5:34:26 PM - rubenvereecken (Ruben Vereecken): Though I see you started a discussion on the index, I should read up first 12/2/2015, 5:34:59 PM - igorshubovych (Igor Shubovych): > That'd be great It is already there. It is done. 12/2/2015, 5:35:22 PM - igorshubovych (Igor Shubovych): let me show it 12/2/2015, 5:35:52 PM - igorshubovych (Igor Shubovych): https://github.com/igorshubovych/tldr/blob/master/scripts/build.sh#L17 12/2/2015, 5:38:26 PM - igorshubovych (Igor Shubovych): that was honestly one of the main purpose of rewrite 12/2/2015, 5:47:31 PM - rubenvereecken (Ruben Vereecken): I'm read up. This is great. rprietro already voiced all my concerns/thoughts throughout the discussion, so my mind is at ease 12/2/2015, 5:47:54 PM - rubenvereecken (Ruben Vereecken): My my you've been industrious :). We should get rprieto to ask content managers 12/2/2015, 5:49:02 PM - rubenvereecken (Ruben Vereecken): With this I might someday accomplish my dream of having a better search in a client 12/3/2015, 5:18:09 AM - igorshubovych (Igor Shubovych): FYI guys, I added @waldyrious as a collaborator 12/3/2015, 5:19:09 AM - waldyrious (Waldir Pimenta): Thanks for the trust! I promise to be cautious and not merge anything in a haste (and submit my own non-trivial changes as PRs) 12/3/2015, 3:23:10 PM - rubenvereecken (Ruben Vereecken): Oh so you _can_ add collaborators 12/3/2015, 3:23:19 PM - rubenvereecken (Ruben Vereecken): Great, welcome on the team @waldyrious :) 12/3/2015, 3:23:36 PM - rubenvereecken (Ruben Vereecken): I know you're thorough enough 12/3/2015, 3:41:08 PM - igorshubovych (Igor Shubovych): @rubenvereecken I found out that I can add collaborators, but not to add to a team. You probably also can do this. 12/3/2015, 4:07:49 PM - rubenvereecken (Ruben Vereecken): Ah. 12/3/2015, 5:54:54 PM - waldyrious (Waldir Pimenta): btw is @ostera a collaborator as well? if not, I think he should be :) 12/3/2015, 6:20:11 PM - rubenvereecken (Ruben Vereecken): :+1: that 12/3/2015, 6:20:26 PM - rubenvereecken (Ruben Vereecken): Is there an easy way to drag people here 12/3/2015, 6:20:45 PM - igorshubovych (Igor Shubovych): i am writing email to him 12/3/2015, 6:22:35 PM - rubenvereecken (Ruben Vereecken): Thanks 12/3/2015, 6:22:42 PM - rubenvereecken (Ruben Vereecken): I'm off for a bit 12/24/2022, 5:00:06 PM - felixonmars (Felix Yan) joined the room 12/3/2015, 6:58:39 PM - * felixonmars (Felix Yan) checks in 12/3/2015, 6:59:30 PM - igorshubovych (Igor Shubovych): Hi, Felix 12/3/2015, 6:59:57 PM - felixonmars (Felix Yan): hi :) 12/3/2015, 7:10:29 PM - igorshubovych (Igor Shubovych): i added Felix too 12/3/2015, 7:57:27 PM - igorshubovych (Igor Shubovych): question, who (except @rprieto) can approve PR on tldr-node-client? 12/3/2015, 7:58:35 PM - felixonmars (Felix Yan): i cannot, i used to own tldr-python-client only 😛 12/3/2015, 7:58:43 PM - igorshubovych (Igor Shubovych): it seems like I managed to fix issue with not being able to update zip 12/3/2015, 7:58:44 PM - igorshubovych (Igor Shubovych): https://github.com/tldr-pages/tldr-node-client/pull/21 12/3/2015, 8:00:43 PM - igorshubovych (Igor Shubovych): this one? https://github.com/tldr-pages/tldr-python-client don’t you use any type of index there? 12/3/2015, 8:01:11 PM - felixonmars (Felix Yan): not yet, that's why i said that i am not active for some time... 12/3/2015, 8:01:25 PM - * felixonmars (Felix Yan) should work on it months ago 12/3/2015, 8:07:46 PM - igorshubovych (Igor Shubovych): oh, i see you load pages on demand. you can just download index.json from http://tldr-pages.github.io/assets/index.json 12/3/2015, 8:08:01 PM - felixonmars (Felix Yan): i see, thanks :3 12/3/2015, 8:16:11 PM - igorshubovych (Igor Shubovych): ok. so let me know if anybody has permissions to approve in tldr-node-client. because for some reason @rprieto disappeared 😟 he does not reply to me... 12/4/2015, 3:30:33 AM - igorshubovych (Igor Shubovych): Guys, i integrated Travis CI to rebuild index and pages archive https://github.com/tldr-pages/tldr/pull/341 12/4/2015, 3:30:59 AM - igorshubovych (Igor Shubovych): could you please review it? it is a big change and any feedback is appreciated 12/24/2022, 5:00:19 PM - ostera (Leandro Ostera) joined the room 12/4/2015, 5:19:37 AM - ostera (Leandro Ostera): hi everyone 12/4/2015, 5:32:39 AM - igorshubovych (Igor Shubovych): hi 12/4/2015, 5:32:52 AM - ostera (Leandro Ostera): how's it going? I'm reviewing your last PR right now 12/4/2015, 5:33:49 AM - igorshubovych (Igor Shubovych): cool 12/4/2015, 5:34:24 AM - ostera (Leandro Ostera): changes spread all over, but it seems okay 12/4/2015, 5:34:59 AM - igorshubovych (Igor Shubovych): sorry, what do you mean by “spread all over”? 12/4/2015, 5:36:14 AM - ostera (Leandro Ostera): it'd be better to have the addition of pages not be part of this pr, it seems like outside the scope. Unless it's part of the scope to also test the travis hooks? 12/4/2015, 5:36:25 AM - ostera (Leandro Ostera): it's really just a detail, nothing to worry about 12/4/2015, 5:37:51 AM - igorshubovych (Igor Shubovych): oh, ok. 12/4/2015, 5:39:28 AM - igorshubovych (Igor Shubovych): ok, so i will wait for yet at least somebody to approve it, and then we can probably merge it 12/4/2015, 5:39:57 AM - igorshubovych (Igor Shubovych): hey, i have quick question, do you have permissions to approve on told-node-client repo? 12/4/2015, 5:44:23 AM - ostera (Leandro Ostera): checking 12/4/2015, 5:44:27 AM - ostera (Leandro Ostera): I left you some comments 12/4/2015, 5:45:26 AM - ostera (Leandro Ostera): nope, only on tldr 12/4/2015, 5:45:58 AM - igorshubovych (Igor Shubovych): ok. nevermind 12/4/2015, 5:47:58 AM - ostera (Leandro Ostera): btw, thanks for letting me contribute to tldr :) very glad to be a part of this project 12/4/2015, 5:48:16 AM - igorshubovych (Igor Shubovych): you are welcome 12/4/2015, 5:58:09 AM - igorshubovych (Igor Shubovych): ok. i will fix #, remove `|| true` and remove `git push … > /dev/null ` 12/4/2015, 5:58:16 AM - igorshubovych (Igor Shubovych): but tomorrow 12/4/2015, 6:08:09 AM - ostera (Leandro Ostera): no worries! 12/4/2015, 6:08:14 AM - ostera (Leandro Ostera): no rush :) 12/4/2015, 6:12:00 AM - igorshubovych (Igor Shubovych): btw, i see in tldr.js you are using index.json from Github API https://github.com/ostera/tldr.js/blob/master/src%2Fstores%2FCommand.js#L11 after that is merged and integrated you will be able to use http://tldr-pages.github.io/assets/index.json 12/4/2015, 9:32:13 PM - igorshubovych (Igor Shubovych): So thanks @ostera for helping me with #342 https://github.com/tldr-pages/tldr/pull/342 Could you guys please also take a look at it? 12/5/2015, 4:08:13 AM - ostera (Leandro Ostera): @igorshubovych awesome, I'll also have to point tldr.js to tldr.jsx – I've rebuilt the client using React and will only be working on that new version from now onwards 12/5/2015, 4:09:10 AM - igorshubovych (Igor Shubovych): so do you think i should merge? no concerns? 12/5/2015, 4:09:44 AM - ostera (Leandro Ostera): It looks alright, just double checked the links and it still seemed to work, so I merged it 12/5/2015, 4:11:07 AM - ostera (Leandro Ostera): also closed the old PR 12/5/2015, 4:11:13 AM - igorshubovych (Igor Shubovych): thanks 12/5/2015, 4:11:21 AM - ostera (Leandro Ostera): no worries 12/5/2015, 4:11:49 AM - igorshubovych (Igor Shubovych): now i have to reconfigure travis 12/5/2015, 4:13:02 AM - ostera (Leandro Ostera): go ahead 12/5/2015, 4:13:08 AM - ostera (Leandro Ostera): I'll keep going through some PR's 12/5/2015, 4:16:30 AM - ostera (Leandro Ostera): actually, @igorshubovych, can you ping me when you're done reconfiguring travis? There's some PR's that could use the automated index generation 12/5/2015, 4:16:45 AM - igorshubovych (Igor Shubovych): yes 12/5/2015, 4:18:22 AM - igorshubovych (Igor Shubovych): weird https://travis-ci.org/tldr-pages/tldr 12/5/2015, 4:21:33 AM - ostera (Leandro Ostera): I see an alert about infrastructure changes 12/5/2015, 4:21:52 AM - ostera (Leandro Ostera): "This job ran on our legacy infrastructure. Please read our docs on how to upgrade." 12/5/2015, 4:22:02 AM - igorshubovych (Igor Shubovych): let me commit it 12/5/2015, 4:27:28 AM - igorshubovych (Igor Shubovych): it is built, but did not push the changes. probably because i have to regenerate the secret. the weird part, is that it says the build is successful. don’t you know why? 12/5/2015, 4:28:38 AM - ostera (Leandro Ostera): if it fails to push we should do an `error "Couldn't push"` 12/5/2015, 4:29:43 AM - igorshubovych (Igor Shubovych): but i thought that non-empty err output will make the build fail 12/5/2015, 4:29:55 AM - ostera (Leandro Ostera): invoking `git push -q` in a sub shell is effectively escaping the `set -ev` 12/5/2015, 4:30:39 AM - igorshubovych (Igor Shubovych): so maybe just do `git push -q` without backticks 12/5/2015, 4:30:46 AM - ostera (Leandro Ostera): that could work 12/5/2015, 4:31:11 AM - igorshubovych (Igor Shubovych): i just don’t want to lost that error output 12/5/2015, 4:31:11 AM - ostera (Leandro Ostera): if it doesn't, then just add an `exit 1` on the else 12/5/2015, 4:31:24 AM - igorshubovych (Igor Shubovych): ok. thanks, working on fixes 12/5/2015, 4:34:21 AM - ostera (Leandro Ostera): no worries 12/5/2015, 4:34:28 AM - ostera (Leandro Ostera): I'll be here if you need me 12/5/2015, 4:41:46 AM - igorshubovych (Igor Shubovych): (dance) https://github.com/tldr-pages/tldr-pages.github.io/commits/master https://travis-ci.org/tldr-pages/tldr 12/5/2015, 4:44:23 AM - ostera (Leandro Ostera): cool! it's not updating the index.json thou 12/5/2015, 4:48:03 AM - igorshubovych (Igor Shubovych): unfortunately it rebuilds `tldr.zip` on every commit, even no .md file was changed. it rebuilds `index.json` too, but Git is smart to recognize it is the same file. it is not that smart with the zip file. it seems like this is related to this issue: http://stackoverflow.com/questions/9714139/why-does-zipping-the-same-content-twice-gives-two-files-with-different-sha1 i tried different recipes, but did not solve it. i added to build script `git config --global diff.zip.textconv "unzip -c -a”` which suppose to fix the issue, but with no success 12/5/2015, 4:49:07 AM - igorshubovych (Igor Shubovych): if you know the solution, you’re welcome to fix it 12/5/2015, 4:49:25 AM - ostera (Leandro Ostera): it might be worth using a tarball 12/5/2015, 4:49:49 AM - igorshubovych (Igor Shubovych): right, i thought about it too, but then we have to rewrite several clients 12/5/2015, 4:50:06 AM - ostera (Leandro Ostera): how come? 12/5/2015, 4:50:39 AM - igorshubovych (Igor Shubovych): those which expect zip 12/5/2015, 4:50:57 AM - igorshubovych (Igor Shubovych): or is it just tldr-node-client? 12/5/2015, 4:51:41 AM - ostera (Leandro Ostera): on tldr-node-client it should be a fairly straightforward change 12/5/2015, 4:51:55 AM - igorshubovych (Igor Shubovych): ok. 12/5/2015, 4:52:11 AM - ostera (Leandro Ostera): perhaps @rubenvereecken can comment on this 12/5/2015, 4:52:43 AM - ostera (Leandro Ostera): and it does seem to be only the node client 12/5/2015, 4:53:00 AM - igorshubovych (Igor Shubovych): for now this is not a big problem: it is just several additional seconds during build, and some inconvinience for those who clone tldr-pages.github.io to fix the static site 12/5/2015, 4:53:08 AM - igorshubovych (Igor Shubovych): but of course we have to fix it 12/5/2015, 4:53:39 AM - ostera (Leandro Ostera): so it's not that much work, just switching unzip2 for node-tar, they seem to have the same API 12/5/2015, 4:53:58 AM - ostera (Leandro Ostera): and we stop polluting the pages history 12/5/2015, 4:54:49 AM - igorshubovych (Igor Shubovych): right, but only @rprieto can commit to node-client 😟 12/5/2015, 4:54:49 AM - ostera (Leandro Ostera): keep in mind that if the file is updated, then doing a request to it to check for an update will make the client behave as if there actually was a new set of pages 12/5/2015, 4:56:07 AM - igorshubovych (Igor Shubovych): i wrote him an email more than a week ago, wrote in Twitter, tried to add in FB, still silence. 12/5/2015, 4:57:59 AM - ostera (Leandro Ostera): hmm 12/5/2015, 4:58:00 AM - ostera (Leandro Ostera): okay 12/5/2015, 4:58:13 AM - ostera (Leandro Ostera): I have to go now, but I'll create an issue so we don't forget 12/5/2015, 4:58:40 AM - igorshubovych (Igor Shubovych): ok. good night 12/5/2015, 5:00:13 AM - ostera (Leandro Ostera): issue created 12/5/2015, 5:00:15 AM - ostera (Leandro Ostera): good night! 12/24/2022, 5:00:47 PM - rprieto (Romain) joined the room 12/7/2015, 11:18:37 AM - rprieto (Romain): hi! 12/7/2015, 11:19:00 AM - rprieto (Romain): sorry I've been out of action for a while, it's great to see so much activity on tldr! 12/7/2015, 11:19:08 AM - rprieto (Romain): Igor I will reply to your email tonight 12/7/2015, 11:19:28 AM - rprieto (Romain): I'm all for having more official contributors, including people with commit access to the node client 12/7/2015, 11:23:00 AM - rprieto (Romain): and really great work on all the recent changes, http://tldr-pages.github.io/ looks great and it's a good move to have the tarball/index.json in a more reliable place + not having everyone rebuilt it every time! 12/8/2015, 5:18:52 AM - igorshubovych (Igor Shubovych): I merged #350, so do not forget to `make setup` again 12/12/2015, 2:44:42 AM - igorshubovych (Igor Shubovych): Ladies and gentelmen, I finally merged this pull request - https://github.com/tldr-pages/tldr-node-client/pull/21. Basically it has to fix issue with pages zip-archive downloading. NPM version is not yet released, so you cannot do `npm update -g`. But you will help a lot, if you do ~~~shell git clone https://github.com/tldr-pages/tldr-node-client.git cd tldr-node-client NODE_ENV=development node ./bin/tldr --update ~~~ Try the last command several times. If i did everything correct, then it should always work, and it should be quite fast. 12/12/2015, 4:02:08 AM - igorshubovych (Igor Shubovych): lol, we need this https://lgtm.co/ 12/13/2015, 10:51:32 AM - felixonmars (Felix Yan): Looks good 😸 12/13/2015, 3:36:10 PM - igorshubovych (Igor Shubovych): @felixonmars What looks good? Have you tried the latest tldr-node-client? 12/13/2015, 4:14:06 PM - igorshubovych (Igor Shubovych): BTW, if you need an inspiration for pages to create, I created a gist with the missing pages https://gist.github.com/igorshubovych/f6c44e6b75fdaf6040a1 12/13/2015, 4:14:22 PM - igorshubovych (Igor Shubovych): feel free to use/add/anything 12/13/2015, 6:28:00 PM - felixonmars (Felix Yan): @igorshubovych I meant lgtm.co 😛 12/13/2015, 6:55:58 PM - igorshubovych (Igor Shubovych): oh, ok 12/14/2015, 1:00:46 AM - waldyrious (Waldir Pimenta): @igorshubovych that list should be moved to the CONTRIBUTING.md page 😃 12/14/2015, 1:40:11 AM - igorshubovych (Igor Shubovych): @waldyrious i doubt that we should put that long list into CONTRIBUTING.md. - IMO Contributing is too long already, it can be even shortened. We are TLDR and should follow this motto everywhere. - Also PagesPlan.md is often changed, because I mark that page is done, after PR is merged. In this case the repo will be polluted by tons of micro-commits. 12/14/2015, 1:41:31 AM - igorshubovych (Igor Shubovych): maybe we can add Wiki page or just keep it in Gists. 12/14/2015, 1:43:52 AM - igorshubovych (Igor Shubovych): Anyway I shared it to ask your opinion on that plan. Does everybody agree that we should add advanced Linux utils like `htop`, which are usually not part of the distribution? How about developers utils? Should we also add framework utils like `rails`? What do you think? 12/14/2015, 3:14:48 AM - waldyrious (Waldir Pimenta): Good points. I think a wiki page would make sense, since it would remain tied to the repo without polluting its history. 12/14/2015, 3:15:46 AM - waldyrious (Waldir Pimenta): I also think that default utils should be prioritized, but common commands should definitely be included too. 12/14/2015, 2:52:08 PM - igorshubovych (Igor Shubovych): @waldyrious what do you mean by default utils? 12/14/2015, 4:47:56 PM - igorshubovych (Igor Shubovych): https://github.com/tldr-pages/tldr/wiki/Pages-plan 12/15/2015, 3:31:50 AM - waldyrious (Waldir Pimenta): I mean those that come by default with common distributions. It's hard to compile an exhaustive list but the list can be built collaboratively :) 12/15/2015, 3:45:15 AM - igorshubovych (Igor Shubovych): ok. i see 12/15/2015, 3:45:56 AM - igorshubovych (Igor Shubovych): guys, @rprieto is saying that these pages (https://github.com/tldr-pages/tldr/pull/313) are against the guidelines. https://github.com/tldr-pages/tldr-node-client/pull/27#issuecomment-164562869 thoughts? 12/16/2015, 6:22:50 PM - igorshubovych (Igor Shubovych): Ladies and gentelmen, the latest tldr-node-client is ready; https://github.com/tldr-pages/tldr-node-client/releases/tag/v1.1.0 12/16/2015, 6:42:02 PM - igorshubovych (Igor Shubovych): i closed all issues in tldr repo, which are related to zip problem 12/24/2015, 6:25:02 PM - igorshubovych (Igor Shubovych): i upgraded told-node-client to 1.1.1. It fixes Page not found message. 12/25/2015, 2:31:02 AM - igorshubovych (Igor Shubovych): Merry Christmas! 12/25/2015, 8:09:45 PM - igorshubovych (Igor Shubovych): Guys, I don’t know what’s happening, but we are trending https://github.com/trending 12/25/2015, 8:11:29 PM - igorshubovych (Igor Shubovych): http://take.ms/kwcIK 12/25/2015, 8:11:45 PM - igorshubovych (Igor Shubovych): and Apple’s Swift is behind us 12/25/2015, 8:12:52 PM - igorshubovych (Igor Shubovych): that’s definitely a sign that we doing an important and useful work! 12/25/2015, 8:13:25 PM - igorshubovych (Igor Shubovych): if anybody knows why (like somebody popular tweeted about us or so), please let us know 12/25/2015, 9:05:30 PM - igorshubovych (Igor Shubovych): it is even higher now http://take.ms/OEDar 12/26/2015, 3:11:57 AM - igorshubovych (Igor Shubovych): overall we are on 7th place today http://take.ms/xxnCaT 12/26/2015, 3:12:41 AM - igorshubovych (Igor Shubovych): i made a little investigation, and found that somebody written about us on several Chinese sites 12/27/2015, 1:41:31 AM - igorshubovych (Igor Shubovych): and today we are on the 3rd place in trending list. wow http://take.ms/hKnae 12/27/2015, 12:21:13 PM - felixonmars (Felix Yan): xD 12/27/2015, 2:53:22 PM - rprieto (Romain): merry Christmas everyone! 12/27/2015, 2:53:32 PM - rprieto (Romain): you're right I think a few blog articles linked to TLDR recently 12/27/2015, 2:53:33 PM - rprieto (Romain): https://github.com/tldr-pages/tldr/graphs/traffic 12/27/2015, 2:53:59 PM - rprieto (Romain): there was ~2700 visitors on Github today 12/27/2015, 2:54:23 PM - rprieto (Romain): i'll try to reply to as many issues as possible (there's a lot of new issues/requests being opened) 12/27/2015, 2:54:49 PM - rprieto (Romain): let's try to keep it nice for all the newcomers! 12/28/2015, 2:42:25 AM - waldyrious (Waldir Pimenta): Oh, so that explains the flurry of recent activity! It's very welcome indeed :) 12/28/2015, 4:38:27 AM - igorshubovych (Igor Shubovych): yes, we have 2700+ stars on Github now, it is approx +700 in a single week. and we are on daily and weekly github.com/trending 12/28/2015, 8:28:03 AM - felixonmars (Felix Yan): don't worry, i also forwarded that article to local communities :3 12/28/2015, 4:34:28 PM - igorshubovych (Igor Shubovych): i actually thought that you related to this, @felixonmars. Thanks for PR (public relations, not pull request) 12/28/2015, 4:35:26 PM - igorshubovych (Igor Shubovych): i am not sure we need more fame at the moment, but earlier i send link to project to qudos, and today it was approved https://www.qudos.io/entries/tldr 12/28/2015, 5:54:01 PM - felixonmars (Felix Yan): that's great, upvoted 😛 12/24/2022, 5:01:10 PM - fluxw42 (Jeroen Meulemeester) joined the room 12/28/2015, 6:21:15 PM - fluxw42 (Jeroen Meulemeester): FYI, TLDR pages is on top of the front page on [HN](https://news.ycombinator.com) :+1: 12/28/2015, 6:23:40 PM - igorshubovych (Igor Shubovych): WOW! 12/28/2015, 6:23:49 PM - igorshubovych (Igor Shubovych): https://twitter.com/newsycombinator/status/681445138145619968 12/28/2015, 6:24:09 PM - felixonmars (Felix Yan): that's great xD 12/28/2015, 6:52:54 PM - felixonmars (Felix Yan): so i try to strike while the iron is hot - contacted some more media xD 12/28/2015, 6:53:26 PM - igorshubovych (Igor Shubovych): oh, i afraid the iron can be very hot then 12/28/2015, 6:53:42 PM - igorshubovych (Igor Shubovych): we have > 3k stars on Github already 12/28/2015, 6:53:42 PM - felixonmars (Felix Yan): xD 12/28/2015, 7:11:06 PM - waldyrious (Waldir Pimenta): The increased attention is great, but I believe it's more important to react quickly and in a friendly manner to PRs than to merge them quickly. This would allow for some modest code review without discouraging contrubutors. Thoughts? 12/28/2015, 7:16:09 PM - felixonmars (Felix Yan): Yeah we are getting more new PRs :3 12/28/2015, 7:30:51 PM - igorshubovych (Igor Shubovych): @waldyrious do you mean anything particular? it seemes to me that we treated new PRs quite nicely. 12/24/2022, 5:01:15 PM - hhirsch (Henry Hirsch) joined the room 12/28/2015, 7:32:30 PM - hhirsch (Henry Hirsch): Feedback was very nice. That is motivating to contribute again. 12/28/2015, 7:33:01 PM - igorshubovych (Igor Shubovych): :) thanks @hhirsch 12/28/2015, 7:33:03 PM - waldyrious (Waldir Pimenta): Definitely, hence my point: nice welcoming is good, and we're already doing that, so fast merge is not necessary :) 12/28/2015, 7:33:54 PM - waldyrious (Waldir Pimenta): I'd say waiting a day or two before merging, to allow other collaborators / maintainers to chime in, would be reasonable 12/28/2015, 7:34:22 PM - waldyrious (Waldir Pimenta): (I know I tend to be nitpicky at times, so let me know if I should dial it down :)) 12/28/2015, 7:36:07 PM - igorshubovych (Igor Shubovych): yes, that makes sense. 12/28/2015, 7:36:33 PM - waldyrious (Waldir Pimenta): :+1: 12/28/2015, 7:37:41 PM - igorshubovych (Igor Shubovych): but some examples are so obvious that probably can be merged. e.g. this one https://github.com/tldr-pages/tldr/pull/410 12/28/2015, 7:38:54 PM - fluxw42 (Jeroen Meulemeester): For me, the shorter the feedback loop, the more encouraging it is to submit a PR. It depends on what the PR contains of course, but when a PR is ready and has all the info needed to merge, shouldn't it be merged as fast as possible? 12/28/2015, 7:46:46 PM - waldyrious (Waldir Pimenta): @igorshubovych agreed, simple changes, README fixes, and so on, can be merged like that. Responding to @fluxw42, the thing is that in such a short period of time, maintainers may not even have the chance to see the notification of a new PR and react. So all issues raised by the "first responder", so to speak, can be addressed, but there may be (and quite often are) details that other maintainers would detect and that then would require another PR to fix, unnecessarily. As the saying goes, "given enough eyes, all bugs are shallow" :) 12/28/2015, 7:48:51 PM - waldyrious (Waldir Pimenta): it is my understanding that replying to a PR quickly and welcomingly is enough encouragement for contributors to remain so. A 1/2 day waiting period before merging contributions that span more than a couple lines doesn't sound like discouraging to me, especially if the reason for the delay is made clear to the PR author. Does that make sense to you @fluxw42 ? 12/28/2015, 8:48:32 PM - fluxw42 (Jeroen Meulemeester): @waldyrious Yes, that sounds reasonable. 12/28/2015, 9:20:27 PM - igorshubovych (Igor Shubovych): ok. let’s make some formal rule. may be one of these? - not least than 2 LGTMs - not least than 2 days of review 12/28/2015, 9:21:42 PM - felixonmars (Felix Yan): so 2 LGTMs in total (including the one who's merging) or 2 LGTMs from others? 12/28/2015, 9:26:13 PM - igorshubovych (Igor Shubovych): what do you think? IMO as it is a Wiki type project 2 LGTM may be legal for most cases. 12/28/2015, 9:27:01 PM - felixonmars (Felix Yan): i think 2 LGTMs in total would be sufficient 12/28/2015, 9:27:37 PM - felixonmars (Felix Yan): although we could also do something like assigning specific field of stuff to one of us 12/28/2015, 9:28:38 PM - felixonmars (Felix Yan): for example, i could take a look at almost anything related to sysadmin/webadmin, etc 12/28/2015, 9:29:17 PM - felixonmars (Felix Yan): just random thoughts 😛 12/28/2015, 9:42:23 PM - igorshubovych (Igor Shubovych): i saw your Github profile, Felix, it looks unbelievable. surely you can handle sysadmin stuff :). but i know a little of everything, therefore i propose on something like 2 LGTMs per PR or 2 days for PR 12/24/2022, 5:01:22 PM - jeanlucaslima (Jean Lucas) joined the room 12/28/2015, 10:09:52 PM - jeanlucaslima (Jean Lucas): Just passing by to say I added xinput.md to linux https://github.com/tldr-pages/tldr/pull/422 12/28/2015, 10:10:28 PM - jeanlucaslima (Jean Lucas): I can also helping solving the issues, at least marking them closed, like this one - https://github.com/tldr-pages/tldr/issues/419 12/28/2015, 10:31:14 PM - igorshubovych (Igor Shubovych): @jeanleonino, thanks for PR. Regarding #419: why do you think it is an issue. the name was chosen some time ago. what do you propose to do now. 12/28/2015, 10:33:21 PM - waldyrious (Waldir Pimenta): 2 LGTMs / 2 days sounds good to me. Is lgtm.co a viable option for enforcing this? 12/28/2015, 10:44:16 PM - igorshubovych (Igor Shubovych): i actually always thought it is a joke :) 12/28/2015, 11:04:57 PM - igorshubovych (Igor Shubovych): so let’s return to q about approval: * 2 LGTMs * 2 days (48 hours) * 2 LGTMs && 2 days (48 hours) 12/28/2015, 11:05:08 PM - igorshubovych (Igor Shubovych): i am voting for 3rd variant 12/28/2015, 11:23:38 PM - igorshubovych (Igor Shubovych): wow, even Ilya Grigorik tweeted abotu us: https://twitter.com/igrigorik/status/681513157542735873 12/29/2015, 12:15:13 AM - igorshubovych (Igor Shubovych): wow, we have 3500 stars on Github, i remember it was less than 2k a week ago 12/24/2022, 5:01:26 PM - pfista (mikey) joined the room 12/29/2015, 12:17:15 AM - pfista (mikey): Really cool stuff! Could I suggest an auto-update on install? 12/29/2015, 12:17:50 AM - igorshubovych (Igor Shubovych): yes, thanks. we have this in todo list for node-client 12/29/2015, 12:30:33 AM - jeanlucaslima (Jean Lucas): @igorshubovych I think it's a solved issue, so the issue should be closed :) 12/29/2015, 1:39:42 AM - waldyrious (Waldir Pimenta): @igorshubovych 3rd variant also is the one that makes the most sense to me. 12/24/2022, 5:01:28 PM - selfagency (Daniel Sieradski) joined the room 12/29/2015, 2:25:14 AM - selfagency (Daniel Sieradski): who do i buy a beer for developing this 12/29/2015, 2:48:45 AM - igorshubovych (Igor Shubovych): @selfagency buy a beer to @rprieto, he is our BDFL 12/29/2015, 3:44:48 AM - waldyrious (Waldir Pimenta): @igorshubovych does lgtm.co actually work? I haven't seen it turn green in any PRs yet. 12/29/2015, 3:54:09 AM - igorshubovych (Igor Shubovych): not yet 12/29/2015, 3:54:21 AM - igorshubovych (Igor Shubovych): i am in the process of configuring it 12/29/2015, 3:54:35 AM - igorshubovych (Igor Shubovych): do you want me to turn it off for a moment? 12/29/2015, 3:57:25 AM - waldyrious (Waldir Pimenta): oh, no hurries, I was just wondering if it was already fully configured, what was holding it down. In that case, carry on :) 12/29/2015, 3:57:47 AM - waldyrious (Waldir Pimenta): @selfagency nice username :) 12/29/2015, 4:19:04 AM - igorshubovych (Igor Shubovych): @waldyrious could you please reply LGTM here https://github.com/tldr-pages/tldr/pull/432 12/29/2015, 4:21:12 AM - waldyrious (Waldir Pimenta): done. is seems to be working :) 12/29/2015, 4:23:20 AM - igorshubovych (Igor Shubovych): Wow! great! 12/29/2015, 4:24:12 AM - igorshubovych (Igor Shubovych): these are equal replies: - :shipit: - :+1: - LGTM 12/29/2015, 4:24:40 AM - igorshubovych (Igor Shubovych): : shipit : : +1 : without spaces 12/29/2015, 4:25:06 AM - waldyrious (Waldir Pimenta): good to know :) is there some place we can propose new synonyms? 12/29/2015, 4:25:27 AM - waldyrious (Waldir Pimenta): 👌, "looks good to me", etc. 12/29/2015, 4:25:28 AM - igorshubovych (Igor Shubovych): .lgtm file in the main repo 12/29/2015, 4:27:38 AM - igorshubovych (Igor Shubovych): i would not add “looks good to me”, it is very easy to make a spelling mistake, put 2 spaces or something like this 12/29/2015, 4:27:53 AM - igorshubovych (Igor Shubovych): i will add ok_hand 12/29/2015, 4:28:13 AM - fluxw42 (Jeroen Meulemeester): At first I thought LGTM meant "Let's Get This Merged" 😄 Had to look it up. 12/29/2015, 4:28:37 AM - waldyrious (Waldir Pimenta): that could be added too 😛 as a backronym! 12/29/2015, 4:36:48 AM - igorshubovych (Igor Shubovych): @waldyrious just added ok_hand 👌, try it somewhere 12/29/2015, 4:39:19 AM - waldyrious (Waldir Pimenta): @igorshubovych tried it in https://github.com/tldr-pages/tldr/pull/432, and strangely enough, it accepted only one LGTM after the merge commit. 12/29/2015, 4:40:01 AM - igorshubovych (Igor Shubovych): i think it is not smart enough to understand that commits were overwritten 12/29/2015, 4:40:15 AM - igorshubovych (Igor Shubovych): so we cannot rely on this tool completely 12/29/2015, 4:40:44 AM - waldyrious (Waldir Pimenta): sure, it's a good helper nevertheless :) 12/29/2015, 4:41:25 AM - igorshubovych (Igor Shubovych): it is just calculating amount of LGTMs 12/29/2015, 4:43:12 AM - waldyrious (Waldir Pimenta): we're getting a lot of merge conflicts 😕 we should make sure people commit to feature branches rather than the master branch. But at the moment it seems to be asking too much from all these new contributors to do their work all over again. Should we rebase the problematic PRs ourselves and merge? 12/29/2015, 4:45:40 AM - igorshubovych (Igor Shubovych): Let’s probably do it for now, and I am fixing the Contributing Guidelines now, so feature branches will be mentioned there 12/29/2015, 4:46:09 AM - igorshubovych (Igor Shubovych): btw, i found it easier to do cherry-picking instead of rebasing in some cases 12/29/2015, 4:47:47 AM - waldyrious (Waldir Pimenta): do your magic, I'm still learning git 😊 12/29/2015, 4:47:51 AM - igorshubovych (Igor Shubovych): wow, 3700 Github stars, and we are Github trending num. 1 of the day, and num. 3 of the week. i am overwhelmed by these numbers. 12/29/2015, 4:48:13 AM - igorshubovych (Igor Shubovych): https://git-scm.com/docs/git-cherry-pick 12/29/2015, 4:48:40 AM - waldyrious (Waldir Pimenta): last time I did a cherry-pick the commit contained a file rename and it became a deletion/insertion 😟 12/29/2015, 4:48:43 AM - igorshubovych (Igor Shubovych): TLDR: it is just take commit with this SHA and apply it to my branch 12/29/2015, 4:49:04 AM - igorshubovych (Igor Shubovych): yes, you should be careful with it 12/29/2015, 6:43:46 AM - felixonmars (Felix Yan): 😃 last night my tweet was on chinese twitter trending, and even linuxtoy re-tweeted 12/29/2015, 9:15:40 AM - felixonmars (Felix Yan): Hmm, any hints why I cannot merge like https://github.com/tldr-pages/tldr/pull/441 ? 12/29/2015, 9:17:31 AM - felixonmars (Felix Yan): or this one: https://github.com/tldr-pages/tldr/pull/425 12/29/2015, 9:17:33 AM - waldyrious (Waldir Pimenta): I suspect it was because 1) master has changed since that PR was sent, and/or 2) the chane was made in the master branch, rather than a feature branch. 12/29/2015, 9:18:17 AM - waldyrious (Waldir Pimenta): As the error message says: "This branch is out-of-date with the base branch. Merge the latest changes from master into this branch." 12/29/2015, 9:19:09 AM - felixonmars (Felix Yan): Well, it shouldn't conflict or the msg would be something related to conflicts. 12/29/2015, 9:19:27 AM - felixonmars (Felix Yan): And GitHub used to handle auto-merges like this gracefully 😕 12/29/2015, 9:19:28 AM - waldyrious (Waldir Pimenta): I agree, not exactly sure what's going on here 12/29/2015, 9:19:48 AM - waldyrious (Waldir Pimenta): maybe our setup is too "smart" 12/29/2015, 9:20:00 AM - felixonmars (Felix Yan): 😛 12/24/2022, 5:01:46 PM - rselwyn (Robbie S) joined the room 12/29/2015, 9:26:55 AM - rselwyn (Robbie S): fyi: a `killall` page needs to be made 12/29/2015, 9:29:44 AM - waldyrious (Waldir Pimenta): @rselwyn lots of pages are still to be made :) it's definitely a work in progress, but the nice thing is that it leaves a lot of room for improvement and contributions 😉 12/29/2015, 9:37:57 AM - rselwyn (Robbie S): Definitely - Submitted a new PR on a different command. 12/29/2015, 11:47:50 AM - hhirsch (Henry Hirsch): @rselwyn Here you go https://github.com/hhirsch/tldr/blob/patch-2/pages/common/killall.md 12/29/2015, 11:54:05 AM - rselwyn (Robbie S): @hhirsch :shipit: 👏 12/29/2015, 11:55:31 AM - rselwyn (Robbie S): @felixonmars Can you take a look at #443 ? 12/29/2015, 1:52:46 PM - ostera (Leandro Ostera): hey guys, anyone on? 12/29/2015, 1:53:15 PM - ostera (Leandro Ostera): it looks like Travis is taking a long time to work through the PR's 12/29/2015, 1:54:32 PM - igorshubovych (Igor Shubovych): No. I integrated lgtm.co. Needs 2 LGTMs from MAINTAINERS 12/29/2015, 1:55:02 PM - ostera (Leandro Ostera): ah, so I'm pretty useless then unless I get added to the organization? 12/29/2015, 1:55:30 PM - igorshubovych (Igor Shubovych): You are added 12/29/2015, 1:59:04 PM - ostera (Leandro Ostera): roger that 12/29/2015, 2:01:07 PM - felixonmars (Felix Yan): @rselwyn The given examples should be the same for both Python 2.x and 3.x. I'd prefer to just leave them in `python` page :) 12/29/2015, 2:32:45 PM - igorshubovych (Igor Shubovych): @ostera could you plz slow down a little bit with merging until we agreed on review terms. Sent you a letter about it 12/29/2015, 2:33:27 PM - ostera (Leandro Ostera): @igorshubovych oh, sorry! I'm mostly pinging the PR authors to rebase/squash 12/29/2015, 2:35:34 PM - ostera (Leandro Ostera): I just merged one 12/29/2015, 2:36:21 PM - igorshubovych (Igor Shubovych): Np 12/29/2015, 2:42:03 PM - felixonmars (Felix Yan): yay 1,243 stars today 12/29/2015, 2:42:18 PM - felixonmars (Felix Yan): now featuring on more medias automagically :3 12/29/2015, 2:42:27 PM - ostera (Leandro Ostera): that's a crazy amount of stars! 12/29/2015, 2:42:31 PM - ostera (Leandro Ostera): kudos everyone 12/29/2015, 3:03:12 PM - igorshubovych (Igor Shubovych): I merged new guidelines. Hope it will help us to simplify approving PRs 12/29/2015, 3:03:45 PM - igorshubovych (Igor Shubovych): I meant updated guidelines 12/29/2015, 3:06:12 PM - ostera (Leandro Ostera): I love how they try to rebase and completely fuck up their branches 😛 12/29/2015, 3:06:24 PM - ostera (Leandro Ostera): we need better tldr pages for git 12/29/2015, 3:11:53 PM - igorshubovych (Igor Shubovych): Feature branches are helpful in this case 12/29/2015, 3:52:30 PM - ostera (Leandro Ostera): guys, whenever you get some time, I'd love some feedback on tldr.jsx. It's getting a lot of views and I'm sure that if it was less appalling it'll help make a better impression for many tldr-pages first-timers :) 12/29/2015, 4:17:59 PM - igorshubovych (Igor Shubovych): I always wanted to ask you about responsive version for it 12/29/2015, 4:18:17 PM - igorshubovych (Igor Shubovych): It should look good on mobile 12/29/2015, 4:31:07 PM - ostera (Leandro Ostera): noted! 12/29/2015, 5:43:04 PM - igorshubovych (Igor Shubovych): **IMPORTANT** Dear contributors! We love you! :+1: Thank you for your contributions. Please be patient while we are reviewing your commits. We have unpredictably high amount of PRs in the recent days! To help you contribute there are detailed instructions in [Contributing Guidelines](https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md). They should solve some of the rebasing issues. TL;DR: use feature branches! 12/29/2015, 8:41:38 PM - igorshubovych (Igor Shubovych): Ladies and gentlemen, I am produd to announce that we released tldr-node-client 1.3, the main feature - Windows support. 12/29/2015, 8:41:50 PM - igorshubovych (Igor Shubovych): plz try it out 12/29/2015, 8:48:10 PM - felixonmars (Felix Yan): *★,°*:.☆\<(=￣▽￣=)>/$:*.°★* 。 12/29/2015, 11:22:42 PM - rselwyn (Robbie S): @igorshubovych Thanks for the update to CONTRIBUTING.md. Clarified a lot for me:) 12/30/2015, 3:08:14 AM - igorshubovych (Igor Shubovych): you are welcome. keep going! 12/30/2015, 4:17:13 AM - rselwyn (Robbie S): Also, @igorshubovych, it seems like there are a lot of PRs that have been approved, but not merged. Is there a solution to merging the approved ones faster? 12/30/2015, 4:17:41 AM - igorshubovych (Igor Shubovych): they will be merged soon 12/30/2015, 4:17:57 AM - igorshubovych (Igor Shubovych): the solution: to merge them! 12/30/2015, 4:20:02 AM - rselwyn (Robbie S): Are you the only one who has merge powers? 12/30/2015, 4:20:11 AM - rselwyn (Robbie S): I know that MAINTAINERS can approve the lgtm 12/30/2015, 4:37:32 AM - igorshubovych (Igor Shubovych): yes, there are 6 people who can approve, but we earlier agreed that we would not merge for 48 hrs to give everybody chance to review 12/30/2015, 4:54:23 AM - rselwyn (Robbie S): That makes sense 12/30/2015, 5:21:58 AM - rselwyn (Robbie S): @igorshubovych I just opened #477, but I'm not sure if it was done correctly 😟 12/30/2015, 5:24:08 AM - igorshubovych (Igor Shubovych): whenever you want to do a update in PR you can do the following ~~~shell git add . # Register new changes git commit —amend # Add current changes to the previous commits git push —force # Overwrite branch of your PR ~~~ it will not break anything 12/30/2015, 5:30:03 AM - igorshubovych (Igor Shubovych): in your situation you can do squashing of commits by rebasing and then `git push - -force` 12/30/2015, 5:50:35 AM - rselwyn (Robbie S): Ok - squashed and updated the PR \ 12/30/2015, 10:50:43 AM - rselwyn (Robbie S): @igorshubovych @waldyrious @felixonmars Is there a way for me to have multiple PRs open at once? 12/30/2015, 11:53:29 AM - felixonmars (Felix Yan): use feature branches :) 12/30/2015, 11:53:39 AM - hhirsch (Henry Hirsch): @igorshubovych We get a crummy history if we encourage people to do stuff like that. Just saying though I do not need to argue about this. 12/30/2015, 4:01:15 PM - igorshubovych (Igor Shubovych): @rselwyn look at my fork https://github.com/igorshubovych/tldr i have several branches each one for the unmerged pull request. i continue fixing pull request in their branches, when i get feedback. 12/30/2015, 11:02:56 PM - igorshubovych (Igor Shubovych): (facepalm) https://github.com/tldr-pages/tldr-node-client/issues/49 12/30/2015, 11:05:25 PM - ostera (Leandro Ostera): 12/24/2022, 5:02:06 PM - Cvetomird91 (Cvetomir Denchev) joined the room 12/30/2015, 11:07:34 PM - Cvetomird91 (Cvetomir Denchev): Hello, there! 12/30/2015, 11:10:29 PM - Cvetomird91 (Cvetomir Denchev): I have the same question concerning separate PRs per commit. So feature branches should do the trick, right? 12/30/2015, 11:10:56 PM - igorshubovych (Igor Shubovych): did you mean several commits per PR? 12/30/2015, 11:10:58 PM - ostera (Leandro Ostera): @Cvetomird91 it's really about one PR per tldr-page you're handling 12/30/2015, 11:11:23 PM - ostera (Leandro Ostera): so if you want to add something to `ls.md` you make a PR for it 12/30/2015, 11:11:38 PM - ostera (Leandro Ostera): and if you also want to add something to `chmod.md` you make another PR 12/30/2015, 11:11:57 PM - ostera (Leandro Ostera): that way it's easier to review, comment, and to merge them 12/30/2015, 11:12:27 PM - Cvetomird91 (Cvetomir Denchev): I see. Thanks. I just made a commit and submitted a PR. The next two commits also appeared on the same PR. This is the reason I am asking this. 12/30/2015, 11:13:02 PM - igorshubovych (Igor Shubovych): yes, do feature branches, it should help 12/30/2015, 11:13:39 PM - Cvetomird91 (Cvetomir Denchev): Thank you. :) I just looked this up and it appears that pull requests are per branch, not per commit on GitHub. 12/30/2015, 11:13:52 PM - ostera (Leandro Ostera): yup! 12/30/2015, 11:19:54 PM - rselwyn (Robbie S): I was the #500th pull request 😮 12/30/2015, 11:23:58 PM - Cvetomird91 (Cvetomir Denchev): Congrats! :) 12/30/2015, 11:24:37 PM - ostera (Leandro Ostera): It'd be a pity if someone...closed it. 12/30/2015, 11:24:41 PM - ostera (Leandro Ostera): Muahaha 12/30/2015, 11:25:46 PM - ostera (Leandro Ostera): but seriously, I'm closing it. Comments on the PR. 12/30/2015, 11:27:18 PM - ostera (Leandro Ostera): fuck that was unintended haha, so sorry 12/30/2015, 11:41:11 PM - rselwyn (Robbie S): @ostera Fixed! 12/31/2015, 3:26:56 AM - Cvetomird91 (Cvetomir Denchev): Hello again. :) 12/31/2015, 3:27:31 AM - Cvetomird91 (Cvetomir Denchev): I noticed that there isn't an OpenBSD and/or FreeBSD section. Where can I propose the adding of such sections? 12/31/2015, 3:29:42 AM - rselwyn (Robbie S): Fork and PR 12/31/2015, 3:29:49 AM - rselwyn (Robbie S): @Cvetomird91 12/31/2015, 3:29:59 AM - Cvetomird91 (Cvetomir Denchev): Thank you. :) 12/31/2015, 3:30:25 AM - rselwyn (Robbie S): See CONTRIBUTING.md 12/31/2015, 5:39:22 AM - waldyrious (Waldir Pimenta): hey @ostera when you get the chance please comment on https://github.com/tldr-pages/tldr/pull/475 12/31/2015, 6:35:50 AM - ostera (Leandro Ostera): @waldyrious donzo 12/31/2015, 6:39:08 AM - waldyrious (Waldir Pimenta): :+1: 12/31/2015, 6:46:10 AM - waldyrious (Waldir Pimenta): I pity the ~100 poor souls (me included) who watch the project, in this period of increased activity xD 12/31/2015, 6:46:27 AM - waldyrious (Waldir Pimenta): I've just finished going over all recently updated PRs 12/31/2015, 6:46:51 AM - waldyrious (Waldir Pimenta): that's a wrap for me, gonna hit the bed. See y'all tomorrow. 12/31/2015, 6:48:19 AM - ostera (Leandro Ostera): good work today @waldyrious 12/31/2015, 6:48:22 AM - ostera (Leandro Ostera): see you tomorrow 12/31/2015, 6:51:07 AM - igorshubovych (Igor Shubovych): :+1: 12/31/2015, 9:11:43 AM - ostera (Leandro Ostera): I'm out everyone, see you all tomorrow 1/2/2016, 6:02:50 AM - waldyrious (Waldir Pimenta): 1/2/2016, 6:03:08 AM - waldyrious (Waldir Pimenta): 12/24/2022, 5:02:21 PM - kmoe (Katy Moe) joined the room 1/2/2016, 6:38:14 AM - kmoe (Katy Moe): hey all, seems build is failing? 1/2/2016, 6:38:36 AM - igorshubovych (Igor Shubovych): really? looking into it 1/2/2016, 6:38:50 AM - kmoe (Katy Moe): linter error 1/2/2016, 6:38:57 AM - kmoe (Katy Moe): trailing spaces on last.md 1/2/2016, 6:39:02 AM - kmoe (Katy Moe): at least, that's what it is on my local 1/2/2016, 6:40:05 AM - igorshubovych (Igor Shubovych): fixed. CI should be updated soon 1/2/2016, 6:40:09 AM - kmoe (Katy Moe): oh no, was this my PR? I have literally no idea how that could have happened 1/2/2016, 6:40:43 AM - waldyrious (Waldir Pimenta): Don't worry, @kmoe, seems to have been #274 :) https://travis-ci.org/tldr-pages/tldr/builds 1/2/2016, 6:40:59 AM - igorshubovych (Igor Shubovych): not your 1/2/2016, 6:41:06 AM - kmoe (Katy Moe): ah yes 1/2/2016, 6:41:08 AM - kmoe (Katy Moe): thanks 1/2/2016, 6:41:18 AM - kmoe (Katy Moe): was worried my pre-commit hook wasn’t working! 1/2/2016, 6:42:04 AM - waldyrious (Waldir Pimenta): @igorshubovych can't we re-enable travis checks? I'm a bit out of touch with the PR checks problems. Wasn't LGTM the only one failing? 1/2/2016, 6:42:34 AM - igorshubovych (Igor Shubovych): i have just added Travis CI check on master branch 1/2/2016, 6:42:48 AM - igorshubovych (Igor Shubovych): let’s see if this don’t cause further issues 1/2/2016, 6:43:07 AM - igorshubovych (Igor Shubovych): thanks for quick reaction @kmoe 1/2/2016, 6:43:10 AM - waldyrious (Waldir Pimenta): :+1: 1/2/2016, 6:43:11 AM - kmoe (Katy Moe): no problem 1/2/2016, 6:43:25 AM - kmoe (Katy Moe): btw, I’m making the pgrep PR now. is it okay if I correct another `{{Finder}}` issue? 1/2/2016, 6:43:31 AM - kmoe (Katy Moe): it’s actually what I copied the syntax from 1/2/2016, 6:43:34 AM - waldyrious (Waldir Pimenta): I'm off to bed, see you all tomorrow 1/2/2016, 6:43:43 AM - kmoe (Katy Moe): cool, see you 1/2/2016, 6:43:55 AM - waldyrious (Waldir Pimenta): keep up the great work 😉 1/2/2016, 7:04:39 AM - kmoe (Katy Moe): wow, I’m guessing Travis is now checking every single PR? 1/2/2016, 7:04:45 AM - kmoe (Katy Moe): (even the closed ones?) 1/2/2016, 7:04:59 AM - igorshubovych (Igor Shubovych): what’s up? 1/2/2016, 7:08:44 AM - kmoe (Katy Moe): just noticed all the PRs now have open checks :) 1/2/2016, 9:57:26 PM - Cvetomird91 (Cvetomir Denchev): Hello again, guys! 1/2/2016, 11:56:17 PM - rselwyn (Robbie S): Hey 1/3/2016, 6:14:21 PM - igorshubovych (Igor Shubovych): sorry, have a failing build. investigating now 1/3/2016, 6:17:14 PM - igorshubovych (Igor Shubovych): Fixed 12/24/2022, 5:02:37 PM - marksylee (Mark Lee) joined the room 1/4/2016, 12:54:35 PM - marksylee (Mark Lee): hello, I wanna add "mailx" command to pages. I notice that "mailx" can accept both "mail" and "mailx" as beginning, so I should create two markdown files named "mail.md" and "mailx.md" with the same content, or there is other better way? Tks a lot! 1/4/2016, 12:58:15 PM - igorshubovych (Igor Shubovych): For now there is no better choice. But I would start with creating a single mailx page, and after it is ready think about copying it. Otherwise there will be too much duplicate work, as we usually have some feedback 1/4/2016, 1:08:16 PM - marksylee (Mark Lee): Got it! Thank you. 1/4/2016, 6:48:57 PM - igorshubovych (Igor Shubovych): Dear contributors, Yesterday we have made some improvements on [Contributing Guidelines](https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md): - add warning to try commands - add video tutorials for interactive rebase - add instructions for git commit --amend They are in #560. I hope it will make contributing even more clear and simple 1/5/2016, 1:37:45 AM - Cvetomird91 (Cvetomir Denchev): Is there a way to squash commits that occured before the master branch was merged into the current branch? 1/5/2016, 1:43:24 AM - Cvetomird91 (Cvetomir Denchev): Excuse me if this question was asked before. Will it be appropriate to close the PR and reopen a new one with the same changes if I don't manage to find a way to do this in a more graceful manner. 1/5/2016, 1:46:02 AM - Cvetomird91 (Cvetomir Denchev): I'm talking about the pull request with id #556 : https://github.com/tldr-pages/tldr/pull/556/commits 1/5/2016, 2:35:13 AM - igorshubovych (Igor Shubovych): you can try to do the following ~~~shell git rebase —interactive HEAD~2 # In the opened file remove the line for the useless commit # Save the file # IMPORTANT: If everything is alright (check `git log`), then git push —force ~~~ 1/5/2016, 2:43:32 AM - Cvetomird91 (Cvetomir Denchev): Thank you. :) 1/5/2016, 2:48:49 AM - igorshubovych (Igor Shubovych): let me know the results (fingers crossed) 1/5/2016, 3:21:49 AM - Cvetomird91 (Cvetomir Denchev): I couldn't find the commit I was looking for in the list with commits. This is what happened in the remote repository: https://github.com/tldr-pages/tldr/pull/556/commits 😕 1/5/2016, 3:22:15 AM - igorshubovych (Igor Shubovych): omg 1/5/2016, 3:22:45 AM - igorshubovych (Igor Shubovych): how did this happen? 😟 1/5/2016, 3:26:50 AM - Cvetomird91 (Cvetomir Denchev): I'm still wondering. 1/5/2016, 3:27:03 AM - igorshubovych (Igor Shubovych): what have you done? 1/5/2016, 3:29:30 AM - Cvetomird91 (Cvetomir Denchev): I've just checked my shell history. It appears that I've closed the interactive rebase vim session without making any changes and pushed to my 'jobs' branch. 1/5/2016, 3:30:24 AM - igorshubovych (Igor Shubovych): but i asked to check logs, it was an important step 1/5/2016, 3:30:32 AM - igorshubovych (Igor Shubovych): i mean `git log` 1/5/2016, 3:31:06 AM - ostera (Leandro Ostera): just in case, when you're doing an interactive rebase to squash everything to the first commit *you made*, you want to use the hash of the commit _previous_ to that first commit you made 1/5/2016, 3:31:40 AM - ostera (Leandro Ostera): so ``` some commit #2 some commit #1 your first commit first commit before your commit ``` 1/5/2016, 3:34:02 AM - ostera (Leandro Ostera): in this case, @Cvetomird91, I'd advice you to take a look at the `git reflog` command, and look for the point in time right before merging master into your branch 1/5/2016, 3:35:00 AM - ostera (Leandro Ostera): and then use that reflog id (usually look like `HEAD@{n}`) to do a hard checkout (`git reset --hard HEAD@{n}`) 1/5/2016, 3:35:16 AM - ostera (Leandro Ostera): that will revert all your changes all the way to your first commit, without destroying that first commit 1/5/2016, 3:36:32 AM - igorshubovych (Igor Shubovych): honestly, in your case, i would 1) save the file somewhere 2) close pull request 3) delete local and remote topic branches (`git branch -d topic-branch-name`) 4) create new topic branch 5) copy saved file there, commit it and publish 6) create new Pull Request 1/5/2016, 3:36:40 AM - ostera (Leandro Ostera): you could go through all this or just copy the file somewhere else, delete the branch...oh igor you beat me to it 1/5/2016, 3:37:04 AM - ostera (Leandro Ostera): he might be able to just delete the local branch, copy the file over, commit, and force push it 1/5/2016, 3:38:19 AM - igorshubovych (Igor Shubovych): maybe, try this, @Cvetomird91 1/5/2016, 3:50:56 AM - Cvetomird91 (Cvetomir Denchev): I've closed the previous PR and created a new topic branch. PR request submitted. Thank you for your assistance and for the new git commands. I'm going to check out those too. 1/5/2016, 5:34:26 PM - igorshubovych (Igor Shubovych): Ok. Ladies and gentlemen, we have some updates for you: we updated the home site - http://tldr-pages.github.io/ Now demo is working just on the home page 1/5/2016, 5:35:30 PM - igorshubovych (Igor Shubovych): We know about some issues there, and @ostera is already working on them. But we thought it would be important for newcomers to try it ASAP. 1/5/2016, 5:37:11 PM - igorshubovych (Igor Shubovych): Another news, we created Twitter account for the project: http://twitter.com/tldr_pages We will try to provide important and interesting updates there. 12/24/2022, 5:02:48 PM - lukeberry99 (Luke Berry) joined the room 1/6/2016, 12:54:42 AM - lukeberry99 (Luke Berry): Hey all, is there a TL;DR api? I'm looking to build an iOS app for it, or would I need to use githubs api to access the most up-to-date pages? 1/6/2016, 12:55:15 AM - ostera (Leandro Ostera): Hey @lukeberry99, Github API is the way to go for now 1/6/2016, 12:55:54 AM - ostera (Leandro Ostera): I'd initially pull the tarball of all pages, and then update with the API as cache breaks 1/6/2016, 12:59:06 AM - lukeberry99 (Luke Berry): Makes sense, cheers :) 1/6/2016, 3:27:29 AM - Cvetomird91 (Cvetomir Denchev): Good evening! 1/6/2016, 3:29:41 AM - Cvetomird91 (Cvetomir Denchev): I've managed to find out the reason for the merging issues I had yesterday. The reason behind this problem was that I didn't synchronize my forked version of the repository with the upstream. Here's how this can be avoided: http://stackoverflow.com/questions/7244321/how-to-update-a-github-forked-repository 1/6/2016, 3:43:34 AM - igorshubovych (Igor Shubovych): i have this as an alias alias.upstream=!git checkout master && git fetch origin -v && git fetch upstream -v && git merge upstream/master 1/6/2016, 3:43:53 AM - igorshubovych (Igor Shubovych): so i run only `git upstream` 12/24/2022, 5:02:54 PM - mflint (Matthew Flint) joined the room 1/6/2016, 4:06:44 AM - mflint (Matthew Flint): Hello - just dropping by to say I have an iOS app almost ready to go. If anyone has an iPhone/iPad running iOS 9.2, I'd be happy to send a TestFlight invitation. 1/6/2016, 4:07:00 AM - mflint (Matthew Flint): Either email m@tthew.org, or grab me on Twitter: @mkflint 1/6/2016, 4:09:05 AM - mflint (Matthew Flint): @lukeberry99 Sorry man, I feel like I've stomped on your conversation from earlier this evening 😕 1/6/2016, 4:09:42 AM - mflint (Matthew Flint): Oh, for TestFlight invitation I'll need an email address. My Twitter DMs are open. 1/6/2016, 4:43:04 AM - igorshubovych (Igor Shubovych): oh, that’s a great news! 1/6/2016, 4:59:54 AM - mflint (Matthew Flint): For the iOS app, I'm collecting bug/enhancements reports in [github issues](https://github.com/mflint/ios-tldr-viewer/issues) 1/6/2016, 10:16:30 PM - Cvetomird91 (Cvetomir Denchev): @igorshubovych Can you please address the following PR: #613 when you have time. Thanks in advance. 1/6/2016, 10:36:43 PM - igorshubovych (Igor Shubovych): replied 1/7/2016, 1:54:53 PM - Cvetomird91 (Cvetomir Denchev): Thank you. 12/24/2022, 5:02:59 PM - Moddus (Moddus) joined the room 1/8/2016, 2:44:04 PM - Moddus (Moddus): Hi there, I just want to let you know that I’ve created a docset for [dash](https://kapeli.com/dash) and [zeal](https://zealdocs.org/) based on your awesome project. The docset is accepted by the creator of dash and is ready for use. The docset repo can be found here https://github.com/Moddus/tldr-python-dash-docset. 1/8/2016, 11:24:37 PM - igorshubovych (Igor Shubovych): Really? That’s an awesome news! 1/8/2016, 11:24:53 PM - igorshubovych (Igor Shubovych): how often it is updated? 1/9/2016, 3:02:21 AM - hhirsch (Henry Hirsch): I think my PRs don't fit your mold. No hard feelings. Still a lot of other contributors. cya 1/9/2016, 3:09:26 AM - ostera (Leandro Ostera): @hhirsch which is your PR? 1/9/2016, 3:11:41 AM - Moddus (Moddus): The update process for docset is based on pull requests which will be merge by @Kapeli. I’ve talked to him and it's okay to frequent send pull request. So I will write a script to generate pull request one or two times a week. Then we will see if this procedure works. 1/9/2016, 6:44:59 PM - igorshubovych (Igor Shubovych): @Moddus I added Dash and Zeal clients here: https://github.com/tldr-pages/tldr/wiki/TLDR-clients 1/9/2016, 6:45:08 PM - igorshubovych (Igor Shubovych): feel free to update this page 1/9/2016, 8:23:18 PM - Moddus (Moddus): @igorshubovych thanks ! I appreciate you work. 1/12/2016, 8:40:49 PM - rubenvereecken (Ruben Vereecken): Hmm this chat actually sees some action as well 12/24/2022, 5:03:05 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im joined the room 1/12/2016, 11:17:10 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im: Just came across tldr pages and I love it! 1/12/2016, 11:18:20 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im: unfortunately, the one man page I was looking for doesn't seem to exist yet (cron/crontab). 1/12/2016, 11:18:26 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im: I can never remember the syntax 1/12/2016, 11:18:50 PM - ostera (Leandro Ostera): @andrewhavens thanks! feel free to add it yourself so you never have to remember it again :) 1/12/2016, 11:19:21 PM - ostera (Leandro Ostera): all contributions are welcome, please have a look at our contributing guidelines: https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md 1/12/2016, 11:19:51 PM - ostera (Leandro Ostera): it's super straightforward, and you can even create new pages from within Github's interface 1/12/2016, 11:20:09 PM - ostera (Leandro Ostera): (or suggest typofixes or modifications to already existing pages) 1/12/2016, 11:22:40 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im: sure, I’d be happy to…just wondering…should I create it as cron or crontab? 1/12/2016, 11:23:49 PM - ostera (Leandro Ostera): well cron is the utility launched by launchd _when there is a crontab_, but you typically execute crontab -e 1/12/2016, 11:24:33 PM - ostera (Leandro Ostera): so `crontab` is the name of the command you use, and thus the page you'd create 1/12/2016, 11:25:01 PM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im: gotcha…curious…does tldr provide any auto-completion? 1/12/2016, 11:25:53 PM - ostera (Leandro Ostera): I don't know if it has been implemented in any cli clients yet, but it's possible 1/12/2016, 11:26:07 PM - ostera (Leandro Ostera): it's on the web client's roadmap to add it 1/12/2016, 11:28:31 PM - ostera (Leandro Ostera): you may want to take a look at `man crontab` and `man 5 crontab` to get a refresher and summarize from 1/13/2016, 1:18:53 PM - rubenvereecken (Ruben Vereecken): I was wondering about auto-completion as well 1/13/2016, 1:19:20 PM - rubenvereecken (Ruben Vereecken): If I'd want it in my oh-my-zsh, I think I'd have to write a zsh plugin that reads from tldr's cache? 1/13/2016, 2:37:54 PM - fluxw42 (Jeroen Meulemeester): For the node client, there is [node-tabtab](https://github.com/mklabs/node-tabtab) or [commander-tabtab](https://github.com/bencevans/commander-tabtab.js). Not sure if the last one works since it's no longer maintained. With node-tabtab you can generate a completion script that works for both bash and zsh. 1/13/2016, 3:04:53 PM - rubenvereecken (Ruben Vereecken): that _is_ fancy 1/13/2016, 3:04:55 PM - rubenvereecken (Ruben Vereecken): well worth it 1/13/2016, 3:04:57 PM - rubenvereecken (Ruben Vereecken): I like tab. 1/13/2016, 3:32:40 PM - rubenvereecken (Ruben Vereecken): Quick Q 1/13/2016, 5:07:34 PM - rubenvereecken (Ruben Vereecken): Taking a break, then incorporating `tldr-lint` with Travis 1/13/2016, 5:07:41 PM - rubenvereecken (Ruben Vereecken): It's been a long road 1/13/2016, 5:07:57 PM - igorshubovych (Igor Shubovych): What was your question? (Quick Q) 1/13/2016, 5:08:21 PM - rubenvereecken (Ruben Vereecken): I dropped it, thanks though 1/13/2016, 5:08:31 PM - igorshubovych (Igor Shubovych): ah 1/13/2016, 5:08:46 PM - rubenvereecken (Ruben Vereecken): What would you say about hosting tldr-lint in the tldrpages org 1/13/2016, 5:08:57 PM - rubenvereecken (Ruben Vereecken): It's better befitting 1/13/2016, 5:11:33 PM - rubenvereecken (Ruben Vereecken): Also :+1: for poking at the older pages 1/13/2016, 8:45:04 PM - igorshubovych (Igor Shubovych): hi guys, it is a great day for us. Thanks to @rubenvereecken `tldr-lint`, we have more sophisticated linter than just linting Markdown! 1/13/2016, 8:52:50 PM - rubenvereecken (Ruben Vereecken): Cheers Igor 1/13/2016, 9:06:06 PM - rubenvereecken (Ruben Vereecken): It's now also aliased to `tldrl` btw 1/13/2016, 9:48:02 PM - ostera (Leandro Ostera): now we just need a tldr-page for it 😛 1/13/2016, 9:57:54 PM - igorshubovych (Igor Shubovych): :) 1/13/2016, 10:33:32 PM - rubenvereecken (Ruben Vereecken): hehe 12/24/2022, 5:03:20 PM - sunny256 (Øyvind A. Holm) joined the room 1/14/2016, 4:14:20 AM - sunny256 (Øyvind A. Holm): Ah, cool. Didn't know about Gitter, so this first comment is somewhat historic. Looks great. 1/14/2016, 4:15:31 AM - sunny256 (Øyvind A. Holm): And just heard about tldr-pages at the Linux Voice podcast. Nice initiative. 1/14/2016, 6:13:29 PM - rubenvereecken (Ruben Vereecken): Never heard of that podcast, cheers 1/15/2016, 4:45:54 PM - waldyrious (Waldir Pimenta): We've reached 7k stars!!! 🌟 🎆 ✨ 1/15/2016, 5:03:43 PM - rubenvereecken (Ruben Vereecken): woot 1/15/2016, 5:04:12 PM - rubenvereecken (Ruben Vereecken): risin' up, back on the street 🎵 12/24/2022, 5:03:26 PM - notpeter (Peter Tripp) joined the room 1/20/2016, 5:27:06 PM - notpeter (Peter Tripp): https://github.com/tldr-pages/tldr/pull/699 1/20/2016, 5:27:12 PM - notpeter (Peter Tripp): Goodnight y'all. 1/20/2016, 6:28:40 PM - igorshubovych (Igor Shubovych): Wow, that’s an impressive commit 1/21/2016, 7:19:46 PM - igorshubovych (Igor Shubovych): https://twitter.com/tldr_pages/status/690169014643990528 1/21/2016, 7:23:39 PM - rubenvereecken (Ruben Vereecken): hahaha 1/22/2016, 5:38:39 AM - waldyrious (Waldir Pimenta): @rubenvereecken good call on most of the assignments. A few of them I can't really do much until the authors respond, but others are indeed within my reach to advance. I'll try to tackle them ASAP 1/22/2016, 5:39:23 AM - waldyrious (Waldir Pimenta): btw can anyone comment on https://github.com/tldr-pages/tldr/issues/686? Am I counting wrong all of a sudden? 1/22/2016, 4:19:52 PM - rubenvereecken (Ruben Vereecken): @waldyrious feel free to flag those to me 1/22/2016, 4:20:14 PM - rubenvereecken (Ruben Vereecken): I forced a bunch of PRs by pulling them in through command line and merging manually, performing whatever edits I wanted 1/22/2016, 8:21:02 PM - waldyrious (Waldir Pimenta): @rubenvereecken I will as soon as I get the time to look at them more carefully :) I addressed a few last night but ran out of time. 2/3/2016, 3:34:05 PM - igorshubovych (Igor Shubovych): tldr-node-client 1.5.0 is released https://github.com/tldr-pages/tldr-node-client/releases/tag/v1.5.0 2/3/2016, 5:48:51 PM - igorshubovych (Igor Shubovych): And we had to release bug-fix for our Windows users. https://github.com/tldr-pages/tldr-node-client/releases/tag/v1.5.1 2/4/2016, 2:05:33 AM - rubenvereecken (Ruben Vereecken): Due to some weird GitHub stuff I'm not an admin for tldr-lint 2/4/2016, 2:05:37 AM - rubenvereecken (Ruben Vereecken): So I can't enable Travis 2/4/2016, 2:05:41 AM - rubenvereecken (Ruben Vereecken): Please get me that admin 12/24/2022, 5:03:34 PM - anoopengineer (Anoop Kunjuraman) joined the room 2/5/2016, 3:22:57 AM - anoopengineer (Anoop Kunjuraman): @all just wanted to show off the tldr client that I made - https://github.com/anoopengineer/tldr 2/5/2016, 3:24:23 AM - anoopengineer (Anoop Kunjuraman): Created as an excuse to work on termbox and termui using go language, it turned out well... i guess.. 2/5/2016, 3:24:36 AM - anoopengineer (Anoop Kunjuraman): Comments welcome! 2/5/2016, 3:29:37 AM - igorshubovych (Igor Shubovych): good one 2/5/2016, 3:30:56 AM - anoopengineer (Anoop Kunjuraman): thanks! 2/5/2016, 3:34:00 AM - igorshubovych (Igor Shubovych): could you plz add it here https://github.com/tldr-pages/tldr/wiki/TLDR-clients 2/5/2016, 3:35:14 AM - anoopengineer (Anoop Kunjuraman): sure! 2/9/2016, 12:38:31 AM - igorshubovych (Igor Shubovych): this is a decent course for everybody, https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github i am glad they made it free now 2/9/2016, 5:50:28 AM - igorshubovych (Igor Shubovych): this is interesting https://twitter.com/mankier/status/696792090315984896 2/9/2016, 2:08:20 PM - waldyrious (Waldir Pimenta): Interesting indeed :) 2/9/2016, 8:28:48 PM - igorshubovych (Igor Shubovych): hi, if you use NodeJS client, could you plz leave your feedback on See Also feature? https://github.com/tldr-pages/tldr-node-client/pull/81 2/20/2016, 2:10:30 AM - igorshubovych (Igor Shubovych): tldr-node-client 1.6.0 https://github.com/tldr-pages/tldr-node-client/releases/tag/v1.6.0 2/29/2016, 8:23:33 PM - ostera (Leandro Ostera): In case anyone's interested, I just updated `tldr.jsx` so it now supports specifying both the repo, the branch, and the platform of the page you want to render. So if you wanted to see for example how the `http.md` page would look in @jkbrzt's fork, in his `http` branch, you can go to: `https://ostera.github.io/tldr.jsx/?repo=jkbrzt/tldr&branch=http&platform=common#/http` 2/29/2016, 8:23:56 PM - ostera (Leandro Ostera): Keep in mind that you'd have to specify the platform because there would be no index available to map from the command name to the available platforms 3/2/2016, 6:34:47 PM - waldyrious (Waldir Pimenta): @ostera can the branch [revert-564-lsof_add_some_options_example](https://github.com/tldr-pages/tldr/compare/revert-564-lsof_add_some_options_example) be deleted, or does it need to get merged? 3/3/2016, 10:13:03 PM - ostera (Leandro Ostera): @waldyrious go ahead and delete it 3/4/2016, 1:47:43 AM - waldyrious (Waldir Pimenta): @ostera :+1: 12/24/2022, 5:03:41 PM - agnivade (Agniva De Sarker) joined the room 6/16/2016, 4:44:48 PM - agnivade (Agniva De Sarker): Hi guys, I have sent #909 a few days back. Comments/feedback is welcome. 6/21/2016, 3:46:46 AM - waldyrious (Waldir Pimenta): @agnivade it appeats that the maintainer team is somewhat swamped at the moment with other commitments (at least, I can speak for myself). Thanks for the PR, we will process it as soon as time is available :) 7/9/2016, 3:05:16 PM - ostera (Leandro Ostera): btw, @/all, would love your feedback on the new web client :) https://tldr.ostera.io/ 7/9/2016, 3:06:36 PM - felixonmars (Felix Yan): Looks nice :) 7/9/2016, 4:54:26 PM - waldyrious (Waldir Pimenta): looks great! Anything specific you'd like feedback on? 7/10/2016, 3:26:40 PM - rubenvereecken (Ruben Vereecken): @ostera that looks reaaally slick 7/11/2016, 10:49:04 AM - ostera (Leandro Ostera): @waldyrious not really, just general feedback or anything you may think is needed. I'm thinking smoothing out the transitions with some fast fades, and adding a night-mode 7/11/2016, 10:49:12 AM - ostera (Leandro Ostera): @rubenvereecken thanks 😃 7/18/2016, 1:32:24 PM - agnivade (Agniva De Sarker): @ostera - Looks nice. Would it be better to highlight the text contained in {{ }} ? Not just to maintain consistency with other clients, but also to give a better feel. 7/18/2016, 7:14:54 PM - waldyrious (Waldir Pimenta): Hey everyone! We've just broken past 8,000 stars! \o/ 7/18/2016, 7:43:44 PM - ostera (Leandro Ostera): woo! 7/18/2016, 10:09:23 PM - agnivade (Agniva De Sarker): wohoo ! 🎉 Waiting for 9000 ! (Then I can say its over 9000 😉 ) 7/19/2016, 12:36:16 AM - ostera (Leandro Ostera): Someone bookmark this: http://www.nerdist.com/wp-content/uploads/2015/02/OVER-9000-e1425115224556.jpg 8/6/2016, 7:27:30 PM - waldyrious (Waldir Pimenta): FYI: I just closed #465 (by merging its changes via #996 -- see that page for details on why this was needed), which was the oldest still open PR on the tldr-pages repository, and the only one from before 2016! Hurray 😃 🎉 8/21/2016, 8:10:59 PM - waldyrious (Waldir Pimenta): @ostera, as I’ve mentioned before (https://github.com/tldr-pages/tldr/issues/980#issuecomment-235387355), I think we need to adopt a semi-automatic progression path for occasional contributors > frequent contributors > maintainers 8/21/2016, 8:11:32 PM - ostera (Leandro Ostera): I agree on this ^ 8/21/2016, 8:12:08 PM - ostera (Leandro Ostera): IMO it’d be fairly easy to implement given the [contributors page](https://github.com/tldr-pages/tldr/contributors) 8/21/2016, 8:12:37 PM - waldyrious (Waldir Pimenta): but before that, I’d like to hear your thoughts on getting @agnivade the maintainer bit 8/21/2016, 8:13:23 PM - waldyrious (Waldir Pimenta): he’s been helping out quite a bit and I think the project is suffering from his lack of ability to merge PRs, given the relative unavailabity of the other maintainers 8/21/2016, 8:13:29 PM - ostera (Leandro Ostera): oh no, he’s no good. In fact I think we should remove all his commits with dad jokes from http://niceonedad.com/ 8/21/2016, 8:13:56 PM - waldyrious (Waldir Pimenta): hahahha 8/21/2016, 8:14:03 PM - waldyrious (Waldir Pimenta): I’m saving that one! 8/21/2016, 8:14:17 PM - ostera (Leandro Ostera): yeah, he’s got my vote 8/21/2016, 8:14:24 PM - ostera (Leandro Ostera): :+1: 8/21/2016, 8:15:09 PM - waldyrious (Waldir Pimenta): ok. I’ll give him commit rights for now, and if other maintainers don’t object for a while, we can add him to the org. sounds good? 8/21/2016, 8:15:48 PM - ostera (Leandro Ostera): also we should start pinging _teams_ instead of pinging all the individuals 8/21/2016, 8:16:28 PM - waldyrious (Waldir Pimenta): well, the best would actually to start using the mention bot he mentioned in #980, don’t you think? 8/21/2016, 8:17:23 PM - igorshubovych (Igor Shubovych): hi everybody, i was out of the project for several months due to personal issues. i think now i am back. what’s the Slack channel for? 8/21/2016, 8:17:28 PM - ostera (Leandro Ostera): true true, but until that happens, tagging @tldr-pages/content is overall better than tagging each one of us individually (better as in less to write, and less forgetion prone) 8/21/2016, 8:17:38 PM - waldyrious (Waldir Pimenta): Igor! welcome back 😃 8/21/2016, 8:17:45 PM - ostera (Leandro Ostera): @igorshubovych we were trying it out, I should comment that we didn’t like it that much for philosophical reasons 8/21/2016, 8:18:16 PM - igorshubovych (Igor Shubovych): Slack? 8/21/2016, 8:18:19 PM - waldyrious (Waldir Pimenta): yes, agreed @ostera 8/21/2016, 8:18:43 PM - ostera (Leandro Ostera): not Slack itself, it’s one wonderful tool, but it has a bigger entry-barrier than Gitter does 8/21/2016, 8:18:56 PM - igorshubovych (Igor Shubovych): ah, i see 8/21/2016, 8:19:03 PM - waldyrious (Waldir Pimenta): @igorshubovych we decided to make as much of the discussion surrounding the project in an open channel (gitter), to encourage participation 8/21/2016, 8:19:10 PM - waldyrious (Waldir Pimenta): and community ownership of the project 8/21/2016, 8:19:17 PM - igorshubovych (Igor Shubovych): yes, i saw that 8/21/2016, 8:19:27 PM - ostera (Leandro Ostera): ^ the more people see that things are moving, the more people will join to move things 8/21/2016, 8:19:41 PM - igorshubovych (Igor Shubovych): >> community ownership what do you mean by that? where can i read about it? 8/21/2016, 8:20:27 PM - ostera (Leandro Ostera): it’s the idea that anyone can submit a PR vs it being a private thing that we work on 8/21/2016, 8:20:55 PM - igorshubovych (Igor Shubovych): do you mean everybody can merge? 8/21/2016, 8:21:15 PM - waldyrious (Waldir Pimenta): sure, let me see if I can find a link, but overall it’s the notion that there should be a smooth transition between onlookers, occasional contributors, frequent contributors, and maintainers (on both directions), so we should remove barriers to participation wherever it’s reasonable and viable 8/21/2016, 8:22:16 PM - ostera (Leandro Ostera): no no 8/21/2016, 8:22:17 PM - waldyrious (Waldir Pimenta): not everyone willy-nilly. the idea is that there should be a clear (i.e. explicit in the CONTRIBUTING.md) definition of our criteria to add new maintainers 8/21/2016, 8:23:12 PM - ostera (Leandro Ostera): what @waldyrious said 8/21/2016, 8:23:21 PM - waldyrious (Waldir Pimenta): e.g. after x merged PRs (without major revisions by current reviewers), we will give commit rights to the repo, and after x+y commits over z months (or something like that, this is just an example) we’ll give org membership 8/21/2016, 8:23:49 PM - ostera (Leandro Ostera): so basically if you get 10 merged PR’s that have minor revisions, you become a contributor 8/21/2016, 8:24:01 PM - ostera (Leandro Ostera): and if you’ve been a contributor for a year, you become part of the organization 8/21/2016, 8:24:05 PM - igorshubovych (Igor Shubovych): oh, i see. it sounds like a good idea. 8/21/2016, 8:24:22 PM - igorshubovych (Igor Shubovych): so we are turning into Wikipedia... 8/21/2016, 8:24:23 PM - ostera (Leandro Ostera): (actual times are just out of my hat, we’d have to sit down and come up with a reasonable timeline) 8/21/2016, 8:24:32 PM - waldyrious (Waldir Pimenta): yeah, the goal is to make the project more resilient long-term considering that we all have periods of reduced availability 8/21/2016, 8:24:42 PM - waldyrious (Waldir Pimenta): or some people just move on to other projects, which is fine 8/21/2016, 8:24:43 PM - ostera (Leandro Ostera): hey don’t look at me, I’m just an evil product engineer that wants to track what people do 8/21/2016, 8:25:06 PM - waldyrious (Waldir Pimenta): wikipedia is a good model if you ask me 😛 8/21/2016, 8:28:13 PM - waldyrious (Waldir Pimenta): ok so I have other commitments today, but my suggestion is that in from now on we use this channel for deciding the overal goals for the project, and coordinate progress on them 8/21/2016, 8:28:36 PM - igorshubovych (Igor Shubovych): ok. transparency ftw 8/21/2016, 8:28:42 PM - waldyrious (Waldir Pimenta): yeah 😃 8/21/2016, 8:29:06 PM - waldyrious (Waldir Pimenta): e.g. collecting commands that people are searching for but not covered yet, creating a comprehensive list of commands to cover (and divide them into milestones), etc. 8/21/2016, 8:29:26 PM - waldyrious (Waldir Pimenta): and of course, decimating the PR backlog!! 8/21/2016, 8:29:51 PM - ostera (Leandro Ostera): yeah, ping me with your email addresses so I can add you to the mixpanel project were the anonyomous data from the webclient usage is being collected :) 8/21/2016, 8:30:32 PM - igorshubovych (Igor Shubovych): add me igor dot shubovych at gmail 8/21/2016, 8:32:16 PM - ostera (Leandro Ostera): the data right now is a bit noisy, but we’re tracking all searches (found and not found), and the entries are structured by Command name and Platform, so some nice things could be done with it 8/21/2016, 8:32:45 PM - ostera (Leandro Ostera): (think filtering out all not found entries against a list of unix commands, to get both unix commands that we’d have to add, and non-unix commands that people are looking for) 8/22/2016, 9:14:18 AM - agnivade (Agniva De Sarker): thanks @/all for giving me the commit bit ! Appreciate the gesture 😄 8/22/2016, 9:14:41 AM - waldyrious (Waldir Pimenta): oh hi there! 8/22/2016, 9:15:05 AM - waldyrious (Waldir Pimenta): looks like I finally managed to find you online at reasonable times for you 😛 8/22/2016, 9:17:05 AM - agnivade (Agniva De Sarker): haha 8/22/2016, 9:19:44 AM - waldyrious (Waldir Pimenta): if you want to put the commit bit to test, the pod.md page is a good candidate 😉 8/22/2016, 9:20:34 AM - agnivade (Agniva De Sarker): Ah yes ! Lets give it a shot .. 8/22/2016, 9:22:31 AM - agnivade (Agniva De Sarker): Do I create a merge commit or "squash and merge" ? 8/22/2016, 9:23:40 AM - waldyrious (Waldir Pimenta): just a sec 8/22/2016, 9:25:24 AM - waldyrious (Waldir Pimenta): https://github.com/tldr-pages/tldr/pull/998#issuecomment-241259139 8/22/2016, 9:25:36 AM - waldyrious (Waldir Pimenta): (this should also be placed in our guidelines) 8/22/2016, 9:26:25 AM - waldyrious (Waldir Pimenta): essentially: atomic, well-described commits —> merge; lots of “update page.md” commits —> squash 8/22/2016, 9:26:59 AM - waldyrious (Waldir Pimenta): it’s particularly important not to squash PRs with multiple commit authors 8/22/2016, 9:27:24 AM - agnivade (Agniva De Sarker): got it. makes sense 8/22/2016, 9:27:33 AM - waldyrious (Waldir Pimenta): :+1: 8/22/2016, 9:31:21 AM - agnivade (Agniva De Sarker): It would be perfect if simman's commits were squashed, and yours left as is, in this PR. 8/22/2016, 9:31:43 AM - waldyrious (Waldir Pimenta): you can do that now 😉 8/22/2016, 9:31:59 AM - waldyrious (Waldir Pimenta): it takes a little extra work, so it’s a balance that’s up to you 8/22/2016, 9:32:27 AM - agnivade (Agniva De Sarker): ooo .. can I squash individual commits ? from the UI itself ? 8/22/2016, 9:32:35 AM - waldyrious (Waldir Pimenta): oh, unfortunately no 8/22/2016, 9:32:42 AM - waldyrious (Waldir Pimenta): not yet at least 8/22/2016, 9:33:01 AM - agnivade (Agniva De Sarker): haha .. ok then. yea I know it can be done from command line. 8/22/2016, 9:33:18 AM - waldyrious (Waldir Pimenta): but that PR was created from a branch that actually lives in the tldr-pages repo (rather than at simman’s fork) 8/22/2016, 9:33:44 AM - waldyrious (Waldir Pimenta): so you can edit it directly (otherwise you’d have to create a separate branch and PR) 8/22/2016, 9:34:20 AM - agnivade (Agniva De Sarker): yep. 8/22/2016, 9:35:25 AM - waldyrious (Waldir Pimenta): the rule of thumb is, you’re free to tweak the git history if you’re up to it, unless you’re creating a mess in the git graph (e.g. a nasty merge commit) or if your changes would destroy information (e.g. squash commits that were properly atomic, remove an author from the merged commit(s), etc.) 8/22/2016, 9:43:52 AM - agnivade (Agniva De Sarker): ahh shucks .. my repo references need to be changed. Since I was sending PRs from my forked repo. My "origin" points to my repo, and "upstream" points to the main repo. I'll just merge this for now. Need to fix my repo references. 8/22/2016, 9:46:21 AM - waldyrious (Waldir Pimenta): yeah xD 8/25/2016, 3:53:53 PM - agnivade (Agniva De Sarker): Hey @waldyrious, should I then close #893 and then send a new PR from its ref ? Or wait a few more days for the author to respond ? 8/28/2016, 3:58:10 AM - waldyrious (Waldir Pimenta): I’d rather we only close the original PR once the new one is merged, but yeah, do grab the reference and create a new branch and PR with your proposed changes :) 9/2/2016, 12:52:20 PM - agnivade (Agniva De Sarker): Hey @/all , what are we planning to do about #822 and #799 ? Those are the last ones that seem to be in a zombie state. 9/2/2016, 2:44:44 PM - waldyrious (Waldir Pimenta): For #822 I suggest we close that PR and create a new PR (or issue) to add specific examples to demonstrate how the crontab format works. 9/2/2016, 2:46:53 PM - waldyrious (Waldir Pimenta): For #799 we’d need to sit down and look at the issues @igorshubovych linked (or maybe he could summarize what he wanted to point out from them?). 9/2/2016, 2:46:56 PM - waldyrious (Waldir Pimenta): We could find a time to meet here and discuss it, or if someone’s up to it, they can do the research themselves and make a summary of needed changes. 9/3/2016, 12:44:51 PM - agnivade (Agniva De Sarker): taking up #822 then. Will send a new PR. I will use concrete examples, probably a couple and try to mix in @ostera 's style. 9/3/2016, 4:28:26 PM - waldyrious (Waldir Pimenta): :+1: :+1: 😃 9/3/2016, 5:40:08 PM - waldyrious (Waldir Pimenta): @/all : as you can probably see from the sidebar on the right, I’ve been working for the past few days in labeling all issues and PRs appropriately. 9/3/2016, 5:40:15 PM - waldyrious (Waldir Pimenta): I renamed some labels, and have already categorized all open issues / PRs, and made some headway with closed PRs. 9/3/2016, 5:40:21 PM - waldyrious (Waldir Pimenta): Right now there are less than 500 unlabeled closed PRs: https://github.com/tldr-pages/tldr/pulls?q=is%3Apr+no%3Alabel+is%3Aclosed 9/3/2016, 5:42:29 PM - waldyrious (Waldir Pimenta): I’ll keep working on that as time permits. Once this is done we’ll be able to get some statistics regarding the growth of the project in terms of new pages created over time, number of edits per page, discussion length per type of PR, mean time for implementing a command request issue, and so on. 9/3/2016, 5:42:47 PM - waldyrious (Waldir Pimenta): I’m sure this’ll be right up @ostera’s alley 😉 9/3/2016, 7:47:16 PM - agnivade (Agniva De Sarker): ah, so that was your intention all along. I was wondering, what were you doing labelling closed PRs. anyways, good work :+1: 9/4/2016, 4:12:22 PM - waldyrious (Waldir Pimenta): @agnivade well, part of the motivation was also just to tidy up the repo, since the labeling has been quite inconsistent so far. 9/4/2016, 4:14:52 PM - waldyrious (Waldir Pimenta): and a nice consequence is that I already came across past discussions that needed a note added, either to connect them together for future reference and to allow following the chain of events, or to follow-up discussions that hadn't been completely resolved (e.g. #1036) 9/8/2016, 1:53:58 PM - waldyrious (Waldir Pimenta): Hey @/all, heads-up: I reactivated LGTM.co integration to provide an explicit check for two thumbs-up on all PRs. This may cause some disruption, so stay tuned and please report if you see anything strange. 9/8/2016, 2:00:43 PM - agnivade (Agniva De Sarker): why was it deactivated then ? 9/8/2016, 2:20:58 PM - waldyrious (Waldir Pimenta): I believe it was causing some issues with PRs, but I can’t tell for sure because at the time I wasn’t a member of the org 9/8/2016, 2:21:31 PM - waldyrious (Waldir Pimenta): I suspect some of the issues were related to another check that was activated around that time, to force all branches to be based off the latest master 9/8/2016, 2:21:39 PM - waldyrious (Waldir Pimenta): this caused all sorts of conflicts 9/8/2016, 2:21:59 PM - agnivade (Agniva De Sarker): okk 9/8/2016, 2:22:01 PM - waldyrious (Waldir Pimenta): so I intent to confirm whether lgtm works on its own now that that check is disabled 9/8/2016, 2:48:08 PM - waldyrious (Waldir Pimenta): (so far it seems to be working well. current open PRs show the missing check of 2 LGTMs) 9/9/2016, 12:59:58 PM - waldyrious (Waldir Pimenta): ok, something weird is going on. In https://github.com/tldr-pages/tldr/pull/1041 for example none of the status checks are working 9/9/2016, 1:01:47 PM - agnivade (Agniva De Sarker): Yep, was just going to ping you. 9/9/2016, 1:02:01 PM - agnivade (Agniva De Sarker): Is there a place we can check the logs ? 9/9/2016, 1:02:04 PM - waldyrious (Waldir Pimenta): The org audit log shows this: > waldyrious – hook.create > Installed webhook for tldr-pages/tldr with issue_comment events > United States 23 hours ago > waldyrious – required_status_check.create > The status approvals/lgtm was marked as required for the branch master on tldr-pages/tldr > United States 23 hours ago > waldyrious – required_status_check.destroy > The status continuous-integration/travis-ci was marked as no longer being required for the branch master on tldr-pages/tldr > United States 23 hours ago 9/9/2016, 1:02:27 PM - waldyrious (Waldir Pimenta): I’m afraid only org members can see it: https://github.com/organizations/tldr-pages/settings/audit-log 9/9/2016, 1:03:50 PM - agnivade (Agniva De Sarker): that's fine. hmm very cyptic logs 9/9/2016, 1:04:31 PM - waldyrious (Waldir Pimenta): those entries appear as coming from the United States, instead as from Portugal, as most of the other actions performed by me appear there. I’m not sure if that’s relevant; I assume it may have to do with some of the actions being happening via the github infrastructure 9/9/2016, 1:05:25 PM - waldyrious (Waldir Pimenta): Apart from that, the first two entries are fine — I indeed installed and activated the lgtm hook, as I mentioned here before 9/9/2016, 1:05:55 PM - waldyrious (Waldir Pimenta): but I don’t recall disabling the travis check. it may have been a byproduct of those actions, somehow… in any case I re-enabled them 9/9/2016, 1:06:11 PM - agnivade (Agniva De Sarker): exactly .. weird stuff .. 9/9/2016, 1:06:16 PM - waldyrious (Waldir Pimenta): but what I’m actually thinking could be the culprit is this later entry: 9/9/2016, 1:06:38 PM - waldyrious (Waldir Pimenta): > waldyrious – org.enable_oauth_app_restrictions > Enabled third-party application access restrictions for the tldr pages organization > Portugal 9 hours ago 9/9/2016, 1:07:44 PM - waldyrious (Waldir Pimenta): I did that based on this: https://help.github.com/articles/approving-third-party-applications-for-your-organization/ 9/9/2016, 1:08:05 PM - waldyrious (Waldir Pimenta): further documentation: https://help.github.com/articles/about-third-party-application-restrictions/ 9/9/2016, 1:09:00 PM - waldyrious (Waldir Pimenta): seems to be a recent security feature, where third-party apps need to be explicitly whitelisted within the org, rather than just been given permission by one of the org members 9/9/2016, 1:10:35 PM - waldyrious (Waldir Pimenta): I’m going to see if I can manually add lgtm and travis to the whitelist, from here: https://github.com/integrations 9/9/2016, 1:11:16 PM - agnivade (Agniva De Sarker): okl 9/9/2016, 1:11:53 PM - waldyrious (Waldir Pimenta): hmm, pretty sure that must have been it. They now appear in the whitelist in https://github.com/organizations/tldr-pages/settings/oauth_application_policy 9/9/2016, 1:14:04 PM - agnivade (Agniva De Sarker): So will it re-trigger the jobs now ? #1041 still shows waiting .. 9/9/2016, 1:14:39 PM - waldyrious (Waldir Pimenta): my thoughts exactly. I don’t think that happens automatically. 9/9/2016, 1:14:48 PM - waldyrious (Waldir Pimenta): let me try adding a new lgtm comment 9/9/2016, 1:15:33 PM - waldyrious (Waldir Pimenta): yup, that was it :) 9/9/2016, 1:15:50 PM - waldyrious (Waldir Pimenta): now I’ll manually restart travis, since they provide that option 9/9/2016, 1:17:42 PM - waldyrious (Waldir Pimenta): hm. apparently the restart button only appears for failed builds… I don’t see anything in https://travis-ci.org/tldr-pages/tldr/builds/158642280 9/9/2016, 1:20:59 PM - waldyrious (Waldir Pimenta): @agnivade try squashing the last commit into the previous one? 9/9/2016, 1:21:54 PM - agnivade (Agniva De Sarker): will do 9/9/2016, 1:23:31 PM - agnivade (Agniva De Sarker): done 9/9/2016, 1:26:26 PM - waldyrious (Waldir Pimenta): that worked, but now @ostera’s LGTM isn’t counted xD 9/9/2016, 1:26:38 PM - waldyrious (Waldir Pimenta): try lgtm-ing yourself, let’s see what happens 9/9/2016, 1:26:49 PM - waldyrious (Waldir Pimenta): (just comment a thumbs-up) 9/9/2016, 1:34:31 PM - waldyrious (Waldir Pimenta): ok, great, that PR seems to have been the only one affected by this. thanks for the help in cleaning up my mess xD 9/9/2016, 1:35:00 PM - agnivade (Agniva De Sarker): anytime dude ! 9/10/2016, 1:14:41 AM - waldyrious (Waldir Pimenta): @/all I decided to read up a bit on CLAs and try out a simple one for our project. Please check the text of the agreement at https://www.clahub.com/agreements/tldr-pages/tldr and let me know what you think in this PR discussion: #1048 9/10/2016, 1:19:53 AM - waldyrious (Waldir Pimenta): I created integrations using both clahub and cla-assistant, to test out the process and decide which one to use. I think I'll go with CLA-assistant, for various reasons: (1) it not only updates the PR status but also comments when contributors have signed, giving extra visibility to the process; (2) It maintains the text of the CLA in a public gist, so that could be a better way to handle eventual changes and improve transparency overall; (3) it allows contributors to sign tha CLA by simply logging in to their github account, while clahub requires the user to fill their info in a form. 9/10/2016, 11:05:12 AM - agnivade (Agniva De Sarker): Hey @waldyrious , this https://www.clahub.com/agreements/tldr-pages/tldr says the page does not exist. Whats up with that ? 9/10/2016, 11:09:21 AM - agnivade (Agniva De Sarker): ah has it changed to https://cla-assistant.io/tldr-pages/tldr now ? 9/10/2016, 12:15:27 PM - waldyrious (Waldir Pimenta): yes, I tried to edit my message but it had already timed out for editing 😛 9/10/2016, 12:16:08 PM - waldyrious (Waldir Pimenta): I changed to cla-assistant for the reasons outlined above, so the url of the agreement also changed. But the text is the same :) 9/10/2016, 5:07:41 PM - agnivade (Agniva De Sarker): @waldyrious - Noticed a slight problem with the lgtm bot. Here in this comment -https://github.com/tldr-pages/tldr/pull/1048#issuecomment-246106979, you gave a +1 but in a different context, but the tldr bot picked it up as a LGTM. 9/10/2016, 5:07:59 PM - agnivade (Agniva De Sarker): I guess this problem will always be there any way we implement it. Any thoughts on this ? 9/10/2016, 5:44:34 PM - waldyrious (Waldir Pimenta): the patterns that define a valid LGTM are defined by us in the .lgtm file, so we can tweak it to ensure no false-positives are caught :) 9/10/2016, 8:46:05 PM - agnivade (Agniva De Sarker): yea I know that .. but I mean if you specify "The PR looks good to me", it becomes too cumbersome. Just saying LGTM should be good, but it means differently in different contexts. 9/10/2016, 8:46:33 PM - agnivade (Agniva De Sarker): Can we tweak the .lgtm file to look for "only" that word as a comment, and nothing else ? 9/10/2016, 8:55:08 PM - agnivade (Agniva De Sarker): ah yes .. indeed we can. 😄 will send a PR for it then. 9/10/2016, 8:55:40 PM - waldyrious (Waldir Pimenta): :+1: 😃 9/15/2016, 7:07:55 PM - ostera (Leandro Ostera): what about `LGTM!` 9/15/2016, 7:08:05 PM - ostera (Leandro Ostera): D: 9/15/2016, 7:08:41 PM - waldyrious (Waldir Pimenta): Actually, we’re likely to get rid of LGTM altogether, since github has now implemented a native PR approval system 9/15/2016, 7:09:27 PM - waldyrious (Waldir Pimenta): I’ve tried it in a smaller repo, and it seems to work well :) the only problem is that it shows a scary red warning saying that the PR can’t be merged, but that will probably be changed soon 9/15/2016, 7:11:24 PM - waldyrious (Waldir Pimenta): https://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-forums-and-features 9/15/2016, 7:11:32 PM - ostera (Leandro Ostera): I’ve been trying the projects out 9/15/2016, 7:11:39 PM - ostera (Leandro Ostera): it’s basically a kanban board 9/15/2016, 7:11:43 PM - waldyrious (Waldir Pimenta): nice, I’m curious about that 9/15/2016, 7:11:51 PM - ostera (Leandro Ostera): there’s no relation between milestones thou 9/15/2016, 7:11:53 PM - waldyrious (Waldir Pimenta): how does it relate to the issues, milestones, etc? 9/15/2016, 7:11:55 PM - waldyrious (Waldir Pimenta): ah 😟 9/15/2016, 7:15:59 PM - ostera (Leandro Ostera): so you can create your own columsn in the board 9/15/2016, 7:16:11 PM - ostera (Leandro Ostera): and assign issues to columns 9/15/2016, 7:16:35 PM - ostera (Leandro Ostera): but it’s all very manual still 9/15/2016, 7:18:41 PM - waldyrious (Waldir Pimenta): hmmm 9/15/2016, 7:19:05 PM - ostera (Leandro Ostera): I don’t think we need it 9/15/2016, 7:19:11 PM - waldyrious (Waldir Pimenta): can we at least filter by milestone? 9/15/2016, 7:19:13 PM - ostera (Leandro Ostera): nope 9/15/2016, 7:19:23 PM - ostera (Leandro Ostera): you can add cards from a given milestone only 9/15/2016, 7:19:31 PM - ostera (Leandro Ostera): but you can’t filter yet by milestone 9/15/2016, 7:19:46 PM - ostera (Leandro Ostera): actually a bit disappointed at this very basic use cases not being considered xD 9/15/2016, 7:19:58 PM - waldyrious (Waldir Pimenta): so we could do like one project per milestone, or something like that? 9/15/2016, 7:20:13 PM - waldyrious (Waldir Pimenta): yeah, well, they seem to have pushed a lot of new stuff out at the same time 9/15/2016, 7:20:17 PM - ostera (Leandro Ostera): yup 9/15/2016, 7:20:20 PM - waldyrious (Waldir Pimenta): it’ll take some time to settle 9/15/2016, 7:20:24 PM - ostera (Leandro Ostera): exactly 9/15/2016, 7:20:29 PM - waldyrious (Waldir Pimenta): the review feature seems to work well, at least 9/15/2016, 7:20:34 PM - ostera (Leandro Ostera): yeah, I liked that one a lot 9/15/2016, 7:20:40 PM - waldyrious (Waldir Pimenta): apart from the scary red warning, that was really over the top 9/15/2016, 7:20:48 PM - ostera (Leandro Ostera): haven’t seen that one 9/15/2016, 7:20:49 PM - ostera (Leandro Ostera): link? 9/15/2016, 7:21:35 PM - ostera (Leandro Ostera): ah, actually you can assign tickets to different projects 9/15/2016, 7:21:58 PM - ostera (Leandro Ostera): so maybe projects aren’t supposed to englobe milestones, but are a way of tracking the state of given issues/pr’s that are related to the same goal 9/15/2016, 7:22:35 PM - waldyrious (Waldir Pimenta): yeah, but what kind of goal? 9/15/2016, 7:23:01 PM - waldyrious (Waldir Pimenta): I think you can add issues to multiple milestones too, but I may be wrong 9/15/2016, 7:30:57 PM - waldyrious (Waldir Pimenta): turns out you can't 9/15/2016, 7:31:02 PM - waldyrious (Waldir Pimenta): so yeah, that could be useful 9/15/2016, 7:31:43 PM - waldyrious (Waldir Pimenta): I was thinking about using milestones to track progress in coverage parity with various lists of commands 9/15/2016, 7:31:48 PM - waldyrious (Waldir Pimenta): and those would overlap 9/15/2016, 7:32:00 PM - waldyrious (Waldir Pimenta): so it seems the only way to do it would be with projects, indeed 9/15/2016, 7:32:10 PM - waldyrious (Waldir Pimenta): but let’s wait and see how this stuff evolves 9/15/2016, 9:35:13 PM - agnivade (Agniva De Sarker): The PR review system looks really good. I'm okay with the red button .. 😄 9/15/2016, 9:35:28 PM - agnivade (Agniva De Sarker): lets wait for a few more days and see what else they ship .. 9/15/2016, 9:35:28 PM - waldyrious (Waldir Pimenta): we can’t edit the comments though 😟 9/15/2016, 9:35:47 PM - agnivade (Agniva De Sarker): yea .. seems like it 9/15/2016, 9:36:35 PM - waldyrious (Waldir Pimenta): We can use it but I wouldn’t set it as required, nor I’d replace LGTM.co with it for now 9/15/2016, 9:36:39 PM - waldyrious (Waldir Pimenta): maybe later on 9/15/2016, 9:37:20 PM - agnivade (Agniva De Sarker): I read that for required reviews, it needs just one "okay" from a maintainer, to allow it to be merged. 9/15/2016, 9:37:25 PM - agnivade (Agniva De Sarker): Can that policy be modified ? 9/15/2016, 9:37:50 PM - waldyrious (Waldir Pimenta): Let me check 9/15/2016, 9:38:38 PM - waldyrious (Waldir Pimenta): I don’t see any setting to configure that.. 9/15/2016, 9:39:22 PM - agnivade (Agniva De Sarker): I see.. that's bad. What if some repo needs 2 or 3 required reviews for a merge .. 9/15/2016, 9:39:59 PM - waldyrious (Waldir Pimenta): Hopefully they’ll listen to the community (those who still bother to communicate feature requests with them) 9/15/2016, 9:41:58 PM - agnivade (Agniva De Sarker): whoa .. my profile page looks like an FB feed now .. 😟 9/15/2016, 9:42:15 PM - waldyrious (Waldir Pimenta): yeah, they did a whole bunch of changes 9/15/2016, 9:42:35 PM - waldyrious (Waldir Pimenta): not sure it was a good idea -_- 9/15/2016, 9:44:21 PM - agnivade (Agniva De Sarker): its all coming from some PM roadmap I'm sure. Technically, I don't see any benefit. They just want to convert this into a social network for coders .. Highlighting your PRs .. and all. 9/15/2016, 9:45:09 PM - agnivade (Agniva De Sarker): next, they'll probably show "This PR of yours received 30 likes !" .. 9/15/2016, 9:45:32 PM - agnivade (Agniva De Sarker): that'll be the day I quit github .. 😆 9/15/2016, 9:46:39 PM - waldyrious (Waldir Pimenta): Hahaha 9/15/2016, 9:46:57 PM - waldyrious (Waldir Pimenta): well, gitlab is certainly looking good release after release 😉 9/15/2016, 9:47:50 PM - waldyrious (Waldir Pimenta): they’re actually dogfooding the product in its own development, so they’re improving lots of functionality that developers actually *need* 9/15/2016, 9:48:39 PM - agnivade (Agniva De Sarker): ah that's nice 9/16/2016, 10:49:23 AM - ostera (Leandro Ostera): @waldyrious I’d have thought they’d take the Milestones and add _kanban_ish boards _to them_. That way you don’t have to add new projects, and get the same thing for free. 9/16/2016, 12:38:48 PM - waldyrious (Waldir Pimenta): my thoughts exactly 9/16/2016, 12:40:51 PM - waldyrious (Waldir Pimenta): they might have thouht most poeple use milestones as preparation for sequential releases, and therefore exclusive to each other; but offering more functionality would harm no one, since those who don’t need it simply can avoid adding issues to multiple milestones 9/16/2016, 12:41:42 PM - waldyrious (Waldir Pimenta): right now, they just add more complexity and noise to the available project management tools than would be necessary IMO 9/16/2016, 4:44:33 PM - waldyrious (Waldir Pimenta): Well, what the hell. I decided to start using the projects to make some of my personal todo (and in-progress) items more visible: https://github.com/tldr-pages/tldr/projects/1 9/16/2016, 5:00:51 PM - waldyrious (Waldir Pimenta): @ostera, @agnivade: https://github.com/tldr-pages/tldr/projects/2 9/16/2016, 5:04:55 PM - agnivade (Agniva De Sarker): yep saw it. 9/16/2016, 5:05:17 PM - waldyrious (Waldir Pimenta): Any thoughts? 9/16/2016, 5:09:37 PM - agnivade (Agniva De Sarker): Our current general todo item , based on our last discussion was to crunch through the backlog PRs. So are we planning to tackle the page hierarchy next ? 9/16/2016, 5:10:08 PM - agnivade (Agniva De Sarker): There are other old unanswered issues too, regarding clients and stuff .. 9/16/2016, 5:10:31 PM - waldyrious (Waldir Pimenta): No, I’m precisely taking advantage of the non-sequential nature of “projects” as opposed to milestones 9/16/2016, 5:11:29 PM - agnivade (Agniva De Sarker): I see .. so you are basically grouping issues into projects so that a roadmap sort of thing is created. 9/16/2016, 5:11:41 PM - waldyrious (Waldir Pimenta): this way we can organize related issues and identify missing steps for a given goal to be achieved, but that doesn’t mean we have to tackle one project before the other, nor it means that once we start a project we can’t work on others as well 9/16/2016, 5:11:59 PM - agnivade (Agniva De Sarker): got it. 9/16/2016, 5:12:04 PM - waldyrious (Waldir Pimenta): yeah, with the difference that it’s a parallel roadmap rather than a sequential one 9/16/2016, 5:12:17 PM - waldyrious (Waldir Pimenta): sequence will make sense inside the projects, but even there it’s not mandatory 9/16/2016, 5:13:26 PM - agnivade (Agniva De Sarker): I think following sequence is a little necessary, once we prioritize things inside a project. No sense jumping around tasks, once we have decided on a clear course of action. 9/16/2016, 5:13:27 PM - waldyrious (Waldir Pimenta): The “General” project, by the way, can be changed to something that makes more sense as a cohesive goal, and unrelated notes/issues currently there moved to another project 9/16/2016, 5:14:45 PM - waldyrious (Waldir Pimenta): Sure, I just meant that we have the flexibility to do so. A project doesn’t lock us down to its tasks — we are the ones who may agree (by consensus rather than technical rules) to work on specific projects before others 9/16/2016, 5:14:49 PM - waldyrious (Waldir Pimenta): makes sense? 9/16/2016, 5:16:15 PM - agnivade (Agniva De Sarker): yep 9/16/2016, 5:16:22 PM - waldyrious (Waldir Pimenta): (I’m talking specifically about not following a predefined sequence *among* projects, not *within* them. Inside them of course we should follow the order defined in the columns, unless there’s no cross-dependencies) 9/16/2016, 9:25:31 PM - waldyrious (Waldir Pimenta): update: all PRs from 2015 onwards have been labeled! phew! 9/16/2016, 9:25:39 PM - waldyrious (Waldir Pimenta): 👉 9/16/2016, 9:26:40 PM - waldyrious (Waldir Pimenta): now onto the older ones :) 9/16/2016, 9:31:35 PM - agnivade (Agniva De Sarker): whoa boy !! 9/16/2016, 9:31:58 PM - agnivade (Agniva De Sarker): 👏 9/16/2016, 9:32:21 PM - waldyrious (Waldir Pimenta): the late 2015 / early 2016 hump was tough to get over 😛 https://github.com/tldr-pages/tldr/graphs/contributors 9/16/2016, 9:33:05 PM - agnivade (Agniva De Sarker): hehe 9/17/2016, 4:27:33 PM - ostera (Leandro Ostera): just fyi, I thought `architecture` was used as a label for the internal architecture of the data 9/17/2016, 4:28:02 PM - ostera (Leandro Ostera): as in, how we structure the pages, and how we deal with redundant data on pages between platforms, and the page spec, and so on and so on 9/17/2016, 4:28:22 PM - ostera (Leandro Ostera): so I made the label `tooling` to deal specifically with the tools we build _around_ the project to make it easier to deal with 9/17/2016, 4:33:46 PM - agnivade (Agniva De Sarker): Hey @waldyrious , just wanted to check - what's pending on #1048 from being merged ? Are we waiting on more people to comment ? It looks like some people had minor queries which have been clarified and there are no strong oppositions against it. 9/17/2016, 4:37:14 PM - waldyrious (Waldir Pimenta): (I’m around but currently formatting a list of links to add to #1070 — I’ll read and reply asap) 9/17/2016, 4:37:57 PM - ostera (Leandro Ostera): @waldyrious I just left a comment for you there, 9/17/2016, 4:44:12 PM - waldyrious (Waldir Pimenta): @ostera yeah, I added a note to the issue management project (https://github.com/tldr-pages/tldr/projects/1) about relabeling all architecture issues/PRs to more specific stuff. PTAL 9/17/2016, 4:45:19 PM - waldyrious (Waldir Pimenta): I wanted the people who added the questions to confirm that the explanations were satisfactory to them. Especially @notpeter since he’s been such a prolific contributor 9/17/2016, 4:45:42 PM - waldyrious (Waldir Pimenta): I should probably ask them explicitly to comment 9/17/2016, 4:46:32 PM - waldyrious (Waldir Pimenta): (anybody else having trouble loading pages from github.com?) 9/17/2016, 4:46:56 PM - ostera (Leandro Ostera): as in through their API or their website? 9/17/2016, 4:46:58 PM - ostera (Leandro Ostera): API: https://tldr.ostera.io/man works fine 9/17/2016, 4:47:05 PM - ostera (Leandro Ostera): Website: a bit slow 9/17/2016, 4:47:08 PM - waldyrious (Waldir Pimenta): the actual github website 9/17/2016, 4:47:24 PM - waldyrious (Waldir Pimenta): it’s completely stalled for me, bit not erroring out 9/17/2016, 4:47:42 PM - waldyrious (Waldir Pimenta): ah ok it’s back to normal now 9/17/2016, 4:48:29 PM - ostera (Leandro Ostera): auto-scaling in action! 9/17/2016, 4:48:41 PM - waldyrious (Waldir Pimenta): :) 9/17/2016, 4:51:39 PM - ostera (Leandro Ostera): quick question: could we get rid of the wiki? By adding a `CLIENTS.md` for the list of clients, and a generated list of commands as issues for the `Pages-plan` page, we can work just fine. 9/17/2016, 4:52:07 PM - waldyrious (Waldir Pimenta): sure thing. I was always against having two lists for the clients 9/17/2016, 4:53:15 PM - waldyrious (Waldir Pimenta): btw the list of links in the pages-plan page is now subsumed by #1070 since I integrated them into the comment I left in the issue 9/17/2016, 4:53:28 PM - ostera (Leandro Ostera): brilliant 9/17/2016, 4:53:42 PM - waldyrious (Waldir Pimenta): (not the commands themselves) 9/17/2016, 4:54:02 PM - ostera (Leandro Ostera): Yeah, I think that we shouldn’t keep a list of commands but instead have issues opened for them 9/17/2016, 4:55:02 PM - ostera (Leandro Ostera): that way we can leverage all of GitHub’s issues filtering/sorting/assigning/labeling, plus projects and milestones 9/17/2016, 4:55:37 PM - waldyrious (Waldir Pimenta): fully agreed 9/17/2016, 4:57:07 PM - ostera (Leandro Ostera): one extra step from there would be integrate into the clients that list of open commands, and selectively say _“hey, this command isn’t here, come open an issue for it”_ or _”hey, this command has an open issue, feel free to chime in or submit a PR for it ”_ 9/17/2016, 5:01:04 PM - ostera (Leandro Ostera): ultimately what I’d like is that _submit a PR for it_ link to take me to an online, side-by-side markdown editor where I can see the tldr-command template on the left, and the documentation for the command on the right (if it’s within our list of known documentation sources like linux.die.net/man), modify everything inline, and submit it – an insanely smooth contributing experience 9/17/2016, 5:02:49 PM - waldyrious (Waldir Pimenta): great idea. I just don’t think that integrating a list of missing commands into the clients is necessary for that to work 9/17/2016, 5:03:05 PM - ostera (Leandro Ostera): actually you’re right 9/17/2016, 5:03:14 PM - ostera (Leandro Ostera): it doesn’t need to be there if it’s web-based 9/17/2016, 5:03:57 PM - waldyrious (Waldir Pimenta): no, not even that. it doesn’t need to check if the command exists in some sanctioned list 9/17/2016, 5:04:21 PM - ostera (Leandro Ostera): clarification: what I meant by list of missing commands is whether or not _we have an issue opened for it already_ 9/17/2016, 5:04:39 PM - waldyrious (Waldir Pimenta): ok, that makes sense, indeed 9/17/2016, 5:04:49 PM - waldyrious (Waldir Pimenta): neither issues nor PRs 9/17/2016, 5:04:58 PM - ostera (Leandro Ostera): exactly 9/17/2016, 5:05:07 PM - waldyrious (Waldir Pimenta): otherwise we could point people to it to add their input :) 9/17/2016, 5:05:16 PM - waldyrious (Waldir Pimenta): this would be really really nice 9/17/2016, 5:05:19 PM - waldyrious (Waldir Pimenta): UX-wise 9/17/2016, 5:05:35 PM - waldyrious (Waldir Pimenta): coupled with the “new page wizard" 9/17/2016, 5:05:48 PM - waldyrious (Waldir Pimenta): let’s add two issues for each of these 9/17/2016, 5:05:53 PM - ostera (Leandro Ostera): on it 9/17/2016, 5:06:05 PM - waldyrious (Waldir Pimenta): ok, I’ll leave that to you :) 9/17/2016, 5:06:17 PM - waldyrious (Waldir Pimenta): I’ll work on #1039 9/17/2016, 5:28:28 PM - waldyrious (Waldir Pimenta): I left a few comments there. It’s quite tricky. Let me know what you guys think. 9/17/2016, 5:29:16 PM - waldyrious (Waldir Pimenta): Gotta leave for now. I’m really happy with the direction things are progressing btw. ttyl! 9/17/2016, 6:32:24 PM - ostera (Leandro Ostera): @/all https://github.com/tldr-pages/tldr/issues/1073 9/17/2016, 6:41:27 PM - waldyrious (Waldir Pimenta): I’ve started reading it. made a minor grammar fix. so far I love the concept! Will comment once I’m done :) 9/17/2016, 6:50:55 PM - waldyrious (Waldir Pimenta): gotta leave, sorry, but will comment later. Awesome proposal! 9/17/2016, 7:00:23 PM - agnivade (Agniva De Sarker): Love #1073 ! Great idea. This is a perfect fit for a web client. 9/17/2016, 7:03:16 PM - agnivade (Agniva De Sarker): We can totally get rid of `Clients` wiki page. No sense having 2 sources of data. The `Pages-plan` page can also be removed. It requires manual work in keeping it up to date. 9/17/2016, 9:06:30 PM - agnivade (Agniva De Sarker): Hey @felixonmars , it seems you have an automated hook to assign PRs to people who refer to it. I'm not sure if that makes sense. For eg- my PR #1074 closes #943. Hence I referred to it from #1074 . But that should not mean I own #943. 12/24/2022, 5:05:29 PM - Parth (Parth) joined the room 9/17/2016, 10:14:44 PM - Parth (Parth): Hey guys! 9/17/2016, 10:14:53 PM - Parth (Parth): A long time ago, I purchased tl-dr.io 9/17/2016, 10:15:16 PM - Parth (Parth): I ended up not doing the project I intended on using the domain for 9/17/2016, 10:15:41 PM - Parth (Parth): Now that I've started contributing to this project, I'd love to help it grow 9/17/2016, 10:16:00 PM - Parth (Parth): is there any interest in buying this domain from me? @/all 9/18/2016, 1:06:21 PM - waldyrious (Waldir Pimenta): @Parth-Mehrotra I was actually quite fond of the demo URL @ostera used in #1073 (tldr.sh), and was wondering if we could set up a crowdfunding campaign to get it, since it’s not exactly cheap (https://www.nic.sh/pricelist.xzx). So for me, tl-dr.io would be a nice addition, but not necessarily our pimary focus (again: this is my opinion only), except if it is significantly cheaper, of course. 9/18/2016, 1:06:36 PM - waldyrious (Waldir Pimenta): Let’s see what others think and move on from there :) 9/18/2016, 3:49:43 PM - ostera (Leandro Ostera): hey so I kinda jumped the gun on that one some time ago haha I actually have plans already on setting up `tldr.sh` for the web client 9/18/2016, 3:55:18 PM - waldyrious (Waldir Pimenta): Oh wow, that’s really great to hear 9/18/2016, 3:55:19 PM - waldyrious (Waldir Pimenta): 😃 9/18/2016, 4:10:36 PM - ostera (Leandro Ostera): yeah, it just felt right 9/18/2016, 4:10:51 PM - ostera (Leandro Ostera): no point in making everyone type my name over and over 😛 9/18/2016, 5:11:40 PM - waldyrious (Waldir Pimenta): Well, if you need any help supporting the costs, let us know, we could setup a gratipay, patreon or a simple one-off crowdfunding campaign. 9/19/2016, 12:05:57 AM - agnivade (Agniva De Sarker): @/all - To implement #1068, I need to be a member of the tldr organization. Let me know if you guys are okay with it. :) Otherwise, I will unassign myself from the issue for others to take up. 9/19/2016, 12:47:25 AM - waldyrious (Waldir Pimenta): I’m ok with it. I want to make that process less manual, but until we get there, I vote for adding you, since you’ve already been functioning pretty much as a org member/maintainer anyway. 9/19/2016, 1:06:46 AM - waldyrious (Waldir Pimenta): @agnivade also, please comment on #1048 — I’d like to hear other voices regarding how to progress with that thread. 9/19/2016, 1:52:29 AM - agnivade (Agniva De Sarker): Frankly, I don't have much experience in the licensing area. Initially I was of the same opinion as @notpeter that we should specify a licence to make it explicit. But your point makes sense to me. And personally, I never cared much about licensing in my open source contributions 😛. I would defer to others for further comments. 9/19/2016, 1:55:46 AM - waldyrious (Waldir Pimenta): yeah, I assumed that was why several people didn’t comment. But none of us are experts, it’s mostly about finding a system that makes sense for everyone and strikes a balance that we agree on, regarding specificity vs. user-friendliness. All opinions are equally valid, unless someone actually identifies as a legal expert/professional. 9/19/2016, 8:37:43 AM - Parth (Parth): Awesome, looking forward to tldr.sh :thumbsup: I'll probably then just mirror or something at tl-dr.io 9/20/2016, 12:08:32 AM - waldyrious (Waldir Pimenta): that would be really nice, @Parth-Mehrotra :) 9/20/2016, 12:08:55 AM - waldyrious (Waldir Pimenta): hey @all, at the moment there are only 48 unlabeled PRs in the repo! https://github.com/tldr-pages/tldr/pulls?q=is%3Apr%20no%3Alabel%20is%3Aclosed 9/20/2016, 12:10:03 AM - waldyrious (Waldir Pimenta): if anyone wants to start making some cool stats with that data, there’s enough juice to get started 😄 9/21/2016, 2:30:21 PM - waldyrious (Waldir Pimenta): @ostera shall we rename the “architecture” label to “platforms”? that should make it clearer to what it applies to. 9/21/2016, 9:15:31 PM - agnivade (Agniva De Sarker): And now except #799, we don't have any pending PRs opened by non-members older than 2 months ! 9/21/2016, 9:18:48 PM - agnivade (Agniva De Sarker): @igorshubovych - Would you be able to take a look at it ? This seems to be the oldest pending PR which requires some major work. 9/21/2016, 9:54:52 PM - waldyrious (Waldir Pimenta): @agnivade commendable work on trimming down our old PRs 👏 9/21/2016, 10:53:06 PM - agnivade (Agniva De Sarker): My pleasure ! Only #799 is bugging me now 😑 .. hopefully we will be able to take care of it too .. 9/28/2016, 3:38:47 AM - waldyrious (Waldir Pimenta): @agnivade since nobody opposed, I’ll go ahead and make you an org member 😄 9/28/2016, 3:40:51 AM - waldyrious (Waldir Pimenta): let me know if the access level is sufficient or if you need something else, e.g. to work on #1068 9/28/2016, 4:01:13 AM - waldyrious (Waldir Pimenta): @/all: I’ve added the “hacktoberfest” label to some issues, so now we’re officially participating in Hacktoberfest 2016 😃 https://www.digitalocean.com/company/blog/ready-set-hacktoberfest/ 9/28/2016, 4:02:29 AM - waldyrious (Waldir Pimenta): All participants who make 4+ PRs in October get a free t-shirt, and maybe stickers as well (last year there were stickers, so maybe they’ll also do it this year) 9/28/2016, 11:53:34 AM - agnivade (Agniva De Sarker): thanks @waldyrious ! 9/28/2016, 11:54:01 AM - agnivade (Agniva De Sarker): wow hacktoberfest sounds cool ! Time to get more stickers !! My laptop badly needs some new ones 😛 9/29/2016, 6:45:28 PM - agnivade (Agniva De Sarker): Hey @/all , I am seeing a lot of junk links being added in the webhooks section. For eg, there are 6 hooks for gitter ! 9/29/2016, 6:46:55 PM - agnivade (Agniva De Sarker): Then there are hooks for zube.io, sweepboard.com, waffle.io and clahub. 9/29/2016, 6:47:01 PM - agnivade (Agniva De Sarker): Can we clear all of these ? 9/29/2016, 9:41:28 PM - waldyrious (Waldir Pimenta): I did try at least some of them. I don’t know about the gitter ones, nor why there are 6. The zube and sweepboard were on me (can’t recall for sure about waffle), as I recently experimented with kanban-style boards. But I suppose they aren’t really needed at the moment, since there are so few active maintainers that we can coordinate easily here on Gitter. If you want to remove them, fine by me (AFAIK nobody’s using them) 9/30/2016, 12:27:35 AM - agnivade (Agniva De Sarker): thanks 9/30/2016, 1:21:48 AM - waldyrious (Waldir Pimenta): Hey @/all check out the new README with even more badges 😃 https://github.com/tldr-pages/tldr#tldr 9/30/2016, 1:22:05 AM - waldyrious (Waldir Pimenta): (let me know if those stats are interesting and which you’d suggest adding/removing) 9/30/2016, 1:38:33 AM - waldyrious (Waldir Pimenta): @agnivade just opened a PR (#1100), but mentionbot doesn’t seem to have been triggered. Is that normal? 9/30/2016, 1:41:28 AM - waldyrious (Waldir Pimenta): Ah, it does work after all :) where does the text come from? 9/30/2016, 11:53:11 AM - agnivade (Agniva De Sarker): that's its default text. It can be modified if needed. 9/30/2016, 11:58:51 AM - agnivade (Agniva De Sarker): hmm the badges do seem a tad too much .. 😑 Maybe we can remove CLAs signed, contributors .. 9/30/2016, 12:40:38 PM - waldyrious (Waldir Pimenta): If that’s the default, then I suppose I’ll send a PR to mentionbot. The wording is slightly awkward ("annotation information”) and there’s no period at the end. 9/30/2016, 12:41:58 PM - waldyrious (Waldir Pimenta): About the badges, haha yeah I guess I got a little carried away. I suppose we could move the CLA badge to contributing.md, and put the contributors one there too, but I’d like to keep the contributors badge in the readme as well, as a way to invite people in :) 9/30/2016, 12:53:52 PM - agnivade (Agniva De Sarker): > If that’s the default, then I suppose I’ll send a PR to mentionbot. No need to send a PR. We can add a config file .mention-bot which can modify the commit message. I am just giving it some run time to be sure that it works okay. > About the badges Sure. 9/30/2016, 12:57:03 PM - waldyrious (Waldir Pimenta): I did notice that we can customize it, but I’d rather fix it at the source :) https://github.com/facebook/mention-bot/pull/170 9/30/2016, 12:57:55 PM - agnivade (Agniva De Sarker): Yea caught your drift. 😃 9/30/2016, 1:06:18 PM - waldyrious (Waldir Pimenta): also: https://github.com/facebook/mention-bot/issues/171 9/30/2016, 1:07:19 PM - waldyrious (Waldir Pimenta): I’m out of time right now, can you please do the badge change yourself? no need for a PR since we’ve already discussed it here and it’s a pretty minor change anyway. 9/30/2016, 1:08:55 PM - waldyrious (Waldir Pimenta): (remove CLA badge from readme.md, and I guess I’d even add all the badges to contributing.md except the build one, since they’re all related to contributing) 9/30/2016, 1:15:35 PM - agnivade (Agniva De Sarker): > can you please do the badge change yourself? Sure. 10/1/2016, 5:04:59 PM - waldyrious (Waldir Pimenta): @agnivade mention bot fix, part II: https://github.com/facebook/mention-bot/pull/172 :) 10/1/2016, 5:36:42 PM - agnivade (Agniva De Sarker): Cool. Looks like your hacktoberfest started on a good note 😃 10/1/2016, 5:38:15 PM - waldyrious (Waldir Pimenta): nah, that’s just me tending to my latest addiction xD I once was just as active on Wikipedia, these days it’s github (see the contribution calendar in my profile and you’ll see what I mean 😛) hactoberfest makes no difference for me other than getting a t-shirt for PRs I would have done anyway xD 10/1/2016, 5:53:31 PM - agnivade (Agniva De Sarker): I meant it as a joke of course 😄 10/1/2016, 5:54:05 PM - waldyrious (Waldir Pimenta): I didn’t take it any other way :) 10/1/2016, 5:54:33 PM - waldyrious (Waldir Pimenta): god damn it how come it isn’t possible to show a simple smile on gitter? 10/1/2016, 5:54:39 PM - waldyrious (Waldir Pimenta): : ) 10/1/2016, 5:55:06 PM - waldyrious (Waldir Pimenta): I guess that’s the best I can do xD 10/1/2016, 5:57:39 PM - agnivade (Agniva De Sarker): haha 12/24/2022, 5:05:53 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) joined the room 1/14/2023, 2:53:36 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) joined the room 10/2/2016, 7:11:05 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Hi :shipit: 10/2/2016, 8:24:51 PM - agnivade (Agniva De Sarker): Howdy ! 10/3/2016, 2:22:55 PM - agnivade (Agniva De Sarker): Hey @/all - Of late, I have been giving some time to the node client codebase and there are a lot of places where the code can be improved. Use of global vars at some places, outdated packages(wrench) and a bit of un-idiomatic way of doing things (using sync calls, downloading to /tmp and then copying to .tldr/ again) are just few of those areas. Using the ES6/7 syntax will also go a long way to improve the code readability. I would like to offer myself up to be a maintainer of the node client repo. Since @waldyrious and @ostera are doing such a great job at maintaining the pages repo, and @ostera already owns the web client, it would be good to have someone actively maintaining the node client. We would strike a good balance between content and client. @igorshubovych does not seem to be very active of late. We already have plans to chalk up a minimal spec which all officially sanctioned clients must adhere to, so this would be a good way to expedite the process. There are a couple of stale issues and PRs just lying there. I just fixed the long standing issue of `npm install -g` thingy, and have some other patches in mind. That would be easy on everybody if I am made a maintainer. Let me know what do you guys think :) 10/3/2016, 3:06:03 PM - waldyrious (Waldir Pimenta): That makes perfect sense @agnivade and I appreciate the detailed write-up. I’ll go ahead and add you to the node-client-maintainers team. 10/3/2016, 3:12:00 PM - waldyrious (Waldir Pimenta): (done) 10/3/2016, 4:56:55 PM - agnivade (Agniva De Sarker): thanks ! 10/3/2016, 5:26:00 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @ostera please review the tldr-pages.github.io PR now, I think it should be alright 10/3/2016, 6:46:55 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @agnivade Need help with porting the node client ES7? I've tried that recently on a few projects, turns out it's very useful to be done. Also good job on fixing those issues. 👏 10/3/2016, 11:26:34 PM - agnivade (Agniva De Sarker): @zdroid - Thanks mate. I have a couple of things on mind. Like replacing "wrench" with "fs-extra" and bringing the repo to a good shape. I will plan to start the port after Oct end. That's when node will EOL the 0.10 branch. 10/3/2016, 11:27:39 PM - agnivade (Agniva De Sarker): It will allow me to set a minimum node version of >=4 and slowly start converting pages and not involve unnecessary babel transpiling. I will involve you in the PRs. Keep an eye out ! 10/3/2016, 11:57:25 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Thanks, I will 🔥 10/4/2016, 1:19:46 AM - agnivade (Agniva De Sarker): Hey guys, need some help here. It seems that to publish a npm package, owners have to be specifically added by original owners. https://docs.npmjs.com/cli/owner. The owners are currently @rprieto and @igorshubovych . So unless they add me as an owner, I am stuck. Any way around to resolve this ? 10/4/2016, 1:47:49 AM - waldyrious (Waldir Pimenta): Well, nobody has objected to you being made an org member, and since @ostera and I were recently added directly as owners, I think it sould be fairly uncontroversial to make you one as well. Just don’t go `rm -rf`-ing around 😛 10/4/2016, 1:48:44 AM - waldyrious (Waldir Pimenta): See if it works now : ) 10/4/2016, 2:22:13 AM - ostera (Leandro Ostera): @agnivade, all of the data layer from the web client could be reused in the node-client :) 10/4/2016, 2:23:54 AM - ostera (Leandro Ostera): it’s all type-checked, functional reactive javascript – the DOM rendering is completely separated from it 10/4/2016, 2:26:15 AM - ostera (Leandro Ostera): I could go one step further and decouple the URL/BrowserHistory from the rest, but as it is right now you should be able to fork the web client and play around with the source to hook in the CLI arguments – I can walk you through it if you’d like to 10/4/2016, 3:12:21 AM - ostera (Leandro Ostera): but come to think of it, most of the reactiveness necessary to make a web application snappier and naturally flowing isn’t really necessary for a CLI client that has basically O(1) access to everything locally 10/4/2016, 3:13:08 AM - ostera (Leandro Ostera): either way, ping me if I can help with anything over there :) 10/4/2016, 4:33:37 AM - waldyrious (Waldir Pimenta): @ostera if you haven’t yet, you must read this 😄 https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f 10/4/2016, 8:48:17 AM - agnivade (Agniva De Sarker): hey @waldyrious , its not working. 😟 10/4/2016, 8:48:35 AM - agnivade (Agniva De Sarker): `npm owner ls` still shows Igor and Romain 10/4/2016, 8:50:48 AM - agnivade (Agniva De Sarker): @ostera - Cool. I will take a look and pick up parts I find interesting 😉 10/4/2016, 12:22:31 PM - ostera (Leandro Ostera): @waldyrious haha 10/4/2016, 12:28:54 PM - ostera (Leandro Ostera): very very accurate 10/4/2016, 12:29:07 PM - ostera (Leandro Ostera): I’d hate to start doing javascript now really 10/4/2016, 12:29:26 PM - waldyrious (Waldir Pimenta): Thought so too. And informative, really. 10/4/2016, 12:29:41 PM - ostera (Leandro Ostera): agree – more than on the tooling, I’d say on the culture 10/4/2016, 12:30:02 PM - ostera (Leandro Ostera): it speaks volumes of the community 10/4/2016, 12:30:26 PM - ostera (Leandro Ostera): the infamous _new is always better_ 10/4/2016, 12:30:41 PM - ostera (Leandro Ostera): I myself have been building websites with makefiles for a while now 10/4/2016, 12:31:03 PM - ostera (Leandro Ostera): can’t get better than that 😛 10/4/2016, 12:32:09 PM - ostera (Leandro Ostera): I mean look at this! https://github.com/ostera/tldr.jsx/blob/master/Makefile#L70-L78 10/4/2016, 12:32:15 PM - waldyrious (Waldir Pimenta): Sure. After all each of the tools got a couple sentences' description at best, while the culture was showcased throughout the whole article : ) 10/4/2016, 12:32:55 PM - waldyrious (Waldir Pimenta): Omg xD 10/4/2016, 12:33:14 PM - ostera (Leandro Ostera): anyone that has ever used unix before will know _exactly_ what’s going on there 😛 10/4/2016, 12:33:54 PM - ostera (Leandro Ostera): but people insist in layers and layers of plugins to gzip your assets, when you likely already have gzip installed 10/4/2016, 12:34:14 PM - waldyrious (Waldir Pimenta): That's why I am so happy that @zdroid is rebuilding the website using simpler technology. Nothing fancier than that was ever needed in this case, anyway.. 10/4/2016, 12:34:40 PM - waldyrious (Waldir Pimenta): Hehe true 10/4/2016, 12:45:03 PM - waldyrious (Waldir Pimenta): @agnivade oh, I see. It's about ownership of the package in npm, not on github. I couldn't figure out how to connect a npm accout with a github one (if it is at all possible), which I hoped would have recognized me as a member of the org behind the package and thus allow me to modify its registry. I guess we'll need @igorshubovych or @rprieto to intervene... 10/4/2016, 12:50:52 PM - agnivade (Agniva De Sarker): 😢 10/4/2016, 12:51:05 PM - agnivade (Agniva De Sarker): Let me see if I can get a hold of them 10/4/2016, 12:52:08 PM - waldyrious (Waldir Pimenta): :+1: 10/4/2016, 5:30:32 PM - agnivade (Agniva De Sarker): Igor just gave me permissions ! Yay ! 🎉 10/4/2016, 8:20:10 PM - waldyrious (Waldir Pimenta): Cool! ✨ 10/4/2016, 10:58:48 PM - ostera (Leandro Ostera): 🙏🏻 10/7/2016, 1:47:39 PM - agnivade (Agniva De Sarker): @/all - Made a simple roadmap project here - https://github.com/tldr-pages/tldr-node-client/projects/1. Any comments are appreciated. 10/7/2016, 1:48:40 PM - ostera (Leandro Ostera): I like it 10/7/2016, 1:48:58 PM - ostera (Leandro Ostera): 👍🏻 10/7/2016, 1:49:56 PM - agnivade (Agniva De Sarker): thanks 10/7/2016, 2:18:39 PM - waldyrious (Waldir Pimenta): nice :) but one question: weren’t color themes introduced in https://github.com/tldr-pages/tldr-node-client/pull/61 ? 10/7/2016, 2:24:07 PM - agnivade (Agniva De Sarker): yes they were, but its not complete. For eg- https://github.com/tldr-pages/tldr-node-client/issues/56 needs to be fixed. And I plan to improve the default theme. 10/7/2016, 2:27:48 PM - waldyrious (Waldir Pimenta): ok :+1: looks good to me! 10/11/2016, 2:25:36 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I've just noticed the comment on my PR for tldr-pages.github.io redesign so I updated that too 10/11/2016, 2:25:38 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I hope that's all 10/11/2016, 12:14:50 PM - agnivade (Agniva De Sarker): @zdroid - would you mind sending a PR to update the screenshot in tldr-pages.github.io ? :) Its still the old one. You can take the one we use on the README of the main repo. 10/11/2016, 12:30:21 PM - agnivade (Agniva De Sarker): Also, can we delete the live-demo and live-demo-no-iframe branches from the tldr-pages repo? It was updated 10 months ago by @igorshubovych , and no activity since then. 10/11/2016, 1:18:50 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Yes @agnivade, go on and delete them 10/11/2016, 1:18:59 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): The changes proposed there are already implemented 10/11/2016, 2:02:19 PM - agnivade (Agniva De Sarker): cool. will do 10/11/2016, 2:08:25 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): also you could review tldr-pages/tldr-pages.github.io#15 10/11/2016, 6:29:39 PM - agnivade (Agniva De Sarker): done 10/12/2016, 12:18:38 PM - ostera (Leandro Ostera): [![Screen Shot 2016-10-12 at 8.43.45 AM.png](https://files.gitter.im/tldr-pages/tldr/Q2KO/thumb/Screen-Shot-2016-10-12-at-8.43.45-AM.png)](https://files.gitter.im/tldr-pages/tldr/Q2KO/Screen-Shot-2016-10-12-at-8.43.45-AM.png) 10/12/2016, 12:18:40 PM - ostera (Leandro Ostera): /@all, I’m very happy to announce that we are _killing it_ since the new web client release last July :) we’ve more than doubled week to week traffic from an old average of 750 to almost 2000 unique visits a week – and we managed to get our bounce rates (how often people visit one page and leave) to under 45%! This means almost 6 out of 10 visitors stays in the website and looks for something else. 10/12/2016, 12:19:12 PM - ostera (Leandro Ostera): (From google analytics results) 10/12/2016, 12:26:33 PM - ostera (Leandro Ostera): We’re yet to draw results from the web client searches to build lists of pages to tackle, but it doesn’t look half bad (under 500 average a week, but plenty of single letter commands, platform prefixes, and some Github API limits throwing some command searches into the not-found pile). 10/12/2016, 12:35:11 PM - waldyrious (Waldir Pimenta): Wow, nice!! 10/12/2016, 12:37:39 PM - waldyrious (Waldir Pimenta): Brilliant work on the web client, @ostera 😃 10/12/2016, 4:02:12 PM - agnivade (Agniva De Sarker): woot ! 👏 10/13/2016, 12:57:16 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @waldyrious I'll need some help to find a proper HTML5 special character to represent the link. I don't wanna use icon font for something that simple 10/13/2016, 12:57:30 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Maybe `#` is enough? 10/13/2016, 1:12:31 PM - waldyrious (Waldir Pimenta): Yeah, or the section marker § 10/13/2016, 1:13:33 PM - waldyrious (Waldir Pimenta): Or we could use Unicode :) http://www.fileformat.info/info/unicode/char/1f517/index.htm 10/13/2016, 1:14:24 PM - waldyrious (Waldir Pimenta): It sure if the Google fonts we're using have that character, though. 10/13/2016, 3:09:56 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I submitted the PR @waldyrious, with some CSS changes 10/14/2016, 2:04:11 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Maybe I am a bit too nit-picky, but [tldr-lint](https://github.com/tldr-pages/tldr-lint) repository should have description 10/14/2016, 7:54:02 AM - ostera (Leandro Ostera): @zdroid not at all! you’re right :) 10/14/2016, 7:55:46 AM - ostera (Leandro Ostera): there – added one. 10/14/2016, 7:57:14 AM - ostera (Leandro Ostera): Guys, feels so good to see the core team growing! Happy to be a part of this. Namaste 🙏🏼 10/14/2016, 1:06:06 PM - waldyrious (Waldir Pimenta): That reminds me, we still need to define an integration roadmap for frequent contributors. I’ve created an issue to track that: https://github.com/tldr-pages/tldr/issues/1117 10/16/2016, 11:02:26 PM - agnivade (Agniva De Sarker): We are now under 20 pending PRs ! 10/17/2016, 12:24:51 AM - waldyrious (Waldir Pimenta): YEAH! @agnivade much of that is due to your diligence :) great job! 10/17/2016, 12:26:27 AM - waldyrious (Waldir Pimenta): by the way, maybe we should start taking advantage of github's new feature to edit PR branches for when the author goes absent. I believe this setting isn't retroactive, so older PRs won't have this and we'd have to copy the commits over to new PRs, but probably some of the more recent ones are amenable to this treatment. 10/17/2016, 10:35:57 AM - ostera (Leandro Ostera): :+1: ^ 10/17/2016, 11:04:46 AM - agnivade (Agniva De Sarker): yep, good idea. 10/18/2016, 1:04:36 PM - agnivade (Agniva De Sarker): FYI - some heated drama happened over at the golang and the overall open source community yesterday. Here are the links if you guys want to give it a read - 10/18/2016, 1:04:46 PM - agnivade (Agniva De Sarker): http://www.florinpatan.ro/2016/10/why-you-should-not-use-iris-for-your-go.html 10/18/2016, 1:04:55 PM - agnivade (Agniva De Sarker): and then this - https://www.reddit.com/r/golang/comments/57w79c/why_you_really_should_stop_using_iris/ 10/18/2016, 1:05:00 PM - rubenvereecken (Ruben Vereecken): Always up for heated drama 10/18/2016, 1:05:22 PM - agnivade (Agniva De Sarker): then you are gonna love this ! 10/19/2016, 2:03:23 AM - ostera (Leandro Ostera): too much dependency man haha 10/19/2016, 2:03:49 AM - ostera (Leandro Ostera): it’s insane how in the erlang world you almost build the most basic version of everything you need 10/20/2016, 9:16:05 AM - agnivade (Agniva De Sarker): that's what is recommended in golang too. The authors suggest to write small parts of code instead of importing another library. And for the rest, use the standard library (which is pretty amazing). 10/20/2016, 9:17:28 AM - agnivade (Agniva De Sarker): But people **LOVE** "web frameworks". Even after the community recommends that standard library is enough, people keep on asking "which is the best web framework in Golang" .. hence you have this .. 😑 10/27/2016, 5:28:45 PM - waldyrious (Waldir Pimenta): @/all I made a mistake: I just sent a commit directly to master without doing a PR. Please review and let me know if there’s anything you’d recommend changing: https://github.com/tldr-pages/tldr/commit/032c83016dce0ad9a28513035d8e585993d97dfc 10/27/2016, 5:54:50 PM - waldyrious (Waldir Pimenta): Ok, I’ve managed to remove the commit from master relatively cleanly (had to force-push to master, but given the short timeframe, there should be no issues 10/27/2016, 5:55:01 PM - ostera (Leandro Ostera): cool 10/27/2016, 5:55:05 PM - waldyrious (Waldir Pimenta): The PR is now at #1131 10/27/2016, 5:57:09 PM - waldyrious (Waldir Pimenta): (I also took the opportunity to activate the CLA in the branch protection options, now that #1048 has been merged.) 10/28/2016, 11:19:51 AM - agnivade (Agniva De Sarker): Guys, I have started work on #1066. I have created a test PR for that purpose, kindly ignore any work on that PR. 😄 10/28/2016, 4:48:03 PM - waldyrious (Waldir Pimenta): looking pretty promising already 😃 10/28/2016, 6:03:00 PM - agnivade (Agniva De Sarker): @waldyrious - can you check the content of the message and let me know if you want to change anything - https://github.com/tldr-pages/tldr/pull/1133#issuecomment-256908608 ? 10/28/2016, 8:03:43 PM - waldyrious (Waldir Pimenta): @agnivade looks great, I would maybe just remove the last line, `npm ERR! Test failed. See above for more details.` — what do you think? 10/28/2016, 8:04:38 PM - waldyrious (Waldir Pimenta): I suppose we can always change the script if we want to tweak the message further, right? 10/28/2016, 8:04:47 PM - waldyrious (Waldir Pimenta): ps - amazing work! 👏 10/28/2016, 8:08:22 PM - waldyrious (Waldir Pimenta): @agnivade I’d also change "The PR has failed” —> “The build has failed” (or “the build for this PR has failed"), with “build” as a link to the travis log 😃 10/28/2016, 8:24:14 PM - agnivade (Agniva De Sarker): Sure, will update. 10/28/2016, 8:25:33 PM - agnivade (Agniva De Sarker): Oh, and also everyone is welcome to come up with a cool profile picture for tldr bot 😄 11/7/2016, 1:10:14 PM - agnivade (Agniva De Sarker): @/all - Any help on finding a cool profile pic for the tldr bot is greatly appreciated ! A self-made logo will be awesome. My designing skills are pathetic. 😆 11/7/2016, 3:31:29 PM - waldyrious (Waldir Pimenta): I don’t have any ideas, but maybe we could take some inspiration from these: https://commons.wikimedia.org/wiki/Category:Robot_head_icons 11/7/2016, 3:31:34 PM - waldyrious (Waldir Pimenta): (they’re all freely licensed) 11/7/2016, 9:06:11 PM - agnivade (Agniva De Sarker): hmm .. I wanted something tldr themed .. will look around a bit more. 11/7/2016, 9:06:30 PM - waldyrious (Waldir Pimenta): Yeah, agreed. that’s why I mentioned “inspiration” 😉 11/7/2016, 9:07:21 PM - waldyrious (Waldir Pimenta): something that occurred to me was a robot head with a terminal for the eyes, with the tldr logo (white `$;` over a black background) in it 11/10/2016, 5:32:08 PM - waldyrious (Waldir Pimenta): Hi @/all! Please take a look at https://github.com/tldr-pages/tldr/pull/958. I’ve updated the proposal for a new, more readable pages syntax, and added a link to a shell script to test it out. Please give it a try and let me know what you think! 11/17/2016, 8:42:28 PM - agnivade (Agniva De Sarker): wow .. UI change ! I initially thought I entered the wrong url 😆 11/17/2016, 8:43:35 PM - ostera (Leandro Ostera): On tldr? D: 11/17/2016, 8:43:59 PM - waldyrious (Waldir Pimenta): Gitter, it seems. I also got the change today (in the desktop client) 11/17/2016, 8:44:08 PM - waldyrious (Waldir Pimenta): I like it a lot, btw :) 1/14/2023, 2:54:20 PM - zddewe (WILLIS WORLEY) joined the room 11/21/2016, 3:00:26 AM - zddewe (WILLIS WORLEY): really thank you. 1/14/2023, 2:54:22 PM - tarvos21 (dubing) joined the room 11/30/2016, 4:09:15 PM - tarvos21 (dubing): hi, how to use the python client of tldr? 11/30/2016, 4:09:34 PM - tarvos21 (dubing): npm client tldr can not be installed, so does gem 11/30/2016, 4:09:59 PM - waldyrious (Waldir Pimenta): what’s the problem you’re getting with installing them? 11/30/2016, 4:11:19 PM - tarvos21 (dubing): wait, I install it again using npm to read the error message 11/30/2016, 4:11:27 PM - waldyrious (Waldir Pimenta): ok 11/30/2016, 4:13:01 PM - tarvos21 (dubing): meny ERR! tldr@1.7.0 postinstall :`node ./bing/tldr --update` Exit code 1 11/30/2016, 4:13:27 PM - tarvos21 (dubing): finally say please include the file /home/bing/npm-debug.log 11/30/2016, 4:13:55 PM - tarvos21 (dubing): failed at the tldr@1.7.0 postinstall script 'node ./bing/tldr --update' 11/30/2016, 4:13:57 PM - waldyrious (Waldir Pimenta): That’s seems like the problem is already known. Can you take a look at https://github.com/tldr-pages/tldr-node-client#installing? 11/30/2016, 4:14:23 PM - tarvos21 (dubing): ok, I will read it, thanks 11/30/2016, 4:14:36 PM - waldyrious (Waldir Pimenta): This is something we’ve been trying to fix, because a lot of people get that error 11/30/2016, 4:14:42 PM - tarvos21 (dubing): so, how to use the python client? tldr curl? 11/30/2016, 4:15:01 PM - tarvos21 (dubing): it tell me config file, such kind of thing 11/30/2016, 4:16:50 PM - waldyrious (Waldir Pimenta): Try doing `sudo npm install -g tldr --user=$(whoami)` to see if the node install works 11/30/2016, 4:28:53 PM - tarvos21 (dubing): Oh great, succeed. I first try to install it by the command, but a error happens saying " not empty, rename .tldr... -> .tldr.DELETE", so I delete the directory ~/.npm-global/lib/node_modules/.tldr.DELETE/, and again I install with the long command, and succeed, great, the representation is explicit and good, thanks so much! 11/30/2016, 4:30:07 PM - waldyrious (Waldir Pimenta): I’m glad that worked : ) I’ve just sent a pull request (#1178) to update the installation instructions so that other people don’t have the same problem 11/30/2016, 4:31:04 PM - tarvos21 (dubing): Great! 1/14/2023, 2:54:28 PM - dikarel (Darius Karel) joined the room 11/30/2016, 7:09:16 PM - dikarel (Darius Karel): Hi, you may have noticed me creating lot of issues wrt. devops tools. I meant these as a todo-list for myself as well as an invitation for others to submit PRs. Let me know if this is not the right way to do it 11/30/2016, 8:44:20 PM - waldyrious (Waldir Pimenta): @dikarel it’s ok, but if you can help on tackling that list, it would be greatly appreciated indeed : ) 1/14/2023, 2:54:30 PM - Krutonium (Krutonium) joined the room 12/1/2016, 3:35:00 AM - Krutonium (Krutonium): Hello all 12/1/2016, 5:31:41 AM - waldyrious (Waldir Pimenta): Hi @PFCKrutonium 12/1/2016, 5:32:03 AM - waldyrious (Waldir Pimenta): I’ve seen you’ve sent some PRs, welcome to the community! 12/1/2016, 5:48:15 AM - Krutonium (Krutonium): Thanks! I'll fix the issues that were pointed out when I am at a PC 12/1/2016, 7:43:46 PM - Krutonium (Krutonium): @waldyrious cmake *should* be fixed 12/1/2016, 7:43:53 PM - Krutonium (Krutonium): Fixing nl now 12/1/2016, 7:59:48 PM - Krutonium (Krutonium): Fixed 12/1/2016, 9:04:25 PM - Krutonium (Krutonium): Did another round of fixing @waldyrious 12/3/2016, 1:16:54 AM - waldyrious (Waldir Pimenta): I do get the notifications on Github @PFCKrutonium, no need to tell me here, but thanks for the attention : ) 12/13/2016, 9:07:20 PM - agnivade (Agniva De Sarker): Hey @/all , how are things ? 😄 I am just back from a vacation and catching up on github notifications. 😆 12/13/2016, 9:08:03 PM - waldyrious (Waldir Pimenta): oh wow. You must have a lot of stuff to process 😛 12/13/2016, 9:10:48 PM - agnivade (Agniva De Sarker): I know .. 😰 12/14/2016, 5:01:29 AM - Krutonium (Krutonium): I leave for a couple days and I just hit the read all button. /Ignores 500+ notifications/ 12/21/2016, 11:26:45 AM - agnivade (Agniva De Sarker): @waldyrious - I think I know the problem with Travis not reporting the build errors. I set the environment variable from travis UI. And I think that doesn't work for PRs from other people. Can you check here - https://travis-ci.org/tldr-pages/tldr/settings and see if you can see the TRAVIS_BOT_GITHUB_TOKEN variable ? 12/21/2016, 11:34:52 AM - agnivade (Agniva De Sarker): Yea, so this is the problem we are facing - https://github.com/travis-ci/travis-ci/issues/1301. Basically the env var won't be available to any external PR. It worked for me because I was sending PRs from the original repo. I was looking at mention-bot, and they have a heroku url where it runs and accepts data via a webhook. 12/21/2016, 11:35:57 AM - agnivade (Agniva De Sarker): Do you see any other way to achieve this ? I think we should revert the changes temporarily until we have a solution. Sorry about this. I was not aware of such issues, as in my testing everything worked fine. 12/21/2016, 1:42:09 PM - waldyrious (Waldir Pimenta): Hey @agnivade 12/21/2016, 1:43:19 PM - waldyrious (Waldir Pimenta): It's not really your fault, you did test the changes, and the reason it didn't work was not at all obvious 12/21/2016, 1:47:21 PM - waldyrious (Waldir Pimenta): If we revert the changes what exactly will happen? I think Travis did correctly report the error status to github on the last PR I checked (but not tldr-bot), but I may be misremembering 12/21/2016, 1:49:40 PM - waldyrious (Waldir Pimenta): Are you saying that we need a server of our own to run custom logic for the bot? I'm on the phone right now but I'll check the link of the issue later for more details. 12/21/2016, 6:33:01 PM - agnivade (Agniva De Sarker): Yea travis correctly reported the error, but the error message was gobbled up by tldr bot. As it was supposed to upload the message to the PR, and it obviously wasn't doing that, I disabled it. 12/21/2016, 6:33:32 PM - agnivade (Agniva De Sarker): > Are you saying that we need a server of our own to run custom logic for the bot? Yea maybe something like that. Check out the link when you have some time. Lets come up with something. 12/21/2016, 7:10:39 PM - waldyrious (Waldir Pimenta): @agnivade after reading the travis issue, I’m a bit unsure: why exactly doesn’t the token get set for PRs originating in forks? what’s the concern here? 12/22/2016, 12:18:21 AM - agnivade (Agniva De Sarker): Its foreign code, so you don't know what someone can do when they get your secure token. 12/22/2016, 12:18:45 AM - waldyrious (Waldir Pimenta): what does the token give access to? 12/22/2016, 11:39:18 PM - agnivade (Agniva De Sarker): In this case, the token gives access to the user profile of tldr bot. But it can be essentially any sort of secret token. So the attacker can do whatever is possible through the token. 12/23/2016, 12:04:33 AM - waldyrious (Waldir Pimenta): yeah, I see. From Travis’s side it’s impossible to know. On the other hand, if we create a token that only gives permission to comment on issues, I suppose it would not be such a big deal to have it public, even though in principle that shouldn’t be done 12/23/2016, 12:05:01 AM - waldyrious (Waldir Pimenta): i.e. place it directly in the testing script’s code 12/23/2016, 10:00:01 AM - agnivade (Agniva De Sarker): That is also not possible unfortunately. Github detects that a user token is available publicly and immediately revokes it. 😟 12/23/2016, 3:40:01 PM - waldyrious (Waldir Pimenta): Yeah, it makes sense that they’d do that. So our only option is to have the code run elsewhere, huh. I wonder if other CI tools would be able to do this? I’ve used CircleCI in the past, not for this kind of task, but maybe it’s worth checking out 12/24/2016, 1:42:17 AM - agnivade (Agniva De Sarker): > So our only option is to have the code run elsewhere, huh Yea seems so. > wonder if other CI tools would be able to do this? Hmm .. will need to check that out. 12/24/2016, 1:43:21 AM - agnivade (Agniva De Sarker): I will give some focus to tldr-node now though. Thats been left out for a long time. So this will take a pause now. 12/24/2016, 2:47:31 AM - waldyrious (Waldir Pimenta): Sure :) 1/1/2017, 5:15:09 PM - agnivade (Agniva De Sarker): Happy New Year everyone !! 🎉 Wish everyone a great year ahead ! 1/2/2017, 11:04:09 PM - agnivade (Agniva De Sarker): Guys - sorry I broke the master branch. This happened because of the faulty travis check that I had removed. But an old PR still had the old check, due to which it did not report the error. @waldyrious - could you please approve #1223 when you get a chance ? 1/2/2017, 11:04:30 PM - waldyrious (Waldir Pimenta): sure, I’ll take a look in a moment 1/2/2017, 11:04:41 PM - waldyrious (Waldir Pimenta): happy 2017 btw :) 1/2/2017, 11:06:41 PM - waldyrious (Waldir Pimenta): approved & merged 1/14/2023, 2:54:45 PM - Erwyn (Martin Goyot) joined the room 1/18/2017, 2:31:57 PM - Erwyn (Martin Goyot): Hello there. I have a question, on the screenshot for tldr there is a lot of coloration but if I run it on my computer it's not the case. There is a configuration or it is terminal related? 1/18/2017, 2:32:48 PM - Erwyn (Martin Goyot): [![blob](https://files.gitter.im/tldr-pages/tldr/XiR5/thumb/blob.png)](https://files.gitter.im/tldr-pages/tldr/XiR5/blob) 1/18/2017, 2:33:06 PM - Erwyn (Martin Goyot): if it is terminal related, what is used? 1/18/2017, 3:31:38 PM - waldyrious (Waldir Pimenta): @Erwyn which client did you install? the node one (via npm), python (via pip), c++ (via homebrew), or some other? 1/18/2017, 3:44:20 PM - Erwyn (Martin Goyot): the node one 1/18/2017, 3:45:39 PM - waldyrious (Waldir Pimenta): Just checked, the default theme seems to be the `simple` one: https://github.com/tldr-pages/tldr-node-client/blob/master/config.json#L41 1/18/2017, 3:45:54 PM - waldyrious (Waldir Pimenta): The documentation should definitely be updated 1/18/2017, 3:46:45 PM - waldyrious (Waldir Pimenta): In the meantime, you can change the theme locally per the instructions here: https://github.com/tldr-pages/tldr-node-client#configuration 1/18/2017, 3:48:00 PM - waldyrious (Waldir Pimenta): Could you make a screenshot with the simple theme without the cursor visible, so I can replace the image in the readme? 1/18/2017, 3:50:35 PM - Erwyn (Martin Goyot): yeah sure 1/18/2017, 3:53:23 PM - waldyrious (Waldir Pimenta): @Erwyn actually, neverming. I’ll just add a legend to the current image :) 1/18/2017, 3:55:19 PM - Erwyn (Martin Goyot): lol ok :) 1/18/2017, 3:55:25 PM - Erwyn (Martin Goyot): and thanks for the link by the way 1/18/2017, 3:56:08 PM - waldyrious (Waldir Pimenta): no problem, thank you for the report :) this will help improve our documentation so that others aren’t subjected to the same confusion as you did 😉 1/18/2017, 4:56:29 PM - waldyrious (Waldir Pimenta): @Erwyn https://github.com/tldr-pages/tldr-node-client/issues/133 1/18/2017, 4:56:47 PM - waldyrious (Waldir Pimenta): I’ll make that change soon, hopefully later today 1/14/2023, 2:54:50 PM - jgluck (Jonathan Gluck) joined the room 1/20/2017, 8:07:56 AM - jgluck (Jonathan Gluck): *looks a bit like someone might have messed up the tldr for `ssh`* 1/20/2017, 11:37:31 AM - agnivade (Agniva De Sarker): Yes, I see it. Its a bug with the node-client(I am assuming you are on the node client). Not the page itself. 1/20/2017, 11:38:31 AM - agnivade (Agniva De Sarker): Actually we were supposed to move to a new format where I think this would not have manifested .. but anyways .. can you file a bug for this ? I will look into it .. 1/20/2017, 10:18:20 PM - jgluck (Jonathan Gluck): Yep, on the node client. 1/23/2017, 12:49:58 PM - rubenvereecken (Ruben Vereecken): Hey lads, just curious why the Travis build passes while there are errors, is this by design? 1/23/2017, 12:51:24 PM - rubenvereecken (Ruben Vereecken): Or maybe the build isn't up to date anymore with the current guidelines or something 1/23/2017, 3:07:37 PM - waldyrious (Waldir Pimenta): I’m pretty sure that is not intended. Probably @agnivade will be able to answer with more certainty 1/23/2017, 3:08:04 PM - rubenvereecken (Ruben Vereecken): Got an example here 1/23/2017, 3:08:05 PM - rubenvereecken (Ruben Vereecken): https://travis-ci.org/tldr-pages/tldr/builds/180431255 1/23/2017, 3:08:38 PM - rubenvereecken (Ruben Vereecken): It might be `tee` swallows the exit code, don't know 1/23/2017, 3:08:54 PM - waldyrious (Waldir Pimenta): Yes, this has come up before, but it was supposedly solved 1/23/2017, 3:09:05 PM - waldyrious (Waldir Pimenta): let me see if I can dig up the previous discussion 1/23/2017, 3:09:11 PM - rubenvereecken (Ruben Vereecken): Oh I see it is a fairly old run 1/23/2017, 3:09:21 PM - waldyrious (Waldir Pimenta): ah, that would explain it 1/23/2017, 3:09:31 PM - rubenvereecken (Ruben Vereecken): Sorry that's probably it then 1/23/2017, 3:09:32 PM - waldyrious (Waldir Pimenta): we did have that problem for a few days but we resolved it 1/23/2017, 3:09:49 PM - waldyrious (Waldir Pimenta): https://github.com/tldr-pages/tldr/pull/1197 1/23/2017, 3:10:25 PM - rubenvereecken (Ruben Vereecken): Hm used to be you could request a rerun on Travis but I don't see it 1/23/2017, 3:10:53 PM - rubenvereecken (Ruben Vereecken): Alriight got it 1/23/2017, 3:11:11 PM - waldyrious (Waldir Pimenta): you found it? 1/23/2017, 3:11:25 PM - rubenvereecken (Ruben Vereecken): Yeap, good PR too, so it _was_ `tee` 1/23/2017, 3:11:36 PM - waldyrious (Waldir Pimenta): yeah I see the build has restarted : ) 1/23/2017, 3:12:31 PM - waldyrious (Waldir Pimenta): hey by the way, since I haven’t seen you around in a while: did you see the discussion about the CLA, and do you have any thought about it? https://github.com/tldr-pages/tldr/pull/1048 1/23/2017, 3:12:51 PM - waldyrious (Waldir Pimenta): I believe you haven’t signed it yet, not sure if by oversight or deliberate choice 1/23/2017, 3:12:51 PM - rubenvereecken (Ruben Vereecken): I did not but will gladly look at it, I've signed the CLA myself this morning 1/23/2017, 3:13:05 PM - waldyrious (Waldir Pimenta): Oh ok, thanks for clarifying :) 1/23/2017, 3:13:43 PM - rubenvereecken (Ruben Vereecken): I'll read up once I have some more time. Was it not MIT before btw? 1/23/2017, 3:14:57 PM - waldyrious (Waldir Pimenta): Sure, take your time. Long story short, that allows us to relicense in the future should we want to. It was and still is MIT, but there is a proposal to use something more suitable for the content pages, such as CC-BY (software could remain under MIT) 1/23/2017, 3:15:20 PM - rubenvereecken (Ruben Vereecken): CC would make sense 1/23/2017, 3:15:30 PM - waldyrious (Waldir Pimenta): Here’s the relicensing discussion: https://github.com/tldr-pages/tldr/issues/1076 1/23/2017, 3:15:38 PM - rubenvereecken (Ruben Vereecken): Ah good 1/23/2017, 3:15:55 PM - waldyrious (Waldir Pimenta): but until we have past contributors on board, it’s not going anywhere : ) 1/23/2017, 3:16:39 PM - rubenvereecken (Ruben Vereecken): The CLA is a smart move 1/23/2017, 3:17:15 PM - waldyrious (Waldir Pimenta): yeah, and I was particularly fond of using something as short and clear as the permissive licenses 1/23/2017, 3:17:29 PM - waldyrious (Waldir Pimenta): most of the CLAs I saw around were pretty bulky and full of legalese 1/23/2017, 3:17:45 PM - rubenvereecken (Ruben Vereecken): They usually are ye 1/23/2017, 3:17:54 PM - rubenvereecken (Ruben Vereecken): I actually read this one 😉 1/23/2017, 3:18:35 PM - waldyrious (Waldir Pimenta): exactly 😃 1/23/2017, 3:19:11 PM - waldyrious (Waldir Pimenta): it’s nice that it’s versioned publicly under a gist, too 1/23/2017, 3:19:18 PM - rubenvereecken (Ruben Vereecken): Hahaha 1/23/2017, 3:19:33 PM - rubenvereecken (Ruben Vereecken): That's too perfect 1/23/2017, 3:20:44 PM - waldyrious (Waldir Pimenta): thought so too! just hope the service sticks around (as github integration, that is — it’s quite convenient and pretty much handles itself ^^) 1/23/2017, 3:21:14 PM - rubenvereecken (Ruben Vereecken): Is the list easily available somewhere? 1/23/2017, 3:22:27 PM - waldyrious (Waldir Pimenta): unfortunately not publicly AFAIK, but probably repo/org owners can all see it. to get it I have to go to cla-assistant.io directly and log in from there 1/23/2017, 3:24:14 PM - rubenvereecken (Ruben Vereecken): Great I see it 1/23/2017, 3:24:35 PM - waldyrious (Waldir Pimenta): Cool. I am not sure others can, though, which is a pity 1/23/2017, 3:24:55 PM - rubenvereecken (Ruben Vereecken): Sure is 1/23/2017, 3:25:00 PM - waldyrious (Waldir Pimenta): I’ve been keeping a list manually updated on #1076 1/23/2017, 3:25:05 PM - waldyrious (Waldir Pimenta): just updated it 1/23/2017, 3:25:13 PM - rubenvereecken (Ruben Vereecken): So did I 1/23/2017, 3:25:21 PM - rubenvereecken (Ruben Vereecken): If you don't mind 1/23/2017, 3:25:26 PM - waldyrious (Waldir Pimenta): several additional people have signed it since last time. (yeah I noticed you checked your name 😉) 1/23/2017, 3:25:56 PM - waldyrious (Waldir Pimenta): did you make additional changes besides that? 1/23/2017, 3:26:04 PM - rubenvereecken (Ruben Vereecken): Just the date change 😛 1/23/2017, 3:26:21 PM - waldyrious (Waldir Pimenta): :+1: 1/23/2017, 3:26:48 PM - waldyrious (Waldir Pimenta): I just updated the full list, and changed the @-pings 1/23/2017, 3:27:13 PM - waldyrious (Waldir Pimenta): the idea is to mention the top 10 people who haven’t yet signed 1/23/2017, 3:27:27 PM - waldyrious (Waldir Pimenta): the group is slowly but surely shrinking 😃 1/23/2017, 3:27:38 PM - rubenvereecken (Ruben Vereecken): I noticed, what's the reasoning of having those select sign? 1/23/2017, 3:27:47 PM - rubenvereecken (Ruben Vereecken): Is it courtesy 1/23/2017, 3:28:14 PM - rubenvereecken (Ruben Vereecken): Because otherwise shouldn't all sign or no one? 1/23/2017, 3:28:58 PM - waldyrious (Waldir Pimenta): if you’re talking about the @, it’s to ping the people who we need to sign the most 1/23/2017, 3:29:32 PM - rubenvereecken (Ruben Vereecken): I know, and I know it's the 10 most prolific contributors, but do we _require_ everyone sign or is there no requirement? 1/23/2017, 3:30:04 PM - waldyrious (Waldir Pimenta): oh, I see. no, signing is not required, but it would be helpful so any licensing change can bring their contributions along 1/23/2017, 3:30:25 PM - rubenvereecken (Ruben Vereecken): Oh and other contributions we wouldn't be allowed to port really, gotcha 1/23/2017, 3:31:03 PM - waldyrious (Waldir Pimenta): otherwise we’d have to have a more complex dual license, which I’d really like to avoid 1/23/2017, 3:33:42 PM - waldyrious (Waldir Pimenta): It would be great to have @igorshubovych’s signature too (*wink wink*) 1/23/2017, 3:33:51 PM - rubenvereecken (Ruben Vereecken): Hehehe 1/28/2017, 5:41:26 PM - agnivade (Agniva De Sarker): Hey guys, giving tldr bot another try with #1259 . In another github discussion, I learnt that if I remove all the API permissions from the bot, github doesn't remove the token. But yet, the bot is able to post comments on PR. Therefore, testing it out. 1/28/2017, 5:41:48 PM - agnivade (Agniva De Sarker): I will send a faulty PR from another friend of mine to completely test out the process end-to-end though 1/28/2017, 5:46:03 PM - waldyrious (Waldir Pimenta): Nice! Looking forward to that :) 1/30/2017, 2:19:36 PM - agnivade (Agniva De Sarker): @/all - I am going to temporarily suspend the requirement of pull request reviews while I debug the tldr bot thing. Makes for quick debugging. Will revert it back once I am done. 1/30/2017, 2:38:59 PM - agnivade (Agniva De Sarker): Everything back to normal now. My experiment failed though. 😞 1/30/2017, 2:49:17 PM - waldyrious (Waldir Pimenta): Too bad 😕 what was the issue? 1/30/2017, 4:07:16 PM - waldyrious (Waldir Pimenta): In the meantime, there’s been some nice progress in the python client, courtesy of @lots0logs 😃 1/30/2017, 10:24:27 PM - agnivade (Agniva De Sarker): My hypothesis that even if all permissions are removed, the bot should be able to post comments was wrong. 1/30/2017, 10:24:40 PM - agnivade (Agniva De Sarker): wow .. good to hear on the python client 1/30/2017, 10:52:52 PM - waldyrious (Waldir Pimenta): So our bet is still a self-hosted service, right? Is Heroku really a no-go, or could it be a possibility since there doesn’t seem to be other options? 1/31/2017, 11:06:28 AM - agnivade (Agniva De Sarker): its a possibility. 1/31/2017, 3:27:54 PM - waldyrious (Waldir Pimenta): Let me know if there’s anything I can help with in that regard. 1/31/2017, 3:28:16 PM - waldyrious (Waldir Pimenta): (unless you prefer using something else) 2/14/2017, 12:10:36 PM - agnivade (Agniva De Sarker): Hey @waldyrious - when you get some time, can you check a few PRs which are pending your approval ? - https://github.com/tldr-pages/tldr/pull/1255, https://github.com/tldr-pages/tldr/pull/1266 1/14/2023, 2:55:17 PM - jeeftor (Jeef) joined the room 2/20/2017, 10:48:31 PM - jeeftor (Jeef): hi folks -> I'm possibly interested in becoming a moderator to the project if you are looking for help 2/21/2017, 9:37:31 AM - agnivade (Agniva De Sarker): Excellent news. Its time we added more to our team 😄 Lets wait for one more week for @waldyrious / @ostera to chime in with their thoughts. If nobody replies, I will do the needful. 2/21/2017, 10:17:48 PM - jeeftor (Jeef): sounds good to me - :) 2/22/2017, 5:57:31 AM - jeeftor (Jeef): So i'm on OSX but use linux often. I have home-brew and have installed figlet on my mac, however, its currently listed under linux only commands. Should this be moved into common? - I have an open pull request for a modification to the command in any case 2/22/2017, 9:59:18 AM - agnivade (Agniva De Sarker): Sure .. it should be moved to common then. But in the example you have mentioned `showfigfonts`. Does this command also get installed with figlet ? And is it available in linux too ? 2/22/2017, 9:52:09 PM - jeeftor (Jeef): Its available on both platforms - I'm just not sure how to reference it - do we create a separate entry - or does it go in figlet? 2/22/2017, 9:53:07 PM - jeeftor (Jeef): `figlet -f {{font}}` lets you print with a specific font, but the only way to see what those fonts are is with `showfigfonts` hence my confusion 2/25/2017, 6:04:34 PM - agnivade (Agniva De Sarker): @/all - Went ahead and cleared off a bunch of old PRs. 2/27/2017, 10:56:40 AM - agnivade (Agniva De Sarker): @jeeftor - You have write access now ! Please familiarize yourself well with the CONTRIBUTION guidelines. One lagging area where we lag is working on and merging old PRs. In the past, I have done that several times, but it seems to creep up on us again. Would you be able to take some time and look into #875, #964 and #1061 ? 2/27/2017, 10:57:47 AM - agnivade (Agniva De Sarker): Also, a note on merging PRs - we always rebase a PR, not merge it, to keep the master branch clean and linear. And when you have a lot of edit related commits, merge them to a single one. 3/2/2017, 3:32:09 AM - waldyrious (Waldir Pimenta): Hi all. I’m sorry for the silence. I had to take a few days off on short notice, but I’m back and will be working through the backlog of tasks for the next few days 3/2/2017, 3:34:07 AM - waldyrious (Waldir Pimenta): For the record, I’m all for extending the project management to more people from the community — we must always make sure to remove barriers to contribution and not think of maintainership as a badge of honour. Welcome @jeeftor :) 3/2/2017, 9:24:44 AM - agnivade (Agniva De Sarker): Welcome back man .. I had assumed you were gone for good 😟 Good to have you back 😄 3/6/2017, 5:12:56 AM - waldyrious (Waldir Pimenta): sorry about that. I should've said something, but these were pretty chaotic days. I've been able to clear up pretty much all of my non-tldr github backlog, and have already handled a couple issues in tldr repos other than the main pages one. I'll now start going through the tldr-pages backlog during this week :) 3/6/2017, 10:13:26 AM - agnivade (Agniva De Sarker): awesome ! 3/8/2017, 10:08:02 AM - agnivade (Agniva De Sarker): https://images.duckduckgo.com/iur/?f=1&image_host=http%3A%2F%2Fiampierremenard.files.wordpress.com%2F2013%2F12%2Fit-s-over-9000-its-over-9000-29849302-496-370.jpg&u=https://iampierremenard.files.wordpress.com/2013/12/it-s-over-9000-its-over-9000-29849302-496-370.jpg 3/8/2017, 10:08:17 AM - agnivade (Agniva De Sarker): we have finally crossed 9000 stars ! wohoo !! 3/13/2017, 3:47:43 PM - waldyrious (Waldir Pimenta): Ah, crap, I’ve waited for months to say this 😛 3/28/2017, 5:42:15 AM - waldyrious (Waldir Pimenta): Hey @agnivade, do you think this might be useful for the node client? https://www.npmjs.com/docs/orgs/ 3/28/2017, 5:42:24 AM - waldyrious (Waldir Pimenta): The release process, specifically 3/28/2017, 2:55:10 PM - agnivade (Agniva De Sarker): will take a look 4/5/2017, 6:02:30 PM - ostera (Leandro Ostera): hey @agnivade, @waldyrious, do we have analytics on the front-page? I'd like to correlate them with the ones from the web client (thinking it's about time to do a refresh on that front, and maybe start implementing some of the features we talked about on https://github.com/tldr-pages/tldr/issues/1073 4/6/2017, 4:49:45 AM - waldyrious (Waldir Pimenta): Hey @ostera. I am not aware of that, but I'm glad you're aiming to tackle #1073. I'm still to find the time to chew through the backlog of PRs, but I'll help out however I can. 4/6/2017, 5:06:18 PM - agnivade (Agniva De Sarker): > analytics on the front-page? By front-page, you mean the github repo front page ? I remember the analytics discussion we had was around which commands were most commonly used and which ones were searched for but were not present in our repo. There is a traffic page which shows which pages are most commonly visited. But its just that. And I see only curl.md on that list. > and maybe start implementing some of the features we talked about on tldr-pages/tldr#1073 Fantastic ! 4/6/2017, 5:27:23 PM - agnivade (Agniva De Sarker): @waldyrious - I like the concept of orgs. But am concerned about existing users. Everybody is used to `npm install -g tldr`. If we put tldr under an org, that will be a pain point. Other than that, I have no qualms. 4/13/2017, 3:17:00 PM - waldyrious (Waldir Pimenta): @agnivade I didn’t realize the install command would change if we adopted an org. would it have to be namespaced, e.g. like `npm install -g tldr-pages/tldr`? 4/13/2017, 3:19:31 PM - waldyrious (Waldir Pimenta): by the way, I have the day off tomorrow (it’s a holiday here in Portugal), and plan use a portion of that to tackle the PR backlog. It would be great if you, @ostera and @jeeftor were around/available sometime so we could unblock some long-overdue tasks, if needed : ) 4/15/2017, 5:16:55 AM - waldyrious (Waldir Pimenta): @agnivade I’m almost halfway down reviewing the backlog (including issues/PRs that have been closed since I last looked at them), and I gotta say, you’ve been doing a superb work as a maintainer. 👌 👌! I’m really proud to have taken part in helping you join our maintenance team :) 4/15/2017, 4:27:54 PM - agnivade (Agniva De Sarker): > would it have to be namespaced, e.g. like npm install -g tldr-pages/tldr? Yes. > I’m almost halfway down reviewing the backlog Aww yea ! You're on a roll today ! > I’m really proud to have taken part in helping you join our maintenance team :) My pleasure ! 4/15/2017, 4:47:09 PM - waldyrious (Waldir Pimenta): There was an issue with the CLA integration which wasn’t allowing PRs to be merged cleanly. I’ve changed the branch protection settings (there were two cla-assistant checks, and I swapped the one that was marked as required) and this seems to have fixed things :) 1/14/2023, 2:55:32 PM - morrme (morrme) joined the room 4/15/2017, 10:22:04 PM - morrme (morrme): i noticed the cla thing too @waldyrious ...... i kept thinking i missed a step 4/15/2017, 10:50:10 PM - morrme (morrme): also 👏 for knocking out the backlog! i had another PR i wanted to submit but i remember you saying there was a backlog....so i held off. just submitted it today :) 4/16/2017, 11:26:21 PM - waldyrious (Waldir Pimenta): @morrme that’s great to hear! And to anyone else reading this, please don’t let the notion of there being a backlog discourage you from submitting a contribution — in fact, more contributions only make this issue more visible and the fix more urgent (which hopefully will make it happen sooner rather than later). 4/17/2017, 3:00:45 AM - morrme (morrme): thanks @waldyrious ! i have another i want to work on (i guess it's in my personal backlog) so i will try to knock it out soon as well. 4/17/2017, 5:29:36 AM - waldyrious (Waldir Pimenta): :+1: :+1: 4/17/2017, 11:03:30 AM - agnivade (Agniva De Sarker): > There was an issue with the CLA integration which wasn’t allowing PRs to be merged cleanly. I’ve changed the branch protection settings. Ah I was wondering what went wrong again. Thanks for fixing it ! 4/19/2017, 8:55:46 AM - morrme (morrme): @waldyrious sorry for not getting to the curl corrections in time--i see the updated PR 😟 4/19/2017, 8:56:07 AM - morrme (morrme): i had a crazy day and was trying to fit in what i could ....usually i do most of this at night (CST USA) 4/19/2017, 3:19:05 PM - waldyrious (Waldir Pimenta): @morrme no problem at all! this is a volunteer project, there’s no timeline or deadlines to meet :) and there’s always room for further improvement, in future PRs or whatever. 4/19/2017, 3:22:30 PM - waldyrious (Waldir Pimenta): By the way, we are always looking for help maintaining the project to ensure contributions are adequately (and timely) integrated. I was wondering if you, @sbrl and maybe others (nominations welcome!) would be interested :) 1/14/2023, 2:55:39 PM - sbrl (Starbeamrainbowlabs) joined the room 4/19/2017, 3:44:25 PM - sbrl (Starbeamrainbowlabs): Heya! I didn't realise that tldr was on gitter. Yeah, I'm certainly interested in helping out around here. 4/19/2017, 3:44:55 PM - sbrl (Starbeamrainbowlabs): tldr is nice because it only requires a few minutes here and there 😃 4/19/2017, 3:45:25 PM - waldyrious (Waldir Pimenta): I was surprised not to see you in the channel :) it’s great that mentions do ping people who are not here 😃 did you get an email notification or otherwise? 4/19/2017, 3:45:29 PM - sbrl (Starbeamrainbowlabs): My timezone is currently BST (UTC + 1) 4/19/2017, 3:46:11 PM - sbrl (Starbeamrainbowlabs): Yeah, I've actually been sitting on go-gitea/gitea because I've got a bug I really want fixing, so I've had it open in the background 4/19/2017, 3:46:24 PM - sbrl (Starbeamrainbowlabs): Your ping came up as a 1 in a circle in the tab title 4/19/2017, 3:46:46 PM - waldyrious (Waldir Pimenta): hmm, I see. I wonder how that would work for github users who aren’t on gitter 4/19/2017, 3:54:46 PM - sbrl (Starbeamrainbowlabs): Only one way to find out I guess! 4/19/2017, 3:54:53 PM - waldyrious (Waldir Pimenta): Hahaha 4/19/2017, 3:55:23 PM - waldyrious (Waldir Pimenta): I’m sure the opportunity will present itself sometime :) 4/19/2017, 9:04:07 PM - morrme (morrme): @waldyrious i agree with @sbrl ...it is a good one to work with. :) i am still "new" but always happy to help in any way i can! 4/19/2017, 9:07:18 PM - waldyrious (Waldir Pimenta): I’m planning to propose a proper “promotion” policy as soon as I’m done with the review backlog, so that we don’t depend on current maintainers’ recent memory for identifying potential new maintainers :) 4/19/2017, 9:11:01 PM - sbrl (Starbeamrainbowlabs): @waldyrious Sounds good! Count me in 😃 4/19/2017, 9:20:48 PM - morrme (morrme): ➕ 4/19/2017, 9:25:26 PM - waldyrious (Waldir Pimenta): I’ll let you guys know when I make the proposal so you can contribute to the discussion :+1: should be in a few days : ) 4/19/2017, 9:36:03 PM - sbrl (Starbeamrainbowlabs): Sounds good! Thanks, @waldyrious 😃 4/20/2017, 2:14:55 AM - waldyrious (Waldir Pimenta): Did you guys know about the DistroWatch web client for tldr pages?? https://distrowatch.com/dwres.php?resource=man-pages 4/20/2017, 2:14:57 AM - waldyrious (Waldir Pimenta): apparently it was put up in january this year :) 4/20/2017, 2:25:19 AM - sbrl (Starbeamrainbowlabs): Oh awesome! They're a big site, right? 4/20/2017, 3:00:07 AM - waldyrious (Waldir Pimenta): Not sure how big, but they’re quite well-known in the linux world :) 4/20/2017, 9:42:27 AM - agnivade (Agniva De Sarker): I was thinking of asking @sbrl myself about joining the maintainer team. But good that @waldyrious already did 😄 4/20/2017, 9:43:46 AM - agnivade (Agniva De Sarker): > Did you guys know about the DistroWatch web client for tldr pages?? https://distrowatch.com/dwres.php?resource=man-pages 4/20/2017, 9:43:52 AM - agnivade (Agniva De Sarker): oh wow .. who did it ? 4/20/2017, 2:04:45 PM - waldyrious (Waldir Pimenta): No idea, but they announced it back in january, see PR #1342 : ) 4/20/2017, 2:08:33 PM - waldyrious (Waldir Pimenta): As for maintainers, I was thinking we can make an exhaustive list of candidates as soon as we formalize the criteria, but since @sbrl has been consistently active since 2015 (https://github.com/tldr-pages/tldr/commits?author=sbrl), I’m inclined to make him a contributor right away — any objections? 4/20/2017, 5:03:23 PM - agnivade (Agniva De Sarker): No objections - as soon as you give him your rundown of the usual merge process that we follow 😄 4/20/2017, 5:10:38 PM - waldyrious (Waldir Pimenta): Of course :+1: 4/20/2017, 5:20:45 PM - waldyrious (Waldir Pimenta): @sbrl unfortunately this content hasn’t yet been compiled into a streamlined document, but most of the relevant stuff can be found in #1209 4/20/2017, 5:28:25 PM - sbrl (Starbeamrainbowlabs): Ok, I'll have a read of that issue then 4/20/2017, 5:29:11 PM - sbrl (Starbeamrainbowlabs): Is there a bot that could attach a label to abandoned PRs automatically? 4/20/2017, 5:33:20 PM - waldyrious (Waldir Pimenta): I’ll make you a quick summary here in a few minutes — I'm a bit busy with work atm :) 4/20/2017, 5:33:43 PM - sbrl (Starbeamrainbowlabs): sure - I'm in and out this afternoon anyway 😛 4/20/2017, 11:38:26 PM - waldyrious (Waldir Pimenta): sorry, tough day at work 4/20/2017, 11:39:25 PM - waldyrious (Waldir Pimenta): so, the gist of it is: we generally prefer to have at least two maintainers review each PR, so for example if one reviews and approves it, the other can merge the PR once they agree as well (unless someone else raises objections). 4/20/2017, 11:40:26 PM - waldyrious (Waldir Pimenta): if other maintainers are too busy and a PR lingers around for too long without a second maintainer’s approval, they can be merged with a single maintainer’s approval, in the interests of providing a timely response to contributions 4/20/2017, 11:51:36 PM - sbrl (Starbeamrainbowlabs): Sounds sensible to me! 4/20/2017, 11:51:41 PM - sbrl (Starbeamrainbowlabs): Easy to remember, too 😛 4/20/2017, 11:52:05 PM - waldyrious (Waldir Pimenta): I’m still a little busy, I’ll add more stuff if I remember :) 4/21/2017, 12:39:08 AM - waldyrious (Waldir Pimenta): One more thing: generally we try to avoid merge commits, to allow a cleaner git history. If the commits in the PR are worth keeping separately (i.e. they represent semantic changes rather than typo fixes or syntax corrections revealed by TravisCI, have descriptive commit messages, etc.), then the "rebase and merge” option is the preferred one. 4/21/2017, 12:40:14 AM - waldyrious (Waldir Pimenta): otherwise, if they’re just a bunch of commits named “edited command.md” or similar, then the "squash and merge” option is to be used instead. 4/21/2017, 12:42:20 AM - waldyrious (Waldir Pimenta): Another thing: For simple, uncontroversial fixes and typos to PR files, it’s best if the maintainer does them rather than ask the contributor, especially because the actual content-related discussion may end up requiring quite a bit of changes, as you experienced yourself with the composer PR :) 4/21/2017, 12:43:27 AM - waldyrious (Waldir Pimenta): in such cases, it’s preferable to either use “rebase and merge” option on the github web interface, or an interactive rebase in the comand line, to clean up any commits that would need to be squashed, reworded, etc. 4/21/2017, 12:36:54 PM - sbrl (Starbeamrainbowlabs): Ah, right. Yeah - I can see why that would be preferable. 4/23/2017, 2:41:42 PM - sbrl (Starbeamrainbowlabs): Thanks for the invitation, @waldyrious! 4/23/2017, 2:41:43 PM - sbrl (Starbeamrainbowlabs): 😃 4/23/2017, 4:28:16 PM - agnivade (Agniva De Sarker): Welcome to the gang 😉 ! 4/23/2017, 5:02:37 PM - sbrl (Starbeamrainbowlabs): Yay 🎊 4/23/2017, 9:05:21 PM - waldyrious (Waldir Pimenta): @agnivade I just realized you were a member of the tldr-pages org, not an owner. I made you an owner too, which was long overdue :) 4/23/2017, 9:09:05 PM - waldyrious (Waldir Pimenta): btw, we’re down to 15 pending PRs ^_^ 4/24/2017, 2:23:38 AM - morrme (morrme): congrats @sbrl ! 4/24/2017, 2:23:49 AM - morrme (morrme): and well done @waldyrious and @agnivade ! 4/24/2017, 2:24:20 AM - sbrl (Starbeamrainbowlabs): Thanks, @morrme! 4/24/2017, 3:10:39 AM - waldyrious (Waldir Pimenta): Hey guys, this is totally unrelated, but I’d appreciate your thoughts on this little side project of mine :) http://waldyrious.net/unstyle/ 4/24/2017, 8:06:03 PM - sbrl (Starbeamrainbowlabs): Looks interesting! Perhaps useful for studying html structure and renderer behaviour. 4/24/2017, 8:06:16 PM - sbrl (Starbeamrainbowlabs): And we're down to 12 PRs~ 4/24/2017, 8:06:48 PM - waldyrious (Waldir Pimenta): I use it all the time to clean up blog posts and cluttered websites for a cleaner reading experience :) 4/25/2017, 3:50:06 AM - morrme (morrme): wow, that's an excellent use for it! definitely necessary 4/25/2017, 3:38:51 PM - sbrl (Starbeamrainbowlabs): Sounds a bit like something I saw ages ago. Was it...... "readability"? It was bought up by someone and merged into some other product, sadly. Nice to know there's an alternative out there! 4/25/2017, 3:50:37 PM - waldyrious (Waldir Pimenta): Yeah, Readability and Instapaper did/do exactly this, but they are more than just a stylesheet — they incorporate a large library of rules for cleaning up news websites and blogs that are known to have a certain structure (so they can hide everything that isn’t the main content) 4/25/2017, 3:50:47 PM - waldyrious (Waldir Pimenta): I ought to mention them in the README, come to think of it 4/26/2017, 12:18:20 AM - sbrl (Starbeamrainbowlabs): I've had a thought. Is hosting sorted for the tldr bot? If not, what language is it written in? I might be able to run it on my server I rent for my website. It has 4 x cpus, 4GB ram, 40GB ssd. 4/26/2017, 3:40:21 AM - waldyrious (Waldir Pimenta): @agnivade is the person that would know how to respond. But in any case, I really appreciate the offer — tldr-bot is an important piece of the improved contribution experience we want to implement, that’s currently missing. 4/26/2017, 1:07:46 PM - agnivade (Agniva De Sarker): Hey @sbrl - That sounds great ! We really needed a separate hosted server for tldr bot to work properly. Read through [here](https://gitter.im/tldr-pages/tldr?at=585a199d0730ce6937f02224) for extra context. The bot is written in python. Its placed here https://github.com/tldr-pages/tldr/blob/master/scripts/post_pr_comment.py. 4/26/2017, 1:09:21 PM - agnivade (Agniva De Sarker): We just need to divert the logic of posting the comments from being run as a travis handler to code running from inside your machine, and send the details of the PR from the travis failure event. 4/26/2017, 1:09:53 PM - agnivade (Agniva De Sarker): Also, I think @waldyrious had some other ideas for tldr-bot to handle .. I am forgetting which was it. Need to look it up. 4/26/2017, 1:11:47 PM - agnivade (Agniva De Sarker): @sbrl - btw, do you have a domain name (with https) for your server ? I wouldn't want to do this on http. 4/26/2017, 1:17:24 PM - agnivade (Agniva De Sarker): Found it https://github.com/tldr-pages/tldr/issues/1209#issuecomment-270510219 ! @waldyrious - The idea is very nice ! Lets get the server setup .. and I can look into tackling this. 4/26/2017, 2:12:24 PM - sbrl (Starbeamrainbowlabs): Yep, I do have a domain name. I currently own https://starbearainbowlabs.com! 4/26/2017, 2:12:43 PM - sbrl (Starbeamrainbowlabs): And I'm using letsencrypt nginx + php7.1-fpm for the web server. 4/26/2017, 2:14:00 PM - sbrl (Starbeamrainbowlabs): It's an ubuntu 16.04 server, using systemd. Having the bot run as a system service would be preferable. 4/26/2017, 2:15:12 PM - sbrl (Starbeamrainbowlabs): A python bot shouldn't be too much trouble :-) 4/26/2017, 3:43:37 PM - agnivade (Agniva De Sarker): Perfect. Perfect. Perfect. ✨ 4/26/2017, 3:44:04 PM - agnivade (Agniva De Sarker): I am pretty comfortable with nginx+ubuntu 4/26/2017, 3:46:26 PM - agnivade (Agniva De Sarker): So .. I am thinking .. setup the bot service running on a custom port, and have nginx do a proxy_pass to it. That way, we let nginx do the ssl offload and other external stuff. And let the bot just be concerned with its application logic. 4/26/2017, 3:46:45 PM - agnivade (Agniva De Sarker): How does that sound ? 4/26/2017, 3:49:13 PM - sbrl (Starbeamrainbowlabs): Yep, sounds good to me! Why does the bot require a domain name though? 4/26/2017, 4:20:38 PM - agnivade (Agniva De Sarker): No no, bot doesn't require a domain name. But I will need to send POST requests from github CI to the bot server. Therefore, a domain name with https. 4/26/2017, 4:39:13 PM - sbrl (Starbeamrainbowlabs): ah - using hooks then? 4/26/2017, 4:39:49 PM - sbrl (Starbeamrainbowlabs): You can print any domain you have at it if you can - otherwise, I'll use something like tldr.bots.starbeamrainbowlabs.com. 4/26/2017, 5:29:22 PM - waldyrious (Waldir Pimenta): Hey @agnivade and @sbrl, please take a look at https://github.com/tldr-pages/tldr/issues/1350 4/26/2017, 5:29:34 PM - waldyrious (Waldir Pimenta): we may not have to implement the ping functionality ourselves :) 4/26/2017, 5:31:37 PM - sbrl (Starbeamrainbowlabs): Let me know when you're ready to deploy the bot to my server. Having it in a git repository with a deploy key might be a good idea - then to update it I can just do a `git pull && sudo systemctl restart tldr-bot` 4/26/2017, 6:20:07 PM - sbrl (Starbeamrainbowlabs): I have just granted @agnivade access to the new `tldr-bot` account on my server. 5/1/2017, 2:41:06 AM - agnivade (Agniva De Sarker): Hey @sbrl - I have pushed the required files to your server. The service file is giving me slight troubles. Its nearly there but somehow not working perfectly. Can you take a look ? 5/1/2017, 2:41:27 AM - agnivade (Agniva De Sarker): Also, I have pushed the repo to github.com/tldr-pages/tldr-bot 5/1/2017, 2:42:03 AM - sbrl (Starbeamrainbowlabs): Hrm. I'll take a look tomorrow! It's bedtime for me now 😃 It won't * actually * work until I symlink it to the correct directory, btw. 5/1/2017, 2:42:31 AM - agnivade (Agniva De Sarker): Great. thanks. 5/1/2017, 2:42:37 AM - sbrl (Starbeamrainbowlabs): the service file to `/etc/systemd/....` 5/1/2017, 12:40:36 PM - sbrl (Starbeamrainbowlabs): Looks like you forgot the current directory in that service file, @agnivade 5/1/2017, 12:41:01 PM - sbrl (Starbeamrainbowlabs): https://unix.stackexchange.com/a/200657/64687 5/1/2017, 12:41:24 PM - sbrl (Starbeamrainbowlabs): Umm ok never mind 5/1/2017, 12:41:39 PM - sbrl (Starbeamrainbowlabs): Just seen `.bootstraprc` 5/1/2017, 12:47:30 PM - sbrl (Starbeamrainbowlabs): It needed chmodding. It's starting now, but taking a while. 5/1/2017, 12:54:41 PM - sbrl (Starbeamrainbowlabs): Ok, so it started (it's showing up in htop, too), but systemd doesn't appear to notice that it's started correctly. Log file contents: https://hastebin.com/fajavigabu 5/1/2017, 12:55:12 PM - sbrl (Starbeamrainbowlabs): [![Selection_003.png](https://files.gitter.im/tldr-pages/tldr/yeo6/thumb/Selection_003.png)](https://files.gitter.im/tldr-pages/tldr/yeo6/Selection_003.png) 5/1/2017, 12:55:15 PM - sbrl (Starbeamrainbowlabs): htop ------^ 5/1/2017, 12:56:31 PM - sbrl (Starbeamrainbowlabs): Oh and if possible, could the bot please run as the `tldr-bot` user, and not root, please? Thanks 😃 5/1/2017, 12:56:31 PM - sbrl (Starbeamrainbowlabs): I suspect that it's an issue with the `Type=forking` line. Have other flask users encountered anything like this? 5/1/2017, 1:49:33 PM - agnivade (Agniva De Sarker): > I suspect that it's an issue with the `Type=forking` line. Have other flask users encountered anything like this? Yea I also think its something to do with that. I have not googled extensively. Take a look if you can 😄 > Oh and if possible, could the bot please run as the tldr-bot user, and not root, please? Yea sure. I don't see any reason not to. 5/1/2017, 2:14:26 PM - sbrl (Starbeamrainbowlabs): I've updated the service file to run as the tldr-bot user. 5/1/2017, 2:14:39 PM - sbrl (Starbeamrainbowlabs): I've just read the extra section on https://unix.stackexchange.com/a/335886/64687 5/1/2017, 2:14:45 PM - sbrl (Starbeamrainbowlabs): is there any truth to it? 5/1/2017, 3:02:25 PM - waldyrious (Waldir Pimenta): @sbrl I liked your comment in https://github.com/tldr-pages/tldr/issues/1316 :) I made it a saved reply, you might want to do so as well : https://github.com/settings/replies 5/1/2017, 3:02:51 PM - waldyrious (Waldir Pimenta): (unfortunately there doesn’t seem to be a way to define saved replies at the org level) 5/1/2017, 4:35:50 PM - agnivade (Agniva De Sarker): @waldyrious - oh wow .. I never knew about saved replies. This is awesome ! 5/1/2017, 4:42:11 PM - agnivade (Agniva De Sarker): @sbrl - Yea, not adding & makes sense. But he is wrong about not needing `ExecStop`. I was also stunned with this but apparently systemd won't start unless you specify the `ExecStop` stanza. Very weird indeed. 5/1/2017, 4:43:13 PM - agnivade (Agniva De Sarker): But yea .. I think we should move to uWSGI .. the documentation on systemd looks good. And the flask web-server was never meant for production use anyway. 5/1/2017, 4:48:19 PM - agnivade (Agniva De Sarker): I will be busy in some other projects for some time. So feel free to start the work on moving to uWSGI. 5/1/2017, 5:20:34 PM - sbrl (Starbeamrainbowlabs): Oooh cool! I didn't know saved replies existed. I've added it too 😃 5/1/2017, 5:21:16 PM - sbrl (Starbeamrainbowlabs): and @agnivade I'll see if I've got time, but there's a lot of prior reading into python, flask, etc. I'd need to do first to understand it properly. 5/1/2017, 6:29:37 PM - agnivade (Agniva De Sarker): Oh dont bother then .. I thought you were well versed in those areas. I will take a look in a few days time. 5/1/2017, 6:44:14 PM - sbrl (Starbeamrainbowlabs): Nope..... 😛 I'm well-versed in Nginx configuration, Proxying, and networking etc, but not in Python 5/2/2017, 12:19:04 PM - agnivade (Agniva De Sarker): Hey @waldyrious - the move to new page format sounds good. But I would like to finalize on the deployment procedure as there are multiple components at play here. Refer to my comment https://github.com/tldr-pages/tldr/pull/958#issuecomment-260107957 5/2/2017, 12:19:49 PM - agnivade (Agniva De Sarker): Can you come up with the final plan and post it in that thread ? 5/2/2017, 12:21:00 PM - agnivade (Agniva De Sarker): The idea of writing the linter in a fresh way does sound very enticing to me .. I think I want to take a stab at that. But after I complete the pending task of the python bot. 5/2/2017, 12:22:07 PM - agnivade (Agniva De Sarker): I am not in the mood though to touch the old linter again and update the rules to reflect the new pages .. 😖 It will be great if someone else can do that. 5/2/2017, 1:06:13 PM - waldyrious (Waldir Pimenta): by "finalize on the deployment procedure”, do you mean of the tldr-bot? 5/2/2017, 1:06:40 PM - waldyrious (Waldir Pimenta): Sure, we can push back the date for the page content change if needed. I just wanted to get the discussion going 5/2/2017, 1:09:14 PM - waldyrious (Waldir Pimenta): as for the process, if I’m understanding you correctly, the only things needed (apart from the client migration) are changing all pages (which will be done in that PR), and updating the linter (which… I’m not sure how to go about. I am probably even less capable to work with the current linter than you are. If you want to rewrite it, we can certainly wait for that and add it as a subtask or something.) 5/2/2017, 5:01:27 PM - agnivade (Agniva De Sarker): > by "finalize on the deployment procedure”, do you mean of the tldr-bot? No no .. the page format change. 5/2/2017, 5:02:09 PM - agnivade (Agniva De Sarker): > as for the process, if I’m understanding you correctly, the only things needed (apart from the client migration) are changing all pages (which will be done in that PR), and updating the linter (which… I’m not sure how to go about. I am probably even less capable to work with the current linter than you are. If you want to rewrite it, we can certainly wait for that and add it as a subtask or something.) Yes, those are the things that need to be done. 5/2/2017, 5:02:44 PM - agnivade (Agniva De Sarker): But my concern is that the moment we push the new page style .. the existing node client will stop working. 5/2/2017, 5:03:11 PM - agnivade (Agniva De Sarker): So until people actually update their clients, they will end up with a non-working client 5/2/2017, 5:03:25 PM - agnivade (Agniva De Sarker): I am not very comfortable with that 5/2/2017, 5:03:47 PM - agnivade (Agniva De Sarker): That's why I wanted to discuss and finalize the procedure 5/2/2017, 5:04:46 PM - agnivade (Agniva De Sarker): And about the linter, if everyone's okay with waiting .. then that's fine. 5/2/2017, 5:28:48 PM - waldyrious (Waldir Pimenta): The only way to avoid that is to push an update to the node client that supports both formats 5/2/2017, 5:28:57 PM - waldyrious (Waldir Pimenta): does that sound viable? 5/2/2017, 8:29:18 PM - agnivade (Agniva De Sarker): That would mean everyone has to update their clients first, before we push the page change. 5/2/2017, 8:29:39 PM - waldyrious (Waldir Pimenta): yes 5/2/2017, 8:29:47 PM - waldyrious (Waldir Pimenta): but we can’t force that, can we? 5/2/2017, 8:30:04 PM - agnivade (Agniva De Sarker): nope .. 5/2/2017, 8:30:26 PM - agnivade (Agniva De Sarker): frankly, users will get pretty pissed off if they suddenly see their clients are broken .. 5/2/2017, 8:30:58 PM - agnivade (Agniva De Sarker): its a tough nut to crack .. 😑 5/2/2017, 8:32:52 PM - agnivade (Agniva De Sarker): Usually things like these are done in a long period of time. Push a new client which supports both. Give users enough time to update their clients. And then make the format change. 5/2/2017, 8:38:15 PM - agnivade (Agniva De Sarker): Interested to hear @ostera's opinion on this 5/2/2017, 9:13:44 PM - waldyrious (Waldir Pimenta): I think users installing a helper for command-line tools will probably be savvy enough to look up the project page and either submit a bug or figure out that a solution already exists 5/2/2017, 9:14:00 PM - waldyrious (Waldir Pimenta): other than that, the only way to guarantee this is a way for the tool to self-update 5/2/2017, 9:14:14 PM - waldyrious (Waldir Pimenta): like the evergreen browsers do e.g. 5/2/2017, 11:49:11 PM - agnivade (Agniva De Sarker): Yea, but still from a software point of view, the user experience is disrupted. I care about that deeply. Software should just work, as expected, and with minimal interruption. The self-update thing is an elegant way to do that. But sadly its not there 😟 5/3/2017, 2:47:50 AM - waldyrious (Waldir Pimenta): could it be implemented? 5/3/2017, 1:16:27 PM - agnivade (Agniva De Sarker): Unless you update the client, no. 5/4/2017, 1:21:55 AM - sbrl (Starbeamrainbowlabs): @waldyrious Yep, but the client needs updating in order for it to take effect 5/4/2017, 1:22:55 AM - sbrl (Starbeamrainbowlabs): Perhaps we could include a big notice in the README about the recent format change? 5/4/2017, 1:21:39 PM - waldyrious (Waldir Pimenta): sure, although nothing will ever be a 100% guarantee of no user disruption. I’m trying to figure out what steps @agnivade would feel are sufficient. Personally, I don’t think it’s the end of the world if a tldr client stops working and users come to the corresponding issue trackers (or even the main one) trying to figure out how to solve it — for the most part, they’ll be able to simply update and get their problem solved; the rest will either prompt the client author to update, or will contribute fixes themselves 5/4/2017, 2:05:56 PM - waldyrious (Waldir Pimenta): …aaaaand we’re under 10 open PRs!!! 🎉 5/4/2017, 7:08:39 PM - agnivade (Agniva De Sarker): > Personally, I don’t think it’s the end of the world if a tldr client stops working Hmm .. I think I have to disagree on this. Yes, at the end of the day its an open source project. But I feel as maintainers, we owe it to our users to make their lives easier, not harder. For us, it may be second nature to go the the repo home page, when a tool we use breaks, check what the issue is, solve it and be done. But it actually breaks the trust that we have with our users, and it gives the impression that the tool is likely to break again. A lot of open source projects (three.js is a shining example) move fast and as a result their APIs keep changing from release to release. No doubt three.js is pretty damn good, but after some time, it just becomes an exercise with you trying to play catch up with their APIs or fall behind with features. Personally, I detest this sort of development. Anyways, I have given some thought to this. And after weighing the pros and cons, I feel its just not worth it to break the clients over trying to improve the page format. The tradeoff seems too skewed to me. @waldyrious - I know you have been working hard to push this. I respect all that you have done with tldr so far. Rarely have I seen someone so diligent with any open source project. But for this change, it just doesn't feel right with me. This should, in no way stop you guys from going ahead, if you feel otherwise. I am completely okay with that. I greatly appreciate the power of collaboration, and having differences is an integral part of it. But that shouldn't stop things from moving on. 😄 I will still be working on the linter revamp btw. 😉 5/4/2017, 7:17:39 PM - jeeftor (Jeef): I have to agree with @waldyrious that its not a big deal if a client breaks. Especially if its an easy-ish fix to make things work again... 5/4/2017, 7:57:47 PM - waldyrious (Waldir Pimenta): > Yes, at the end of the day its an open source project. Just to clarify, that’s not the reason I said breaking the clients is justifiable. What I meant was that a documentation tool that is only used to look up how to use a given command, is not something that would cause serious problems to a user that temporarily loses access to it. For multiple reasons: (1) that won’t actually stop the commands themselves from working; (2) the commands almost always have `--help`options or manpages; (3) there’s always Google, StackOverflow, explainshell.com, `cheat`, `bropages`, etc. which can assist users when tldr-pages clients can’t; (4) not all of the clients will be broken, and the majority of the the most popular ones already support the new format, or can be adapted quickly; (5) the vast majority of our commands cover unix-based systems, and the intersection of users of such systems and users of command line tools (as opposed to, say, GUI programs) is much likely to know about github and issue trackers than, say, any tech savvy computer users in general that happen to install a package. I could go on, but my overall point is that the practical negative effects are much less severe than if we were talking about a library that is used in other software, or if the commands we cover were mostly about critical tools whose wrongful usage could cause severe damage. Neither is the case. But that said, I do agree that the psychological damage to the trust of users is real, and that leads me to the second point: > A lot of open source projects (three.js is a shining example) move fast and as a result their APIs keep changing from release to release. I would point out that we never changed the format of the pages before, and plan not to do it again (except to add on extra stuff that can be added in separate files, if necessary). The current format was decided without much thought, contrary to the new one, which has been examined by many people, both consumers of the pages and client authors, whose concerns have been addressed. So it is very unlikely that this kind of syntax change will happen again. So breaking the clients once is damaging, sure, but there’s no indication that we’re looking at a regular breakage pattern. 5/4/2017, 8:00:31 PM - waldyrious (Waldir Pimenta): I do appreciate your care and don’t think it is misplaced, but I disagree with the balance you make between the inconvenience to users (which has happened many times before, due to other bugs in the clients, as you’re well aware) and the advantages we’d have by using a more structured format (including one that makes semantic sense in terms of the markup used, while the current one is a bunch of single-item unordered lists interweaved with lines in monospace format) 5/4/2017, 9:51:20 PM - agnivade (Agniva De Sarker): I understand. Fair points. I think we both have put forth our thoughts on the table. Always good to analyze both sides of the argument before taking a decision. Feel free to go ahead with it if you guys are in consensus. 5/4/2017, 9:52:23 PM - agnivade (Agniva De Sarker): btw hooray on reaching less than 10 PRs !! Long time overdue !! 🎉 5/4/2017, 10:04:57 PM - waldyrious (Waldir Pimenta): yes, and let’s make sure we automate maintainership as much as possible to prevent the backlog to grow again :) 5/4/2017, 10:07:41 PM - waldyrious (Waldir Pimenta): as for the syntax change, even if others agree, we still should wait for the linter update, but at least we have a deadline after which we can make the change any time 5/5/2017, 1:25:13 AM - sbrl (Starbeamrainbowlabs): I vote to go ahead with it. It would be cool if there was a poll function here on gitter 5/5/2017, 7:29:16 AM - morrme (morrme): congrats on the PR shrinkage 5/7/2017, 5:05:37 PM - agnivade (Agniva De Sarker): Hey @sbrl - I have updated the service file to run with uswgi and pushed it in the repo. You just need to do an additional `pip install uwsgi`. The extra directives in the nginx section are also mentioned in the repo README. 5/7/2017, 5:05:52 PM - agnivade (Agniva De Sarker): Give it a shot ! 5/7/2017, 5:20:06 PM - sbrl (Starbeamrainbowlabs): @agnivade Awesome! I'll run that pi install now. What's the url of the README again? 5/7/2017, 5:24:10 PM - agnivade (Agniva De Sarker): github.com/tldr-pages/tldr-bot 5/7/2017, 6:12:17 PM - sbrl (Starbeamrainbowlabs): I've adjusted the nginx config, @agnivade 5/7/2017, 6:12:45 PM - sbrl (Starbeamrainbowlabs): What's next? 5/8/2017, 1:20:22 AM - agnivade (Agniva De Sarker): Have you copied the new service file and tried to start the service ? 5/8/2017, 1:20:42 AM - agnivade (Agniva De Sarker): check that it works 5/8/2017, 1:21:07 AM - agnivade (Agniva De Sarker): if yes, then just do a GET request at the /test endpoint and see that if you get an "OK". 5/8/2017, 12:04:26 PM - sbrl (Starbeamrainbowlabs): There - it's configured and started. I had to change a few settings here and there to tweak it to my liking 5/8/2017, 12:04:39 PM - sbrl (Starbeamrainbowlabs): Let me know if that's ok, @agnivade! 5/8/2017, 12:04:43 PM - sbrl (Starbeamrainbowlabs): 😃 5/8/2017, 12:51:04 PM - agnivade (Agniva De Sarker): All good ! Let me run some tests .. then we can close this thing 😄 5/8/2017, 12:51:26 PM - agnivade (Agniva De Sarker): Also, please send a PR with the updated .service file. 5/8/2017, 10:06:16 PM - sbrl (Starbeamrainbowlabs): sure, can do 😃 5/8/2017, 10:08:41 PM - sbrl (Starbeamrainbowlabs): I've created tldr-pages/tldr-bot#1, @agnivade 5/9/2017, 4:17:43 AM - morrme (morrme): awesome work yall! 5/13/2017, 3:12:19 PM - sbrl (Starbeamrainbowlabs): @morrme Thanks 😃 5/14/2017, 3:56:52 AM - morrme (morrme): @waldyrious sorry for the comment on the PR, i feel so picky.... 5/14/2017, 8:27:36 PM - waldyrious (Waldir Pimenta): No problem @morrme, it’s by staying vigilant about these details that we ensure that the project remains consistent and high-quality :) 5/14/2017, 8:27:52 PM - waldyrious (Waldir Pimenta): besides, it’s always better to make the explicit choice to overlook a given guideline or convention, than assuming implicitly that it doesn’t matter. 5/14/2017, 8:43:49 PM - morrme (morrme): yeah, i'm still newish, but from watching all of the feeedback go by as some of these other PRs have been discussed, it makes me think along the same lines.... 5/14/2017, 8:44:54 PM - waldyrious (Waldir Pimenta): :+1: that’s how the project ensures its long-term viability: by embedding these nunaced concepts into a culture rather than a rigid set of rules and guidelines :) 5/15/2017, 1:28:13 AM - morrme (morrme): all i can say is that teaching syntax is one thing, teaching shortcuts is another. the shortcut thing can be a rabbit hole. if you divide readers up between advanced people and beginners new to the command, advanced people are there to grok which option does what, and they know they cna combine when needed...while beginners would be confused by some things being on their own an others "smashed" together 5/15/2017, 1:28:36 AM - morrme (morrme): and they would not be empowered to try things out, they'd be faced with having to do further research/digging 5/15/2017, 1:29:17 AM - morrme (morrme): this has a negative tone, but it isnt intended, which is why i didnt want to type it into the PR comments 5/15/2017, 12:51:03 PM - waldyrious (Waldir Pimenta): I fully get what you mean. But note that e.g. combining two options can have various motivations, not necessarily just being a shortcut for efficiency’s sake 5/15/2017, 12:52:20 PM - waldyrious (Waldir Pimenta): that is a one of the reasons, but if it were the only one it would not make sense for tldr, as you say, since it would put the convenience of the expert above the ability of the beginner to really understand what’s going on (which is what we strive for) 5/15/2017, 12:53:57 PM - waldyrious (Waldir Pimenta): in this case, however, and as I commented on the PR, it has the beginner in mind when it tries to make the options combination easier to memorize while still explaining all parts of it. It does have the benefit of being more compact, which is good for experts, but experts would pick such a compact form anyway (and in many cases already have) 5/15/2017, 12:58:55 PM - waldyrious (Waldir Pimenta): (I’m assuming you’re talking about #1375) 5/15/2017, 10:53:07 PM - morrme (morrme): i am 1/14/2023, 3:02:24 PM - @darless1-58c0c2c9d73408ce4f4f59f0:gitter.im joined the room 5/17/2017, 8:31:50 PM - @darless1-58c0c2c9d73408ce4f4f59f0:gitter.im: First time using tldr and running tldr I get the following: https://pastebin.com/sizhLvQW could someone shed light on this if they know it 5/17/2017, 10:43:30 PM - waldyrious (Waldir Pimenta): That seems to be a problem with the node client. @agnivade is probably the one who can help you. 5/17/2017, 11:03:06 PM - agnivade (Agniva De Sarker): What is the node version that you are running ? tldr needs a minimum node version of 4.7 to run. 5/17/2017, 11:13:01 PM - @darless1-58c0c2c9d73408ce4f4f59f0:gitter.im: @agnivade I was running v0.10.25, installed latest via nodejs docs now I'm running v6.10.3 and tldr is working. Thanks for your help. @waldyrious thank you as well. 5/18/2017, 1:18:35 AM - agnivade (Agniva De Sarker): np 😄 5/18/2017, 1:19:30 AM - sbrl (Starbeamrainbowlabs): @MadRussian Yeah, that looked like your version of node didn't understand the new arrow functions in ES6, which the node client appears to use. 5/18/2017, 2:54:15 PM - waldyrious (Waldir Pimenta): Hey @agnivade, I’ve been wondering: is tldr-bot just a regular github account, or some special account type that could be accessed by multiple people? 5/18/2017, 2:55:40 PM - waldyrious (Waldir Pimenta): also, @agnivade, @sbrl, @ostera, @oxguy3: we need to decide what to do about #799 5/18/2017, 4:39:43 PM - agnivade (Agniva De Sarker): Its just a regular account. 5/18/2017, 4:43:17 PM - agnivade (Agniva De Sarker): About #799, I think we might as well close it and start anew. Its too late to rebase now. @oxguy3 has documented nicely what all he has done. So would not be very difficult(but its gonna be boring!) to replicate them on top of latest master. 5/19/2017, 1:36:13 AM - sbrl (Starbeamrainbowlabs): Hrm. Yeah, I think we need to draw up a list of commands that need moving in a new issue and then create & merge a PR on it 5/19/2017, 1:36:17 AM - sbrl (Starbeamrainbowlabs): or something 5/19/2017, 1:50:22 AM - sbrl (Starbeamrainbowlabs): and @tldr-bot is _really_ lightweight! It's only used ~1.04s of cpu time in 1 week and 3 days, and risen to 31M of ram. I'm impressed! 5/20/2017, 10:36:22 AM - morrme (morrme): not very difficult but boring....seems like a task made for me. 5/23/2017, 1:12:40 AM - sbrl (Starbeamrainbowlabs): Down to 6 PRs! I wonder where they all went..... 😛 5/24/2017, 10:06:29 PM - morrme (morrme): @agnivade 5/25/2017, 11:50:51 PM - agnivade (Agniva De Sarker): Hey @waldyrious - do you know if its possible to give backticks in the command example itself ? I am trying to create a page for ssh-agent, and the linter is not allowing me in any way to escape a backtick. 5/25/2017, 11:56:48 PM - waldyrious (Waldir Pimenta): it looks like wrapping the code span in triple backticks (inline, without having to put the triple backticks in their own lines) allows single backticks to be rendered inside that span, but I’m not sure this is something the linter can understand 5/25/2017, 11:57:12 PM - waldyrious (Waldir Pimenta): let me see if it works here: "abc ```foo`bar``` def" 5/25/2017, 11:57:19 PM - waldyrious (Waldir Pimenta): ah yea, it works too :) 5/25/2017, 11:58:20 PM - waldyrious (Waldir Pimenta): so what I did was this (replacing backticks with, uh… forward ticks?): "abc ´´´foo´bar´´´ def" 5/26/2017, 12:10:57 AM - agnivade (Agniva De Sarker): nope the problem is with the linter .. its doesn't understand that 5/26/2017, 12:11:23 AM - agnivade (Agniva De Sarker): damn I'm stuck now .. and I dont want to touch the linter to fix this 😢 5/26/2017, 12:13:49 AM - sbrl (Starbeamrainbowlabs): Aww no! Write a new one? 5/26/2017, 5:22:52 AM - waldyrious (Waldir Pimenta): I’ll just say that the new page format would solve this issue 😛 5/26/2017, 12:24:13 PM - agnivade (Agniva De Sarker): haha .. thats true 😄 6/8/2017, 2:11:56 AM - sbrl (Starbeamrainbowlabs): I've blogged about tldr-pages! Thought you'd like to see: https://starbeamrainbowlabs.com/blog/article.php?article=posts%2F241-tldr-pages.html 6/8/2017, 8:01:41 AM - waldyrious (Waldir Pimenta): nice post :) sums it up pretty well! 6/8/2017, 11:24:09 AM - sbrl (Starbeamrainbowlabs): @waldyrious Thanks 😃 6/8/2017, 2:36:31 PM - agnivade (Agniva De Sarker): cool ! 6/16/2017, 3:38:12 PM - agnivade (Agniva De Sarker): @sbrl - travis is failing to post to tldr bot. Its getting a 502 6/16/2017, 3:38:14 PM - agnivade (Agniva De Sarker): ``` cat test_result | python scripts/send_to_bot.py Traceback (most recent call last): File "scripts/send_to_bot.py", line 38, in post_comment(PR_NUMBER, comment) File "scripts/send_to_bot.py", line 14, in post_comment f = urllib2.urlopen(req) File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 406, in open response = meth(req, response) File "/usr/lib/python2.7/urllib2.py", line 519, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/python2.7/urllib2.py", line 444, in error return self._call_chain(*args) File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 502: Bad Gateway ``` 6/16/2017, 3:38:26 PM - agnivade (Agniva De Sarker): can you check if you changed anything from your side ? 6/17/2017, 12:10:00 AM - sbrl (Starbeamrainbowlabs): @agnivade Oooh! That's odd. It died for some reason. 6/17/2017, 12:10:35 AM - sbrl (Starbeamrainbowlabs): I've disabled the `StandardError = syslog` directive, so we should get some output in `journalctl -u tldr-bot` next time I think. 6/17/2017, 12:10:52 AM - sbrl (Starbeamrainbowlabs): I need to look into syslog properly and figure out how it works.... 😛 6/17/2017, 12:10:59 AM - sbrl (Starbeamrainbowlabs): I've restarted it, anyway. 6/17/2017, 12:11:21 AM - sbrl (Starbeamrainbowlabs): Not sure why systemd didn't restart, as it's got a `Restart = always` directive set.... 6/17/2017, 12:12:17 AM - sbrl (Starbeamrainbowlabs): I'll also have to configure it so that your `tldr-bot` account can restart it's own service at some point too 6/17/2017, 12:33:24 AM - agnivade (Agniva De Sarker): Please update the code in github too 6/17/2017, 12:36:22 AM - sbrl (Starbeamrainbowlabs): uhh sure 6/17/2017, 12:36:37 AM - sbrl (Starbeamrainbowlabs): But I don't even know if it'll work yet 😉 6/17/2017, 12:37:20 AM - agnivade (Agniva De Sarker): ahh got you. This is just for debugging purposes 6/17/2017, 12:43:36 AM - sbrl (Starbeamrainbowlabs): yep 6/17/2017, 12:43:58 AM - sbrl (Starbeamrainbowlabs): I've edited the service file and left an suitable commit message, anyway 6/28/2017, 7:48:55 PM - sbrl (Starbeamrainbowlabs): 1.2K PRs merged! 🎆 6/28/2017, 8:46:05 PM - waldyrious (Waldir Pimenta): 🔥 🔥 🔥 1/14/2023, 3:02:51 PM - dgadelha (Douglas Gadêlha) joined the room 6/30/2017, 11:12:08 AM - dgadelha (Douglas Gadêlha): Hey guys, in what frequency the web client is updated? A page added 4 days ago (#1415) isn't live in the web client yet 6/30/2017, 2:23:43 PM - waldyrious (Waldir Pimenta): @dgadelha the person who you should ask is @ostera : ) 7/1/2017, 2:44:17 PM - sbrl (Starbeamrainbowlabs): Out of the 9825 commands on the linux.die.net command list, we've got 328 of them documented in tldr-pages, which is about ~3.34% so far! 9497 to go... 1/14/2023, 3:02:53 PM - Jahhein (Jacob Hein) joined the room 7/2/2017, 11:32:31 AM - Jahhein (Jacob Hein): That's pretty good! 7/3/2017, 9:20:04 AM - agnivade (Agniva De Sarker): FYI - A lot of the commands in our repo are non-standard commands which won't be there in the linux.die.net page. However its a good metric to keep an eye on nevertheless. 7/3/2017, 9:20:39 AM - agnivade (Agniva De Sarker): I would say even going to 10% coverage would cover most of the commands people will ever use 7/3/2017, 9:20:57 AM - agnivade (Agniva De Sarker): barring exceptions of course 😉 7/6/2017, 1:45:28 PM - agnivade (Agniva De Sarker): Gitter is open source now, if you didnt already know - https://gitlab.com/gitlab-org/gitter/webapp/ 7/21/2017, 2:06:20 PM - waldyrious (Waldir Pimenta): Great to hear, @agnivade! I was really happy when gitlab bought them :) 7/21/2017, 2:07:39 PM - waldyrious (Waldir Pimenta): Btw just a heads up, I'm going through some very busy times which is why I haven't been keeping up with the repo activity. I'll try to get back on track asap 7/22/2017, 12:30:04 PM - agnivade (Agniva De Sarker): yea I figured. No rush .. me and @sbrl are keeping things in line 😄 7/22/2017, 2:11:49 PM - sbrl (Starbeamrainbowlabs): Yep! I think I'm getting better at this review thing 😛 7/25/2017, 1:31:36 AM - sbrl (Starbeamrainbowlabs): Don't hesitate @mention me if you think I should review a PR. I check my notifications much more often than the PR page itself, and the notifications appear on my phone as emails (which often use as an indicator as to whether I need to check on something) 7/25/2017, 8:50:37 AM - agnivade (Agniva De Sarker): well, so when a PR comes, doesn't that give a notification to you ? Actually any update in the tldr repo should give you a notification. (As it does in my case) 7/25/2017, 11:11:33 AM - sbrl (Starbeamrainbowlabs): It doesn't appear to, no 7/25/2017, 3:43:08 PM - agnivade (Agniva De Sarker): ok, then it only does that for owners. 8/10/2017, 12:13:28 AM - waldyrious (Waldir Pimenta): @sbrl you can watch the repository, then any activity in issues, PRs, etc will give you a notification. 8/10/2017, 12:13:48 AM - waldyrious (Waldir Pimenta): I actually think that's the exact mechanism used for the owners, it's just that github automatically checks that option, which makes sense. 8/10/2017, 12:17:49 AM - waldyrious (Waldir Pimenta): By the way, since I'm not sure I'll be able to produce the proposal for explicit promotion guidelines for contributors (which I've been promising for months now, shame on me) anytime soon, I think it's about time to get @sbrl into the tldr org. Thoughts? 8/10/2017, 12:46:37 AM - sbrl (Starbeamrainbowlabs): @sbrl Ah right. I'll look into that. Thanks :-) 8/10/2017, 7:14:16 PM - agnivade (Agniva De Sarker): > I think it's about time to get @sbrl into the tldr org. Thoughts? Yes, I was about to ping you about this. I agree ! 8/10/2017, 7:20:06 PM - agnivade (Agniva De Sarker): btw - are you back ? or still busy with other stuff ? 8/10/2017, 7:45:17 PM - waldyrious (Waldir Pimenta): Almost back. In the last few days I managed to clear up the hundreds of github notifications from other repos / threads that had accumulated, and now they're pretty much under control. I should be able to start tackling the tldr ones next week. 8/10/2017, 7:48:32 PM - waldyrious (Waldir Pimenta): That said, I did recently have to quit my job and return to the university to finish my PhD, which I must conclude asap because it was financed with a scholarship. 8/10/2017, 7:48:52 PM - waldyrious (Waldir Pimenta): So for the next few months that will be my priority and I won't make any promises regarding larger tasks related to tldr. I will however keep an eye on the notifications and the gitter chat, in case I'm needed for something : ) 8/10/2017, 8:34:25 PM - agnivade (Agniva De Sarker): Oh yea .. finishing a phd is a huge pain. 8/10/2017, 8:35:48 PM - agnivade (Agniva De Sarker): What is your thesis about ? (If you don't mind me asking) 8/11/2017, 12:37:30 AM - waldyrious (Waldir Pimenta): Of course not :) it's about computer-generated holography. Trying to make the process less taxing in terms of memory and/or processing time 8/11/2017, 12:41:38 AM - sbrl (Starbeamrainbowlabs): @waldyrious Cool! 8/11/2017, 12:42:03 AM - sbrl (Starbeamrainbowlabs): and being part of the organisation would be awesome, thanks everyone 😺 8/11/2017, 1:01:32 AM - waldyrious (Waldir Pimenta): Ok then! I've just sent you an invite. As a member, but eventually we'll promote you to owner (just for the sake of the logical progression, not that I don't trust you 😉) 8/11/2017, 1:02:32 AM - sbrl (Starbeamrainbowlabs): Accepted 😃 8/11/2017, 1:04:27 AM - waldyrious (Waldir Pimenta): Welcome! 🎉 Again heheh 8/11/2017, 1:05:10 AM - sbrl (Starbeamrainbowlabs): 😛 8/11/2017, 9:12:38 AM - agnivade (Agniva De Sarker): Wow .. that is an interesting topic indeed. Have fun ! 8/11/2017, 12:11:58 PM - waldyrious (Waldir Pimenta): Thanks, I'll try xD 1/14/2023, 3:03:06 PM - brontosaurusrex (brontosaurusrex) joined the room 8/11/2017, 9:11:38 PM - brontosaurusrex (brontosaurusrex): https://tldr.ostera.io/apt fails, while tldr pdf has it. 8/11/2017, 10:04:23 PM - sbrl (Starbeamrainbowlabs): @waldyrious 8/12/2017, 2:12:32 AM - waldyrious (Waldir Pimenta): Uhh, I think the person to ping is @ostera.. Maybe report an issue in the repo 8/12/2017, 2:21:06 AM - waldyrious (Waldir Pimenta): https://github.com/ostera/tldr.jsx 8/12/2017, 3:02:28 AM - sbrl (Starbeamrainbowlabs): Ah, I looked at the wrong repo 😛 8/13/2017, 1:13:05 PM - agnivade (Agniva De Sarker): @waldyrious - If you have some time, can you look at - https://github.com/tldr-pages/tldr/pull/1434 ? It's something that I would like to get out of the way. 8/13/2017, 3:13:48 PM - waldyrious (Waldir Pimenta): Sure :) I might not be able to do it today, but tomorrow I should have the time to take a look. 8/13/2017, 4:11:25 PM - agnivade (Agniva De Sarker): :+1: 8/20/2017, 9:27:32 PM - agnivade (Agniva De Sarker): @waldyrious - I updated the PR. Not sure you saw or not, pinging here too. 8/21/2017, 7:26:25 PM - waldyrious (Waldir Pimenta): I hadn't seen it, but am taking a look now. Btw: I'm abroad until the end of the month so internet connection (actually, free time, mostly) is scarce, which might explain some delay both here on gitter and on github 9/3/2017, 10:58:49 AM - agnivade (Agniva De Sarker): @/all - We just broke into the 10k stars group of repos !! 🎉 🎆 : Awesome work ppl ! 9/3/2017, 1:26:16 PM - sbrl (Starbeamrainbowlabs): 😃 9/3/2017, 4:00:34 PM - waldyrious (Waldir Pimenta): Oh wow! We gotta do something to celebrate!! 9/3/2017, 4:01:33 PM - waldyrious (Waldir Pimenta): I'm traveling today, but I'll try to find some time, maybe I'll finally hash out the proposal for maintainers guide and contributor evolution guidelines :) 9/3/2017, 4:02:11 PM - waldyrious (Waldir Pimenta): What do you think? Let's focus on big wins that have been in the oven for a while 😃 9/3/2017, 7:55:32 PM - agnivade (Agniva De Sarker): > Oh wow! We gotta do something to celebrate!! Totally ! Too bad we are geographically distributed 😛 > maybe I'll finally hash out the proposal for maintainers guide and contributor evolution guidelines Yes. That would be great ! I think with the PR template done, a lot of things are already falling into line. Now that this repo has reached a certain level of popularity, more people will obviously come up and help out. So fleshing out the maintainer's guide will be very helpful. 9/4/2017, 4:05:05 AM - waldyrious (Waldir Pimenta): I ended up doing a bunch if other stuff in the repo, but hopefully some of them will result in short-term changes as significant as the maintainers guide (in particular, the project rename) 9/4/2017, 7:53:06 PM - sbrl (Starbeamrainbowlabs): Awesome 😃 and too many notifications lol! I think I'll have to find a way to get notifications about new PRs, but not _everything_ that comes with watching the repo. 9/4/2017, 8:51:59 PM - waldyrious (Waldir Pimenta): Heheh 9/4/2017, 8:55:01 PM - waldyrious (Waldir Pimenta): I actually use github almost as a social network: I've got into the habit of treating the notifications page as if it were, say, Facebook's feed, and visit it often 9/4/2017, 8:56:53 PM - waldyrious (Waldir Pimenta): I also avoid clicking on notifications I don't have the time to check / react to at the moment. So the unread notifications will stay there, like when one uses the email inbox as a todo list (which, sadly, I do as well) 9/4/2017, 9:00:40 PM - waldyrious (Waldir Pimenta): Most of the notifications don't require actions from you, actually, so you'll usually open them, quickly read the new stuff and close the tab (or mark it as read if it's a thread you're only following from the sidelines). It may seem overwhelming at first, but the project activity waxes and wanes over time, and I find it useful to have a finger in the pulse of the projects I follow, even when I don't participate in the discussions myself. 9/4/2017, 9:02:40 PM - waldyrious (Waldir Pimenta): That said, be extra careful to avoid feeling burned out! Take some time off if the maintenance work starts feeling taxing or unpleasant. Good maintainers are hard to come by so it's important to keep the ones we have happy :) 9/4/2017, 9:34:33 PM - sbrl (Starbeamrainbowlabs): Ah, thanks for the insight 😃 9/4/2017, 9:34:38 PM - sbrl (Starbeamrainbowlabs): It's really helpful :-) 9/4/2017, 9:56:41 PM - waldyrious (Waldir Pimenta): I'm glad to hear that : ) 9/5/2017, 12:41:49 AM - agnivade (Agniva De Sarker): Glad to see @waldyrious back in form. :) I hope you are not neglecting that thesis of yours 😉 9/5/2017, 1:10:10 AM - waldyrious (Waldir Pimenta): Uh.. Let's not talk about that xD 9/5/2017, 1:12:47 AM - waldyrious (Waldir Pimenta): (it's actually kinda stressful to fight my urge to get involved in multiple projects all the time, which in the long run end up spreading me thin... That's why I'm so glad to have to you and @sbrl around ^^) 9/5/2017, 1:20:50 AM - sbrl (Starbeamrainbowlabs): Aww, thanks! I'll be starting my third year at uni this October - any advice? 9/5/2017, 1:35:20 AM - waldyrious (Waldir Pimenta): PhD work is quite different from regular coursework, where your more likely to have a blueprint to follow. What I'd suggest is to take any opportunity to expand skills in areas of your own interests while doing the required assignments 9/5/2017, 1:40:08 AM - waldyrious (Waldir Pimenta): For example, using a programming language of your choice to implement some task, or working in an open source project related to one of the classes you'll be taking, etc. 9/5/2017, 1:46:14 AM - waldyrious (Waldir Pimenta): These days, practical knowledge, and networking within the communities where you'll later be working in, are just as valuable (if not more) as a degree, so keep that in mind :) 9/5/2017, 1:48:31 AM - waldyrious (Waldir Pimenta): s/your/you're/ 😳 9/5/2017, 3:11:28 AM - sbrl (Starbeamrainbowlabs): Ah, thanks! I'll certainly bear that in mind 😺 1/14/2023, 3:03:20 PM - jayvdb (John Vandenberg) joined the room 9/5/2017, 4:20:04 PM - jayvdb (John Vandenberg): hiya, just a heads up, I am running a coding competition in Indonesia for high school students (https://www.facebook.com/BesutKode/) , and one of their first tasks is to create a tldr .md file on a fork. We dont expect them to do a pull request, as they are typically just beginners, and neither tldr nor I wants to manage a public mess as they learn PRs in your repo. I dont have any specific plan for *all* those .md files to be PR'd by the student, as they have lots of other increasingly difficult tasks to do that dont involve social interactions. If they cant do the technical tasks (i.e. follow technical instructions), they are eliminated. If they can do the tasks, we teach them the social aspects, safely, but that is only a small subset of the students. 9/5/2017, 4:21:40 PM - jayvdb (John Vandenberg): We are not requiring that their .md files are particularly good. The first task is about teaching them forking, markdown and CI. They usually make a bit of mess in their fork 😉 9/5/2017, 4:24:46 PM - sbrl (Starbeamrainbowlabs): Ah, thanks for the notice! If we do get any PRs since they'll show up as first-time contributors I'll go extra-easy on them 😛 Seriously though, they should be fine - we've got since decent guidelines set out already, so it shouldn't be too much of a problem 😺 9/5/2017, 4:28:00 PM - jayvdb (John Vandenberg): Ya, but I dont want to drown them the guidelines and such at this stage. I picked tldr because it is very probable that they could create PRs and get them merged, but I havent planned out that part of it yet, except that the top 15 or so will be competent and can do it easily. 9/5/2017, 4:33:07 PM - jayvdb (John Vandenberg): The best I could do at the moment is share our google spreadsheet with someone who is interested in looking at the forks doing assessment there : submit PR vs cherry-pick vs discard as junk 😉 9/5/2017, 4:33:31 PM - waldyrious (Waldir Pimenta): That would be very helpful : ) 9/5/2017, 4:35:06 PM - waldyrious (Waldir Pimenta): And thanks for picking tldr. I know it was a pragmatic decision but I think all parts involved have a lot to gain from this, so we'll do our best to help this experiment go as smoothly as possible. 9/5/2017, 4:40:08 PM - jayvdb (John Vandenberg): ok, I've added you @waldyrious , and now I see your profile ... I know who you are ... haha! 9/5/2017, 4:42:30 PM - waldyrious (Waldir Pimenta): Oh, you're *that* John Vandenberg! Haha small world :) how are you doing? 9/5/2017, 4:43:31 PM - jayvdb (John Vandenberg): yup, that one. The other one is a fashion model and ... not me 9/5/2017, 4:43:36 PM - jayvdb (John Vandenberg): not bad. 9/5/2017, 4:44:16 PM - waldyrious (Waldir Pimenta): Hahaha. Great to see you're still innovating with openness-related projects 😉 9/5/2017, 4:44:56 PM - jayvdb (John Vandenberg): I was doing open source before open content was a thing 😉 and now returning a bit to my roots 9/5/2017, 4:45:16 PM - jayvdb (John Vandenberg): there is a thread about another part of the Besut Kode program at https://www.facebook.com/groups/wikipediaweekly/permalink/1421641337883693/ 9/5/2017, 4:46:17 PM - waldyrious (Waldir Pimenta): So I got access to the spreadsheet, thanks. Hopefully it can assist during this process. And of course, do let us know if you need anything (and feel free to point the participants here as well) 9/5/2017, 4:47:18 PM - waldyrious (Waldir Pimenta): Thanks for the link, I've saved it to read later 9/5/2017, 4:47:20 PM - jayvdb (John Vandenberg): great ... so you're main focus would be the "Documentation 1" sheet 9/5/2017, 4:47:52 PM - waldyrious (Waldir Pimenta): Ah that's helpful. I was a bit lost tbh xD 9/5/2017, 4:48:21 PM - waldyrious (Waldir Pimenta): Any plans to add a legend for what the colors mean? 9/5/2017, 4:49:00 PM - waldyrious (Waldir Pimenta): Also, would it be helpful if we provided a list of commands that need documentation, or is that part of their assignment? 9/5/2017, 4:49:47 PM - jayvdb (John Vandenberg): we let them choose, but it wouldnt hurt to give them a list of commands that you want documented, or an ideas list 9/5/2017, 4:51:40 PM - jayvdb (John Vandenberg): I've given you access to the repo where we put all the final versions of the level 1 tasks - let me know any changes you want done 9/5/2017, 4:52:23 PM - waldyrious (Waldir Pimenta): Ok. I've been planning to compile such a list, and hopefully will achieve that soon, but for now there are a bunch of resources at #1070 9/5/2017, 4:52:26 PM - jayvdb (John Vandenberg): cc @yukiisbored ^ 9/5/2017, 4:55:16 PM - waldyrious (Waldir Pimenta): One minor question: I've added the spreadsheet to a folder on my Google drive, and in the folder view, the "detail" pane has a "description" field for that file. I wrote "test' there. I can you check if that is a note for me only or whether it's shared with anyone with access to the document? 9/5/2017, 4:59:14 PM - jayvdb (John Vandenberg): Only mentors can see that spreadsheet, so add any notes you want to it 9/5/2017, 5:00:40 PM - waldyrious (Waldir Pimenta): It was more a concern of noise than privacy, but thanks for confirming : ) 9/5/2017, 5:02:33 PM - waldyrious (Waldir Pimenta): Gotta get back to work, but I'll check back here regularly. Cheers! 9/5/2017, 5:31:45 PM - jayvdb (John Vandenberg): fwiw, our second documentation task is to create a gitbook, using asciinema , like https://bekicot.gitbooks.io/mailcatcher/content/ 9/5/2017, 8:13:49 PM - waldyrious (Waldir Pimenta): :+1: 9/7/2017, 12:49:56 AM - agnivade (Agniva De Sarker): Wow .. I am really humbled at this news. Thanks @jayvdb ! 9/7/2017, 12:50:12 AM - agnivade (Agniva De Sarker): I think it's an excellent idea to point the participants to the gitter chat. 9/7/2017, 12:50:48 AM - agnivade (Agniva De Sarker): That way they can ask questions without feeling any pressure .. 9/7/2017, 12:52:28 AM - agnivade (Agniva De Sarker): And btw - all issues marked "up-for-grabs" are welcome to be taken up and sent a PR 9/7/2017, 12:52:29 AM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr/issues?q=is%3Aissue+is%3Aopen+label%3A%22up+for+grabs%22 9/9/2017, 7:41:05 PM - jayvdb (John Vandenberg): @agnivade , gitter is public, and kids are ... kids ... so I dont want them on gitter for our first tasks. I dont want responsibility for them creating a google identity problem for themselves. We have a private telegram room at the moment. We'll introduce them to gitter towards the end of the program, for only the students who are sensible, and by then they have adjusted to open source projects being semi serious, and not 'facebook' / 'instragram'. 9/9/2017, 7:47:57 PM - sbrl (Starbeamrainbowlabs): :+1: 9/10/2017, 4:09:33 PM - jayvdb (John Vandenberg): have you considered joining Google Code-in, perhaps as part of an 'umbrella' organisation like FOSSASIA ? 9/11/2017, 9:49:20 AM - agnivade (Agniva De Sarker): Hmm .. didn't know about that. But we participated in last year's Hacktoberfest ! And hopefully will do this year too :) 9/11/2017, 9:50:49 AM - agnivade (Agniva De Sarker): On a side note - it's interesting to see that inspite of having a PR template checklist, people ignore that completely and still send malformed PRs. I guess unless something is forced, its hard to change one's habit 😑 9/11/2017, 1:40:57 PM - sbrl (Starbeamrainbowlabs): @agnivade Indeed! So long as you have X, there will always be people who ignore it 😛 What's hackoberfest? 9/11/2017, 2:57:44 PM - waldyrious (Waldir Pimenta): @jayvdb that would be a great idea! How available are mentors expected to be during the Code-in period? Say, one daily meeting? One a week? Several a day? 9/11/2017, 2:58:15 PM - waldyrious (Waldir Pimenta): That could be an issue because at the moment there are only 3 regularly active maintainers (if I could be considered "regularly" active...) 9/11/2017, 2:59:13 PM - waldyrious (Waldir Pimenta): @agnivade I didn't realize there were that many malformed PRs. I haven't been able to catch up to the last dozen or so PRs I haven't reviewed yet, so I haven't seen the latest ones. 9/11/2017, 2:59:49 PM - waldyrious (Waldir Pimenta): Do you think it could be that the PR template is too overbearing? Maybe we could shorten the checklist and simplify the language... 9/11/2017, 3:03:16 PM - waldyrious (Waldir Pimenta): @sbrl hacktoberfest is a yearly informal event organized by DigitalOcean (in partnership with GitHub, it seems?), where anyone who signs up and submits one or more PRs labeled "hactoberfest" to a FOSS project that gets merged during the month of October, will get a t-shirt and some stickers sent to them for free 9/11/2017, 3:03:23 PM - waldyrious (Waldir Pimenta): https://hacktoberfest.digitalocean.com/ 9/11/2017, 3:08:38 PM - sbrl (Starbeamrainbowlabs): @waldyrious Ah, cool! That sounds awesome. A great way to get people into open source :-) 9/11/2017, 3:09:32 PM - sbrl (Starbeamrainbowlabs): I haven't noticed too many PRs that don't follow the template guidelines, but there is quite a bit of text there. Maybe 'short and sweet' as they say would work better? 9/11/2017, 3:10:20 PM - waldyrious (Waldir Pimenta): yeah! and the best part is, us as maintainers don't have to do much, just add the label to issues so PRs can be opened against them 9/11/2017, 3:11:04 PM - waldyrious (Waldir Pimenta): as long as the issues are well described and actionable, and we have contribution guidelines, it's quite a hands-off thing, which is great : ) 9/11/2017, 5:21:28 PM - sbrl (Starbeamrainbowlabs): 😺 9/11/2017, 10:15:42 PM - jayvdb (John Vandenberg): In GCI, you allocate multiple mentors to each task, and when a student submits a task it must be accepted or rejected with 36hrs iirc 9/11/2017, 10:17:50 PM - jayvdb (John Vandenberg): It sounds like you have enough active maintainers to handle having a few tasks available. You could probably handle 5 at a time. 9/11/2017, 10:19:19 PM - jayvdb (John Vandenberg): The best tasks are 'repeatable'. Each student has the same task. e,g, 'create a .md for a missing posix command' , with more info to help them understand it 9/11/2017, 10:19:50 PM - jayvdb (John Vandenberg): As you encounter errors, you improve the task description a bit 9/11/2017, 10:21:07 PM - jayvdb (John Vandenberg): Eventually the mentor either says rtfm, or approves. Not much complex communications require after the task template is well written 9/11/2017, 10:21:32 PM - waldyrious (Waldir Pimenta): We can certainly give it a try. When does the next edition start? 9/11/2017, 10:22:23 PM - jayvdb (John Vandenberg): End of November usually 9/11/2017, 10:22:56 PM - jayvdb (John Vandenberg): Orgs have to submit their list of tasks mid october usually 9/11/2017, 10:23:21 PM - waldyrious (Waldir Pimenta): Ok. @agnivade, @sbrl do you guys want to give it a shot? 9/11/2017, 10:23:43 PM - jayvdb (John Vandenberg): Orgs need to submit 70-100 tasks. Which is why you would need to be a sub-org 9/11/2017, 10:24:07 PM - waldyrious (Waldir Pimenta): yeah, makes sense : ) 9/11/2017, 10:24:33 PM - jayvdb (John Vandenberg): FOSSASIA is the main 'umbrella' org for smaller unaffiliated projects 9/11/2017, 10:25:39 PM - sbrl (Starbeamrainbowlabs): Umm yeah - that sounds good! I might be able to help out :-) I'm in GMT (BST atm actually) myself, so I can probably cover some time there 9/11/2017, 10:25:48 PM - sbrl (Starbeamrainbowlabs): How do we sign up? 9/11/2017, 10:25:56 PM - jayvdb (John Vandenberg): my main org coala was part of FOSSASIA last year. This year we're planning to apply to be an org 9/11/2017, 10:27:21 PM - jayvdb (John Vandenberg): I dont know how to signup precisely 😉 9/11/2017, 10:28:39 PM - waldyrious (Waldir Pimenta): I'm in WET so I don't add that much extra time zone coverage, but at least it's an extra pair of eyes/hands to help out :) 9/11/2017, 10:29:37 PM - jayvdb (John Vandenberg): I guess contact https://blog.fossasia.org/author/mario-behling/ if you want to join FOSSASIA 9/11/2017, 10:31:02 PM - jayvdb (John Vandenberg): If the tasks were mainly .md about linters , maybe you could fit under the coala umbrella 9/11/2017, 10:32:01 PM - waldyrious (Waldir Pimenta): maybe we could try that as a first experiment 9/11/2017, 10:36:49 PM - jayvdb (John Vandenberg): either way, the Besut Kode documentation task is roughly all you need for a GCI 'beginner' task, re-translated back to English of course 9/11/2017, 10:37:30 PM - jayvdb (John Vandenberg): And then write another task for the first pull request, mostly links to your existing guidelines 9/11/2017, 10:43:31 PM - sbrl (Starbeamrainbowlabs): I guess! I at least am not in asia though, so does that mean I can't take part? 9/11/2017, 11:05:15 PM - jayvdb (John Vandenberg): No. FOSSASIA has mentors from everywhere; the students who to tasks offered by FOSSASIA are typically Asian, but not required. Last year an East European girl was one of their winners. 9/11/2017, 11:06:46 PM - sbrl (Starbeamrainbowlabs): Ah, ok! Thanks for clearing that up :-) 9/11/2017, 11:09:33 PM - agnivade (Agniva De Sarker): So.. a task is basically a description of how to send a PR ? Maybe I am a bit confused here - is a student supposed to send a PR ? Or is he supposed to mail me the .md file ? 9/11/2017, 11:17:03 PM - jayvdb (John Vandenberg): you define the tasks however you want. I suggest the frst task is ' write an .md in a fork ', followed by a separate task for submitting those changes as a PR. That prevents you from having shitty .md's in messy PRs. 9/11/2017, 11:20:02 PM - agnivade (Agniva De Sarker): Got it. 9/11/2017, 11:20:45 PM - agnivade (Agniva De Sarker): So .. Nov end .. Let's see. If I don't have too much of a workload, I am willing to give it a shot. I don't want to overcommit and do a half-assed effort. 9/11/2017, 11:21:24 PM - agnivade (Agniva De Sarker): I am from India btw. So TZ shouldn't be an issue. 9/12/2017, 1:10:33 AM - sbrl (Starbeamrainbowlabs): I'll help out with reviewing them as usual. I assume the instructions will request that PRs will be prefixed for identification? I'm happy to help with other related tasks too, if I'm given instructions :-) 9/12/2017, 4:07:14 PM - waldyrious (Waldir Pimenta): @jayvdb could you provide us with a list of linters so we could prepare to participate under the coala umbrella? 9/12/2017, 4:17:10 PM - jayvdb (John Vandenberg): Are we allowing shell builtins in tldr common ? e.g. https://raw.githubusercontent.com/haruute0/tldr/master/pages/sunos/logout.md , @yukiisbored 9/12/2017, 4:19:49 PM - jayvdb (John Vandenberg): > $ echo $(cd coala-bears && git grep "executable='" | sed -e "s/^[^']*'//;s/'.*//;" ) > apertium_lint astyle cppcheck cppclean cpplint flawfinder mcs indent cmakelint coffeelint dockerfile_lint puppet-lint tomlv postcss csscomb csslint stylelint csvlint dartanalyzer elm-format licensecheck textlint dennis-cmd errcheck goimports golint goreturns gotype go gofmt ghc-mod hlint bootlint httpolice java infer eslint happiness cr jshint standard julia chktex luacheck remark alex proselint scspell write-good perlcritic phpcs php phpmd pug-lint bandit pydocstyle pyflakes pylint pycodestyle Rscript Rscript rstcheck rubocop reek ruby java scss-lint shellcheck sqlint stylint tailor tslint verilator perl vint xmllint ramllint travis yamllint 9/12/2017, 4:20:05 PM - jayvdb (John Vandenberg): @waldyrious ^ that is a good start 😉 9/12/2017, 4:20:31 PM - jayvdb (John Vandenberg): https://github.com/coala/coala-bears/ 9/12/2017, 4:21:29 PM - jayvdb (John Vandenberg): And then we can mine the coala-bears PRs and issues for more linters we dont yet support 9/12/2017, 4:37:19 PM - waldyrious (Waldir Pimenta): Great! We can make a tracking issue similar to #1162 9/12/2017, 4:51:07 PM - waldyrious (Waldir Pimenta): #1488 9/12/2017, 4:51:30 PM - waldyrious (Waldir Pimenta): Those are more than enough for a start :) 1/14/2023, 3:03:56 PM - sils (Lasse Schuirmann) joined the room 9/12/2017, 6:05:48 PM - sils (Lasse Schuirmann): Hi tldr people :) 9/12/2017, 6:06:42 PM - waldyrious (Waldir Pimenta): Welcome! 9/12/2017, 6:10:04 PM - sils (Lasse Schuirmann): @jayvdb CCed me on https://github.com/tldr-pages/tldr/issues/1488 - I'm super happy to see this. whoami anyway: I'm Lasse, one of the original creators of coala, nowadays not that much involved anymore esp not from the technical PoV but we started working on gitmate.io as a startup which grew out of the project automation needs we had in coala. Thanks to some government funding I'm working full time on that now - which is great: right now our main aim is basically automating maintenance tasks for open source projects :) 9/12/2017, 6:11:50 PM - waldyrious (Waldir Pimenta): Wow, that's something I've been thinking a lot about these days! 1/14/2023, 3:03:58 PM - yukiisbored (Yuki) joined the room 9/12/2017, 6:12:36 PM - yukiisbored (Yuki): @jayvdb I don't think there's a problem with documenting shell built-ins but something that's specific to a shell may be a problem 9/12/2017, 6:12:52 PM - yukiisbored (Yuki): but generic stuff like logout should be ok 9/12/2017, 6:13:07 PM - waldyrious (Waldir Pimenta): We'd love to give some of your tools a try : ) we're a very small maintenance team, so we take any help we can get from bots and automation tools. 9/12/2017, 6:13:38 PM - sils (Lasse Schuirmann): gitmate.io is ready to roll and MIT licensed 9/12/2017, 6:14:13 PM - sils (Lasse Schuirmann): @waldyrious actually would you mind having a quick call with us about this? We're trying to get as much information about your needs so we develop into the right direction 9/12/2017, 6:14:28 PM - waldyrious (Waldir Pimenta): @sils just a quick suggestion: as a user, I'd have preferred if the homepage had a way to learn about gitmate's features, before starting the signup process (clicking the blue buttons) 9/12/2017, 6:14:39 PM - waldyrious (Waldir Pimenta): sure thing 😃 9/12/2017, 6:14:42 PM - waldyrious (Waldir Pimenta): I'd love to. 9/12/2017, 6:15:38 PM - sils (Lasse Schuirmann): filed your issue at https://gitlab.com/gitmate/open-source/gitmate-2-frontend/issues/42 9/12/2017, 6:15:47 PM - waldyrious (Waldir Pimenta): ❤️ 9/12/2017, 6:15:56 PM - waldyrious (Waldir Pimenta): you guys are quick :) 9/12/2017, 6:15:59 PM - sils (Lasse Schuirmann): for the call, just pick a `datetime` at calendly.com/sils 9/12/2017, 6:17:31 PM - sils (Lasse Schuirmann): I am in the very comfortable position to work full time on almost exclusively open source stuff on my own startup idea :) 9/12/2017, 6:20:13 PM - waldyrious (Waldir Pimenta): I'm really happy for you. I feel constantly disheartened at the amount of work people could be doing (out of intrinsic motivation, even) but aren't due to external constraints. Like that saying about how many Einsteins might have spent their entire lives working in a factory to feed their family. It's really quite wasteful, and sad. 9/12/2017, 6:22:20 PM - sils (Lasse Schuirmann): thanks for the event 9/12/2017, 6:22:40 PM - waldyrious (Waldir Pimenta): :+1: 9/12/2017, 6:29:12 PM - sils (Lasse Schuirmann): @waldyrious seeing forward to that, right now having some bugs to fix, also the update of the landing page isn't on the top of our prio list right now because we're more into getting to know our clients than actually selling stuff so far but it's good feedback that we will address hopefully within ~2weeks. 9/12/2017, 6:30:24 PM - waldyrious (Waldir Pimenta): No problem, I didn't expect an immediate fix anyway : ) 9/12/2017, 6:30:47 PM - sils (Lasse Schuirmann): actually @waldyrious did you ever think of using an automatic text summary algorithm? 9/12/2017, 6:31:07 PM - waldyrious (Waldir Pimenta): Not really. Tell me more! 9/12/2017, 6:31:34 PM - sils (Lasse Schuirmann): I mean obv it's not going to be as good as a human summary but algorithms exist to basically figure out important parts of texts 9/12/2017, 6:31:57 PM - sils (Lasse Schuirmann): I had actually tried one on the wikipedia article about automatic text summarization and it was pretty decent 9/12/2017, 6:32:08 PM - sils (Lasse Schuirmann): https://pypi.python.org/pypi/sumy 9/12/2017, 6:32:12 PM - sils (Lasse Schuirmann): first command under "usage" 9/12/2017, 6:32:14 PM - waldyrious (Waldir Pimenta): But are you talking about tldr pages specifically? 9/12/2017, 6:32:37 PM - sils (Lasse Schuirmann): I'm thinking something like that could be used to auto sum up manpages where no human version exists yet 9/12/2017, 6:32:55 PM - sils (Lasse Schuirmann): smth like "hey we didn't write a TLDR for this yet but here's a generated one, please rate it" 9/12/2017, 6:33:22 PM - waldyrious (Waldir Pimenta): Ok, but in our case the format is quite specific, example-based 9/12/2017, 6:33:45 PM - sils (Lasse Schuirmann): algorithms can be changed to search for those examples 9/12/2017, 6:33:56 PM - sils (Lasse Schuirmann): dunno that was just an idea 😉 9/12/2017, 6:34:14 PM - sils (Lasse Schuirmann): cause eventually I want gitmate to sum up long issues 9/12/2017, 6:34:28 PM - sils (Lasse Schuirmann): sometimes we have huge issues at coala and I really don't manage to read through the whole ... conversation 9/12/2017, 6:34:46 PM - waldyrious (Waldir Pimenta): We do aim to sort of "tell a story", i.e. ensure we start with simpler invocations and gradually build up to more complexity, but I am having trouble imagining a generic text summarizer being able to produce a list of examples from a manpage (unless it already has an EXAMPLES section, of course) 9/12/2017, 6:35:11 PM - sils (Lasse Schuirmann): I'm just saying the result might be better than "This article doesn't exist yet" 9/12/2017, 6:35:22 PM - waldyrious (Waldir Pimenta): Yeah, that is one of the topics I'd love to dive into sometime: tools to enhance structured discussion in digital platforms 9/12/2017, 6:36:02 PM - waldyrious (Waldir Pimenta): Yes, definitely. I think the best bang-for-the-buck option in ourt case could actually to parse manpages looking for EXAMPLES sections, which are already quite close to the format we use 9/12/2017, 6:36:52 PM - waldyrious (Waldir Pimenta): TBH something cleverer doesn't strike me as viable at the moment, unless someone specifically works with that (e.g. by creating a machine learning model focused on that) 9/12/2017, 6:37:11 PM - sbrl (Starbeamrainbowlabs): Sounds like a good idea! Would take some development effort though. Open an issue? 9/12/2017, 6:37:38 PM - waldyrious (Waldir Pimenta): In fact, I don't think we have an issue to track the task I mentioned -- we definitely should 9/12/2017, 6:38:18 PM - sils (Lasse Schuirmann): speaking of filing issues, check out https://gitter.im/coala/corobo 😛 9/12/2017, 6:38:34 PM - * sils (Lasse Schuirmann) misses being able to `corobo file issue` in this gitter channel to have the conversation linked 9/12/2017, 6:38:57 PM - sils (Lasse Schuirmann): https://github.com/coala/corobo I mean 9/12/2017, 6:39:34 PM - waldyrious (Waldir Pimenta): lol, it also needs some intro documentation :) 9/12/2017, 6:39:47 PM - sils (Lasse Schuirmann): yeah I just noticed that 😛 https://github.com/coala/corobo/issues/289 9/12/2017, 6:42:24 PM - waldyrious (Waldir Pimenta): haha 😃 9/12/2017, 6:45:26 PM - sils (Lasse Schuirmann): to sum it up it's a chatbot that does stuff like filing issues but also assigning people 9/12/2017, 6:45:44 PM - sils (Lasse Schuirmann): cause you don't want to give all new contributors write access still you don't want to assign them all by hand 9/12/2017, 6:45:55 PM - sils (Lasse Schuirmann): esp if your issues already have a label for like newcomer issues 9/12/2017, 6:46:16 PM - sils (Lasse Schuirmann): the bot autoinvites them into the org, assigns them, marks PRs wip/pending review and stuff like that 9/12/2017, 6:46:21 PM - sils (Lasse Schuirmann): without any admin having to be involved 9/12/2017, 6:46:23 PM - sbrl (Starbeamrainbowlabs): That would be `up for grabs` 9/12/2017, 6:46:29 PM - sils (Lasse Schuirmann): like a unix binary with an s flag 9/12/2017, 6:46:35 PM - sils (Lasse Schuirmann): yep 9/12/2017, 6:48:32 PM - waldyrious (Waldir Pimenta): just created #1489 for the EXAMPLES sections import :) 9/12/2017, 6:49:21 PM - sbrl (Starbeamrainbowlabs): :+1: 9/12/2017, 6:50:59 PM - waldyrious (Waldir Pimenta): btw @sils have you been in touch with @RichardLitt yet? He's been working on pretty similar problems (https://maintainer.io/) 9/12/2017, 6:56:54 PM - sils (Lasse Schuirmann): interesting, I tried something like that with osbusiness.viperdev.io but never went serious about that; I also never got any feedback or interest on that though 9/12/2017, 6:57:36 PM - waldyrious (Waldir Pimenta): Yeah, this is a problem most people don't even realize they have 9/12/2017, 6:57:42 PM - waldyrious (Waldir Pimenta): until they burn out 😟 9/12/2017, 6:58:26 PM - sils (Lasse Schuirmann): but also I was hoping that some companies would pay decently for that 9/12/2017, 6:59:22 PM - waldyrious (Waldir Pimenta): I'm sure they would, after they recognize the benefits. But I'm convinced that in things like this, you can't really convince people of the value of a thing, they have to see it by themselves 9/12/2017, 6:59:43 PM - waldyrious (Waldir Pimenta): like the thing they say that Wikipedia is a project that only works in practice, never in theory? 9/12/2017, 6:59:49 PM - sils (Lasse Schuirmann): yep that's the problem, you need the early adopters 9/12/2017, 6:59:58 PM - waldyrious (Waldir Pimenta): Because most of the benefits are indirect 9/12/2017, 7:00:24 PM - sils (Lasse Schuirmann): when we focused on code analysis with gitmate we saw the same problem, people just wouldn't see the benefit because it's not direct enough 9/12/2017, 7:00:59 PM - waldyrious (Waldir Pimenta): yeah, it sucks 9/12/2017, 7:06:35 PM - sils (Lasse Schuirmann): contacted richard :+1: 9/12/2017, 7:06:57 PM - waldyrious (Waldir Pimenta): nice! keep me posted about any updates 😃 9/12/2017, 7:07:33 PM - sils (Lasse Schuirmann): you know him? 9/12/2017, 7:08:44 PM - waldyrious (Waldir Pimenta): Kind of. We had exchanged messages in a few threads in projects we both were involved, and when I found out about maintainer.io I reached out for a call 9/12/2017, 7:09:23 PM - waldyrious (Waldir Pimenta): I was looking to join him, but at the time he didn't have funding to expand the team, and soon after I had to switch gears and return to my PhD 9/12/2017, 7:09:55 PM - sils (Lasse Schuirmann): his prices look rather low FWIW 9/12/2017, 7:10:12 PM - sils (Lasse Schuirmann): compared to the effort it takes 9/12/2017, 7:10:38 PM - waldyrious (Waldir Pimenta): I didn't really think about the business side of things, I was mostly excited that was a thing 😛 9/12/2017, 8:12:40 PM - sils (Lasse Schuirmann): check osbusiness.viperdev.io , tried it. Never got any interest but I also never really tried. 9/12/2017, 8:13:02 PM - sils (Lasse Schuirmann): viperdev.io worked way better, I didn't try either and still people were coming at me because they actually have this really really painful problem 1/14/2023, 3:04:24 PM - RichardLitt (Richard Littauer) joined the room 9/12/2017, 8:13:03 PM - RichardLitt (Richard Littauer): :+1: Well I been trying 9/12/2017, 8:13:14 PM - sils (Lasse Schuirmann): ah hey @RichardLitt :) 9/12/2017, 8:13:22 PM - RichardLitt (Richard Littauer): Speak of the devil 9/12/2017, 8:13:25 PM - sils (Lasse Schuirmann): > Well I been trying is it working out? 9/12/2017, 8:15:10 PM - RichardLitt (Richard Littauer): Yep. :) 9/12/2017, 8:15:32 PM - RichardLitt (Richard Littauer): Company is doing pretty well. Lots of work going on, for me. Started hiring contractors here and there, no full time employees though 9/12/2017, 8:16:43 PM - sils (Lasse Schuirmann): nice! That's awesome to see. So companies are coming for it 9/12/2017, 8:19:46 PM - RichardLitt (Richard Littauer): Yeah! Not many. but a few. Mostly I am selling consulting as the main thing 9/12/2017, 8:20:16 PM - sils (Lasse Schuirmann): i.e. outside the packages? 9/12/2017, 8:20:22 PM - RichardLitt (Richard Littauer): Yeah. 9/12/2017, 8:21:25 PM - sils (Lasse Schuirmann): Hm makes sense though having a shared issue management team between companies gets better experience sharing which they ultimately only get if they buy the packages 9/12/2017, 8:22:14 PM - RichardLitt (Richard Littauer): Sure. But the idea was to use the packages to lead to better consulting packages for corporate clients 9/12/2017, 8:22:36 PM - sils (Lasse Schuirmann): @RichardLitt mind hopping on a call with me at some time when it's convenient to you? Would love to hear more. If you got some time we can also have a little chat about automation tools. Would love to hear more about your opinion on things 9/12/2017, 8:24:33 PM - RichardLitt (Richard Littauer): Yeah! I'd be happy to do that. 9/12/2017, 8:25:16 PM - sils (Lasse Schuirmann): you can see my calendar at calendly.com/sils (I know it's not personal but I hate the whole back and forth of date finding ^^ after all I'm into automation) 9/12/2017, 11:10:03 PM - agnivade (Agniva De Sarker): @sils - good to see that you guys are using gitlab. For my company, I made the shift from github to gitlab mainly to get the free CI for private repos, and I'm pretty happy now with the state it is in. 9/12/2017, 11:10:25 PM - agnivade (Agniva De Sarker): During the early days, it was pretty slow, but now its comparable to github speeds 9/12/2017, 11:19:27 PM - sils (Lasse Schuirmann): @agnivade yep also for us the rebase stuff is rather important, we actually built an automatic rebase into gitmate.io because we can't migrate coala.io easily to gitlab 9/13/2017, 12:10:34 AM - agnivade (Agniva De Sarker): That's like a cardinal rule I keep telling everyone - don't merge, rebase ! 9/13/2017, 2:10:23 AM - jayvdb (John Vandenberg): Anyone seen good visual docs on rebase workflow? 9/13/2017, 2:10:56 AM - jayvdb (John Vandenberg): A flowchart on how to edit patches 9/13/2017, 2:56:33 AM - sbrl (Starbeamrainbowlabs): @agnivade Why's rebase so much better than merge? 9/13/2017, 3:05:55 AM - jayvdb (John Vandenberg): A green non-rebased PR may not still be green. Only way to be sure is to know impact of all changes since the green build (basically you a doing a partial build in your head) or to rebase 9/13/2017, 3:07:41 AM - jayvdb (John Vandenberg): Also the commit history is much simpler, and a bit smaller, but infinitely easier to parse 9/13/2017, 3:20:18 AM - sbrl (Starbeamrainbowlabs): Um ok. What do you mean by 'green' though? 9/13/2017, 3:24:34 AM - jayvdb (John Vandenberg): Passing CI 9/13/2017, 3:24:53 AM - jayvdb (John Vandenberg): E.G. Travis build passes 9/13/2017, 3:27:34 AM - jayvdb (John Vandenberg): A rebase will identify a problem from outside the source tree, such as a new version incompatibility. A merge assumes nothing has changed since the previous build 9/13/2017, 3:29:23 AM - sbrl (Starbeamrainbowlabs): Ah, ok! I didn't know that. So Travis doesn't do another build on a merge commit? Interesting 9/13/2017, 3:34:34 AM - jayvdb (John Vandenberg): It does (it is the 'push' build'), but now the commit is merged. So you have a red/broken build on master. Of course you might fix it quick, but one day you dont, .. and a few other PRs are created, and are red. How do you explain that you wont merge their red PR until master is fixed, when you merged your own commit which broke master. 9/13/2017, 3:38:42 AM - jayvdb (John Vandenberg): and if you have a large team with active patches being landed daily, and/or lots of newbies, the 'how do we handle broken master' typically becomes 'core devs commit whatever they like, and everyone else hopes the tree goes green soon' 9/13/2017, 3:39:10 AM - jayvdb (John Vandenberg): Which is an anti-pattern for the community 9/13/2017, 3:39:59 AM - jayvdb (John Vandenberg): With a forced 'rebase and merge green only', everyone is equal. 9/13/2017, 3:44:37 AM - jayvdb (John Vandenberg): Then when something outside breaks the build, the last commit on master was green, but all PRs are red, everyone is stuck, even core devs. The only accepted PR is one that is green, including any&all fixes needed to unbreak the build so the next commit to master is also green. 9/13/2017, 9:42:41 AM - agnivade (Agniva De Sarker): @sbrl - Even if you don't use travis, if you keep merging commits, you will end up with a total mess of commit branches. And one day, you will want to revert some commit which is a few months old. Then tracing it back to its dependent commits becomes near impossible. 9/13/2017, 1:55:05 PM - waldyrious (Waldir Pimenta): @jayvdb > Anyone seen good visual docs on rebase workflow? 9/13/2017, 1:56:29 PM - waldyrious (Waldir Pimenta): THe best one I've found is this: http://www.bitsnbites.eu/a-tidy-linear-git-history/ 9/13/2017, 1:57:48 PM - waldyrious (Waldir Pimenta): I made a tweak to that post's diagram to include the three main merging strategies, and posted them to the threads discussing the rebase-then-merge functionality for both [gitlab](https://gitlab.com/gitlab-org/gitlab-ee/issues/28#note_31915883) and [bitbucket](https://bitbucket.org/site/master/issues/6106/provide-the-option-to-use-git-merge-ff#comment-37482851) 9/13/2017, 1:58:29 PM - waldyrious (Waldir Pimenta): (I'd recommend my diagram since it's easier to see the big picture, but I wanted to credit the original post) 9/13/2017, 1:59:27 PM - waldyrious (Waldir Pimenta): btw does anyone know if there's a similar issue thread for github? Perhaps in https://github.com/isaacs/github ? 9/13/2017, 2:11:13 PM - sbrl (Starbeamrainbowlabs): Ah, cool! I think I get it now. Thanks, @agnivade 😺 9/13/2017, 4:16:51 PM - waldyrious (Waldir Pimenta): > btw does anyone know if there's a similar issue thread for github? Perhaps in https://github.com/isaacs/github ? I didn't find one there, so I opened https://github.com/isaacs/github/issues/1017 : ) 9/13/2017, 6:35:57 PM - jayvdb (John Vandenberg): kinda wonky implementation 9/13/2017, 6:36:17 PM - jayvdb (John Vandenberg): Github does support it now; you can require rebase before merge. But the PR commits are given new hashes when the PR is merged. There is no fast–forward merge PR option 9/13/2017, 6:36:21 PM - jayvdb (John Vandenberg): Github does support it now; you can require rebase before merge. But the PR commits are given new hashes when the PR is merged. There is no fast–forward merge PR option 9/13/2017, 6:43:08 PM - waldyrious (Waldir Pimenta): > There is no fast–forward merge PR option You mean if no rebase was needed? 9/13/2017, 6:44:47 PM - waldyrious (Waldir Pimenta): > Github does support it now; you can require rebase before merge. Yeah, but that merely forces someone (PR author or repo owner) to rebase, using the command line, IIRC. There's no way in the interface to actually do the rebase, is there? 9/13/2017, 6:46:11 PM - jayvdb (John Vandenberg): Not a proper rebase, no 9/13/2017, 6:49:11 PM - sbrl (Starbeamrainbowlabs): Isn't there the "rebase and merge" option when merging a PR? 9/13/2017, 7:06:13 PM - waldyrious (Waldir Pimenta): Yes, but it doesn't create a merge commit 9/13/2017, 7:06:21 PM - sbrl (Starbeamrainbowlabs): ahh 9/13/2017, 7:06:23 PM - waldyrious (Waldir Pimenta): i.e. it doesn't preserve the branch information 9/13/2017, 7:06:43 PM - waldyrious (Waldir Pimenta): I really thought the diagram was self-explanatory, but apparently not 😅 9/14/2017, 5:27:00 AM - yukiisbored (Yuki): IMO, just use `rebase` 9/14/2017, 5:27:17 AM - yukiisbored (Yuki): I really don't like the bright green button that GitHub provides, makes a lot of trashy commits. 9/15/2017, 2:52:29 AM - sils (Lasse Schuirmann): @waldyrious hey just got your mail 9/15/2017, 2:53:10 AM - sils (Lasse Schuirmann): apparently not here... 9/15/2017, 1:10:25 PM - waldyrious (Waldir Pimenta): yeah, I was just quickly wrapping some loose ends before going to bed (had to wake up early today) 9/28/2017, 9:12:29 AM - agnivade (Agniva De Sarker): Hacktoberfest announcement is made :) I'm gonna label all issues which are "up for grabs" as "Hacktoberfest" 9/28/2017, 2:16:30 PM - sbrl (Starbeamrainbowlabs): :+1: 9/28/2017, 2:33:38 PM - waldyrious (Waldir Pimenta): yeah :) 10/2/2017, 9:16:03 PM - jayvdb (John Vandenberg): I've created a spreadsheet for [GCI tasks](https://docs.google.com/spreadsheets/d/1zvEIEnseTUFg1vvQCYPlB7nsWDcjt2O9BtExQtGiqOY/edit), and added one tldr task there 10/2/2017, 9:19:19 PM - waldyrious (Waldir Pimenta): nice :) what are your thoughts regarding the comment I left here --> https://github.com/tldr-pages/tldr/issues/1488#issuecomment-331077739 ? 10/2/2017, 10:04:12 PM - jayvdb (John Vandenberg): oh my apology for not following (i.e. ignoring) that (and millions of other issues) 10/2/2017, 10:10:47 PM - jayvdb (John Vandenberg): @waldyrious , how do newcomers get assigned to issues in tldr? 10/2/2017, 10:18:40 PM - jayvdb (John Vandenberg): replied 10/3/2017, 10:14:17 AM - agnivade (Agniva De Sarker): @jayvdb - One can just comment in the issue that he/she is working on it. 10/3/2017, 11:47:41 AM - jayvdb (John Vandenberg): Ok 10/11/2017, 10:14:47 AM - agnivade (Agniva De Sarker): Hey @jeeftor - Just checking in. Haven't seen you active in this repo any more. Are you still interested in being a collaborator ? 10/14/2017, 6:25:43 PM - waldyrious (Waldir Pimenta): (hey @agnivade and all: just stepping in to say I'm haven't abandoned the project! life keeps getting in the way... but in a good way this time: I found out that I'm going to be a father :) ) 10/14/2017, 6:26:42 PM - waldyrious (Waldir Pimenta): I hope to still be able to help prepare us for the Google Code-in with Coala, and Hacktoberfest 10/14/2017, 6:34:13 PM - sbrl (Starbeamrainbowlabs): Congrats, man! 10/14/2017, 6:46:06 PM - waldyrious (Waldir Pimenta): Thanks! :) :) 10/14/2017, 7:48:36 PM - agnivade (Agniva De Sarker): oh wow .. great news !! Congratulations ! 1/14/2023, 3:04:53 PM - pepa65 (pepa65) joined the room 10/14/2017, 7:49:24 PM - pepa65 (pepa65): Congratulations, welcome to the club! @waldyrious 10/14/2017, 8:11:46 PM - waldyrious (Waldir Pimenta): Thanks, guys! ^^ 10/24/2017, 8:57:04 PM - jayvdb (John Vandenberg): [coala GCI mentor signup form](https://docs.google.com/forms/d/e/1FAIpQLSfaYHOBgVwH7EMjNtFw6Xe7MhGbleVNvIlpFO13zHJeZNL8KQ/viewform?usp=sf_link) 10/24/2017, 9:29:16 PM - sbrl (Starbeamrainbowlabs): So what's this review queue thing it talks about? isn't that the PR list? 10/24/2017, 9:47:08 PM - jayvdb (John Vandenberg): yup 10/25/2017, 10:17:33 AM - agnivade (Agniva De Sarker): Couple of questions - - What is the chat that is being mentioned to ? - The review queue seems to be of coala repo's. But we (tldr maintainers) will have to look after the tasks for our own repo right ? 10/25/2017, 10:18:07 AM - agnivade (Agniva De Sarker): Lastly, about the organisation, we should be in the other section as 'tldr' right ? 10/25/2017, 10:23:50 AM - jayvdb (John Vandenberg): We will initially direct all students to gitter.im/coala/gci for their first task, but the tldr tasks will direct them here. And this team will be org 'tldr' , with a tldr tag, and ability to edit the tldr tasks as you see fit so they improve over time. 10/25/2017, 10:25:25 AM - jayvdb (John Vandenberg): we have 39 mentors signed up 😉 no tldr mentors have filled in the coala GCI mentor signup form so far 10/25/2017, 10:29:02 AM - agnivade (Agniva De Sarker): Got it. So how does the tldr tasks get published ? As in where / how do the students see the tasks ? 10/25/2017, 10:34:28 AM - jayvdb (John Vandenberg): They will be published in the Google Code-in website. Draft tasks are in Repeatable sheet of [this gspread](https://docs.google.com/spreadsheets/d/1zvEIEnseTUFg1vvQCYPlB7nsWDcjt2O9BtExQtGiqOY/edit) 10/25/2017, 10:58:55 AM - agnivade (Agniva De Sarker): Thanks. I will get the tasks setup by this weekend. It seems like there will be some manual work involved in tracking and assigning the issues. 10/25/2017, 10:59:14 AM - agnivade (Agniva De Sarker): @waldyrious - will you be available as a mentor ? 10/25/2017, 5:59:56 PM - jayvdb (John Vandenberg): @agnivade & @sbrl , it would be helpful if you could create https://openhub.net accounts (or let me know your usernames if they are different from your github username) 10/25/2017, 6:00:28 PM - jayvdb (John Vandenberg): Pretty picture example: https://www.openhub.net/accounts/waldyrious 10/26/2017, 12:35:28 AM - sbrl (Starbeamrainbowlabs): I've no clue what OpenHub is, but I've created an account here: https://www.openhub.net/accounts/Starbeamrainbowlabs @jayvdb 10/26/2017, 12:43:55 AM - sbrl (Starbeamrainbowlabs): I've signed up with that form you linked to above, too. Note that just because I've said 1-5 hours as my availability doesn't mean I won't be around. It's because my time is terribly fragmented atm due to university 😛 10/26/2017, 7:16:53 AM - jayvdb (John Vandenberg): @sbrl Down the bottom of your openhub profile page is a 'Claim Contributions' link (when you are logged in) 10/26/2017, 7:48:43 AM - jayvdb (John Vandenberg): oh pretty https://www.openhub.net/accounts/Starbeamrainbowlabs/languages 10/26/2017, 7:50:35 AM - jayvdb (John Vandenberg): @sbrl , https://gitlab.com/sbrl is available ... claim it while you can 😉 10/26/2017, 10:34:50 AM - agnivade (Agniva De Sarker): I signed up to openhub .. but when I click on claim contributions, it is showing stuff that is not mine. 10/26/2017, 10:35:01 AM - agnivade (Agniva De Sarker): Filtering by my name also doesn't show anything 10/26/2017, 10:35:49 AM - agnivade (Agniva De Sarker): https://www.openhub.net/accounts/agnivade 10/26/2017, 10:49:17 AM - jayvdb (John Vandenberg): @agnivade https://www.openhub.net/p/tldr-pages/contributors/3085017027492686 10/26/2017, 10:52:41 AM - jayvdb (John Vandenberg): more unrecognised committers at https://www.openhub.net/p/tldr-pages/contributors?sort=latest_commit&time_span=12+months 10/26/2017, 10:54:21 AM - jayvdb (John Vandenberg): @agnivade , [these](https://www.openhub.net/people?query=Agniva%20De%20Sarker) are not your commits ? If only some are your commits, you can click on "2 commits" to claim only the commits in that project 10/26/2017, 11:09:43 AM - jayvdb (John Vandenberg): [Felix Yan](https://www.openhub.net/p/tldr-pages/contributors/3085014879404871) is your fourth highest committer 10/26/2017, 1:54:53 PM - jayvdb (John Vandenberg): special request : https://github.com/tldr-pages/tldr/pull/1583 is by my intern. 10/26/2017, 2:02:07 PM - sbrl (Starbeamrainbowlabs): @jayvdb Right. I've claimed that GitLab url, too! I've noticed that OpenHub doesn't have any of my personal projects on it - which is where I've spent most time so far. 10/26/2017, 2:06:09 PM - sbrl (Starbeamrainbowlabs): And I've reviewed #1583 😺 - looks good! Just a pointer or two - nothing major 😃 10/26/2017, 2:34:16 PM - jayvdb (John Vandenberg): updated ^ 10/26/2017, 3:19:23 PM - waldyrious (Waldir Pimenta): @jayvdb I've reviewed the PR as well and marked @sbrl's review as addressed. It should be ready to merge :+1: 10/26/2017, 3:20:48 PM - waldyrious (Waldir Pimenta): @agnivade I believe I might be able to help, yes. I need to make sure what are the availability requirements, though, to be sure I won't be committing to more than I'm able to actually accomplish. Where should I look for that, @jayvdb? 10/26/2017, 3:25:29 PM - jayvdb (John Vandenberg): ok , merge when ready 😉 10/26/2017, 3:29:45 PM - jayvdb (John Vandenberg): For GCI, there are two distinct phases - the two weeks and the last four weeks. During the first two weeks, especially the first week, we'll be drowned in newcomers, and need people to answer questions and do reviews. Our mentor signup form asks how many hours during the first week (Nov 28 - Dec 4) you will be available, and it can be anywhere from 1 to 40+ 10/26/2017, 3:32:32 PM - waldyrious (Waldir Pimenta): Ok, sounds good. I'll be conservative in the estimate to play it safe, but I should be able to help : ) 10/26/2017, 3:32:55 PM - jayvdb (John Vandenberg): For the other weeks, you'll be mentoring specific tasks, and you choose how many tasks you want 'open' to be selected by the students 10/26/2017, 3:33:44 PM - waldyrious (Waldir Pimenta): Not sure I understand this last part 10/26/2017, 3:34:01 PM - jayvdb (John Vandenberg): for those last four weeks, you can control how many students can choose your tasks, and thus control your time commitment 10/26/2017, 3:34:22 PM - jayvdb (John Vandenberg): including, turning off the tasks, if you need a holiday 😉 10/26/2017, 3:36:49 PM - waldyrious (Waldir Pimenta): So does it work by having mentors assigned to specific tasks, and they can choose how many of those tasks should be active simultaneously? Or per week? 10/26/2017, 3:37:24 PM - jayvdb (John Vandenberg): active simultaneously. 10/26/2017, 3:37:28 PM - waldyrious (Waldir Pimenta): (if this is all described somewhere, feel free to point me there) 10/26/2017, 3:38:02 PM - waldyrious (Waldir Pimenta): Cool, sounds good. In the signup form, in the question "What's your project's organisation?", am I to write down "tldr", then? 10/26/2017, 3:38:37 PM - jayvdb (John Vandenberg): no it isnt all described elsewhere, sorry ... your questions will be answered automatically in about 6 hrs when you can add tasks in the Google Code-in system 10/26/2017, 3:39:21 PM - jayvdb (John Vandenberg): yup, tldr 10/26/2017, 4:02:25 PM - waldyrious (Waldir Pimenta): Just submitted the form. The time zone question was slightly confusing because of daylight saving time, which ends this Sunday. Maybe you could edit that question to clarify what period it applies to; the way the question is phrased makes it seem like it's asking about the _current_ local time (i.e. when the form is being filled) 10/26/2017, 4:07:37 PM - jayvdb (John Vandenberg): Done 10/26/2017, 4:07:50 PM - waldyrious (Waldir Pimenta): :+1: 10/26/2017, 9:36:39 PM - jayvdb (John Vandenberg): https://twitter.com/coala_io/status/923581379547299841 10/26/2017, 9:42:55 PM - sbrl (Starbeamrainbowlabs): @waldyrious Ok, I'll take another look a bit later today when I've got time. 10/26/2017, 9:51:42 PM - agnivade (Agniva De Sarker): done with openhub 10/26/2017, 9:51:46 PM - agnivade (Agniva De Sarker): submitted GCI form too 10/26/2017, 9:52:04 PM - agnivade (Agniva De Sarker): do we need to anything else as tldr org ? (apart from setting up the tasks) 10/26/2017, 9:53:50 PM - jayvdb (John Vandenberg): not yet; we'll send out more info. i'll start by inviting you into the gci website as mentors 10/26/2017, 9:54:04 PM - agnivade (Agniva De Sarker): great 10/26/2017, 9:58:26 PM - sbrl (Starbeamrainbowlabs): cool 10/26/2017, 9:58:33 PM - sbrl (Starbeamrainbowlabs): Let me know when the invite is out 10/26/2017, 10:13:51 PM - sbrl (Starbeamrainbowlabs): Merged #1583 😺 10/26/2017, 10:38:18 PM - sbrl (Starbeamrainbowlabs): Ok, I've received that invite for google code-in 10/26/2017, 10:38:30 PM - sbrl (Starbeamrainbowlabs): It's telling me I need a minimum of 75 tasks? 10/26/2017, 10:38:42 PM - sbrl (Starbeamrainbowlabs): I thought that was across all the whole organisation 10/26/2017, 10:39:33 PM - sbrl (Starbeamrainbowlabs): Ahh I see - so it's the dashboard for the tldr-pages suborg? 10/26/2017, 10:49:51 PM - jayvdb (John Vandenberg): that is 75 for all coala & sub-orgs 10/26/2017, 11:18:05 PM - sbrl (Starbeamrainbowlabs): Ahh right! 10/26/2017, 11:18:06 PM - sbrl (Starbeamrainbowlabs): phew 10/26/2017, 11:18:07 PM - sbrl (Starbeamrainbowlabs): 😛 10/27/2017, 12:51:16 AM - sbrl (Starbeamrainbowlabs): So from reading this document that @jayvdb has linked me to, I can summise: 1. Be especially nice to GCI students. 2. Most GCI work takes place on the GCI website. 3. We need a community code of conduct as a reference point to deal with unacceptable behaviour. 4. It's happening between November 28th and January 17th. 5. We'll get a higher rate of PRs than normal (~50% more?) 6. Responses to student questions should be within a maximum of ~16 hours 10/27/2017, 12:51:56 AM - sbrl (Starbeamrainbowlabs): Document link: https://docs.google.com/document/d/1D8I6T50q_o4MYGzQBdjl6o33h8WFRPedeOpJtK7zKwU/edit# 10/27/2017, 12:56:18 AM - sbrl (Starbeamrainbowlabs): 7 . An FAQ might not go amiss if we get lots of the same questions 10/27/2017, 9:52:01 AM - jayvdb (John Vandenberg): [our tasks from last year](https://codein.withgoogle.com/archive/search/?q=coala) 10/27/2017, 9:53:00 AM - jayvdb (John Vandenberg): The three most detailed repeatable tasks: [CI1](https://codein.withgoogle.com/archive/2016/organization/5747272637743104/task/6545921269563392/), [CI2](https://codein.withgoogle.com/archive/2016/organization/5747272637743104/task/6534874613678080/), [CI3](https://codein.withgoogle.com/archive/2016/organization/5747272637743104/task/4860301761576960/) 1/14/2023, 3:05:23 PM - mstruebing (Max Strübing) joined the room 10/28/2017, 10:03:00 PM - mstruebing (Max Strübing): Hey all, I love the idea and use tldr every day. I contribute with a pull request to tldr-pages every time I miss some example or even a whole command. I've made a tldr client written in golang. You can see it here: https://github.com/mstruebing/tldr And would love to transfer it into the official organization as this would mean more users, more contributors(I've somehow got a very active one) and more bug reports. I've chatted a bit with @agnivade and he said at least that he is not averse to transfer it into the official organization. I think it's very stable until now. I've tried to implement everything that is stated here: https://github.com/tldr-pages/tldr/issues/1065#issuecomment-251053184 just the `~/.tldrrc` file is currently not readen. Of course I would maintain this tool in the future. Pros of this: - no runtime needed - no runtime dependencies (external tools) - cross-platform - nice tooling for code quality - fast Cons: - tell me What do you think? 10/28/2017, 10:10:31 PM - waldyrious (Waldir Pimenta): Hi @mstruebing! I'm glad you're enjoying both using and contributing to tldr :) 10/28/2017, 10:11:05 PM - waldyrious (Waldir Pimenta): in principle I have no objections to moving the repo under the tldr organization umbrella, but I'd like to hear your thoughts regarding the points raised at https://github.com/tldr-pages/tldr/issues/1410 10/28/2017, 10:27:25 PM - sbrl (Starbeamrainbowlabs): Sounds like the kind of client we could use! Perhaps we could push it as an alternative to the node client if it's decently cross platform? My personal stance is that a monorepo wouldn't be a good idea in our case. 10/28/2017, 10:46:32 PM - mstruebing (Max Strübing): I don't think the transpiling idea could work in a reasonable amount of work/time and would not be stable I think, every language moves on and that would be a huge amount of work to be maintained. A single client would be great if it would be working *perfectly*, I remember I had issues the first time I tried tldr and heard the same from a colleague whom I showed my client. That's why I think the diversity of clients should be given and not just one official client should be supported. I had the possibility to just install an other client of the same organization, I'm not sure if I would have been willing to install a client from some other source because I didn't know if the client would be updated, reacts on changes of the official organisation - like when you change the markdown for your pages, change the location of the pages to download - or stuff. I don't really think a monorepo across all clients could work. That would mean that this repo have a TONS of issues and pull requests. You would try to sort the issues and prs via labels but that gets confusing sooner as someone might think. There should might be a repository for general tldr stuff (not the pages) where things like client specification are written (or a wiki) and the maintainers of the single repository should be responsible to take issues they get into the general tldr repo/wiki if it is something which has to do with all clients e.g. new features. 10/28/2017, 11:08:37 PM - sbrl (Starbeamrainbowlabs): This. You've described it much better than I could 😛 10/28/2017, 11:10:43 PM - mstruebing (Max Strübing): :) 10/28/2017, 11:25:30 PM - waldyrious (Waldir Pimenta): > I'm not sure if I would have been willing to install a client from some other source because I didn't know if the client would be updated Well, that's an issue as well: we're a tiny maintenance team, and our availability varies with time. Even with the small number of clients in our org, not all of them (e.g. the python one) are actively maintained. I'd be wary of expanding that list tbh... 10/28/2017, 11:29:37 PM - mstruebing (Max Strübing): But as an outsider I would give organization clients way more trust than third party clients 10/28/2017, 11:31:49 PM - waldyrious (Waldir Pimenta): Absolutely, I'm not questioning that. What I'm questioning is whether that trust would be justified -- e.g. there are some long-standing bugs in the Python client that users can't access yet, just because a release hasn't been published by the author on PyPI (https://github.com/tldr-pages/tldr-python-client/issues/47) 10/28/2017, 11:32:09 PM - waldyrious (Waldir Pimenta): and some of them took a long time to fix because nobody was actively maintaining the repo 10/28/2017, 11:33:00 PM - waldyrious (Waldir Pimenta): Same for the linter, for example, which depends on @rubenvereecken since most people are not familiar with the toolchain it uses 10/28/2017, 11:34:06 PM - waldyrious (Waldir Pimenta): so there's no guarantee that repos under the org are more stable, or better maintained -- in fact the contrary is true in some cases 10/28/2017, 11:40:16 PM - agnivade (Agniva De Sarker): Some news from GCI side. I have created a list of 12 issues from the main list. This contains issues from various programming languages so that we have good variety and we don't focus on just a single thing. 10/28/2017, 11:40:19 PM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr/issues?q=is%3Aissue+is%3Aopen+label%3Agci+no%3Aassignee 10/28/2017, 11:40:35 PM - agnivade (Agniva De Sarker): All the issues have links to the main webpage for the tool and the documentation link. 10/28/2017, 11:40:48 PM - agnivade (Agniva De Sarker): And also a supplementary link to our CONTRIBUTING page 10/28/2017, 11:41:10 PM - agnivade (Agniva De Sarker): @jayvdb - we can share this link with the participants. 10/28/2017, 11:42:06 PM - waldyrious (Waldir Pimenta): 👏 awesome work @agnivade : ) 10/28/2017, 11:43:09 PM - agnivade (Agniva De Sarker): Thanks ! 10/28/2017, 11:43:56 PM - agnivade (Agniva De Sarker): how is it going with you ? 10/28/2017, 11:44:29 PM - waldyrious (Waldir Pimenta): trying to juggle lots of stuff at the same time, but slowly progressing 10/28/2017, 11:45:47 PM - agnivade (Agniva De Sarker): its tough .. from what I hear .. 10/28/2017, 11:45:54 PM - agnivade (Agniva De Sarker): I'm sure you'll do fine :) 10/28/2017, 11:46:43 PM - waldyrious (Waldir Pimenta): on the FOSS front, I've cleared up my github notifications backlog for all repos other than tldr and a handful of issues I need to take an hour or two to process; just yesterday I managed to review some hacktoberfest PRs to other repos before it was too late 10/28/2017, 11:47:15 PM - agnivade (Agniva De Sarker): alright ! 10/28/2017, 11:47:42 PM - waldyrious (Waldir Pimenta): I'll make sure to prioritize GCI when the tasks start coming in. I'm counting on you guys to keep me on my toes 😉 10/28/2017, 11:48:11 PM - agnivade (Agniva De Sarker): there's one PR in particular which needs your focus - https://github.com/tldr-pages/tldr/pull/1594 10/28/2017, 11:48:24 PM - agnivade (Agniva De Sarker): haha sure 😃 10/28/2017, 11:49:01 PM - waldyrious (Waldir Pimenta): oh well... I don't have much more time today, might as well get that one off my place 😛 I'll take a look 10/28/2017, 11:50:01 PM - agnivade (Agniva De Sarker): oh I wasn't saying to take a look at it right now .. 10/28/2017, 11:50:09 PM - agnivade (Agniva De Sarker): just bump this higher up in your TODO list 10/28/2017, 11:51:21 PM - waldyrious (Waldir Pimenta): haha I know, but I figured I'd at least take a look to give some feedback. I know how it sucks being on the receiving end of unresponsiveness :) 10/28/2017, 11:51:44 PM - waldyrious (Waldir Pimenta): oh, but I see it's only hours old 10/28/2017, 11:52:13 PM - waldyrious (Waldir Pimenta): I guess @iamam34 won't mind if I take a look in a couple days : ) 10/29/2017, 1:25:26 AM - sbrl (Starbeamrainbowlabs): Thanks, @agnivade! 10/29/2017, 1:26:09 AM - sbrl (Starbeamrainbowlabs): I guess the next task there is to write the google code-in task in the GCI dashboard? 10/29/2017, 1:26:38 AM - sbrl (Starbeamrainbowlabs): I can take a look at that if you want? 10/29/2017, 5:40:35 AM - jayvdb (John Vandenberg): @agnivade , yup, add that link in the task 10/29/2017, 10:35:59 AM - agnivade (Agniva De Sarker): @sbrl sure go ahead. 10/31/2017, 12:12:10 AM - sbrl (Starbeamrainbowlabs): Going ahead now! Which tldr pages do people think are great examples of what we're after? 10/31/2017, 12:22:36 AM - sbrl (Starbeamrainbowlabs): I've created the first task here: https://codein.withgoogle.com/dashboard/tasks/4838166143959040/preview/ 10/31/2017, 12:37:47 AM - sbrl (Starbeamrainbowlabs): Tasks for all the issues tagged with `gci` have been created - except `eslint`, of course (since someone's decided to do that one already 😛 10/31/2017, 12:38:23 AM - sbrl (Starbeamrainbowlabs): I've used a sort of template description. Feedback appreciated 😺 10/31/2017, 9:44:25 AM - agnivade (Agniva De Sarker): I think we are supposed to have just one task. And this is the link that should be used - https://github.com/tldr-pages/tldr/issues?q=is%3Aissue+is%3Aopen+label%3Agci+no%3Aassignee. Because tasks are supposed to be repeatable. So, therefore using that same link, which is a list of unassigned issues, students can pick up an issue an work on it. 10/31/2017, 9:44:38 AM - agnivade (Agniva De Sarker): No need to create separate task for separate issues. 10/31/2017, 9:45:09 AM - jayvdb (John Vandenberg): ill take a look 10/31/2017, 9:45:21 AM - agnivade (Agniva De Sarker): The template looks great, just update the wording to include the link above. 10/31/2017, 9:46:24 AM - jayvdb (John Vandenberg): definitely keep the tasks that have been created 10/31/2017, 9:47:01 AM - agnivade (Agniva De Sarker): Ah ok, so you want a one to one correspondence between gci tasks and github issues ? 10/31/2017, 9:47:08 AM - jayvdb (John Vandenberg): `ruby` doesnt exist in tldr? 10/31/2017, 9:47:20 AM - agnivade (Agniva De Sarker): > `ruby` doesnt exist in tldr? 10/31/2017, 9:47:22 AM - agnivade (Agniva De Sarker): no 10/31/2017, 9:47:44 AM - jayvdb (John Vandenberg): that is another potential set of tldr pages which would definitely be in scope : any package managers & language runtimes 10/31/2017, 9:48:26 AM - agnivade (Agniva De Sarker): sure. But if you want a one to one correspondence, then maybe the link I provided is useless now right ? 10/31/2017, 9:48:39 AM - agnivade (Agniva De Sarker): because the students get directly assigned to github issues 10/31/2017, 9:48:44 AM - jayvdb (John Vandenberg): the package managers (including the windows ones) will be helpful for kids installing stuff at the beginning of gci 😉 10/31/2017, 9:50:59 AM - jayvdb (John Vandenberg): the good part of individual tasks is we can give each task different tags, like @sbrl did. so, I think we should have at least two tasks for each language . i.e. two for go linters, like has been done. We can then create an additional generic task which is used for any other linter 10/31/2017, 9:51:57 AM - jayvdb (John Vandenberg): re tags: `terminal, linux, c++, command line` - terminal & command line are redundant ? 10/31/2017, 9:52:57 AM - jayvdb (John Vandenberg): re title: `tldr-pages: ...` , could be just `tldr: ...` ? 10/31/2017, 9:53:50 AM - agnivade (Agniva De Sarker): > terminal & command line are redundant ? why do you say so ? > could be just tldr: ... ? sure 10/31/2017, 9:54:27 AM - jayvdb (John Vandenberg): having lots of different tags, especially one for every language, will be really useful as the kids will search on things they know, and language names will be one of the most common search terms 10/31/2017, 9:55:17 AM - agnivade (Agniva De Sarker): that's fine. I think terminal and command line are still useful tags 10/31/2017, 9:55:31 AM - jayvdb (John Vandenberg): ok 10/31/2017, 9:56:30 AM - agnivade (Agniva De Sarker): great ! So @sbrl , we have some great feedback. This is a good start. You can continue creating the other tasks. 10/31/2017, 9:56:44 AM - agnivade (Agniva De Sarker): I will see if I can create some more issues for package managers and runtimes 10/31/2017, 9:57:32 AM - jayvdb (John Vandenberg): https://en.wikipedia.org/wiki/List_of_compilers 11/4/2017, 4:29:13 AM - sbrl (Starbeamrainbowlabs): Ok, sure! (Sorry, I've been rather busy at uni - Fridays are my worst day there 😛) So we need: - 2 tasks per language - not one per linter - An additional generic task that links to the list of GCI-labeled issues? Not sure I completely understand the 2 tasks per language bit though. 11/4/2017, 4:29:23 AM - sbrl (Starbeamrainbowlabs): I'll take a closer look at it tomorrow. 11/4/2017, 5:40:57 AM - jayvdb (John Vandenberg): @sbrl ; one issue per linter ; one task per linter ; but dont create issues/tasks for every linter. only create issues & tasks for two linters for each programming language. 11/4/2017, 5:41:22 AM - jayvdb (John Vandenberg): Then we have a generic task for all of the other linters. 11/4/2017, 5:41:45 AM - jayvdb (John Vandenberg): e.g. we create separate tasks for two of the go linters. 11/4/2017, 5:42:02 AM - jayvdb (John Vandenberg): not all 6 of the go linters that coala supports 11/4/2017, 5:43:35 AM - jayvdb (John Vandenberg): the other 4 go linters would be covered by a generic task which isnt linter or language specific 11/4/2017, 5:33:53 PM - sbrl (Starbeamrainbowlabs): O.o 6 linters for go? I had no idea! Yeah, we should certainly limit it to 2 linters per language. 11/4/2017, 5:40:24 PM - sbrl (Starbeamrainbowlabs): Created a generic task: https://codein.withgoogle.com/dashboard/tasks/6102656995033088/ 11/4/2017, 5:40:48 PM - jayvdb (John Vandenberg): :+1: 11/4/2017, 5:42:02 PM - sbrl (Starbeamrainbowlabs): So now I guess we just need to delete tasks until we have 2 per language (I'll do that now), and then create issues for popular languages & package managers (which @agnivade says he's dealing with)? 11/4/2017, 5:42:48 PM - jayvdb (John Vandenberg): rather than delete, for any tasks where you have more than two per language, change the linter to be a different language 11/4/2017, 5:43:56 PM - sbrl (Starbeamrainbowlabs): ...right? In that case it's over to @agnivade then? 11/4/2017, 11:49:39 PM - agnivade (Agniva De Sarker): ok so just to be clear, we are now creating a linter+package manager+runtime per programming language right ? 11/5/2017, 7:26:55 AM - jayvdb (John Vandenberg): per programming language: 1 package manager + 1 runtime + 2 linters 11/5/2017, 7:27:30 AM - jayvdb (John Vandenberg): e.g. npm + nodejs + standard + eslint 11/5/2017, 10:25:57 AM - agnivade (Agniva De Sarker): got it. It might be a bit difficult to find package managers and runtimes for all programming languages .. 11/5/2017, 10:26:15 AM - agnivade (Agniva De Sarker): for eg npm and node already have their pages 11/5/2017, 10:30:13 AM - jayvdb (John Vandenberg): yarn .. 😉 11/5/2017, 10:30:53 AM - agnivade (Agniva De Sarker): hehe .. that also has a page 11/5/2017, 10:33:43 AM - jayvdb (John Vandenberg): grunt 😛 11/5/2017, 10:33:49 AM - jayvdb (John Vandenberg): (And I checked this time ...) 11/5/2017, 10:34:26 AM - agnivade (Agniva De Sarker): grunt is not a package manager .. but I see where you are going with this 11/5/2017, 1:19:43 PM - mstruebing (Max Strübing): BTW as I see you are participating in GCI, there is also a `hacktoberfest` every year, sponsored from Digital Ocean 😉 11/5/2017, 1:36:51 PM - jayvdb (John Vandenberg): I find the quality of hacktoberfest PRs is quite low 11/5/2017, 1:37:25 PM - jayvdb (John Vandenberg): Good coders can get the tshirt with prs in their normal repos 11/5/2017, 1:38:04 PM - jayvdb (John Vandenberg): bad coders do prs in 'algo' repos or worse 11/5/2017, 1:39:21 PM - jayvdb (John Vandenberg): A few newcomers appear, and they tend to do light PRs, and dont stick around after tshirt 11/6/2017, 9:27:02 AM - agnivade (Agniva De Sarker): @mstruebing - Yes we already participated in hacktoberfest. If you didn't already notice, the issues were tagged hacktoberfest during October. 11/6/2017, 8:47:13 PM - agnivade (Agniva De Sarker): Hey guys, here is the list I came up with 11/6/2017, 8:47:15 PM - agnivade (Agniva De Sarker): Go - dep (package manager) gofmt (linter) Ruby - ruby (runtime) rubo cop (linter) C++ cppclean (linter) g++ (compiler) Python pycodestyle (linter) Node gulp (task runner) grunt (task runner) 11/6/2017, 8:47:43 PM - agnivade (Agniva De Sarker): let me know if you want to add anything 11/6/2017, 8:47:59 PM - agnivade (Agniva De Sarker): I will start creating issues then 11/6/2017, 8:50:12 PM - jayvdb (John Vandenberg): if you create issues, is there a chance someone will come along and decide to do them; i.e. are issues increasing the chance that these will be done before GCI ? 11/6/2017, 8:52:10 PM - jayvdb (John Vandenberg): for python, pyflakes and autoflake are partner orgs with coala, so probably a good idea to have them as separate issues that are done in the first batch 11/6/2017, 8:53:25 PM - jayvdb (John Vandenberg): general faq question (sorry) ; how does tldr try to approach versions of commands that are different ; not a good example, but e.g. python2 vs python3 11/6/2017, 8:54:04 PM - jayvdb (John Vandenberg): (that one is still interesting, because they do quite different things even though their options are similar) 11/6/2017, 8:55:21 PM - agnivade (Agniva De Sarker): I can hold on actually creating the issues before gci .. but if someone creates a PR for that page .. it might be rude to reject that. So in that case, we can't do much. 11/6/2017, 8:55:37 PM - jayvdb (John Vandenberg): agree on not being rude. 11/6/2017, 8:55:50 PM - jayvdb (John Vandenberg): maybe create a issue generator ... ? 11/6/2017, 8:56:01 PM - jayvdb (John Vandenberg): so it is easy to create them as needed 11/6/2017, 8:56:43 PM - agnivade (Agniva De Sarker): about your version question - we don't handle it very elegantly as of now. At max, we add a note saying "Look at `python2`" , and then the client says to also check that page when the command is typed 11/6/2017, 8:59:33 PM - agnivade (Agniva De Sarker): an issue generator to create issues ? that sounds like an overkill .. :) 11/6/2017, 8:59:45 PM - agnivade (Agniva De Sarker): usually we just click new issue button, write the title and be done with it. 11/6/2017, 9:00:03 PM - agnivade (Agniva De Sarker): but only for gci, I have been extra diligent and including the command page and the CONTRIBUTING.md 11/6/2017, 9:02:56 PM - agnivade (Agniva De Sarker): but overall, what do you think about the list ? Do you want to add/remove anything ? 11/6/2017, 9:03:28 PM - jayvdb (John Vandenberg): for python, pyflakes and autoflake are partner orgs with coala, so probably a good idea to have them as separate issues that are done in the first batch 11/6/2017, 9:03:42 PM - jayvdb (John Vandenberg): rubo cop -> rubocop 11/6/2017, 9:04:09 PM - agnivade (Agniva De Sarker): > so probably a good idea to have them as separate issues that are done in the first batch I didn't get that. what do you mean "first batch" ? 11/6/2017, 9:04:11 PM - jayvdb (John Vandenberg): otherwise good 11/6/2017, 9:04:56 PM - jayvdb (John Vandenberg): first batch = explicitly requested pages , which will be tasks available for students on day 1 11/6/2017, 9:05:28 PM - agnivade (Agniva De Sarker): yes .. all these are explicitly requested pages, no ? 11/6/2017, 9:05:38 PM - jayvdb (John Vandenberg): yup 11/6/2017, 9:05:56 PM - jayvdb (John Vandenberg): and im suggesting pyflakes + autoflake are added to that list 11/6/2017, 9:06:25 PM - agnivade (Agniva De Sarker): ohh ok ok. 11/6/2017, 9:07:10 PM - agnivade (Agniva De Sarker): alright, I will save the list. And create it just before gci. 11/13/2017, 10:09:29 PM - sbrl (Starbeamrainbowlabs): Hey! Just got an invite to a time-tracking tool and a chat thingy. The chat thingy's apparently the chat client that Coala is going to use, but what's this time tracking tool for? 1/14/2023, 3:06:13 PM - SanketDG (Sanket Dasgupta) joined the room 11/13/2017, 10:24:16 PM - SanketDG (Sanket Dasgupta): @jayvdb ^^ 11/13/2017, 10:32:50 PM - jayvdb (John Vandenberg): Both optional . Toggl is for tracking how much time your time invests into gci. And you can create entries retrospectively i think 11/13/2017, 10:35:53 PM - jayvdb (John Vandenberg): We've been given an unlimited license for GCI. The students who complete a non-newcomer task will be offered an account, with lots of warning about cloud based services 11/13/2017, 10:36:48 PM - jayvdb (John Vandenberg): It is free for personal use, so no lock-in 11/13/2017, 10:38:15 PM - jayvdb (John Vandenberg): Imo it is the best tool of its kind, balancing privacy very well, with all client side apps being open source and not requesting permissions like 'read all contacts' 11/13/2017, 11:17:07 PM - sbrl (Starbeamrainbowlabs): I see. What do you plan to do with the data about how much time I spend on GCI? 11/14/2017, 6:00:52 AM - jayvdb (John Vandenberg): the main uses will be related to understanding how much effort it takes to be part of gci. Maybe next year telling suborgs roughly how much preparation will be required. How much time is needed in week 1 vs week 2. 11/14/2017, 6:07:12 AM - jayvdb (John Vandenberg): It is going to be more useful for the mentors of coala tasks, where we have about 40 mentors. Seeing which are helping with preparations, and who is absent during week 1, is something that toggl can help with, as it is too many ppl to individually track. 11/14/2017, 2:30:01 PM - sbrl (Starbeamrainbowlabs): Ah, ok! I'll be generally doing most of it from my phone on the bus and using other small pockets of time I should imagine, so it'll be difficult track it effectively. 11/14/2017, 2:30:17 PM - sbrl (Starbeamrainbowlabs): I'll still have a go though is the information is useful. 11/14/2017, 3:08:21 PM - jayvdb (John Vandenberg): Dont spend too much time on it 😉 11/14/2017, 3:16:59 PM - sbrl (Starbeamrainbowlabs): Sure - I've got University & personal stuff to do too 😛 11/18/2017, 11:45:30 AM - agnivade (Agniva De Sarker): Hey guys, just wanted to say that the node client now has a command search feature. By which you can search for pages containing words. It works just like the `apropos` command. 11/18/2017, 11:45:40 AM - agnivade (Agniva De Sarker): Feel free to download the latest version and give it a spin. 11/18/2017, 2:21:11 PM - sbrl (Starbeamrainbowlabs): Cool! I'll have to check it out 😃 11/18/2017, 2:21:48 PM - sbrl (Starbeamrainbowlabs): Currently using the bash client though, since I experienced issues with the node one (was a long time ago, can't remember what it was, haven't bothered to switch back 😛) 11/25/2017, 6:07:08 PM - sbrl (Starbeamrainbowlabs): Not too long until Google Code-In starts! Any preparations that still need to be made that I can help out with? 11/25/2017, 6:09:17 PM - waldyrious (Waldir Pimenta): @sbrl I haven't been able to help out much or prepare for GCI. I'll reserve a pair of hours this afternoon to work on tldr stuff. Any suggestions on where to direct my attention / efforts? 11/25/2017, 6:10:06 PM - sbrl (Starbeamrainbowlabs): I've no idea what need doing, so I'm not much help there 😛 11/25/2017, 6:10:13 PM - sbrl (Starbeamrainbowlabs): @agnivade? 11/25/2017, 6:10:23 PM - waldyrious (Waldir Pimenta): Will you be around for the next hours or so? 11/25/2017, 6:10:56 PM - sbrl (Starbeamrainbowlabs): Should be here and there :-) 11/25/2017, 6:11:10 PM - sbrl (Starbeamrainbowlabs): Got to go out at ~2pm GMT though 11/25/2017, 6:12:13 PM - waldyrious (Waldir Pimenta): oh ok -- I'll schedule tldr time for now then :) I'll start in a few minutes, and will let you know if I need anything : ) 11/25/2017, 6:13:51 PM - sbrl (Starbeamrainbowlabs): sure thing :-) 11/25/2017, 6:14:20 PM - sbrl (Starbeamrainbowlabs): If you need my help, please @mention me to get a notification showing on my screen 11/25/2017, 6:14:35 PM - waldyrious (Waldir Pimenta): sure, sure 😃 11/25/2017, 6:17:41 PM - agnivade (Agniva De Sarker): Hey @waldyrious , nothing much to do from your side for GCI. I just have to create a bunch of issues, which I will do in a short while. 11/25/2017, 6:18:08 PM - agnivade (Agniva De Sarker): If you have time, just review this PR https://github.com/tldr-pages/tldr/pull/1594 11/25/2017, 6:18:22 PM - waldyrious (Waldir Pimenta): Ok! I'll start there :+1: 11/25/2017, 6:18:45 PM - agnivade (Agniva De Sarker): great 1/14/2023, 3:06:25 PM - OrionRandD (OrionRandD) joined the room 11/25/2017, 7:09:31 PM - OrionRandD (OrionRandD): I think the command is oversimplified 😟 11/25/2017, 7:09:46 PM - OrionRandD (OrionRandD): I installed it but did not really like it 11/25/2017, 7:10:17 PM - sbrl (Starbeamrainbowlabs): Hey, @OrionRandD! Could you describe a bit more about your issue? 11/25/2017, 7:10:48 PM - OrionRandD (OrionRandD): It is an evocation for laziness in the Open 11/25/2017, 7:10:53 PM - OrionRandD (OrionRandD): source world 11/25/2017, 7:11:30 PM - OrionRandD (OrionRandD): I am reffering to the tldr command... 11/25/2017, 7:13:40 PM - sbrl (Starbeamrainbowlabs): You mean that the tldr-pages are a bit over-simplified? One might consider them to be, certainly. For more advanced uses of a command, we generally refer people to man pages - the tldr pages are supposed to aid people with remembering just the most common usages of a command - i.e. they give the user an ideaa as to what the command is capable of. 1/14/2023, 3:06:28 PM - milleniumbug (milleniumbug) joined the room 11/25/2017, 7:14:03 PM - milleniumbug (milleniumbug): IOW, it's by design 11/25/2017, 7:14:56 PM - milleniumbug (milleniumbug): also most manpages are basically incomprehensible unless you already know the ins and outs of the commands so there 11/25/2017, 7:15:32 PM - sbrl (Starbeamrainbowlabs): @milleniumbug Indeed! For example, I can never remember the correct sequence of letters to extract a .tar.bz2 archive. I can read the tldr-page and extract my archive in 2 minutes - or I can trawl through the man pages and take 1/2/ hour over it 11/25/2017, 7:17:51 PM - milleniumbug (milleniumbug): > git-push - Update remote refs along with associated objects 11/25/2017, 7:17:54 PM - milleniumbug (milleniumbug): I mean, have fun 11/25/2017, 7:18:22 PM - sbrl (Starbeamrainbowlabs): I've got a lot to do, so I prefer to have an aid for the simple things so I can focus on the more complex problems. For example, I might want to extract only the newer files from a .tar.bz that's stored on a tape drive - whilst keeping backup copies of the original files in the target location. For that, I'd certainly read a man page. 11/25/2017, 7:18:24 PM - OrionRandD (OrionRandD): Not very convincing for me... 11/25/2017, 7:18:43 PM - OrionRandD (OrionRandD): I still think it is an invocation to laziness... 11/25/2017, 7:19:01 PM - milleniumbug (milleniumbug): well, YMMV. feel free to not use it if you consider it "lazy" 11/25/2017, 7:19:11 PM - OrionRandD (OrionRandD): look for example "tldr rsync" 11/25/2017, 7:19:30 PM - sbrl (Starbeamrainbowlabs): @OrionRandD It's your choice! 11/25/2017, 7:19:39 PM - OrionRandD (OrionRandD): I know I am free to use whatever command I like... 11/25/2017, 7:20:33 PM - OrionRandD (OrionRandD): I am not saying that the command or project is not useful, but could have a little more "meat" on that 11/25/2017, 7:20:54 PM - sbrl (Starbeamrainbowlabs): I never seem get the correct rsync options myself actually - having the basic usages on a tldr-page really helps in that instance as I personally have issues figuring it out from the manual page 😛 11/25/2017, 7:21:00 PM - OrionRandD (OrionRandD): I like the project, but still think it is over simplified 11/25/2017, 7:21:20 PM - sbrl (Starbeamrainbowlabs): If you've got a suggestion for a page, feel free to send a pull request and we'll review it. 11/25/2017, 7:21:56 PM - milleniumbug (milleniumbug): I don't see what's wrong with the tldr rsync page 11/25/2017, 7:22:31 PM - OrionRandD (OrionRandD): rsync for example does not show a single example on how to deal with non-standard port numbers 11/25/2017, 7:22:58 PM - sbrl (Starbeamrainbowlabs): Pull requests are welcome, if you'd like to do something about it :-) 11/25/2017, 7:23:09 PM - OrionRandD (OrionRandD): so, in the end you have to use another command to get to know that... 11/25/2017, 7:24:46 PM - sbrl (Starbeamrainbowlabs): tldr-pages is a community effort. As a maintainer, I have a limited amount of time to research and edit/create pages. 11/25/2017, 7:24:56 PM - OrionRandD (OrionRandD): scp is another missing port example... 11/25/2017, 7:25:52 PM - OrionRandD (OrionRandD): and in this case we cannot use "-p" like in rsync or ssh 11/25/2017, 7:25:59 PM - milleniumbug (milleniumbug): indeed, given how NAT is rampant, custom ports are surprisingly common and this sounds like something people would want to do 11/25/2017, 7:26:16 PM - waldyrious (Waldir Pimenta): sorry to interject. @sbrl I assume you'll be leaving soon 11/25/2017, 7:26:31 PM - sbrl (Starbeamrainbowlabs): @waldyrious in ~1/2 hour 11/25/2017, 7:26:45 PM - sbrl (Starbeamrainbowlabs): I'll let you know when I do :-) 11/25/2017, 7:26:53 PM - OrionRandD (OrionRandD): it must be capital p "-P" and has to be near the command itself... 11/25/2017, 7:26:59 PM - waldyrious (Waldir Pimenta): I've been mulling over #1594 and wanted to tell you and @agnivade (and everyone else) about my thoughts 11/25/2017, 7:27:08 PM - OrionRandD (OrionRandD): If you know what I mean... 11/25/2017, 7:27:15 PM - milleniumbug (milleniumbug): OTOH, a missing example in pages X, Y and Z are fixable issues 11/25/2017, 7:28:30 PM - sbrl (Starbeamrainbowlabs): @waldyrious Go ahead! @OrionRandD I see what you mean about `scp`. Personally I haven't noticed since it reads my `~/.ssh/config` file that I've set the custom port numbers in. If you don't have time to create a PR, please open an issue against the main GitHub repository. 11/25/2017, 7:29:44 PM - waldyrious (Waldir Pimenta): I'm thinking about keeping only README.md, CONTRIBUTING.md and LICENSE.md in the root directory, out of convention; and the rest would be in a `docs` folder: docs/governance.md (including info currently in the MAINTAINERS file), docs/style-guide.md, docs/clients.md (the list currently in the README) 11/25/2017, 7:30:16 PM - waldyrious (Waldir Pimenta): possibly a `docs/github-howto.md` and `docs/git-cli-howto.md` moving detailed info currently in CONTRIBUTING.md 11/25/2017, 7:31:29 PM - waldyrious (Waldir Pimenta): the idea is to have CONTRIBUTING.md be a short, self-contained reference for contributing (very much like tldr pages themselves 😃) with links to the other pages in `docs /` for those who need them 11/25/2017, 7:31:39 PM - waldyrious (Waldir Pimenta): what do you think about this overall structure? 11/25/2017, 7:35:42 PM - sbrl (Starbeamrainbowlabs): That's an excellent idea, @waldyrious. I for one vote for that! 11/25/2017, 7:35:47 PM - sbrl (Starbeamrainbowlabs): :+1: 11/25/2017, 7:38:18 PM - agnivade (Agniva De Sarker): hmm .. overall good idea. But I wouldn't want much content removed from CONTRIBUTING.md. I like that I can find all the things I need to be in a single page. 11/25/2017, 7:38:26 PM - agnivade (Agniva De Sarker): Too much jumping around pages is not ideal 11/25/2017, 7:38:36 PM - waldyrious (Waldir Pimenta): yes, fully agreed. 11/25/2017, 7:39:32 PM - waldyrious (Waldir Pimenta): glad we're roughly on the same page. I'll continue fleshing this out then, and make a more concrete proposal asap 11/25/2017, 7:39:48 PM - agnivade (Agniva De Sarker): Great. Yep, please go ahead. 11/25/2017, 7:45:51 PM - sbrl (Starbeamrainbowlabs): 😃 11/25/2017, 7:50:58 PM - agnivade (Agniva De Sarker): @waldyrious - Also, this has been another long standing issue - https://github.com/tldr-pages/tldr/issues/1117. Recently, another person pinged me regarding wanting to be a member. I just gave the usual response and mentioned that we are working on an official process. 11/25/2017, 7:52:41 PM - waldyrious (Waldir Pimenta): That's actually one of the things that would be in the governance.md document I mentioned above. I'm planning to include that in the change I'll propose. 11/25/2017, 7:53:08 PM - agnivade (Agniva De Sarker): ah I see. Perfect. 👏 11/25/2017, 7:53:37 PM - waldyrious (Waldir Pimenta): I think it might be easiest to rebase #1594 to only move things around, then make a separate PR adding the rest of the things. 11/25/2017, 7:54:02 PM - agnivade (Agniva De Sarker): ok, you don't want any changes to it ? 11/25/2017, 7:54:33 PM - waldyrious (Waldir Pimenta): I do. regarding what will go where. Give me 3 minutes and I'll paste an outline here 11/25/2017, 7:54:51 PM - agnivade (Agniva De Sarker): sure 11/25/2017, 8:01:35 PM - waldyrious (Waldir Pimenta): Ok so the current structure is: ``` CONTRIBUTING.md * Guidelines * Markdown format ** Token syntax * Submitting a pull request ** Using Github's web interface ** Using the command line ** Commit message * Licensing ``` 11/25/2017, 8:04:15 PM - waldyrious (Waldir Pimenta): The proposed structure in #1594 is: ``` CONTRIBUTING.md * Submitting a pull request ** Using Github's web interface ** Using the command line ** Commit message * Licensing STYLEGUIDE.md * Layout (was: Markdown format) * Style ** Philosophy (was: Guidelines) ** Token syntax (same title as before) ** Descriptions (was part of the Guidelines section) ``` 11/25/2017, 8:08:34 PM - waldyrious (Waldir Pimenta): I was thinking to keep the Philosophy/Guidelines in the main CONTRIBUTING.md file, and leave STYLEGUIDE.md for the specific rules only 11/25/2017, 8:09:08 PM - waldyrious (Waldir Pimenta): the contribution workflow would later be moved to separate files and summarized briefly in the main CONTRIBUTING.md 11/25/2017, 8:10:06 PM - waldyrious (Waldir Pimenta): But with the first change I mentioned, I think the PR could be merged and then the rest of the reorganization done in a separate PR. Does that make sense? 11/25/2017, 8:10:23 PM - waldyrious (Waldir Pimenta): we could keep the example format in CONTRIBUTING.md as well, to keep it self-contained 11/25/2017, 8:11:35 PM - waldyrious (Waldir Pimenta): (above when I say "specific rules", I mean "less subjective" rules) 11/25/2017, 8:12:51 PM - waldyrious (Waldir Pimenta): @sbrl in case you're still around, your opinion would be welcome as well 11/25/2017, 8:12:57 PM - agnivade (Agniva De Sarker): right, let's keep the example format in CONTRIUTING.md itself. 11/25/2017, 8:13:03 PM - agnivade (Agniva De Sarker): I agree with the other changes. 11/25/2017, 8:13:24 PM - waldyrious (Waldir Pimenta): alright. I'll rebase the branch and will ping you once it's ready :+1: 11/25/2017, 8:14:33 PM - agnivade (Agniva De Sarker): cool 11/25/2017, 8:30:01 PM - agnivade (Agniva De Sarker): Alright, we are officially ready for GCI ! I have added the final commands https://github.com/tldr-pages/tldr/issues?q=is%3Aissue+is%3Aopen+label%3Agci 11/25/2017, 8:30:16 PM - agnivade (Agniva De Sarker): I have kept 2 issues for css .. I think css deserves to be its own language :) 11/25/2017, 8:30:36 PM - waldyrious (Waldir Pimenta): 👏 great work @agnivade : ) 11/25/2017, 8:33:19 PM - agnivade (Agniva De Sarker): ping @jayvdb to notify. 11/25/2017, 8:51:48 PM - waldyrious (Waldir Pimenta): Looks like I pushed github too far 😕 #1594 has been closed following the rebase, so I had to open #1665 as a resubmission (commit authorship preserved) 11/25/2017, 8:51:59 PM - waldyrious (Waldir Pimenta): @sbrl @agnivade please take a look : ) 11/25/2017, 10:18:28 PM - sbrl (Starbeamrainbowlabs): Hey! Sorry, I forgot to say when I was leaving 😅 Yeah, that PR looks good to me! Yeah - let's include the actual adding of things in a separate PR to keep things simple. 11/25/2017, 10:18:48 PM - sbrl (Starbeamrainbowlabs): I've approved #1665 11/25/2017, 10:19:25 PM - jayvdb (John Vandenberg): :+1: 11/25/2017, 10:19:34 PM - jayvdb (John Vandenberg): looks good. 11/25/2017, 10:19:37 PM - sbrl (Starbeamrainbowlabs): and awesome, @agnivade! So as a reminder, GCI participants comment on the GH issue to say they are doing it, then they send a PR which closes the issue which we then merge 11/25/2017, 10:19:45 PM - sbrl (Starbeamrainbowlabs): am I right? 11/25/2017, 10:19:55 PM - sbrl (Starbeamrainbowlabs): (Just want to be clear in my own head) 11/25/2017, 10:22:11 PM - sbrl (Starbeamrainbowlabs): I've just noticed that we don't mention in the GCI task description that they should comment on the issue that they are intending to do 11/25/2017, 10:22:33 PM - sbrl (Starbeamrainbowlabs): Would this be obvious, do you think - or do we need to spell that out in the description more clearly? 11/25/2017, 11:28:14 PM - jayvdb (John Vandenberg): better to be precise, IMO 11/25/2017, 11:28:49 PM - jayvdb (John Vandenberg): often they have no idea what to do, and are also 'scared' of doing something wrong; shy 11/26/2017, 9:37:13 AM - agnivade (Agniva De Sarker): Yep, agree. Please update the task description to reflect that. 11/26/2017, 2:56:20 PM - sbrl (Starbeamrainbowlabs): Ah, as I thought. I'll update it then. 11/26/2017, 3:03:39 PM - sbrl (Starbeamrainbowlabs): Updated. 11/26/2017, 3:05:27 PM - sbrl (Starbeamrainbowlabs): Who's the _Anish Mukherjee_ person listed as a mentor? 11/26/2017, 4:45:24 PM - jayvdb (John Vandenberg): I can remove them 11/26/2017, 4:46:20 PM - jayvdb (John Vandenberg): The gci system lets any mentor do mentoring of any tasks 11/26/2017, 4:47:17 PM - jayvdb (John Vandenberg): Org admins will send out mentor guidelines to prevent that 11/26/2017, 5:52:27 PM - jayvdb (John Vandenberg): I think the 'linux' tag should be removed from most of these ; as they also work on windows 11/26/2017, 5:52:38 PM - sbrl (Starbeamrainbowlabs): ? 11/26/2017, 5:52:57 PM - jayvdb (John Vandenberg): linter & static analysis would be good tags to add 11/26/2017, 5:54:49 PM - jayvdb (John Vandenberg): also e.g. `csscomb` is node , so maybe add `node` as tag, to attract kids interested in that 11/26/2017, 5:55:15 PM - jayvdb (John Vandenberg): the language of each linter is available on https://docs.google.com/spreadsheets/d/1zvEIEnseTUFg1vvQCYPlB7nsWDcjt2O9BtExQtGiqOY/edit#gid=503641928 11/26/2017, 5:56:15 PM - jayvdb (John Vandenberg): "Create a new tldr page ..." -> "Create a new tldr (markdown language) page .." ? 11/26/2017, 5:56:56 PM - jayvdb (John Vandenberg): ^ that might make the participants feel more comfortable with the task 11/26/2017, 5:58:40 PM - jayvdb (John Vandenberg): I can batch update the tasks if we have a template I can use, substituting in the issue no. & linter name & tags for each 11/26/2017, 5:58:50 PM - jayvdb (John Vandenberg): im working on the batch task uploader now (tonight) 😉 11/26/2017, 6:01:42 PM - sbrl (Starbeamrainbowlabs): "Create a new tldr (markdown language) page" -> "Create a new tldr page in markdown"? 11/26/2017, 6:01:52 PM - jayvdb (John Vandenberg): :+1: 1/14/2023, 3:07:04 PM - @amosbird-54e48ded15522ed4b3dc26b7:gitter.im joined the room 11/26/2017, 6:45:09 PM - @amosbird-54e48ded15522ed4b3dc26b7:gitter.im: hello, what client do you guys use? 11/26/2017, 6:45:19 PM - @amosbird-54e48ded15522ed4b3dc26b7:gitter.im: i tried c++ and go but neither work 11/26/2017, 8:14:20 PM - sbrl (Starbeamrainbowlabs): Hey, @amosbird! I use the bash client. 11/27/2017, 10:53:29 AM - agnivade (Agniva De Sarker): @amosbird - Please file a bug in the respective client's repo if you face any issues. 1/14/2023, 3:07:07 PM - marekdominiak (marekdominiak) joined the room 11/27/2017, 12:50:59 PM - marekdominiak (marekdominiak): Looks like I'm getting ``` -> tldr tldr -l Known tldr pages: 301 Moved Permanently

301 Moved Permanently

nginx
``` 11/27/2017, 2:35:28 PM - agnivade (Agniva De Sarker): @marekdominiak - You have to be a bit more specific here. Is this an issue you are facing ? Which client are you using ? What is the `-l` for ? 11/27/2017, 3:38:24 PM - marekdominiak (marekdominiak): @agnivade I installed the tldr via npm, and I tried to invoke it from the command line (fish under ubuntu) I have run `tldr tar` but it returns "tldr page for command tar not found" then I wanted to see the list of available commands tldr is defined for with `tldr -l` however I got the 301 moved permanently 11/27/2017, 3:42:58 PM - agnivade (Agniva De Sarker): You say you did `tldr -l`, but the screenshot says `tldr tldr -l`. 11/27/2017, 3:44:16 PM - agnivade (Agniva De Sarker): Anyways, please open an issue in the tldr node client repo with appropriate details like node version, OS, and exact repro steps for the issue so that we can debug this. 11/27/2017, 3:55:31 PM - marekdominiak (marekdominiak): @agnivade it was copy paste from the command line (my bad), the first tldr was the current directory of fish 11/27/2017, 3:56:27 PM - marekdominiak (marekdominiak): I will do that, but before opening I will just check if I don't have and strange npm/nodejs settings locally 11/27/2017, 8:47:19 PM - agnivade (Agniva De Sarker): @/all - There seems to be a sudden surge of traffic. Lots of issues created. 11/27/2017, 8:47:38 PM - agnivade (Agniva De Sarker): [![ss.png](https://files.gitter.im/tldr-pages/tldr/uiUU/thumb/ss.png)](https://files.gitter.im/tldr-pages/tldr/uiUU/ss.png) 11/27/2017, 8:48:19 PM - agnivade (Agniva De Sarker): Interestingly, the referring sites seem to be github mainly. So not sure how this is happening all of a sudden. 11/27/2017, 8:48:24 PM - agnivade (Agniva De Sarker): Is this due to GCI ? 11/27/2017, 8:50:24 PM - waldyrious (Waldir Pimenta): you mean lots of forks created, right? 11/27/2017, 8:50:58 PM - agnivade (Agniva De Sarker): It just shows clones and visitors. Not forks. 11/27/2017, 8:51:11 PM - agnivade (Agniva De Sarker): The visitors graph has spiked considerably 11/27/2017, 8:51:25 PM - waldyrious (Waldir Pimenta): I believe forks = clones in github parlance 11/27/2017, 8:51:56 PM - agnivade (Agniva De Sarker): huh .. 11/27/2017, 8:52:05 PM - waldyrious (Waldir Pimenta): I was just making sure I wasn't missing anything, since the list of issues doesn't show many issues being created 11/27/2017, 8:52:20 PM - waldyrious (Waldir Pimenta): that could be problematic depending on the nature of the issues 11/27/2017, 8:52:37 PM - waldyrious (Waldir Pimenta): (i.e. time-consuming to handle) 11/27/2017, 8:53:25 PM - agnivade (Agniva De Sarker): I dont have hard nos. but there has never been so many issues created per day. And they are mostly general questions and setup problems. So yea, there is a definite uptick in issues. 11/27/2017, 8:53:35 PM - agnivade (Agniva De Sarker): Its okay - I have some time in my hand. 11/27/2017, 8:54:51 PM - agnivade (Agniva De Sarker): but on the flip side, I see lots of PRs too :) which is great. 11/27/2017, 8:55:18 PM - waldyrious (Waldir Pimenta): just to make sure we're on the same page: I see 13 issues created in the past 4 days (not counting PRs). Does this match what you're seeing? 11/27/2017, 8:55:52 PM - waldyrious (Waldir Pimenta): before that the most recent issue was created 20 days ago according to github: https://github.com/tldr-pages/tldr/issues 11/27/2017, 8:56:24 PM - agnivade (Agniva De Sarker): Yea sure, I don't have the nos. It was just a mental impression. 11/27/2017, 8:56:38 PM - waldyrious (Waldir Pimenta): Ok :+1: 11/27/2017, 8:56:49 PM - agnivade (Agniva De Sarker): when I say "so many issues created per day" - I meant like 3-4. 11/27/2017, 8:56:51 PM - waldyrious (Waldir Pimenta): I'll reserve a couple hours today to help out :) 11/27/2017, 8:57:07 PM - waldyrious (Waldir Pimenta): hehe yeah I get it. The graph scared me for a second 11/27/2017, 8:57:14 PM - milleniumbug (milleniumbug): If you're wondering why there's a sudden influx of people, you're on Hacker News 11/27/2017, 8:57:19 PM - milleniumbug (milleniumbug): https://news.ycombinator.com/item?id=15779382 11/27/2017, 8:57:33 PM - waldyrious (Waldir Pimenta): oh! that makes sense, thanks for the pointer! 11/27/2017, 8:57:36 PM - agnivade (Agniva De Sarker): ah ! I have fallen behind on my HN feed. 11/27/2017, 8:59:40 PM - agnivade (Agniva De Sarker): oh wow .. huge discussion. Let me see if I can help out. 11/27/2017, 10:46:43 PM - sbrl (Starbeamrainbowlabs): Oh, wow! It's blown up! I'll help out in an hour or two. 11/27/2017, 10:47:14 PM - sbrl (Starbeamrainbowlabs): I had 50 notifications this morning 11/27/2017, 10:47:24 PM - sbrl (Starbeamrainbowlabs): followed my another 20 emails at lunch time 11/27/2017, 10:47:29 PM - sbrl (Starbeamrainbowlabs): and another 38 now O.O 11/27/2017, 11:04:01 PM - sbrl (Starbeamrainbowlabs): Why did you close issue #1600, @agnivade? 11/27/2017, 11:22:26 PM - sbrl (Starbeamrainbowlabs): In #1672 there's an 'approval' by someone who's not in our org yet 11/27/2017, 11:23:03 PM - sbrl (Starbeamrainbowlabs): @agnivade / @waldyrious thoughts? 11/27/2017, 11:25:51 PM - waldyrious (Waldir Pimenta): github allows that, but our convention is 2 approvals by maintainers, so IMO we should stick to that, unless 2 maintainers are not available in a reasonable time frame (#1209) 11/27/2017, 11:27:20 PM - waldyrious (Waldir Pimenta): that said, non-maintainer approvals are still welcome! reviewing other PRs is a great way to get started in the path to maintainership : ) 11/27/2017, 11:27:28 PM - sbrl (Starbeamrainbowlabs): Ah, ok. I was just thinking that it would be good if I had something to point said user at in that instance 11/27/2017, 11:28:08 PM - waldyrious (Waldir Pimenta): If all goes according to plan, there will soon (but I've been known to say that before 😇) 11/27/2017, 11:30:12 PM - sbrl (Starbeamrainbowlabs): lol ok 😛 thanks 😃 11/27/2017, 11:58:33 PM - agnivade (Agniva De Sarker): I closed #1600 and couple of others in accordance with our GCI plan that every programming language will have only 2 tasks. 11/28/2017, 12:05:57 AM - sbrl (Starbeamrainbowlabs): Ah, ok @agnivade! Have you deleted the associated GCI tasks too? 11/28/2017, 12:06:20 AM - sbrl (Starbeamrainbowlabs): Also I think #1632 seems to have slipped through the net 11/28/2017, 12:10:13 AM - sbrl (Starbeamrainbowlabs): That's all my notifications cleared up! 😃 11/28/2017, 12:12:38 AM - sbrl (Starbeamrainbowlabs): For future reference, what on earth is this _Hacker News_ thing? 11/28/2017, 12:49:05 AM - waldyrious (Waldir Pimenta): @sbrl it's an online forum for tech-related topics. I suppose it is kind of a modern-day Slashdot (although you may not know that one either) 11/28/2017, 12:51:49 AM - waldyrious (Waldir Pimenta): it was created by Y-Combinator, the startup incubator, so the audience there has a sizeable proportion of young programmers and other comp-sci types, which means it's a good place to stay up-to date on the latest trends in programming languages, frameworks, and even general commentary on recent science and technology news 11/28/2017, 12:52:01 AM - waldyrious (Waldir Pimenta): oh well, I should've just linked to wikipedia xD 11/28/2017, 12:53:55 AM - waldyrious (Waldir Pimenta): anyway, changing subject a bit: I've submitted #1694 (coincidentally a follow-up of #1594!) -- I'd like you and @agnivade to take a look when you get the chance. 11/28/2017, 1:08:19 AM - sbrl (Starbeamrainbowlabs): Looks ok to me! 😃 11/28/2017, 1:08:57 AM - sbrl (Starbeamrainbowlabs): I'll be glad to get us finally making progress towards #1117 and #1209 😛 11/28/2017, 1:10:19 AM - waldyrious (Waldir Pimenta): Yeah, I wish I had the time to work on tldr as I'd like to. The list of stuff I want to do just keeps growing... 11/28/2017, 1:12:56 AM - sbrl (Starbeamrainbowlabs): Ah, don't worry! We've been holding down the fort, so to speak 😛 The compiler I'm writing for uni is due on Thursday and I'm in a good position with it, so I've got free time atm 😛 11/28/2017, 1:13:30 AM - sbrl (Starbeamrainbowlabs): If I help out dealing with all the little stuff, then it helps to free you up for the bigger stuff lol 11/28/2017, 1:15:00 AM - waldyrious (Waldir Pimenta): Yeah, I'm glad you guys are around 😃 which is why I really want to flesh out the project governance docs. We need to make it easier for new maintainers to come along. 11/28/2017, 2:01:59 AM - sbrl (Starbeamrainbowlabs): Absolutely :+1: 11/28/2017, 8:58:46 AM - agnivade (Agniva De Sarker): Ah you are writing a compiler ! Very nice. We had a similar task too when I was in college. Mainly some lex and yacc stuff. But it was a haphazard effort. I wish I could go back and redo some stuff 😆 11/28/2017, 9:00:42 AM - jayvdb (John Vandenberg): @waldyrious , I still have you listed as a mentor who hasnt accepted the invite 11/28/2017, 9:00:59 AM - jayvdb (John Vandenberg): maybe you didnt get the emails from GCI ? 11/28/2017, 9:01:26 AM - jayvdb (John Vandenberg): or you're not sure about signing up? 11/28/2017, 9:06:26 AM - agnivade (Agniva De Sarker): Also, I see that the instance count for the tldr task is 34. Shouldn't it be 12 ? Since we have 12 issues on github. 11/28/2017, 9:06:47 AM - jayvdb (John Vandenberg): wow 11/28/2017, 9:07:22 AM - jayvdb (John Vandenberg): oh 11/28/2017, 9:07:37 AM - jayvdb (John Vandenberg): there were 34 total ; only 12 of those were for tldr 11/28/2017, 9:08:13 AM - jayvdb (John Vandenberg): and one of those tasks is a generic task, which doesnt need its own issue 11/28/2017, 9:09:23 AM - agnivade (Agniva De Sarker): Ok so you are saying the instance count is not tied down to a single task 11/28/2017, 9:10:59 AM - jayvdb (John Vandenberg): the tasks which mention a specific command can only have one solution -- a merged PR for that page. 11/28/2017, 9:11:39 AM - jayvdb (John Vandenberg): We only have one 'instance' for those tasks, so two students dont try to submit the same PR 11/28/2017, 9:12:11 AM - agnivade (Agniva De Sarker): Oh ? Can you give me that link. I think we are looking at different things. I am seeing only 1 task in my dashboard, and its a generic task. Not tied to any command. 11/28/2017, 9:12:14 AM - jayvdb (John Vandenberg): after those 11 are 'taken', we'll create more 😉 11/28/2017, 9:12:51 AM - jayvdb (John Vandenberg): in the dashboard [tasks](https://codein.withgoogle.com/dashboard/tasks/), unselect "My tasks" 11/28/2017, 9:13:01 AM - jayvdb (John Vandenberg): it is down the bottom 11/28/2017, 9:14:06 AM - jayvdb (John Vandenberg): you should see another 11 tasks, which you can self-assign to be the mentor of 11/28/2017, 9:14:13 AM - jayvdb (John Vandenberg): or I can do it for you 😉 11/28/2017, 9:15:15 AM - agnivade (Agniva De Sarker): got it now. 11/28/2017, 9:16:23 AM - jayvdb (John Vandenberg): the generic task is not published; we'll publish that one after some students have done the first 11 11/28/2017, 9:17:09 AM - jayvdb (John Vandenberg): we'll learn a lot in the first few days, which we can use to ensure we're ready to have 34 students working concurrently 11/28/2017, 9:27:03 AM - agnivade (Agniva De Sarker): Ok I have added the new pages to match with the issues in github. 11/28/2017, 9:27:07 AM - agnivade (Agniva De Sarker): Please publish them 11/28/2017, 9:27:31 AM - agnivade (Agniva De Sarker): And please remove cpplint, golint, csscomb and ruby tasks 11/28/2017, 9:28:07 AM - agnivade (Agniva De Sarker): I couldnt seem to add tags though. Maybe I don't have enough permissions 11/28/2017, 9:31:18 AM - jayvdb (John Vandenberg): why remove cpplint, golint, csscomb and ruby ? 11/28/2017, 9:31:24 AM - jayvdb (John Vandenberg): I've published the ones you've added 11/28/2017, 9:31:30 AM - jayvdb (John Vandenberg): and added tags to one of them 11/28/2017, 9:31:50 AM - agnivade (Agniva De Sarker): ruby was already taken by someone before gci could start 11/28/2017, 9:31:53 AM - jayvdb (John Vandenberg): you should be able to add tags 11/28/2017, 9:32:07 AM - agnivade (Agniva De Sarker): and about others, I think we decided to keep 2 tasks per language 11/28/2017, 9:32:11 AM - agnivade (Agniva De Sarker): so I removed them 11/28/2017, 9:34:15 AM - jayvdb (John Vandenberg): unpublished 11/28/2017, 9:34:33 AM - agnivade (Agniva De Sarker): thanks :) We are now set ! 11/28/2017, 9:35:10 AM - jayvdb (John Vandenberg): I have marked the 'ruby' one with 'DNP' (do not publish) . Can you replace ruby with some other command which we will want a page for, after the first batch ? 11/28/2017, 9:35:29 AM - agnivade (Agniva De Sarker): hmm .. let me see 11/28/2017, 9:36:15 AM - jayvdb (John Vandenberg): https://github.com/tldr-pages/tldr/issues/1218 - astyle can be closed ? 11/28/2017, 9:37:15 AM - agnivade (Agniva De Sarker): Yep. done. Lot of times, people forget to add the auto-close tags. 11/28/2017, 9:38:42 AM - jayvdb (John Vandenberg): what about we convert the ruby one into a task about https://github.com/tldr-pages/tldr/issues/749 11/28/2017, 9:39:13 AM - jayvdb (John Vandenberg): that is a slightly more advanced task, as it requires understanding the existing pages, and will also involve more communication with your team 11/28/2017, 9:40:26 AM - jayvdb (John Vandenberg): if you like that idea, in the task description, state that a prerequisite for the csvkit task is completing one of the other 'new tldr page' tasks first 11/28/2017, 10:02:24 AM - agnivade (Agniva De Sarker): I'd rather keep it simple. 11/28/2017, 10:02:44 AM - agnivade (Agniva De Sarker): Doing #749 is a bit complicated and requires deeper understanding 11/28/2017, 10:02:56 AM - jayvdb (John Vandenberg): nod, ok 11/28/2017, 10:24:49 AM - agnivade (Agniva De Sarker): @jayvdb - I am still not able to edit tags 11/28/2017, 10:28:20 AM - jayvdb (John Vandenberg): try a different browser? 11/28/2017, 10:29:54 AM - jayvdb (John Vandenberg): ive asked some other mentors to also test if they can modify tags 11/28/2017, 10:35:26 AM - jayvdb (John Vandenberg): they say they can 😕 11/28/2017, 10:35:33 AM - jayvdb (John Vandenberg): anyway, ive put some tags on all your task 11/28/2017, 10:36:39 AM - jayvdb (John Vandenberg): @agnivade , can you assign yourself to the tasks written by @sbrl ? 11/28/2017, 10:36:57 AM - agnivade (Agniva De Sarker): ok seems to work in ff 11/28/2017, 10:37:08 AM - agnivade (Agniva De Sarker): > can you assign yourself to the tasks written by @sbrl ? 11/28/2017, 10:37:11 AM - agnivade (Agniva De Sarker): yea will do 11/28/2017, 10:37:32 AM - agnivade (Agniva De Sarker): about the ruby task - I am thinking of changing it to tsc. We don't have a page for that yet 11/28/2017, 10:44:08 AM - agnivade (Agniva De Sarker): Updated it to tsc. 11/28/2017, 11:17:25 AM - agnivade (Agniva De Sarker): Hey @waldyrious - whenever you get some time, can you take a quick look at https://github.com/tldr-pages/tldr/pull/1675#issuecomment-347420243 ? Just need your opinion on this. 11/28/2017, 2:51:39 PM - waldyrious (Waldir Pimenta): @jayvdb I've been having some rough weeks, and to be honest I've been kind of avoiding handling my email. I sent you a message so we can clarify the best way I can help out with GCI. 11/28/2017, 2:51:56 PM - waldyrious (Waldir Pimenta): @agnivade sure, I'll take a look 11/28/2017, 2:51:59 PM - jayvdb (John Vandenberg): no worries 11/28/2017, 3:15:14 PM - waldyrious (Waldir Pimenta): @agnivade I left a comment on #1675 11/28/2017, 3:15:55 PM - agnivade (Agniva De Sarker): great, taking a look 11/28/2017, 3:16:45 PM - waldyrious (Waldir Pimenta): also, @agnivade and @sbrl: I chatted with @jayvdb a bit and I'll sign up as a GCI mentor, but I won't be able to process the emails for the time being. I'll mostly be available here on gitter, so please let me know here if I'm needed for anything. 11/28/2017, 3:17:11 PM - sbrl (Starbeamrainbowlabs): Ok, sure! 11/28/2017, 3:17:25 PM - agnivade (Agniva De Sarker): that's great. Thanks for being here. 11/28/2017, 3:17:41 PM - sbrl (Starbeamrainbowlabs): 😃 11/28/2017, 3:17:48 PM - sbrl (Starbeamrainbowlabs): It's almost about to start - 5pm today it opens 11/28/2017, 3:18:34 PM - waldyrious (Waldir Pimenta): thanks for understanding : ) I did suggest we enter GCI so it's the least I can do! 11/28/2017, 3:18:55 PM - sbrl (Starbeamrainbowlabs): lol yeah! 11/28/2017, 3:19:09 PM - sbrl (Starbeamrainbowlabs): It's just a shame I'll be leaving a virtual environments lecture at 5pm 11/28/2017, 3:19:24 PM - sbrl (Starbeamrainbowlabs): with a 1hr trip home 😕 11/28/2017, 3:19:46 PM - waldyrious (Waldir Pimenta): I'll be around at that time :) 11/28/2017, 3:25:16 PM - agnivade (Agniva De Sarker): @waldyrious - replied to #1675 11/28/2017, 10:32:02 PM - waldyrious (Waldir Pimenta): so... GCI's live, right? 11/28/2017, 10:40:49 PM - jayvdb (John Vandenberg): yup 11/28/2017, 10:47:22 PM - waldyrious (Waldir Pimenta): @agnivade do you see the vulnerability warning at https://github.com/tldr-pages/tldr-node-client? 11/28/2017, 10:48:09 PM - agnivade (Agniva De Sarker): Yes I am aware. This is due to a PR which changed dependencies to the caret format from tilde format. 11/28/2017, 10:48:22 PM - agnivade (Agniva De Sarker): It is on my TODO list. Will take care 11/28/2017, 10:49:03 PM - waldyrious (Waldir Pimenta): Cool. I assumed you were aware, but wanted to make sure just in case : ) 11/28/2017, 10:52:50 PM - jayvdb (John Vandenberg): seven students working on the 'create your accounts' task 11/28/2017, 11:35:50 PM - sbrl (Starbeamrainbowlabs): Oooh, the dashboard has changed, yeah 11/28/2017, 11:36:05 PM - sbrl (Starbeamrainbowlabs): I guess that you see more than I do, @jayvdb? 11/28/2017, 11:37:08 PM - agnivade (Agniva De Sarker): you can untick the mytasks checkbox to see all 11/28/2017, 11:38:48 PM - sbrl (Starbeamrainbowlabs): Ah, cool! Thanks, @agnivade 😃 11/28/2017, 11:39:06 PM - sbrl (Starbeamrainbowlabs): Looks like 4 on setup, & 2 on gitlab ci 11/28/2017, 11:39:30 PM - waldyrious (Waldir Pimenta): are all tldr-pages tasks assigned to you two? or did you pick the ones you were comfortable with mentoring? 11/28/2017, 11:41:00 PM - agnivade (Agniva De Sarker): yea its assigned to both of us. 11/28/2017, 11:41:17 PM - sbrl (Starbeamrainbowlabs): Yeah, I think all of them are assigned to me 11/28/2017, 11:41:19 PM - agnivade (Agniva De Sarker): gives more flexibility in case one of us is not active 11/28/2017, 11:41:23 PM - sbrl (Starbeamrainbowlabs): yeah 11/28/2017, 11:41:27 PM - waldyrious (Waldir Pimenta): I guess I can add myself as well, then 11/28/2017, 11:42:48 PM - sbrl (Starbeamrainbowlabs): It looks like it might take a while for the students to 'filter through the system', so to speak lol 😛 11/28/2017, 11:42:49 PM - waldyrious (Waldir Pimenta): @jayvdb I can paste task links here, right? 11/28/2017, 11:44:38 PM - jayvdb (John Vandenberg): yes you can 11/28/2017, 11:44:46 PM - waldyrious (Waldir Pimenta): :+1: 11/28/2017, 11:45:37 PM - waldyrious (Waldir Pimenta): 1 question: why does this task have 3 mentors while the other tldr-pages tasks have 2? 11/28/2017, 11:45:42 PM - waldyrious (Waldir Pimenta): https://codein.withgoogle.com/dashboard/tasks/6102656995033088/ 11/29/2017, 12:14:33 AM - waldyrious (Waldir Pimenta): another question: why does this task only have one mentor? an overlook, I assume? https://codein.withgoogle.com/dashboard/tasks/5285165687373824/ 11/29/2017, 12:23:40 AM - agnivade (Agniva De Sarker): yes. 11/29/2017, 12:24:31 AM - agnivade (Agniva De Sarker): Regarding your previous question, you can scroll up @jayvdb had answered it previously. @sbrl had asked the same question too. Don't remember the answer though 😛 11/29/2017, 12:26:47 AM - jayvdb (John Vandenberg): because you havent assigned yourself to them 😛 11/29/2017, 12:27:47 AM - agnivade (Agniva De Sarker): no no .. this is the anish mukherjee thingy 11/29/2017, 12:31:51 AM - jayvdb (John Vandenberg): oh ... gotcha 11/29/2017, 12:50:52 AM - jayvdb (John Vandenberg): I've unassigned Anish 11/29/2017, 1:14:31 AM - sbrl (Starbeamrainbowlabs): Ok, just about to do a server reboot - so @tldr-bot won't be available for ~5 mins 11/29/2017, 1:18:29 AM - sbrl (Starbeamrainbowlabs): Reboot complete! 11/29/2017, 1:19:23 AM - sbrl (Starbeamrainbowlabs): Apparently tldr-bot doesn't start on boot 11/29/2017, 1:19:24 AM - sbrl (Starbeamrainbowlabs): hrm 11/29/2017, 1:23:35 AM - sbrl (Starbeamrainbowlabs): Fixed that - we'll know whether my fix worked in a few weeks time 😛 11/29/2017, 10:14:24 AM - agnivade (Agniva De Sarker): I believe you need to add a `After=network.target` in the [Unit] section of the systemctl service 11/29/2017, 10:14:29 AM - agnivade (Agniva De Sarker): is that what you did ? 11/29/2017, 11:41:50 AM - agnivade (Agniva De Sarker): @waldyrious - pushed a minor fix here https://github.com/tldr-pages/tldr/commit/4b638bfc34f42ebec824a687613bf5521e588a48 11/29/2017, 3:29:31 PM - sbrl (Starbeamrainbowlabs): Nope, I added it to rc.local because it is complaining about 'too many levels of symbolic links when I try to enable it on boot (even though I don't think there are any) 11/29/2017, 3:29:52 PM - sbrl (Starbeamrainbowlabs): I do have `WantedBy=multi-user.target` though 11/29/2017, 3:34:03 PM - agnivade (Agniva De Sarker): ok, that should also work 11/29/2017, 3:34:19 PM - agnivade (Agniva De Sarker): did you do `systemctl enable tldr-bot` ? 11/29/2017, 3:34:39 PM - agnivade (Agniva De Sarker): I think that needs to be done to let systemd know to automatically start it 1/14/2023, 3:08:10 PM - realchriswells (realchriswells) joined the room 11/29/2017, 4:03:53 PM - realchriswells (realchriswells): Hi folks, perhaps it's just me being dumber than rocks, but I've gone and done an `npm install -g tldr` and it's installed without issue, but when I try to use it I get an error: ``` /usr/local/lib/node_modules/tldr/node_modules/natural/lib/natural/classifiers/classifier.js:32 if (e.code !== 'MODULE_NOT_FOUND') throw e; ``` 11/29/2017, 4:04:35 PM - realchriswells (realchriswells): This is on MacOS 10.13 11/29/2017, 4:39:21 PM - sbrl (Starbeamrainbowlabs): (that's the point - it says `Failed to execute operation: Too many levels of symbolic links` if I try to enable it - hence the editing of rc.local 😛) 11/29/2017, 5:27:14 PM - agnivade (Agniva De Sarker): @sbrl - ah it fails when you enable it. hmm .. 11/29/2017, 5:28:18 PM - agnivade (Agniva De Sarker): @realchriswells - I am guessing you are encountering something similar to https://github.com/tldr-pages/tldr-node-client/issues/179 11/29/2017, 5:28:59 PM - agnivade (Agniva De Sarker): try out the solution which worked here - https://github.com/tldr-pages/tldr-node-client/issues/179#issuecomment-347014392 11/29/2017, 5:49:51 PM - realchriswells (realchriswells): Thanks for the @agnivade - works a treat now! 11/29/2017, 5:50:05 PM - realchriswells (realchriswells): and strangely I tried finding that but no joy 11/29/2017, 5:51:37 PM - agnivade (Agniva De Sarker): I will try adding a section to the README. 11/29/2017, 8:55:19 PM - agnivade (Agniva De Sarker): what the heck is this - https://github.com/tldr-pages/tldr/wiki/Automated-test-and-generate-RESTful-API-documentation-through-rest-client ? 11/29/2017, 8:55:23 PM - agnivade (Agniva De Sarker): seems like spam ? 11/29/2017, 8:55:38 PM - agnivade (Agniva De Sarker): seems like anybody can create / edit wiki pages .. 11/29/2017, 10:06:47 PM - sbrl (Starbeamrainbowlabs): Yeah - that's correct 11/29/2017, 10:10:05 PM - sbrl (Starbeamrainbowlabs): also, we had our first task claimed - even though it was abandoned 5 mins later lol 11/29/2017, 10:10:29 PM - agnivade (Agniva De Sarker): right .. got a mail 1/14/2023, 3:09:12 PM - Mixih (mixih) joined the room 11/30/2017, 9:06:27 AM - Mixih (mixih): good evening. I'm Mixih from the coala organization, and we're currently doing a rewrite of our GCI wiki page. Is there a specific link you would like us to put there for GCI? 11/30/2017, 9:11:11 AM - agnivade (Agniva De Sarker): Good morning. You can put http://tldr.sh as a link 11/30/2017, 9:11:29 AM - Mixih (mixih): Thanks! 1/14/2023, 3:09:14 PM - andrewda (Andrew Dassonville) joined the room 11/30/2017, 10:10:36 AM - andrewda (Andrew Dassonville): 👋 Hello from GCI, by the way! I've used tldr in the past, but I'm really excited to start contributing! 11/30/2017, 10:12:45 AM - agnivade (Agniva De Sarker): Hi there. :) Thanks for your contribution ! 11/30/2017, 3:06:40 PM - sbrl (Starbeamrainbowlabs): Hey there, @andrewda! 11/30/2017, 3:28:15 PM - jayvdb (John Vandenberg): > what the heck is this - https://github.com/tldr-pages/tldr/wiki/Automated-test-and-generate-RESTful-API-documentation-through-rest-client ? 😉 github spam. script kidding pissing off people who build 'earth scale' automated systems is not smart 11/30/2017, 3:28:51 PM - waldyrious (Waldir Pimenta): @agnivade about the minor fix (tldr-pages/tldr@4b638bf): thanks, I did test the links on the branch but for some reason it doesn't work the same way live, I guess 11/30/2017, 3:29:52 PM - agnivade (Agniva De Sarker): @sbrl - can you look into #1717 and #1718 when you get a chance ? Those are the GCI PRs. 11/30/2017, 3:32:42 PM - waldyrious (Waldir Pimenta): > seems like anybody can create / edit wiki pages .. Yes. Do you think it shouldn't be the case? I like that wikis provide a way for people to do quick edits without needing maintainers to intervene. In fact, that's kind of the definition of a wiki: anyone can edit, with minimal barriers 11/30/2017, 3:34:08 PM - sbrl (Starbeamrainbowlabs): Reviewed #1717 11/30/2017, 3:34:10 PM - agnivade (Agniva De Sarker): It's okay. Unfortunately the internet is filled with trolls. Wikipedia pages are also trolled from time to time. 11/30/2017, 3:34:53 PM - waldyrious (Waldir Pimenta): Yeah, but fortunately such instances are rarer than legitimate edits (and the cleanup is easy, too) 11/30/2017, 3:35:23 PM - waldyrious (Waldir Pimenta): regarding the GCI tasks: if I click "assign me" that'll add me as a mentor? 11/30/2017, 3:35:54 PM - waldyrious (Waldir Pimenta): I thought assignees were the people who were to complete the tasks 11/30/2017, 3:36:12 PM - sbrl (Starbeamrainbowlabs): Reviewed & merged #1718 11/30/2017, 3:36:23 PM - agnivade (Agniva De Sarker): :+1: 11/30/2017, 3:36:50 PM - sbrl (Starbeamrainbowlabs): Right, got to travel to uni now 11/30/2017, 3:37:00 PM - waldyrious (Waldir Pimenta): 👋 see ya! 11/30/2017, 3:37:10 PM - sbrl (Starbeamrainbowlabs): I'llr eviewt he rest of the PRs later today. I don't think I need to update the GCI dashboard, right? 11/30/2017, 3:38:12 PM - sbrl (Starbeamrainbowlabs): 👋 11/30/2017, 3:43:21 PM - waldyrious (Waldir Pimenta): @jayvdb why is the tsc task marked DNP? https://codein.withgoogle.com/dashboard/tasks/6017418201661440/ 11/30/2017, 4:32:03 PM - jayvdb (John Vandenberg): DO NOT PUBLISH :-) 11/30/2017, 4:32:44 PM - jayvdb (John Vandenberg): it was 'ruby' iirc, but someone did that page before GCI started 11/30/2017, 5:21:43 PM - waldyrious (Waldir Pimenta): Yeah, I found your previous message in this room explaining the acronym -- what I wanted to understand was the purpose of keeping the task on the list. Is there a reason it isn't simply deleted? Or is it being adapted to the `tsc` command and then it'll be published? I'm trying to understand the workflow : ) 11/30/2017, 5:53:56 PM - agnivade (Agniva De Sarker): @jayvdb wanted this new page to be ready in case the students finish all the tasks 11/30/2017, 6:06:52 PM - waldyrious (Waldir Pimenta): @agnivade should we still be marked as mentors? Only @sbrl is marked as its mentor atm 11/30/2017, 6:07:12 PM - waldyrious (Waldir Pimenta): (thanks for the explanation btw!) 11/30/2017, 6:08:23 PM - jayvdb (John Vandenberg): you can, and should, self-assign as mentors of any tldr task 11/30/2017, 6:09:13 PM - waldyrious (Waldir Pimenta): :+1: 12/1/2017, 1:37:30 AM - sbrl (Starbeamrainbowlabs): Reviewed #1723 for GCI 12/1/2017, 2:55:08 AM - jayvdb (John Vandenberg): I think we'll need to arrange some harder tldr tasks 😉 12/1/2017, 2:55:42 AM - jayvdb (John Vandenberg): @andrewda , you might like to tackle a linterhub task next ; have you played with Docker at all ? 12/1/2017, 4:38:52 AM - andrewda (Andrew Dassonville): @jayvdb I've used it a bit but haven't set up any environments before. Will look into the task! 12/1/2017, 4:49:38 AM - jayvdb (John Vandenberg): Ping the mentor in Zulip 😉 12/1/2017, 4:52:30 AM - sbrl (Starbeamrainbowlabs): Ok, after playing around and experiencing this for a bit, I think this is how it's going to have to work in order for me to manage my time effectively and not go insane in the process. I'm going to continue to review my GH notifications at the normal rate, but if there's a GCI one then either a) I'll see the email notification on my (it syncs ~4-6 hours), or someone will have to message me in here to get me to review. 12/1/2017, 11:52:54 AM - agnivade (Agniva De Sarker): sure, I can ping you. 12/1/2017, 3:01:34 PM - sbrl (Starbeamrainbowlabs): Thanks, @agnivade 😃 I've just been overwhelmed recently with the volume of notifications from tldr-pages - that hacker news thing hasn't helped the situation lol 😛 12/1/2017, 3:02:47 PM - agnivade (Agniva De Sarker): totally. me too. 12/1/2017, 3:03:41 PM - sbrl (Starbeamrainbowlabs): starting another sweep now. 12/1/2017, 3:17:03 PM - sbrl (Starbeamrainbowlabs): done 12/1/2017, 3:17:22 PM - sbrl (Starbeamrainbowlabs): looks like your attention is required in #1703 when you have time, @agnivade 12/1/2017, 5:31:54 PM - felixonmars (Felix Yan): FYI: Arch users can install the python client with `pacman -S tldr` https://www.archlinux.org/packages/community/any/tldr/ 12/1/2017, 10:39:14 PM - jayvdb (John Vandenberg): A tldr-pages task has been submitted just now for g++ 12/1/2017, 10:42:11 PM - agnivade (Agniva De Sarker): the pr was already reviewed and merged. But the task instance was not available due to some parental permissions issues. 12/1/2017, 10:42:15 PM - agnivade (Agniva De Sarker): I have accepted the task now 12/2/2017, 1:10:28 AM - sbrl (Starbeamrainbowlabs): @jayvdb Unfortunately, we already have a page for g++. 12/2/2017, 1:10:43 AM - sbrl (Starbeamrainbowlabs): Ref: https://github.com/tldr-pages/tldr/blob/master/pages/common/g++.md 12/2/2017, 1:13:09 AM - sbrl (Starbeamrainbowlabs): Reviewed GCI PR #1730 12/2/2017, 5:42:14 AM - jayvdb (John Vandenberg): btw, you can ask students to amend their comments, instead of having multiple commits. Up to you 12/2/2017, 5:42:50 AM - jayvdb (John Vandenberg): for coala repos, it is mandatory that they squash their commits, so they will all have learnt that before coming to tldr 12/2/2017, 7:09:19 AM - jayvdb (John Vandenberg): @sbrl , please dont fix students PRs. They need to do the work 12/2/2017, 7:10:33 AM - jayvdb (John Vandenberg): and please always click a button on the GCI tasks. https://codein.withgoogle.com/dashboard/task-instances/4633085364666368/ is 7 hours without a button being clicked 12/2/2017, 9:07:51 AM - jayvdb (John Vandenberg): I've approved it 12/2/2017, 9:33:55 AM - agnivade (Agniva De Sarker): > btw, you can ask students to amend their comments, instead of having multiple commits. 12/2/2017, 9:34:39 AM - agnivade (Agniva De Sarker): we always prefer to have multiple commits 12/2/2017, 9:34:55 AM - agnivade (Agniva De Sarker): that way it is easy to review what has changed in a review 12/2/2017, 9:35:12 AM - agnivade (Agniva De Sarker): while merging the PR, we finally squash all the commits. 12/2/2017, 9:44:00 AM - agnivade (Agniva De Sarker): > https://codein.withgoogle.com/dashboard/task-instances/4633085364666368/ is 7 hours without a button being clicked 12/2/2017, 9:44:26 AM - agnivade (Agniva De Sarker): I have to go to sleep sometime. So there can be 7-8 hours of gap when a button does not get clicked. I have tried to remain awake as late as possible. But beyond a certain limit, I don't think I can do more. 12/2/2017, 9:58:24 AM - agnivade (Agniva De Sarker): In hindsight, I think I should not have committed to being a mentor. The requirement to update GCI tasks ASAP is taking too much of my time. I apologize for any inconveniences, but is it possible to revoke my participation from GCI ? 12/2/2017, 11:09:30 AM - jayvdb (John Vandenberg): delays are ok if you're offline, sleeping especially. You had time to answer in gci, you just needed to also click the button 12/2/2017, 11:09:48 AM - jayvdb (John Vandenberg): Im sure you'll get used to it 12/2/2017, 11:10:10 AM - jayvdb (John Vandenberg): It is a tiny bit of extra processing 12/2/2017, 11:12:10 AM - jayvdb (John Vandenberg): And the reward is the project will very likely find a student who wants to put in the effort to become a project maintainer 12/2/2017, 11:35:35 AM - agnivade (Agniva De Sarker): Actually I didn't have time to answer. It was out of the commitment I made to be a mentor and respond to tasks. I couldn't foresee that it would be so difficult. Thanks for understanding. 12/2/2017, 3:29:26 PM - sbrl (Starbeamrainbowlabs): @jayvdb I'm only following the standard practice taught to me by @agnivade and @waldyrious. If you didn't want me editing student PRs for trivial changes, then I'd appreciate prior notice. I'll always follow the standard tldr-pages practice unless explicitly asked otherwise. 12/2/2017, 3:30:38 PM - sbrl (Starbeamrainbowlabs): And I had no idea which button to click, so I left it. "More work needed" did not appear to be the correct response as I didn't want the student to do more work. I was waiting for @agnivade to approve, so surly that means that I should _not_ have clicked a button? 12/2/2017, 3:32:25 PM - sbrl (Starbeamrainbowlabs): Unfortunately due to the fact that I have high-functioning ASD, I tend to take things very literally. Thank you for understanding. 12/2/2017, 3:44:16 PM - sbrl (Starbeamrainbowlabs): (Ref https://github.com/tldr-pages/tldr/issues/1209#issuecomment-298532051) 12/2/2017, 4:15:46 PM - jayvdb (John Vandenberg): @sbrl, hiya, I just got home. wrt editing students work, sorry for not mentioning that before hand. We are in week 1, and all learning in our first GCI. My apologies, and hopefully this can be accommodated in future with students PRs. They learn more if they have to do the final polishing touches themselves. 12/2/2017, 4:18:06 PM - sbrl (Starbeamrainbowlabs): ok :-) I don't understand `wrt` though. `hopefully this can be accommodated` -> hopefully what? Sorry for being dense 😛 12/2/2017, 4:18:23 PM - jayvdb (John Vandenberg): wrt = with regards to 12/2/2017, 4:19:03 PM - sbrl (Starbeamrainbowlabs): Ah 12/2/2017, 4:19:20 PM - jayvdb (John Vandenberg): hopefully tldr can adjust the way the GCI PRs are handled so that the students are given review comments until the end, rather than mentors amending their PRs 12/2/2017, 4:20:50 PM - jayvdb (John Vandenberg): As requested, I am removing Agniva from the mentoring role on the remaining published tldr tasks. 12/2/2017, 4:29:44 PM - jayvdb (John Vandenberg): The other aspect where tldr workflows are conflicting with GCI a little is a reluctance to merge until two mentors have reviewed the PR and have explicitly noted their approval. That is a more fundamental aspect of tldr it seems, and not something to be 'fixed'. I can only change one thing: We can advise the students of the process, that there are signoffs needed from both sides of the globe, which means that even a 'perfect' PR wont be merge straight away. I am still sure that students will take up tldr tasks, even with that warning, but they will know in advance that they should do something else while they wait, and then we are also not obligated to make response times on par with the rest of the coala group 12/2/2017, 4:55:37 PM - sbrl (Starbeamrainbowlabs): Right. Re amending PRs - sure, I can do that. If I notice it's a GCI PR, then I try not to. Re 2 mentors - ping @waldyrious. I think the best solution here will be to alter the task descriptions. 12/2/2017, 6:13:52 PM - agnivade (Agniva De Sarker): > The other aspect where tldr workflows are conflicting with GCI a little is a reluctance to merge until two mentors have reviewed the PR and have explicitly noted their approval. It's part of our process. It is not in our intention to be reluctant. 😛 12/2/2017, 6:14:43 PM - agnivade (Agniva De Sarker): We can alter the task descriptions to be extra clear on that. 12/2/2017, 6:47:07 PM - jayvdb (John Vandenberg): yup; if the students are forewarned, especially if we can explain why, then they go into it with open eyes. We can still push them to do the tldr tasks; I was thinking of making it a pre-req for some of our other tasks. It is good for them to also experience 'slower' projects, if they are forewarned they can better understand why it is a bit slower, and use the time to poke around under the covers of the project. 12/2/2017, 6:53:36 PM - agnivade (Agniva De Sarker): sounds good to me. I will move back to my normal pace and still review github PRs normally. But I won't be logging in to the GCI dashboard. 12/2/2017, 8:10:03 PM - sbrl (Starbeamrainbowlabs): Sounds good to me! Looks like there's a valuable experience to be had on both sides of the table 12/2/2017, 8:14:02 PM - jayvdb (John Vandenberg): absolutely. 12/4/2017, 1:57:09 PM - waldyrious (Waldir Pimenta): Hi everyone. I'm sorry I haven't been able to help out with the extra burden. Actually two or three times I went to update a GCI task myself, one of the others happened to do it minutes before. Which makes sense since our time zones do overlap quite a bit 12/4/2017, 1:57:44 PM - waldyrious (Waldir Pimenta): As for the 2-maintainer review, how about we ping each other here on gitter as soon as the extra approval is the only thing needed? 12/4/2017, 1:58:43 PM - waldyrious (Waldir Pimenta): We can furthermore agree to a reasonable period (say, 6 hours?) after which GCI PRs will get merged even with a single maintainer's approval. It seems like a sensible compromise given the circumstances 12/4/2017, 1:58:52 PM - waldyrious (Waldir Pimenta): What do you guys think? 12/4/2017, 6:05:14 PM - agnivade (Agniva De Sarker): I still think we should uphold the 2-maintainer approval rule. 12/4/2017, 6:12:09 PM - sbrl (Starbeamrainbowlabs): Agreed. 12/4/2017, 6:55:11 PM - waldyrious (Waldir Pimenta): Ok then. Let's make sure to ping each other here as soon as another maintainer's attention is required (IIUC we were already doing that, but just making sure) 12/4/2017, 6:58:13 PM - waldyrious (Waldir Pimenta): Also, it looks like each student can only have one GCI task in progress (I don't know if you were aware of this -- I wasn't until recently). So any delay on our part would be holding them back not only on the tldr task but on other GCI tasks as well. 12/4/2017, 7:25:35 PM - sbrl (Starbeamrainbowlabs): Ah, hrm - that's interesting. I thought that for sure you'd be able to do more than one at once. 12/4/2017, 7:25:55 PM - sbrl (Starbeamrainbowlabs): Sure, I'll mention on here as soon as I've reviewed a GCI PR. 12/4/2017, 8:06:45 PM - waldyrious (Waldir Pimenta): :+1: 12/4/2017, 8:25:18 PM - sbrl (Starbeamrainbowlabs): @waldyrious What do you think about #1744? 12/4/2017, 8:56:41 PM - waldyrious (Waldir Pimenta): @sbrl interesting one. I left a comment, please take a look : ) 12/4/2017, 8:58:59 PM - sbrl (Starbeamrainbowlabs): I thought you'd find it interesting! On a side note, I'm at the tail-end of a module at university that has taught me _GNU flex_ and _GNU bison_ - the successors to _lex_ and _yacc_ that are used for the tldr linter. 12/4/2017, 8:59:34 PM - sbrl (Starbeamrainbowlabs): To that end if we reach an consensus on a new page format, I'd be happy to look at refactoring the linter. 12/4/2017, 9:01:00 PM - sbrl (Starbeamrainbowlabs): Initial impressions: The lexer is rather messy and difficult to udnerstand 12/4/2017, 9:01:06 PM - waldyrious (Waldir Pimenta): sounds great! In the meantime, if you find the time (and interest) to figure out and document the current code a bit, it could help swifter fixing and general improvements by others who arent' familiar with those tools : ) 12/4/2017, 9:01:14 PM - waldyrious (Waldir Pimenta): ah, I see you were one step ahead of me 😛 12/4/2017, 9:04:54 PM - sbrl (Starbeamrainbowlabs): I'll take a look at that! Why is there a second parser in `lib` when one has already been defined in `tldr.yy`? 12/4/2017, 9:05:55 PM - waldyrious (Waldir Pimenta): Such mysteries are beyond my comprehension 😛 perhaps @agnivade can help, and most certainly @rubenvereecken will 12/4/2017, 9:08:15 PM - sbrl (Starbeamrainbowlabs): There's some seriously heavy stuff going on in there, though 12/4/2017, 9:09:55 PM - sbrl (Starbeamrainbowlabs): Looks like it's not flex/bison, but jison instead 12/4/2017, 9:17:35 PM - sbrl (Starbeamrainbowlabs): The file name extensions are deceptive 12/4/2017, 9:21:38 PM - sbrl (Starbeamrainbowlabs): tbh it's documented fairly well already - it's jujst that you can't just insert a comment _anywhere_, as will be intpreted as part of the grammar 12/4/2017, 9:21:47 PM - waldyrious (Waldir Pimenta): Is there a different extension for jison files? 12/4/2017, 9:23:19 PM - waldyrious (Waldir Pimenta): As for documentation, perhaps adding some quick pointers in the README to would-be contributors (e.g. relevant entry points, required background knowledge, etc.) would help, then? 12/4/2017, 9:27:18 PM - sbrl (Starbeamrainbowlabs): Yeah, apparently it's `.jison` and `.jisonlex` 12/4/2017, 9:35:25 PM - waldyrious (Waldir Pimenta): maybe send a PR 😃 12/5/2017, 12:07:27 AM - sbrl (Starbeamrainbowlabs): Not sure if renaming them would break something else 😛 I'll still look at putting together and sending a PR for some additional contributing getting started docs in the README though. 12/5/2017, 12:18:11 AM - waldyrious (Waldir Pimenta): 👌 12/5/2017, 1:05:13 AM - agnivade (Agniva De Sarker): I believe the tldr-parser.js is generated from tldr.yy 12/5/2017, 1:05:20 AM - agnivade (Agniva De Sarker): Though not 100% sure 12/5/2017, 1:05:47 AM - agnivade (Agniva De Sarker): I just dabbled in a few rules a long time ago .. so I'm not super familiar 12/5/2017, 2:39:28 AM - sbrl (Starbeamrainbowlabs): Yeah, that sounds about right @agnivade 12/5/2017, 2:49:48 PM - waldyrious (Waldir Pimenta): hey guys -- there's a GCI task for cppclean, but #1745 was not submitted as part of GCI, was it? 12/5/2017, 5:01:07 PM - jayvdb (John Vandenberg): no, not GCI, so I have unpublished it 12/5/2017, 8:30:13 PM - sbrl (Starbeamrainbowlabs): Looks ok to me, so I'v merged it 12/5/2017, 9:02:59 PM - agnivade (Agniva De Sarker): not GCI. I had removed the GCI tag from the issue. 12/5/2017, 9:13:09 PM - waldyrious (Waldir Pimenta): got it, thanks all for the clarifications and tying up the loose ends : ) 12/13/2017, 4:43:20 PM - sbrl (Starbeamrainbowlabs): The `dep` command has been claimed through GCI 12/13/2017, 4:44:26 PM - sbrl (Starbeamrainbowlabs): We've also got a PR for it 12/13/2017, 4:44:38 PM - sbrl (Starbeamrainbowlabs): I'm not sure if they're by the same person? 12/13/2017, 4:44:44 PM - sbrl (Starbeamrainbowlabs): Ping @waldyrious / @agnivade 12/13/2017, 4:47:05 PM - sbrl (Starbeamrainbowlabs): I've treated it as such 12/13/2017, 4:51:19 PM - waldyrious (Waldir Pimenta): it clearly is the same person (the student's name matches their username). Was there any info that led you to believe otherwise, @sbrl? 12/13/2017, 5:00:30 PM - waldyrious (Waldir Pimenta): There were no restrictions on who was supposed to update the task page with the link to the PR, right? 12/13/2017, 5:00:36 PM - sbrl (Starbeamrainbowlabs): Hrm, they do? Ah, right! I must have read them incorrectly 😛 12/13/2017, 5:00:54 PM - waldyrious (Waldir Pimenta): Please check again and let me know : ) 12/13/2017, 5:01:04 PM - sbrl (Starbeamrainbowlabs): I thought it was the student who commented to ask for review 12/13/2017, 5:01:18 PM - waldyrious (Waldir Pimenta): I don't follow. 12/13/2017, 5:01:58 PM - sbrl (Starbeamrainbowlabs): Neither do I - I think I just got confused 12/13/2017, 5:02:20 PM - waldyrious (Waldir Pimenta): lol ok 😛 12/13/2017, 5:02:31 PM - waldyrious (Waldir Pimenta): Btw I left some comments on the PR, PTAL 12/13/2017, 5:02:42 PM - sbrl (Starbeamrainbowlabs): Thanks! 12/13/2017, 5:02:46 PM - sbrl (Starbeamrainbowlabs): (and PTAL? not sure I know that one) 12/13/2017, 5:03:19 PM - waldyrious (Waldir Pimenta): I thought you were the one who asked about that acronym once, maybe I'm mixing people up : ) it means "please take a look" 12/13/2017, 5:48:09 PM - agnivade (Agniva De Sarker): It was me 😛 12/13/2017, 5:51:20 PM - sbrl (Starbeamrainbowlabs): Ahhh ok, thanks! 12/13/2017, 5:51:48 PM - waldyrious (Waldir Pimenta): xD 12/14/2017, 10:02:14 AM - jayvdb (John Vandenberg): https://github.com/tldr-pages/tldr/pull/1796 was merged; could someone click approve on https://codein.withgoogle.com/dashboard/task-instances/5102697852174336/ 12/14/2017, 10:02:27 AM - jayvdb (John Vandenberg): otherwise i'll do it shortly, no drama 12/14/2017, 10:12:23 AM - jayvdb (John Vandenberg): I've clicked accept 12/14/2017, 2:55:41 PM - sbrl (Starbeamrainbowlabs): Morning! 12/14/2017, 2:55:45 PM - sbrl (Starbeamrainbowlabs): :+1: 12/14/2017, 2:56:29 PM - waldyrious (Waldir Pimenta): Just arrived as well 👋 12/16/2017, 11:22:00 PM - waldyrious (Waldir Pimenta): @sbrl I need you to help me make an experiment 12/16/2017, 11:22:44 PM - waldyrious (Waldir Pimenta): can you add new members to the tldr organization? Do you see any option to do that here? https://github.com/orgs/tldr-pages/people 12/16/2017, 11:47:55 PM - sbrl (Starbeamrainbowlabs): Hey! Sure :-) Nope, I can't currently see an option to add people on that page. 12/18/2017, 3:39:19 PM - waldyrious (Waldir Pimenta): Cool, thanks. I am fleshing out a proposal for the governance guidelines of the tldr org. I'm aiming at something between StackOverflow's automatic karma-based permissions system and Wikipedia's admin election process. 12/18/2017, 3:39:27 PM - waldyrious (Waldir Pimenta): I will probably publish a proposal sometime this week :) 12/18/2017, 3:40:27 PM - waldyrious (Waldir Pimenta): one of the ideas being that the community can self-manage without top-down management (e.g. a handful of people deciding who to add or not to the org) 12/18/2017, 3:42:45 PM - waldyrious (Waldir Pimenta): which is both good for transparency and democracy, since the guidelines will be explicit rather than only in the heads of the maintainers, but also will improve long-term resilience of the project, since there will be less reliance on a few people's availability for making decisions and implementing them 12/18/2017, 3:47:27 PM - sbrl (Starbeamrainbowlabs): Sounds good to me! 12/19/2017, 9:26:46 AM - agnivade (Agniva De Sarker): Great. I have another concern though, what about members who have been added but now have gone inactive ? Should there be any process that revokes their membership ? 12/19/2017, 5:23:20 PM - sbrl (Starbeamrainbowlabs): Oooh, good point, @agnivade 12/19/2017, 5:23:28 PM - sbrl (Starbeamrainbowlabs): I'm not sure. 12/19/2017, 11:22:50 PM - waldyrious (Waldir Pimenta): @agnivade @sbrl I thought about that too. In my experience a sensible guideline would be similar to Wikipedia's: http://enwp.org/WP:INACTIVITY 12/19/2017, 11:27:06 PM - sbrl (Starbeamrainbowlabs): Yeah, sounds good to me 12/19/2017, 11:27:28 PM - sbrl (Starbeamrainbowlabs): though I'm not sure how to represent former maintainers on GH 12/19/2017, 11:29:53 PM - waldyrious (Waldir Pimenta): you mean, to recognize past contributions? That's a good point. I guess we could use a maintainers.md file with two sections. 12/19/2017, 11:34:57 PM - sbrl (Starbeamrainbowlabs): Yeah, that would work I think. It would be awesome if GH allowed us to have custom things next to people's name (e.g. more than just `owner`, `member`, and `contributor` etc.) 12/19/2017, 11:35:55 PM - waldyrious (Waldir Pimenta): it might get there eventually : ) they were recently hiring for a maintainer-focused role, so they hopefully will be paying more attention to these needs 12/19/2017, 11:36:57 PM - sbrl (Starbeamrainbowlabs): cool! 12/20/2017, 12:10:58 AM - jayvdb (John Vandenberg): or create a team for them ? 12/20/2017, 12:11:52 AM - jayvdb (John Vandenberg): (we have the same unsolved problem in coala ; we think about it occasionally, but never bother to pull the pin on the inactive maintainers) 12/20/2017, 12:12:47 AM - waldyrious (Waldir Pimenta): teams would complicate things here. There are already multiple levels of permissions, between repo-specific collaborators, org members and org owners. Adding teams to the mix would make the system even more complex 12/20/2017, 12:13:41 AM - waldyrious (Waldir Pimenta): My plan was to define a very forgiving, procedural-only guidelines for removing maintainer status, whereas as soon as the user is active again on the project, they'd automatically be granted the status back 12/20/2017, 12:14:39 AM - waldyrious (Waldir Pimenta): (still on the teams topic, github now supports multiple levels of sub-teams, with nested permissions, plus external collaborators... it's a mess at the moment, IMO) 12/20/2017, 6:24:35 AM - jayvdb (John Vandenberg): A team can have almost zero rights 12/20/2017, 6:25:12 AM - jayvdb (John Vandenberg): E.g. coalas 'newcomers' team 12/20/2017, 6:25:53 AM - jayvdb (John Vandenberg): 'Read' access only 12/20/2017, 2:09:28 PM - waldyrious (Waldir Pimenta): I know, what concerns me is that it is yet another orthogonal axis of permissions / access 12/20/2017, 2:10:17 PM - waldyrious (Waldir Pimenta): between members vs. owners vs. team members vs. external collaborators vs. repo-specific collaborators... the whole system becomes too complex 12/20/2017, 3:24:11 PM - jayvdb (John Vandenberg): nod. 12/27/2017, 9:01:38 AM - agnivade (Agniva De Sarker): I am back after a short trip. Catching up on stuff. 12/27/2017, 2:45:34 PM - waldyrious (Waldir Pimenta): Right on time! I just submitted #1839 last night 😃 12/27/2017, 2:46:08 PM - waldyrious (Waldir Pimenta): @jayvdb, @sils, I'd appreciate your input as well : ) 12/27/2017, 3:35:36 PM - sbrl (Starbeamrainbowlabs): Hope everyone had a relaxing and peaceful Christmas :-) 12/27/2017, 3:44:46 PM - jayvdb (John Vandenberg): The students didnt relax, so I didnt either! I wont be available on NYE tho! :) 12/27/2017, 3:49:09 PM - sbrl (Starbeamrainbowlabs): We haven't had any more GCI PRs that I can tell. They sure must be hard at work elsewhere though! 12/27/2017, 6:58:57 PM - jayvdb (John Vandenberg): added a few comments on https://github.com/tldr-pages/tldr/issues/1839 12/27/2017, 7:00:02 PM - jayvdb (John Vandenberg): another idea I've had due to other projects I've been involved in is a project maintenance sabbatical 12/27/2017, 7:00:39 PM - jayvdb (John Vandenberg): often a core contributor gets very sidetracked on building a component that is in a different org 12/27/2017, 7:02:58 PM - jayvdb (John Vandenberg): if their 'sidetracked component' is being built because of an identified need within the primary org, they are effectively on a sabbatical. there is definitely no need to formally include this in the governance, as it already allows for resumption when activity resumes, and that is a neat and very common solution. 12/27/2017, 7:04:25 PM - jayvdb (John Vandenberg): but maybe there is something to the concept, so I am just throwing it out there ... 😉 12/27/2017, 7:20:29 PM - waldyrious (Waldir Pimenta): I think it's best to make it as clear as possible that, as a volunteer project which is part of a wider ecosystem of volunteer, passion-fueled projects, people are expected to work on whatever they feel like, whether it somehow relates to the tldr project or not, and the status within the org will be updated simply to reflect the ground truth. 12/27/2017, 7:22:11 PM - waldyrious (Waldir Pimenta): If they're not maintaining the tldr project anymore, for whatever reason, that's perfectly fine. IMO it helps no one to open exceptions that effectively allow us to say that someone is maintaining the project, when they aren't. 12/27/2017, 7:22:56 PM - sbrl (Starbeamrainbowlabs): :+1: 12/27/2017, 7:22:59 PM - waldyrious (Waldir Pimenta): In fact, I fear that it would only complicate things (for everyone, really) to add exceptions aimed at keeping them in the list of maintainers in case their absence is "justified". Not to mention that such a rule would then give the impression that unrelated absences are not justified (or that contributors owe the project any justification at all). 12/27/2017, 7:23:41 PM - waldyrious (Waldir Pimenta): (I said something along these lines in my reply to your review comment in the PR, too -- please take a look when you get the chance) 12/27/2017, 8:53:26 PM - agnivade (Agniva De Sarker): agree with @waldyrious to keep the rules simple. Being an org member should not be viewed as a position of power or influence, but just as a measure of repo activity. If anyone takes a sabbatical, remove the person. And when he/she is back, add the person. Simple and easy. 1/14/2023, 3:14:37 PM - jsonbruce (Max Xu) joined the room 12/27/2017, 8:58:03 PM - jsonbruce (Max Xu): 👍 1/10/2018, 5:42:48 AM - waldyrious (Waldir Pimenta): In case anyone missed it, #1839 is now merged, which means we now have an official governance policy! 🎉 1/10/2018, 5:43:32 AM - waldyrious (Waldir Pimenta): As a follow-up, I opened #1878 to apply them to the current list of contributors. Comments welcome! 1/10/2018, 7:52:56 PM - sils (Lasse Schuirmann): 🎉 1/13/2018, 10:46:57 PM - pepa65 (pepa65): Another way of managing the transition from old to new syntax sensibly would be to convert all the old pages to new pages that are stored at a new location. Old clients keep working (but don't get new pages or updates), and clients that can handle the new syntax can transition to the new pages. 1/13/2018, 10:47:51 PM - pepa65 (pepa65): It is important to not cause users to be annoyed by breaking the tools that are working for them. 1/13/2018, 10:48:36 PM - agnivade (Agniva De Sarker): But still the fact remains that users will have to update their clients first. 1/13/2018, 10:48:51 PM - agnivade (Agniva De Sarker): How long will you wait till you are sure all users have updated their clients ? 1/13/2018, 10:49:03 PM - agnivade (Agniva De Sarker): Some users _will_ get affected. 1/13/2018, 10:49:12 PM - agnivade (Agniva De Sarker): There's just no way we can do this safely. 1/13/2018, 10:50:40 PM - sbrl (Starbeamrainbowlabs): I guess all we can do it plan to minimise the number of users we affect, and then once we've done all we can in that department, we go ahead with the syntax change. 1/13/2018, 10:51:43 PM - agnivade (Agniva De Sarker): right. 1/14/2023, 3:14:42 PM - owenvoke (Owen Voke) joined the room 1/13/2018, 10:56:46 PM - owenvoke (Owen Voke): :+1: 1/13/2018, 11:18:35 PM - pepa65 (pepa65): If you keep the old pages around, old clients keep working. 1/14/2018, 9:44:51 AM - agnivade (Agniva De Sarker): Ah you meant to say store the new pages in an entirely new location and look for that location only from new clients. Got it 1/14/2018, 9:46:34 AM - agnivade (Agniva De Sarker): That might also work. 1/14/2018, 2:55:33 PM - sbrl (Starbeamrainbowlabs): :+1: 1/14/2023, 3:14:45 PM - dbrgn (Danilo Bargen) joined the room 1/14/2018, 4:41:44 PM - dbrgn (Danilo Bargen): We could also move the new (converted) pages to a new path/directory/repository and inject an upgrade warning header into all "old format" pages. It's just markdown after all. 1/14/2018, 4:42:01 PM - dbrgn (Danilo Bargen): Then give a deadline (e.g. 1 year from the initial warnings) until the old files are removed. 1/14/2018, 4:43:57 PM - dbrgn (Danilo Bargen): In any case, I think the argument that people will just stop using tldr if it doesn't work anymore should not mean that that we should not do any changes. People should use clients that they can easily (and ideally automatically) update. After all, it's a piece of software that pulls untrusted data from the internet and parses it. That's something that can have security implications. Using a program that was npm installed 3 years ago and never updating it is not good security practice. 1/14/2018, 10:37:42 PM - agnivade (Agniva De Sarker): @pxgamer / @jsonbruce - feel free to review the PRs .. sometimes, we miss a few things. 1/14/2018, 10:37:50 PM - agnivade (Agniva De Sarker): So an extra pair of eyes always help :) 1/15/2018, 2:44:33 PM - waldyrious (Waldir Pimenta): @pepa65's idea could actually provide a nice way to tackle #190 :) 1/15/2018, 2:44:45 PM - waldyrious (Waldir Pimenta): although that may complicate things for clients even further... 1/15/2018, 2:54:03 PM - dbrgn (Danilo Bargen): @waldyrious I agree, new structure and new syntax could be done at the same time. 1/15/2018, 2:54:35 PM - dbrgn (Danilo Bargen): main downside would be to ask all clients that have already implemented the new syntax to do a breaking change *again* 😕 1/15/2018, 2:54:42 PM - waldyrious (Waldir Pimenta): exactly my worry 1/15/2018, 2:54:59 PM - waldyrious (Waldir Pimenta): maybe we should simply do one after the other since the work is indeed separable 1/15/2018, 2:55:24 PM - waldyrious (Waldir Pimenta): that way we don't hold any of these changes because of the other one 1/15/2018, 2:55:54 PM - waldyrious (Waldir Pimenta): as a client author, do you have thoughts on what would be preferable regarding #190? 1/15/2018, 2:56:32 PM - dbrgn (Danilo Bargen): it depends. if we want to avoid further work for the new clients, then we'd have to convert the *existing* pages to the new format. if we move them to a new URL, a change is required anyways, in that case we could just as well include the directory structure change. 1/15/2018, 2:57:14 PM - dbrgn (Danilo Bargen): I like #190 but I'm not sure if it's really much easier. In both cases, you have to do a file-exists operation on the specific page, then on the generic page. 1/15/2018, 2:57:41 PM - waldyrious (Waldir Pimenta): I'd like to know how many of the clients rely on the actual repo structure, and which ones use the index.json and archive.zip from the webpage repo 1/15/2018, 2:58:40 PM - waldyrious (Waldir Pimenta): if most of them use the latter strategy, we could change the repo and simply start producing updates on a new location, which for clients supporting the new syntax would mean simply using a different URL for fetching the pages. Is this correct? 1/15/2018, 2:59:12 PM - dbrgn (Danilo Bargen): there's an `index.json`? where? 1/15/2018, 2:59:38 PM - waldyrious (Waldir Pimenta): https://github.com/tldr-pages/tldr-pages.github.io/tree/master/assets 1/15/2018, 2:59:49 PM - waldyrious (Waldir Pimenta): I think we were planning to deprecate that, though 1/15/2018, 3:00:56 PM - dbrgn (Danilo Bargen): ah. it does not really make things easier though, since even after checking index.json you still need to check whether the file actually exists in the cache/download. 1/15/2018, 3:01:20 PM - dbrgn (Danilo Bargen): it's another indirection layer that makes changes to the strucure easier, but I'm not sure how much the advantages are. especially since it needs to be kept up to date. 1/15/2018, 3:02:09 PM - waldyrious (Waldir Pimenta): I was thinking that we could rely on that to avoid keeping both the old and the new syntax in the repo simultaneously 1/15/2018, 3:02:34 PM - waldyrious (Waldir Pimenta): i.e. we'd have two archives, but the canonical data would be only in the new syntax 1/14/2023, 3:14:55 PM - psibi (Sibi Prabakaran) joined the room 1/15/2018, 3:55:31 PM - psibi (Sibi Prabakaran): Never knew about `index.json` actually. My Haskell client depends on the git repo structure actually. I think creating a new directory for the new syntax would be much easier. That way, the existing client can work without breaking and new the newer version can only decide to support newer syntax. 1/15/2018, 4:01:05 PM - dbrgn (Danilo Bargen): Agree. After a few clients are stable with the new version, we could inject upgrade notices into all the old TLDR pages. 1/16/2018, 5:42:26 AM - waldyrious (Waldir Pimenta): Hi all, just an update about the maintainers' guide (#1209): I've got the bulk of the document in place and it only needs some editing to fix organization issues and some repetition. I expect to have the final proposal ready before the end of the week. Hopefully in one or two days. 1/16/2018, 2:35:44 PM - owenvoke (Owen Voke): I have a quick question, when merging PRs, do we Squash and Merge? 1/16/2018, 2:53:20 PM - waldyrious (Waldir Pimenta): @pxgamer that's actually already covered in the current text of the maintainer's guide :) https://github.com/tldr-pages/tldr/blob/master/contributing-guides/maintainers-guide.md 1/16/2018, 2:53:29 PM - waldyrious (Waldir Pimenta): basically you'd either squash or rebase 1/16/2018, 2:54:09 PM - owenvoke (Owen Voke): Apologies, I'm not sure how I missed that. 1/16/2018, 2:54:15 PM - owenvoke (Owen Voke): Cheers. :+1: 1/16/2018, 2:54:26 PM - waldyrious (Waldir Pimenta): no problem :) perhaps it should be better structured, bolded or something 1/16/2018, 2:54:45 PM - waldyrious (Waldir Pimenta): in any case, let me know if anything in the text there isn't clear so that I can incorporate changes in the upcoming extension 1/16/2018, 2:54:58 PM - owenvoke (Owen Voke): Ok 😄 1/14/2023, 3:15:01 PM - zhujian0805 (Jian Zhu) joined the room 1/17/2018, 10:55:35 AM - zhujian0805 (Jian Zhu): Is there a 'search' or list function for tldr? 1/17/2018, 10:56:14 AM - zhujian0805 (Jian Zhu): list all available commands and search for specific string, not just command itself. 1/17/2018, 12:50:58 PM - agnivade (Agniva De Sarker): If you use the node client, then yes. `tldr --list` and `tldr --search ` 1/17/2018, 2:34:17 PM - jsonbruce (Max Xu): :+1: 1/17/2018, 6:08:56 PM - owenvoke (Owen Voke): Are markdown links supported in pages? e.g. for the page descriptions. 1/17/2018, 7:09:22 PM - waldyrious (Waldir Pimenta): They aren't forbidden, but most clients won't provide a rich rendering anyway (I don't think most shells even support that) so it's probably better to just use raw URLs 1/17/2018, 7:33:28 PM - owenvoke (Owen Voke): Ah, ok. Should one be changed like in the case of #1898? 1/17/2018, 7:51:30 PM - waldyrious (Waldir Pimenta): I see. That one is actually something that should be relevant to all pages. This kind of metadata fields has been raised in a few issues in the past, and is tracked in #1082. 1/17/2018, 7:52:07 PM - waldyrious (Waldir Pimenta): So until we can support that properly, I'd suggest not using such URLs in the pages themselves. Please do include it in the commit message, though, when merging that PR 1/17/2018, 7:57:22 PM - owenvoke (Owen Voke): Ok :+1: 1/18/2018, 6:56:22 PM - waldyrious (Waldir Pimenta): Phew! made a bunch of changes to implement the missing role transition changes. tldr-pages is getting closer to become a self-managing community 😃 See details at https://github.com/tldr-pages/tldr/issues/1878#issuecomment-358610454. 1/19/2018, 4:21:33 AM - sbrl (Starbeamrainbowlabs): Google Code-In has ended! 1/19/2018, 4:22:01 AM - sbrl (Starbeamrainbowlabs): Apparently we have to choose winners as an organisation. 1/19/2018, 4:36:31 AM - owenvoke (Owen Voke): What is it? 1/19/2018, 4:37:36 AM - sbrl (Starbeamrainbowlabs): It's a competition for 13-17 year-olds to get involved in open source. Check out their about page: https://codein.withgoogle.com/about/ We took part as a sub-organisation. 1/19/2018, 4:37:48 AM - sbrl (Starbeamrainbowlabs): That's what all the issues tagged with `GCI` pare 1/19/2018, 4:39:00 AM - owenvoke (Owen Voke): Sounds good. 1/19/2018, 4:39:25 AM - sbrl (Starbeamrainbowlabs): Yeah! 1/19/2018, 4:40:31 AM - owenvoke (Owen Voke): How long has that been around for? 1/19/2018, 4:40:56 AM - owenvoke (Owen Voke): Didn't mean to send that. I read the page. :+1: 1/19/2018, 4:42:44 AM - sbrl (Starbeamrainbowlabs): Erm I think it start back in ~november time? It's been running for a few years, but as an organisation I think this year was the first one that we participated in 1/19/2018, 4:42:53 AM - sbrl (Starbeamrainbowlabs): Ah, ok 😛 1/19/2018, 4:45:02 AM - owenvoke (Owen Voke): Wish I'd known about it a couple of years ago. Would have been interesting to do. 1/19/2018, 4:49:29 AM - sbrl (Starbeamrainbowlabs): Yeah! I discovered it a few years ago too, but I didn't have the confidence to enter. I wish I did 😕 1/19/2018, 9:24:03 AM - agnivade (Agniva De Sarker): great work @waldyrious ! Good to have these things documented ! 1/19/2018, 10:34:24 AM - agnivade (Agniva De Sarker): Btw - updated all the gci labels to help wanted. 1/19/2018, 1:20:57 PM - owenvoke (Owen Voke): :+1: I think Grunt (one of the gci ones) would be a useful page to have. Might look into making a page for it. 1/19/2018, 3:40:46 PM - waldyrious (Waldir Pimenta): Are we as a sub-org also expected to pick winners? I thought that would be only the top-level orgs. @jayvdb can you confirm? 1/19/2018, 3:46:12 PM - owenvoke (Owen Voke): Interested for #1908 which I've just opened. It has 12 detailed commands so I was going to seperate it into multiple files, such as `reg-add`, `reg-query`, etc. Is this the right way of going about this? 1/19/2018, 3:50:30 PM - waldyrious (Waldir Pimenta): "I was going" --> are you still planning to? 1/19/2018, 3:51:17 PM - waldyrious (Waldir Pimenta): For the record, if they're complex enough on their own, then yeah, it makes sense, as per the precedent of git et al. 1/19/2018, 3:51:21 PM - owenvoke (Owen Voke): Yes, I am planning to. Unless it's the wrong way to do it. 1/19/2018, 3:51:40 PM - waldyrious (Waldir Pimenta): Just making sure. The past tense confused me slightly : ) 1/19/2018, 3:51:44 PM - sbrl (Starbeamrainbowlabs): Sounds like a sensible plan to me, @pxgamer :+1: 1/19/2018, 3:51:56 PM - owenvoke (Owen Voke): And ok :+1: I will create them as seperate pages. 😄 (And sorry for the confusion) 1/19/2018, 4:11:37 PM - jayvdb (John Vandenberg): @waldyrious , there is a discussion ongoing with all mentors , at coala.zulipchat.org 1/19/2018, 4:13:21 PM - jayvdb (John Vandenberg): final decision is made by the admins(Lasse, Mixih & I), but it is based mentors decisions 1/19/2018, 4:15:09 PM - waldyrious (Waldir Pimenta): Ok, thanks for confirming : ) I didn't interact much with the students, so I'll let @sbrl and @agnivade say something if they noticed someone outstanding. 1/19/2018, 4:17:43 PM - sbrl (Starbeamrainbowlabs): I'd say that @andrewda would be my candidate. He really got the hang of it quickly with his 2 PRs he did 1/20/2018, 9:27:33 AM - agnivade (Agniva De Sarker): I would refrain from any comments since I revoked my mentorship. 1/20/2018, 3:27:50 PM - sbrl (Starbeamrainbowlabs): We didn't actually get as many GCI contributors in the end as I was expecting 1/20/2018, 4:02:59 PM - mstruebing (Max Strübing): Quick question: would it be ok to add pages for a weechat(irc client) plugin? I'm using this: https://github.com/wee-slack/wee-slack and often has to go to the github page to see how the syntax to react to a previous message is or something, if things like this is also welcoming I would create a PR 1/20/2018, 4:09:29 PM - sbrl (Starbeamrainbowlabs): You mean for the command-line program? Sure, @mstruebing! I don't think it should clash with anything. If you're talking about the what looks like slash commands inside the program, those would be a better fit for a cheat-sheet. 1/20/2018, 4:12:09 PM - mstruebing (Max Strübing): wee-slack itself isn't a command-line program, it's a plugin for a command-line program and I can use it from within this program, but not on it's own. So if I understand correctly, no need to create a PR for this? :)\ 1/20/2018, 4:14:20 PM - sbrl (Starbeamrainbowlabs): Yeah. tldr-pages is only for command-line programs. I'd recommend creating a cheat sheet though! 1/20/2018, 4:14:46 PM - mstruebing (Max Strübing): thx 1/20/2018, 4:17:02 PM - sbrl (Starbeamrainbowlabs): No problem 😺 1/20/2018, 9:59:09 PM - waldyrious (Waldir Pimenta): @mstruebing I'd be curious to see what such a tldr page would look like 1/20/2018, 9:59:36 PM - waldyrious (Waldir Pimenta): we already have pages for things that aren't exactly command-line tools, e.g. crontab 1/20/2018, 10:00:19 PM - waldyrious (Waldir Pimenta): so in theory it could be possible to make it work 1/20/2018, 10:02:01 PM - waldyrious (Waldir Pimenta): > We didn't actually get as many GCI contributors in the end as I was expecting Yeah, the stream kind of trickled out at some point. But at least now we know how it works and what to expect. We might consider participating again next year, especially now that we'll start expanding the maintenance team more frequently :) 1/20/2018, 10:02:20 PM - sbrl (Starbeamrainbowlabs): Yeah! 1/21/2018, 12:18:04 AM - mstruebing (Max Strübing): Okay, then I can propose an example tomorrow 1/21/2018, 1:18:58 AM - mstruebing (Max Strübing): Just an idea, how about a folder called 'cheatsheet' on this level: https://github.com/tldr-pages/tldr/tree/master/pages I think there are many cases where it would be useful 1/21/2018, 1:28:31 AM - waldyrious (Waldir Pimenta): @mstruebing I'd suggest opening an issue with a concrete plan that people can chime in on, in particular one that addresses other nonstandard pages that have come up before. See [this comment](https://github.com/tldr-pages/tldr/issues/1744#issuecomment-348995255) and the pages/links references there, for some useful background. 1/21/2018, 1:29:35 AM - waldyrious (Waldir Pimenta): But also keep in mind that we don't need to do everything for everyone. In the Unix spirit, it's best to do one thing and do it well, especially when there are alternative projects (listed in our README) that aim to tackle related problems 1/21/2018, 1:33:44 AM - sbrl (Starbeamrainbowlabs): You could even start your own project! 1/21/2018, 1:34:27 AM - waldyrious (Waldir Pimenta): I'd recommend joining forces with an existing one that already does what he envisions, if possible 1/21/2018, 1:41:12 AM - sbrl (Starbeamrainbowlabs): Indeed 1/21/2018, 5:00:50 AM - jayvdb (John Vandenberg): Fyi, public discussion around GCI winners is not allowed until after Google announces them. See rules for the process that must be followed 1/21/2018, 5:04:19 AM - jayvdb (John Vandenberg): There would have been more GCI contributors if there were more mentors. That is something that it sounds like you'll be fixing over the next year. 1/21/2018, 3:42:11 PM - sbrl (Starbeamrainbowlabs): @jayvdb ......I see. I was not aware of this rule, and I don't have any other way of contacting you. Furthermore, we're just a (small) suborg. So does that mean that we don't have a 'winner' per se? 1/21/2018, 5:21:24 PM - jayvdb (John Vandenberg): as mentioned earlier, there is a private chat ongoing at http://coala.zulipchat.com/ , or you can chat privately with me on gitter 1/21/2018, 5:22:52 PM - jayvdb (John Vandenberg): if tldr wants to participate again next year, it is worthwhile to get involved in this final discussion to understand how the program works at the end, as that helps understand how to mentor it throughout 1/21/2018, 5:23:43 PM - jayvdb (John Vandenberg): there is only one set of winners and finalists per org. as a suborg, you participate as mentors, just like the main coala mentors 1/21/2018, 6:10:51 PM - sbrl (Starbeamrainbowlabs): Ah, ok 1/21/2018, 6:11:17 PM - sbrl (Starbeamrainbowlabs): I don't have and don't intend to have a _zulipchat_ account though 1/14/2023, 3:15:25 PM - Leandros (Arvid Gerstmann) joined the room 1/25/2018, 4:08:56 PM - Leandros (Arvid Gerstmann): [![Screen Shot 2018-01-25 at 11.37.51.png](https://files.gitter.im/tldr-pages/tldr/IOMT/thumb/Screen-Shot-2018-01-25-at-11.37.51.png)](https://files.gitter.im/tldr-pages/tldr/IOMT/Screen-Shot-2018-01-25-at-11.37.51.png) 1/25/2018, 4:08:57 PM - Leandros (Arvid Gerstmann): Sure you meant to do that? 1/25/2018, 4:13:17 PM - sbrl (Starbeamrainbowlabs): Certainly not! Which issue is that on, @Leandros? 1/25/2018, 5:36:01 PM - Leandros (Arvid Gerstmann): @sbrl Every issue and pull request on the tldr repo: https://github.com/tldr-pages/tldr 1/25/2018, 5:36:14 PM - Leandros (Arvid Gerstmann): Probably not the best idea to give everyone admin access? 😛 1/25/2018, 5:53:49 PM - waldyrious (Waldir Pimenta): We actually reduced the number of people with admin access with the latest org changes : ) only sbrl was converted from member to owner 1/25/2018, 5:55:34 PM - waldyrious (Waldir Pimenta): Looking at the audit log at https://github.com/organizations/tldr-pages/settings/audit-log, I see this: > agnivade – repo.config > Enabled push access limits to the tldr-pages/tldr repository > 2018-01-25 09:20 UTC 1/25/2018, 5:55:45 PM - waldyrious (Waldir Pimenta): Not sure what that's about, I'll take a look 1/25/2018, 5:58:05 PM - waldyrious (Waldir Pimenta): I see this in https://github.com/tldr-pages/tldr/settings: > ## Temporary interaction limits > > Temporarily restrict which users can interact with your repository (comment, open issues, or create pull requests) for a 24-hour period. This may be used to force a "cool-down" period during heated discussions. > > - [ ] **Limit to existing users** -- Users that have recently created their account will be unable to interact with the repository. > - [ ] **Limit to prior contributors** -- Users that have not previously committed to the repository's master branch will be unable to interact with the repository. > - [x] **Limit to repository collaborators** -- Users that have not been granted push access will be unable to interact with the repository. *(Enabled with about 21 hours remaining)* 1/25/2018, 5:58:54 PM - waldyrious (Waldir Pimenta): Either we had a spam attack and this was to mitigate it, or it was a mistake, or somebody hacked into @agnivade's account 😕 1/25/2018, 5:59:02 PM - waldyrious (Waldir Pimenta): I'll uncheck that option for now. 1/25/2018, 5:59:38 PM - waldyrious (Waldir Pimenta): Thanks for the heads-up, @Leandros : ) 1/25/2018, 6:02:44 PM - owenvoke (Owen Voke): :+1: 1/25/2018, 9:08:25 PM - sbrl (Starbeamrainbowlabs): Ah, so that's what that option does 1/25/2018, 9:09:48 PM - owenvoke (Owen Voke): Just looking at #1937, I take it keyboard shortcuts are fine? The only thing I was going to comment on was the length of the description. 1/25/2018, 9:28:01 PM - waldyrious (Waldir Pimenta): good call, @pxgamer -- actually the shortcuts have been standardized to a specific format; see #1354 and #1356 1/25/2018, 9:28:40 PM - waldyrious (Waldir Pimenta): I'll add a task to my list for describing that in the style guide: https://github.com/tldr-pages/tldr/blob/master/contributing-guides/style-guide.md 1/25/2018, 9:29:06 PM - owenvoke (Owen Voke): Aha, I will add that as a review comment :+1: Cheers. 1/25/2018, 9:30:54 PM - waldyrious (Waldir Pimenta): happy to help : ) 1/26/2018, 10:40:49 AM - agnivade (Agniva De Sarker): Oh so sorry. I misunderstood the thing. I thought I was enabling the _ability_ to be able to limit interacting the repository. Did not want to enable it. My apologies 😭 1/26/2018, 10:41:52 AM - agnivade (Agniva De Sarker): Also I should have notified here after doing that. Somehow it slipped my mind. 1/26/2018, 5:02:14 PM - waldyrious (Waldir Pimenta): No problem, it was resolved quicky : ) thanks for confirming! 1/26/2018, 9:01:04 PM - waldyrious (Waldir Pimenta): @agnivade have you seen this? https://github.com/blog/2495-multiple-issue-and-pull-request-templates 1/26/2018, 9:01:17 PM - waldyrious (Waldir Pimenta): thought it might interest you (also @sbrl) 1/26/2018, 9:06:32 PM - agnivade (Agniva De Sarker): Hmm .. it seems to be useful to only collaborators and owners ? Because you have to add the query string manually. 1/26/2018, 9:06:40 PM - agnivade (Agniva De Sarker): Atleast that is what I understood 1/26/2018, 9:07:47 PM - waldyrious (Waldir Pimenta): I was thinking we could provide custom links in the readme and/or contributing documents. Of course if they click directly in the "New issue" button, there's nothing we can do to customize the template, so they'd see the generic one 1/26/2018, 9:08:12 PM - agnivade (Agniva De Sarker): I see. Do you have some other templates in mind ? 1/26/2018, 9:09:26 PM - waldyrious (Waldir Pimenta): To be honest, I'm not sure it's warranted. It would make the process more complex, and more cumbersome than it is now. I just wanted to let you know since I seem to recall you complaining about the lack of such an option when we were first discussing the issue template 1/26/2018, 9:10:05 PM - agnivade (Agniva De Sarker): right. I think we are good for now. 1/26/2018, 9:10:14 PM - waldyrious (Waldir Pimenta): :+1: 1/27/2018, 3:25:34 AM - sbrl (Starbeamrainbowlabs): @waldyrious Yeah, I did! Perhaps we could make use of it? Not sure we absolutely need it right now, but it's good to keep in mind 1/27/2018, 6:12:02 PM - waldyrious (Waldir Pimenta): yep, agreed 1/28/2018, 11:37:14 PM - owenvoke (Owen Voke): I was just interested, when merging PRs, do any of you use interactive rebasing or squash merges? 1/29/2018, 12:22:25 AM - agnivade (Agniva De Sarker): I rarely use interactive rebase. I either squash or rebase. 1/29/2018, 12:34:16 AM - owenvoke (Owen Voke): I squashed a change the other day (locally), but didn't push it as it doesn't seem to let you without forcing. Was interested if that's right. 1/29/2018, 2:19:03 AM - sbrl (Starbeamrainbowlabs): Hrm. I usually use the web interface to review & merge PRs 1/29/2018, 2:19:40 AM - sbrl (Starbeamrainbowlabs): Squashing requires a force-push to the PR branch as it modifies history, IIRC 1/29/2018, 2:20:00 AM - owenvoke (Owen Voke): That's what I use too. (The web interface). 1/29/2018, 2:20:48 AM - owenvoke (Owen Voke): I was just interested if it's easy to do locally. I'll stick with the web interface for now. :+1: 1/29/2018, 2:28:42 AM - sbrl (Starbeamrainbowlabs): Yeah, it's a bit of a pain. IIRC, the web interface gives you instructions to do it locally somewhere 1/29/2018, 2:03:03 PM - waldyrious (Waldir Pimenta): @pxgamer I sometimes do interactive rebase if I particularly like some of the individual commits in a PR but have to modify or combine others (e.g. if one of them has a typo). It's fine to do that as long as the resulting history is an accurate summary of the actual changes in the PR. 1/29/2018, 2:03:15 PM - waldyrious (Waldir Pimenta): The main downside is that it takes longer and requires dropping down to the CLI, so we don't ask any maintainer to do that. But they certainly can if they're up for it. 1/29/2018, 2:03:47 PM - waldyrious (Waldir Pimenta): I personally find it preferable to do an interactive rebase (if I have the time/patience) rather than outright squashing a series of commits down to one, just to suppress some noisy ones in the lot. 1/29/2018, 2:05:39 PM - owenvoke (Owen Voke): :+1: Cheers. I usually prefer CLI usage. But I'll have to look properly into how to do those things (not really used anything before other than a basic merge) as I don't help with many other projects. 1/29/2018, 2:06:53 PM - waldyrious (Waldir Pimenta): the nice thing with git being decentralized is you can try stuff locally without worries, and only push if it looks good :) 1/29/2018, 2:09:04 PM - owenvoke (Owen Voke): :+1: 1/29/2018, 3:33:37 PM - sbrl (Starbeamrainbowlabs): Yeah - the `git` commands you end up using as a maintainer are quite often radically different to those when programming by yourself lol 1/29/2018, 3:40:35 PM - waldyrious (Waldir Pimenta): Yep. Although it does make you better art contributing to projects where you're not a maintainer, though, since you start paying more attention to what makes reviewing/merging easier 😉 1/29/2018, 3:41:14 PM - waldyrious (Waldir Pimenta): (small, atomic, well described commits; up-to-date branch bases; etc.) 1/29/2018, 4:02:58 PM - sbrl (Starbeamrainbowlabs): Indeed! 1/14/2023, 3:15:43 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im joined the room 1/30/2018, 11:43:34 AM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Hey! I was thinking about adding some new functionality to tldr pages, would like to discuss it first. Anyone up...? 1/30/2018, 12:09:10 PM - owenvoke (Owen Voke): I am now. :+1: 1/30/2018, 12:10:48 PM - owenvoke (Owen Voke): Better to wait for a proper owner though. 😄 1/30/2018, 12:51:22 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Well, I was thinking about writing a tool that can render the tldr pages as pdf, could be useful for portability and offline usage, maybe for printing. Just wanted to discuss around the idea 1/30/2018, 1:07:09 PM - sbrl (Starbeamrainbowlabs): Sounds like a cool idea! I'm aware that there is a script or something that renders the whole lot to PDF, but I'm not sure where that went. Go ahead! 1/30/2018, 1:19:16 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Yeah, I wanted to know if something like that already exists 1/30/2018, 1:20:58 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: I can try to include options to selectively render as well. Ready to hear about more ideas 1/30/2018, 1:34:56 PM - agnivade (Agniva De Sarker): @aydwi - Please take a look at this - https://github.com/tldr-pages/tldr/blob/master/scripts/generate-pdf.sh. 1/30/2018, 1:35:11 PM - agnivade (Agniva De Sarker): I tried working with it .. got stuck installing some latex dependency. 1/30/2018, 1:35:23 PM - agnivade (Agniva De Sarker): Would be great if you can bring it to a working state ! 1/30/2018, 1:39:00 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: I'll definitely look into it. I was thinking about writing it in Python, so that there is no platform specific dependency 1/30/2018, 1:58:53 PM - agnivade (Agniva De Sarker): :+1: 1/30/2018, 1:59:27 PM - agnivade (Agniva De Sarker): Python 3 please .. 😄 1/30/2018, 3:14:23 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Sure, also any other ideas are welcome 1/31/2018, 11:42:04 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Hey people, I wrote a script that can render the pages as a PDF without any platform specific dependency. Would like to know your thoughts - https://github.com/aydwi/tldr/tree/master/pdf 1/31/2018, 11:52:55 PM - owenvoke (Owen Voke): That sounds great. Just looking at it now. :+1: 1/31/2018, 11:55:47 PM - owenvoke (Owen Voke): It's unlikely I'd ever use it. But looks nice to me. 😄 2/1/2018, 12:28:18 AM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: @pxgamer I wrote it because it could be helpful for offline viewing or printing maybe! 2/1/2018, 1:08:07 AM - owenvoke (Owen Voke): I assume so. Where I work we were recently thinking about sticking common commands we use on the walls. 😛 So this is pretty similar actually. 2/1/2018, 1:22:25 AM - sbrl (Starbeamrainbowlabs): Ah, looks cool, @aydwi! I've used the CLI version of WEasyPrint before - it's awesome. Good job! 😺 2/2/2018, 2:29:54 PM - owenvoke (Owen Voke): Should it be alright to merge #1943? I was just wondering if it's required to wait for a reply. 😄 2/2/2018, 2:39:46 PM - waldyrious (Waldir Pimenta): There should be no problem in waiting for the submitter's response, nothing is lost and stale-bot would take care of bumping the thread after a while anyway 2/2/2018, 2:41:48 PM - owenvoke (Owen Voke): Sounds good :+1: 2/2/2018, 2:42:22 PM - waldyrious (Waldir Pimenta): but since there are two approvals already, and the question asked is quite minor (i.e. it's reasonable to expect that the response wouldn't make much of a difference), I guess it's ok to wrap it up 2/2/2018, 2:42:45 PM - waldyrious (Waldir Pimenta): Maybe I'd give it a week, just to use a "rounder" time period 😛 2/2/2018, 2:42:59 PM - waldyrious (Waldir Pimenta): so 2 days from now, if I'm reading the timestamps correctly 2/2/2018, 2:44:10 PM - waldyrious (Waldir Pimenta): Btw, I'm glad you asked this. It's very important to have explicit and predictable rules in collaborative projects, but it's even more important to develop a sense of when it's ok to bend those rules : ) 2/6/2018, 1:32:26 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: @sbrl @agnivade Made suggested changes to the PDF rendering script! 2/6/2018, 1:33:04 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: I think it can be reviewed now - https://github.com/tldr-pages/tldr/pull/1964 2/6/2018, 1:35:16 PM - owenvoke (Owen Voke): I might test it out in a bit. :+1: Looks interesting and I'm wondering what the new structure is. 2/6/2018, 1:38:55 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: Would love to know your thoughts 😄 2/6/2018, 1:39:48 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: The new script renders all the pages as a single PDF, with their respective title pages 2/6/2018, 2:24:19 PM - owenvoke (Owen Voke): All pages sounds good. Is that seperated by OS? Or all in one? :+1: 2/6/2018, 2:25:27 PM - owenvoke (Owen Voke): It's Python 3, right? 2/6/2018, 2:45:54 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: All pages, separated by the name of the OS 2/6/2018, 2:46:05 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: It is Python 3 2/6/2018, 3:00:29 PM - owenvoke (Owen Voke): :+1: Sounds good. 2/9/2018, 2:40:12 PM - owenvoke (Owen Voke): Hi, I was just going to merge #1981. I know the title makes it quite obvious what it does, but do we have a consistent message. (i.e. pages being `page: description`). I was going to change the commit message to `README: add Dash docset (#1981)` 2/9/2018, 2:53:46 PM - agnivade (Agniva De Sarker): yes, that is preferred. 2/9/2018, 2:56:35 PM - owenvoke (Owen Voke): Cool :+1: 2/11/2018, 7:29:15 PM - dbrgn (Danilo Bargen): Tealdeer is now at 1.0.0 🎉 https://github.com/dbrgn/tealdeer/ 2/11/2018, 7:30:38 PM - dbrgn (Danilo Bargen): Also, I did some speed testing: A `tldr tar` command takes 9ms on average on my system to render :) 2/11/2018, 10:54:19 PM - sbrl (Starbeamrainbowlabs): Congrats, @dbrgn! 2/11/2018, 11:57:40 PM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im: @dbrgn Looks good! 2/12/2018, 8:03:13 AM - jayvdb (John Vandenberg): "tealdeer" is a cute name, and a great logo 2/12/2018, 3:00:24 PM - sbrl (Starbeamrainbowlabs): Indeed! 😃 2/12/2018, 4:24:13 PM - dbrgn (Danilo Bargen): Thanks! :) @sshrike came up with the name, and the logo is based on a public domain illustration IIRC. 2/17/2018, 11:44:51 AM - agnivade (Agniva De Sarker): @/all - I have started work on the command coverage tool. There doesn't seem to be a programmatic way to get commands for all platforms from the internet. For linux, there are some solutions, but none that I liked. So, I have decided to go with parsing wikipedia pages for this. I believe wikipedia pages will have a stable structure and we can get commands for all platforms from a single source. 2/17/2018, 3:15:51 PM - sbrl (Starbeamrainbowlabs): Cool! 2/17/2018, 4:20:58 PM - owenvoke (Owen Voke): Just interested about PR #2003, as per the style guide is it fine to have it as an example with a preceding slash? If so, I'll mark it as approved by me. It looks like `{{/dev/sdb7}}` is used in the 2 pages they mentioned anyway. 😄 2/17/2018, 4:51:35 PM - sbrl (Starbeamrainbowlabs): Yeah, I think that `/dev/*` paths are a special case. 2/17/2018, 4:52:17 PM - owenvoke (Owen Voke): Cool :+1: I'll mark it as approved. :) 2/18/2018, 12:24:42 AM - agnivade (Agniva De Sarker): Yes, @sbrl is right. 2/19/2018, 1:09:43 PM - owenvoke (Owen Voke): Should PR #1986 be named as it is when merging? As it contains both a new page and an edit to an existing page. 2/20/2018, 10:32:48 AM - agnivade (Agniva De Sarker): Yes, as long as the individual commits are named properly. I don't see a major issue. 2/20/2018, 1:07:38 PM - owenvoke (Owen Voke): Cheers. 2/22/2018, 12:31:26 PM - agnivade (Agniva De Sarker): ping @waldyrious - Will you be able to review https://github.com/tldr-pages/tldr/pull/2002 ? 2/22/2018, 12:31:35 PM - agnivade (Agniva De Sarker): anybody else is also welcome to review 1/14/2023, 3:16:07 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im joined the room 2/22/2018, 1:23:58 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: Hi @agnivade , just for interest at this pr: Is the command_coverage.svg auto generated? 2/22/2018, 1:27:31 PM - owenvoke (Owen Voke): Pretty sure, I think that's what the 2/22/2018, 1:29:14 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: Yeah, I just saw that `scripts/command_coverage/runner.py` generates it 2/22/2018, 1:29:58 PM - owenvoke (Owen Voke): Sorry, accidentally posted before finishing. 2/22/2018, 1:30:43 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: I knew what you wanted to write, haha 😃 2/22/2018, 1:31:28 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: I'm not really into Python, just wanted to see how it works 😊 2/22/2018, 1:32:28 PM - owenvoke (Owen Voke): :+1: I don't use Python either. 2/22/2018, 4:05:37 PM - waldyrious (Waldir Pimenta): @agnivade I've seen it, very excited to review it, but I can't promise when I'll have the time to do so 2/22/2018, 4:06:35 PM - waldyrious (Waldir Pimenta): would you suggest checking out the branch locally and running the script to test it, or just an overall review of the code? 2/22/2018, 4:07:39 PM - waldyrious (Waldir Pimenta): @pxgamer you normally can just tap the up arrow key and gitter will let you amend your previous message 2/22/2018, 4:08:07 PM - waldyrious (Waldir Pimenta): probably for a couple minutes or so, and possibly not after someone responds, but I haven't tested 2/22/2018, 4:08:36 PM - owenvoke (Owen Voke): On a mobile? I couldn't find a way. 😛 2/22/2018, 4:09:41 PM - waldyrious (Waldir Pimenta): oh, don't know about that. good question. On desktop there's the three dots icon that you can click to open a menu (instead of pressing "up"), but I'm not sure that exists in the mobile app 2/22/2018, 4:10:11 PM - waldyrious (Waldir Pimenta): (the ... appears next to the timestamp, if you hover a message) 2/22/2018, 4:10:36 PM - owenvoke (Owen Voke): Doesn't seem to. I'm using a desktop at the moment so no worries :) 2/22/2018, 4:15:35 PM - waldyrious (Waldir Pimenta): :+1: 2/22/2018, 4:16:23 PM - waldyrious (Waldir Pimenta): btw, regarding the path guidelines in the style guide, indeed paths that are meant to be absolute (rather than an example) should have the leading `/` 2/22/2018, 4:18:20 PM - waldyrious (Waldir Pimenta): I went to change [the document](https://github.com/tldr-pages/tldr/blob/master/contributing-guides/style-guide.md#token-syntax) to clarify that, but I am a bit confused with points 3 and 4. I can't pinpoint what different contexts they are meant to apply to (i.e. why they're two separate rules rather than a single one). 2/22/2018, 4:24:00 PM - waldyrious (Waldir Pimenta): Tracing the git history back, they seem to have been introduced in #981 by @agnivade. I re-read the PR discussion (jeez, that one must have been a pain in the ass!), but even though at the time I acknowledged there being two entries for path-related tokens (e.g. in [this comment](https://github.com/tldr-pages/tldr/pull/981#discussion_r74396743)), I didn't seem to be bothered by the apparent duplication. I guess at the time I understood the difference between them, but at the moment I don't 😕 can anyone chime in with their thoughts? 2/22/2018, 8:48:57 PM - agnivade (Agniva De Sarker): @waldyrious - Yes, I meant an overall review of the code. @Crease29 - The entire svg is not auto-generated. Just the value in the svg is updated if there is a change. 2/22/2018, 8:49:42 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: @agnivade then I'd either compress it or format it correctly 2/22/2018, 8:50:27 PM - agnivade (Agniva De Sarker): You mean remove whitespaces ? I didn't do that to keep it readable. 2/22/2018, 8:53:24 PM - agnivade (Agniva De Sarker): @waldyrious - AFAIR, the point was to remain consistent. To apply the preceding '/' or not can be easily understood by the user. It's just that for disk partitions, it is really odd to say - "dev/sda1" rather than "/dev/sda1". Technically you can say that since its a concrete value, it needs to be correct. Whereas a generic token like "path/to/file" does not need to be correct. Hence it makes sense to be consistent in generic tokens, and to be correct in concrete tokens. 2/22/2018, 8:59:17 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: Yes, by compressing i mean putting everything in one line or so. By formatting it correctly I mean indenting the code 2/22/2018, 9:06:18 PM - owenvoke (Owen Voke): Is there anything wrong with using a URL in the README that gets updated, which would keep the padding on it the same as the other badges? e.g. ![example](https://img.shields.io/badge/command%20coverage-30%25-brightgreen.svg) (or is it an svg just to keep it independent from the rest of the repo)? 2/22/2018, 9:13:24 PM - waldyrious (Waldir Pimenta): @agnivade I understand that; concrete absolute path examples should include the /, and generic example paths should not. What I'm confused is about the difference between rules 3 and 4 in the style guide. They seem to be saying more or less the same to me 2/22/2018, 11:34:27 PM - agnivade (Agniva De Sarker): @Crease29 - Ah, it's the `` element, isn't it ? 😉 I will fix it. 2/22/2018, 11:34:48 PM - agnivade (Agniva De Sarker): @waldyrious - Hmm .. you are right. I think they should be combined into 1. It is essentially about the path tokens. 2/22/2018, 11:35:50 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: @agnivade I'd format it like this: ```xml command coverage command coverage 30% 30% ``` 2/22/2018, 11:36:49 PM - agnivade (Agniva De Sarker): Thanks. I will change it. 2/22/2018, 11:37:12 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: You're welcome 😊 2/22/2018, 11:41:15 PM - agnivade (Agniva De Sarker): hmm .. I just checked. Just a minor issue. Since I am rewriting the file after updating the xml dom, the python minidom library puts the `` and `` tag in the first line. 2/22/2018, 11:41:33 PM - agnivade (Agniva De Sarker): I guess not much to do here. I will leave it at that for now. 2/22/2018, 11:44:17 PM - agnivade (Agniva De Sarker): @pxgamer - The README already points to an svg file. The code just updates the svg file. The padding is slightly out of whack. I have been focussing on the code for the moment. Will fix those issues eventually. 2/22/2018, 11:45:12 PM - owenvoke (Owen Voke): Sounds good. :+1: 2/22/2018, 11:52:56 PM - owenvoke (Owen Voke): Looks better now. 😄 2/23/2018, 12:02:09 AM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: Nice, thanks for checking this though! 1/14/2023, 3:16:27 PM - hellojmbtech (JMB Technology Limited) joined the room 2/25/2018, 4:24:02 PM - hellojmbtech (JMB Technology Limited): Hello, I'm working on a project making data on GitHub more useful: https://www.datatig.com/ I put the tldr data in it as a demo: https://www.datatig.com/gh/tldr-pages/tldr/b/master/ It's very early days for this project but I just wanted to get in touch to ask for thoughts and feedback. My email is james@jmbtechnology.co.uk or @ me here. 2/25/2018, 4:24:48 PM - hellojmbtech (JMB Technology Limited): (Also, Your live demo on the front page is broken - if you click the "edit" link you get a "Content Security Policy" block) 2/26/2018, 1:58:37 PM - owenvoke (Owen Voke): @hellojmbtech that looks interesting. Good luck with your project. :+1: 2/26/2018, 1:59:24 PM - owenvoke (Owen Voke): Regarding the demo, I'm not sure if that's really much of an issue. All it is is a demo, so I'm assuming that someone wouldn't be using it through an iframe in real use. 😄 2/26/2018, 2:28:43 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: I don't understand the benefit of DataTig 😃 2/26/2018, 3:52:08 PM - hellojmbtech (JMB Technology Limited): @pxgamer Well, a real use of it would be someone trying it out on the front page of your website as they have been invited to do and finding an error :-) Just thought it would look better not to have errors on the site so thought I would mention. 2/26/2018, 3:58:13 PM - hellojmbtech (JMB Technology Limited): @Crease29 Maybe this isn't a good example as this project already has great ways of distributing the content, but for some projects I'm hoping this can make the content much more useful. For instance in one of our documentation MD files we have a YML block at the top with tags; on GitHub you just see a wee table https://github.com/DataTig/Documentation/blob/master/docs/field-latlng.md but we can make those tags searchable https://www.datatig.com/gh/DataTig/Documentation/b/master//d/docs/f/tags (ps. Our Documentation is very much a work in progress as is the project, sorry!) Other data we can put on maps or calendars for people. I guess as people who work with user content on GitHub I was just interested in your feedback. (Thanks @pxgamer :-) ) 2/26/2018, 4:05:26 PM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im: Thank you for providing these examples, @hellojmbtech 😊 Gotcha! 2/26/2018, 4:10:03 PM - hellojmbtech (JMB Technology Limited): Do you think there is something we could have added to our front page explanation to make it clearer? (May as well do some user research :-) ) 3/1/2018, 3:02:11 AM - owenvoke (Owen Voke): Sorry for not getting back to you @hellojmbtech, I actually think that from looking at the front page, it's pretty explanatory. 3/1/2018, 5:18:52 AM - hellojmbtech (JMB Technology Limited): @pxgamer Thanks :-) 3/25/2018, 12:39:15 AM - agnivade (Agniva De Sarker): @/all - Github pushed a new feature recently allowing multiple reviewers for PRs. https://blog.github.com/2018-03-23-require-multiple-reviewers/ 3/25/2018, 12:39:27 AM - agnivade (Agniva De Sarker): I have set the no. to 2 for our repo according to our policy. 3/25/2018, 12:40:00 AM - agnivade (Agniva De Sarker): This will hopefully make things more clear to newcomers who might be wondering why is a PR not yet pushed even after it has got one approval. 3/25/2018, 1:25:20 AM - owenvoke (Owen Voke): That sounds good to me. :+1: 3/25/2018, 2:47:09 AM - sbrl (Starbeamrainbowlabs): Cool! 😃 3/25/2018, 10:19:28 AM - jayvdb (John Vandenberg): that is a very nice feature 3/25/2018, 10:19:43 AM - jayvdb (John Vandenberg): GitLab has had that forever .. 😉 3/26/2018, 1:52:46 PM - waldyrious (Waldir Pimenta): Finally, the last bit of the LGTM service becomes native to github :) (that was the last one missing, right?) 3/26/2018, 3:53:02 PM - sbrl (Starbeamrainbowlabs): Think so! 3/27/2018, 10:24:01 AM - agnivade (Agniva De Sarker): yep 1/14/2023, 3:16:36 PM - thescalaguy (thescalaguy) joined the room 3/27/2018, 11:44:15 AM - thescalaguy (thescalaguy): So I ran into this interesting case where linter fails on GitHub but passes locally 😛 3/27/2018, 11:50:25 AM - thescalaguy (thescalaguy): Ok, ignore. I ended up accidentally committing another .md file. 3/27/2018, 1:25:00 PM - owenvoke (Owen Voke): :+1: 3/30/2018, 7:51:28 PM - agnivade (Agniva De Sarker): tldr node client is released with some new features. Download and check it out. 3/30/2018, 7:51:36 PM - agnivade (Agniva De Sarker): Please report if you see any issues 😃 1/14/2023, 3:16:39 PM - tgrrr (Phil) joined the room 5/12/2018, 7:00:17 PM - tgrrr (Phil): Hey, big fan - and I'd like to start using this for other languages. Ie. Python, R language, React and JavaScript ES6. Ideally, I'd like to contribute it to tue current tldr-pages. But I'm happy to fork it, if that's what you'd all prefer? 5/12/2018, 7:13:26 PM - sbrl (Starbeamrainbowlabs): Hey there, @tgrrr! Erm, how do you mean "other languages"? I thought that tldr-pages was language-agnostic, as it documents common usages of commands. 1/14/2023, 3:16:44 PM - ShivamSinghania (Shivam Singhania) joined the room 5/16/2018, 11:21:59 PM - ShivamSinghania (Shivam Singhania): hey I'm new, I have ubuntu 18.04 and bash as terminal... which client should I install ? node.js, bash, snap ? what's the difference between them ? 5/17/2018, 12:58:05 AM - sbrl (Starbeamrainbowlabs): Hello, @ShivamSinghania! The Node.JS client is maintained by @agnivade, who is a part of tldr-pages itself - so I'd recommend that one. Personally, I use the bash client, as it's more lightweight - so there's that option too. Mainly, it comes down to which language you prefer your programs to be written in. For example, a programmer who primarily uses Python would probably want to install the Python client, as they are more familiar with that environment. 5/17/2018, 1:24:37 AM - ShivamSinghania (Shivam Singhania): ok. thanks @sbrl 5/17/2018, 1:25:00 AM - sbrl (Starbeamrainbowlabs): Np! Just let us know fi you need any further assistance 😺 5/19/2018, 3:39:39 PM - tgrrr (Phil): @sbrl I mean documentation for languages like Python, React, JavaScript, etc 5/19/2018, 3:58:04 PM - sbrl (Starbeamrainbowlabs): Ah, I see! I'm not sure. tldr-pages is meant for command-line tools. @agnivade / @waldyrious? 5/19/2018, 8:32:24 PM - agnivade (Agniva De Sarker): @tgrrr - Sorry I don't understand. tldr pages are like simplified man pages for command line tools. It has nothing to do with documentation for languages. 5/20/2018, 5:08:40 AM - tgrrr (Phil): @agnivade @sbrl tldr pages is great, and the way it's been built to work almost anywhere is ideal. I've found myself wanting a tldr pages version for other languages I'm working with, and so would really like to make it available for them 1/14/2023, 3:16:48 PM - IvanFon (Ivan Fonseca) joined the room 5/20/2018, 7:13:51 AM - IvanFon (Ivan Fonseca): The closest thing to tldr pages for programming languages is probably SyntaxDB or Learn X in Y Minutes 5/20/2018, 7:14:08 AM - IvanFon (Ivan Fonseca): @tgrrr ^ 5/20/2018, 12:49:19 PM - tgrrr (Phil): @IvanFon Thanks. @agnivade @sbrl, would you prefer if I forked tldr pages? Although, mainly I'd just be creating new markdown pages, a Dash docset and Alfred integration for the other languages. 5/20/2018, 12:51:13 PM - agnivade (Agniva De Sarker): It is under MIT license, so feel free to fork. 5/20/2018, 2:39:25 PM - sbrl (Starbeamrainbowlabs): Go ahead! I think a fork would be best at this stage, yeah. 5/21/2018, 6:54:41 AM - tgrrr (Phil): Thanks guys, obviously I'd rather keep it together, but much appreciated! 5/21/2018, 1:01:52 PM - agnivade (Agniva De Sarker): I may not be able to understand your idea properly. But tldr pages are just for commands, so I don't think it is possible to have a "tldr pages version" for programming languages. 5/21/2018, 1:02:03 PM - agnivade (Agniva De Sarker): But please feel free to fork and work on it. 5/21/2018, 1:13:10 PM - agnivade (Agniva De Sarker): Note that tldr pages are not meant to be a cheat sheet sort of thing. If you are thinking of making a shorter, one-page version of devhints.io, then perhaps a fork is the best way to go. 5/21/2018, 1:45:14 PM - waldyrious (Waldir Pimenta): wow, I didn't know about syntaxdb nor devhints.io -- thanks @IvanFon and @agnivade for the pointers, added to my bookmarks. 5/21/2018, 1:46:07 PM - waldyrious (Waldir Pimenta): I personally like hyperpolyglot, which is even on github: http://hyperpolyglot.org/, https://github.com/clarkgrubb/hyperpolyglot 5/21/2018, 1:48:59 PM - waldyrious (Waldir Pimenta): @tgrrr we do have pages for programming languages's CLIs though, see e.g. [python](https://github.com/tldr-pages/tldr/blob/master/pages/common/python.md), [javascript (node)](https://github.com/tldr-pages/tldr/blob/master/pages/common/node.md), [ruby](https://github.com/tldr-pages/tldr/blob/master/pages/common/ruby.md), [perl](https://github.com/tldr-pages/tldr/blob/master/pages/common/perl.md), etc. 5/21/2018, 1:49:49 PM - waldyrious (Waldir Pimenta): does any of these, or the sites mentioned, approximate what you had in mind? if not, could you provide an example or two of what you idealize? 5/21/2018, 2:12:38 PM - sbrl (Starbeamrainbowlabs): Neither did I! They look cool. 5/21/2018, 2:18:51 PM - waldyrious (Waldir Pimenta): And an off-topic note, but I owe the community and especially the other maintainers: my son was born last month 😃 he's healthy and taking up big chunks of my time and energy, which is why I haven't been actively maintaining the project in a while 5/21/2018, 2:20:11 PM - waldyrious (Waldir Pimenta): we might want to update the list of maintainers to mark me as temporarily inactive (and maybe consider onboarding new ones?), so that people aren't mislead by our documentation. 5/21/2018, 3:38:13 PM - sbrl (Starbeamrainbowlabs): Ah, great to hear! Re onboarding new ones, @pxgamer has joined us recently as a maintainer 5/21/2018, 3:46:40 PM - owenvoke (Owen Voke): Congratulations @waldyrious! 5/21/2018, 3:46:45 PM - waldyrious (Waldir Pimenta): yes, I am aware of @pxgamer (and I believe @jsonbruce as well, right?) joining. I've been noticing particularly @pxgamer's activity in my notifications, I'm glad he joined us! I was just wondering if other potential candidates had emerged in the community :) 5/21/2018, 3:46:51 PM - waldyrious (Waldir Pimenta): thanks! 😃 5/21/2018, 3:49:03 PM - sbrl (Starbeamrainbowlabs): I haven't noticed any, but that's not to say they don't exist. I'm just bad at noticing that kind of thing 😛 5/21/2018, 3:49:24 PM - waldyrious (Waldir Pimenta): we all are. My goal is to eventually have a bot to do it for us 😃 5/21/2018, 3:50:54 PM - sbrl (Starbeamrainbowlabs): Ah, awesome! Maybe @tldr-bot could do it eventually 5/21/2018, 3:55:38 PM - owenvoke (Owen Voke): That would be great. :+1: 5/21/2018, 3:55:53 PM - agnivade (Agniva De Sarker): Congrats @waldyrious ! Hope to have you back soon. 5/21/2018, 3:56:06 PM - agnivade (Agniva De Sarker): Let me see about the list of maintainers .. maybe I can send a PR. 5/21/2018, 3:58:55 PM - waldyrious (Waldir Pimenta): thanks :) 5/21/2018, 3:59:43 PM - waldyrious (Waldir Pimenta): oh, I just noticed that gitter finally stopped replacing `:)` with `:smile:`! It was about time 😃 5/21/2018, 4:00:15 PM - waldyrious (Waldir Pimenta): huh, I guess conversion of all simple ASCII emojis were deactivated. Cool. 😟 😕 😛 😮 5/21/2018, 7:48:14 PM - owenvoke (Owen Voke): Hmm. :) 5/21/2018, 7:48:23 PM - owenvoke (Owen Voke): They were? 5/21/2018, 7:51:06 PM - waldyrious (Waldir Pimenta): the changes had been merged about 3 months ago, but the deployment apparently only happened last week: https://gitlab.com/gitlab-org/gitter/webapp/merge_requests/1097 1/14/2023, 3:17:02 PM - TimothyBramlett (Timothy Bramlett) joined the room 6/6/2018, 3:15:30 AM - TimothyBramlett (Timothy Bramlett): Question: Does tldr use a library for rendering the markdown files on the CLI? Or someone wrote some custom code to do it? 6/6/2018, 3:16:38 AM - sbrl (Starbeamrainbowlabs): Great question, @TimothyBramlett ! It depends on the client. Each client is free to do it differently - I'd recommend asking the maintainer(s) of a specific client. A list of clients can be found in the README on the main tldr-pages repo. 6/6/2018, 3:17:41 AM - TimothyBramlett (Timothy Bramlett): @sbrl Oh interesting! I was wondering because I want to render some markdown files on the CLI. I'm going to seek out some of the best options to do so I guess. 6/6/2018, 3:17:56 AM - TimothyBramlett (Timothy Bramlett): @sbrl Thanks for the info! :) 6/6/2018, 3:18:30 AM - sbrl (Starbeamrainbowlabs): Ah, I see. In that case, I'd recommend asking the maintainer of the client that's written in the language we want to use when rendering your own markdown on the CLI. 6/6/2018, 3:18:33 AM - sbrl (Starbeamrainbowlabs): And np! 6/6/2018, 3:21:03 AM - TimothyBramlett (Timothy Bramlett): @sbrl Oh good point! 6/6/2018, 7:35:55 PM - agnivade (Agniva De Sarker): It also depends on the language you are using. The node client uses the marked library. It does its job well enough. 6/13/2018, 9:52:37 PM - waldyrious (Waldir Pimenta): Hi everyone. As some of you may be aware, my account has been compromised a few days ago. It looks like the only malicious actions were a bunch of releases in repositories where I have push access, which included a malware executable called install.exe as an attachment. 6/13/2018, 9:53:48 PM - waldyrious (Waldir Pimenta): My account has been flagged due to a report from one of the affected users (a member of another organization I'm part of) and since then I activated 2-factor authentication in my account, changed my password, revoked all active sessions, and emailed github support 6/13/2018, 9:55:24 PM - owenvoke (Owen Voke): Glad to hear you've sorted it. :+1: 6/13/2018, 9:56:01 PM - waldyrious (Waldir Pimenta): Hopefully that should be sufficient to restore my account's security. I apologize for any inconvenience to users of repositories in the tldr-pages organization 😟 6/13/2018, 9:57:06 PM - waldyrious (Waldir Pimenta): Thanks for understanding @pxgamer. I don't know what I did to make my account vulnerable. I encourage everyone to activate 2FA just in case :) 6/13/2018, 9:57:20 PM - sbrl (Starbeamrainbowlabs): Oh no! I hadn't noticed yet. 6/13/2018, 9:57:34 PM - sbrl (Starbeamrainbowlabs): No problem though! 6/13/2018, 9:57:39 PM - waldyrious (Waldir Pimenta): Hahah that's good I guess. Looks like the damage was limited 6/13/2018, 9:58:12 PM - sbrl (Starbeamrainbowlabs): Yeah 6/13/2018, 9:58:30 PM - sbrl (Starbeamrainbowlabs): I can't see any recent commits of yours that look suspicious in the main tldr-pages repo 6/13/2018, 9:59:31 PM - waldyrious (Waldir Pimenta): Yeah, IIUC it was actually a tag, not a commit; and the release had the executable added as an attachment 6/13/2018, 10:00:38 PM - waldyrious (Waldir Pimenta): in any case, I believe the releases made in the tldr-pages org were already deleted (I can't find those actions in the audit log, though) 6/13/2018, 10:00:52 PM - sbrl (Starbeamrainbowlabs): ah, ok 6/13/2018, 10:01:00 PM - waldyrious (Waldir Pimenta): There's more context here: https://github.com/opencompany/www.opencompany.org/issues/176 6/13/2018, 10:01:25 PM - waldyrious (Waldir Pimenta): I commented there but until my account is unflagged by github, you won't be able to see it. 6/13/2018, 10:05:55 PM - sbrl (Starbeamrainbowlabs): Ah 6/13/2018, 10:06:10 PM - sbrl (Starbeamrainbowlabs): I can post a comment about it if you like to let everyone know 6/13/2018, 10:08:32 PM - waldyrious (Waldir Pimenta): Oh, that'd be nice, thanks. Please let them know that I thank @balupton for reporting my account, but unfortunately due to the resulting flagging of my account as a spammer, my comment in that thread is not visible. Tell them I've taken steps to secure my account and will make sure to clean up any remaining issues once my account gets unflagged. 6/13/2018, 10:08:35 PM - waldyrious (Waldir Pimenta): Thanks! 😃 6/13/2018, 10:09:11 PM - waldyrious (Waldir Pimenta): In fact, since this chat log is public, you can link to my explanation above: https://gitter.im/tldr-pages/tldr?at=5b2144cd1ee2d149ecbf3d00 6/13/2018, 10:10:09 PM - sbrl (Starbeamrainbowlabs): Done: https://github.com/opencompany/www.opencompany.org/issues/176#issuecomment-397004921 6/13/2018, 10:10:40 PM - sbrl (Starbeamrainbowlabs): Ah, awesome! Didn't know you could link to a specific time in a Gitter conversation. 6/13/2018, 10:10:50 PM - waldyrious (Waldir Pimenta): I couldn't have said it better 😃 thanks a lot! 6/13/2018, 10:11:08 PM - sbrl (Starbeamrainbowlabs): no problem :-) 6/13/2018, 10:11:20 PM - waldyrious (Waldir Pimenta): yeah, the timestamp is a link :) 6/13/2018, 10:11:30 PM - waldyrious (Waldir Pimenta): there's also a daily archive, let me see if I can find it 6/13/2018, 10:11:51 PM - waldyrious (Waldir Pimenta): yup, here: https://gitter.im/tldr-pages/tldr/archives/all 6/13/2018, 10:12:38 PM - waldyrious (Waldir Pimenta): it's the "Archives" link in the menu that shows up if you click the "room settings" icon on the top right 1/14/2023, 3:17:18 PM - balupton (Benjamin Lupton) joined the room 6/13/2018, 10:15:04 PM - balupton (Benjamin Lupton): Just popping in to say glad it is all getting sorted. Hope that your account gets restored soon, and ideally if GitHub can help you find the cause. Cheers all. And thanks Waldir for the thank you, happy I was able to be of some use. :) 6/13/2018, 10:16:43 PM - sbrl (Starbeamrainbowlabs): Ah, awesome! 6/13/2018, 10:19:14 PM - waldyrious (Waldir Pimenta): @balupton yeah, I hope they are able to give me some details about how my account got compromised. I reviewed the security log at https://github.com/settings/security but didn't find any clues there... 6/13/2018, 10:46:12 PM - agnivade (Agniva De Sarker): phew .. glad everything is fine. Even github.com/waldyrious started to give 404s, I was thinking of shooting you a mail, but here you are :) 6/13/2018, 10:49:59 PM - waldyrious (Waldir Pimenta): Yeah, I activated 2FA right away, but apart from that, only today I managed to actually look into the issue in more detail, review the security logs and contact github. 6/13/2018, 10:50:05 PM - waldyrious (Waldir Pimenta): I have this terrible habit of not providing feedback until I actually have good news to tell, so I ended up postponing reaching out to you guys to reassure you. Sorry about that! 6/13/2018, 11:00:29 PM - waldyrious (Waldir Pimenta): I just got a response from GitHub; my account has been unflagged and they confirmed that it is secured now. 6/13/2018, 11:12:19 PM - agnivade (Agniva De Sarker): 🎉 6/14/2018, 12:10:41 AM - sbrl (Starbeamrainbowlabs): Awesome 😺 6/14/2018, 12:10:50 AM - sbrl (Starbeamrainbowlabs): Glad you've got it sorted out 6/14/2018, 12:24:34 AM - owenvoke (Owen Voke): :thumbsup: 6/14/2018, 2:00:10 AM - sbrl (Starbeamrainbowlabs): Thanks for correcting your username, @waldyrious! I have some issues with spellings sometimes.... 😛 7/9/2018, 7:01:50 PM - owenvoke (Owen Voke): Just interested, are the tldr repositories using the Travis CI GitHub Apps integration? 7/9/2018, 7:04:31 PM - sbrl (Starbeamrainbowlabs): Good question, @pxgamer! I'm not sure. We should be, if we're not. I'll go take a look at the repo setting and see if I can figure out whether we are. 7/9/2018, 7:06:01 PM - sbrl (Starbeamrainbowlabs): [![Selection_029.png](https://files.gitter.im/tldr-pages/tldr/y0od/thumb/Selection_029.png)](https://files.gitter.im/tldr-pages/tldr/y0od/Selection_029.png) 7/9/2018, 7:06:22 PM - sbrl (Starbeamrainbowlabs): Looks like we're still using services for travis. I think we should probably upgrade that! 7/9/2018, 7:08:52 PM - sbrl (Starbeamrainbowlabs): I've just signed in to Travis CI, and found this button: 7/9/2018, 7:08:59 PM - sbrl (Starbeamrainbowlabs): [![Selection_030.png](https://files.gitter.im/tldr-pages/tldr/6kcD/thumb/Selection_030.png)](https://files.gitter.im/tldr-pages/tldr/6kcD/Selection_030.png) 7/9/2018, 7:09:08 PM - sbrl (Starbeamrainbowlabs): I think that's the one we want. 7/9/2018, 7:09:55 PM - sbrl (Starbeamrainbowlabs): @agnivade I think this is right? 7/9/2018, 7:11:36 PM - sbrl (Starbeamrainbowlabs): Ah - look like each organisation has an option a sidebar (not pictured). 7/9/2018, 7:15:40 PM - owenvoke (Owen Voke): :+1: Yeah, I thought we probably should be. Just so it doesn't suddenly fall over next January. 7/9/2018, 7:18:13 PM - sbrl (Starbeamrainbowlabs): Indeed! 7/9/2018, 7:19:27 PM - sbrl (Starbeamrainbowlabs): Cool, I've activated it. Got this though: 7/9/2018, 7:19:46 PM - sbrl (Starbeamrainbowlabs): [![Selection_031.png](https://files.gitter.im/tldr-pages/tldr/iBrX/thumb/Selection_031.png)](https://files.gitter.im/tldr-pages/tldr/iBrX/Selection_031.png) 7/9/2018, 7:19:58 PM - sbrl (Starbeamrainbowlabs): Time for some reading 7/9/2018, 7:20:16 PM - owenvoke (Owen Voke): Oh yeah. 7/9/2018, 7:26:50 PM - sbrl (Starbeamrainbowlabs): Looks like there's a migration process that's due to start in a month or two for open-source repos. 7/9/2018, 7:27:24 PM - sbrl (Starbeamrainbowlabs): Apparently travis-ci.org is the legacy service, and travis-ci.com is the new service. 7/9/2018, 7:27:26 PM - sbrl (Starbeamrainbowlabs): Source: https://docs.travis-ci.com/user/open-source-on-travis-ci-com/#Existing-Open-Source-Repositories-on-travis-ci.org 7/9/2018, 7:27:31 PM - owenvoke (Owen Voke): I think it said end of Q2? 7/9/2018, 7:27:35 PM - sbrl (Starbeamrainbowlabs): yeah 7/9/2018, 7:27:47 PM - sbrl (Starbeamrainbowlabs): I'm confused about this bit though: `This is an opt-in process: to have a repository migrated over, it must first be activated on travis-ci.com.` 7/9/2018, 7:27:59 PM - sbrl (Starbeamrainbowlabs): I don't see an opt-in button though 7/9/2018, 7:28:37 PM - sbrl (Starbeamrainbowlabs): Maybe it'll come later 7/9/2018, 7:29:50 PM - owenvoke (Owen Voke): Maybe :+1: 7/10/2018, 12:40:25 AM - agnivade (Agniva De Sarker): Oh I was not aware of this. So github services are being deprecated for github apps ? 7/10/2018, 12:40:46 AM - agnivade (Agniva De Sarker): And for travis we need to use travis-ci.com instead of travis-ci.org ? 7/10/2018, 12:43:53 AM - agnivade (Agniva De Sarker): > it must first be activated on travis-ci.com. This is not clear to me. The main page says the repo cannot be migrated because it is active on travis-ci.org. And the doc page says, for a repo to be migrated over, it needs to be first activated on travis-ci.com. How ? 7/10/2018, 12:46:12 AM - sbrl (Starbeamrainbowlabs): Hrm, I'm not sure. Maybe we need to enquire? 7/10/2018, 12:46:57 AM - sbrl (Starbeamrainbowlabs): The docs say that there will be a migration period, apparently 7/10/2018, 12:47:18 AM - sbrl (Starbeamrainbowlabs): They also say that if we're fine with migrating and leaving our build history behind, then we can contact them to do this 7/10/2018, 12:47:34 AM - sbrl (Starbeamrainbowlabs): Either way, I think we might need to ask for clarification. 1/14/2023, 3:17:35 PM - ediardo (Eddie Ramirez) joined the room 7/10/2018, 5:58:38 AM - ediardo (Eddie Ramirez): Hello all, first of all, thanks a lot to all of the maintainers of this awesome project, I've seen how it's seeded many other projects that aim to make the CLI more user friendly and easier to understand. I'm working on a project that uses TLDR Pages commands as a starting to point to build *yet another community-driven repository of commands* and this time, I want to share with you a repository (https://github.com/kommandr/tldr-pages-parser) with scripts that extract information from the .md files living inside of tldr-pages repo and generate a pair of JSON files named programs.json and commands.json with all of the information available in your manual pages. I managed to extract more than 4.2k commands from your repository!! The project I'm working can be accessible at kommandr.com and feedback will be much appreciated. Thanks! 7/10/2018, 9:21:05 AM - agnivade (Agniva De Sarker): Thanks, this looks very similar to index.json for our node client. 7/10/2018, 10:07:38 AM - ediardo (Eddie Ramirez): @agnivade Yes, I just checked the source code and looks very similar as the one I created. I hope it can be useful to you guys in the future. :) 7/10/2018, 8:12:26 PM - sbrl (Starbeamrainbowlabs): So it's kinda like an aggregator? 7/10/2018, 8:12:28 PM - sbrl (Starbeamrainbowlabs): Cool 7/10/2018, 8:13:04 PM - sbrl (Starbeamrainbowlabs): Suggestion: Set the website of the repository to the web address. 7/10/2018, 8:14:28 PM - sbrl (Starbeamrainbowlabs): [![Selection_032.png](https://files.gitter.im/tldr-pages/tldr/qyI6/thumb/Selection_032.png)](https://files.gitter.im/tldr-pages/tldr/qyI6/Selection_032.png) 7/10/2018, 8:15:11 PM - sbrl (Starbeamrainbowlabs): Click the edit button, and then change the website address. This allows people to check out a demo of your code if they land at the repository, @ediardo 7/10/2018, 9:10:13 PM - ediardo (Eddie Ramirez): It looks like an aggregator right now, we have some plans for it 7/10/2018, 9:12:26 PM - ediardo (Eddie Ramirez): But all depends on how users find it useful, this is an open source project too and developed on our spare time. We'll see how it goes from now, it's been a very good learning experience though. On this blogpost I explained what what it is and could be 7/10/2018, 9:13:21 PM - ediardo (Eddie Ramirez): https://medium.com/@ediardo/first-step-towards-a-more-social-and-smart-command-library-fb27dccb7e71 7/10/2018, 9:13:27 PM - ediardo (Eddie Ramirez): Thanks @sbrl 7/10/2018, 9:17:13 PM - sbrl (Starbeamrainbowlabs): Cool! Open-source is a great environment in which to learn 😃 7/10/2018, 9:17:44 PM - sbrl (Starbeamrainbowlabs): What does `MvP` in your blog post mean though? 7/10/2018, 9:21:57 PM - ediardo (Eddie Ramirez): It's a word that people from marketing like: minimum viable product 7/10/2018, 9:29:01 PM - sbrl (Starbeamrainbowlabs): Ah, ok! I'm rather inexperienced in those things 😛 Perhaps in future posts you could consider writing out the full version at first, with the abbreviation in brackets. For example: `The minimum viable product (MvP) will be ready on Tuesday. The MvP is currently on-track for the projected release date` 7/10/2018, 10:22:39 PM - ediardo (Eddie Ramirez): +1, easy to forget about these little details that do matter 7/10/2018, 10:22:48 PM - ediardo (Eddie Ramirez): Thank you guys 7/10/2018, 10:30:49 PM - sbrl (Starbeamrainbowlabs): No problem! :-) 1/14/2023, 3:17:44 PM - gpenghe (Penghe Geng) joined the room 7/12/2018, 12:48:16 AM - gpenghe (Penghe Geng): Currently tldr will refresh the cache every time it doesn't recognize the command. Even you run tldr several times in a row. Do we think this is something that should be fixed? 7/12/2018, 12:50:41 AM - gpenghe (Penghe Geng): Before I realize I can install tldr's bash auto-completion, I tried a lot of times to see if tldr supports a specific command. And it incurs refreshing each time. 7/12/2018, 1:27:34 AM - sbrl (Starbeamrainbowlabs): Hey, @gpenghe! What client are you using? 7/12/2018, 1:27:50 AM - gpenghe (Penghe Geng): the official node one 7/12/2018, 1:29:58 AM - sbrl (Starbeamrainbowlabs): Ah, ok. Could you open an issue against [it's repository](https://github.com/tldr-pages/tldr-node-client) please? 7/12/2018, 1:55:10 AM - gpenghe (Penghe Geng): Submitted: #225 7/12/2018, 1:56:04 AM - gpenghe (Penghe Geng): Sorry. I realized it belongs to another chat room... 7/12/2018, 1:57:14 AM - gpenghe (Penghe Geng): mmm, which doesn't seem to exist (for node-client) 7/12/2018, 2:36:07 AM - sbrl (Starbeamrainbowlabs): This chat room is fine, as it's for general tldr-pages org stuff 7/12/2018, 2:36:15 AM - sbrl (Starbeamrainbowlabs): of which the node client is a part IIRC 7/12/2018, 2:36:59 AM - sbrl (Starbeamrainbowlabs): For reference, you opened tldr-pages/tldr-node-client#225 7/22/2018, 7:15:59 PM - gpenghe (Penghe Geng): I tried to run `npm run test`, but the `render.spec.js` won't pass. First issue I found is that the test reads my `$HOME/.tldrrc` which causes some problem. (Should a unittest be insulated from external environment?) After fixing that, it still doesn't pass. In line 19 `text.should.startWith('\n');`, the text is a string that does start with "\n", but it doesn't have a `should` property. What's happening? Anybody able to run `npm run test` successfully? 7/24/2018, 1:17:00 AM - gpenghe (Penghe Geng): The test above is on Windows. Then I changed to Ubuntu 16.04. The render tests still don't pass, but it's good after I deleted my ~/.tldrrc 7/24/2018, 1:27:02 AM - sbrl (Starbeamrainbowlabs): Hey, thanks for the message! Is this related to your earlier issue? 7/24/2018, 1:27:12 AM - sbrl (Starbeamrainbowlabs): If so, then a comment on that issue would probably be appropriate. 7/24/2018, 1:27:22 AM - sbrl (Starbeamrainbowlabs): If not, then I would suggest opening another issue. 7/24/2018, 1:27:38 AM - sbrl (Starbeamrainbowlabs): @agnivade, can you advise? 7/24/2018, 1:28:15 AM - gpenghe (Penghe Geng): I haven't submitted an issue for this one yet. 7/24/2018, 1:30:41 AM - gpenghe (Penghe Geng): I am still trying to understand the causes of the problem. I say causes since it appears there are multiple. At least, the unit test render.spec.js shouldn't be influenced by $HOME/.tldrrc, which probably means we need to hardcode `config.get().themes` in `beforeEach()`. 7/24/2018, 1:34:39 AM - sbrl (Starbeamrainbowlabs): ....I see. i'm not well-versing in the node client for tldr-pages, so I'd recommend contacting either @agnivade or @rubenvereecken about it. 7/24/2018, 2:45:04 AM - gpenghe (Penghe Geng): https://github.com/tldr-pages/tldr-node-client/issues/229 submitted. 7/24/2018, 3:36:37 AM - sbrl (Starbeamrainbowlabs): Thanks, @gpenghe! @agnivade will probably take a look when they next have time. 7/26/2018, 2:15:44 PM - agnivade (Agniva De Sarker): Thanks. I need to find some time to look at the PR. A quick glance looks okay. 7/27/2018, 11:55:37 AM - agnivade (Agniva De Sarker): What is this new blue border thing around github comments now ? I am unable to find any logic behind it 7/27/2018, 1:28:46 PM - waldyrious (Waldir Pimenta): Seems to be a marker for the linked comment if there's an anchor in the URL (e.g. `#issuecomment-1234567890`) 7/27/2018, 2:02:26 PM - sbrl (Starbeamrainbowlabs): Do you have an example? 7/27/2018, 2:08:46 PM - agnivade (Agniva De Sarker): Ah that's right ! Thanks @waldyrious 7/27/2018, 2:08:52 PM - agnivade (Agniva De Sarker): example -https://github.com/golang/go/issues/26627#issuecomment-408350313 7/27/2018, 2:17:47 PM - waldyrious (Waldir Pimenta): glad the mystery's solved :) 7/27/2018, 2:56:07 PM - sbrl (Starbeamrainbowlabs): Ah, I see! Very cool. I wonder if GitHub will update it further to allow you to follow the link in reverse? 7/27/2018, 3:39:52 PM - waldyrious (Waldir Pimenta): What do you mean, in reverse? 7/27/2018, 3:53:15 PM - sbrl (Starbeamrainbowlabs): i.e. click to see what is referencing it 7/27/2018, 4:02:48 PM - waldyrious (Waldir Pimenta): That's a problem as old as the internet :) 7/27/2018, 4:03:43 PM - waldyrious (Waldir Pimenta): Have you heard of Ted Nelson's Project Xanadu? 7/27/2018, 4:06:23 PM - sbrl (Starbeamrainbowlabs): Nope 😛 7/27/2018, 4:28:38 PM - waldyrious (Waldir Pimenta): It was a project similar to Tim Berner Lee's WWW, to implement the hypertext system, but more ambitious 7/27/2018, 4:29:08 PM - waldyrious (Waldir Pimenta): eventually it didn't come to fruition in time and the WWW (with unidirectional hyperlinks) became the standard 7/27/2018, 4:29:26 PM - waldyrious (Waldir Pimenta): but one of the features of Xanadu was that links would be bidirectional 7/27/2018, 4:29:44 PM - waldyrious (Waldir Pimenta): (Rule 7 in https://en.wikipedia.org/wiki/Project_Xanadu#Original_17_rules) 7/27/2018, 4:30:28 PM - waldyrious (Waldir Pimenta): It had other very interesting properties, like the ability to transclude sections of a page (rather than entire pages like we can to with iframes in html) 7/27/2018, 4:31:09 PM - sbrl (Starbeamrainbowlabs): Ah, cool! 😃 7/27/2018, 4:31:28 PM - waldyrious (Waldir Pimenta): Some subsystems ended up implementing these properties -- e.g. some blogging platforms had this pingback system, and google's main value was precisely in having built the graph of links among web pages -- so they could know who linked to where 7/27/2018, 4:31:32 PM - sbrl (Starbeamrainbowlabs): So like "What links here" on a wiki 7/27/2018, 4:31:45 PM - waldyrious (Waldir Pimenta): yep, exactly, I was going to mention mediawiki 7/27/2018, 4:32:16 PM - waldyrious (Waldir Pimenta): they also have a more advanced transclusion system that can receive parameters (i.e. templates) 7/27/2018, 4:32:47 PM - sbrl (Starbeamrainbowlabs): Indeed! 7/27/2018, 4:32:50 PM - waldyrious (Waldir Pimenta): so it is possible to do this but only by implementing the tech in-house, while the ideal would be to have this feature baked into the web itself 7/27/2018, 4:33:09 PM - sbrl (Starbeamrainbowlabs): Ah 7/27/2018, 4:33:54 PM - sbrl (Starbeamrainbowlabs): I've implemented a transclusion system like that before - but not a what links here yet 7/27/2018, 4:33:58 PM - sbrl (Starbeamrainbowlabs): that's harder 😛 7/27/2018, 4:34:21 PM - waldyrious (Waldir Pimenta): yeah, the graph edges implement N-to-N structures 7/27/2018, 4:34:37 PM - sbrl (Starbeamrainbowlabs): Yep 7/27/2018, 4:35:11 PM - waldyrious (Waldir Pimenta): But I guess with graph databases it might be easier to experiment with now 7/27/2018, 4:35:30 PM - waldyrious (Waldir Pimenta): not sure how to make the database distributed though 7/27/2018, 4:36:00 PM - waldyrious (Waldir Pimenta): the www is sort of a linked list where each node is self-contained in relation to where it links to 7/27/2018, 4:36:27 PM - waldyrious (Waldir Pimenta): but traversing the links backward would require some sort of search, I'm afraid 7/27/2018, 4:36:51 PM - waldyrious (Waldir Pimenta): I mean otherwise if I link to your page, your server would have to detect that and add a backlink to mine (if we wanted to allow going back from your page using information contained in that node alone) 7/27/2018, 4:37:00 PM - waldyrious (Waldir Pimenta): As I said, it's an old problem :) 7/27/2018, 4:38:08 PM - sbrl (Starbeamrainbowlabs): Yeah 1/14/2023, 3:18:10 PM - idleberg (Jan T. Sott) joined the room 7/31/2018, 5:58:27 PM - idleberg (Jan T. Sott): hi 7/31/2018, 11:44:20 PM - sbrl (Starbeamrainbowlabs): Hey there, @idleberg! 8/7/2018, 2:18:13 PM - sbrl (Starbeamrainbowlabs): Hey, @waldyrious! Thanks for the invite to Handshake. What is it? 8/7/2018, 2:19:16 PM - waldyrious (Waldir Pimenta): Hi. It seems to be a decentralized DNS 8/7/2018, 2:20:23 PM - waldyrious (Waldir Pimenta): they are building the registry a blockchain with an associated currency/token, which is to be used to buy domains and pay for the people who run the routing nodes 8/7/2018, 2:21:07 PM - sbrl (Starbeamrainbowlabs): Ah, I see! Cool. I'll have to check it out then, since you've been kind enough to provide me with an invite :-) 8/7/2018, 2:21:13 PM - waldyrious (Waldir Pimenta): I'm not 100% sure it's the best way to decentralize DNS, but they are distributing a large portion of the initial tokens to FOSS developers, so I thought I'd forward them to a few I know of 😉 8/7/2018, 2:21:17 PM - waldyrious (Waldir Pimenta): just in case it catches on 8/7/2018, 2:21:36 PM - waldyrious (Waldir Pimenta): Nah, you could have registered by yourself, it's not closed or anything 8/7/2018, 2:22:23 PM - waldyrious (Waldir Pimenta): you need to verify your account either by linking it to a Freenode IRC account, or a github page, or a PGP email IIRC 8/7/2018, 2:22:28 PM - waldyrious (Waldir Pimenta): (or all of them) 8/7/2018, 2:23:46 PM - sbrl (Starbeamrainbowlabs): Ah, I see! I have a GPG key (via keybase!) and a GitHub account, so that should work. 8/7/2018, 2:24:55 PM - waldyrious (Waldir Pimenta): sure :) the github account alone would suffice, but it can take a couple days since they seem to have some manual validation process (probably just to make sure it's not a spam/unused account) 8/7/2018, 2:25:24 PM - sbrl (Starbeamrainbowlabs): Sure 8/7/2018, 2:29:22 PM - sbrl (Starbeamrainbowlabs): When signing up, they ask for my name. DO they want my _real_ name, or my pseudonym? 8/7/2018, 2:29:50 PM - waldyrious (Waldir Pimenta): I don't think anyone is checking with ID documents or anything 8/7/2018, 2:30:03 PM - waldyrious (Waldir Pimenta): I'd use whatever you're comfortable with 8/7/2018, 2:30:23 PM - sbrl (Starbeamrainbowlabs): I see. Also, a line in their T&Cs makes me rather uncomfortable: > THE PARTIES HEREBY WAIVE THEIR CONSTITUTIONAL AND STATUTORY RIGHTS TO GO TO COURT AND HAVE A TRIAL IN FRONT OF A JUDGE OR A JURY 8/7/2018, 2:30:43 PM - sbrl (Starbeamrainbowlabs): I live in the UK, and this is a US company. I don't think they've the right to include that? 8/7/2018, 2:31:58 PM - waldyrious (Waldir Pimenta): You're much more careful with these things than I am :) 8/7/2018, 2:32:20 PM - waldyrious (Waldir Pimenta): I am not endorsing them or encouraging you to sign up, I just thought the concept was potentially interesting 8/7/2018, 2:32:57 PM - waldyrious (Waldir Pimenta): And they asked me to mention a few people (which I could skip doing, so it's not even a big deal) during the sign up process 8/7/2018, 2:33:00 PM - sbrl (Starbeamrainbowlabs): Indeed! It is most interesting. I think that they just haven't considered international users when structuring their T&Cs and Privacy Policy 8/7/2018, 2:33:03 PM - waldyrious (Waldir Pimenta): probably just to spread the word 8/7/2018, 2:33:08 PM - sbrl (Starbeamrainbowlabs): Yeah 8/7/2018, 2:33:49 PM - waldyrious (Waldir Pimenta): I'd bet they have used some template document for the T&C 8/7/2018, 2:33:56 PM - waldyrious (Waldir Pimenta): with minor adjustments 8/7/2018, 2:36:11 PM - sbrl (Starbeamrainbowlabs): Yeah 8/7/2018, 2:36:21 PM - sbrl (Starbeamrainbowlabs): I'm drafting an email to send to them to ask 8/7/2018, 2:36:42 PM - waldyrious (Waldir Pimenta): I mean, most people don't even read those, let alone write them. Same with bylaws, contracts, etc. Everybody tends to delegate to existing templates that offer some guarantee of covering most bases, rather than composing a document fully adjusted to ones's specific needs 8/7/2018, 2:36:49 PM - waldyrious (Waldir Pimenta): That's great of you :) 8/7/2018, 2:38:21 PM - waldyrious (Waldir Pimenta): Last time I signed a work contract I almost went back to ask them to fix some details that made little sense in the context of that company, but eventually I decided against it, as they would probably consider that being pedantic and I didn't want to start off with the wrong foot 8/7/2018, 2:39:07 PM - sbrl (Starbeamrainbowlabs): Heh - I don't usually read these things either - I'm just being particularly careful because they used the word "blockchain" in their explanation of what they do - which makes me automatically suspicious 😛 8/7/2018, 2:39:18 PM - waldyrious (Waldir Pimenta): Hahahaha 8/7/2018, 2:39:24 PM - waldyrious (Waldir Pimenta): Fair enough :) 8/7/2018, 2:44:05 PM - sbrl (Starbeamrainbowlabs): Their fault for having a dense & unreadable T&Cs and Privacy Policy 😛 8/7/2018, 2:44:27 PM - waldyrious (Waldir Pimenta): Agreed :+1: 1/14/2023, 3:18:27 PM - Asternitix_gitlab (Asternitix) joined the room 8/11/2018, 4:37:06 AM - Asternitix_gitlab (Asternitix): hello world 8/11/2018, 4:37:28 AM - sbrl (Starbeamrainbowlabs): Hey there, @Asternitix_gitlab! 😃 8/11/2018, 4:37:36 AM - Asternitix_gitlab (Asternitix): 🐔 🥚 8/11/2018, 4:38:03 AM - Asternitix_gitlab (Asternitix): that's awesome 8/11/2018, 4:38:27 AM - Asternitix_gitlab (Asternitix): @everyone does not ping everyone. that's amazing. 8/11/2018, 4:39:40 AM - sbrl (Starbeamrainbowlabs): Welcome to tldr-pages. 8/13/2018, 10:07:00 AM - agnivade (Agniva De Sarker): @/all - I have just reverted a PR on chsh. The `-l` option wasn't there on all linux platforms. So it shouldn't be there on the page. Just FYI. 8/17/2018, 12:06:42 AM - idleberg (Jan T. Sott): has anybody managed to use the methods of `tldr-node-client` in a project? 8/17/2018, 12:07:15 AM - idleberg (Jan T. Sott): i've imported `commands()`, but keep running into `ENOENT: no such file or directory, open '/config.json'` 8/17/2018, 1:38:33 AM - sbrl (Starbeamrainbowlabs): Hey! It might be helpful if we could see your code. @agnivade is the person to talk to 8/17/2018, 2:04:01 PM - sbrl (Starbeamrainbowlabs): @idleberg 8/17/2018, 10:50:59 PM - agnivade (Agniva De Sarker): The config.json is the default theme which is packaged along with it. 8/17/2018, 10:51:12 PM - agnivade (Agniva De Sarker): You need the file in the root folder. 8/17/2018, 10:51:47 PM - agnivade (Agniva De Sarker): I haven't tested it by importing the node-client as a library in some other project. So you might indeed be the first one. 8/19/2018, 1:39:30 AM - sbrl (Starbeamrainbowlabs): Just got a reply from their support team at Handshake...... and they've "forwarded my concerns" on to someone else, @waldyrious 😛 8/20/2018, 3:48:00 PM - waldyrious (Waldir Pimenta): ....suuure 8/20/2018, 3:50:00 PM - sbrl (Starbeamrainbowlabs): lol 8/23/2018, 12:49:53 PM - agnivade (Agniva De Sarker): tldr.sh is hijacked. 8/23/2018, 12:50:08 PM - agnivade (Agniva De Sarker): tldr-node-client updates are failing because they point to http paths. 8/23/2018, 12:50:19 PM - agnivade (Agniva De Sarker): I have removed the CNAME file from tldr-pages.github.io repo for now. 8/23/2018, 12:50:29 PM - agnivade (Agniva De Sarker): It will take some time for DNS changes to expire. 8/23/2018, 12:50:37 PM - agnivade (Agniva De Sarker): I am reaching out to @ostera 8/23/2018, 1:00:11 PM - owenvoke (Owen Voke): :+1: 8/23/2018, 2:00:06 PM - agnivade (Agniva De Sarker): Issue is resolved now. 8/23/2018, 2:00:15 PM - agnivade (Agniva De Sarker): I will wait for a day to put back the CNAME file. 8/23/2018, 2:20:21 PM - sbrl (Starbeamrainbowlabs): Oh dear! That's unfortunate. It's hosted with GH pages, right? 8/23/2018, 4:41:44 PM - owenvoke (Owen Voke): Yeah. :+1: 8/23/2018, 4:59:22 PM - sbrl (Starbeamrainbowlabs): Hrm. I wonder how it got hijacked 😕 8/23/2018, 5:02:04 PM - owenvoke (Owen Voke): Domain probably expired? 8/23/2018, 5:43:37 PM - sbrl (Starbeamrainbowlabs): possibly. 8/23/2018, 5:44:04 PM - sbrl (Starbeamrainbowlabs): Perhaps there should be a tldr-pages account or something that the owners of the tldr-pages repository have access to? 8/23/2018, 8:28:35 PM - agnivade (Agniva De Sarker): Yes, it got expired. It was bought by @ostera and we didn't think much. I will ask if more than one person can have access. 8/23/2018, 9:00:44 PM - sbrl (Starbeamrainbowlabs): Ah 8/23/2018, 9:01:02 PM - sbrl (Starbeamrainbowlabs): Cool 8/25/2018, 1:28:24 AM - sbrl (Starbeamrainbowlabs): Attempting the big 16.04 -> 18.04 upgrade on my server - tldr-bot might break for a moment :-) 8/25/2018, 3:16:21 AM - sbrl (Starbeamrainbowlabs): All done! Let me know if it's not working right. 8/25/2018, 3:44:03 AM - owenvoke (Owen Voke): Great. :+1: Well done. 😄 8/25/2018, 4:03:15 AM - sbrl (Starbeamrainbowlabs): Thanks! _Almost_ locked myself out through an `/etc/ssh/sshd_config` error, but managed to catch the warning message and fixed it just in time 😛 8/25/2018, 9:31:51 AM - agnivade (Agniva De Sarker): Nice :) 8/25/2018, 9:32:07 AM - agnivade (Agniva De Sarker): I have been punting the upgrade on my laptop .. 8/25/2018, 9:32:13 AM - agnivade (Agniva De Sarker): need to do it sometime .. 8/26/2018, 2:10:20 AM - sbrl (Starbeamrainbowlabs): It's quite a straightforward one actually 8/26/2018, 2:10:29 AM - sbrl (Starbeamrainbowlabs): As far as Ubuntu upgrades go 8/26/2018, 2:10:53 AM - sbrl (Starbeamrainbowlabs): though don't go and lock yourself out by not updating your SSH config file as I almost did 😛 8/26/2018, 11:48:25 AM - agnivade (Agniva De Sarker): Did some long time pending stuff. 8/26/2018, 11:48:44 AM - agnivade (Agniva De Sarker): Moved @waldyrious to former maintainer (He has been asking that himself for some time 😛) 8/26/2018, 11:49:42 AM - agnivade (Agniva De Sarker): Invited @pxgamer as an org member. I think we can all agree he has been very actively participating in all the reviews along with a healthy load of PRs. So this was a long time due. 8/26/2018, 11:49:50 AM - agnivade (Agniva De Sarker): Welcome aboard @pxgamer ! 8/26/2018, 11:50:22 AM - agnivade (Agniva De Sarker): (P.S. By mistake I created the issue to move to org owner instead of member, corrected it now) 8/26/2018, 2:19:26 PM - sbrl (Starbeamrainbowlabs): Cool, thanks @agnivade! Soundss good to me 😃 8/26/2018, 2:19:38 PM - sbrl (Starbeamrainbowlabs): Congrats, @pxgamer 😃 8/26/2018, 2:40:54 PM - owenvoke (Owen Voke): Thank you. 🎉 I've now joined. 😄 8/26/2018, 3:01:26 PM - sbrl (Starbeamrainbowlabs): 🎆 8/27/2018, 4:38:16 PM - waldyrious (Waldir Pimenta): I'm glad you found your way to the project, @pxgamer! It can only thrive as long as people continue to join and take ownership in practice as you did :) the role change is just a recognition of what was already true in the ground. Cheers! 1/14/2023, 3:18:51 PM - AayuStark007 (Aayush Gupta) joined the room 9/5/2018, 11:57:02 AM - AayuStark007 (Aayush Gupta): Hi, I recently installed tldr using npm and I'm getting an Update Error when trying to run `tldr --update` Here are the steps taken to install: `sudo apt install nodejs npm` `sudo npm install -g tldr` 9/5/2018, 12:00:34 PM - AayuStark007 (Aayush Gupta): When running `tldr --update` I get the following error: ``` UpdatingError: Cannot update from https://tldr-pages.github.io/assets/tldr.zip at Extract.extractor.on (/usr/local/lib/node_modules/tldr/lib/remote.js:33:14) at emitOne (events.js:121:20) at Extract.emit (events.js:211:7) at Parse. (/usr/local/lib/node_modules/tldr/node_modules/node-unzip-2/lib/extract.js:28:10) at emitOne (events.js:116:13) at Parse.emit (events.js:211:7) at /usr/local/lib/node_modules/tldr/node_modules/node-unzip-2/lib/parse.js:64:12 at runCallback (timers.js:794:20) at tryOnImmediate (timers.js:752:5) at processImmediate [as _immediateCallback] (timers.js:729:5) ``` 9/5/2018, 12:03:20 PM - AayuStark007 (Aayush Gupta): Node and npm version: ``` nodejs -v v8.10.0 npm -v 3.5.2 ``` 9/5/2018, 1:57:52 PM - waldyrious (Waldir Pimenta): Hey @AayuStark007 -- welcome! @agnivade is the node client guy :) he should be able to help you once he's around. 9/5/2018, 2:51:59 PM - sbrl (Starbeamrainbowlabs): Hey! Yeah, @agnivade is the main person to ask. I notice though that you're not running the latest version of Node.JS though, according to the [Node.JS Website](https://nodejs.org/). Perhaps you could try updating? 9/5/2018, 3:02:38 PM - waldyrious (Waldir Pimenta): As someone who barely uses node, I highly recommend `nvm` to install specific node versions and easily swap them 9/5/2018, 3:02:59 PM - waldyrious (Waldir Pimenta): https://github.com/creationix/nvm#installation 9/6/2018, 7:23:31 PM - sbrl (Starbeamrainbowlabs): Perhaps you could try [opening an issue](https://github.com/tldr-pages/tldr-node-client/issues/new) on the node client repository, @AayuStark007? 9/6/2018, 7:25:59 PM - sbrl (Starbeamrainbowlabs): And hey @agnivade, @waldyrious, and @pxgamer. I've seen @ mfrw around a bit. What level are they in terms on COMMUNITY-ROLES.md, and should we invite them to the next one? 9/6/2018, 7:43:59 PM - waldyrious (Waldir Pimenta): if COMMUNITY-ROLES doesn't make that clear, it is failing at its job :) 9/6/2018, 7:44:47 PM - waldyrious (Waldir Pimenta): Doesn't this work? > Specifically: once a contributor has had 5 non-trivial pull requests merged on a repository under the tldr-pages organization, they should be invited to become a collaborator in that repository. 9/6/2018, 7:45:34 PM - sbrl (Starbeamrainbowlabs): Ah, I think I see. I'm a bit confused as to what role @ mfrw currently has - hence the question 9/6/2018, 7:46:56 PM - waldyrious (Waldir Pimenta): Any role change should be tracked in an issue, so a search for issues with his username in the title should suffice, right? 9/6/2018, 7:47:28 PM - waldyrious (Waldir Pimenta): But AFAIK he hasn't been proposed for a role change before 9/6/2018, 7:48:39 PM - sbrl (Starbeamrainbowlabs): I've just figured out how to get a list of PRs opened by a person. As far as I can tell, @ mfrw has 4 emrged and 1 open, so will be eligible once #2268 is merged. 9/6/2018, 7:48:54 PM - waldyrious (Waldir Pimenta): Alternatively, collaborators are visible at https://github.com/tldr-pages/tldr/settings/collaboration, and org members and owners are visible at https://github.com/orgs/tldr-pages/people 9/6/2018, 7:49:05 PM - waldyrious (Waldir Pimenta): great :) 9/6/2018, 7:50:20 PM - waldyrious (Waldir Pimenta): and btw this is a great candidate for automation (identifying regulars who meet the criteria for a role change), because manual checking can only get us so far. Does this sound like something tldr-bot could take on? 9/6/2018, 7:51:45 PM - sbrl (Starbeamrainbowlabs): Erm I'd ask @agnivade that - I think he wrote the bot. Probably though! 9/6/2018, 7:51:58 PM - sbrl (Starbeamrainbowlabs): We should certainly open an issue about it if we haven't already. 9/6/2018, 7:52:26 PM - sbrl (Starbeamrainbowlabs): And thanks for the links! 9/6/2018, 7:52:30 PM - waldyrious (Waldir Pimenta): Would you mind doing that? I'm juggling several tasks right now :) 9/6/2018, 7:53:09 PM - waldyrious (Waldir Pimenta): (the links are all in COMMUNITY-ROLES.md, but please edit it if you think they should be made more prominent) 9/6/2018, 8:00:13 PM - sbrl (Starbeamrainbowlabs): Ah - I must have missed them in there. And yeah, creating an issue now. 9/6/2018, 8:00:34 PM - waldyrious (Waldir Pimenta): Thank you :) 9/6/2018, 8:02:37 PM - sbrl (Starbeamrainbowlabs): Opened #2304 1/14/2023, 3:19:01 PM - mfrw (Muhammad Falak R Wani) joined the room 9/7/2018, 12:23:03 AM - mfrw (Muhammad Falak R Wani): > I've just figured out how to get a list of PRs opened by a person. As far as I can tell, @ mfrw has 4 emrged and 1 open, so will be eligible once #2268 is merged. I think it should be more than that, I have modified my full name :) 9/7/2018, 2:05:41 AM - sbrl (Starbeamrainbowlabs): Hey @mfrw! With #2304 you do qualify for collaborator status.To that end, I've opened #2306. 9/7/2018, 9:14:50 AM - mfrw (Muhammad Falak R Wani): @sbrl awsome... thanks for the opportunity :) 9/7/2018, 1:12:25 PM - waldyrious (Waldir Pimenta): @mfrw on the contrary, you took the first step of donating your time and energy to this project :) we're simply moving out of the way 😉 9/7/2018, 1:15:43 PM - waldyrious (Waldir Pimenta): We don't believe it's in the best interests of a vibrant community to have leaders making the shots and "giving out opportunities" -- we're all here to serve the project one way or the other, and maintenance work is just another way to serve :) 9/7/2018, 1:15:47 PM - waldyrious (Waldir Pimenta): hopefully we can be a blip in the efforts to reverse the traditional command structure of organizations, at least in the open source world 9/7/2018, 1:16:33 PM - waldyrious (Waldir Pimenta): do take a read of the GOVERNANCE.md and COMMUNITY-ROLES.md documents if you haven't already :) 9/7/2018, 1:42:56 PM - agnivade (Agniva De Sarker): @AayuStark007 - Please open an issue if the problem persists. 9/7/2018, 8:43:19 PM - mfrw (Muhammad Falak R Wani): I had an idea, where should we discuss it, here or should i open a github issue ? 'Since Hactober-Fest is almost one month away, why don't we start preping our repo for first timers, by having some easy work which they could do, while they also learning how to contribute and get some free (probably) T-Shirts and stickers' PS: I too started with the hacktober fest last year. 9/7/2018, 8:47:12 PM - waldyrious (Waldir Pimenta): A good rule of thumb is if the discussion involves a lot of back and forth before consolidating; another is whether it would be relevant to have the contents of the discussion easily accessible in the future (gitter archives are public, but more cumbersome to navigate than github issues) 9/7/2018, 8:47:48 PM - waldyrious (Waldir Pimenta): Discussing this year's Hactoberfest makes sense to me as an issue 9/7/2018, 8:48:16 PM - waldyrious (Waldir Pimenta): Also, glad to hear that's where you got started! It's a great idea indeed. 9/7/2018, 8:49:29 PM - sbrl (Starbeamrainbowlabs): Indeed! Participating in hacktoberfest sounds good to me. Definitely go ahead and open an issue, @mfrw! 9/14/2018, 8:48:38 PM - sbrl (Starbeamrainbowlabs): We've got rather a lot of new page requests - it's getting somewhat overwhelming navigating the issue list. 9/14/2018, 8:57:33 PM - waldyrious (Waldir Pimenta): @sbrl do you mean there has been a recent increase in the rate at which issues are created? Or do you mean the accumulated total has gradually grown large? 9/14/2018, 8:57:46 PM - sbrl (Starbeamrainbowlabs): An increase in the rate 9/14/2018, 8:58:06 PM - waldyrious (Waldir Pimenta): Hmm, I didn't notice that (though I haven't been following the repo as closely as I used to) 9/14/2018, 8:58:21 PM - sbrl (Starbeamrainbowlabs): I think most of them have been opened by @mfrw 9/14/2018, 8:58:28 PM - waldyrious (Waldir Pimenta): But don't the search operators help with navigating the issue list? 9/14/2018, 8:58:50 PM - sbrl (Starbeamrainbowlabs): Erm not really 9/14/2018, 8:58:53 PM - waldyrious (Waldir Pimenta): As long as they're properly tagged (and titled), I don't see any immediate problems, but I might be missing something 9/14/2018, 8:59:12 PM - sbrl (Starbeamrainbowlabs): I think I might be missing something too 😛 9/14/2018, 9:00:01 PM - waldyrious (Waldir Pimenta): What kind of thing would you like to do that has been made harder by the growth in issues? 9/14/2018, 9:02:28 PM - sbrl (Starbeamrainbowlabs): It's just that all the recent page requests are drowning out other issues, such as #2304, #2266, and #2213. It's more of an information processing issue I have 9/14/2018, 9:02:44 PM - sbrl (Starbeamrainbowlabs): *other issues that aren't page requests 9/14/2018, 9:06:24 PM - waldyrious (Waldir Pimenta): I see. I'm not sure if negative search queries are possible -- that would be ideal for this situation I believe 9/14/2018, 9:06:51 PM - waldyrious (Waldir Pimenta): either `-label:page-request` or `-author:mfrw` (or both) 9/14/2018, 9:07:07 PM - waldyrious (Waldir Pimenta): Let me see if I can find anything 9/14/2018, 9:07:29 PM - waldyrious (Waldir Pimenta): (for the record I'm absolutely sympathetic to information processing woes -- I suffer greatly from this myself) 9/14/2018, 9:07:54 PM - sbrl (Starbeamrainbowlabs): Ah, thanks so much for understanding 😃 9/14/2018, 9:09:27 PM - waldyrious (Waldir Pimenta): Looks like negated search operators are possible! https://help.github.com/articles/searching-issues-and-pull-requests/#search-by-label 9/14/2018, 9:10:09 PM - waldyrious (Waldir Pimenta): Does this help? https://github.com/tldr-pages/tldr/issues?utf8=%E2%9C%93&q=is%3Aissue+-label%3A%22new+command%22 9/14/2018, 9:15:49 PM - sbrl (Starbeamrainbowlabs): Ah, it does thanks! 😃 Is there any way to set that as the default? 9/14/2018, 9:45:14 PM - waldyrious (Waldir Pimenta): Hmmm, you mean for yourself or for anyone visiting the repo? 9/14/2018, 9:45:27 PM - waldyrious (Waldir Pimenta): Well, I guess it's irrelevant because AFAIK it's not possible natively 9/14/2018, 9:45:55 PM - waldyrious (Waldir Pimenta): If I were you I'd bookmark that URL in my browser and use it instead of navigating to the issues tab 9/14/2018, 9:46:19 PM - waldyrious (Waldir Pimenta): That's what I do e.g. for complex gmail queries, I have a bunch of them bookmarked for convenience 9/14/2018, 9:53:12 PM - sbrl (Starbeamrainbowlabs): Just for me :-) 9/14/2018, 9:53:23 PM - sbrl (Starbeamrainbowlabs): Good idea though, I'll add it to my bookmarks 9/14/2018, 10:50:59 PM - mfrw (Muhammad Falak R Wani): Hi people.... 9/14/2018, 10:51:34 PM - mfrw (Muhammad Falak R Wani): I think I got a little too carried away while creating issues. 9/14/2018, 10:52:10 PM - mfrw (Muhammad Falak R Wani): My aim is to atleast open 1 issue every day with a help wanted label. 9/14/2018, 10:52:28 PM - mfrw (Muhammad Falak R Wani): The plan is to eventually rename them to hactoberfest. 9/14/2018, 10:53:10 PM - mfrw (Muhammad Falak R Wani): If we do not get any help on those issue, I will eventually add pages for those. 9/15/2018, 1:49:55 PM - agnivade (Agniva De Sarker): 1 issue every day till the end of time ? 😱 9/15/2018, 1:50:32 PM - agnivade (Agniva De Sarker): how long do you plan to continue this ? 9/15/2018, 4:58:23 PM - mfrw (Muhammad Falak R Wani): Hahaha not till the end of time... Only till October. Recall hactoberfest :) 9/15/2018, 5:40:59 PM - sbrl (Starbeamrainbowlabs): I think that 30 is enough lol 😛 https://github.com/tldr-pages/tldr/issues?q=is%3Aissue+is%3Aopen+label%3A%22new+command%22 9/15/2018, 5:49:32 PM - mfrw (Muhammad Falak R Wani): Sure ... 30 looks enough :) 9/15/2018, 5:55:56 PM - sbrl (Starbeamrainbowlabs): :+1: 9/15/2018, 6:21:50 PM - agnivade (Agniva De Sarker): 😆 9/18/2018, 1:38:30 PM - agnivade (Agniva De Sarker): Hey @mfrw - we typically reserve putting backticks in the descriptions for other commands like `cp`, `rm`. This is because the client picks those up and shows a `See other: cp` section at the end. 9/18/2018, 1:39:01 PM - agnivade (Agniva De Sarker): Of course, there may be cases where `` is required. But in this case, I would rather say home directory. 9/18/2018, 1:39:10 PM - agnivade (Agniva De Sarker): This is regarding #2339 of course. 9/18/2018, 1:56:02 PM - owenvoke (Owen Voke): :+1: 9/19/2018, 12:55:45 AM - dbrgn (Danilo Bargen): Hi. Is it possible to create sub-rooms in this community for implementations? E.g. one for tealdeer (https://github.com/dbrgn/tealdeer)? 9/19/2018, 12:55:54 AM - dbrgn (Danilo Bargen): Doesn't really make sense to create a separate gitter community for that. 9/19/2018, 12:58:52 AM - sbrl (Starbeamrainbowlabs): Sounds like a good idea, @dbrgn? Perhaps a sub-room for discussing implementations of tldr would work for now? 9/19/2018, 12:59:23 AM - sbrl (Starbeamrainbowlabs): Not sure how to create rooms though - or even if I have permissions to do so (does it carry over from GH?) 9/19/2018, 3:32:57 AM - waldyrious (Waldir Pimenta): @sbrl IIRC the permissions do carry over from the github org 9/19/2018, 3:33:32 AM - waldyrious (Waldir Pimenta): The "Add a room" button on the bottom left should be where a new room can be created within the tldr community 9/19/2018, 4:00:59 AM - sbrl (Starbeamrainbowlabs): Ah, ok. I'll wait to see what others say first though :-) 9/19/2018, 5:01:27 AM - dbrgn (Danilo Bargen): > Perhaps a sub-room for discussing implementations of tldr would work for now? Hm, I'm not sure. I'd like to put that link to that room into the README. For me to be able to see discussions, the chat would have a high signal-to-noise ratio. I would not be interested in implementation discussion of the node client, for example, so separate rooms per implementation would be better I think. Of course I can also just create a separate community with its own room, if you don't want it in the tldr-pages community :) 9/19/2018, 9:18:16 AM - agnivade (Agniva De Sarker): I think this room is fine. Even for node client, people post and discuss bugs here. It is not _that_ high traffic. So you can point this room in your README. 9/19/2018, 1:39:43 PM - idleberg (Jan T. Sott): have you ever evaluated `write-good` and whether it makes sense to integrate it into `tldr-linter`? https://www.npmjs.com/package/write-good 9/19/2018, 8:52:15 PM - agnivade (Agniva De Sarker): Thanks, I have not. The tldr linter is a difficult package to change with lots of lex and yacc rules to parse and validate the pages. 9/19/2018, 8:52:30 PM - agnivade (Agniva De Sarker): There is already a rudimentary grammar check implemented 9/19/2018, 8:52:37 PM - agnivade (Agniva De Sarker): any PRs are most welcome. 9/20/2018, 2:05:37 AM - waldyrious (Waldir Pimenta): @dbrgn I agree with @agnivade that if even this "everything tldr-pages" room isn't that active, a room for a specific client might not be warranted. That said, IIRC gitter allows any repo to have an associated room (including activity feed integration as you can see in the sidebar in this room) 9/22/2018, 10:47:39 PM - psibi (Sibi Prabakaran): ANN: A new version of haskell client has been released with bug fixes. Changelog here: https://github.com/psibi/tldr-hs/blob/master/CHANGELOG.md#031 9/22/2018, 11:37:00 PM - sbrl (Starbeamrainbowlabs): :+1: 9/22/2018, 11:39:11 PM - sbrl (Starbeamrainbowlabs): (What does `ANN` mean though?) 9/22/2018, 11:39:51 PM - psibi (Sibi Prabakaran): Announcement :-) 9/22/2018, 11:50:28 PM - sbrl (Starbeamrainbowlabs): Ah :-) 10/1/2018, 9:57:36 AM - agnivade (Agniva De Sarker): I am going to submit some wabt (https://github.com/WebAssembly/wabt) commands for hacktoberfest ! 10/1/2018, 12:14:29 PM - sbrl (Starbeamrainbowlabs): Cool, @agnivade! I've always wanted to get into WebAssembly, but I've been waiting till browsers have actually implemented it. Any word on that at all? 10/1/2018, 12:34:10 PM - owenvoke (Owen Voke): :+1: I'm also really interested in WebAssembly. But haven't got into it yet, I'll have to take a look. 10/1/2018, 5:32:27 PM - agnivade (Agniva De Sarker): WebAssembly is great. I am giving a talk about it in our local Go meetup :) 10/1/2018, 5:32:34 PM - agnivade (Agniva De Sarker): Yes, all browsers now implement it. 10/1/2018, 5:32:58 PM - agnivade (Agniva De Sarker): Here is a cool demo - https://agniva.me/wasm/2018/06/18/shimmer-wasm.html 10/1/2018, 10:01:17 PM - mfrw (Muhammad Falak R Wani): @agnivade are you reffering to this meetup : https://www.meetup.com/Golang-Bangalore/ 10/1/2018, 10:03:39 PM - sbrl (Starbeamrainbowlabs): Awesome, @agnivade! I'll have to investigate it. Is there a master list of languages that can target wasm? 10/1/2018, 10:05:55 PM - mfrw (Muhammad Falak R Wani): @sbrl probably this may help: https://github.com/appcypher/awesome-wasm-langs 10/1/2018, 10:26:58 PM - agnivade (Agniva De Sarker): @mfrw - Yes :) 10/1/2018, 10:32:36 PM - mfrw (Muhammad Falak R Wani): cool .. are you presenting on 6th ? 10/1/2018, 10:32:38 PM - agnivade (Agniva De Sarker): @sbrl - Currently, C/C++ and Rust have the best support. 10/1/2018, 10:33:16 PM - agnivade (Agniva De Sarker): Go, C#, Java are a bit behind. Although I dont know much about C# and Java though .. 10/1/2018, 10:33:22 PM - agnivade (Agniva De Sarker): @mfrw - Yes 10/1/2018, 10:33:50 PM - mfrw (Muhammad Falak R Wani): @agnivade (y) 10/1/2018, 11:45:23 PM - sbrl (Starbeamrainbowlabs): I see - thanks, @agnivade. I know C/C++ (+flex+bison) but it's a bit of a pain. I don't know Rust, but as soon as I can actually install it I'd love to give it a go! 10/2/2018, 9:27:09 AM - agnivade (Agniva De Sarker): If you ever want to give Go a go 😄 , feel free to let me know. Would love to help. 10/23/2018, 2:19:57 AM - sbrl (Starbeamrainbowlabs): I didn't even know that GitHub was down today! Did we loose anything? 10/23/2018, 8:42:41 AM - mfrw (Muhammad Falak R Wani): @sbrl Ohh was it, I used it intermittenly. I don't think so we lost anything 10/23/2018, 5:47:02 PM - agnivade (Agniva De Sarker): nothing was lost. But the site was partially inaccessible throughout the day 10/23/2018, 5:47:10 PM - agnivade (Agniva De Sarker): see status.github.com. 10/23/2018, 5:47:16 PM - agnivade (Agniva De Sarker): an outage of around 24 hours 1/14/2023, 3:19:37 PM - rishitells (Rishabh Sharma) joined the room 10/23/2018, 8:42:14 PM - rishitells (Rishabh Sharma): Hi, can you tell me what are you guys using for highlighting the tldr outputs. On https://tldr.sh/ there is an example (https://tldr.sh/assets/img/screenshot.png) where the output of tldr (tldr tar) is colorful (red and green highlighting for commands and instructions). 10/23/2018, 11:37:08 PM - idleberg (Jan T. Sott): i guess it's the chalk module https://www.npmjs.com/package/chalk 10/24/2018, 9:13:28 AM - agnivade (Agniva De Sarker): correct 10/24/2018, 9:13:55 AM - agnivade (Agniva De Sarker): This is just for the node client though. 1/14/2023, 3:19:40 PM - guilhermeleobas (Guilherme Leobas) joined the room 10/24/2018, 6:31:34 PM - guilhermeleobas (Guilherme Leobas): Hi all, Can I send a PR adding more examples to a tool already present on TLDR? 10/24/2018, 6:32:43 PM - owenvoke (Owen Voke): Yes. :+1: 10/24/2018, 6:32:56 PM - guilhermeleobas (Guilherme Leobas): Thanks :) 10/24/2018, 8:37:10 PM - agnivade (Agniva De Sarker): Sure, but keep in mind that it is a tldr page. So we deliberately try to keep it minimal and have only useful examples for someone to get started on a command. 10/24/2018, 8:37:19 PM - agnivade (Agniva De Sarker): Also, we have a hard limit of 8 examples. 1/14/2023, 3:19:43 PM - satelliteoflove (Christopher Childress) joined the room 10/26/2018, 8:42:38 PM - satelliteoflove (Christopher Childress): Hi, all. I'm having trouble updating tldr after installing using npm. My company uses DPI and I'm pretty sure this is the problem. Is there a way to ignore certificate errors in the tldr update process, and if not what domain(s) does tldr contact to update its repository of docs? 10/26/2018, 8:49:59 PM - satelliteoflove (Christopher Childress): nm; I believe I've found a work-around 10/26/2018, 11:16:30 PM - sbrl (Starbeamrainbowlabs): Cool, @satelliteoflove! Glad you managed to solve the issue :-) 11/6/2018, 4:11:21 AM - sbrl (Starbeamrainbowlabs): Hey! Looks like @AnimiVulpis is eligible for contributor access! 11/6/2018, 4:11:53 AM - waldyrious (Waldir Pimenta): Woohoo! 👏 another one :) 11/6/2018, 4:13:26 AM - waldyrious (Waldir Pimenta): I'm hoping my recent updates to the documentation of the role changing process had at least something to do with you noticing that now 😃 11/6/2018, 4:13:58 AM - sbrl (Starbeamrainbowlabs): Yep 😛 11/6/2018, 4:14:23 AM - waldyrious (Waldir Pimenta): yay! 😊 11/6/2018, 4:14:40 AM - sbrl (Starbeamrainbowlabs): Also the fact that I've seen a bunch of their PRs around recently, so I thought I'd check on their status 11/6/2018, 4:14:54 AM - sbrl (Starbeamrainbowlabs): I think there's another one who qualifies too 11/6/2018, 4:15:24 AM - waldyrious (Waldir Pimenta): Great! The more the merrier. 11/6/2018, 4:23:10 AM - sbrl (Starbeamrainbowlabs): I've sent the invitation to @AnimiVulpis through the settings 11/6/2018, 4:23:51 AM - waldyrious (Waldir Pimenta): Did you create the issue first? It would be better for them to get that notification first, because it provides context. 11/6/2018, 4:24:25 AM - waldyrious (Waldir Pimenta): That said, if they do arrive more or less at the same time, it shouldn't make that much of a difference which one arrives first. 11/6/2018, 4:25:01 AM - sbrl (Starbeamrainbowlabs): Oops! I should do that 😛 11/6/2018, 4:25:19 AM - waldyrious (Waldir Pimenta): The docs failed once more 😢 11/6/2018, 4:28:51 AM - sbrl (Starbeamrainbowlabs): I think I just missed that bit and didn't read the whole file. 11/6/2018, 4:29:01 AM - sbrl (Starbeamrainbowlabs): I have a habit of not reading the middle of things...... 11/6/2018, 4:29:19 AM - waldyrious (Waldir Pimenta): It might be a sign that it's too long, though 11/6/2018, 4:31:29 AM - sbrl (Starbeamrainbowlabs): I'm not sure that's the case. I just haven't reviewed it in a while and was still at least somewhat still in 'process tldr-pages PR mode' 11/6/2018, 4:36:31 AM - waldyrious (Waldir Pimenta): yeah, we do need more maintainers to avoid having to go through backlogs like this (and to ensure we bounce these details off each other every so often, helping them stick to memory). I mean, it's not realistic to expect anyone to memorize all these guides, nor to consult them fully before doing anything in the project 11/6/2018, 4:37:12 AM - waldyrious (Waldir Pimenta): I'm sorry I'm not around as often as I'd like to, to help in that process 11/6/2018, 4:38:21 AM - waldyrious (Waldir Pimenta): I actually just commented on #2512 somewhat to that effect 1/14/2023, 3:19:52 PM - robospicywiener_twitter (Rob Newman) joined the room 11/24/2018, 4:41:10 AM - robospicywiener_twitter (Rob Newman): Nice work! I like it - just looked up whereis cmd and not found - is there an area to recommend cmds? 11/24/2018, 4:42:00 AM - robospicywiener_twitter (Rob Newman): and locate - I use them a bit. 11/24/2018, 4:48:25 AM - sbrl (Starbeamrainbowlabs): Looks like we have both `whereis` and `locate` pages already, @robospicywiener_twitter. 11/24/2018, 4:48:31 AM - sbrl (Starbeamrainbowlabs): What client are you using? 11/24/2018, 4:48:45 AM - sbrl (Starbeamrainbowlabs): And on what OS? 11/24/2018, 4:49:03 AM - sbrl (Starbeamrainbowlabs): Some clients won't search platforms other than your current one automatically. 11/24/2018, 5:22:21 PM - robospicywiener_twitter (Rob Newman): ah, ok was on safari on mac 11/24/2018, 5:25:13 PM - robospicywiener_twitter (Rob Newman): Tried with Firefox and Chrome, same-ish return - apart from firefox 'where' is shown, but doesn't link to anything. 11/24/2018, 5:25:44 PM - robospicywiener_twitter (Rob Newman): MacOS Mojave 10.14.1 11/24/2018, 5:25:45 PM - sbrl (Starbeamrainbowlabs): Ah, I see. The `locate` and `whereis` pages are in the `linux` section. 11/24/2018, 5:26:09 PM - sbrl (Starbeamrainbowlabs): So you'd need to do `tldr linux/locate` for example. 11/24/2018, 5:26:20 PM - robospicywiener_twitter (Rob Newman): ah, seen - thanks 11/24/2018, 5:26:37 PM - sbrl (Starbeamrainbowlabs): If they are available on macOS, would you be able to open a PR that copies the pages to the osx folder please? 12/7/2018, 4:16:05 PM - dbrgn (Danilo Bargen): for the programming language nerds: tealdeer is now on [rust 2018](https://hacks.mozilla.org/2018/12/rust-2018-is-here/)! https://github.com/dbrgn/tealdeer/pull/69 12/7/2018, 4:27:26 PM - sbrl (Starbeamrainbowlabs): Cool! 😃 12/7/2018, 5:04:59 PM - psibi (Sibi Prabakaran): @dbrgn Congrats! I just read in your `README.md` that you were not able to install the Haskell client for benchmarking it. If you are still feeling to pursue it, you can install it via this command: ``` stack install tldr --resolver=nightly-2018-12-06 ``` Feel free to open an issue if you are still unable to install it. 12/7/2018, 6:09:08 PM - dbrgn (Danilo Bargen): @psibi thanks for the info :) does that install tldr system-wide? I'd like to be able to just build/run it without installing it, if that's possible. 12/8/2018, 7:58:46 AM - psibi (Sibi Prabakaran): @dbrgn IIRC, It will be installed in `~./.local/bin`. You will likely have to add it to $PATH for it to work 12/8/2018, 7:59:36 AM - psibi (Sibi Prabakaran): The installation manager (stack) will likely inform you the place where its installed. 12/15/2018, 12:18:33 AM - sbrl (Starbeamrainbowlabs): Looks like pinning issues is a thing! 12/15/2018, 12:18:33 AM - sbrl (Starbeamrainbowlabs): https://blog.github.com/changelog/2018-12-13-pinned-issues/ 12/17/2018, 6:41:34 PM - waldyrious (Waldir Pimenta): Do you have any issues in mind for the tldr repo? 12/17/2018, 8:33:45 PM - sbrl (Starbeamrainbowlabs): What about one of the lists of pages to give people an idea as to what to write a page about? 12/17/2018, 8:34:53 PM - sbrl (Starbeamrainbowlabs): There's #1579, and #2213 that might be good candidates 12/18/2018, 4:55:11 AM - waldyrious (Waldir Pimenta): Good thinking. 12/18/2018, 4:56:33 AM - waldyrious (Waldir Pimenta): We can pin those, but I'd prefer a more descriptive title for the windows one 12/18/2018, 4:57:10 AM - waldyrious (Waldir Pimenta): Something similar to the GNU one would do fine :) 12/18/2018, 5:18:40 AM - sbrl (Starbeamrainbowlabs): Indeed! 12/18/2018, 5:18:52 AM - sbrl (Starbeamrainbowlabs): What about "Windows commands missing in tldr-pages"? 12/18/2018, 5:19:40 AM - sbrl (Starbeamrainbowlabs): Checking into it, there's only 1 command left in #1579 - `wmic`! 12/18/2018, 6:09:54 AM - owenvoke (Owen Voke): I was thinking of adding a few more things to the Windows list. 12/18/2018, 6:10:23 AM - owenvoke (Owen Voke): Actually, I thought I had finished the WMIC command. Maybe I'll do it tomorrow. 12/18/2018, 4:09:42 PM - sbrl (Starbeamrainbowlabs): Ah, right! Maybe we could start a new issue then for the next list, since #1579 is getting kinda long. 12/18/2018, 4:49:23 PM - owenvoke (Owen Voke): :+1: Sounds good to me. Plus, it's not really 'Getting started with the new Windows section' anymore. 😛 12/18/2018, 4:50:09 PM - owenvoke (Owen Voke): I've added quite a few of the commands, looks like WMIC is now being deprecated and removed from future versions of Windows (it also has a huge number of commands) so not sure if it's worth adding it. 12/18/2018, 5:01:33 PM - sbrl (Starbeamrainbowlabs): Cool! Hrm. 12/18/2018, 5:01:51 PM - sbrl (Starbeamrainbowlabs): You may be right. 12/18/2018, 5:01:57 PM - sbrl (Starbeamrainbowlabs): What's replacing it?/ 12/18/2018, 5:10:11 PM - owenvoke (Owen Voke): Powershell CIM cmdlets. 12/19/2018, 3:44:42 PM - sbrl (Starbeamrainbowlabs): Ah 12/20/2018, 5:06:50 AM - sbrl (Starbeamrainbowlabs): Drat! I pushed that commit to master by accident. 12/20/2018, 5:07:16 AM - sbrl (Starbeamrainbowlabs): I reverted it & created a new branch, but now GitHub _claims_ there aren't any changes..... 12/20/2018, 5:07:25 AM - sbrl (Starbeamrainbowlabs): But `git diff` clearly shows otherwise 12/20/2018, 5:11:09 AM - sbrl (Starbeamrainbowlabs): Thoughts? 1/14/2023, 3:20:59 PM - FraYoshi (Francesco Yoshi Gobbo) joined the room 12/20/2018, 7:53:29 AM - FraYoshi (Francesco Yoshi Gobbo): hi!! 12/20/2018, 7:53:54 AM - FraYoshi (Francesco Yoshi Gobbo): is tldr now mainly on github or gitlab? i find it in both and updated XD 12/20/2018, 7:57:06 AM - FraYoshi (Francesco Yoshi Gobbo): okay, it was udated apparently.. if I understand correctly, it is still on github ^^ i checked because some moved to gitlab after Microsoft's acquisition. :) 12/20/2018, 3:45:32 PM - sbrl (Starbeamrainbowlabs): Hey there, @FraYoshi! I haven't seen tldr-pages on GitLab. DO you have a link to that please? 12/20/2018, 3:45:54 PM - sbrl (Starbeamrainbowlabs): As far as I'm aware, the official home of tldr-pages is still GitHub. 12/20/2018, 6:04:39 PM - waldyrious (Waldir Pimenta): @FraYoshi hey, sorry for the confusion! The gitlab repo is a mirror I set up. gitlab has this neat feature that automatically keeps mirrors up to date, but I can see how that may confuse people regarding where things are actually being actively maintained 😅 12/20/2018, 6:05:13 PM - waldyrious (Waldir Pimenta): @sbrl I've commented in https://github.com/tldr-pages/tldr/issues/2649#issuecomment-448983548 about the branch mixup 12/20/2018, 6:05:40 PM - waldyrious (Waldir Pimenta): if you and @agnivade react quickly enough, we might be able to clean things up before new commits are pushed to master :) 12/20/2018, 6:06:10 PM - waldyrious (Waldir Pimenta): @pxgamer and @mfrw, please hold off merging any PRs if you see this. 12/20/2018, 10:01:46 PM - sbrl (Starbeamrainbowlabs): Thanks! I've cleaned it up via cherry picking & opened a PR. 12/20/2018, 10:01:58 PM - sbrl (Starbeamrainbowlabs): Here's a bit of bash for everyone: ```bash reset && while read nextcmd; do tldr "${nextcmd}" >/dev/null 2>&1; if [[ $? -ne 0 ]]; then echo $nextcmd; fi done < <(history | awk '{print $2}' | sort | uniq | grep -iP '^[a-zA-Z0-9]+$') ``` 12/20/2018, 10:02:39 PM - sbrl (Starbeamrainbowlabs): It will search your entire shell history and output a list of all the commands you've used that don't have a tldr page. 12/20/2018, 10:03:10 PM - sbrl (Starbeamrainbowlabs): It relies on your tldr client exiting with a non-zero exit code if a page wasn't found. 12/20/2018, 10:14:13 PM - sbrl (Starbeamrainbowlabs): It's a bit rough atm, as I've only just thrown it together. 12/20/2018, 10:14:21 PM - sbrl (Starbeamrainbowlabs): You could probably optimise it quite a bit 12/20/2018, 10:36:55 PM - waldyrious (Waldir Pimenta): ah, that's a good point. I use a home-made shell script as a "client" and I don't think I made sure it returns the appropriate error code if it doesn't find the page 12/20/2018, 10:38:26 PM - waldyrious (Waldir Pimenta): would it make sense to call `exit 1` under this line? https://gist.github.com/waldyrious/805d6357fa0b55135354ea4b996e0818#file-tldr-sh-L84 12/20/2018, 10:41:24 PM - sbrl (Starbeamrainbowlabs): Yeah, I think so! 12/20/2018, 10:41:34 PM - sbrl (Starbeamrainbowlabs): I should make a comment on the client spec page about that too 12/20/2018, 10:41:51 PM - sbrl (Starbeamrainbowlabs): Personally, I use the bash client 12/20/2018, 10:43:06 PM - waldyrious (Waldir Pimenta): yeah, I've been meaning to take a look at the bash client 12/20/2018, 10:43:38 PM - waldyrious (Waldir Pimenta): but I wanted to experiment with a dirt simple client that simply dumps the plain text content of files to the terminal 12/20/2018, 10:43:51 PM - waldyrious (Waldir Pimenta): one that hopefully could be included out of the box with the tldr repo :) 12/20/2018, 10:50:23 PM - waldyrious (Waldir Pimenta): @sbrl I use zsh on macos and the command you shared above fails with the error `zsh: parse error near 'done'` 12/20/2018, 10:55:47 PM - waldyrious (Waldir Pimenta): (the grep command needs -E instead of -P on macOS, but I get the same error even with that changed) 12/20/2018, 10:58:53 PM - waldyrious (Waldir Pimenta): anyway, edited my bash micro-client: https://gist.github.com/waldyrious/805d6357fa0b55135354ea4b996e0818/revisions#diff-044a673dd5c3490d8e9695e8822dcc61 12/21/2018, 2:02:51 AM - sbrl (Starbeamrainbowlabs): Ah, cool! 12/21/2018, 2:03:06 AM - sbrl (Starbeamrainbowlabs): Yeah, I'm unsure as to whether it'll work right with zsh 12/21/2018, 2:03:49 AM - sbrl (Starbeamrainbowlabs): I wrote it with Bash - it's probably the process substitution (`< <(....)`) that's causing it to complain 12/21/2018, 2:05:40 AM - sbrl (Starbeamrainbowlabs): You might need to do `bash -c '....'` to get it to work 12/21/2018, 2:05:59 AM - sbrl (Starbeamrainbowlabs): Or save it to a file with `#!/usr/bin/env bash` as the first line 1/14/2023, 3:21:11 PM - fredluvsangie_twitter (Fred Flores) joined the room 12/22/2018, 5:04:30 PM - fredluvsangie_twitter (Fred Flores): Ok 12/22/2018, 5:05:48 PM - fredluvsangie_twitter (Fred Flores): Hi 12/22/2018, 5:17:20 PM - sbrl (Starbeamrainbowlabs): Hey there, @fredluvsangie_twitter! Welcome to tldr-pages. 12/22/2018, 5:21:19 PM - sbrl (Starbeamrainbowlabs): (Also, @waldyrious, you might find recent developments in #1065 interesting. I've started to draft an official client spec) 12/27/2018, 1:33:07 PM - waldyrious (Waldir Pimenta): @sbrl I tried `bash -c '...'` but the history file for bash is pretty much empty, as I've been using zsh since I set up this laptop :) but while trying to get it to work, I came across this: https://stackoverflow.com/a/32805596/266309 12/27/2018, 1:33:24 PM - waldyrious (Waldir Pimenta): wouldn't piping be more readable than process substitution? 12/27/2018, 1:34:59 PM - waldyrious (Waldir Pimenta): as for #1065, I did notice some movement there in the past few weeks, but I didn't open the notification because I wanted to do it when I had the time to participate meaningfully 12/27/2018, 1:35:48 PM - waldyrious (Waldir Pimenta): otherwise I'd just be aware of the progress but wouldn't be able to contribute, and I'd lose the unread notification as a reminder / backlog entry to make sure I'd get to it 12/27/2018, 4:03:42 PM - sbrl (Starbeamrainbowlabs): Ah, yeah, it would! I just couldn't remember the syntax for it - and I cooked that up in ~5 minutes 12/27/2018, 4:03:50 PM - sbrl (Starbeamrainbowlabs): I could rewrite to utilise that 12/27/2018, 4:04:26 PM - sbrl (Starbeamrainbowlabs): Perhaps you could alter it to do `cat ~/.zsh_history` instead of `history` or whatever the file is 12/28/2018, 2:05:30 PM - waldyrious (Waldir Pimenta): :+1: will try that :) 12/28/2018, 5:12:03 PM - waldyrious (Waldir Pimenta): @sbrl I ended up going with the following: 12/28/2018, 5:12:55 PM - waldyrious (Waldir Pimenta): ```sh $ cat $HISTFILE | grep -oE '^: \d+:0;[a-z]+' | cut -d';' -f2 | sort | uniq > /tmp/my-commands.txt $ find ~/.local/src/tldr/pages/ -name '*.md' | grep -oE '[^/]+\.md' | cut -d'.' -f1 | sort | uniq > /tmp/tldr-commands.txt $ comm -23 /tmp/my-commands.txt /tmp/tldr-commands.txt ``` 12/28/2018, 5:15:04 PM - sbrl (Starbeamrainbowlabs): Ah, awesome solution! 12/28/2018, 5:15:12 PM - sbrl (Starbeamrainbowlabs): Didn't know that `comm` was a thing 😛 12/28/2018, 11:48:03 PM - waldyrious (Waldir Pimenta): I learned about it from reviewing a PR to tldr 😉 12/28/2018, 11:49:11 PM - waldyrious (Waldir Pimenta): #408 😃 12/28/2018, 11:49:57 PM - waldyrious (Waldir Pimenta): I later edited it in #858 12/28/2018, 11:51:23 PM - sbrl (Starbeamrainbowlabs): 😛 12/28/2018, 11:51:39 PM - waldyrious (Waldir Pimenta): I love the online tool Venny, to compare up to 4 lists using an interactive Venn diagram interface. `comm` is essentially the CLI version of it 😊 12/28/2018, 11:51:47 PM - sbrl (Starbeamrainbowlabs): Sounds like just the thing I could use in multiple different circumstances 12/28/2018, 11:52:06 PM - waldyrious (Waldir Pimenta): Yep, it's quite convenient 12/28/2018, 11:52:16 PM - waldyrious (Waldir Pimenta): Not very intuitive though 12/28/2018, 11:52:24 PM - sbrl (Starbeamrainbowlabs): e.g. for updating Nextcloud to the next version 12/28/2018, 11:52:36 PM - sbrl (Starbeamrainbowlabs): gotta copy all the apps over manually 12/28/2018, 11:53:31 PM - sbrl (Starbeamrainbowlabs): and there's no way to tell which are the default ones, and which ones are yours - except comparing the list to those in the new version...... 12/28/2018, 11:55:21 PM - waldyrious (Waldir Pimenta): For the occasions where you have more than 2 lists, give Venny a try. It's really cool. 12/29/2018, 12:02:59 AM - sbrl (Starbeamrainbowlabs): Yeah! 1/14/2023, 3:21:26 PM - mebeim (Marco Bonelli) joined the room 1/9/2019, 5:49:29 AM - mebeim (Marco Bonelli): Hi guys, it is not really clear from `CONTRIBUTING.md`: are you accepting translations in new languages? (Or just the ones already present?) If so, I would like to start translating some pages in Italian since I am a native speaker. If that's ok, would it be fine to create a PR with a new `pages.it` top level directory containing some translated pages? 1/9/2019, 5:50:27 AM - waldyrious (Waldir Pimenta): @mebeim new translations in any language are most welcome :) you can create `pages.it`, sure! 1/9/2019, 5:50:56 AM - waldyrious (Waldir Pimenta): Also PRs to make CONTRIBUTING.md clearer in this regard would be greatly appreciated! 😄 1/9/2019, 5:51:32 AM - mebeim (Marco Bonelli): Thank you, would it be preferred to have one commit per translated command or just a few commits with more than one translated page? 1/9/2019, 5:53:12 AM - waldyrious (Waldir Pimenta): IMO either a single commit for everything, or one commit per page, whatever is easier for you. I don't think a middle ground of several commits, each with a batch of pages would make much sense. 1/9/2019, 5:53:57 AM - waldyrious (Waldir Pimenta): of course, when I say "everything", I don't mean translations should cover all existing pages! You're free to send multiple PRs as time permits 1/9/2019, 5:54:21 AM - mebeim (Marco Bonelli): Yeah that's exactly what I was talking about :) 1/9/2019, 5:55:49 AM - waldyrious (Waldir Pimenta): Yeah, makes sense. You can also add more translations to an existing PR which hasn't been merged yet, if you're OK with it being squash-merged 1/9/2019, 5:56:07 AM - waldyrious (Waldir Pimenta): Anyway, the exact model can be worked out in the PR discussion, there are no hard-set rules 1/9/2019, 5:57:05 AM - waldyrious (Waldir Pimenta): I need to go now. Talk to you later :) 1/9/2019, 5:57:11 AM - mebeim (Marco Bonelli): Bye 1/9/2019, 6:01:53 AM - sbrl (Starbeamrainbowlabs): Hey, @mebeim! Translations are a really new thing, so we haven't gotten around to updating the docs yet 😛 1/9/2019, 6:02:23 AM - sbrl (Starbeamrainbowlabs): Translations are most welcome! We've even got a special new label to attach to such PRs 😃 1/9/2019, 6:07:32 AM - mebeim (Marco Bonelli): Thanks, I noticed. 1/9/2019, 6:09:48 AM - mebeim (Marco Bonelli): I would also suggest to add a checker which checks the pages missing examples in a certain language, to make it easier for people to identify what needs to be translated. That would be a non-trivial task though, I'm still looking around to see how the whole thing could possibly work. 1/9/2019, 3:37:37 PM - mebeim (Marco Bonelli): Could you guys clarify something to me? I very often see something like this: ```md - Print "hello" to the screen: `echo {{hello}}` ``` For example in the [`ag`](https://github.com/tldr-pages/tldr/blob/master/pages/common/ag.md) command: ```md - Find files containing "foo", and print the line matches in context: `ag {{foo}}` ``` Does this follow the style guidelines? Shouldn't double curly braces only be used only to mark *variables* rather than constants? Or should they be used *anywhere* there is something that is entered by the user? 1/9/2019, 5:13:53 PM - sbrl (Starbeamrainbowlabs): The double curly braces are should surround anything that the user can change. 1/9/2019, 5:28:52 PM - mebeim (Marco Bonelli): @sbrl thank you for the clarification 1/9/2019, 6:11:28 PM - sbrl (Starbeamrainbowlabs): np :-) 1/14/2023, 3:21:35 PM - schneiderl (Lucas Gabriel Schneider) joined the room 1/11/2019, 4:31:07 AM - schneiderl (Lucas Gabriel Schneider): Hi, I'm new to the project but I'm willing to add some Brazilian Portuguese translations of some pages. Since the creation of translation folders follows ISO 639-1 it would be expected for a new folder called "pages.pt" to be created and the translations should be added under that folder. The problem is that this could lead to a mix of European and Brazilian Portuguese translations under that folder. I could just create a new folder called pages.br but that would go against what is currently being done. Another option is to create folders like pages.pt.br but that would also go against ISO 639-1. Do you guys have any input on what is the best alternative here? 1/11/2019, 5:08:19 AM - mebeim (Marco Bonelli): Adding my humble opinion on top of this: it should be stated somewhere clearly which spec is being used for language names. I think ISO 639-1 would be good with a fallback to ISO 639-2 for languages that don't have an ISO 639-1 code. Alternatively everything could be just done in ISO 639-2 for all languages (that would mean renaming the existing ones first). 1/11/2019, 5:11:42 AM - waldyrious (Waldir Pimenta): ISO 639-2 does not solve the Brazilian Portuguese issue though (it's still "por", as is European Portuguese), plus it's less well-known 1/11/2019, 5:12:21 AM - waldyrious (Waldir Pimenta): usually software projects tend to use IETF language codes (BCP 47 ) for this purpose, so Brazilian Portuguese would be `pt-BR` 1/11/2019, 5:15:58 AM - waldyrious (Waldir Pimenta): that's largely compatible with ISO 639-1 IIUC, and indeed existing folder names for translations already conform to BCP 47 1/11/2019, 5:16:48 AM - waldyrious (Waldir Pimenta): Also, I agree that "it should be stated somewhere clearly which spec is being used for language names" 1/11/2019, 5:17:06 AM - waldyrious (Waldir Pimenta): Probably in CONTRIBUTING.md 1/11/2019, 5:17:08 AM - mebeim (Marco Bonelli): Oh, that's right, IETF looks like the best spec 1/11/2019, 5:17:39 AM - mebeim (Marco Bonelli): @waldyrious yeah was thinking exactly that 1/11/2019, 5:18:52 AM - mebeim (Marco Bonelli): I think that this should be done quickly since people seem to begin to be willing to translate pages 1/11/2019, 5:20:16 AM - waldyrious (Waldir Pimenta): Sure. Anyone can contribute that, though :) I'm personally in the middle of other tasks so I can't do that myself. 1/11/2019, 5:27:43 AM - mebeim (Marco Bonelli): I could do that but I wouldn't want to appear like trying to impose my own rules 1/11/2019, 5:28:53 AM - waldyrious (Waldir Pimenta): Ah, please don't worry about that :) that's precisely what pull request review is for! 1/11/2019, 5:29:16 AM - waldyrious (Waldir Pimenta): Also, the archives of this chat are public, so you can link to this conversation if that makes you feel more comfortable :) 1/11/2019, 5:29:39 AM - mebeim (Marco Bonelli): Oh, cool, did not know, how can I link to this? 1/11/2019, 5:29:43 AM - waldyrious (Waldir Pimenta): You can click on any message's three-dot menu at the right to get a timestamp to it 1/11/2019, 5:30:07 AM - mebeim (Marco Bonelli): Got it, ty 1/11/2019, 5:30:12 AM - waldyrious (Waldir Pimenta): There are also daily archives accessible from the settings button at the top right 1/11/2019, 5:48:42 AM - sbrl (Starbeamrainbowlabs): Ah, that's a tricky problem! I agree, we should definitely switch to the ab-CD format ASAP before clients start to depend on it. 1/11/2019, 5:48:56 AM - sbrl (Starbeamrainbowlabs): Updating the docs sounds like a good plan too. 1/11/2019, 5:49:09 AM - sbrl (Starbeamrainbowlabs): Would you like to take a look at that, @mebeim? 1/11/2019, 6:15:13 AM - mebeim (Marco Bonelli): @sbrl I am right now, but gotta go to bed (2AM here), probably going to make a pull request tomorrow 1/11/2019, 6:15:49 AM - sbrl (Starbeamrainbowlabs): Cool! In UK here - should probably go to bed myself 😛 1/11/2019, 6:16:28 AM - sbrl (Starbeamrainbowlabs): I want to start writing up an actual _real_ draft of the client spec tomorrow if I've got time (and don't get distracted) 1/11/2019, 6:22:07 AM - mebeim (Marco Bonelli): well goodnight then 1/11/2019, 6:22:42 AM - mebeim (Marco Bonelli): (also answered to your comments on my pr), now I really got to go, bye! 1/11/2019, 9:43:20 AM - agnivade (Agniva De Sarker): If the existing folder names already conform to BCP-47, do we still need to change them ? Or is that just for making things consistent ? 1/11/2019, 10:28:39 AM - agnivade (Agniva De Sarker): Ok, I just took a look at https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html#Locale-Names. 1/11/2019, 10:30:52 AM - agnivade (Agniva De Sarker): They also use the ll_CC format which is a combination of the ISO-639 2 letter language code and ISO3166 2 letter country code. 1/11/2019, 10:31:35 AM - agnivade (Agniva De Sarker): But they are joined by _, whereas https://en.wikipedia.org/wiki/IETF_language_tag#Syntax_of_language_tags it is mentioned that they are separated by hypens (-) 1/11/2019, 10:31:38 AM - agnivade (Agniva De Sarker): Are both valid ? 1/11/2019, 10:43:59 AM - agnivade (Agniva De Sarker): Hmm .. from the spec, it does look like hypen is the valid separator (https://tools.ietf.org/rfc/bcp/bcp47.txt). Not sure why GNU uses _. 1/11/2019, 4:50:05 PM - mebeim (Marco Bonelli): right, I was looking at that difference too... I thought the underscore was accepted, I am too used to see it everywhere 1/11/2019, 5:08:16 PM - mebeim (Marco Bonelli): also, found this cool page to test BCP 47 country codes: http://schneegans.de/lv/ 1/11/2019, 5:32:16 PM - agnivade (Agniva De Sarker): thanks. 1/11/2019, 5:37:09 PM - agnivade (Agniva De Sarker): @mebeim - Do you plan on sending the folder rename change ? 1/11/2019, 5:38:03 PM - agnivade (Agniva De Sarker): I was thinking of sending the documentation change, since translations seem to be gathering steam and I might need to add client support. 1/11/2019, 7:01:41 PM - sbrl (Starbeamrainbowlabs): :+1: 1/11/2019, 7:06:44 PM - mebeim (Marco Bonelli): @agnivade I was planning on adding guidelines for country codes to `CONTRIBUTING.md`, but I could do that too I suppose 1/11/2019, 7:13:06 PM - mebeim (Marco Bonelli): by the way I was thinking: what about languages that can be represented as more than one code (like for italian `it` and `it-IT`)? 1/11/2019, 8:17:30 PM - agnivade (Agniva De Sarker): oh I see. From the discussion above, I thought you will send the folder rename change. No worries, let me know whatever you plan to do. 1/11/2019, 8:18:28 PM - agnivade (Agniva De Sarker): > by the way I was thinking: what about languages that can be represented as more than one code (like for italian `it` and `it-IT`)? We won't be accepting `it` anymore. The country code needs to be there in the folder name. 1/11/2019, 8:24:45 PM - mebeim (Marco Bonelli): i'll push the doc in the late evening (3PM here) 1/12/2019, 1:18:02 AM - mebeim (Marco Bonelli): done: [x](https://github.com/tldr-pages/tldr/pull/2703) 1/12/2019, 1:30:38 AM - sbrl (Starbeamrainbowlabs): Hey, @mebeim! I'm having issues reviewing that PR. I think GitHub is having issues (GitHub pages are taking ages to load - but no other websites) 1/12/2019, 1:30:47 AM - sbrl (Starbeamrainbowlabs): It looks great! Just 1 comment: I'm unsure whether we should include English as an example, as the pages are, by default, already in English. 1/12/2019, 1:31:25 AM - sbrl (Starbeamrainbowlabs): There we go - 8th time lucky.... 1/12/2019, 1:35:17 AM - mebeim (Marco Bonelli): @sbrl wait, you're totally right, let me update it so it is clearer. 1/12/2019, 1:35:36 AM - sbrl (Starbeamrainbowlabs): 😃 1/12/2019, 1:53:42 AM - mebeim (Marco Bonelli): Done, but this got me thinking though... what about the existence of multiple countries which use the same language, like for example Spanish: `es-AR`, `es-BO`, `es-CL`, `es-CO`, `es-CR`, `es-DO`, etc... 1/12/2019, 1:55:53 AM - mebeim (Marco Bonelli): Or even English: `en-US`, `en-GB`, `en-CA`, etc.. I think it should probably be stated that adding an already existing language for a different country should only be done when there are significant differences between the two 🤔🤔 1/12/2019, 1:56:51 AM - sbrl (Starbeamrainbowlabs): Hrm, yeah - that might be a good idea. 1/12/2019, 2:50:32 AM - mebeim (Marco Bonelli): Done :) 1/12/2019, 3:33:14 AM - sbrl (Starbeamrainbowlabs): [![Selection_107.png](https://files.gitter.im/tldr-pages/tldr/7ZpW/thumb/Selection_107.png)](https://files.gitter.im/tldr-pages/tldr/7ZpW/Selection_107.png) 1/12/2019, 3:33:22 AM - sbrl (Starbeamrainbowlabs): Looks like we just passed 20K stars 😃 1/12/2019, 3:34:28 AM - mebeim (Marco Bonelli): nice! 1/12/2019, 11:08:38 PM - sbrl (Starbeamrainbowlabs): Yay! We have a spec document in #2706 1/12/2019, 11:42:43 PM - mebeim (Marco Bonelli): imo omitting the "ideally" on [L155](https://github.com/tldr-pages/tldr/pull/2706/commits/4e51358e4dadeb9d144a2c5e585ad79b486487f2#diff-c44bfdc3ffa7de3ea2e723f752666686R155) and make it a more strict rule would be a better idea 1/13/2019, 12:01:19 AM - sbrl (Starbeamrainbowlabs): Thanks, @mebeim 😺 1/13/2019, 2:27:26 AM - mebeim (Marco Bonelli): Are markdown styles like `**bold**`, `_italics_` and `*italics*` allowed in the pages? I don't see it mentioned anywhere and I also only see five (5) total pages using a word which is styled in such a way. 1/13/2019, 2:29:33 AM - mebeim (Marco Bonelli): I think it would probably be better to only use regular text without any styling for two main reasons: 1) examples are already short and simple, no need to highlight stuff in them other than user entered variables; 2) I don't think most clients handle this at all, and just print the examples description as is, leaving those symbols as plaintext. 1/13/2019, 2:43:22 AM - sbrl (Starbeamrainbowlabs): You _can_ use them in pagess, but we don't recommend it. The main reason for the comment on CommonMark is the issue with the new `> Homepage: ` syntax, which makes use of autolinks 1/13/2019, 3:00:49 AM - mebeim (Marco Bonelli): Oh, ok, did not know you could use them, I thought they just randomly slipped out of reviews. 1/15/2019, 3:28:05 AM - waldyrious (Waldir Pimenta): @mebeim, @agnivade -- the discrepancy in using `-` vs. `_` is due to different standards: IETF language tags (BCP 47), which uses the former, and POSIX locales (ISO/IEC 15897), which use the latter. 1/15/2019, 3:28:49 AM - waldyrious (Waldir Pimenta): https://en.wikipedia.org/wiki/Locale_(computer_software)#POSIX_platforms 1/15/2019, 3:32:56 AM - mebeim (Marco Bonelli): @waldyrious yep, googled that yesterday 1/15/2019, 3:33:11 AM - waldyrious (Waldir Pimenta): :+1: 1/15/2019, 3:33:38 AM - waldyrious (Waldir Pimenta): I'm in a meeting right now but I'll try to review your PR before going to bed 1/15/2019, 3:33:43 AM - mebeim (Marco Bonelli): That was a sad discovery tho 1/15/2019, 3:33:51 AM - mebeim (Marco Bonelli): Oh yeah, no problem take your time :) 1/15/2019, 3:34:13 AM - waldyrious (Waldir Pimenta): haha at least it's two competing standards, rather than 7 😉 1/15/2019, 3:34:37 AM - mebeim (Marco Bonelli): 😆 1/15/2019, 3:34:52 AM - waldyrious (Waldir Pimenta): ah sorry, I actually meant 15 xD --> https://xkcd.com/927/ 1/15/2019, 3:35:19 AM - mebeim (Marco Bonelli): oh that XKCD! love it hahah 1/15/2019, 3:47:37 AM - sbrl (Starbeamrainbowlabs): 😛 1/15/2019, 3:48:02 AM - sbrl (Starbeamrainbowlabs): I don't think it really matters which we use - so long as we pick one and stick with it 1/15/2019, 3:48:40 AM - waldyrious (Waldir Pimenta): Agreed. I am partial to hyphens myself, but I won't oppose if you guys prefer underscores 1/15/2019, 3:53:03 AM - sbrl (Starbeamrainbowlabs): Yeah - I use hyphens quite a lot myself 1/15/2019, 3:53:15 AM - sbrl (Starbeamrainbowlabs): In css, toml settings files, ..... 1/15/2019, 5:30:25 AM - owenvoke (Owen Voke): I prefer hyphens too. :+1: 1/15/2019, 5:31:07 AM - owenvoke (Owen Voke): But guess it just matters to stick with something. 1/15/2019, 11:18:39 AM - agnivade (Agniva De Sarker): I don't mind either. Let's just stick with one. 1/14/2023, 3:22:05 PM - Charles-Neil (Charles) joined the room 1/17/2019, 8:18:24 AM - Charles-Neil (Charles): Hi guys, I am new here. I wonder whether there is a flag to view pages in specific language like `tldr --lang=zh apt-get`? 1/17/2019, 4:28:42 PM - sbrl (Starbeamrainbowlabs): Hey, @Charles-Neil! Great question. As for yet, we do not currently have a client that has support for multiple languages AFAIK - as multiple language support is new! 1/17/2019, 4:29:23 PM - sbrl (Starbeamrainbowlabs): However, we plan to implement support in the [official node client](https://github.com/tldr-pages/tldr-node-client) soon. 1/17/2019, 4:30:03 PM - sbrl (Starbeamrainbowlabs): The way it should work is that will determine what language of page to show you by the `LANG` and `LANGUAGE` environment variables. 1/17/2019, 4:30:40 PM - sbrl (Starbeamrainbowlabs): We're currently hashing this out in #2706, if you'd like to check it out! 1/18/2019, 10:35:07 AM - Charles-Neil (Charles): Thanks for explanation about that. Looking forward to it :thumbsup: . 1/18/2019, 4:27:15 PM - sbrl (Starbeamrainbowlabs): 😃 1/19/2019, 2:04:13 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/O3v3/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/O3v3/image.png) 1/19/2019, 2:04:28 AM - mebeim (Marco Bonelli): Wow, looks like tldr > man, hahaha! 1/19/2019, 2:07:36 AM - sbrl (Starbeamrainbowlabs): 🎆 1/19/2019, 2:07:40 AM - sbrl (Starbeamrainbowlabs): 😃 1/19/2019, 9:38:22 PM - waldyrious (Waldir Pimenta): 😍 1/28/2019, 3:25:55 AM - mebeim (Marco Bonelli): I was looking through some commands while translating and came across [`case`](https://github.com/tldr-pages/tldr/blob/master/pages/common/case.md) (in the `common` section). So is it ok to document internal shell-specific statements too? I mean, is not a package, command, or similar, it got me a bit confused. 1/28/2019, 3:28:09 AM - mebeim (Marco Bonelli): I mean if it's ok I think it should be at least stated that it is an sh/bash statement rather than a command. 1/28/2019, 3:40:04 AM - sbrl (Starbeamrainbowlabs): I think so, @mebeim. Another example includes `shopt`. I think with things like shell commands you just need to be careful to mention that it's a shell builtin and to make the page as compatible as possible with different shell variants 1/28/2019, 3:42:30 AM - mebeim (Marco Bonelli): Hmm, yeah that's kinda strange. I saw `for` too. 1/28/2019, 4:14:54 AM - sbrl (Starbeamrainbowlabs): Yeah, there are a few floating around 1/29/2019, 12:14:12 AM - sbrl (Starbeamrainbowlabs): Looks like a few PRs & notifications slipped through my notifications net. 1/29/2019, 12:14:41 AM - sbrl (Starbeamrainbowlabs): I've changed email clients now & _finally_ got my sieve rules sorted, so it shouldn't happen nearly as often from now on 😛 1/29/2019, 12:38:25 AM - mebeim (Marco Bonelli): I disabled mail notifications a while ago since they were filling my inbox and I didn't want to create a filter just for them. Do you happen to know if there's some way to get mobile notifications for GitHub? Like IFTTT or similar? 1/29/2019, 12:40:27 AM - sbrl (Starbeamrainbowlabs): Hrm. Not sure - might have to hook into the GH api and output an Atom feed or something 1/29/2019, 6:56:36 AM - mebeim (Marco Bonelli): hmm, gh api might be a cool idea... 1/29/2019, 12:13:41 PM - owenvoke (Owen Voke): I've used a few apps before like `GH::watch` to receive notifications. 1/29/2019, 12:15:45 PM - owenvoke (Owen Voke): But yeah, you can do it with the API. I had it sending notifs with PushBullet for a while. 1/29/2019, 3:43:43 PM - sbrl (Starbeamrainbowlabs): It's a shame they don't have standard Atom fed for your notifications 1/30/2019, 4:31:46 AM - mebeim (Marco Bonelli): Right, that would have been much simpler 1/30/2019, 4:33:01 AM - mebeim (Marco Bonelli): I'll probably code a simple module to my telegram bot to get notifications via the gh api 1/30/2019, 5:48:34 AM - sbrl (Starbeamrainbowlabs): Cool! 1/31/2019, 11:33:53 PM - mebeim (Marco Bonelli): Guys, what are the settings of the master branch for the tldr-pages/tldr repo? I guess it's set to [something like this](https://i.imgur.com/fukJHRK.png) right? 1/31/2019, 11:35:47 PM - sbrl (Starbeamrainbowlabs): https://screenshots.firefox.com/krVT4GfIlLRfn3hM/github.com 1/31/2019, 11:35:56 PM - sbrl (Starbeamrainbowlabs): ^---- The branch settings 1/31/2019, 11:37:03 PM - sbrl (Starbeamrainbowlabs): I did have to temporarily disable it for a sec the other day in order to force-push when I accidentally committed 1/31/2019, 11:37:17 PM - sbrl (Starbeamrainbowlabs): But I reset it back to the way it was before 1/31/2019, 11:37:22 PM - mebeim (Marco Bonelli): So basically no one can push to master without a PR 1/31/2019, 11:37:35 PM - sbrl (Starbeamrainbowlabs): Basically, yeah 1/31/2019, 11:37:40 PM - mebeim (Marco Bonelli): I might have found a vulnerability in how the build process is configured anyway 1/31/2019, 11:37:44 PM - sbrl (Starbeamrainbowlabs): Oh? 1/31/2019, 11:37:55 PM - mebeim (Marco Bonelli): Actually, remove the "might" 1/31/2019, 11:38:11 PM - sbrl (Starbeamrainbowlabs): Perhaps we should move this conversation to keybase? 1/31/2019, 11:38:17 PM - sbrl (Starbeamrainbowlabs): If it's a vulnerability 1/31/2019, 11:38:29 PM - mebeim (Marco Bonelli): Yep, was about to ask you, see you there 1/31/2019, 11:38:33 PM - sbrl (Starbeamrainbowlabs): Sure 2/1/2019, 10:05:06 PM - mebeim (Marco Bonelli): I see there's a `MAINTAINERS.md` file where contributors/members/owners are listed. Should I add myself there? 2/1/2019, 11:19:43 PM - sbrl (Starbeamrainbowlabs): Absolutely, @mebeim! 2/1/2019, 11:19:55 PM - sbrl (Starbeamrainbowlabs): I forgot that was a thing lol 2/1/2019, 11:21:29 PM - mebeim (Marco Bonelli): Ok, thanks :) 2/4/2019, 7:48:04 PM - mebeim (Marco Bonelli): Someone please take a look at this: https://travis-ci.org/tldr-pages/tldr/jobs/488514400#L546 2/4/2019, 8:12:13 PM - mebeim (Marco Bonelli): Nevermind, just figured it out, sneaky sneaky. See #2752 :) 2/11/2019, 11:00:32 PM - owenvoke (Owen Voke): Just updated my local repo and it just says that files have been renamed no matter how many times I hard reset. ``` renamed: pages.it/common/ls.md -> pages.it/common/ls.md renamed: pages.it/common/rm.md -> pages.it/common/rm.md ``` Tried cloning it down again, still the same. 2/11/2019, 11:18:03 PM - sbrl (Starbeamrainbowlabs): That's odd, @pxgamer. 2/11/2019, 11:18:08 PM - sbrl (Starbeamrainbowlabs): What version of git is that? 2/11/2019, 11:18:18 PM - sbrl (Starbeamrainbowlabs): And which branch? 2/12/2019, 1:08:26 AM - mebeim (Marco Bonelli): @pxgamer weird. I assume you did not touch anything, right? Did you re-clone in a different folder? I have no issue with those files. Very strange. 2/12/2019, 1:10:01 AM - mebeim (Marco Bonelli): The only thing I can think of right now is some problem with your HDD that makes git believe the files were modified. I've had similar issues in the past with other programs since I've got some pretty old HDD on my PC. Other than that IDK really, difficult to say what's wrong without looking at it in first person. 2/12/2019, 1:34:12 AM - sbrl (Starbeamrainbowlabs): You could always try cloning it to a tmpfs partition to test that 2/12/2019, 1:34:20 AM - sbrl (Starbeamrainbowlabs): or if you're on Windows, an ImDisk virtual ramdisk 2/12/2019, 3:00:42 AM - owenvoke (Owen Voke): Windows. Git 2.20.1 and master. 2/12/2019, 3:02:07 AM - owenvoke (Owen Voke): Recloned to another location. 2/12/2019, 3:05:24 AM - owenvoke (Owen Voke): I'll test it on my Linux PC as well. Maybe it's just Windows. 2/12/2019, 3:53:30 AM - sbrl (Starbeamrainbowlabs): Yeah 2/12/2019, 3:53:39 AM - sbrl (Starbeamrainbowlabs): It could also be a permissions issue 2/12/2019, 3:54:11 AM - sbrl (Starbeamrainbowlabs): i.e. git works with Linux permissions by default, so it could have automatically translated the permissions to something else. 2/12/2019, 3:54:18 AM - sbrl (Starbeamrainbowlabs): Does `git diff` display anything? 2/12/2019, 5:18:34 AM - owenvoke (Owen Voke): Just says it's a rename. 2/12/2019, 4:32:49 PM - owenvoke (Owen Voke): Doesn't seem to be a permissions thing. 2/12/2019, 4:37:09 PM - owenvoke (Owen Voke): Ah. Found the issue. I'll open a PR. 2/12/2019, 4:46:35 PM - owenvoke (Owen Voke): Opened #2775 2/12/2019, 4:48:27 PM - owenvoke (Owen Voke): Windows doesn't render the spaces in command prompt 😠 2/12/2019, 8:07:19 PM - agnivade (Agniva De Sarker): Great find @pxgamer ! 2/19/2019, 3:20:32 AM - mebeim (Marco Bonelli): Hi guys, one question: where are clients supposed to get the pages from? tldr-pages.github.io? Is this stated somewhere? Because I could not find anything about it. If not, I'd probably make a PR to edit the current client specification draft (#2706) to precisely specify where pages should be downloaded from by the client. 2/19/2019, 3:28:17 AM - sbrl (Starbeamrainbowlabs): I think it's https://github.com/tldr-pages/tldr-pages.github.io 2/19/2019, 3:28:32 AM - sbrl (Starbeamrainbowlabs): Specifically https://github.com/tldr-pages/tldr-pages.github.io/blob/master/assets/tldr.zip 2/19/2019, 3:49:15 AM - mebeim (Marco Bonelli): yeah I meant that 2/19/2019, 3:49:46 AM - mebeim (Marco Bonelli): are client supposed to get the pages from there? i.e. instead of https://github.com/tldr-pages/tldr/archive/master.zip 2/19/2019, 3:50:06 AM - mebeim (Marco Bonelli): if so that should probably be stated somewhere 2/19/2019, 5:01:08 AM - sbrl (Starbeamrainbowlabs): I think so 2/19/2019, 5:01:15 AM - sbrl (Starbeamrainbowlabs): Yeah, you're right there 2/19/2019, 5:01:29 AM - sbrl (Starbeamrainbowlabs): I haven't had the time to review the client spec issue today though 2/19/2019, 5:01:36 AM - sbrl (Starbeamrainbowlabs): Should get to it real soon though 2/19/2019, 5:01:51 AM - sbrl (Starbeamrainbowlabs): I try to check through all my GH notifications every ~2-3 days 2/19/2019, 5:29:23 AM - mebeim (Marco Bonelli): Yeah I don't have much time either recently, I just check/review stuff randomly but cannot manage to get anything serious done. I'll get into that as soon as I've got some spare time though if it is still needed. 2/19/2019, 5:34:42 AM - sbrl (Starbeamrainbowlabs): Cool, thanks! 2/19/2019, 8:09:17 PM - agnivade (Agniva De Sarker): Where did https://github.com/tldr-pages/tldr/archive/master.zip come from ? I thought the build script uploaded the zip archive to the tldr-pages.github.io repo only ? 2/19/2019, 8:09:35 PM - agnivade (Agniva De Sarker): There should be only one source of truth. 2/19/2019, 8:11:16 PM - agnivade (Agniva De Sarker): The archive links are stated here - https://github.com/tldr-pages/tldr/wiki/TLDR-clients and here - https://github.com/tldr-pages/tldr/wiki/Minimum-specifications-for-TLDR-command-line-clients. 2/19/2019, 8:12:00 PM - agnivade (Agniva De Sarker): And both of them point to the .github.io repo. 2/19/2019, 8:23:45 PM - mebeim (Marco Bonelli): @agnivade that link I mentioned comes directly from GitHub, it's just the link you get if you want to download the repo as zip! As you say, the build script is only responsible of the archive on the `tldr-pages.github.io` repo. Also, thanks for the links, I didn't even know there were Wiki pages 😮, I'm dumb. 2/19/2019, 9:03:39 PM - agnivade (Agniva De Sarker): Oh it's the entire repo as a zip ! Got it. 2/19/2019, 9:04:38 PM - agnivade (Agniva De Sarker): The build script only takes a specific subset of that (pages*/ and LICENSE.md) so I think that is the correct way to go. 2/19/2019, 9:10:27 PM - mebeim (Marco Bonelli): Yes, that's definitely better indeed. 1/14/2023, 3:22:36 PM - Relsoul (soul) joined the room 2/22/2019, 9:42:54 AM - Relsoul (soul): hello~ tldr expected to support multi-languages? 2/22/2019, 3:31:05 PM - owenvoke (Owen Voke): It is in the process (see #2339). Currently people are able to contribute new translations in the format `pages.{language-code}/...`, but I'm not sure if the clients support it yet. 2/22/2019, 8:14:24 PM - agnivade (Agniva De Sarker): AFAIK, the clients do not support it yet. You are most welcome to send a PR ! I have been meaning to get to it, but sadly more open-source responsibilities are piling on me from other projects. 3/5/2019, 2:51:26 PM - owenvoke (Owen Voke): Does anyone else keep getting emails from IssueHunt about tldr? 3/5/2019, 3:32:10 PM - sbrl (Starbeamrainbowlabs): Nope, @pxgamer! 3/5/2019, 3:32:13 PM - sbrl (Starbeamrainbowlabs): What do they say? 3/5/2019, 3:32:21 PM - sbrl (Starbeamrainbowlabs): Who or what is issuehunt? 3/5/2019, 5:48:29 PM - owenvoke (Owen Voke): It's an issue bounty service I guess. They say "We help build a sustainable open source ecosystem. I wanted to learn how you manage tldr and show you how we can help you out." 3/5/2019, 10:30:47 PM - sbrl (Starbeamrainbowlabs): Hrm. 3/5/2019, 10:31:13 PM - sbrl (Starbeamrainbowlabs): Not sure anyone would pay a bounty for pages being created here on tldr-pages really 😛 3/7/2019, 3:15:30 AM - owenvoke (Owen Voke): Sorry, didn't reply. I got back to say I wasn't interested. 3/7/2019, 3:34:11 AM - sbrl (Starbeamrainbowlabs): np 😛 3/7/2019, 3:34:17 AM - sbrl (Starbeamrainbowlabs): And yeah, probably the best response 3/7/2019, 11:24:47 AM - agnivade (Agniva De Sarker): I think I might have got once. 3/7/2019, 11:24:49 AM - agnivade (Agniva De Sarker): Just ignored 3/8/2019, 5:00:46 PM - owenvoke (Owen Voke): Ah, that's fine :+1: 3/12/2019, 1:04:29 PM - agnivade (Agniva De Sarker): Does someone know how does the read notifications in github reduce ? 3/12/2019, 1:05:23 PM - agnivade (Agniva De Sarker): My number has been ever increasing since github made the change to save notifications for later 3/12/2019, 1:05:41 PM - agnivade (Agniva De Sarker): Will the number just keep on increasing forever ? 3/12/2019, 1:06:10 PM - waldyrious (Waldir Pimenta): I've wondered the same 3/12/2019, 1:06:30 PM - waldyrious (Waldir Pimenta): It may be related to the new ability to control all subscriptions in a centralized place https://github.com/notifications/subscriptions 3/12/2019, 1:06:38 PM - agnivade (Agniva De Sarker): right ? 3/12/2019, 1:06:43 PM - agnivade (Agniva De Sarker): It's baffling me 3/12/2019, 1:07:10 PM - agnivade (Agniva De Sarker): But I don't want to unsubscribe from an issue 3/12/2019, 1:07:17 PM - waldyrious (Waldir Pimenta): I suppose as long as you're still subscribed to a thread, those notifications will be there marked as read. 3/12/2019, 1:07:22 PM - agnivade (Agniva De Sarker): I just want the read notifications to go away 3/12/2019, 1:07:23 PM - waldyrious (Waldir Pimenta): Yeah, I get you 3/12/2019, 1:07:50 PM - waldyrious (Waldir Pimenta): well, I can see a use case for the recently read ones (say last 30 days) 3/12/2019, 1:08:13 PM - agnivade (Agniva De Sarker): Oh man .. that's a huge problem. Because I am a member of Go repo- which has thousands of issues. So automatically I get subscribed to every one of them since I am a member 3/12/2019, 1:08:33 PM - agnivade (Agniva De Sarker): Currently, my number is 1056 😟 3/12/2019, 1:09:07 PM - agnivade (Agniva De Sarker): Yeah .. but that no. has to reduce somehow right ? That's what I am not getting. 3/12/2019, 1:09:11 PM - waldyrious (Waldir Pimenta): now you can not only mark a notification as read, but also mark as unread; if you decide to mark something as unread after closing the notifications page, the UI doesn't show an easy way to do so other than the "read" tab 3/12/2019, 1:09:36 PM - waldyrious (Waldir Pimenta): it's still poor UI but that particular use case isn't served otherwise AFAIK 3/12/2019, 1:10:04 PM - waldyrious (Waldir Pimenta): I guess they expect us to consider that as the "all mail" tab of gmail, or something 3/12/2019, 1:10:36 PM - waldyrious (Waldir Pimenta): and unsubscribing would then be like deleting an email 3/12/2019, 1:11:30 PM - waldyrious (Waldir Pimenta): They have been making changes recently so hopefully they're still iterating in the UI 3/12/2019, 1:11:55 PM - agnivade (Agniva De Sarker): The analogy is not exactly perfect. Even if I delete an email, if someone responds to the same thread, I will get notified. But if I unsubscribe, and someone comments on the issue, I won't be notified. 3/12/2019, 1:12:54 PM - waldyrious (Waldir Pimenta): hmm, yeah. In any case, I'm just speculating. I wish I knew what usage model they are going for 3/12/2019, 1:15:04 PM - agnivade (Agniva De Sarker): yeah 3/12/2019, 1:18:20 PM - waldyrious (Waldir Pimenta): Changing subject a bit, yesterday I came across this: https://opensource.googleblog.com/2019/03/introducing-season-of-docs.html 3/12/2019, 1:18:43 PM - waldyrious (Waldir Pimenta): I'm trying to figure out if it's something we could fit tldr-pages work in 3/12/2019, 1:19:10 PM - waldyrious (Waldir Pimenta): I'd love to use that as a way to tackle my huge backlog of tasks in the project, especially the big ones 3/12/2019, 1:39:45 PM - agnivade (Agniva De Sarker): Interesting. From what I see, these will be purely technical documentation tasks. But were you talking about other technical tasks which can change the architecture of our pages ? Or the one where we wanted to show the page coverage ? 3/12/2019, 5:15:41 PM - sbrl (Starbeamrainbowlabs): That sounds really cool! 3/12/2019, 5:15:58 PM - sbrl (Starbeamrainbowlabs): We should apply and see - only 1 way to find out 😛 3/12/2019, 5:16:36 PM - sbrl (Starbeamrainbowlabs): My new subscriptions sits at 1K+ 3/13/2019, 1:55:16 AM - waldyrious (Waldir Pimenta): Both, @agnivade, but especially the architecture ones 3/13/2019, 1:55:57 AM - waldyrious (Waldir Pimenta): the completeness drive can be completed in a distributed manner so they require (comparatively) less focused effort 3/13/2019, 1:57:39 AM - waldyrious (Waldir Pimenta): I managed to get in touch with one of the organizers through the WriteTheDocs Slack: https://www.writethedocs.org/slack/ 3/13/2019, 1:58:02 AM - waldyrious (Waldir Pimenta): Hopefully she'll be able to clarify whether this is something that could benefit us :) 3/13/2019, 2:03:40 AM - sbrl (Starbeamrainbowlabs): Cool! I look forward to hearing back 😃 3/13/2019, 2:06:06 AM - waldyrious (Waldir Pimenta): Me too ^^ 3/13/2019, 2:07:16 AM - waldyrious (Waldir Pimenta): btw, I'm sorry I couldn't contribute to the discussion on the client spec before it got merged 3/13/2019, 2:07:31 AM - waldyrious (Waldir Pimenta): one more thing going into my backlog to review later 😛 3/13/2019, 2:11:03 AM - sbrl (Starbeamrainbowlabs): No problem! 3/22/2019, 1:38:10 PM - owenvoke (Owen Voke): Just a random question, I assume using anchors in page URLs should be fine? 3/22/2019, 2:19:58 PM - waldyrious (Waldir Pimenta): I can't think of any reason why they shouldn't :) 3/22/2019, 4:55:42 PM - owenvoke (Owen Voke): Ah, ok :+1: 3/22/2019, 4:55:43 PM - sbrl (Starbeamrainbowlabs): Yeah, they should 3/22/2019, 4:55:46 PM - owenvoke (Owen Voke): I'll test it out. 3/22/2019, 4:55:52 PM - sbrl (Starbeamrainbowlabs): :+1: 3/26/2019, 4:17:13 AM - waldyrious (Waldir Pimenta): Early April the Season of Docs program will start accepting project proposals from organizations. Do you guys want to start listing some of the bigger tasks we could use dedicated effort with? --> https://developers.google.com/season-of-docs/docs/timeline 3/26/2019, 4:19:28 AM - waldyrious (Waldir Pimenta): We will also need to nominate mentors, btw, but I think we can pick stuff that woulnd't require too much mentoring work, especially if we can get people already involved with the project to work on the tasks (I'm considering applying myself, FWIW) 3/26/2019, 12:21:57 PM - agnivade (Agniva De Sarker): Translation support in clients is one of the biggest tasks right now. Then probably move duplicate files in linux and mac folders to common. 3/26/2019, 1:08:54 PM - owenvoke (Owen Voke): :+1: I might have a look at the duplicate files stuff. 3/26/2019, 1:10:11 PM - owenvoke (Owen Voke): Oh, that's things for contributors to do. Cool. :+1: 3/26/2019, 1:40:00 PM - waldyrious (Waldir Pimenta): Let's create a page on our wiki for these ideas 3/26/2019, 2:01:50 PM - waldyrious (Waldir Pimenta): https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects 3/26/2019, 2:02:26 PM - waldyrious (Waldir Pimenta): please fill up the existing entries with more details as you can, or add new ones. I have some more to add as well :) 3/26/2019, 2:05:22 PM - waldyrious (Waldir Pimenta): (I took the liberty of adding potential mentors, but feel free to edit those 😄) 3/26/2019, 2:21:48 PM - sbrl (Starbeamrainbowlabs): Hey, great idea! I'll definitely be up for mentoring a linter conversion. I'd also be up for mentoring missing page creation, so I've put my name down for that 3/26/2019, 2:22:48 PM - sbrl (Starbeamrainbowlabs): With respect to a new linter, it'd be great if we could simultaneously develop a test suite that fully exercises the linter and demonstrates errors that it catches. 3/26/2019, 2:23:17 PM - sbrl (Starbeamrainbowlabs): (We've got a huge supply of test cases for when it is supposed to work 😛) 3/26/2019, 2:23:45 PM - sbrl (Starbeamrainbowlabs): I think the idea with that project is to convert it into something maintainable, so there'll definitely be an emphasis these 3/26/2019, 2:59:08 PM - agnivade (Agniva De Sarker): oh yea the linter upgrade is sorely overdue 3/26/2019, 3:16:13 PM - owenvoke (Owen Voke): :+1: 1/14/2023, 3:23:11 PM - ian0371 (Chihyun Song) joined the room 3/26/2019, 3:39:41 PM - ian0371 (Chihyun Song): Hi, I'm getting an error while running `tldr -u`. ``` { Error: connect ECONNREFUSED 185.199.110.153:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1083:14) errno: 'ECONNREFUSED', code: 'ECONNREFUSED', syscall: 'connect', address: '185.199.110.153', port: 443 } ``` Can somebody help? 3/26/2019, 4:49:00 PM - sbrl (Starbeamrainbowlabs): Hey, @ian0371! Do you have a firewall in the way at all? 3/26/2019, 5:23:12 PM - agnivade (Agniva De Sarker): Try manually connecting at that port and see what happens. 3/26/2019, 5:26:40 PM - sbrl (Starbeamrainbowlabs): Which client are you using? Is it the node client (https://github.com/tldr-pages/tldr-node-client)? 3/26/2019, 8:03:56 PM - sbrl (Starbeamrainbowlabs): Which client are you using? Is it the node client (https://github.com/tldr-pages/tldr-node-client)? 3/26/2019, 9:25:19 PM - agnivade (Agniva De Sarker): I can mentor the language support for node client. Hopefully that shouldn't be too difficult. 3/26/2019, 9:27:01 PM - sbrl (Starbeamrainbowlabs): :+1: 3/26/2019, 9:28:53 PM - agnivade (Agniva De Sarker): fleshed out the section in the wiki page 1/14/2023, 3:23:15 PM - surmish (Urmish Shah) joined the room 3/26/2019, 11:18:48 PM - surmish (Urmish Shah): How do you install tldr on RedHat (without node.js) 3/26/2019, 11:20:08 PM - sbrl (Starbeamrainbowlabs): Have you checked the client list in the README, @surmish? There's a client in almost every language! 3/26/2019, 11:20:17 PM - sbrl (Starbeamrainbowlabs): Perhaps the Python or C++ client would do the trick? 3/26/2019, 11:20:49 PM - sbrl (Starbeamrainbowlabs): Not sure if any of them have been officially packaged for REHL, but you're welcome to help out by doing so 😃 3/26/2019, 11:43:53 PM - surmish (Urmish Shah): I am in a work environment. And I wish to use the Python client and install tldr on a local disk space I have 3/26/2019, 11:44:06 PM - surmish (Urmish Shah): So without sudo privileges, how should I go about this. 3/26/2019, 11:44:15 PM - surmish (Urmish Shah): I have python 3.7 but can't really do pip install. 3/26/2019, 11:45:23 PM - surmish (Urmish Shah): The bash client is the easiest options it looks like. 3/26/2019, 11:49:04 PM - surmish (Urmish Shah): I was able to get the bash client working (tldr-sh). Thanks! 3/26/2019, 11:56:18 PM - sbrl (Starbeamrainbowlabs): Awesome! I use the bash client myself. I've cloned it to my `~/bin` folder and set up a symlink 3/27/2019, 7:36:15 AM - ian0371 (Chihyun Song): @sbrl @agnivade I guess it was the firewall problem. Used VPN and it worked! 3/27/2019, 2:44:01 PM - agnivade (Agniva De Sarker): @surmish - You can always do a pip install for your user. 3/27/2019, 2:44:06 PM - agnivade (Agniva De Sarker): Don't need root for that 3/27/2019, 2:44:23 PM - agnivade (Agniva De Sarker): You just have to set the path to the local pip path 3/27/2019, 4:26:27 PM - sbrl (Starbeamrainbowlabs): Great, @ian0371 ! 1/14/2023, 3:23:21 PM - matrixbot (matrixbot) joined the room 3/27/2019, 10:37:29 PM - matrixbot (matrixbot): `felixonmars` or use pip --user 3/28/2019, 5:00:01 AM - waldyrious (Waldir Pimenta): Thanks @agnivade and @sbrl for the edits to the wiki. I think we're going to have a good set of projects to apply with. 3/28/2019, 5:00:11 AM - sbrl (Starbeamrainbowlabs): 😃 3/28/2019, 5:00:18 AM - waldyrious (Waldir Pimenta): I've made some more edits to add missing details 3/28/2019, 5:01:08 AM - waldyrious (Waldir Pimenta): I haven't followed the discussion about the duplicate pages in linux and mac, so someone else probably should fill that section 3/28/2019, 5:01:47 AM - waldyrious (Waldir Pimenta): It can be especially tricky since we don't want to check just for availability, but for compatible interface as well. 3/28/2019, 5:08:21 AM - sbrl (Starbeamrainbowlabs): Cool! I'm not sure about the moving of duplicates to common. Isn't `common` only for pages that are common across _all_ OSes? 3/28/2019, 5:09:21 AM - waldyrious (Waldir Pimenta): Again, I haven't followed the latest discussions on the topic, so I can't say for sure 3/28/2019, 5:12:29 AM - sbrl (Starbeamrainbowlabs): Edited homepages section, it's an easy one so I could mentor that one if anyone wanted to take it on 3/28/2019, 5:15:31 AM - waldyrious (Waldir Pimenta): :+1: 3/28/2019, 5:16:02 AM - waldyrious (Waldir Pimenta): I hope to be able to work on fleshing these out this weekend 3/28/2019, 5:56:59 AM - sbrl (Starbeamrainbowlabs): 😃 3/28/2019, 1:59:39 PM - agnivade (Agniva De Sarker): See here https://github.com/tldr-pages/tldr/issues/2813#issuecomment-468758919. The idea is that if a page is common for more than one folders, then we put it in common. It's not necessary for it to be common for all platforms. We thought that before, but it's better this way. Only when a page differs between platforms, then the specific one can remain in the platform-specific folder. 3/28/2019, 1:59:46 PM - agnivade (Agniva De Sarker): The client will first look for a page in the host platform, then look in common. 3/28/2019, 1:59:47 PM - agnivade (Agniva De Sarker): This does change one behavior slightly, where a client using windows will be able to see a page for linux+mac. But I remember we had a discussion to show an extra message that this page is not in windows, but available in so and so platform; please use the --os flag to get that page. 3/28/2019, 2:00:36 PM - agnivade (Agniva De Sarker): so this change will be default enable that behavior 3/29/2019, 5:05:51 PM - sbrl (Starbeamrainbowlabs): I think I get it. Does that mean we need to update the client spec? 3/29/2019, 5:06:11 PM - sbrl (Starbeamrainbowlabs): It would be helpful to have that documented somewhere if it isn't already 3/30/2019, 6:54:02 PM - agnivade (Agniva De Sarker): Yeah, I think only this section https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#platform needs to be changed 3/30/2019, 6:54:22 PM - agnivade (Agniva De Sarker): this looks more or less fine to me - https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#page-resolution. But can do with some more clarification 3/30/2019, 7:08:54 PM - sbrl (Starbeamrainbowlabs): Would you like to open a PR? 3/30/2019, 7:08:57 PM - sbrl (Starbeamrainbowlabs): Or shall I do it 3/31/2019, 1:00:44 AM - agnivade (Agniva De Sarker): You can go ahead. 3/31/2019, 1:07:42 AM - sbrl (Starbeamrainbowlabs): Ok! 3/31/2019, 1:16:22 AM - sbrl (Starbeamrainbowlabs): Opened PR #2859 1/14/2023, 3:23:30 PM - prfcttone_gitlab (Andrew Martin Farias) joined the room 4/1/2019, 9:09:41 AM - prfcttone_gitlab (Andrew Martin Farias): Hello 4/1/2019, 2:13:41 PM - sbrl (Starbeamrainbowlabs): Hello, @prfcttone_gitlab! Welcome to tldr-pages :-) 4/8/2019, 3:18:29 AM - waldyrious (Waldir Pimenta): Hey guys. The Season of Docs organization applications are now open, so I've read about the process in mode detail. There are a few things we need to decide 4/8/2019, 3:18:58 AM - waldyrious (Waldir Pimenta): 1) each organization will be allowed a max of 2 projects for this first edition, so we need to choose which project we want to go with 4/8/2019, 3:20:38 AM - waldyrious (Waldir Pimenta): The program seems much more geared towards people who are primarily technical writers than developers, so we might want to focus on the content projects more than on the development ones (for those GSoC or GCI would be a better fit) 4/8/2019, 3:21:20 AM - waldyrious (Waldir Pimenta): For convenience, here's what we got so far: https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects 4/8/2019, 3:26:18 AM - waldyrious (Waldir Pimenta): 2) We need to have two organization administrators. I think it would make sense for them to be @agnivade and @sbrl, as the two currently active organization owners. But we can pick something else if you guys prefer. 4/8/2019, 3:27:27 AM - sbrl (Starbeamrainbowlabs): Yeah, sounds good! I'll def. be an admin for that, but I'll probably need at least a little guidance on what I'm supposed to do there 4/8/2019, 3:28:23 AM - sbrl (Starbeamrainbowlabs): Is this kinda like GCI, where there are many contributors? 4/8/2019, 3:28:24 AM - waldyrious (Waldir Pimenta): I've been following the program's slack workspace, so I should be able to help with that :) 4/8/2019, 3:28:31 AM - sbrl (Starbeamrainbowlabs): Cool! Thanks :-) 4/8/2019, 3:29:03 AM - waldyrious (Waldir Pimenta): I'm still reading the guidelines to be sure, but so far I think it's more like GSoC 4/8/2019, 3:29:23 AM - sbrl (Starbeamrainbowlabs): Right. That was one with many contributors too? 4/8/2019, 3:29:26 AM - waldyrious (Waldir Pimenta): they seem to be aiming for projects that could take up to 3 months to fully complete 4/8/2019, 3:29:27 AM - sbrl (Starbeamrainbowlabs): I get confused betweent he 2 lol 4/8/2019, 3:29:31 AM - sbrl (Starbeamrainbowlabs): right. 4/8/2019, 3:30:01 AM - waldyrious (Waldir Pimenta): Ah, hehe sorry. Yeah, GSoC is the one with larger tasks and fewer participants 4/8/2019, 3:30:53 AM - sbrl (Starbeamrainbowlabs): Ah, right - I see! For content projects, `Completeness: create missing pages` and `Add links to all existing pages`, or possibly `Merge the lists of clients on the wiki, the README and the website` would probably be the best bets then 4/8/2019, 3:30:58 AM - waldyrious (Waldir Pimenta): The projects don't need to be complex; in our case most of the work (assuming we do focus on content more than coding) it's a matter of slowly tackling a backlog more than requiring a lot of skill 4/8/2019, 3:31:56 AM - waldyrious (Waldir Pimenta): Merging the client lists sounds a bit light for a 3-month project, but we can always submit more than 2, since they will dip into the extras list if there are vacant slots :) 4/8/2019, 3:32:08 AM - sbrl (Starbeamrainbowlabs): Ah, I see! 4/8/2019, 3:32:18 AM - sbrl (Starbeamrainbowlabs): So we need to put things in priority order? 4/8/2019, 3:32:40 AM - sbrl (Starbeamrainbowlabs): It would be nice to get some of the smaller things out of the way first 4/8/2019, 3:33:07 AM - waldyrious (Waldir Pimenta): We could have a project composed of multiple small things 4/8/2019, 3:33:40 AM - sbrl (Starbeamrainbowlabs): Ah, good idea 4/8/2019, 3:33:46 AM - waldyrious (Waldir Pimenta): Let me just finish the list of things we need to decide :) 4/8/2019, 3:33:52 AM - sbrl (Starbeamrainbowlabs): ok :-) 4/8/2019, 3:34:15 AM - sbrl (Starbeamrainbowlabs): We could def. bundle `Move duplicate pages` and `Add links to all existing pages` I think. 4/8/2019, 3:34:54 AM - waldyrious (Waldir Pimenta): 3) There's an optional stipend for organizations of $500 per mentored participant. Since we currently don't have any process for handling incoming money (not even donations), so I'd say it's best to skip that for now to make things simpler 4/8/2019, 3:36:15 AM - waldyrious (Waldir Pimenta): 4) Each project should have two mentors. Administrators can mentor projects, but I'm not sure a mentor can mentor more than one project. I'll confirm, but in the meantime, please consider stepping up. Two mentors by project means it should be relatively lightweight for each one 4/8/2019, 3:36:36 AM - waldyrious (Waldir Pimenta): I think that's about it for decisions 4/8/2019, 3:38:38 AM - waldyrious (Waldir Pimenta): So for now I'll start by moving the coding projects to a separate wiki page, which we can use later for GSoC or GCI 4/8/2019, 3:52:50 AM - sbrl (Starbeamrainbowlabs): Cool! And I've no idea how accepting money would even work lol, so yeah probably best to skip that for now, though it is an interesting possibility 4/8/2019, 3:53:22 AM - sbrl (Starbeamrainbowlabs): @pxgamer? 4/8/2019, 3:53:32 AM - waldyrious (Waldir Pimenta): yes, I think it's something we should look at for the future, but let's not add too much to our plate at once :) 4/8/2019, 3:55:50 AM - waldyrious (Waldir Pimenta): Hmmm, looks like they ask for an organization email address in the application form, but we don't have one. I'll ask them what they'd recommend in a case like ours. 4/8/2019, 4:06:29 AM - sbrl (Starbeamrainbowlabs): I see. I can always create a special email account on my server if need be. 4/8/2019, 4:06:36 AM - sbrl (Starbeamrainbowlabs): and lol yeah 😛 4/8/2019, 4:07:08 AM - sbrl (Starbeamrainbowlabs): Though tbh messaging here on Gitter is more likely to obtain a swift response 4/8/2019, 4:07:12 AM - waldyrious (Waldir Pimenta): I've asked on slack (https://seasonofdocs.slack.com). I suspect it won't be a problem but I'll let you know once they respond. 4/8/2019, 4:07:19 AM - sbrl (Starbeamrainbowlabs): Sure! 4/8/2019, 4:08:24 AM - waldyrious (Waldir Pimenta): I need to get going for today, but we already have some action items to decide on, so it's probably best not to pollute the chat log much more 😉 4/8/2019, 4:08:49 AM - waldyrious (Waldir Pimenta): In any case the application period is open until the 23rd, so there's no hurry :) 4/8/2019, 4:13:02 AM - sbrl (Starbeamrainbowlabs): ok! I need to go to bed too, so see you later! Prob. a good idea to give the others a chance to reply. 4/8/2019, 4:13:55 AM - waldyrious (Waldir Pimenta): :+1: 👋 4/8/2019, 10:20:07 AM - agnivade (Agniva De Sarker): Sounds good to me 4/8/2019, 10:22:43 AM - agnivade (Agniva De Sarker): None of the doc projects are long enough to take 3 months though .. but adding the missing pages is probably the longest of them 4/8/2019, 10:22:56 AM - agnivade (Agniva De Sarker): so we can club it with something else 4/8/2019, 7:25:52 PM - mebeim (Marco Bonelli): I can help with merging clients if there's the need, I've basically looked at each one of them for the latest issue I opened 4/8/2019, 8:37:25 PM - sbrl (Starbeamrainbowlabs): Cool! Could you put your name down on the wiki please, @mebeim? 4/8/2019, 10:04:41 PM - mebeim (Marco Bonelli): @sbrl Where should I put it precisely? Under "potential mentors" or somewhere else? 4/8/2019, 10:19:00 PM - sbrl (Starbeamrainbowlabs): yeah, potential mentors is the place :-) 4/8/2019, 10:55:18 PM - mebeim (Marco Bonelli): ok, done 4/8/2019, 10:58:57 PM - sbrl (Starbeamrainbowlabs): 😃 4/9/2019, 12:38:55 AM - mebeim (Marco Bonelli): Wait is this only for owners/members? Because I'm neither of those. 4/9/2019, 12:40:15 AM - mebeim (Marco Bonelli): Also I was looking at Nearley (the parser that was proposed here https://github.com/tldr-pages/tldr/wiki/Coding-projects) and it looks cool. I wrote a simple grammar to recognize TLDR pages in like 10 minutes... I'm impressed 4/9/2019, 12:43:53 AM - mebeim (Marco Bonelli): The challenging part about the parser/linter is dealing with the language I think though. Like, do we want an "universal" parser which should accept pages written in any language? Or do we want specific parsers for different languages? This choice is crucial. 4/9/2019, 12:48:36 AM - sbrl (Starbeamrainbowlabs): You aren't? I see. Have you merged 10 PRs yet? We can promote you to an org member if you have. https://github.com/tldr-pages/tldr/blob/master/COMMUNITY-ROLES.md Yeah, I haven't had chance to look into it, but I found it here: https://heredragonsabound.blogspot.com/2019/03/map-borders-part-5.html What do you mean "language"? If you're referring to 'human' languages such as english, spanish, etc., then 1 parser for all languages sounds the most appropriate. 4/9/2019, 12:50:03 AM - mebeim (Marco Bonelli): Hmm how do I see if I merged 10 PRs though 4/9/2019, 12:50:35 AM - mebeim (Marco Bonelli): And with "language" I mean exactly what you just said 4/9/2019, 12:51:05 AM - sbrl (Starbeamrainbowlabs): I'm not sure, actually. Maybe list commits you've authored? 4/9/2019, 12:51:25 AM - sbrl (Starbeamrainbowlabs): When you merge it includes you as an author, IIRC 4/9/2019, 12:53:00 AM - mebeim (Marco Bonelli): Oh, well yeah but there are probably many more commits than PRs haha 4/9/2019, 12:54:33 AM - sbrl (Starbeamrainbowlabs): True 4/9/2019, 12:58:03 AM - mebeim (Marco Bonelli): I just looked into it and you cannot filter PRs by who merged them, that's silly. I'm pretty sure I merged more than 10 though. 4/9/2019, 1:00:45 AM - sbrl (Starbeamrainbowlabs): Sure! I see a number of them when go looking too. I'll begin the process of making you a member :-) 4/9/2019, 1:01:05 AM - mebeim (Marco Bonelli): By the way, I made a very simple draft for a grammar which accepts tldr pages here https://pastebin.com/8UTJiXTQ 4/9/2019, 1:01:20 AM - mebeim (Marco Bonelli): @sbrl thanks :) 4/9/2019, 1:03:41 AM - sbrl (Starbeamrainbowlabs): Opened #2874! I'll wait until there's approval from another org member before actually sending the invite though 4/9/2019, 1:05:46 AM - sbrl (Starbeamrainbowlabs): And hey, that grammar is pretty cool! I think that could be a real contender to replacing our hard-to-maintain bison-based linter. 4/9/2019, 1:08:08 AM - mebeim (Marco Bonelli): Sure np 4/9/2019, 1:09:42 AM - mebeim (Marco Bonelli): That's for sure 100 times more readable than the current, but its simplicity could be a double edged sword, I didn't have much time to look at it, just half an hour on the docs. The fact that the tldr-pages page structure is rather simple helps for sure. 4/9/2019, 1:15:40 AM - sbrl (Starbeamrainbowlabs): Well, there's only 1 way to test it 😛 4/9/2019, 1:44:19 AM - mebeim (Marco Bonelli): Hahaha 4/9/2019, 3:11:52 AM - waldyrious (Waldir Pimenta): They responded about the email thing 4/9/2019, 3:12:28 AM - waldyrious (Waldir Pimenta): They suggested us to either create a new email account for the org, or use something like Google Groups to create a mail list for the org admins. 4/9/2019, 3:12:57 AM - waldyrious (Waldir Pimenta): it's probably easier to do the latter. If you guys agree, I can take care of that. 4/9/2019, 3:13:14 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I guess a mailing list might be better, but it seems like a far cry from our current workflow 4/9/2019, 3:13:25 AM - sbrl (Starbeamrainbowlabs): Yeah, if you don't mind :-) 4/9/2019, 3:13:47 AM - waldyrious (Waldir Pimenta): I was thinking using it just for the program, since we don't have any use case for it otherwise 4/9/2019, 3:14:24 AM - sbrl (Starbeamrainbowlabs): Yeah 4/9/2019, 3:14:54 AM - sbrl (Starbeamrainbowlabs): Perhaps a note in the group saying "Don't use this - open an issue on GH instead"? 😛 4/9/2019, 3:15:58 AM - waldyrious (Waldir Pimenta): We can add such a notice if people find it and start using it to contact the org. Doing it preemptively may sound a bit too aggressive :) 4/9/2019, 3:16:20 AM - sbrl (Starbeamrainbowlabs): True 😛 4/9/2019, 3:16:38 AM - sbrl (Starbeamrainbowlabs): I've also taken the time to improve my tldr missing pages detector 1-liner I wrote a while back 4/9/2019, 3:16:38 AM - sbrl (Starbeamrainbowlabs): https://gitlab.com/sbrl/bin/blob/master/tldr-missing-pages 4/9/2019, 3:16:50 AM - sbrl (Starbeamrainbowlabs): It now only shows commands installed on your system 4/9/2019, 3:16:58 AM - sbrl (Starbeamrainbowlabs): and it's much faster 4/9/2019, 3:18:06 AM - sbrl (Starbeamrainbowlabs): ~2.7s to process 30K lines in my history 4/9/2019, 3:18:12 AM - mebeim (Marco Bonelli): @sbrl is that a script that checks your history for commands not in tldr-pages? 4/9/2019, 3:18:18 AM - sbrl (Starbeamrainbowlabs): Yep! 4/9/2019, 3:18:27 AM - sbrl (Starbeamrainbowlabs): I think I wrote it as a 1-liner before you joined 4/9/2019, 3:18:31 AM - sbrl (Starbeamrainbowlabs): I've just upgraded it now 4/9/2019, 3:18:41 AM - sbrl (Starbeamrainbowlabs): Playing with bash is fun 4/9/2019, 3:18:51 AM - mebeim (Marco Bonelli): why not use the `history` cmd instead of the file? 4/9/2019, 3:19:00 AM - sbrl (Starbeamrainbowlabs): Because it doesn't work in a shell script 😛 4/9/2019, 3:19:08 AM - mebeim (Marco Bonelli): oh really 4/9/2019, 3:19:18 AM - sbrl (Starbeamrainbowlabs): Indeed, or at least it didn't work for me 4/9/2019, 3:19:27 AM - mebeim (Marco Bonelli): so it's not a command it's a bash built-in 4/9/2019, 3:19:32 AM - sbrl (Starbeamrainbowlabs): I think so 4/9/2019, 3:19:46 AM - sbrl (Starbeamrainbowlabs): yeah - `which history` returns nothing 4/9/2019, 3:19:50 AM - mebeim (Marco Bonelli): yep 4/9/2019, 3:20:02 AM - mebeim (Marco Bonelli): I only have 2k lines of hist tho 4/9/2019, 3:20:20 AM - sbrl (Starbeamrainbowlabs): Should be even faster! `time ./tldr-missing-pages` 4/9/2019, 3:20:53 AM - sbrl (Starbeamrainbowlabs): I have 142 missing commands, apparently 4/9/2019, 3:20:56 AM - mebeim (Marco Bonelli): my results are `arping` `python3` `vi` `z3`, cool 4/9/2019, 3:21:03 AM - sbrl (Starbeamrainbowlabs): Awesome! 4/9/2019, 3:21:05 AM - mebeim (Marco Bonelli): I could actually write a page for `arping` 4/9/2019, 3:21:10 AM - sbrl (Starbeamrainbowlabs): 😃 4/9/2019, 3:21:26 AM - mebeim (Marco Bonelli): this is very useful since if you have a program in the history you probably know how to use it 4/9/2019, 3:21:38 AM - sbrl (Starbeamrainbowlabs): good thinking - yeah! 4/9/2019, 3:22:13 AM - mebeim (Marco Bonelli): imma copy it in my scripts directory 😉 4/9/2019, 3:22:16 AM - sbrl (Starbeamrainbowlabs): 😃 4/9/2019, 3:22:25 AM - sbrl (Starbeamrainbowlabs): Go ahead lol 4/9/2019, 3:25:34 AM - waldyrious (Waldir Pimenta): I've created tldr-pages@googlegroups.com 4/9/2019, 3:25:55 AM - waldyrious (Waldir Pimenta): Membership is by invitation 4/9/2019, 3:26:25 AM - mebeim (Marco Bonelli): Cool! 4/9/2019, 3:29:52 AM - waldyrious (Waldir Pimenta): I'm preparing an initial invite to all current maintainers 4/9/2019, 3:32:52 AM - waldyrious (Waldir Pimenta): @mebeim is your email address public? 4/9/2019, 3:40:09 AM - waldyrious (Waldir Pimenta): I've sent invitations to all the current org members (rprieto, sbrl, agnivade and pxgamer). Since @mebeim is in the process of joining, I'll add him as well as soon as I have his email address :) 4/9/2019, 3:41:44 AM - waldyrious (Waldir Pimenta): @sbrl the application form must be submitted by one of the admins before the project mentors can sign up. Would you like to get that started? https://docs.google.com/forms/d/e/1FAIpQLScrEq5yKmadgn7LEPC8nN811-6DNmYvus5uXv_JY5BX7CH-Bg/viewform 4/9/2019, 3:42:29 AM - waldyrious (Waldir Pimenta): (the form data can be edited after submission until the end of the application period, so don't worry too much about the data entered there) 4/9/2019, 3:55:40 AM - mebeim (Marco Bonelli): @waldyrious it is not, I'd rather send it to you privately 4/9/2019, 3:56:13 AM - waldyrious (Waldir Pimenta): Sure, no problem. You can IM me here or email me if you prefer 4/9/2019, 3:56:29 AM - mebeim (Marco Bonelli): Done :) 4/9/2019, 3:57:21 AM - waldyrious (Waldir Pimenta): Invitation sent! 4/9/2019, 3:58:05 AM - mebeim (Marco Bonelli): Thanks 4/9/2019, 4:02:10 AM - mebeim (Marco Bonelli): What should we do about #2252 guys? 4/9/2019, 4:05:30 AM - mebeim (Marco Bonelli): Or, in general, for these kind of situations where there hasn't been a reply for such a long time? I recall reading on the guidelines that trivial changes like these could be handled when merging. 4/9/2019, 4:06:33 AM - waldyrious (Waldir Pimenta): Yes: https://github.com/tldr-pages/tldr/blob/master/contributing-guides/maintainers-guide.md#ii-handling-prs 4/9/2019, 4:06:43 AM - waldyrious (Waldir Pimenta): (we should probably number those bullets for easier reference) 4/9/2019, 4:07:45 AM - waldyrious (Waldir Pimenta): I didn't follow the conversation there, so I can't comment specifically, but if all that's needed is trivial fixes, a maintainer can do that. We usually have push access to PR branches, so that shouldn't be a problem. 4/9/2019, 4:11:13 AM - mebeim (Marco Bonelli): The only thing missing in that PR is converting one uppercase "N" character to lowercase :') it has been sitting there for a little to much I'd say... 4/9/2019, 4:14:52 AM - waldyrious (Waldir Pimenta): Definitely do that then :) such fixes are OK to let contributors do, so that they can practice the git / code review process, but there's no reason we should _require_ the changes to be done by them if they're not inclined to do so (as long as someone else is willing to complete them, of course) 4/9/2019, 4:15:53 AM - mebeim (Marco Bonelli): Right, makes sense 4/9/2019, 9:13:28 AM - agnivade (Agniva De Sarker): Accepted invitation 4/9/2019, 1:16:42 PM - sbrl (Starbeamrainbowlabs): Getting some weirdness with that invite. 4/9/2019, 1:16:49 PM - sbrl (Starbeamrainbowlabs): [![Selection_143.png](https://files.gitter.im/tldr-pages/tldr/L2Bi/thumb/Selection_143.png)](https://files.gitter.im/tldr-pages/tldr/L2Bi/Selection_143.png) 4/9/2019, 1:17:01 PM - sbrl (Starbeamrainbowlabs): After accepting it, I still see this: 4/9/2019, 1:17:15 PM - sbrl (Starbeamrainbowlabs): I'm filling out that google form though 4/9/2019, 1:19:52 PM - sbrl (Starbeamrainbowlabs): Right. Apparently we need a primary and an alternative admin 4/9/2019, 1:20:05 PM - sbrl (Starbeamrainbowlabs): who should we put down? 4/9/2019, 1:20:10 PM - sbrl (Starbeamrainbowlabs): I'm happy to be one of them 4/9/2019, 1:31:57 PM - waldyrious (Waldir Pimenta): As I suggested (way) above, I think it would make sense for the admins to be you and @agnivade, since you're the two active organization owners 4/9/2019, 1:32:56 PM - waldyrious (Waldir Pimenta): As for the mailing list issue, it could be some interaction with your google account? I invited you using the email in your github profile, sbrl@starbeamrainbowlabs.com 4/9/2019, 1:33:29 PM - waldyrious (Waldir Pimenta): If you're logged in to a different google account, that may cause conflicts. That's my guess... 4/9/2019, 1:33:53 PM - waldyrious (Waldir Pimenta): I can change the settings to accept anyone to apply, if that would help 4/9/2019, 3:53:23 PM - sbrl (Starbeamrainbowlabs): Ah, my google account is starbeamrainbowlabs@gmail.com 4/9/2019, 3:53:42 PM - sbrl (Starbeamrainbowlabs): I should probably change the email address on my google account actually, since I don't use it anymore 4/9/2019, 3:53:50 PM - sbrl (Starbeamrainbowlabs): though I have forwarding setup 4/9/2019, 3:56:02 PM - sbrl (Starbeamrainbowlabs): Ok, @agnivade - apparently you need to fill in this form: https://docs.google.com/forms/d/e/1FAIpQLSc5ZsBzqfsib-epktZp8bYxL_hO4RhT_Zz8AY6zXDHB79ue9g/viewform 4/9/2019, 3:57:20 PM - sbrl (Starbeamrainbowlabs): Also, another question: "What previous experience has your organization had in documentation or collaborating with technical writers?" 4/9/2019, 3:57:42 PM - sbrl (Starbeamrainbowlabs): I can answer the next one down "What previous experience has your organization had mentoring individuals?", as I can talk about the GSoC and the GCI 4/9/2019, 9:07:03 PM - agnivade (Agniva De Sarker): Since there are no technical tasks for this, I am not choosing to be a mentor. Just a secondary admin. 4/9/2019, 9:07:25 PM - agnivade (Agniva De Sarker): submitted the form 4/9/2019, 9:07:34 PM - sbrl (Starbeamrainbowlabs): Cool, thanks @agnivade 4/9/2019, 9:10:11 PM - sbrl (Starbeamrainbowlabs): Mentors (apart from myself, since I'm filling out this form) need to fill out this form: https://www.google.com/url?q=https://forms.gle/a1x26WQGzURLerv66&sa=D&ust=1554827966978000&usg=AFQjCNFhY3tp79o5PXUjaUOOhD3l5a-UwQ 4/9/2019, 9:10:23 PM - sbrl (Starbeamrainbowlabs): So @mebeim 4/9/2019, 9:10:52 PM - sbrl (Starbeamrainbowlabs): and anyone else who wants to take part (@pxgamer?) 4/9/2019, 9:11:11 PM - sbrl (Starbeamrainbowlabs): I'm putting down that we want to mentor 2 technical writers 4/9/2019, 9:26:42 PM - mebeim (Marco Bonelli): @sbrl I should put my personal e-mail address on the form, not the google groups mail of the org, right? 4/9/2019, 11:31:14 PM - sbrl (Starbeamrainbowlabs): Yeah 4/9/2019, 11:32:50 PM - mebeim (Marco Bonelli): I submitted it 4/10/2019, 2:07:44 AM - waldyrious (Waldir Pimenta): @sbrl would you like me to invite you to the mailing list as starbeamrainbowlabs@gmail.com? I see that you've joined with the custom domain email, but if it still doesn't work let me know and I'll send an invitation to your gmail account 4/10/2019, 2:18:33 AM - sbrl (Starbeamrainbowlabs): Yeah, it still doesn't work. The one you sent the invite to is actually my primary email address and I self-host my own email server, but it's not attached to my google account, so it won't let me in (is such a thing possible? I think I'd prefer that, tbh) 4/10/2019, 2:18:36 AM - sbrl (Starbeamrainbowlabs): @waldyrious 4/10/2019, 2:19:22 AM - waldyrious (Waldir Pimenta): I know people who have non-gmail accounts as their primary email in a google account but I have no idea how to set it up 4/10/2019, 2:19:31 AM - waldyrious (Waldir Pimenta): for now I'll add your google account then 4/10/2019, 2:20:03 AM - sbrl (Starbeamrainbowlabs): Thanks :-) 4/10/2019, 2:20:18 AM - waldyrious (Waldir Pimenta): Just sent out the invite 4/10/2019, 2:20:51 AM - sbrl (Starbeamrainbowlabs): Cool! That should get forwarded to my backup address (since I guess it's really bad to sign up for a server hosting service with an email account that's hosted on the box you rent lol) 4/10/2019, 2:21:13 AM - waldyrious (Waldir Pimenta): haha indeed 4/10/2019, 3:39:28 AM - waldyrious (Waldir Pimenta): Regarding mentorship, I'm not sure I can help as a mentor since I plan to a apply as a participant, as I mentioned earlier. I've asked the organizers if doing so would be acceptable under the program, and will update you once they respond. 4/10/2019, 3:40:52 AM - waldyrious (Waldir Pimenta): In any case, assuming we will have two projects, we only need one primary mentor for each; admins can double as primary or secondary mentors, and the primary mentor of one project can be the secondary mentor in another (although ideally each mentor would be dedicated to a single project) 4/10/2019, 3:43:28 AM - sbrl (Starbeamrainbowlabs): Ah, ok! Sounds like a plan! 4/10/2019, 3:43:47 AM - sbrl (Starbeamrainbowlabs): I don't remember you mentioning you're applying as a participant, but that works for me 😛 4/10/2019, 3:43:55 AM - waldyrious (Waldir Pimenta): If they allow me to be a participant in a project and a secondary mentor in another, we could have @sbrl, @mebeim, @pxgamer (if he agrees) and myself as the 2 primary mentors + 2 secondary mentors. So let's wait and see what they recommend. 4/10/2019, 3:44:26 AM - sbrl (Starbeamrainbowlabs): I guess the next step is to refactor the wiki page to be the 2 projects 4/10/2019, 3:44:44 AM - waldyrious (Waldir Pimenta): That was my main motivation for pushing for our application, actually :) I was hoping to finally tackle the giant backlog of tasks I have for the project ^^ 4/10/2019, 3:46:31 AM - waldyrious (Waldir Pimenta): yep, that was what I was planning to work on next 4/10/2019, 3:56:02 AM - sbrl (Starbeamrainbowlabs): Awesome 😃 4/10/2019, 4:33:37 AM - waldyrious (Waldir Pimenta): I ended up working on a new update to community-roles.md instead 😛 4/10/2019, 4:34:03 AM - waldyrious (Waldir Pimenta): it's funny how every time we do that dance, new holes are found in the instructions :) 4/10/2019, 4:52:42 AM - sbrl (Starbeamrainbowlabs): lol 😛 4/10/2019, 5:02:13 AM - mebeim (Marco Bonelli): Just to be sure, @waldyrious when you say "two projects" you mean the one for Season of Docs and the one for GSoC? Because I see multiple are listed under the two wiki pages. 4/10/2019, 10:29:12 AM - agnivade (Agniva De Sarker): It is a much better place than having no community-roles at all 😃 4/10/2019, 1:21:39 PM - owenvoke (Owen Voke): Sorry, I never seem to get Gitter notifications on my phone. 😕 Only just read all the info back to the 8th. 4/10/2019, 2:58:35 PM - sbrl (Starbeamrainbowlabs): No problem, @pxgamer! 4/10/2019, 6:02:48 PM - schneiderl (Lucas Gabriel Schneider): Hi there, I was trying to use tldr web client but it just doesnt seem to be finding any of the commands I type in. Even the ones set as examples on the client main page aren't working. Is this really a problem or I'm just doing something wrong? 4/10/2019, 8:04:30 PM - owenvoke (Owen Voke): It seems to be working for me. If you browse to something like https://tldr.ostera.io/tar, do you get any output? 4/10/2019, 8:05:31 PM - mebeim (Marco Bonelli): (works for me too) 4/10/2019, 8:06:33 PM - owenvoke (Owen Voke): Do you get any console errors? 4/10/2019, 10:07:01 PM - schneiderl (Lucas Gabriel Schneider): Weirdly enough now it works. I have no idea what happend. 4/11/2019, 12:20:46 AM - sbrl (Starbeamrainbowlabs): That's odd! If it happens again, try `tldr --update` 4/11/2019, 1:17:37 AM - owenvoke (Owen Voke): @sbrl, it's the web client. 😉 4/11/2019, 1:27:45 AM - sbrl (Starbeamrainbowlabs): Ah, lol 😛 4/11/2019, 1:27:55 AM - sbrl (Starbeamrainbowlabs): CTRL + SHIFT + R then 4/11/2019, 3:00:13 AM - waldyrious (Waldir Pimenta): > Just to be sure, @waldyrious when you say "two projects" you mean the one for Season of Docs and the one for GSoC? Because I see multiple are listed under the two wiki pages. @mebeim sorry for the confusion. I meant two projects for Season of Docs. GSoC is past the org application phase anyway :) 4/11/2019, 3:01:35 AM - waldyrious (Waldir Pimenta): The wiki page still needs to be worked into two main project ideas, yeah 4/11/2019, 3:05:21 AM - waldyrious (Waldir Pimenta): @pxgamer are you up for being a mentor for Season of Docs? Either a primary or secondary mentor (the latter is not required to be as available) would be great 4/11/2019, 3:36:19 AM - mebeim (Marco Bonelli): Oh ok @waldyrious, so precisely which are the two projects? 4/11/2019, 3:36:42 AM - waldyrious (Waldir Pimenta): We have to decide that :) 4/11/2019, 3:37:24 AM - waldyrious (Waldir Pimenta): I was planning to make a proposal about that tonight but I'm still processing some notifications 4/11/2019, 3:40:27 AM - mebeim (Marco Bonelli): Ok, just wanted to be sure 😅 4/11/2019, 3:40:36 AM - waldyrious (Waldir Pimenta): :) 4/11/2019, 4:22:11 AM - owenvoke (Owen Voke): I'd be happy to be a secondary mentor. :+1: 4/11/2019, 4:24:04 AM - waldyrious (Waldir Pimenta): Awesome :) now let's wait and see if they allow me as both a mentor and a participant, otherwise we'll need someone else to fill the slot (or we could apply with only one project if needed) 4/11/2019, 4:24:43 AM - sbrl (Starbeamrainbowlabs): Cool! Could you fill out this form please, @pxgamer? https://www.google.com/url?q=https://forms.gle/a1x26WQGzURLerv66&sa=D&ust=1554828427031000&usg=AFQjCNG6rDaZdOpcLJQR3I38ye7soE8Wew 4/11/2019, 4:29:41 AM - waldyrious (Waldir Pimenta): Ok guys, so after reading through my personal notes and the wiki page with the list of ideas, I'm inclined to pick as the two projects the completeness one, and the migration to the new syntax 4/11/2019, 4:30:15 AM - waldyrious (Waldir Pimenta): (those seem to be those more likely to be at the scale of 3 months of work) 4/11/2019, 4:31:05 AM - sbrl (Starbeamrainbowlabs): The migration to the new syntax is a huge amount of work, I'm definitely inclined to agree there 4/11/2019, 4:31:19 AM - sbrl (Starbeamrainbowlabs): It also depends on action from a lot of other people 4/11/2019, 4:31:32 AM - waldyrious (Waldir Pimenta): yeah. I'm worried about the linter, though 4/11/2019, 4:31:59 AM - sbrl (Starbeamrainbowlabs): Because not everyone implements the new client spec, so they won't display correctly (despite the new client spec requiring CommonMark support) 4/11/2019, 4:32:03 AM - waldyrious (Waldir Pimenta): but in 3 months I suppose a tech writer could learn a bit about parsers :) 4/11/2019, 4:32:05 AM - sbrl (Starbeamrainbowlabs): Yeah, the linter is an issue too 4/11/2019, 4:32:23 AM - sbrl (Starbeamrainbowlabs): The linter task would have to have taken too if the page syntax is to be changed. 4/11/2019, 4:32:24 AM - waldyrious (Waldir Pimenta): I was thinking about applying for the completeness project, but I could go for the new syntax one instead 4/11/2019, 4:32:45 AM - sbrl (Starbeamrainbowlabs): Parsing is actually quite a complicated computer science topic 4/11/2019, 4:33:03 AM - sbrl (Starbeamrainbowlabs): Although hopefully the Nearly parser I've linked to can offset some of that 4/11/2019, 4:33:08 AM - waldyrious (Waldir Pimenta): yeah but our syntax is not too complex :) 4/11/2019, 4:33:12 AM - sbrl (Starbeamrainbowlabs): (I haven't used it myself just yet) 4/11/2019, 4:33:14 AM - sbrl (Starbeamrainbowlabs): true 4/11/2019, 4:33:46 AM - waldyrious (Waldir Pimenta): @mebeim, @pxgamer, @agnivade what do you think? should we move forward with those two? 4/11/2019, 4:34:38 AM - waldyrious (Waldir Pimenta): Once we decide on which ones to focus, we can flesh them out to finish our application 4/11/2019, 4:35:40 AM - waldyrious (Waldir Pimenta): In any case, at this point we only need clear problem descriptions, not full solution outlines (that's part of the program work to be done in coordination with the participants) 4/11/2019, 9:28:22 AM - agnivade (Agniva De Sarker): I would love to finish the duplicate pages move too. It's a small thing, but good to clean up. Perhaps we can club it with the completeness one ? 4/11/2019, 12:27:27 PM - owenvoke (Owen Voke): I think those seem ok! Duplicates pages seems good to me too. 4/11/2019, 12:27:47 PM - owenvoke (Owen Voke): Just wondering, for the project URL, do we just put the main GitHub org link? 4/11/2019, 12:31:24 PM - owenvoke (Owen Voke): Sorry, does anyone else get push notifs from Gitter? 4/11/2019, 12:34:18 PM - agnivade (Agniva De Sarker): I use the web client 4/11/2019, 12:36:26 PM - owenvoke (Owen Voke): Ah, same when I'm on PC. Just normally on my phone. 4/11/2019, 12:39:11 PM - owenvoke (Owen Voke): Hmm. Just interested, what if we haven't had previous experience with mentoring and collaborating with technical writers? 4/11/2019, 12:42:08 PM - agnivade (Agniva De Sarker): I guess we will just have to see how it goes 4/11/2019, 3:57:13 PM - mebeim (Marco Bonelli): I think completeness and new linter are the main ones so probably keep those and squash something into completeness 4/11/2019, 3:57:47 PM - mebeim (Marco Bonelli): Merging the list of clients isn't really a problem I could do that easily 4/11/2019, 10:39:41 PM - sbrl (Starbeamrainbowlabs): For that question, I wrote this @pxgamer: > Our project is primarily about documenting things, so we're well versed in writing documentation. We've collaborated with people through Google Summer of Code and Google Code-In, which involved collaborating over the writing of documentation. 4/11/2019, 10:40:22 PM - sbrl (Starbeamrainbowlabs): For the previous experience question, I put this: > As an open-source project, we have mentored individuals through the Google Summer of Code initiative and the Google Code-In initiative. > > As part of this, we learnt a lot about how to handle new first-time contributors to our project, and how to make the experience as smooth as possible. Our experiences here will inform the way we handle the Season of Docs. Many of the contributors who participated in GSoC and GCI did not have much experience writing 'code', so to speak, so there are a number of aspects that we can draw on to inform our approach in the Season of Docs. 4/11/2019, 11:48:25 PM - mebeim (Marco Bonelli): Oh wait I just realized, the new linter is not in the scope of Season of Docs. You know what I'd add? Creating an efficent way of managing translations, sort of what was proposed in #2793 but without all the quirks and workaraunds 🤔 4/11/2019, 11:59:59 PM - sbrl (Starbeamrainbowlabs): I think that's quite a technical challenge, @mebeim! Perhaps that's better for GSoC? 4/12/2019, 12:02:17 AM - mebeim (Marco Bonelli): Well.. it depends: if there already are tools like po4a that can handle this in a better way than what's currently proposed, that's rather easier than coding it by scratch. If there aren't, well you're right, that's big trouble, it would probably mean building a completely customized infrastructure to handle it. 4/12/2019, 12:02:40 AM - mebeim (Marco Bonelli): Either way you're probably right, that's more suitable for GSoC. 4/12/2019, 12:04:08 AM - mebeim (Marco Bonelli): And about GSoC, @sbrl what was done in the previous years and how did it go? I never took part in something like this so I don't know how well it could work. 4/12/2019, 12:05:17 AM - sbrl (Starbeamrainbowlabs): I can't actually remember. I do remember GCI, which happens from Nov~Jan ish 4/12/2019, 12:05:45 AM - sbrl (Starbeamrainbowlabs): Basically we got bunch of issues opened & setup on GitHub with a special label 4/12/2019, 12:06:02 AM - sbrl (Starbeamrainbowlabs): and we paired that with tasks on the GCI interface 4/12/2019, 12:06:16 AM - sbrl (Starbeamrainbowlabs): I don't remember GSoC though 4/12/2019, 12:07:04 AM - sbrl (Starbeamrainbowlabs): I think we've missed GSoC for this year though 4/12/2019, 12:07:11 AM - sbrl (Starbeamrainbowlabs): https://summerofcode.withgoogle.com/how-it-works/#timeline 4/12/2019, 12:14:32 AM - mebeim (Marco Bonelli): Yep we did indeed 4/12/2019, 12:16:20 AM - sbrl (Starbeamrainbowlabs): oops lol 4/12/2019, 12:17:48 AM - sbrl (Starbeamrainbowlabs): Does this count at 5 non-trivial PRs? 4/12/2019, 12:17:49 AM - sbrl (Starbeamrainbowlabs): https://github.com/tldr-pages/tldr/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Aschneiderl 4/12/2019, 12:18:12 AM - sbrl (Starbeamrainbowlabs): I think @schneiderl might be eligible to be a contributor 4/12/2019, 12:23:06 AM - mebeim (Marco Bonelli): I was wondering about that too, I did not look too much into the PRs though 4/12/2019, 12:26:10 AM - sbrl (Starbeamrainbowlabs): @pxgamer? 4/12/2019, 1:14:12 AM - owenvoke (Owen Voke): I thought about that too. Seems like it would be 4/12/2019, 1:40:34 AM - sbrl (Starbeamrainbowlabs): ok! I'll invite them as a collaborator 😃 4/12/2019, 1:45:10 AM - owenvoke (Owen Voke): :+1: 4/12/2019, 1:46:35 AM - sbrl (Starbeamrainbowlabs): Also, in #2884 should we merge it and then open a new PR with fixes? It seems like the review process in that one has been rather lengthy already 4/12/2019, 3:26:37 AM - waldyrious (Waldir Pimenta): > I would love to finish the duplicate pages move too. It's a small thing, but good to clean up. Perhaps we can club it with the completeness one ? Makes sense to me @agnivade :) good call. 4/12/2019, 3:27:39 AM - waldyrious (Waldir Pimenta): > Sorry, does anyone else get push notifs from Gitter? @pxgamer I think the mobile app only sends notifications if the web app is not open in a browser window. I have this tab pinned in my home pc so I never get mobile notifications 😟 4/12/2019, 3:28:58 AM - waldyrious (Waldir Pimenta): @sbrl I don't think we ever participated in GSoC, only GCI, but I might be misremembering. @agnivade do you recall if we did? 4/12/2019, 3:29:34 AM - waldyrious (Waldir Pimenta): If not, we should remove that reference from the application form (the responses can be edited until the submission deadline) 4/12/2019, 3:38:28 AM - waldyrious (Waldir Pimenta): @mebeim I've added the translation platform idea to the coding projects page :) https://github.com/tldr-pages/tldr/wiki/Coding-projects 4/12/2019, 3:49:15 AM - mebeim (Marco Bonelli): @waldyrious nice, thank you :) 4/12/2019, 4:17:08 AM - owenvoke (Owen Voke): Pretty sure tldr participated in GCI (there are GCI labels on issues). 4/12/2019, 4:17:24 AM - waldyrious (Waldir Pimenta): yeah, in GCI I'm sure we did 4/12/2019, 4:17:39 AM - waldyrious (Waldir Pimenta): GSoC, I think not, but I'm not 100% sure. 4/12/2019, 4:18:06 AM - waldyrious (Waldir Pimenta): @mebeim np :) I've also just merged the duplicated pages project into the completeness one, as @agnivade suggested. 4/12/2019, 4:20:05 AM - owenvoke (Owen Voke): @sbrl, I think it would make sense to merge that page and then update the tokens in a follow-up PR :+1: Or just manually commit and push the changes to their repo branch. 4/12/2019, 4:20:31 AM - sbrl (Starbeamrainbowlabs): Thanks, @pxgamer. I'll do that now 4/12/2019, 4:23:10 AM - waldyrious (Waldir Pimenta): I think the completeness project is now decently explained. Please take a look: https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects#completeness-create-missing-pages 4/12/2019, 4:28:24 AM - waldyrious (Waldir Pimenta): Next up I'll expand the syntax change project, and with that we should be good to go :) but that'll wait for later, it's late here already and I need to get going. 4/12/2019, 4:29:20 AM - sbrl (Starbeamrainbowlabs): Great, thanks @waldyrious! 4/12/2019, 4:29:38 AM - sbrl (Starbeamrainbowlabs): I think we'll only be able to actually submit 2 projects to the SoD though 4/12/2019, 4:29:50 AM - sbrl (Starbeamrainbowlabs): or at least mentor 2 people 4/12/2019, 4:29:52 AM - waldyrious (Waldir Pimenta): That's what I meant. The top 2 in the wiki page 4/12/2019, 4:29:57 AM - sbrl (Starbeamrainbowlabs): ahhh ok 4/12/2019, 4:30:26 AM - waldyrious (Waldir Pimenta): (I don't think we should delete the other ones since it's useful to keep them described somewhere) 4/12/2019, 4:30:52 AM - sbrl (Starbeamrainbowlabs): Indeed! 4/12/2019, 4:32:14 AM - waldyrious (Waldir Pimenta): Alright, I'll leave for today. Do let me know what you think of the completeness project's description. For a project idea to be fleshed out by the applicants, it seems reasonably complete (heh) to me. 4/12/2019, 4:32:34 AM - waldyrious (Waldir Pimenta): 👋 4/12/2019, 4:32:56 AM - sbrl (Starbeamrainbowlabs): It looks great! Thanks so much 😺 4/12/2019, 5:01:26 AM - mebeim (Marco Bonelli): I'm adding a separator on the wiki page so it's clear which projects are up for SoD and which are not. 4/12/2019, 5:02:30 AM - mebeim (Marco Bonelli): By the way, I can help in any of those, so you can just assign me where you need guys. 4/12/2019, 5:08:22 AM - sbrl (Starbeamrainbowlabs): :+1: 4/12/2019, 5:08:35 AM - sbrl (Starbeamrainbowlabs): Feel free to work on whatever takes your fancy :-) 4/12/2019, 5:09:14 AM - sbrl (Starbeamrainbowlabs): Personally I just follow wherever my inspiration takes me in my personal time 4/13/2019, 4:41:13 AM - waldyrious (Waldir Pimenta): @mebeim by "assign" did you mean as a mentor for Season of Docs, or as in doing those tasks yourself? I understood the former but it looks like @sbrl read the latter. 4/13/2019, 4:43:22 AM - mebeim (Marco Bonelli): former, I mean since I'm a secondary mentor I can help whichever of the two needs it 4/13/2019, 4:44:38 AM - mebeim (Marco Bonelli): i will also contribute personally from time to time of course 4/13/2019, 4:45:34 AM - waldyrious (Waldir Pimenta): :+1: that's great, thanks! Hopefully we won't need to stretch anyone too thin with the mentorship duties. 4/17/2019, 4:28:26 AM - schneiderl (Lucas Gabriel Schneider): Hi there, I have a little doubt about homepages: how do you guys feel about using the actual man pages as homepages to tldr pages? As an example: using http://man7.org/linux/man-pages/man1/script.1.html to tldr script.md files. 4/17/2019, 4:32:20 AM - mebeim (Marco Bonelli): That isn't really an homepage. I don't know how appropriate it would be to add it given that's basically the same as doing `man script`, basically duplicated information IMHO. 4/17/2019, 4:32:53 AM - schneiderl (Lucas Gabriel Schneider): Another thing that I've noticed and felt kinda awkward: On script.md files we have a description that is different on windows and linux pages. It doesnt seem right as the command is in fact the same, just the way it is used that might be different. I was thinking about creating a script to help us "copy" the descriptions from one page to another in cases we have them duplicated. (Keeping the examples untouched, of course). I know that it is possible to have completly different commands under windows and linux pages so I would double check the copied descriptions after running the script to make sure the modifications make sense. 4/17/2019, 4:35:05 AM - waldyrious (Waldir Pimenta): My understanding is that we should add links to the best reference page that provides more details about the tool -- either an official website for the tool if one exists, or the readme of the project, or, indeed, a man page, if it is the most complete and reliable resource on the tool. 4/17/2019, 4:36:29 AM - waldyrious (Waldir Pimenta): We will necessarily duplicate information from manpages of the tools we cover; that's by design: a manpage provides a complete usage reference, and we provide a summary of it. 4/17/2019, 4:36:41 AM - waldyrious (Waldir Pimenta): @mebeim please correct me if I misinterpreted you. 4/17/2019, 4:39:25 AM - waldyrious (Waldir Pimenta): As for the synchronization of descriptions, I do agree it makes sense to keep them consistent. If we're ambitious, we could even have an automated check to point out mismatches (like a readme badge or a PR check). But that's me dreaming out loud 😛 4/17/2019, 4:41:45 AM - schneiderl (Lucas Gabriel Schneider): I don't see the PR check as something that unachievable :) I would be glad to work on something to keep everything synced. 4/17/2019, 4:41:51 AM - mebeim (Marco Bonelli): I must be misinterpreting the term "homepage" then. I thought it was intended for linking actual project homepages or CLI documentations, not just a web-hosted manual page. Of course I'm going to do `man X` if I don't find the example I need with `tldr X`, I don't really feel like pointing to `man` pages somehow adds value to a tldr page. 4/17/2019, 4:42:45 AM - schneiderl (Lucas Gabriel Schneider): @mebeim thats's the way I felt too. 4/17/2019, 4:42:48 AM - mebeim (Marco Bonelli): And yes, keeping translations synced is basically the most challenging aspect of this project since when they were introduced. 4/17/2019, 4:42:51 AM - waldyrious (Waldir Pimenta): That's great to hear, @schneiderl! I'd love to see that in place. 4/17/2019, 4:43:33 AM - waldyrious (Waldir Pimenta): I think we all agree that manpages are often not that helpful or convenient (it's why this whole project exists!) 4/17/2019, 4:46:31 AM - waldyrious (Waldir Pimenta): that said, if no better resource exist, I don't see a problem in linking to a hosted manpage. The link shouldn't be interpreted as "Homepage:" or "Official website:", but rather "More information:". It's about helping people figure out what exactly the page is about (since often the names alone are ambiguous), and where to learn more about it. 4/17/2019, 4:47:34 AM - mebeim (Marco Bonelli): If that's the case, then allow me to argue that saying "Homepage" feels somehow confusing. 4/17/2019, 4:47:39 AM - waldyrious (Waldir Pimenta): So, case by case, we should decide what's the best available resource that can fill this role. If a manpage is the best we can arrange for a given page, it is what it is. I think it would be a disservice to users to withhold this info from them and show no URL at all. 4/17/2019, 4:48:52 AM - mebeim (Marco Bonelli): I get the idea though, could make sense. 4/17/2019, 4:48:53 AM - waldyrious (Waldir Pimenta): Yes, I agree the name should probably be different. IIRC we did discuss what to call it, and possibly decided to just start adding links to the pages, which was the most time-consuming part, since we could always change the label later. 4/17/2019, 4:49:16 AM - sbrl (Starbeamrainbowlabs): I was under the impression that you can use anything that;s most appropriate: i.e. `Homepage:`, `Documentation:`, etc. 4/17/2019, 4:49:47 AM - sbrl (Starbeamrainbowlabs): I thought it was, in order of preference: CLI Reference Docs, Project Homepage 4/17/2019, 4:49:49 AM - waldyrious (Waldir Pimenta): I would get the link to the issue where this was discussed, but I'm currently in the middle of working the Season of Docs project description, so my hands are a bit full :) 4/17/2019, 4:50:17 AM - waldyrious (Waldir Pimenta): That's right, @sbrl, that's the order of usefulness for readers :) 4/17/2019, 4:50:37 AM - waldyrious (Waldir Pimenta): (in terms of what our mission is) 4/17/2019, 4:50:53 AM - sbrl (Starbeamrainbowlabs): I would probably advise against linking to hosted man pages if possible. Yeah! It's all about what would be most useful for readers 😃 4/17/2019, 4:50:58 AM - mebeim (Marco Bonelli): Oh yeah so it's basically part of the description rather than a separate kind of section, that makes sense. Using different labels seems like the way to go. 4/17/2019, 4:51:23 AM - sbrl (Starbeamrainbowlabs): Use whatever label seems appropriate. 4/17/2019, 4:51:29 AM - waldyrious (Waldir Pimenta): If we could find something generic enough to work for all cases, I'd be OK with that 4/17/2019, 4:51:34 AM - sbrl (Starbeamrainbowlabs): I think we need to update the style guidelines if we haven't already done so 4/17/2019, 4:51:49 AM - sbrl (Starbeamrainbowlabs): Since this feature is rather new 4/17/2019, 4:52:01 AM - mebeim (Marco Bonelli): Yeah I would advise that too... fact is, when I was writing my own client I also thought about implementing an automatic fallback to `man` if the page is not found haha 4/17/2019, 4:52:33 AM - mebeim (Marco Bonelli): but of course we're talking about pages that are found here 4/17/2019, 4:55:25 AM - mebeim (Marco Bonelli): Either way, I don't necessarily think linking to the web-hosted man page is a problem, I was just thinking about how useful I'd find it as a user, and the answer is "not that useful" in my case. 4/17/2019, 4:56:26 AM - waldyrious (Waldir Pimenta): Whatever provides additional info is better than nothing 4/17/2019, 4:57:07 AM - waldyrious (Waldir Pimenta): man pages are typically not ideal, but as a last resort, I think it's perfectly acceptable. In fact, some mapages are quite good :) 4/17/2019, 5:20:59 AM - waldyrious (Waldir Pimenta): I've finally completed the first draft for the syntax update project, take a look! https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects 4/17/2019, 5:22:54 AM - waldyrious (Waldir Pimenta): Also, I've received confirmation from the program organizers that I can apply as a participant. So we'd need two other people to be primary and secondary mentor in that project 4/17/2019, 5:23:19 AM - waldyrious (Waldir Pimenta): right now @sbrl and @pxgamer are suggested as potential mentors for the completeness project 4/17/2019, 5:23:59 AM - waldyrious (Waldir Pimenta): If @mebeim would take up the syntax one, then we'd only need one more person as a secondary / back-up mentor. What do you guys think? 4/17/2019, 5:24:43 AM - waldyrious (Waldir Pimenta): (Of course, I'll still help with mentoring unofficially) 4/17/2019, 5:32:21 AM - mebeim (Marco Bonelli): Wait so are you *officially* mentoring or not? I see your name under the syntax project. 4/17/2019, 9:41:23 AM - agnivade (Agniva De Sarker): My thinking was that the Homepage link was for user made projects which usually have documentation on a github page or a dedicated website. That's how it originated, where folks were unable to figure out the true documentation of a command. 4/17/2019, 9:42:45 AM - agnivade (Agniva De Sarker): To me, it is not compulsory for every page to have a Homepage link. Only pages which have their documentation on github or someplace else which is not a man page. 4/17/2019, 9:42:52 AM - agnivade (Agniva De Sarker): But changing the label is also fine with me. 4/17/2019, 9:43:10 AM - agnivade (Agniva De Sarker): In any case, I agree we should write it down somewhere so that everybody is on the same page. 4/17/2019, 12:40:00 PM - waldyrious (Waldir Pimenta): Tee hee... "on the same page" 😛 4/17/2019, 12:41:50 PM - waldyrious (Waldir Pimenta): @mebeim right, I should have removed that. I don't think I can join the program both as a mentor and a participant 4/17/2019, 12:48:10 PM - waldyrious (Waldir Pimenta): Done, I've updated the page. 4/17/2019, 12:51:33 PM - waldyrious (Waldir Pimenta): As for the links, maybe we could call them "Full documentation" to better reflect the intent? I.e. where one would go to get the non-tldr version of the docs. For that reason, I wouldn't exclude linking to a manpage if no other documentation is available 4/17/2019, 3:30:05 PM - sbrl (Starbeamrainbowlabs): I'd be willing to mentor (or at least provide support for) the syntax one if need be. 4/17/2019, 3:30:22 PM - sbrl (Starbeamrainbowlabs): Esp. surrounding linter updates 4/17/2019, 3:30:59 PM - sbrl (Starbeamrainbowlabs): Do we have an idea of how many people we will be mentoring? 4/17/2019, 5:14:48 PM - waldyrious (Waldir Pimenta): I think it would work best if the communication happened mostly in this channel, so everyone could chip in 4/17/2019, 5:17:10 PM - waldyrious (Waldir Pimenta): Of course, the primary mentor should be directly contactable if needed, but we should encourage that being more for exceptional or private matters. 4/17/2019, 5:52:00 PM - sbrl (Starbeamrainbowlabs): Yeah, good idea! 4/17/2019, 6:57:46 PM - mebeim (Marco Bonelli): Have you guys ever thought about moving to Slack? 4/17/2019, 6:59:10 PM - mebeim (Marco Bonelli): It has some cool features like the possibility to create multiple channels, private channels etc 4/17/2019, 6:59:52 PM - mebeim (Marco Bonelli): I don't know if using this chat room for both projects is a good idea, there will probably be confusion 4/17/2019, 7:26:55 PM - mebeim (Marco Bonelli): By the way, there's kind of a problem with the Syntax update project: looks like more of a coding project than a documentation project. It would require figuring out how to update the build process without breaking the clients, and also how to update the linter (possibly creating a new one). 4/17/2019, 8:08:26 PM - agnivade (Agniva De Sarker): We had discussed about moving to slack long time back. There is even a slack channel which we used for some time. But eventually we decided against it because gitter has good integration with git. Things like issue nos. and stuff gets automatically linked. Not sure if there are slack plugins which does that automatically. 4/17/2019, 8:15:13 PM - mebeim (Marco Bonelli): There is, but I did not look into that much. Looks like it can track repos on various events https://slack.github.com/ 4/17/2019, 8:15:23 PM - sbrl (Starbeamrainbowlabs): I don't really like slack myself, as you've got to create a new account for every workspace you join 4/17/2019, 8:15:57 PM - sbrl (Starbeamrainbowlabs): In Gitter you can create multiple rooms IIRC 4/17/2019, 8:16:45 PM - mebeim (Marco Bonelli): Yeah that's something I also find strange about Slack, I have multiple workspaces with the same email but had to register multiple times, weird 4/17/2019, 8:17:32 PM - mebeim (Marco Bonelli): BTW I was just thinking about how things could go for the projects if we only use this room 4/17/2019, 8:24:18 PM - sbrl (Starbeamrainbowlabs): I see. It depends how much IM interaction is needed. 4/17/2019, 8:24:30 PM - sbrl (Starbeamrainbowlabs): If it's a lot, then perhaps a separate room would be a good idea 4/20/2019, 8:29:58 PM - mebeim (Marco Bonelli): Hi guys, is it possible to check if someone as signed the CLA given their e-mail address? 4/20/2019, 8:34:42 PM - mebeim (Marco Bonelli): I'm asking because of #2866, I could easily change the commit author to be `ghostslayer989 ` and then merge, but I don't know if that address has signed the CLA. 4/20/2019, 9:29:32 PM - sbrl (Starbeamrainbowlabs): Hrm. Not sure 4/20/2019, 9:30:03 PM - sbrl (Starbeamrainbowlabs): Might only be 1 way to find out lol 4/20/2019, 9:32:39 PM - mebeim (Marco Bonelli): Well, I'll try to do that eventually if the guy does not respond for a while... before closing the PR. 4/20/2019, 9:33:37 PM - mebeim (Marco Bonelli): Looks like he just made those three automated PRs and then ran away 😆 4/20/2019, 9:37:49 PM - sbrl (Starbeamrainbowlabs): I'd be wary of changing the email address in a PR for CLA reasons without their consent though 4/20/2019, 9:40:53 PM - mebeim (Marco Bonelli): Well, they said they signed the CLA. And that's a noreply github email. I don't see any issue in trying that. 4/20/2019, 9:42:29 PM - mebeim (Marco Bonelli): So if I change that: either 1) the check passes because they agreed to CLA and we can merge; or 2) the check does not pass, the PR gets closed because we cannot merge it. 4/20/2019, 9:49:24 PM - sbrl (Starbeamrainbowlabs): Ah, I see. I haven't looked at the PR yet. Yeah, I'd say changing the email account in the PR to match that of their GH account would be fine then 4/20/2019, 9:53:50 PM - mebeim (Marco Bonelli): How come you didn't look? You even commented on it 😂 4/20/2019, 9:59:45 PM - sbrl (Starbeamrainbowlabs): I did? One sec lol I check my notifications in waves, and I wasn't planning on doing another wave right now 4/20/2019, 10:00:30 PM - sbrl (Starbeamrainbowlabs): Ah, that one! 4/20/2019, 10:00:33 PM - mebeim (Marco Bonelli): Oh yeah no problem 4/20/2019, 10:00:35 PM - sbrl (Starbeamrainbowlabs): Yeah, I see what you mean 4/20/2019, 10:00:42 PM - mebeim (Marco Bonelli): Yep.. 4/20/2019, 10:00:47 PM - sbrl (Starbeamrainbowlabs): Yeah, I think we should do it ourselves then 4/20/2019, 10:01:01 PM - mebeim (Marco Bonelli): Will do if they don't respond 4/20/2019, 10:02:37 PM - sbrl (Starbeamrainbowlabs): Thanks 4/20/2019, 10:02:47 PM - mebeim (Marco Bonelli): Duty! Haha 4/21/2019, 2:23:04 AM - waldyrious (Waldir Pimenta): Regarding slack, it's not just the saner account system (only one as opposed to multiple) and the native integration with git hosts that led us to stick with it. It's also the public availability openness it operates with, which is very much the opposite of the slack ethos 4/21/2019, 2:23:45 AM - waldyrious (Waldir Pimenta): Openness in various ways: - people who aren't in the channel can see the discussions, so there isn't an outsider/insider division (discussions here are as public as issue/PR threads on github) - messages can be linked via URL and used as reference on github, etc (useful to provide transparency for community decisions) - anyone can join the room uninvited (troublemakers can still be booted by the admins, but in practice that has never happened) - unlimited archives are free and available to anyone (on slack, they are hidden behind a paywall after some limit) 4/21/2019, 2:28:06 AM - waldyrious (Waldir Pimenta): Not to mention the tool itself is open source 😃 4/21/2019, 2:30:21 AM - waldyrious (Waldir Pimenta): I any case, we can create private rooms here on gitter. But usually we just use one-to-one conversation if any sensitive info (e.g. personal emails, etc.) needs to be discussed. That has worked out so far, but if we find the channel flooded with discussion on a particular topic that doesn't interest most, we can create a channel for it. Hopefully it doesn't need to be a private one :) 4/21/2019, 2:31:32 AM - mebeim (Marco Bonelli): Makes total sense, I understand 4/21/2019, 2:32:03 AM - waldyrious (Waldir Pimenta): > By the way, there's kind of a problem with the Syntax update project: looks like more of a coding project than a documentation project. It would require figuring out how to update the build process without breaking the clients, and also how to update the linter (possibly creating a new one). Good point, I'll try to clean it up a bit 4/21/2019, 2:38:37 AM - waldyrious (Waldir Pimenta): By the way, I made some edits to the project descriptions earlier today, and I think they're now sufficiently detailed for the program. The deadline is close so we should finalize the application form soon 4/21/2019, 2:42:30 AM - waldyrious (Waldir Pimenta): @sbrl what else do we have to prepare besides the project list? Does the application form ask for other stuff we haven't provided yet? 4/21/2019, 2:49:17 AM - mebeim (Marco Bonelli): @waldyrious are you talking about this form? https://docs.google.com/forms/d/e/1FAIpQLSe-JjGvaKKGWZOXxrorONhB8qN3mjPrB9ZVkcsntR73Cv_K7g/viewform 4/21/2019, 2:50:08 AM - waldyrious (Waldir Pimenta): That too. But I was asking about the admin one 4/21/2019, 2:57:03 AM - waldyrious (Waldir Pimenta): @mebeim do these changes help with making the syntax update project more fitting to a documentation program? https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects/_compare/423dd0fcc878310859a72fe9f58baeba3ebda069...bc7257b3bd43716240715eb78bdf16d47d44c1e3 4/21/2019, 3:01:46 AM - mebeim (Marco Bonelli): just saw that, they do for sure IMHO 4/21/2019, 3:02:02 AM - waldyrious (Waldir Pimenta): Great to hear :) 4/21/2019, 3:02:07 AM - mebeim (Marco Bonelli): Much better wording, good job 4/21/2019, 3:03:28 AM - mebeim (Marco Bonelli): BTW, for the one form I linked no there's not much to add. It only asked for mentors' names, name of the open source project and previous experience. I did not see the admin one. 4/21/2019, 3:04:23 AM - waldyrious (Waldir Pimenta): OK, cool. I think the admin form might ask for at least the project ideas' titles, and possibly a link to a page describing them 4/21/2019, 3:04:41 AM - waldyrious (Waldir Pimenta): Or maybe an attachment with the full descriptions 4/21/2019, 3:05:30 AM - waldyrious (Waldir Pimenta): Overall, what do you think of the descriptions right now? Could they be submitted as-is, or do you see improvements we could make in terms of structure, lack of detail, missing context, etc.? 4/21/2019, 3:08:13 AM - waldyrious (Waldir Pimenta): Ah, they say this in the [admin guide](https://developers.google.com/season-of-docs/docs/admin-guide): > You should publish your project ideas on a public web page, in a blog post, or in some other publicly visible document. When you create your organization's application for Season of Docs, you should include a link to your project ideas. 4/21/2019, 3:11:40 AM - waldyrious (Waldir Pimenta): And here are the [guidelines for project ideas](https://developers.google.com/season-of-docs/docs/project-ideas). 4/21/2019, 3:12:12 AM - waldyrious (Waldir Pimenta): (Another advantage of gitter over slack: support for markdown-formatted links 😃) 4/21/2019, 3:53:14 AM - mebeim (Marco Bonelli): Yeah that's a feature I don't understand why they don't have haha 4/21/2019, 3:53:33 AM - mebeim (Marco Bonelli): When's the deadline? 4/21/2019, 4:03:59 AM - mebeim (Marco Bonelli): Oh it's the 23rd, ok... I'll take a good look at everything tomorrow (21) (midnight here) 4/21/2019, 4:39:44 AM - sbrl (Starbeamrainbowlabs): @waldyrious: The application form I filled out didn't specify anything else I don't think. Only that the secondary admin should fill out a form (done), and that mentors who are not the primary admin should fill out a third form that I linked to above 4/21/2019, 4:41:05 AM - sbrl (Starbeamrainbowlabs): Yeah, it did ask for a link to the contribution homepage and the page containing the list of projects or something, which I interpreted to be the same thing, and pasted in the link to that page 4/21/2019, 4:42:14 AM - sbrl (Starbeamrainbowlabs): If I made a mistake in the form, I'm hoping that some googly person will contact me somehow 4/21/2019, 4:42:44 AM - sbrl (Starbeamrainbowlabs): Also, that's a dead link @waldyrious 4/21/2019, 4:44:24 AM - sbrl (Starbeamrainbowlabs): Another also, I've just seen https://github.com/tldr-pages/tldr/wiki/Minimum-specifications-for-TLDR-command-line-clients 4/21/2019, 4:44:38 AM - sbrl (Starbeamrainbowlabs): Which seems rather outdated, considering that we have a client spec now 4/21/2019, 5:05:26 AM - waldyrious (Waldir Pimenta): Hmm. "a link to the contribution homepage" sounds like they are talking about the contribution guidelines that are typically in a CONTRIBUTING.md file. On the other hand, "the page containing the list of projects" sounds like the wiki page we've been working on with project ideas. So I'd venture saying those aren't supposed to be the same link. 4/21/2019, 5:07:07 AM - waldyrious (Waldir Pimenta): What link is dead, @sbrl? Both links I added above (admin guide and guidelines for project ideas) work for me. 4/21/2019, 5:07:36 AM - sbrl (Starbeamrainbowlabs): This one: https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects/_compare/423dd0fcc878310859a72fe9f58baeba3ebda069...bc7257b3bd43716240715eb78bdf16d47d44c1e3 4/21/2019, 5:07:52 AM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/0BXl/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/0BXl/image.png) 4/21/2019, 5:08:42 AM - sbrl (Starbeamrainbowlabs): Hrm. I can't remember the exact wording, but yeah - I might have got the 2 mixed up lol 4/21/2019, 5:10:41 AM - waldyrious (Waldir Pimenta): As for the client spec wiki page, yeah, there had been efforts in the past in this direction but we never managed to finalize them. There might still be useful bits on the wiki page which should be recovered into the client spec, so that the wiki page can be safely deleted. 4/21/2019, 5:13:56 AM - sbrl (Starbeamrainbowlabs): True 4/21/2019, 1:06:31 PM - waldyrious (Waldir Pimenta): Oh I see what happened. I renamed the wiki page from "projects" to "project ideas" to match their recommendations, and now that diff link is broken. 4/21/2019, 1:11:53 PM - waldyrious (Waldir Pimenta): I can't seem to find a way to get the diff now, since the page was renamed. I'm afraid we'd have to clone the wiki locally to see the diff. Github really needs to start following renaming when showing history of files... 4/21/2019, 1:15:25 PM - waldyrious (Waldir Pimenta): Anyway, we have 2 days left to submit the application. If the wording looks good to you all, then the only thing we need now is a secondary mentor for the syntax update project. Maybe @schneiderl would be up for it? 4/21/2019, 3:13:40 PM - sbrl (Starbeamrainbowlabs): Ah, I see. that will break the page names int he form I submitted too 4/21/2019, 3:13:52 PM - sbrl (Starbeamrainbowlabs): Do you have the link for that so I can edit it please? 4/21/2019, 3:14:14 PM - sbrl (Starbeamrainbowlabs): (And Happy Easter!) 4/21/2019, 3:33:34 PM - waldyrious (Waldir Pimenta): What do you mean? The link to the new location of the project list? That would be https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-project-ideas 4/21/2019, 3:34:47 PM - waldyrious (Waldir Pimenta): If I understood correctly, the form responses can be edited up until the submission deadline, so you should be able to adjust the URL 4/21/2019, 3:36:50 PM - waldyrious (Waldir Pimenta): Or do you mean a link to the form? I think you should get a personalized link at the end of the form submission process, which you can use edit your responses. They would probably have emailed this to you the first time you submitted the form. 4/21/2019, 3:37:26 PM - waldyrious (Waldir Pimenta): That way the form should be preloaded with your answers and you wouldn't need to re-enter all the information again 4/21/2019, 3:37:37 PM - waldyrious (Waldir Pimenta): But let me know if you didn't get such a link 4/21/2019, 3:38:05 PM - waldyrious (Waldir Pimenta): Happy Easter to you too and everyone else here :) 4/21/2019, 3:39:42 PM - sbrl (Starbeamrainbowlabs): Ah, yeah! I forgot I got a link in an email 4/21/2019, 3:39:43 PM - sbrl (Starbeamrainbowlabs): thanks 4/21/2019, 3:42:08 PM - sbrl (Starbeamrainbowlabs): Ah, and it's just "Link to project ideas list" in my form 4/21/2019, 3:42:22 PM - sbrl (Starbeamrainbowlabs): It looks like a mis-remembered it 4/21/2019, 3:42:42 PM - waldyrious (Waldir Pimenta): Nice. So hopefully our wiki page is in good enough shape 4/21/2019, 3:43:43 PM - waldyrious (Waldir Pimenta): Did you read it after the edits I did yesterday? I added a bit more context in the beginning to match [their recommendations](https://developers.google.com/season-of-docs/docs/project-ideas) 4/21/2019, 3:45:54 PM - waldyrious (Waldir Pimenta): It's bothering me a lot that the wiki page doesn't have the edit history easily accessible. I'll rename it back to the original title 😟 4/21/2019, 3:46:58 PM - waldyrious (Waldir Pimenta): Ok, done: https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects/_history 4/21/2019, 5:50:27 PM - mebeim (Marco Bonelli): Should we make those into real GH projects? 4/21/2019, 7:31:54 PM - sbrl (Starbeamrainbowlabs): Oh yeah! That's a thing right? I totally forgot about that 4/21/2019, 7:32:03 PM - sbrl (Starbeamrainbowlabs): And yeah I did! They look great 😃 4/21/2019, 7:42:28 PM - mebeim (Marco Bonelli): So, just to be sure I'm up-to-date... I filled the one form for mentors you linked days ago. The two projects seem to have an appropriate description and we submitted the admin form (which I did not see but I assume it was done, right?). So is there anything else that needs to be done or are we ok? 4/21/2019, 8:01:09 PM - sbrl (Starbeamrainbowlabs): Yep, that's right 4/21/2019, 8:01:13 PM - sbrl (Starbeamrainbowlabs): I think we're good to go 4/21/2019, 8:30:17 PM - agnivade (Agniva De Sarker): Anything to be done from my end ? 4/21/2019, 8:36:40 PM - mebeim (Marco Bonelli): @agnivade Don't know, were you up for mentoring? I forgot. 4/21/2019, 8:58:35 PM - agnivade (Agniva De Sarker): Nope, just admin 4/21/2019, 8:59:26 PM - mebeim (Marco Bonelli): Ok, then I think we are fine... except we might need another person as secondary-mentor for the syntax project. 4/21/2019, 9:00:14 PM - agnivade (Agniva De Sarker): We also have @mfrw 4/22/2019, 2:18:50 AM - sbrl (Starbeamrainbowlabs): Did @pxgamer sign up? 4/23/2019, 1:52:59 AM - waldyrious (Waldir Pimenta): I just sent an email via the mailing list with the current status of our application and what needs to be done 4/23/2019, 1:54:01 AM - waldyrious (Waldir Pimenta): The deadline is tomorrow :) but I think we're pretty much done. Let's make sure we don't miss any details. Please check the email when you can! 4/23/2019, 2:18:50 AM - mebeim (Marco Bonelli): Got it, I replied to the e-mail, but let me also write here: I'd say this is more or less the last ping before deciding what to do, so: 1) @pxgamer make sure you've submitted [the mentor form](https://docs.google.com/forms/d/e/1FAIpQLSe-JjGvaKKGWZOXxrorONhB8qN3mjPrB9ZVkcsntR73Cv_K7g/viewform); 2) @agnivade, @mfrw and @schneiderl: any of you would like to be a second mentor for [the syntax update project](https://github.com/tldr-pages/tldr/wiki/Season-of-Docs-projects)? If so, please let us know and fill the form ASAP since we're basically on the deadline already. You should know what's the goal of the project and also a rough idea on what to do to get it started though. I am also ok to apply with only one project if you guys don't want or don't have much time to mentor (this project feels more about scripting/coding than a documenting imho) so don't feel obliged in any way! 4/23/2019, 2:24:26 AM - waldyrious (Waldir Pimenta): Thanks @mebeim :) I'd also add that the mentors (especially the secondary ones) are not supposed to be particularly versed on the details of each project; the role is mostly to provide a stable channel of communication with the participants; and in the case of the secondary mentor, a back-up in case the primary one becomes temporarily unavailable. So it shouldn't require much effort or dedication. 4/23/2019, 2:25:04 AM - waldyrious (Waldir Pimenta): Ideally the discussions about the projects should mostly happen here on Gitter, so the technical mentorship duties will be shared by everyone here who can help. 4/23/2019, 2:30:02 AM - owenvoke (Owen Voke): I have now submitted the form. Apologies for my lack of action, I have been very busy with personal matters over the last few days. 4/23/2019, 2:30:58 AM - sbrl (Starbeamrainbowlabs): No problem, @pxgamer :-) 4/23/2019, 2:31:15 AM - waldyrious (Waldir Pimenta): @pxgamer no problem at all, that's totally understandable :) thanks for taking the time to do it 4/23/2019, 2:31:33 AM - mebeim (Marco Bonelli): @pxgamer thanks, we just needed an ACK 😉 4/23/2019, 2:32:43 AM - sbrl (Starbeamrainbowlabs): Was the email entitled "Application to Google Season of Docs"? 4/23/2019, 2:33:23 AM - mebeim (Marco Bonelli): @sbrl yep 4/23/2019, 2:33:33 AM - sbrl (Starbeamrainbowlabs): Cool, thanks! 4/23/2019, 2:34:14 AM - sbrl (Starbeamrainbowlabs): Regarding a secondary syntax mentor, I'm probably qualified since I've done a module at University entitled _Languages and Compilers_, in which I learnt about parsing, and wrote a context-free compiler with flex+bison, which is very similar to the tldr linter. 4/23/2019, 2:35:07 AM - mebeim (Marco Bonelli): I'm doing that next year! Sucks that I didn't have the opportunity to learn about the topic already. 4/23/2019, 2:36:25 AM - sbrl (Starbeamrainbowlabs): Yeah, I can certainly recommend it! It's a fascinating topic to learn about. I had a great lecturer too, so I had a great time with it. It's no walk in the park though. Apart from _3D Graphics and Simulation_, it's probably the hardest module I did at undergraduate level (I'm doing an Msc now). 4/23/2019, 2:37:36 AM - waldyrious (Waldir Pimenta): When filling the mentor registration form do they ask what project the mentor will be associated with? If not, we could swap things up later on to whatever distribution makes more sense :) 4/23/2019, 2:38:29 AM - sbrl (Starbeamrainbowlabs): I don't think they did, no 😛 4/23/2019, 2:39:05 AM - waldyrious (Waldir Pimenta): cool, that makes things easier for us :) 4/23/2019, 2:41:23 AM - waldyrious (Waldir Pimenta): Game of Thrones is starting, talk to you guys later! 4/23/2019, 2:42:42 AM - mebeim (Marco Bonelli): Haha have fun with that 4/23/2019, 7:39:27 AM - mfrw (Muhammad Falak R Wani): @mebeim yep I would love to be a mentor. Sorry I was busy with some personal stuff at home and was not active on github. I am back now :) 4/23/2019, 8:40:03 AM - mebeim (Marco Bonelli): @mfrw perfect :) fill out the form, looks like we're all set 4/23/2019, 9:22:14 AM - mebeim (Marco Bonelli): ([this one](https://docs.google.com/forms/d/e/1FAIpQLSe-JjGvaKKGWZOXxrorONhB8qN3mjPrB9ZVkcsntR73Cv_K7g/viewform)) 4/23/2019, 10:56:42 AM - agnivade (Agniva De Sarker): Great, looks like we are good to go 4/23/2019, 2:22:51 PM - waldyrious (Waldir Pimenta): Yay :) 4/23/2019, 9:45:57 PM - mfrw (Muhammad Falak R Wani): @mebeim done :) 4/23/2019, 9:46:34 PM - mebeim (Marco Bonelli): wp 4/23/2019, 10:04:28 PM - sbrl (Starbeamrainbowlabs): What does wp mean, @mebeim? 4/23/2019, 10:07:45 PM - mebeim (Marco Bonelli): "Well Played", haha, online gaming jargon 4/23/2019, 10:09:40 PM - sbrl (Starbeamrainbowlabs): Ah, lol 4/24/2019, 12:31:19 AM - waldyrious (Waldir Pimenta): Great, so now we just have to wait, right? 4/24/2019, 12:38:01 AM - mebeim (Marco Bonelli): Looks like so 👀 1/14/2023, 3:26:18 PM - unmem (unmem) joined the room 4/24/2019, 3:53:44 PM - unmem (unmem): Why find an non-existing command takes so long time ? :help: 4/24/2019, 3:54:00 PM - unmem (unmem): does it need an network to work? 4/24/2019, 4:18:59 PM - sbrl (Starbeamrainbowlabs): Hey, @unmem! Which client are you using? 4/24/2019, 4:34:20 PM - unmem (unmem): terminal client 4/24/2019, 4:34:54 PM - unmem (unmem): ➜ tldr abcdefg This page doesn't exist yet! Submit new pages here: https://github.com/tldr-pages/tldr 4/24/2019, 4:35:06 PM - unmem (unmem): and run 5s 4/24/2019, 4:37:05 PM - unmem (unmem): 5 seconds 4/24/2019, 5:20:09 PM - agnivade (Agniva De Sarker): @unmem - There are various terminal clients depending on the programming language. So it depends on what it is doing. Some clients may take from the network, some keep a cache of it. Sometimes, if it cannot find a page, then it may choose to download the page cache again just to check if the page has been newly added. 4/24/2019, 5:53:28 PM - mebeim (Marco Bonelli): @unmem that's unfortunate, some clients are indeed not that much optimized or may try to re-download a new cache, as @agnivade pointed out 4/24/2019, 6:14:10 PM - sbrl (Starbeamrainbowlabs): Umm there are over a dozen terminal clients, @unmem. See the list here: https://github.com/tldr-pages/tldr/#clients 4/25/2019, 11:16:42 AM - unmem (unmem): i have check the version is `tldr-cpp-client` by using `man tldr` 4/25/2019, 11:18:27 AM - unmem (unmem): and i search the github https://github.com/tldr-pages/tldr-cpp-client/blob/0603faf4280af75315408974d091949cf2929ec3/src/tldr.c#L158-L159 maybe it need network 4/25/2019, 2:52:10 PM - sbrl (Starbeamrainbowlabs): Yeah. Looks like if a page doesn't exist locally, it tries updating the local cache before telling you that it doesn't exist. 4/25/2019, 2:52:35 PM - sbrl (Starbeamrainbowlabs): If this behaviour is undesirable, you could always open an issue asking for a configiuration directive, @unmem 4/26/2019, 6:51:28 AM - unmem (unmem): maybe the truth is here: https://github.com/tldr-pages/tldr-cpp-client/blob/0603faf4280af75315408974d091949cf2929ec3/src/parser.c#L211-L223, anyway i open a issue at https://github.com/tldr-pages/tldr-cpp-client/issues/45 4/26/2019, 2:58:31 PM - sbrl (Starbeamrainbowlabs): Thanks, @unmem 😺 4/30/2019, 2:11:24 AM - mebeim (Marco Bonelli): Just as I thought, I changed the e-mail in the commit and now it is correctly recognized as CLA signed: https://github.com/tldr-pages/tldr/pull/2866 4/30/2019, 2:26:56 AM - mebeim (Marco Bonelli): Also, I am not sure about this... why do we need `husky` (https://www.npmjs.com/package/husky) in our `package.json` as a dependency? It doesn't look like we are using it. Am I missing something? 4/30/2019, 3:20:17 AM - sbrl (Starbeamrainbowlabs): Hmmm, not sure. @agnivade? 4/30/2019, 4:18:25 AM - owenvoke (Owen Voke): Husky is used to link Git hooks on npm install. When you install `npm i`, it will set up a commit hook to run `npm test` before each commit. 4/30/2019, 4:21:05 AM - owenvoke (Owen Voke): In `v0.*` of Husky, commit hooks were taken from the script names (e.g. `precommit`). But in v1 and above, they are under a `husky.hooks` subkey. I've applied this in #2960, where I combined those dependency updates. 4/30/2019, 4:33:39 AM - mebeim (Marco Bonelli): @pxgamer Oh, I see.. I was looking at the doc for `husky` and I only saw the `husky.hooks` mentioned so I thought it wasn't used. Good job 😉 4/30/2019, 4:38:51 AM - owenvoke (Owen Voke): :+1: No problem. 5/1/2019, 12:06:15 AM - waldyrious (Waldir Pimenta): The organizations selected for this year's Season of Docs have been picked: https://developers.google.com/season-of-docs/docs/participants/ (we aren't among them) 5/1/2019, 12:06:41 AM - waldyrious (Waldir Pimenta): @sbrl did they send an email or something about why we weren't selected? 5/1/2019, 12:06:57 AM - sbrl (Starbeamrainbowlabs): Ah, better luck next time! I'll check 5/1/2019, 12:08:51 AM - waldyrious (Waldir Pimenta): In any case, the selected organizations are well established and well-known, and apparently there were almost 200 applications, so it's likely that we didn't have a bad application at all (I think we had a pretty good one) -- there just was a lot of competition :) 5/1/2019, 12:09:40 AM - waldyrious (Waldir Pimenta): I just checked and (so far) they didn't send anything to the mailing list we created: https://groups.google.com/forum/#!forum/tldr-pages 5/1/2019, 2:39:11 AM - mebeim (Marco Bonelli): Oh snap, better luck next time 😟 5/1/2019, 1:27:00 PM - sbrl (Starbeamrainbowlabs): Gosh! That's a lot. I forget to mention since I got distracted sorting through my mailboxes, but it looks like I did't receive anything either 5/3/2019, 3:40:13 PM - sbrl (Starbeamrainbowlabs): [![Re: Your application for Season of Docs 2019 was unsuccessful - Inbox - sbrl@posteo.net - Mozilla Thunderbird_148.png](https://files.gitter.im/tldr-pages/tldr/9Nyw/thumb/Re_-Your-application-for-Season-of-Docs-2019-was-unsuccessful---Inbox---sbrl_posteo.net---Mozilla-Thunderbird_148.png)](https://files.gitter.im/tldr-pages/tldr/9Nyw/Re_-Your-application-for-Season-of-Docs-2019-was-unsuccessful---Inbox---sbrl_posteo.net---Mozilla-Thunderbird_148.png) 5/3/2019, 3:40:32 PM - sbrl (Starbeamrainbowlabs): Update! Looks like we did receive something after all, the google group just didn't work 5/3/2019, 3:40:50 PM - sbrl (Starbeamrainbowlabs): So they re-sent it again CCing the admins 5/5/2019, 12:15:10 PM - waldyrious (Waldir Pimenta): Oh, crap. We might need to fine-tune the posting rules in the Google group 😳 5/5/2019, 4:02:33 PM - sbrl (Starbeamrainbowlabs): Lol 😛 5/5/2019, 4:03:48 PM - sbrl (Starbeamrainbowlabs): _(Also, PSA: I'm fiddling with the DNS provider for starbeamrainbowlabs.com, with the intention of transferring the domain to Cloudflare for DNS only. If things go a bit wonky with the tldr-bot, please don't worry!)_ 5/5/2019, 5:26:36 PM - sbrl (Starbeamrainbowlabs): _(Transfer complete!)_ 5/6/2019, 2:18:18 AM - waldyrious (Waldir Pimenta): Nice :) 5/6/2019, 2:19:48 AM - waldyrious (Waldir Pimenta): I've just configured the Google group to allow anyone to post to it. Hopefully that will prevent bounced messages from now on. 5/6/2019, 2:24:28 AM - sbrl (Starbeamrainbowlabs): Awesome! 5/6/2019, 2:24:35 AM - sbrl (Starbeamrainbowlabs): And thanks 😃 5/8/2019, 5:10:42 AM - sbrl (Starbeamrainbowlabs): I think @Aracki might have enough PRs now to be a collaborator 5/8/2019, 5:11:15 AM - sbrl (Starbeamrainbowlabs): _(I don't have time to check & do an invite now, but I'll do it later if someone hasn't already taken care of it)_ 5/8/2019, 12:05:11 PM - owenvoke (Owen Voke): I was thinking that too. Is anyone else due a role change? :slight_smile: 5/8/2019, 2:38:01 PM - sbrl (Starbeamrainbowlabs): Hrm, not sure. I think @andrik is ready too 5/8/2019, 8:30:22 PM - owenvoke (Owen Voke): They definitely have enough PRs. :+1: 5/8/2019, 8:31:38 PM - sbrl (Starbeamrainbowlabs): Opened #2988 😃 5/8/2019, 8:35:16 PM - owenvoke (Owen Voke): Should they have had separate PRs? 5/8/2019, 8:40:11 PM - sbrl (Starbeamrainbowlabs): Hrm, I'm not sure. 5/8/2019, 8:40:30 PM - sbrl (Starbeamrainbowlabs): I'm working through my notifications now, I'll get it it again in a bit 5/8/2019, 8:40:56 PM - owenvoke (Owen Voke): Also just noticed I'm technically eligible for becoming an org owner. 😛 5/8/2019, 8:42:15 PM - sbrl (Starbeamrainbowlabs): Ah, awesome! I should def. do that. 5/8/2019, 8:44:13 PM - sbrl (Starbeamrainbowlabs): Opened #2989 😃 😃 5/8/2019, 8:44:47 PM - owenvoke (Owen Voke): Whoops. Shouldn't have mentioned it 😉 5/8/2019, 8:45:45 PM - sbrl (Starbeamrainbowlabs): lol 5/8/2019, 8:46:02 PM - sbrl (Starbeamrainbowlabs): I can delete the issue again? 😛 5/8/2019, 8:48:27 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/sxem/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/sxem/image.png) 5/8/2019, 8:48:30 PM - sbrl (Starbeamrainbowlabs): Also, I think GitHub has a bug: 5/8/2019, 8:48:40 PM - sbrl (Starbeamrainbowlabs): Apparently @waldyrious has invented a time machine 5/8/2019, 8:51:41 PM - owenvoke (Owen Voke): That's... odd 😂 5/8/2019, 8:52:38 PM - sbrl (Starbeamrainbowlabs): I tweeted @GithubHelp lol 5/8/2019, 9:14:07 PM - owenvoke (Owen Voke): :+1: 5/9/2019, 2:07:49 AM - mebeim (Marco Bonelli): Yeah, GitHub is having some quite strange bugs with PR comments, dates and mentions today. 5/10/2019, 7:40:26 PM - owenvoke (Owen Voke): Just interested, on the tldr pages org, the website is linked to an HTTP version of the github.io site (which redirects). Is it worth updating this to https://tldr.sh? 5/10/2019, 7:51:29 PM - mebeim (Marco Bonelli): yeah, that's probably a good idea. 5/10/2019, 8:02:24 PM - sbrl (Starbeamrainbowlabs): :+1: 5/10/2019, 8:11:09 PM - schneiderl (Lucas Gabriel Schneider): Hi there, I'm working on a PR to standardize domain examples in tldr pages. I was thinking of two possibilities: using "foo.com" or "example.com". What do you guys think is better? Any of you have other suggestion? 5/10/2019, 8:11:57 PM - sbrl (Starbeamrainbowlabs): Hey, @schneiderl! That sounds great. I think I'd prefer example.com, as it's more obvious. 5/10/2019, 8:12:18 PM - sbrl (Starbeamrainbowlabs): Note that some pages will require different ones though 5/10/2019, 8:12:38 PM - sbrl (Starbeamrainbowlabs): e.g. if they are dealing with multiple hosts 5/10/2019, 8:14:12 PM - schneiderl (Lucas Gabriel Schneider): Yes, for sure. I have created a list of pages that contain general examples (there are some specific ones like some amazon pages etc that cant be changed to something more generic) and will analyze each of them individually. 5/10/2019, 8:15:46 PM - sbrl (Starbeamrainbowlabs): cool! 5/10/2019, 8:42:03 PM - owenvoke (Owen Voke): I'd prefer `example.com` as well, because it's an official recommended domain for providing examples. Whereas foo.com could be bought as an actual domain for use. Also, it's easier for people who are maybe less used to the foo/bar terminology. 5/10/2019, 8:43:59 PM - owenvoke (Owen Voke): And updated to use https://tldr.sh, another thing (less relevant), on GitHub you can verify a domain for an org. Is that worth doing as well? I'm not sure who owns tldr.sh, so they'd have to do it as it requires an email. 5/10/2019, 9:08:03 PM - sbrl (Starbeamrainbowlabs): You can? I wonder what that does. 5/10/2019, 9:08:44 PM - sbrl (Starbeamrainbowlabs): I think it belongs to @ostera (their GitHub username) 5/10/2019, 9:08:57 PM - sbrl (Starbeamrainbowlabs): if I've spelt their name correctly 5/10/2019, 9:09:15 PM - sbrl (Starbeamrainbowlabs): `whois` lists it under `Ostera Industries` at least 5/10/2019, 10:22:02 PM - owenvoke (Owen Voke): Oh right. It basically let's you have a verified icon next to your org. e.g. https://help.github.com/en/articles/verifying-your-organizations-domain 5/10/2019, 10:31:00 PM - sbrl (Starbeamrainbowlabs): Ah, I see! 5/10/2019, 10:31:01 PM - sbrl (Starbeamrainbowlabs): Sounds useful 5/11/2019, 1:23:00 PM - schneiderl (Lucas Gabriel Schneider): Hi, I have just seen your comment [here](https://github.com/tldr-pages/tldr/pull/3004#discussion_r283085120) @agnivade . I think it is great to ask for homepage urls as we already create the content with all the information. But IMHO it would be even better if we have this in our Contributing Guide. If anyone reads our CONTRIBUTING.md file there is nothing about homepage links. Also our PR's checklist could have one line like "Add command homepage if it exists". Do you guys agree with that? 5/11/2019, 2:25:05 PM - schneiderl (Lucas Gabriel Schneider): I don't actually know if CONTRIBUTING.md is the place for that to be in. Style guide file might be more appropriate. 5/11/2019, 6:20:46 PM - owenvoke (Owen Voke): Style guide makes more sense. 5/11/2019, 9:11:44 PM - sbrl (Starbeamrainbowlabs): Yeah, updating the style guide sounds like a great idea. 5/11/2019, 9:12:00 PM - sbrl (Starbeamrainbowlabs): By this point the homepage / documentation thing is pretty well established 5/12/2019, 2:36:17 AM - schneiderl (Lucas Gabriel Schneider): Ok. I'll work on that PR. 5/12/2019, 5:49:09 PM - agnivade (Agniva De Sarker): Just got back from a vacation. 5/12/2019, 5:49:56 PM - agnivade (Agniva De Sarker): Was reviewing PRs from mobile for a few days. 5/12/2019, 5:50:29 PM - agnivade (Agniva De Sarker): > Also our PR's checklist could have one line like "Add command homepage if it exists". I like this 5/15/2019, 4:30:51 AM - sbrl (Starbeamrainbowlabs): I've noticed that a new tab has appeared on GitHub PRs called "checks" 5/15/2019, 4:31:23 AM - sbrl (Starbeamrainbowlabs): [![Selection_165.png](https://files.gitter.im/tldr-pages/tldr/11P2/thumb/Selection_165.png)](https://files.gitter.im/tldr-pages/tldr/11P2/Selection_165.png) 5/15/2019, 4:31:27 AM - sbrl (Starbeamrainbowlabs): I'm seeing this 5/15/2019, 4:31:39 AM - sbrl (Starbeamrainbowlabs): Interesting with respect to tldr-bot? 5/15/2019, 5:14:51 AM - owenvoke (Owen Voke): This has been here for a while. :+1: It's pretty neat to integrate with. 5/15/2019, 8:22:35 PM - sbrl (Starbeamrainbowlabs): Oh, right! 5/15/2019, 8:22:39 PM - sbrl (Starbeamrainbowlabs): Didn't know 😛 1/14/2023, 3:26:49 PM - lbonanomi (lbonanomi) joined the room 5/16/2019, 6:08:09 PM - lbonanomi (lbonanomi): Hi maintainers! Did you want an issue opened for duplicate pages? The page for "at" appears under Linux and common, and which-one-lives seems like a decision above my notional paygrade 5/16/2019, 6:54:48 PM - sbrl (Starbeamrainbowlabs): lol! I'd recommend checking that they aren't different first. If there's one in `common/`, then it covers more than 1 platform. However, if there's a more specific page in `linux/` for example, it's possible that it's showcasing additional platform-specific functionality 5/16/2019, 6:55:05 PM - sbrl (Starbeamrainbowlabs): If they are the same, then yeah we should delete 1 5/16/2019, 6:55:17 PM - sbrl (Starbeamrainbowlabs): Depending on whether the command functions on more than 1 platform 5/16/2019, 6:55:19 PM - sbrl (Starbeamrainbowlabs): @lbonanomi 5/16/2019, 8:21:29 PM - lbonanomi (lbonanomi): I can dig it @sbrl ; looking at the `cal` pages shows some diversity of arguments but the `at` examples on-offer seem to be portable across the board. I'd suggest poaching the additional arguments from the linux example and keeping the `common/` entry but am happy to take instructions. 5/16/2019, 8:26:09 PM - sbrl (Starbeamrainbowlabs): Sounds good to me! 5/19/2019, 8:59:00 PM - mebeim (Marco Bonelli): Opened #3041, you're very welcome to vote guys :) 5/26/2019, 4:38:34 AM - mebeim (Marco Bonelli): Hey guys, any thought about this? https://help.github.com/en/articles/about-github-sponsors 5/26/2019, 5:15:34 AM - sbrl (Starbeamrainbowlabs): Hey, @mebeim! I did see that. I was considering joining the waiting list actually 5/26/2019, 5:16:10 AM - sbrl (Starbeamrainbowlabs): I can't deny that the chance to be sponsered for the honestly quite considerable amount of time I spend per month reviewing PRs and doing other maintenance tasks is attractive 5/26/2019, 11:35:09 PM - mebeim (Marco Bonelli): Yep looks cool 5/27/2019, 2:54:39 AM - agnivade (Agniva De Sarker): I feel like the whole point of open source is giving back. There is no harm in getting paid for doing something you love. But then by definition, it makes it your job. 5/27/2019, 3:37:34 AM - sbrl (Starbeamrainbowlabs): Very true, @agnivade. 5/27/2019, 4:04:22 AM - mebeim (Marco Bonelli): Well yeah, a sponsorship is a sponsorship. I'm really curious to see how this goes. 5/29/2019, 1:39:18 AM - sbrl (Starbeamrainbowlabs): TIL that duckduckgo has tldr-pages integration. 5/29/2019, 1:39:22 AM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/huOl/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/huOl/image.png) 5/29/2019, 2:28:16 AM - mebeim (Marco Bonelli): oh yeah, I sent a similar screenshot months ago haha 5/29/2019, 2:28:48 AM - mebeim (Marco Bonelli): that's very cool indeed 5/29/2019, 3:23:09 AM - sbrl (Starbeamrainbowlabs): lol, I forgot 5/29/2019, 9:40:58 PM - mebeim (Marco Bonelli): What do you guys think about the whole links for coreutils discussion? I mean, what do you think meta-wise, I already know what we all think about that particular topic. 5/29/2019, 9:42:05 PM - mebeim (Marco Bonelli): Has such a controversial discussion/decision ever happened before? I'm really unsure about what to do 😕 5/29/2019, 10:02:28 PM - sbrl (Starbeamrainbowlabs): @waldyrious 5/31/2019, 1:26:26 AM - agnivade (Agniva De Sarker): Yeah, it had happened once before. 5/31/2019, 1:26:41 AM - agnivade (Agniva De Sarker): That was for the pages format upgrade. 5/31/2019, 1:27:18 AM - agnivade (Agniva De Sarker): I was against it initially. But then I said, fine let's do it. 5/31/2019, 1:27:32 AM - agnivade (Agniva De Sarker): It is yet to be done though, but the process took some time to be approved. :) 6/2/2019, 11:02:01 PM - waldyrious (Waldir Pimenta): @sbrl, thanks for the ping. I'm a bit swamped with work these days, not able to participate in the discussions as usual 6/2/2019, 11:02:24 PM - sbrl (Starbeamrainbowlabs): No problem! 6/2/2019, 11:02:36 PM - waldyrious (Waldir Pimenta): I agree, as @agnivade said, we did have long discussions before. Besides the format one, I recall the CLA one as well 6/2/2019, 11:03:04 PM - sbrl (Starbeamrainbowlabs): Oh right! I think that was before my time. 6/2/2019, 11:03:11 PM - waldyrious (Waldir Pimenta): And to a lesser degree, there was also a proposal to adopt the C++ client as the single officially sanctioned one 6/2/2019, 11:03:32 PM - sbrl (Starbeamrainbowlabs): Huh, interesting 6/2/2019, 11:03:55 PM - sbrl (Starbeamrainbowlabs): The current issue is an impasse at whether to include a link to an online man page in the `More information:` description line or not 6/2/2019, 11:04:00 PM - sbrl (Starbeamrainbowlabs): Hence the ping :-) 6/2/2019, 11:04:28 PM - waldyrious (Waldir Pimenta): I think that's a good exercise for our ability to reach consensus. When it's easy to reach, it's not that telling of our ability for decision-making as a community 6/2/2019, 11:04:45 PM - sbrl (Starbeamrainbowlabs): I'll have to go digging through the discussions there to see how they were resolved. 6/2/2019, 11:04:50 PM - sbrl (Starbeamrainbowlabs): Good point! 6/2/2019, 11:07:26 PM - waldyrious (Waldir Pimenta): As for this particular discussion: I'll make sure to read the backlog and comment as soon as I can. If you guys feel that we should move on before that, no problem; I can always make a proposal afterwards. But I don't think it's a pressing issue regarding our main mission, so IMHO business can continue as usual until we reach a decision. 6/2/2019, 11:08:33 PM - sbrl (Starbeamrainbowlabs): Thanks so much! And yeah, you're right. We can take our time :-) 6/2/2019, 11:10:11 PM - waldyrious (Waldir Pimenta): I appreciate the understanding! ^^ 6/2/2019, 11:10:37 PM - sbrl (Starbeamrainbowlabs): 😃 6/3/2019, 9:36:28 AM - agnivade (Agniva De Sarker): Oh yeah .. I remember the C++ client discussion .. 6/3/2019, 9:38:34 AM - agnivade (Agniva De Sarker): I wasn't very actively involved in that, but the main motivation against the node client was that there is simply so many dependencies to install ! (which I partially agree to :), but don't think that is the only driving factor ) 6/3/2019, 9:38:41 AM - agnivade (Agniva De Sarker): Anyways, totally agree that it's a good exercise to see how well we function when there is disagreement. When there is unanimous consensus, things are easy :) 6/5/2019, 1:24:16 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/M7Vb/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/M7Vb/image.png) 6/5/2019, 1:24:20 AM - mebeim (Marco Bonelli): interesting 6/5/2019, 1:26:02 AM - sbrl (Starbeamrainbowlabs): Oh, yeah! That's really neat. 6/5/2019, 1:26:14 AM - sbrl (Starbeamrainbowlabs): I do have to wonder how that works with an organisation though....? 6/5/2019, 1:26:28 AM - mebeim (Marco Bonelli): I do too.. 6/5/2019, 1:27:33 AM - sbrl (Starbeamrainbowlabs): Maybe one of us should apply and find out lol Not sure how much of a good idea that is though 6/5/2019, 1:30:39 AM - mebeim (Marco Bonelli): im not really sure either, and if anything it should be one of the org owners to do it 6/5/2019, 1:31:15 AM - mebeim (Marco Bonelli): in such case it would be better to first talk about it though, not everyone might like it 6/5/2019, 1:33:16 AM - sbrl (Starbeamrainbowlabs): Indeed, @mebeim. As an org owner, I'd be open to talking about it - but our organisation model does make it a challenge to organise something like that. 6/5/2019, 1:33:49 AM - mebeim (Marco Bonelli): That's true. 6/5/2019, 11:15:08 AM - owenvoke (Owen Voke): For an org, you can just add a `.github/FUNDING.yml` file. If you go to Settings for the repo, it should have an option to generate one. It seems that a lot of other open source projects are using Open Collective and just adding their link to the sponsor stuff, rather than using GitHub Sponsors. With GitHub, you can do up to 4 sponsored usernames I think. 6/5/2019, 3:20:31 PM - sbrl (Starbeamrainbowlabs): Ah, I see @pxgamer - that makes sense. 6/7/2019, 1:20:38 AM - mebeim (Marco Bonelli): Oh, that's coool I didn't know that :) 6/8/2019, 8:30:58 PM - owenvoke (Owen Voke): For us, if we do go down the funding route, it's probably better using another service. Because there are obviously more than 4 people. :+1: Unless you can mark `tldr-pages` as a sponsorable entity. 6/8/2019, 8:37:52 PM - mebeim (Marco Bonelli): It could also be something like "ok sponsor these 4 people" but then the money is just put together in a single place and used to maintain the project (e.g. paying for some hosting etc) 6/8/2019, 8:38:15 PM - mebeim (Marco Bonelli): But yeah, in an org like this, it's not so simple to manage such thing 6/8/2019, 8:46:55 PM - owenvoke (Owen Voke): Ah, just found that you can request to join a team sponsorship program with GitHub. Which would be exactly what we'd need. 6/8/2019, 8:50:46 PM - mebeim (Marco Bonelli): Ah, nice 6/9/2019, 12:38:14 AM - sbrl (Starbeamrainbowlabs): Huh, interesting! Might be worth investigating - or at least opening an issue to discuss. 6/9/2019, 4:29:18 AM - owenvoke (Owen Voke): I'll open an issue tomorrow if no one else has. :+1: 6/9/2019, 4:31:07 AM - sbrl (Starbeamrainbowlabs): Thanks, @pxgamer :-) 6/10/2019, 5:22:35 PM - owenvoke (Owen Voke): Sorry, didn't end up opening it yesterday. But I've opened #3102 today. :+1: 6/10/2019, 5:30:25 PM - sbrl (Starbeamrainbowlabs): :+1: 6/12/2019, 2:12:59 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/R11h/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/R11h/image.png) 6/12/2019, 2:13:52 AM - mebeim (Marco Bonelli): So it turns out that if you start a review and forget to finish it and the comment is left unpublished, when you later publish it this happens, strange 😆 6/12/2019, 2:26:14 AM - sbrl (Starbeamrainbowlabs): 😛 6/12/2019, 11:10:33 AM - agnivade (Agniva De Sarker): Definitely a github bug 6/12/2019, 3:38:05 PM - sbrl (Starbeamrainbowlabs): lol, we've seen a few of those recently 6/13/2019, 2:33:20 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/IfyN/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/IfyN/image.png) 6/13/2019, 2:34:29 AM - mebeim (Marco Bonelli): This badge isn't showing up lately for me (last few days), did you guys also notice it or is it only me? 6/13/2019, 3:05:25 AM - sbrl (Starbeamrainbowlabs): Yeah, I'm having an issue there too 6/13/2019, 3:05:35 AM - sbrl (Starbeamrainbowlabs): Not sure what the url is for that badge 6/13/2019, 3:06:36 AM - sbrl (Starbeamrainbowlabs): Can you get the file count via the GH api? If so, then sheilds.io has a dynamic mode we might be able to use 6/13/2019, 4:41:08 AM - owenvoke (Owen Voke): Looks like the URL is from Tokei. 6/13/2019, 4:41:16 AM - owenvoke (Owen Voke): https://tokei.rs/b1/github/tldr-pages/tldr?category=files 6/13/2019, 4:42:22 AM - owenvoke (Owen Voke): Weird that the alt text is number of files, but the badge seems to be number of lines. 6/13/2019, 4:46:04 AM - owenvoke (Owen Voke): Looking at Shields, I can't see any badges that match. But as you mentioned, there is the `/endpoint` stuff, which you can customise. However, if it is available through the API, it could be quite a nice badge to add to Shields directly (I've added some previously). 6/13/2019, 5:26:45 AM - sbrl (Starbeamrainbowlabs): Oh, interesting! Didn't know you could contribute to shields.io 6/13/2019, 5:27:22 AM - sbrl (Starbeamrainbowlabs): I didn't see it under the repository endpoint, but that doesn't mean to say it doesn't exist 6/15/2019, 6:41:28 PM - mebeim (Marco Bonelli): I took a look at the GH API and it doesn't seem like there's an endpoint to request the number of files in a repo 🤔 this one https://developer.github.com/v3/repos/contents/#get-contents looks like the closer you can get to an actual file count. The tokei badge looks broken (not only for us, I've seen other repos with the same issue). Shields doesn't have one like that. Hmmm... this is awkward. 6/15/2019, 6:49:41 PM - sbrl (Starbeamrainbowlabs): Hrm. The reason I ask about the GH API is that shields.io supports dynamic badges: https://shields.io/#dynamic-badge 6/15/2019, 6:50:51 PM - sbrl (Starbeamrainbowlabs): You point it at a JSON file, and tell it which property to display and what label to give it. 6/15/2019, 6:52:53 PM - sbrl (Starbeamrainbowlabs): I wonder if you could ~~ab~~use the HTML page as XML, and pull out the file count that way? :thinking: 6/15/2019, 7:45:03 PM - owenvoke (Owen Voke): It has to be a specific format though for the JSON response. Unless they've changed it in the last few months. 6/15/2019, 7:46:49 PM - owenvoke (Owen Voke): So we couldn't just point it at the GitHub API. Would need to set up a relay that returns the required spec. :+1: 6/15/2019, 7:47:03 PM - owenvoke (Owen Voke): . 6/15/2019, 7:47:45 PM - owenvoke (Owen Voke): Oh. Ignore me, that's new right? :thinking: The dynamic API stuff? 6/15/2019, 9:05:48 PM - sbrl (Starbeamrainbowlabs): Yeah, it is! I've used it in one of my personal projects already 6/15/2019, 9:06:03 PM - sbrl (Starbeamrainbowlabs): No need for a proxy or relay 😃 6/15/2019, 10:26:15 PM - owenvoke (Owen Voke): Pretty neat! I was thinking of the Endpoint stuff they did. 6/15/2019, 10:31:31 PM - sbrl (Starbeamrainbowlabs): Ah 6/15/2019, 10:31:44 PM - sbrl (Starbeamrainbowlabs): Yeah, they've got a bunch of presets that were there before 6/15/2019, 10:32:00 PM - sbrl (Starbeamrainbowlabs): I suspect that it's just that they've exposed their backend that powers the pre-existing features 6/16/2019, 12:56:06 AM - mebeim (Marco Bonelli): So @sbrl you're saying there's a GH endpoint somewhere that returns the number of files to be used in a dynamic badge? Which is it? 6/16/2019, 1:06:03 AM - sbrl (Starbeamrainbowlabs): No, I don't think it does @mebeim. We're saying that we can get shields.io to display _any_ statistic we can get from the GH api. 6/16/2019, 1:06:12 AM - sbrl (Starbeamrainbowlabs): We could alter tldr-bot to return it though & display that. 6/16/2019, 1:10:32 AM - mebeim (Marco Bonelli): Oh ok got it, seems a bit overkill though 6/16/2019, 1:12:13 AM - sbrl (Starbeamrainbowlabs): True 6/16/2019, 2:30:03 AM - owenvoke (Owen Voke): What might be better is to just add a file count to the build, and it just adds a JSON file to the ZIP that gets uploaded to GitHub Pages? Then we are only counting the actual pages. 6/16/2019, 2:33:17 AM - mebeim (Marco Bonelli): Now that seems unnecessary 🤨 6/16/2019, 2:46:58 AM - sbrl (Starbeamrainbowlabs): Nice idea, @pxgamer! That might be useful for clients too etc, if they want to display tldr-pages stats. 6/16/2019, 2:47:28 AM - sbrl (Starbeamrainbowlabs): I might make a graph tldr-pages stats over time - that sounds interesting 6/16/2019, 2:47:49 AM - sbrl (Starbeamrainbowlabs): It's interesting metadata at least 6/16/2019, 2:53:17 AM - mebeim (Marco Bonelli): It's interesting for sure, but I IMHO having it inside the built archive file doesn't makes much sense. It feels like redundant information to me. 6/16/2019, 2:55:03 AM - sbrl (Starbeamrainbowlabs): Ah, I see 6/16/2019, 2:55:07 AM - sbrl (Starbeamrainbowlabs): Yeah, I guess 6/16/2019, 3:40:20 AM - owenvoke (Owen Voke): Not in the archive file. 6/16/2019, 3:41:00 AM - mebeim (Marco Bonelli): what do you mean by "adds a JSON file to the ZIP that gets uploaded to GitHub Pages" then? 6/16/2019, 3:41:37 AM - owenvoke (Owen Voke): It's not a zip, thought it was. 6/16/2019, 3:42:01 AM - owenvoke (Owen Voke): We push it to the website repo. :+1: I was mistaken. 6/16/2019, 3:42:07 AM - owenvoke (Owen Voke): Like https://github.com/tldr-pages/tldr-pages.github.io/blob/master/assets/index.json 6/16/2019, 3:42:41 AM - mebeim (Marco Bonelli): Oh got it, yeah that could be interesting 6/16/2019, 3:42:51 AM - owenvoke (Owen Voke): So we'd just have like a `stats.json` or something. 6/16/2019, 3:43:23 AM - owenvoke (Owen Voke): Maybe with languages, pages, etc. as keys 6/16/2019, 9:22:45 AM - agnivade (Agniva De Sarker): I think we can just remove that badge. No. of files doesn't reaaaallly need a badge 😛 6/16/2019, 2:55:44 PM - owenvoke (Owen Voke): Seems fair. 6/16/2019, 5:33:56 PM - sbrl (Starbeamrainbowlabs): Yeah. It's fun to explore the alternative options though - even if we don't ultimately take them 6/16/2019, 11:18:05 PM - mebeim (Marco Bonelli): Yeah I agree with @agnivade tbh 6/17/2019, 12:36:44 AM - sbrl (Starbeamrainbowlabs): Check out the comment in the issue/pr that @waldyrious posted. I think it's a good counter-argument 6/17/2019, 12:36:55 AM - sbrl (Starbeamrainbowlabs): I can't remember the #number off the top of my head though 6/21/2019, 4:26:47 AM - mebeim (Marco Bonelli): I was looking at https://github.com/tldr-pages/tldr/releases and... do we really need that tag? Looks confusing to see "1 release" just because of that "0.0.1" tag. Actually, looks strange to even have that tag in the first place. 6/21/2019, 4:27:48 AM - mebeim (Marco Bonelli): Was this ever talked about? If not I'd like to open an issue to discuss about removing it. 6/21/2019, 4:27:54 AM - sbrl (Starbeamrainbowlabs): Hrm. That's a good question. Who was that tag created by? 6/21/2019, 4:28:10 AM - sbrl (Starbeamrainbowlabs): Might be worth investigating it's history 6/21/2019, 4:28:15 AM - mebeim (Marco Bonelli): by @rprieto 6/21/2019, 4:28:31 AM - sbrl (Starbeamrainbowlabs): Ah. He would be the founder of this project, IIRC 6/21/2019, 4:28:49 AM - mebeim (Marco Bonelli): Yep. That tag doesn't look like anything special at all, that's why I'm asking. Looks kinda out of place. 6/21/2019, 4:28:51 AM - sbrl (Starbeamrainbowlabs): That was waaay before my time. 6/21/2019, 4:29:20 AM - mebeim (Marco Bonelli): Yeah that's true, it was 5 years ago :') 6/21/2019, 4:29:41 AM - sbrl (Starbeamrainbowlabs): I'd recommend opening an issue and ccing @agnivade and @waldyrious. Maybe @rubenvereecken too? Not sure if they are still active though 6/21/2019, 4:29:59 AM - sbrl (Starbeamrainbowlabs): Or @ostera 6/21/2019, 4:30:05 AM - mebeim (Marco Bonelli): But you don't recalling about talking about it since you've been part of the project, am I correct? 6/21/2019, 4:30:23 AM - sbrl (Starbeamrainbowlabs): Nope. It hasn't come up before, as far as I remember 6/21/2019, 4:30:41 AM - sbrl (Starbeamrainbowlabs): I have noticed it, but I just thought of it as a curiousity 6/21/2019, 4:30:48 AM - sbrl (Starbeamrainbowlabs): I bet there's a story behind it 6/21/2019, 4:30:48 AM - mebeim (Marco Bonelli): Yep that's what I wanted to do indeed, just checking to avoid creating a duplicate 6/21/2019, 4:31:24 AM - mebeim (Marco Bonelli): Probably, I'm curious about that, I'll open an issue tomorrow 6/21/2019, 4:31:32 AM - sbrl (Starbeamrainbowlabs): Sure! 6/21/2019, 1:05:25 PM - agnivade (Agniva De Sarker): AFAIK, this wasn't discussed before. We can delete it and see what breaks, and recreate it if somebody complains. 6/21/2019, 1:06:07 PM - agnivade (Agniva De Sarker): Maybe also cc major client owners in that issue just to check if anybody is using that tag. 6/21/2019, 3:23:44 PM - owenvoke (Owen Voke): I wondered about the tag before as well. Seems a bit random, especially when it is so out of date. 6/21/2019, 5:55:56 PM - mebeim (Marco Bonelli): Just created #3121 6/21/2019, 7:13:21 PM - owenvoke (Owen Voke): :+1: 1/14/2023, 3:27:52 PM - principis (Arthur Bols) joined the room 6/23/2019, 4:06:10 AM - principis (Arthur Bols): Hi! I just noticed that there are 2 versions of the rename command... A perl version for Debian and util-linux for everyone else... The problem is that the page is written for the perl version and it's very different than the util-linux command 6/23/2019, 4:32:52 AM - sbrl (Starbeamrainbowlabs): Oh dear! That's a very interesting problem. How different is very different? 6/23/2019, 4:33:06 AM - sbrl (Starbeamrainbowlabs): I'd open an issue about that @principis 6/23/2019, 4:43:44 AM - mebeim (Marco Bonelli): Oh dear, that's true, can confirm on my Ubuntu 18 vs Debian 9, the commands look very differently. That's annoying :\ 6/23/2019, 4:44:37 AM - sbrl (Starbeamrainbowlabs): Definitely a _why did you do this, debian developers?!_ moment 6/23/2019, 4:53:31 AM - mebeim (Marco Bonelli): Yep, SIGH :\ 6/23/2019, 3:38:53 PM - principis (Arthur Bols): @sbrl I didn't know if I should've opened an issue that's why I mentioned it here :) https://unix.stackexchange.com/questions/275254/why-is-the-rename-utility-on-debian-ubuntu-different-than-the-one-on-other-distr 6/23/2019, 3:40:32 PM - principis (Arthur Bols): http://manpages.ubuntu.com/manpages/trusty/man1/prename.1.html vs http://man7.org/linux/man-pages/man1/rename.1.html 6/23/2019, 3:43:55 PM - principis (Arthur Bols): I've opened an issue https://github.com/tldr-pages/tldr/issues/3125 6/23/2019, 3:44:12 PM - principis (Arthur Bols): @mebeim are you saying debian uses the util-linux package? 6/23/2019, 3:58:20 PM - sbrl (Starbeamrainbowlabs): Interesting history there! 6/23/2019, 5:39:08 PM - mebeim (Marco Bonelli): Nope @sbrl, Ubuntu uses util-linux 6/23/2019, 5:39:18 PM - sbrl (Starbeamrainbowlabs): Ah 6/23/2019, 6:11:56 PM - principis (Arthur Bols): @mebeim not for me on Ubuntu server 18.04 (I installed the rename package) 6/23/2019, 6:13:21 PM - principis (Arthur Bols): so rename is the perl version rename.ul is the util-linux version 6/23/2019, 6:15:49 PM - principis (Arthur Bols): on fedora 30 rename is util-linux, prename perl... This is confusing 😛 6/23/2019, 6:21:36 PM - mebeim (Marco Bonelli): @principis Well, I did NOT install the `rename` package. That's what I meant: by default, Ubuntu uses the `util-linux` `rename`. Since `util-linux` is required (i.e. it is a built-in package), that's what I was talking about. 6/23/2019, 6:23:44 PM - sbrl (Starbeamrainbowlabs): How about we move this discussion to the issue? It might clear things up a bit 😛 6/23/2019, 6:24:15 PM - mebeim (Marco Bonelli): I will, I'm gathering the needed information and testing things out. I was about to post a comment there. 6/23/2019, 6:30:20 PM - sbrl (Starbeamrainbowlabs): Ah, cool :-) 6/23/2019, 7:39:28 PM - principis (Arthur Bols): @mebeim well that's strange because I've now tested on multiple ubuntu 18.04 machines and all of them have no rename by default but do have rename.ul and if you install rename it's the perl version. But I'll wait for your comment :) 6/23/2019, 7:49:09 PM - mebeim (Marco Bonelli): @principis yeah I apologize for the confusion, you are indeed right, I just left a comment on your Issue which should clarify everything :slight_smile: 6/23/2019, 7:50:19 PM - mebeim (Marco Bonelli): > @principis Well, I did NOT install the `rename` package. That's what I meant: by default, Ubuntu uses the `util-linux` `rename`. Since `util-linux` is required (i.e. it is a built-in package), that's what I was talking about. This is true, but the dafault `util-linux` rename is called `rename.ul`, not `rename`. Sorry for the confusion again 😅 6/24/2019, 1:26:54 PM - principis (Arthur Bols): NP :) 6/26/2019, 1:43:08 AM - mebeim (Marco Bonelli): LOL https://github.com/tldr-pages/tldr/issues/3134 6/26/2019, 1:47:53 AM - sbrl (Starbeamrainbowlabs): Hrm :thinking: 7/2/2019, 3:52:29 AM - owenvoke (Owen Voke): Just thought I'd mention that I've updated my GPG key. This shouldn't make any difference to the GitHub interface though. :slight_smile: 7/2/2019, 4:03:15 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/unv1/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/unv1/image.png) 7/2/2019, 4:03:19 AM - mebeim (Marco Bonelli): cool new feature 7/2/2019, 5:36:13 AM - sbrl (Starbeamrainbowlabs): Nice! Not as useful here on tldr-pages, but still cool 7/4/2019, 1:14:57 PM - agnivade (Agniva De Sarker): phew .. just got done with a huge refactor of tldr-node codebase. 7/4/2019, 1:14:58 PM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr-node-client/pull/266 7/4/2019, 1:15:00 PM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr-node-client/pull/267 7/4/2019, 1:15:06 PM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr-node-client/pull/268 7/4/2019, 1:15:09 PM - agnivade (Agniva De Sarker): https://github.com/tldr-pages/tldr-node-client/pull/269 7/4/2019, 1:16:04 PM - agnivade (Agniva De Sarker): The objective was to remove global state and convert exported functions into class methods. 7/4/2019, 1:16:14 PM - agnivade (Agniva De Sarker): All of this creates the base for language support. 7/4/2019, 1:16:33 PM - agnivade (Agniva De Sarker): Anybody is welcome to comment on the PRs 7/4/2019, 2:38:17 PM - owenvoke (Owen Voke): Taking a look now! 7/4/2019, 3:43:00 PM - sbrl (Starbeamrainbowlabs): Oh wow, nice @agnivade! 7/15/2019, 11:23:21 PM - mflint (Matthew Flint): Hello team - this isn’t strictly _pages_ 7/15/2019, 11:23:36 PM - mflint (Matthew Flint): Derp 7/15/2019, 11:24:19 PM - mflint (Matthew Flint): This isn’t strictly _pages_ related, but I’ve got a new beta of the iOS client, with support for iOS 13 beta and their new “dark mode” 7/15/2019, 11:25:07 PM - mflint (Matthew Flint): So if any of you are crazy enough to run iOS 13 beta, I’d love to get more people testing the client. (I don’t recommend this on your main device!) 7/15/2019, 11:26:57 PM - mflint (Matthew Flint): TestFlight link: https://testflight.apple.com/join/Say2nJBZ 7/15/2019, 11:32:42 PM - sbrl (Starbeamrainbowlabs): Hey, very cool @mflint! I don't own an Apple device, but I'm sure Apple users will find that a great addition to tldr-pages. 7/15/2019, 11:33:56 PM - sbrl (Starbeamrainbowlabs): Have you checked out our new [client specification](https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md) yet, out of curiousity? It would be great to have another pair of eyes looking at it from an implementer's perspective. 7/15/2019, 11:34:48 PM - sbrl (Starbeamrainbowlabs): We're still ironing out some details (e.g. see #3183), but it's pretty much there. 7/15/2019, 11:59:23 PM - mflint (Matthew Flint): Thank-you @sbrl, I'm aware of it but haven't taken a close look. (It looked like it was very command-line specific, but I'm sure there are things there I could use) 7/16/2019, 12:00:14 AM - sbrl (Starbeamrainbowlabs): Yeah, that is an issue we're discovering with it. Suggestions on how to improve it and make it more applicable to all types of client are welcome :-) 7/16/2019, 12:01:38 AM - mflint (Matthew Flint): But on that subject: I do like how the maintainers tag client-developers in pull requests and issues. It's saved me more than once, when the zipfile has changed somehow :-) 7/16/2019, 12:26:42 AM - sbrl (Starbeamrainbowlabs): Thanks! I do try to tag people when I remember 😛 7/17/2019, 8:23:56 PM - agnivade (Agniva De Sarker): Great to see work happening with other clients. 1/14/2023, 3:28:13 PM - Aracki (Ivan Aracki) joined the room 7/19/2019, 7:01:50 PM - Aracki (Ivan Aracki): What do we do with stale PRs. For example: https://github.com/tldr-pages/tldr/pull/3155#issuecomment-513142905, I requested some changes which 3 of us think is a reasonable change. Stale bot arrived, OP of the PR is not posting anything. What are the next steps? 7/19/2019, 7:04:47 PM - sbrl (Starbeamrainbowlabs): Hrm, that's always a tough one @Aracki. Generally, I wait until the stale bot closes it, and then reopen it and fix it up myself 7/19/2019, 7:05:01 PM - sbrl (Starbeamrainbowlabs): Of course, if the OP doesn't sign the CLA then there's nothing we can do. 7/19/2019, 7:09:19 PM - Aracki (Ivan Aracki): Thanks for this one 👌 7/19/2019, 7:10:49 PM - sbrl (Starbeamrainbowlabs): np! 7/19/2019, 7:14:44 PM - mebeim (Marco Bonelli): I usually ping them, then check if I can apply the changes myself. If they have not granted edit rights to us I just wait enough time and then close it and open a new one cloning their branch (so that commits keep their author). 7/19/2019, 7:15:14 PM - mebeim (Marco Bonelli): I only did this one time where over a month had passes, but I think that's reasonable enough. 7/19/2019, 7:19:53 PM - sbrl (Starbeamrainbowlabs): Yeah, something like that. 7/19/2019, 7:20:18 PM - sbrl (Starbeamrainbowlabs): @stale-bot will notify after 2 weeks, and then close after a month IIRC 7/19/2019, 7:25:58 PM - Aracki (Ivan Aracki): :+1: seems reasonable 7/23/2019, 4:01:50 AM - waldyrious (Waldir Pimenta): Nowadays most PRs are created by default with edit permissions to the project maintainers. If I recall corretly, authors have to explicitly disable that permission for it to not be in place. That means that in most cases, there should be no need to close a PR (or let stale bot close it) and open a new one. In fact, I personally think it's quite undesirable to let the PR get to the point of being closed. It's highly preferable to make the edits ourselves if the authors have become unresponsive. 7/23/2019, 4:03:49 AM - waldyrious (Waldir Pimenta): The Maintainer's guide refers specifically to this situation, btw: > If a PR stops getting feedback from the submitter and is marked as stale by probot-stale, any maintainer can choose to take over the PR and make the necessary changes to get the content ready for merging. > - https://github.com/tldr-pages/tldr/blob/master/contributing-guides/maintainers-guide.md#ii-handling-prs 7/23/2019, 4:04:31 AM - waldyrious (Waldir Pimenta): The next point in the guide is also relevant: > During the review process, make sure that contributors, especially new ones, are not overwhelmed with too many change requests. Be mindful of signs of fatigue (less enthusiastic responses, slower reactions), and relax review standards if necessary — minor issues can always be fixed later. 7/23/2019, 4:12:17 AM - mebeim (Marco Bonelli): Yes, by default edit privileges are granted to maintainers, but I've seen quite a lot of people uncheck that. There are quite the number of PRs open that are basically stuck there for this reason. 7/23/2019, 4:16:10 AM - waldyrious (Waldir Pimenta): Huh. That's weird. Why would someone prefer to do that? It could be understandable if there was a pattern of maintainers forcibly taken over PRs from contributors to make changes they didn't agree with, but I never saw that happen tbh (in any project on github). 7/23/2019, 4:29:45 AM - mebeim (Marco Bonelli): Yeah that's odd indeed :\ 7/23/2019, 4:32:11 AM - sbrl (Starbeamrainbowlabs): Ah, so I've been over-cautious then. 7/23/2019, 4:32:32 AM - sbrl (Starbeamrainbowlabs): In that case, if I see a stale PR I'll be more pro-active in doing something with it. 7/23/2019, 4:34:55 AM - mebeim (Marco Bonelli): Uhm.. what's going on with these Wiki edits? 7/23/2019, 4:35:07 AM - mebeim (Marco Bonelli): https://github.com/tldr-pages/tldr/wiki/TLDR-clients/_compare/80e30c9d64cc05fedc865ec505c8460150ecfb76...8f224b7e5ede22ccc1f3f170f7977c8afd40113e 7/23/2019, 4:38:29 AM - mebeim (Marco Bonelli): I am confused. How can this user edit Wiki pages? Are they repository collaborators? Or can arbitrary users edit the Wiki? Also there's this issue #3202 which doesn't make much sense 🤔 7/23/2019, 4:48:46 AM - mebeim (Marco Bonelli): Ok, looks like this user is inserting spammy links to their repositories in our Wiki... what 😐 https://github.com/tldr-pages/tldr/wiki/TLDR-clients/_compare/4ff30c7a9bcec7680d4f52fbb74364aa4d69ac0a...40191fdb4c890901983377dd6fe19141912bea93 7/23/2019, 4:48:50 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/VjMa/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/VjMa/image.png) 7/23/2019, 4:49:40 AM - mebeim (Marco Bonelli): ^ They also cloned the repository of an existing client for some reason (https://github.com/Quadrillion-dev/tldr-Jquery-client) and they seem to want to add it to the wiki under their name (wut???), unsuccesfully though 7/23/2019, 4:52:23 AM - mebeim (Marco Bonelli): Looks like a spam bot to me really :\ 7/23/2019, 4:58:08 AM - sbrl (Starbeamrainbowlabs): Hrm. They also opened an issue IIRC that I gave a canned response to. 7/23/2019, 4:58:34 AM - sbrl (Starbeamrainbowlabs): IIRC, anyone can make wiki edits 7/23/2019, 4:58:44 AM - sbrl (Starbeamrainbowlabs): Looks like we'll have to revert those changes 😕 7/23/2019, 4:58:46 AM - mebeim (Marco Bonelli): Yeah the one I linked above, that response was pretty hilarious tbh sorry 😆 7/23/2019, 4:58:51 AM - sbrl (Starbeamrainbowlabs): lol 7/23/2019, 4:58:59 AM - sbrl (Starbeamrainbowlabs): Haven't read it yet 😛 7/23/2019, 4:59:10 AM - sbrl (Starbeamrainbowlabs): Might want to report the user to GitHub too 7/23/2019, 4:59:24 AM - mebeim (Marco Bonelli): OH, didn't know anyone could edit Wikis without basically any kind of notification to maintainers. That's..... ODD! 7/23/2019, 4:59:28 AM - sbrl (Starbeamrainbowlabs): tbh this is my first time encountering a spambot on GitHub 7/23/2019, 4:59:51 AM - mebeim (Marco Bonelli): Mine too, could be a person but still looks very fishy 7/23/2019, 4:59:53 AM - sbrl (Starbeamrainbowlabs): How about we take it as a compliment that our project is worth spamming 😛 7/23/2019, 5:00:16 AM - mebeim (Marco Bonelli): Haha, that's the spirit 7/23/2019, 5:01:45 AM - sbrl (Starbeamrainbowlabs): 😃 7/23/2019, 5:02:46 AM - mebeim (Marco Bonelli): Reverted wiki changes, I'd suggest closing the Issue but I'll just wait so that more people notice 7/23/2019, 5:13:13 AM - mebeim (Marco Bonelli): Lol just saw #3204, coincidence? 😂 7/23/2019, 5:53:44 AM - sbrl (Starbeamrainbowlabs): 😛 7/28/2019, 4:16:37 AM - sbrl (Starbeamrainbowlabs): Just seen your comment about astronomer, @mebeim - I've set it going in a `screen` session, so we'll see what happens tomorrow I guess lol 7/28/2019, 5:48:59 AM - sbrl (Starbeamrainbowlabs): Wow, it finished before I went to bed! 7/28/2019, 5:49:00 AM - sbrl (Starbeamrainbowlabs): https://pastebin.com/xgWi7nrk 7/28/2019, 5:49:31 AM - sbrl (Starbeamrainbowlabs): Not _entirely_ sure how to read the output 7/28/2019, 5:53:12 AM - mebeim (Marco Bonelli): lol u only fetched 1k stars... I wanted to try and fetch all of them 😂 7/28/2019, 3:26:37 PM - sbrl (Starbeamrainbowlabs): How do you do that? It didn't give me an option 7/28/2019, 3:26:52 PM - sbrl (Starbeamrainbowlabs): _That's_ why it completed so quickly...... 7/28/2019, 6:02:45 PM - mebeim (Marco Bonelli): With the command line option `-a` 7/28/2019, 6:13:44 PM - sbrl (Starbeamrainbowlabs): ah, ty 7/28/2019, 10:04:34 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/frN7/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/frN7/image.png) 7/28/2019, 10:04:37 PM - sbrl (Starbeamrainbowlabs): Drat! 7/28/2019, 10:05:34 PM - mebeim (Marco Bonelli): Yep... same happened to me! 😟 7/28/2019, 10:06:06 PM - sbrl (Starbeamrainbowlabs): That's a shame. Bug report? 7/28/2019, 10:06:26 PM - mebeim (Marco Bonelli): Not a bug, probably GitHub saying "hey stahp with all these requests" 7/28/2019, 10:07:51 PM - sbrl (Starbeamrainbowlabs): lol 7/28/2019, 10:08:19 PM - sbrl (Starbeamrainbowlabs): Maybe they should add a function to rate-limit it 😛 7/28/2019, 10:09:06 PM - mebeim (Marco Bonelli): I think the ETA would jump to N days with that 😂 7/28/2019, 10:22:37 PM - sbrl (Starbeamrainbowlabs): yeah, but on a server time doesn't matter. I can go for days and check back next week 😛 7/29/2019, 12:59:35 PM - agnivade (Agniva De Sarker): Not sure if it's just me, but the gitter sidebar seems always expanded now. I can't collapse it. 7/29/2019, 12:59:42 PM - agnivade (Agniva De Sarker): Is it the same for you guys ? 7/29/2019, 2:42:25 PM - mebeim (Marco Bonelli): Yes looks like it's the same for me :\ annoying 7/29/2019, 3:02:31 PM - principis (Arthur Bols): Seems to be working for me 7/29/2019, 3:18:34 PM - principis (Arthur Bols): #3168 welp major version bump again 7/29/2019, 3:20:27 PM - sbrl (Starbeamrainbowlabs): Which sidebar? 7/29/2019, 3:20:36 PM - sbrl (Starbeamrainbowlabs): I can collapse both of them 7/29/2019, 3:20:43 PM - sbrl (Starbeamrainbowlabs): 3 lines, bottom corners 7/29/2019, 3:45:55 PM - mebeim (Marco Bonelli): Oh, right, I didn't even see that. 7/29/2019, 8:26:01 PM - agnivade (Agniva De Sarker): Ah thanks @sbrl ! That was a relief 7/30/2019, 7:33:57 PM - mebeim (Marco Bonelli): Hey guys I have a Python script to help translate pages. It finds the next page in alphabetical order that needs to be translated to the chosen language, copies it in the correct folder and opens it in your default text editor. Here it is https://pastebin.com/ubS4G45W I'll leave this here if anyone is interested, I figured it could be helpful to someone. 8/1/2019, 12:16:45 AM - sbrl (Starbeamrainbowlabs): np! 8/1/2019, 12:17:24 AM - sbrl (Starbeamrainbowlabs): And nice @mebiem! What about linking to it in the wiki? 8/1/2019, 12:21:22 AM - mebeim (Marco Bonelli): Maybe, that could be a good idea 🤔 8/3/2019, 1:10:06 AM - agnivade (Agniva De Sarker): I'd suggest to put it in a gist and link it in the wiki 8/3/2019, 1:10:54 AM - mebeim (Marco Bonelli): I'm not sure on which page to link it though 🤔 8/3/2019, 2:22:31 PM - agnivade (Agniva De Sarker): Hey guys, I just ran "npm test" on the tldr repo and saw this - 8/3/2019, 2:22:34 PM - agnivade (Agniva De Sarker): `pages.zh/osx/qlmanage.md: 9: MD032 Lists should be surrounded by blank lines` 8/3/2019, 2:22:44 PM - agnivade (Agniva De Sarker): How come travis is not reporting this ? 8/3/2019, 3:31:34 PM - sbrl (Starbeamrainbowlabs): Hrm, that weird 8/3/2019, 3:31:39 PM - sbrl (Starbeamrainbowlabs): 🤔 8/4/2019, 1:35:44 PM - owenvoke (Owen Voke): It's not something to do with the Chinese characters is it? I guess then it shouldn't error on yours. :thinking: 8/4/2019, 4:47:17 PM - sbrl (Starbeamrainbowlabs): It could be, I guess. Also, does travis run for all languages? 8/4/2019, 4:48:01 PM - mebeim (Marco Bonelli): Nope it does not 8/4/2019, 4:48:24 PM - mebeim (Marco Bonelli): Linter breaks for languages like Chinese if I recall right 8/4/2019, 5:40:04 PM - sbrl (Starbeamrainbowlabs): Ah, that'd be why then! Mystery solved 😛 8/4/2019, 5:40:20 PM - sbrl (Starbeamrainbowlabs): Sounds like we really do need a utf8-capable linter now 8/4/2019, 6:14:24 PM - owenvoke (Owen Voke): Is that output above from markdownlint (runs on all languages) or `tldr-lint`? :slight_smile: 8/4/2019, 6:19:13 PM - mebeim (Marco Bonelli): Hmmm looks like markdownlint. If so that's an issue I was not aware of, should be checked indeed, it's probably just a typo. 8/5/2019, 3:29:07 AM - sbrl (Starbeamrainbowlabs): Blast from the past: Looking through my old blog posts, apparently I was into terminal / bash references even then. I made my own primitive one: https://starbeamrainbowlabs.com/blog/article.php?article=posts/013-Terminal-Reference.html 8/5/2019, 3:29:23 AM - sbrl (Starbeamrainbowlabs): Apparently I was looking for tldr-pages 8/5/2019, 3:34:03 AM - mebeim (Marco Bonelli): 😍 8/5/2019, 2:50:30 PM - agnivade (Agniva De Sarker): It is the result of `bash -c 'markdownlint pages*/**/*.md && tldr-lint ./pages 2>&1 | tee test_result; test ${PIPESTATUS[0]} -eq 0'` 8/5/2019, 2:50:40 PM - agnivade (Agniva De Sarker): so it looks like all pages are being tested 8/5/2019, 2:55:36 PM - agnivade (Agniva De Sarker): And this is what is being executed in the travis tests 8/5/2019, 2:57:05 PM - agnivade (Agniva De Sarker): So travis does indeed run for all languages, except it is not getting any failures. 8/5/2019, 2:57:38 PM - agnivade (Agniva De Sarker): https://travis-ci.org/tldr-pages/tldr/builds/567546184#L200 8/5/2019, 2:57:54 PM - agnivade (Agniva De Sarker): No failures ☝ 8/5/2019, 3:15:32 PM - mebeim (Marco Bonelli): Ok, all pages tested by markdownlint, but only English pages tested by tldr-lint. I will take a look at this later today 👀 8/5/2019, 3:15:33 PM - sbrl (Starbeamrainbowlabs): Very strange 8/5/2019, 3:15:48 PM - sbrl (Starbeamrainbowlabs): Could be environment variables or something? 8/5/2019, 3:15:52 PM - sbrl (Starbeamrainbowlabs): Version of node? 8/5/2019, 8:33:15 PM - agnivade (Agniva De Sarker): Not sure 8/6/2019, 4:15:24 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/1HN4/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/1HN4/image.png) 8/6/2019, 4:16:56 AM - mebeim (Marco Bonelli): Very strange, `markdownlint` doesn't seem to catch this error on my PC. It should fail for "MD032 Lists should be surrounded by blank lines" as per their documentation: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md032 8/6/2019, 4:40:03 AM - mebeim (Marco Bonelli): I opened an issue on their repo: https://github.com/DavidAnson/markdownlint/issues/211 8/6/2019, 5:11:06 AM - sbrl (Starbeamrainbowlabs): :+1: 8/6/2019, 5:11:26 AM - sbrl (Starbeamrainbowlabs): Subscribed 8/6/2019, 3:27:40 PM - waldyrious (Waldir Pimenta): Hey guys, just came across this app: https://github.com/apps/weekly-digest 8/6/2019, 3:28:02 PM - waldyrious (Waldir Pimenta): It produces weekly digests like this: https://github.com/nock/nock/issues/1638 8/6/2019, 3:28:12 PM - waldyrious (Waldir Pimenta): WDYT about installing it? 8/6/2019, 3:31:44 PM - mebeim (Marco Bonelli): Uhm... In my honest opinion that looks like it has more potential to be annoying than useful 😕 8/6/2019, 3:48:38 PM - sbrl (Starbeamrainbowlabs): The commits section does seem a bit verbose. How configurable is it? 8/6/2019, 4:40:04 PM - waldyrious (Waldir Pimenta): According to the repo: > One can change the default configuration of the app by adding a .github/weekly-digest.yml file in their GitHub repository, which allows them to configure the publish day and the specific information included in the digest. 8/6/2019, 4:42:22 PM - waldyrious (Waldir Pimenta): The available options are described here: https://github.com/probot/weekly-digest/blob/master/docs/configuration.md 8/6/2019, 4:48:27 PM - sbrl (Starbeamrainbowlabs): Ah, very interesting. I wonder if it could include the PRs that have been open the longest without any activity or something? 8/6/2019, 4:56:19 PM - waldyrious (Waldir Pimenta): That sounds like an extra feature. We could certainly request it :) 8/6/2019, 4:58:16 PM - waldyrious (Waldir Pimenta): Doesn't seem to be planned: https://github.com/probot/weekly-digest/issues/9 8/6/2019, 4:58:50 PM - waldyrious (Waldir Pimenta): But community input seems to be collected in https://github.com/probot/weekly-digest/issues/1 (although I'd personally prefer a separate issue) 8/6/2019, 5:08:12 PM - waldyrious (Waldir Pimenta): Anyway, what would you say about installing it with `canPublishCommits: false`? @mebeim is there anything else in the example digest that looked too noisy to you? 8/6/2019, 5:13:32 PM - mebeim (Marco Bonelli): Actually to me even just the concept of having an app opening one Issue per week just for some stats seems too noisy 😅 also: listing stale PRs or Issues would basically mean having the usual N Issues always listed, kind of redundant. And lastly, this would conflict with the Issue resolution badge that counts avg # of days for an issue to be resolved. 8/6/2019, 5:21:09 PM - sbrl (Starbeamrainbowlabs): true 8/6/2019, 5:24:41 PM - agnivade (Agniva De Sarker): This seems like a managerial report maker 😛 8/6/2019, 5:41:37 PM - sbrl (Starbeamrainbowlabs): lol yeah 8/6/2019, 6:35:29 PM - waldyrious (Waldir Pimenta): Fair enough. I liked the idea because it provided a way to keep a record of the Pulse report that github itself makes available, since we can't go back in time to other time periods in the native interface. But I can understand why we might not want it as an issue. Perhaps it would be a good idea if the app created wiki pages instead of issues :) 8/6/2019, 6:42:56 PM - mebeim (Marco Bonelli): Yep wiki pages would definitely be better 8/6/2019, 10:10:14 PM - mebeim (Marco Bonelli): So as it turns out from https://github.com/DavidAnson/markdownlint/issues/211 there is no issue with `markdownlint`... that syntax is valid markdown for list item continuation. The check should be made by `tldr-lint`, but we don't currently run that on Chinese pages because reasons. Another reason to update/rewrite the linter. 8/6/2019, 10:11:56 PM - sbrl (Starbeamrainbowlabs): Ah, I see! 8/6/2019, 10:12:00 PM - sbrl (Starbeamrainbowlabs): Mystery solved then 8/6/2019, 10:13:19 PM - mebeim (Marco Bonelli): yep! 8/7/2019, 12:09:18 AM - owenvoke (Owen Voke): Still doesn't make sense that it reported the error for @agnivade though. 🤔 8/7/2019, 12:10:03 AM - owenvoke (Owen Voke): Oh... just read the rest of the issue. Ignore me. :+1: 8/8/2019, 1:58:04 PM - agnivade (Agniva De Sarker): Wait, I still don't understand why does it fail in my machine though ? 8/8/2019, 1:59:12 PM - agnivade (Agniva De Sarker): Is it because my version of markdownlint-cli is old ? 8/8/2019, 2:00:10 PM - agnivade (Agniva De Sarker): Ah yes .. that was it. Wiped out node_modules are reinstalled, and all seems fine. 8/8/2019, 4:23:56 PM - owenvoke (Owen Voke): :+1: 8/19/2019, 8:26:31 PM - sbrl (Starbeamrainbowlabs): Update to my [tldr-missing-pages](https://gitlab.com/sbrl/bin/blob/master/tldr-missing-pages) shell script! I've added a second mode of operation that searches your man page list instead: `tldr-missing-pages man` The old mode is still available via `tldr-missing-pages history`. 8/19/2019, 8:27:03 PM - sbrl (Starbeamrainbowlabs): I'm considering turning it into a 'full' project, packaging it into a .deb file and adding it to my apt repository. 8/19/2019, 9:49:59 PM - owenvoke (Owen Voke): :+1: Neat! 8/19/2019, 10:03:29 PM - mebeim (Marco Bonelli): @sbrl did you add that to the wiki? 8/19/2019, 10:04:07 PM - mebeim (Marco Bonelli): I think we should make a Wiki page called "Useful scripts" or something like that where we can collect stuff like this 8/19/2019, 11:06:35 PM - sbrl (Starbeamrainbowlabs): Nope! Just a random thing I did. I should though! 8/19/2019, 11:06:43 PM - sbrl (Starbeamrainbowlabs): and thanks 😃 8/19/2019, 11:08:54 PM - sbrl (Starbeamrainbowlabs): Hmmmm, looking at the wiki, we've apparently [got a page](https://github.com/tldr-pages/tldr/wiki/Minimum-specifications-for-TLDR-command-line-clients) on the minimum client spec 8/19/2019, 11:09:01 PM - sbrl (Starbeamrainbowlabs): we should point that at the full spec 8/19/2019, 11:19:47 PM - mebeim (Marco Bonelli): Hmm true 8/19/2019, 11:23:46 PM - sbrl (Starbeamrainbowlabs): I've done that 8/19/2019, 11:24:06 PM - sbrl (Starbeamrainbowlabs): But where should put the useful scripts section? 8/19/2019, 11:30:29 PM - mebeim (Marco Bonelli): Well, we currently have this page: https://github.com/tldr-pages/tldr/wiki/Tips-&-Tricks 8/19/2019, 11:30:35 PM - mebeim (Marco Bonelli): I would suggest renaming that page 8/19/2019, 11:31:06 PM - mebeim (Marco Bonelli): I will add my translation helper script when I can 8/20/2019, 12:06:27 AM - sbrl (Starbeamrainbowlabs): Done, @mebeim https://github.com/tldr-pages/tldr/wiki/Useful-scripts-and-programs 8/20/2019, 12:11:43 AM - mebeim (Marco Bonelli): Cool! :+1: Will add mine later 8/20/2019, 12:12:19 AM - sbrl (Starbeamrainbowlabs): 😃 8/20/2019, 7:49:05 AM - mebeim (Marco Bonelli): Added my script :) 8/20/2019, 3:23:29 PM - sbrl (Starbeamrainbowlabs): Awesome! 8/31/2019, 5:46:47 PM - sbrl (Starbeamrainbowlabs): Gosh, tldr-pages is quiet atm. Must be because we're near the start of a new academic year 8/31/2019, 5:47:44 PM - mebeim (Marco Bonelli): It sure is the reason for me! 8/31/2019, 10:59:21 PM - owenvoke (Owen Voke): Been busy with work personally. But still keeping an eye on PRs and issues. 9/1/2019, 12:41:30 AM - sbrl (Starbeamrainbowlabs): Yeah, I've been busy with my Msc report 9/1/2019, 6:11:33 AM - waldyrious (Waldir Pimenta): And I just got married! 😁 9/1/2019, 9:54:43 AM - mebeim (Marco Bonelli): @waldyrious Woah! Congratulations!!! 🎉🎊🎈 9/1/2019, 10:51:26 AM - owenvoke (Owen Voke): Wow! Congrats. 🎉 9/1/2019, 4:28:32 PM - sbrl (Starbeamrainbowlabs): Oh, wow congrats @waldyrious! Hope you have many happy years to come with your new partner 😃 9/3/2019, 9:44:07 AM - agnivade (Agniva De Sarker): Congrats @waldyrious !! wohooo ! 9/9/2019, 1:07:54 AM - sbrl (Starbeamrainbowlabs): [![Selection_023.png](https://files.gitter.im/tldr-pages/tldr/N3Do/thumb/Selection_023.png)](https://files.gitter.im/tldr-pages/tldr/N3Do/Selection_023.png) 9/9/2019, 1:08:04 AM - sbrl (Starbeamrainbowlabs): Just received this in an email 9/9/2019, 1:08:20 AM - sbrl (Starbeamrainbowlabs): I haven't seen @igorshubovych around for a while. 9/9/2019, 1:08:28 AM - sbrl (Starbeamrainbowlabs): Anyone know what "CodeHub" is? 9/9/2019, 1:15:59 AM - mebeim (Marco Bonelli): Ah, CodeHub is an application for iOS, a GitHub client basically. I used to use it a while ago. Looks like @igorshubovych request access to the organization through CodeHub or something like that. 9/9/2019, 1:25:53 AM - sbrl (Starbeamrainbowlabs): Ah, right. Just unsure as to whether I should approve it or deny it 9/9/2019, 1:46:34 AM - mebeim (Marco Bonelli): Well it seems odd, if a user is part of an org shouldn't they already have the needed privileges to do stuff inside the org? Or is @igorshubovych not part of the org? Either way looks strange, never seen an app request access to the org itself rather than the user. 9/9/2019, 2:27:39 AM - sbrl (Starbeamrainbowlabs): Apparently apps require admin approval to be used with repos in an org 9/9/2019, 2:27:50 AM - sbrl (Starbeamrainbowlabs): other than that I'm not sure :shrugs: 9/17/2019, 1:46:37 AM - waldyrious (Waldir Pimenta): Thanks guys ^_^ 9/17/2019, 1:46:51 AM - waldyrious (Waldir Pimenta): Just got back from the honeymoon :) 9/17/2019, 1:47:33 AM - waldyrious (Waldir Pimenta): as for the permission request, in my experience such apps typically ask for more permissions than they need (or maybe it's github's permission system that's not granular enough) 9/17/2019, 1:48:32 AM - waldyrious (Waldir Pimenta): it would be useful if we had private repos in our org, but since all our repos are already public, denying the request will have no impact in Igor's usage of the app. 9/17/2019, 2:05:19 AM - sbrl (Starbeamrainbowlabs): Cool, thanks @waldyrious 9/17/2019, 2:05:29 AM - sbrl (Starbeamrainbowlabs): So I'll approve it then? 9/17/2019, 2:48:26 AM - waldyrious (Waldir Pimenta): I was suggesting the opposite :) there's no need for giving the app special access to our org, as all our content is accessible to it already. So it should be safe to reject the request. 9/17/2019, 2:57:34 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I'll reject it then. 9/17/2019, 3:01:00 AM - sbrl (Starbeamrainbowlabs): Done. 9/17/2019, 3:01:16 AM - sbrl (Starbeamrainbowlabs): Also, we seem to have it set as a policy to ask about applications: 9/17/2019, 3:01:20 AM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/oWrb/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/oWrb/image.png) 9/17/2019, 3:09:47 AM - waldyrious (Waldir Pimenta): That sounds sensible to me. Btw what are the Branches and Codetree apps used for? 9/17/2019, 3:23:36 AM - sbrl (Starbeamrainbowlabs): Good question. I have no idea 9/17/2019, 3:24:32 AM - sbrl (Starbeamrainbowlabs): Here's the full list 9/17/2019, 3:24:36 AM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/u5mG/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/u5mG/image.png) 9/17/2019, 3:24:48 AM - sbrl (Starbeamrainbowlabs): We might want to check that we're using all the applications on that list 9/17/2019, 5:10:26 AM - mebeim (Marco Bonelli): i'd say deny everything that we don't directly recognize and leave only travis and cla 9/17/2019, 5:11:31 AM - mebeim (Marco Bonelli): then if someone was using one of those apps and it suddenly asks for permission again it's easy to spot and allow if needed 9/18/2019, 11:10:09 PM - agnivade (Agniva De Sarker): I think most of the unrecognizable ones were added during our GCI stint 9/18/2019, 11:10:32 PM - agnivade (Agniva De Sarker): Might as well remove them and see what breaks 9/20/2019, 9:18:21 PM - agnivade (Agniva De Sarker): Welcome back @waldyrious :) I see you are already adding some polish to new pages. 9/21/2019, 3:33:05 PM - waldyrious (Waldir Pimenta): Thanks! Still much less than what I'd like to be doing (as usual 😅) but it's a start :) 9/21/2019, 3:47:51 PM - waldyrious (Waldir Pimenta): As for the apps, I agree, let's remove anything we don't know for sure why they're there 9/22/2019, 10:25:18 PM - agnivade (Agniva De Sarker): Done. Most of them were requested by you @waldyrious 9/22/2019, 10:25:45 PM - agnivade (Agniva De Sarker): A lot were kanban style issue tracking apps that we were experimenting with in the past. 9/22/2019, 10:30:21 PM - sbrl (Starbeamrainbowlabs): Cool 9/22/2019, 11:35:16 PM - owenvoke (Owen Voke): :+1: 9/25/2019, 8:53:51 PM - agnivade (Agniva De Sarker): Hacktoberfest is live . .but atleast they have limited to first 50000 9/25/2019, 8:54:04 PM - agnivade (Agniva De Sarker): I was wondering how they will be able to keep up sending sooo many tshirts :) 9/25/2019, 8:54:25 PM - agnivade (Agniva De Sarker): Atleast the PR bar is still 4 9/26/2019, 3:46:38 AM - owenvoke (Owen Voke): I didn't think the PRs counted until 1st Oct. 🤔 But yeah! Should be good for tldr pages. 9/26/2019, 3:57:00 AM - sbrl (Starbeamrainbowlabs): PR bar is still 4? And oh yeah! We should rename the help wanted tag again 10/2/2019, 8:56:18 AM - agnivade (Agniva De Sarker): The hacktoberfest traffic has started to come. 10/2/2019, 8:56:23 AM - agnivade (Agniva De Sarker): I have renamed the tag now. 10/2/2019, 11:35:47 AM - mebeim (Marco Bonelli): oh wow, doubles the PRs in one day! 10/2/2019, 6:50:10 PM - mebeim (Marco Bonelli): Guys what do you think about adding a "question" label so that we can mark issues that are only just simple questions with it? 10/2/2019, 6:57:08 PM - mebeim (Marco Bonelli): I created and applied it here as a good first example, let me know what you think :) https://github.com/tldr-pages/tldr/issues/3269 10/2/2019, 9:06:49 PM - sbrl (Starbeamrainbowlabs): Gosh, definitely seeing the increased October traffic here. Definitely a great time for tldr-pages expansion! Also, yeah - that's good idea! 10/2/2019, 9:07:27 PM - sbrl (Starbeamrainbowlabs): I've processed and reviewed all my notifications. 10/2/2019, 9:12:24 PM - agnivade (Agniva De Sarker): I really need to find some time to finish the lang support for node client. 10/2/2019, 9:12:52 PM - sbrl (Starbeamrainbowlabs): :+1: 10/2/2019, 9:13:10 PM - sbrl (Starbeamrainbowlabs): Yeah, we've had a few questions about it 10/2/2019, 9:13:25 PM - agnivade (Agniva De Sarker): Btw @mebeim, thanks for following up on #3269. 10/2/2019, 9:20:22 PM - mebeim (Marco Bonelli): Pleasure! 🙂 10/2/2019, 9:20:57 PM - mebeim (Marco Bonelli): BTW these guys are pretty fast to address review comments, woah 10/2/2019, 9:36:09 PM - sbrl (Starbeamrainbowlabs): Oh my, they are right?! 10/2/2019, 9:37:36 PM - mebeim (Marco Bonelli): Yeah, can't even blink 😅 10/2/2019, 9:40:19 PM - sbrl (Starbeamrainbowlabs): 😛 10/3/2019, 12:11:12 PM - agnivade (Agniva De Sarker): SO. MANY. NOTIFICATIONS. I am subscribed to multiple high traffic repos. I am just tempted to hit the "mark all read" button. 10/3/2019, 12:13:25 PM - mebeim (Marco Bonelli): Oh gawd! I can only imagine 😅 @agnivade you're also in the golang repo right? How many (%) from there? I always wondered... 10/3/2019, 1:11:58 PM - agnivade (Agniva De Sarker): Yeah .. right now it's night in US so it's low. But I will let you know tomorrow morning when I wake up. Usually it's a 90-10 split. Now it seems to be 65-35. 10/3/2019, 1:13:55 PM - mebeim (Marco Bonelli): well, fair enough, that's a big org 10/3/2019, 3:29:09 PM - sbrl (Starbeamrainbowlabs): Oh gosh, it's super busy. I'm glad tldr-pages is the only high-traffic repo I maintain 10/3/2019, 6:15:09 PM - mebeim (Marco Bonelli): Seems this commit message wasn't cleaned up when squashing, unlucky https://github.com/tldr-pages/tldr/commit/1e704a118bb218607f04eaacfe21adc3321865c7 10/3/2019, 6:18:29 PM - sbrl (Starbeamrainbowlabs): Oops! I think I hit ctrl + enter too quick on that one @mebeim 10/3/2019, 6:18:41 PM - sbrl (Starbeamrainbowlabs): I do wonder how everyone always notices that 😛 10/3/2019, 7:04:22 PM - mebeim (Marco Bonelli): When I see a triple dot near the commit I'm always courious :') 10/3/2019, 7:26:39 PM - sbrl (Starbeamrainbowlabs): 😛 10/4/2019, 1:29:21 AM - sbrl (Starbeamrainbowlabs): Oof, my GH notifications look like I haven't checked them today 10/4/2019, 1:29:30 AM - sbrl (Starbeamrainbowlabs): but I did them earlier today lol 10/4/2019, 8:44:34 AM - agnivade (Agniva De Sarker): Okay so I have exactly 100 notifications - 62 golang/go, 36 tldr, 2 golang/tools. Kinda exactly what I predicted. 10/4/2019, 10:05:30 AM - mebeim (Marco Bonelli): that's quite the number of notifications 😅 10/4/2019, 3:18:15 PM - sbrl (Starbeamrainbowlabs): Wow, that's a lot! 10/6/2019, 4:27:23 PM - sbrl (Starbeamrainbowlabs): I've packaged my `tldr-missing-pages` script and put it in my apt repository! https://apt.starbeamrainbowlabs.com/ It should work for all Debian-based distributions. Once the apt repo is setup, just do `sudo apt install tldr-missing-pages` 10/6/2019, 5:19:38 PM - mebeim (Marco Bonelli): nice! 10/6/2019, 5:20:18 PM - sbrl (Starbeamrainbowlabs): 😃 10/7/2019, 9:10:54 AM - agnivade (Agniva De Sarker): wow you have an apt repository .. nice 10/7/2019, 3:27:49 PM - sbrl (Starbeamrainbowlabs): Yeah! I wasn't actually that difficult to setup. I just adapted a script from unix.stackexchange.com 10/7/2019, 3:28:39 PM - sbrl (Starbeamrainbowlabs): Link to said adaptation: https://git.starbeamrainbowlabs.com/sbrl/aptosaurus 10/9/2019, 4:14:07 AM - sbrl (Starbeamrainbowlabs): I've been rather ill, and now my notifications have exploded! I've had to mark merged PRs as read to bring the count down to reasonable levels. If there's anything I've missed, please let me know. 10/9/2019, 5:08:51 AM - sbrl (Starbeamrainbowlabs): Phew, all done! 10/9/2019, 5:09:05 AM - sbrl (Starbeamrainbowlabs): ....October is such an intense month for tldr-pages 10/9/2019, 1:51:04 PM - agnivade (Agniva De Sarker): No worries. Feel better soon ! 10/9/2019, 3:40:07 PM - sbrl (Starbeamrainbowlabs): Thanks - I think I'm over the worst of it now :-) 10/9/2019, 10:02:07 PM - schneiderl (Lucas Gabriel Schneider): Haven't been around here in a while. Is tldr traffic so high only because of hacktoberfest or is there another reason that I'm unaware of? 10/9/2019, 10:59:08 PM - mebeim (Marco Bonelli): Nah just hacktoberfest 10/10/2019, 12:16:50 AM - sbrl (Starbeamrainbowlabs): Yeah, it's hacktoberfest @schneiderl 10/10/2019, 12:17:07 AM - sbrl (Starbeamrainbowlabs): It got busy around this time last year, but I think it's busier this year than it was last year 1/14/2023, 3:32:19 PM - andrik (Andrik Albuquerque) joined the room 10/10/2019, 6:36:51 AM - andrik (Andrik Albuquerque): Hi guys, I'm wondering if it would be nice to have a categorization of commands on tldr. I'm saying that because I see the project not just a reference for commands that we already know, but as a learning project for new tools/commands. That way would be easy to look for new commands under a category. As a reference, I use a lot of Ruby Toolbox (https://www.ruby-toolbox.com/categories) to know new projects that could be useful to me. Even GNU Coreutils (https://www.gnu.org/software/coreutils/manual/html_node/index.html) provides a kind of categorization of commands What do you guys think about that? 10/10/2019, 9:57:12 AM - agnivade (Agniva De Sarker): Are you talking about adding multiple tags to a page ? I think this was discussed before .. probably already has an issue 10/10/2019, 3:23:26 PM - sbrl (Starbeamrainbowlabs): It would be interesting to categorise commands. I'm not sure how the syntax would work for that though 10/11/2019, 5:34:01 PM - agnivade (Agniva De Sarker): @waldyrious - https://github.com/tldr-pages/tldr-pages.github.io/pull/36#issuecomment-540987649 was likely a spam. Hence I didn't bother to comment much. 10/11/2019, 6:16:41 PM - mebeim (Marco Bonelli): very strange pr 10/11/2019, 6:34:53 PM - sbrl (Starbeamrainbowlabs): Indeed 10/11/2019, 6:35:06 PM - sbrl (Starbeamrainbowlabs): There was the Quickstart.md one recently too 10/11/2019, 6:35:09 PM - sbrl (Starbeamrainbowlabs): equally confusing 10/11/2019, 7:36:07 PM - waldyrious (Waldir Pimenta): yeah @agnivade I figured as much, but I commented anyway just to err on the side of caution, and also to make sure it doesn't look bad to others who may come across the conversation and not realize the context. 10/11/2019, 7:36:21 PM - waldyrious (Waldir Pimenta): It's best to seem too nice than too rough IMO :) 10/11/2019, 7:44:47 PM - sbrl (Starbeamrainbowlabs): :+1: 10/11/2019, 8:37:40 PM - waldyrious (Waldir Pimenta): PSA: Spam PRs should be tagged with the `invalid` label so they don't count for Hacktoberfest. I already did that for https://github.com/tldr-pages/tldr-pages.github.io/pull/36 10/11/2019, 8:37:54 PM - waldyrious (Waldir Pimenta): https://hacktoberfest.digitalocean.com/details#spam 10/11/2019, 9:05:04 PM - agnivade (Agniva De Sarker): Yeah, clearly this person is trying to get a t-shirt - https://github.com/tldr-pages/tldr-python-client/pull/80 10/11/2019, 9:08:31 PM - waldyrious (Waldir Pimenta): yeah, I had that tab open, I'll try to think about a good way to close it without sounding rude 😛 10/11/2019, 10:54:51 PM - sbrl (Starbeamrainbowlabs): Ah, I see. It all makes sense now. What about something along the lines of we're already considering a logo? I think we've got an issue open about it somewhere. 10/11/2019, 10:55:48 PM - waldyrious (Waldir Pimenta): Yeah, we do. If you want to respond, please go ahead. I probably won't be able to do it today, but was aiming for tomorrow 10/11/2019, 11:00:55 PM - sbrl (Starbeamrainbowlabs): I'm actually in the middle of reading a scientific paper on flood risk and machine learning for my PhD, so if I do it it'll have to wait until later 10/11/2019, 11:02:16 PM - waldyrious (Waldir Pimenta): Oh, don't worry then! I just said that in case you wanted to do it and didn't want to step on my toes or something :) 10/11/2019, 11:02:36 PM - waldyrious (Waldir Pimenta): Didn't know you were doing a PhD, good luck! 10/11/2019, 11:03:37 PM - sbrl (Starbeamrainbowlabs): Ah, np! I'll do it if I get around to it before you lol 😛 And yeah, I am! I think I forgot to mention it here. "Using the Internet of Things and big data to dynamically map flood risk" is the title 10/11/2019, 11:03:52 PM - sbrl (Starbeamrainbowlabs): Thanks - I think I'll need it lol 10/11/2019, 11:06:32 PM - waldyrious (Waldir Pimenta): In my experience, the most important thing you will need is to make sure you align what you spend your energy on, with what the program expects of you (usually publications) 10/11/2019, 11:07:03 PM - waldyrious (Waldir Pimenta): Unfortunately in many places people don't care that much about the science (e.g. negative results) 10/11/2019, 11:07:08 PM - waldyrious (Waldir Pimenta): Anyway, gotta go, ttyl! 10/11/2019, 11:09:07 PM - sbrl (Starbeamrainbowlabs): Yeah. My supervisor does seem to be enthusiastic about the science. There's definitely a leaning towards the "contributing modest new knowledge" bit, what with the 6 monthly reviews and technical panels I'm going to have later, apparently 10/11/2019, 11:09:34 PM - sbrl (Starbeamrainbowlabs): See you later! And yeah, negative results are just as important! I think someone mentioned that in the welcome talks. 10/12/2019, 3:11:23 PM - owenvoke (Owen Voke): We don't appear to have an `invalid` label on the main tldr repository, should this be added? 🤔 10/12/2019, 3:11:53 PM - waldyrious (Waldir Pimenta): I think so 10/12/2019, 3:34:29 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/Tptu/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/Tptu/image.png) 10/12/2019, 3:34:49 PM - sbrl (Starbeamrainbowlabs): Created the label. #ffffff with the description "Something doesn't look right." 10/12/2019, 3:35:15 PM - sbrl (Starbeamrainbowlabs): Come to think of it, only 2 other labels have descriptions 10/12/2019, 3:53:35 PM - waldyrious (Waldir Pimenta): Yeah, we need to improve that 10/12/2019, 4:21:40 PM - owenvoke (Owen Voke): Cheers, I'm going to leave #3370 for a couple more days and see if I get a reply. But seems like it's `invalid`. 10/12/2019, 4:28:32 PM - sbrl (Starbeamrainbowlabs): :+1: 10/12/2019, 4:30:45 PM - waldyrious (Waldir Pimenta): I think since you replied very soon after the PR was created, we don't need to wait much longer. Two days have passed already 10/12/2019, 4:31:08 PM - waldyrious (Waldir Pimenta): IMO we could mark it as invalid and close it, telling the user to request reopening if there was a mistake. 10/12/2019, 4:35:24 PM - mebeim (Marco Bonelli): Agree^ 10/12/2019, 4:35:46 PM - mebeim (Marco Bonelli): Also, what's the requirement to get a T-Shirt from Hacktoberfest? 10/12/2019, 4:36:38 PM - waldyrious (Waldir Pimenta): I think having submitted four PRs that don't get marked as invalid within a week is sufficient 10/12/2019, 4:36:50 PM - waldyrious (Waldir Pimenta): up to the maximum of 50k T-shirts 10/12/2019, 4:41:06 PM - mebeim (Marco Bonelli): So could I get one even if I register after the PRs were merged? I already did 4 haha 10/12/2019, 4:42:53 PM - sbrl (Starbeamrainbowlabs): I thought it was 5 last year? 10/12/2019, 4:49:34 PM - waldyrious (Waldir Pimenta): Yeah, I think they tweak the numbers each year 10/12/2019, 4:49:44 PM - waldyrious (Waldir Pimenta): The spam think was new this year IIRC 10/12/2019, 4:51:04 PM - waldyrious (Waldir Pimenta): Btw, I'm right now in a local event for the Hacktoberfest, and of course I pitched tldr-pages as a project people could contribute to 😉 10/12/2019, 4:51:34 PM - waldyrious (Waldir Pimenta): some PRs have already been created! 10/12/2019, 4:52:38 PM - sbrl (Starbeamrainbowlabs): Awesome! 10/12/2019, 4:53:07 PM - sbrl (Starbeamrainbowlabs): I've never actually been to a programming even like jam/hackathon/hacktoberfest event before 10/12/2019, 4:55:38 PM - sbrl (Starbeamrainbowlabs): Just to confirm: tldr pages are in en-US, right? My native language is en-GB, and I'm reviewing #3381 10/12/2019, 5:12:11 PM - waldyrious (Waldir Pimenta): You should definitely try going to such an event, they're great for meeting like-minded people and learn new stuff :) 10/12/2019, 5:12:53 PM - waldyrious (Waldir Pimenta): As for the language, I don't think we should enforce a variant. If someone creates a page using a consistent variant throughout (e.g. "colour" instead of "color"), IMO we should allow that. 10/12/2019, 5:13:26 PM - waldyrious (Waldir Pimenta): It's not like pt_BR and pt_PT where there may be significant differences in vocabulary 10/12/2019, 5:16:33 PM - sbrl (Starbeamrainbowlabs): Right, ok 10/12/2019, 7:45:26 PM - waldyrious (Waldir Pimenta): Do you guys have any idea why the Travis build keeps failing for this PR? https://github.com/tldr-pages/tldr/pull/3386 10/12/2019, 8:04:28 PM - sbrl (Starbeamrainbowlabs): Looks like it passed for me 10/12/2019, 8:05:08 PM - sbrl (Starbeamrainbowlabs): [![Screenshot_2019-10-12 csvkit add file by GuilhermeJSilva · Pull Request #3386 · tldr-pages tldr.png](https://files.gitter.im/tldr-pages/tldr/7Dly/thumb/Screenshot_2019-10-12-csvkit-add-file-by-GuilhermeJSilva-Pull-Request-3386-tldr-pages-tldr.png)](https://files.gitter.im/tldr-pages/tldr/7Dly/Screenshot_2019-10-12-csvkit-add-file-by-GuilhermeJSilva-Pull-Request-3386-tldr-pages-tldr.png) 10/12/2019, 8:05:19 PM - sbrl (Starbeamrainbowlabs): The user hasn't signed the CLA yet, so it can't be mrged. 10/12/2019, 8:05:23 PM - sbrl (Starbeamrainbowlabs): @waldyrious 10/12/2019, 8:07:45 PM - waldyrious (Waldir Pimenta): Ah, my bad. Thanks for the heads-up :+1: 10/12/2019, 8:10:13 PM - sbrl (Starbeamrainbowlabs): Np! I've done a full review on that one too. It seems like it's a page for a toolkit, rather than a command. 10/12/2019, 8:10:44 PM - waldyrious (Waldir Pimenta): Yes, that was my first comment. I recall when the commands were introduced back in #702 :) 10/12/2019, 8:10:45 PM - sbrl (Starbeamrainbowlabs): I'm concerned about discoverability in that instance - generally users will do a `tldr command_name`, rather than `tldr toolkit_name` 10/12/2019, 8:11:42 PM - waldyrious (Waldir Pimenta): The individual pages are already there, so this page is a net positive, since it helps those who use the former approach :) 10/12/2019, 8:11:53 PM - sbrl (Starbeamrainbowlabs): Ah, right - I see! 10/12/2019, 8:12:13 PM - sbrl (Starbeamrainbowlabs): My notifications are looking quite daunting again lol 10/12/2019, 8:12:34 PM - sbrl (Starbeamrainbowlabs): You'd never believe I worked through them all last night 10/12/2019, 8:12:59 PM - waldyrious (Waldir Pimenta): Sorry, I am responsible for about a dozen of those 😅 10/12/2019, 8:13:14 PM - waldyrious (Waldir Pimenta): one of the guys in the hackathon I'm in went all in with the Portuguese pages! 10/12/2019, 8:13:51 PM - sbrl (Starbeamrainbowlabs): No problem! More for tldr pages 😃 10/12/2019, 8:14:19 PM - sbrl (Starbeamrainbowlabs): We do need to sort translations out at some point though. There was a PR for that, but I'm not what happened to the idea 10/12/2019, 8:15:22 PM - waldyrious (Waldir Pimenta): Yeah 😟 I have been struggling to rework my routines to make room for this work, but it's been challenging 10/12/2019, 8:21:05 PM - sbrl (Starbeamrainbowlabs): Don't worry about it :-) 10/12/2019, 8:22:38 PM - waldyrious (Waldir Pimenta): I know the project is in great hands, that's not the issue :) but there are so many things I've been wanting to do in its scope, and it's frustrating to see my backlog just continue to grow 10/12/2019, 9:24:12 PM - sbrl (Starbeamrainbowlabs): Yeah, I can relate to that. 10/12/2019, 10:23:22 PM - agnivade (Agniva De Sarker): local meetups are great ! It's a great way to network and connect with the community working on similar stuff. 10/12/2019, 10:23:53 PM - sbrl (Starbeamrainbowlabs): Indeed! I attend a local hardware / embedded systems meetup myself 10/12/2019, 10:25:40 PM - agnivade (Agniva De Sarker): Re: backlog, I think setting aside a dedicated time to go through some issues so that they never exceed a threshold is how I do it. Sometimes though, when I'm not in the mood, I just ignore some notifications knowing that I will anyways be pinged individually if anything is needed from me. I have come to realize that one cannot look into _every single change_ in a project. 10/12/2019, 10:30:33 PM - sbrl (Starbeamrainbowlabs): I usually ignore a PR if someone else has reviewed it, until they add their approval 10/12/2019, 10:44:22 PM - owenvoke (Owen Voke): Thanks for closing that PR @agnivade, I was on a dog walk and then forgot about it. 👌 10/13/2019, 8:33:03 AM - agnivade (Agniva De Sarker): no worries :) 10/13/2019, 4:49:19 PM - sbrl (Starbeamrainbowlabs): I'm marking the pt_BR translations as read. If anyone needs me in those PRs, please @summon me 😛 10/13/2019, 7:13:07 PM - mebeim (Marco Bonelli): same 👀 10/13/2019, 8:21:16 PM - agnivade (Agniva De Sarker): Loving the "improve grammar" PRs 10/13/2019, 8:25:22 PM - sbrl (Starbeamrainbowlabs): 😛 10/13/2019, 8:26:00 PM - sbrl (Starbeamrainbowlabs): Personally my focus would be on expanding to new pages, rather than making sure the current ones are 'perfect' 10/13/2019, 8:26:12 PM - sbrl (Starbeamrainbowlabs): not to say that improving existing pages isn't important 10/14/2019, 12:08:15 AM - mebeim (Marco Bonelli): yeah but they are very simple and straight forward PRs, so I like when people does that too 10/14/2019, 12:08:37 AM - mebeim (Marco Bonelli): instead of saying "huh it's a minor typo it'll just get fixed sometime in the future" 10/14/2019, 12:26:53 AM - sbrl (Starbeamrainbowlabs): true! 10/14/2019, 4:26:57 PM - waldyrious (Waldir Pimenta): I actually think it's important to welcome all types of contributions, regardless of their perceived importance: first because that allows us to attract a wider set of people who may be more inclined to work in some aspects than others; and second because neglected aspects tend to pile up over time, which would later require a large cleanup effort to address, synchronization effort to make sure no toes are stepped on (e.g. git conflicts due to concurrent PRs), and so on 10/14/2019, 5:12:07 PM - sbrl (Starbeamrainbowlabs): :+1: 10/17/2019, 1:19:45 AM - sbrl (Starbeamrainbowlabs): All these PRs that are clearly just trying to get a t-shirt are taking lots of time to review. For example, #3423 10/17/2019, 1:50:22 AM - mebeim (Marco Bonelli): Yeah... All these seemingly pointless PRs are costing more effort than they should :\ 10/17/2019, 9:25:06 AM - agnivade (Agniva De Sarker): Thanks, commented. Don't go above and beyond with trying to review lot of PRs. That just reduces review quality. Peace of mind is more important than somebody sneakily getting a t-shirt. 10/17/2019, 9:52:50 PM - schneiderl (Lucas Gabriel Schneider): Hi, What about #3428 and #3427, should we tag them as invalid? The PRs are just copying pages from common to osx. 10/17/2019, 9:54:27 PM - mebeim (Marco Bonelli): If that's the case, I would definitely say yes, and also close them explaining why. 10/18/2019, 1:20:14 AM - sbrl (Starbeamrainbowlabs): :+1: @mebeim. Yeah, the explaining why is important I think 10/18/2019, 4:56:17 PM - agnivade (Agniva De Sarker): Yeah, the author hasn't even replied back. And he created one more, which I already marked invalid. I think we can do these too. 1/14/2023, 3:32:54 PM - dddeveloperrr (farhad) joined the room 10/20/2019, 4:25:20 PM - dddeveloperrr (farhad): hello guys, I installed TLDR via snap. how can I get a colored output in tldr? at the moment, all output in my terminal is in White color. thanks 10/20/2019, 5:28:06 PM - sbrl (Starbeamrainbowlabs): Hey, @dddeveloperrr! That depends on which client it is that the snap package installed. Does the description give anything away? 10/20/2019, 8:42:11 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/q4Tt/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/q4Tt/image.png) 10/20/2019, 8:43:12 PM - sbrl (Starbeamrainbowlabs): @mebeim ❤️ 😃 10/23/2019, 9:29:02 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/WDzy/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/WDzy/image.png) 10/23/2019, 9:29:10 PM - mebeim (Marco Bonelli): @sbrl Is this checked on the tldr repo? 10/23/2019, 9:29:40 PM - mebeim (Marco Bonelli): I remember some time ago there was someone who was not a collaborator trying to add random sketchy links in the wiki 10/23/2019, 9:39:24 PM - sbrl (Starbeamrainbowlabs): I don't think so @mebeim 10/23/2019, 9:39:26 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/L9AC/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/L9AC/image.png) 10/23/2019, 9:39:35 PM - sbrl (Starbeamrainbowlabs): Is this the box you're talking about? 10/23/2019, 9:39:43 PM - sbrl (Starbeamrainbowlabs): I can tick if you like 10/23/2019, 9:46:27 PM - mebeim (Marco Bonelli): It'd probably be better, to avoid unwanted edits from non-trusted people. 10/23/2019, 10:08:06 PM - sbrl (Starbeamrainbowlabs): Right. 10/23/2019, 10:08:22 PM - sbrl (Starbeamrainbowlabs): Done, @mebeim 10/23/2019, 10:09:05 PM - mebeim (Marco Bonelli): nice 10/23/2019, 10:38:40 PM - owenvoke (Owen Voke): :+1: 10/24/2019, 12:16:17 AM - sbrl (Starbeamrainbowlabs): #3463 appears to be spam too. 10/24/2019, 12:16:36 AM - sbrl (Starbeamrainbowlabs): What bothers me is people try to pass other people's work of as their own 10/24/2019, 12:18:14 AM - sbrl (Starbeamrainbowlabs): Should we tag it with invalid and close? 10/24/2019, 12:19:06 AM - sbrl (Starbeamrainbowlabs): Looks like they just cherry-picked the commit & opened a new PR 10/24/2019, 12:28:29 AM - mebeim (Marco Bonelli): What... 10/24/2019, 12:28:39 AM - mebeim (Marco Bonelli): wait, how is that PR even possible? wut 10/24/2019, 12:29:12 AM - mebeim (Marco Bonelli): it doesn't change anything, how come GitHub shows it as adding a file that already exists with the exact same content? 10/24/2019, 12:32:06 AM - mebeim (Marco Bonelli): And indeed I also tagged it as "new command" thinking it was a legit new command... the user basically took your branch @sbrl and created a PR for it to be merged on master. 10/24/2019, 12:33:40 AM - mebeim (Marco Bonelli): So: 1. That branch (page/mssh) should have been deleted when merging, but that's not the problem. 2. GitHub is seriously bugged in allowing something like this... .__. 10/24/2019, 12:35:19 AM - sbrl (Starbeamrainbowlabs): Indeed, it baffles me too 10/24/2019, 12:36:06 AM - sbrl (Starbeamrainbowlabs): I've got a habit now of doing a `tldr {{command}}` if I sort of remember a previoous PR for that command now lol 10/24/2019, 12:36:29 AM - mebeim (Marco Bonelli): They did not cherry-pick though, I think they just saw the existing branch and though "oh ok, let's merge it to master"... 10/24/2019, 12:37:30 AM - sbrl (Starbeamrainbowlabs): Ah, I see 10/24/2019, 12:37:38 AM - sbrl (Starbeamrainbowlabs): Should delete the branch then 10/24/2019, 12:37:43 AM - sbrl (Starbeamrainbowlabs): I'll do that now 10/24/2019, 12:37:50 AM - mebeim (Marco Bonelli): Yeah but please don't do it right away 10/24/2019, 12:38:19 AM - mebeim (Marco Bonelli): Just keep everything as is for now so that we can take a closer look at this, it is very interesting 10/24/2019, 12:38:28 AM - sbrl (Starbeamrainbowlabs): ok 10/24/2019, 12:38:47 AM - sbrl (Starbeamrainbowlabs): Can't delete it through the web ui until the PR is closed, anyway 10/24/2019, 12:39:17 AM - mebeim (Marco Bonelli): Is there a way to "lock" the PR so that it cannot be closed? 10/24/2019, 12:42:04 AM - mebeim (Marco Bonelli): Hmm, bummer, I don't think so. Need to check if this is a bug in GitHub or git, not that easy though 10/24/2019, 12:42:13 AM - sbrl (Starbeamrainbowlabs): Sort of 10/24/2019, 12:42:28 AM - sbrl (Starbeamrainbowlabs): As an admin I can lock the conversation 10/24/2019, 12:42:38 AM - mebeim (Marco Bonelli): By locking I don't mean locking the conversation, I mean locking the state (open/closed) 10/24/2019, 12:42:38 AM - sbrl (Starbeamrainbowlabs): But then the PR opener can't respond lol 10/24/2019, 12:43:11 AM - mebeim (Marco Bonelli): Yeah that's not needed 10/24/2019, 12:43:20 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I left a request changes to block ordinary merges 10/24/2019, 12:43:44 AM - sbrl (Starbeamrainbowlabs): So you've got to be an admin to merge it 10/24/2019, 12:44:02 AM - mebeim (Marco Bonelli): yep, saw that 10/24/2019, 12:44:11 AM - sbrl (Starbeamrainbowlabs): You've got to tick a checkbox you see 10/24/2019, 12:44:21 AM - sbrl (Starbeamrainbowlabs): I think that's the closest we get 10/24/2019, 12:44:38 AM - sbrl (Starbeamrainbowlabs): On a happier note, @einverne is really close to being a collaborator! 10/24/2019, 12:44:39 AM - mebeim (Marco Bonelli): yeah I guess 10/24/2019, 12:44:58 AM - mebeim (Marco Bonelli): Yeah I noticed :) 10/24/2019, 12:45:03 AM - sbrl (Starbeamrainbowlabs): Does #3251 count as non-trivial? 10/24/2019, 12:45:14 AM - sbrl (Starbeamrainbowlabs): I merged #3454 10/24/2019, 12:45:39 AM - mebeim (Marco Bonelli): hrm, 3251 looks pretty trivial haha 10/24/2019, 12:46:08 AM - sbrl (Starbeamrainbowlabs): Then we're waiting on #3459 I think 10/24/2019, 1:04:11 AM - mebeim (Marco Bonelli): By the way the exact problem already happened in #3416 10/24/2019, 1:04:49 AM - sbrl (Starbeamrainbowlabs): Hrm. Again? Definitely need to close and delete the branch then 10/24/2019, 1:04:54 AM - sbrl (Starbeamrainbowlabs): Sounds like it's confusing people 10/24/2019, 1:05:08 AM - mebeim (Marco Bonelli): After playing a bit with `git` on my terminal I'm pretty sure this is a GitHub bug. 10/24/2019, 1:05:26 AM - mebeim (Marco Bonelli): git allows to merge something that does not introduce any change, it just results in an empty commit 10/24/2019, 1:06:04 AM - sbrl (Starbeamrainbowlabs): Hrm. I wonder if it's possible to report this? 10/24/2019, 1:06:05 AM - mebeim (Marco Bonelli): but here GitHub is showing changes that really should not be there, since the PR is trying to add a page that already exists 10/24/2019, 1:06:35 AM - mebeim (Marco Bonelli): It's probably possible, though I don't have much time to investigate further at the moment. 10/24/2019, 1:07:31 AM - mebeim (Marco Bonelli): For now let's keep it open so others can read the messages up here too 10/24/2019, 1:07:51 AM - mebeim (Marco Bonelli): It's important that we all know about this possibility to avoid future errors 10/24/2019, 1:08:24 AM - sbrl (Starbeamrainbowlabs): Yeah 10/24/2019, 1:08:31 AM - sbrl (Starbeamrainbowlabs): I'm really quite busy myself with this PhD 10/24/2019, 2:08:47 AM - schneiderl (Lucas Gabriel Schneider): I've just read #3463 and the full discussion: lol 10/24/2019, 2:08:54 AM - schneiderl (Lucas Gabriel Schneider): why would people do that 10/24/2019, 2:42:22 AM - mebeim (Marco Bonelli): yeah it's pretty strange... my wild guess is that they just saw the open branch and thought about merging it into master 10/24/2019, 2:44:48 AM - mebeim (Marco Bonelli): Waaaait what the hell... the PR just disappeared out of thin air 🤨🤨🤨🤨 10/24/2019, 2:46:32 AM - mebeim (Marco Bonelli): Hmmm.... 10/24/2019, 2:47:23 AM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/LkGE/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/LkGE/image.png) 10/24/2019, 2:47:53 AM - mebeim (Marco Bonelli): PR #3463 is now missing... I am literally *clueless* 10/24/2019, 3:04:51 AM - sbrl (Starbeamrainbowlabs): Maybe GH zapped it? 10/24/2019, 3:05:38 AM - mebeim (Marco Bonelli): yeah that's the only thing I can think of 10/24/2019, 3:05:40 AM - mebeim (Marco Bonelli): 🤷‍♂️ 10/24/2019, 8:59:07 AM - agnivade (Agniva De Sarker): Any thoughts on the icon issue ? I would like to get a closure on that. The issue has been hanging around for quite some time. 10/24/2019, 1:40:23 PM - mebeim (Marco Bonelli): @agnivade we only need to fill the table I commented, then it's done. I would like to see an example with `$_`. I could even create one myself, but I'm too busy lately. My preference for the icon itself would probably be: either `$_` or `>_`, dark blue button, white text, source code pro. 10/24/2019, 3:27:39 PM - sbrl (Starbeamrainbowlabs): I thumbs-upped your comment @agnivade. I'd be fine with either yours or @mebeim's suggestion. Though my personal preference would be for `$_`, we should certainly have something rather than nothing. 10/24/2019, 5:20:55 PM - agnivade (Agniva De Sarker): @mebeim - Yeah I would like to see one with $_ too, but it seems things are not moving because we want to check other options. 10/24/2019, 5:48:57 PM - mebeim (Marco Bonelli): yeah... that's unfortunately true 😅 10/24/2019, 8:10:54 PM - agnivade (Agniva De Sarker): Let me see what others think 10/27/2019, 10:32:33 PM - mebeim (Marco Bonelli): I don't really understand why this keeps happening... https://github.com/tldr-pages/tldr/pull/3483#discussion_r339352867 10/27/2019, 10:34:04 PM - mebeim (Marco Bonelli): Oh, I see, that's because @sbrl just merged the other french PR. My bad, didn't notice. 10/27/2019, 10:34:31 PM - sbrl (Starbeamrainbowlabs): Oh, oops! I didn't realise that the other French PR added the `git` page 10/27/2019, 10:34:43 PM - sbrl (Starbeamrainbowlabs): I saw the stale bot notification and merged it 10/27/2019, 10:37:21 PM - mebeim (Marco Bonelli): No problem, I was just reviewing the other PR and noticed it. I suggested to remove it from the PR as we already have it translated. 10/27/2019, 10:57:19 PM - sbrl (Starbeamrainbowlabs): Good idea 10/28/2019, 1:46:05 PM - agnivade (Agniva De Sarker): Has anybody here lost access to github and had to mail support ? I did some stupidity where I installed 2fa app on my new phone, but the codes weren't working. I was testing that on my phone browser. But I had this great idea to logout my desktop session and test it. 😓 And now I can't login 10/28/2019, 1:46:15 PM - agnivade (Agniva De Sarker): My recovery codes don't seem to work too 10/28/2019, 2:53:10 PM - owenvoke (Owen Voke): Don't think so. 🤔 Hope you manage to sort it out. 10/28/2019, 2:54:41 PM - owenvoke (Owen Voke): GitHub have been pretty slow to respond when I've emailed them recently though due to high demand on support. 10/28/2019, 2:58:42 PM - mebeim (Marco Bonelli): Oh damn, that's no good... D: 10/28/2019, 3:02:07 PM - agnivade (Agniva De Sarker): oh boy .. 10/28/2019, 3:02:44 PM - agnivade (Agniva De Sarker): yeah .. I screwed up big time. 10/28/2019, 3:03:48 PM - mebeim (Marco Bonelli): when you say the recovery key are you talking about the 10/28/2019, 3:04:30 PM - mebeim (Marco Bonelli): recovery codes for 2fa which are like a bunch of hex strings? 10/28/2019, 3:04:36 PM - agnivade (Agniva De Sarker): correct 10/28/2019, 3:05:13 PM - mebeim (Marco Bonelli): ok.. the fact that that doesn't work is alarming to say the least 10/28/2019, 3:06:04 PM - mebeim (Marco Bonelli): maybe your 2fa codes got out of sync? do you have the seed? 10/28/2019, 3:06:56 PM - agnivade (Agniva De Sarker): yeah .. I am guessing it all happened when I installed the 2fa app on my new phone and re-added github to it. 10/28/2019, 3:07:26 PM - agnivade (Agniva De Sarker): Seed ? 10/28/2019, 3:07:47 PM - mebeim (Marco Bonelli): 2fa codes are generated based on a seed 10/28/2019, 3:07:47 PM - agnivade (Agniva De Sarker): where do I get that ? 10/28/2019, 3:08:09 PM - mebeim (Marco Bonelli): when you scan the QR to add the code in the all that's basically the seed plus some more info 10/28/2019, 3:08:21 PM - mebeim (Marco Bonelli): some apps let you export the seed 10/28/2019, 3:08:41 PM - mebeim (Marco Bonelli): (Google authenticator doesn't, if you're using that..) 10/28/2019, 3:08:47 PM - agnivade (Agniva De Sarker): oh .. no I don't. I use google authenticator. It doesn't seem to have anything like that 10/28/2019, 3:09:16 PM - mebeim (Marco Bonelli): ah unlucky 10/28/2019, 5:21:13 PM - sbrl (Starbeamrainbowlabs): I had to use a backup code once. It did appear to work. 10/28/2019, 5:21:21 PM - sbrl (Starbeamrainbowlabs): Yeah, it's a shared secret @mebeim 10/28/2019, 5:21:41 PM - sbrl (Starbeamrainbowlabs): Do you have any devices that you're already logged into GH with? 10/28/2019, 6:33:57 PM - owenvoke (Owen Voke): Also, if you've connected Facebook (ew) then you can use that to re-gain access I think. 10/28/2019, 6:40:44 PM - sbrl (Starbeamrainbowlabs): Yeah, that's a thing IIRC. Note that under normal circumstances they can't give you back control of your GH account when you have 2FA enabled. Since it's never worked for you though, I think they might be able to make an exception 10/28/2019, 6:41:09 PM - sbrl (Starbeamrainbowlabs): (On a related note, I can recommend the Solo open-source hardware security key) 10/28/2019, 6:46:35 PM - mebeim (Marco Bonelli): The problem persists though: lose the key -> lose everything. The only way to not lose acces is to always save your 2FA seed and physically store it somewhere safe. 10/28/2019, 6:48:00 PM - sbrl (Starbeamrainbowlabs): Indeed. 10/28/2019, 6:48:09 PM - sbrl (Starbeamrainbowlabs): Also, you can register multiple 2fa devices 10/28/2019, 6:48:20 PM - sbrl (Starbeamrainbowlabs): then if you loose one, you still have the other 10/28/2019, 6:48:28 PM - sbrl (Starbeamrainbowlabs): I suppose the same goes for SSH key-based auth too 10/28/2019, 7:27:54 PM - schneiderl (Lucas Gabriel Schneider): @mebeim dude how many languages do you speak? haha 10/28/2019, 7:28:36 PM - schneiderl (Lucas Gabriel Schneider): I think I've seen you reviewing Portuguese/French/Italian/English 10/28/2019, 7:28:41 PM - schneiderl (Lucas Gabriel Schneider): It's pretty impressive :) 10/28/2019, 8:39:07 PM - agnivade (Agniva De Sarker): It did work for me before. But not after I reinstalled it on my new phone. 10/28/2019, 8:39:26 PM - agnivade (Agniva De Sarker): Can't they just disable 2FA and let me login. I have had that done for other sites before 10/28/2019, 8:40:16 PM - agnivade (Agniva De Sarker): No I don't have any devices that I am logged into. My desktop was the last one. 10/28/2019, 9:05:02 PM - agnivade (Agniva De Sarker): Ok, it seems all hope is not lost: https://medium.com/@kaumac/how-to-recover-your-github-account-if-you-lost-your-2fa-credentials-and-recovery-codes-d171b2bb87f0 10/28/2019, 9:05:06 PM - agnivade (Agniva De Sarker): I have that 10/28/2019, 9:05:21 PM - agnivade (Agniva De Sarker): Now only if GH support agrees to disable the 2FA, all should be good 10/28/2019, 9:59:08 PM - owenvoke (Owen Voke): :+1: 10/28/2019, 11:00:33 PM - mebeim (Marco Bonelli): @schneiderl I only speak English and Italian, but French is pretty easy to understand knowing Italian. I also pass every page through a grammar checker and check the errors myself, most of the times there are typos or singular/plural errors or wrong verb conjugations. Verbs work the same in Italian so that's also easy to fix by googling the conjugation. For the Brazilian Portuguese pages I never did very in-depth reviews though. 10/28/2019, 11:01:34 PM - mebeim (Marco Bonelli): thanks btw 😎 10/28/2019, 11:37:51 PM - sbrl (Starbeamrainbowlabs): nice 😃 10/29/2019, 4:39:37 AM - mebeim (Marco Bonelli): @agnivade take a look at #3297 if you can, I would like to merge since it's been open for quite a while. 10/29/2019, 4:41:01 AM - mebeim (Marco Bonelli): just give us an ACK here 10/29/2019, 8:59:26 AM - agnivade (Agniva De Sarker): LGTM 10/29/2019, 12:12:47 PM - mebeim (Marco Bonelli): @agnivade thx 10/29/2019, 5:56:40 PM - mebeim (Marco Bonelli): Has @einverne already been added as collaborator? 10/29/2019, 6:26:45 PM - owenvoke (Owen Voke): I think so, they'll just need to accept it afaik. 10/29/2019, 6:27:10 PM - mebeim (Marco Bonelli): Ok 10/29/2019, 6:28:11 PM - owenvoke (Owen Voke): Although, @sbrl asked in the issue if we could add @einverne as a collab. So maybe not...? 🤔 10/29/2019, 6:28:34 PM - mebeim (Marco Bonelli): They accepted, that's why I was asking 10/29/2019, 7:06:41 PM - sbrl (Starbeamrainbowlabs): No, I haven't yet sent the invite - unless someone else did 10/29/2019, 7:06:49 PM - sbrl (Starbeamrainbowlabs): just about to check through my GH notifications again now 10/29/2019, 7:07:39 PM - mebeim (Marco Bonelli): Ok, then I think you can merge #3496 after inviting :) 10/29/2019, 7:10:37 PM - sbrl (Starbeamrainbowlabs): Huh, looks like nobody else has sent the collaborator invite either. I've just sent that now 10/29/2019, 8:32:03 PM - agnivade (Agniva De Sarker): phew .. I am back ! 😃 10/29/2019, 8:32:08 PM - schneiderl (Lucas Gabriel Schneider): I was wondering since now we have way more contributors then we had like half a year ago maybe we can think of increasing the minimum number of accepted reviews from 2 to 3. 3 approvals will not be very hard (nor will it take too much time) to get as we have at least 7 active contributors doing maintenance work. By doing that I believe we can increase even more or review process quality. What do you guys think? 10/29/2019, 8:37:01 PM - mebeim (Marco Bonelli): oh thank god @agnivade how did you manage to get the account back? 10/29/2019, 8:38:47 PM - mebeim (Marco Bonelli): @schneiderl I was thinking about that but I don't know how useful that would be.. even now it's not that fast to merge something 10/29/2019, 8:39:43 PM - agnivade (Agniva De Sarker): I had the ssh verification token. So support verified that and just disabled my 2FA. Although there was one round of to-and-fro where they asked me to check my backups if I have missed the verifications tokens somehow. 10/29/2019, 8:40:43 PM - mebeim (Marco Bonelli): oh, well good to know 10/29/2019, 8:53:45 PM - schneiderl (Lucas Gabriel Schneider): @mebeim I agree with you that it is not that fast to merge something during unusual traffic periods (like hacktoberfest), but when we get back to the usual, which I believe don't go over 20 PR's/week, I think we can handle it well 10/29/2019, 8:55:48 PM - schneiderl (Lucas Gabriel Schneider): and I think that gives us maintainers more time to express our opinions about new PRs instead of sometimes just seeing them after they're already merged 10/29/2019, 9:09:32 PM - mebeim (Marco Bonelli): that would for sure increase merging time and the amount of "ping @ @" comments though 😅 I don't know, I'm conflicted, you should probably open an Issue so we can hear what others have to say 10/29/2019, 9:19:55 PM - agnivade (Agniva De Sarker): I think 2 is fine. If the PR is merged before someone gets a chance to make a review, it's okay to review on a merged PR. That's what I have been doing. Imagine you are on a vacation and then come back and want to review PRs. I believe the same approach works here. 10/29/2019, 9:20:53 PM - schneiderl (Lucas Gabriel Schneider): yeah @mebeim you're right on that too haha 10/29/2019, 9:26:14 PM - waldyrious (Waldir Pimenta): I agree with @agnivade (welcome back btw! Happy to hear it sorted out). I often review PRs that have been merged and submit any changes I'd have suggested as new PRs. It's not like anything in our repo is set in stone anyway :) 10/30/2019, 2:09:37 AM - sbrl (Starbeamrainbowlabs): marked all the translation PRs as read again. Message me on here if I'm needed. 10/30/2019, 6:21:17 AM - mebeim (Marco Bonelli): Hey is any of you guys attending 36C3? 10/30/2019, 2:46:54 PM - owenvoke (Owen Voke): No idea what it is 😋 10/30/2019, 2:52:02 PM - mebeim (Marco Bonelli): very cool tech/security conference https://events.ccc.de/congress/2019/wiki/index.php/Main_Page 10/30/2019, 3:20:28 PM - sbrl (Starbeamrainbowlabs): Sadly not @mebeim 10/30/2019, 3:20:50 PM - sbrl (Starbeamrainbowlabs): But there is a chance that I will be attending an international conference of some description in ~2.5 years time 10/30/2019, 3:20:57 PM - sbrl (Starbeamrainbowlabs): as part of my PhD 10/30/2019, 4:11:42 PM - owenvoke (Owen Voke): I should really go to some conferences _sigh_ 10/30/2019, 4:12:06 PM - owenvoke (Owen Voke): Looks interesting @mebeim :+1: 10/30/2019, 4:22:50 PM - mebeim (Marco Bonelli): It is, last time I didn't go and I still regret that hahah, this year I already got the ticket 10/30/2019, 6:48:05 PM - sbrl (Starbeamrainbowlabs): Nice! Do enjoy @mebeim 10/30/2019, 8:55:31 PM - mebeim (Marco Bonelli): Will do 😎 thanks 1/14/2023, 3:33:51 PM - einverne (Ein Verne) joined the room 10/31/2019, 6:54:17 AM - einverne (Ein Verne): Oh, one question here guys, when I tried to squash and merge what commit body should I put? 10/31/2019, 6:55:33 AM - mebeim (Marco Bonelli): We usually remove everything from there. There are exceptional cases in which it is useless to have something there like explanation of complicated/multiple changes or stuff like that, but it's rare. 10/31/2019, 6:56:10 AM - einverne (Ein Verne): OK I see. 10/31/2019, 6:56:28 AM - mebeim (Marco Bonelli): If you take a look at the commit history you can see that 99.9% of the squash merges have empty commit bodies (only one short commit msg) 10/31/2019, 6:57:34 AM - mebeim (Marco Bonelli): This is an example of a meaningful commit body which was kept because the author of the PR took time to document the changes and it's nice to keep: https://github.com/tldr-pages/tldr/commit/7904a322f2004e1203bb834b95b4001b4b9d86b3 10/31/2019, 6:58:28 AM - einverne (Ein Verne): Got it. 10/31/2019, 6:59:00 AM - einverne (Ein Verne): [![screenshot-area-2019-10-31-092729.png](https://files.gitter.im/tldr-pages/tldr/Agm1/thumb/screenshot-area-2019-10-31-092729.png)](https://files.gitter.im/tldr-pages/tldr/Agm1/screenshot-area-2019-10-31-092729.png) 10/31/2019, 6:59:27 AM - mebeim (Marco Bonelli): Ah yes, that one I merged just today :) 10/31/2019, 6:59:43 AM - einverne (Ein Verne): OK thanks. 10/31/2019, 7:00:04 AM - mebeim (Marco Bonelli): You're welcome :slight_smile: 10/31/2019, 7:35:03 AM - mebeim (Marco Bonelli): By the way, @einverne this https://github.com/tldr-pages/tldr/commit/974cafbef5f0d3377a7a082251b135dc942ca543 is exactly the kind of commit body we try to avoid. In such cases just wipe it out when squashing. 10/31/2019, 7:36:08 AM - einverne (Ein Verne): Oh, sorry, I remember I clear all commit body on the webpage. 10/31/2019, 7:40:26 AM - mebeim (Marco Bonelli): no prob, happens to everyone, just making making sure my explanation was clear 😅 10/31/2019, 7:42:21 AM - einverne (Ein Verne): Can we fix it? 10/31/2019, 7:44:18 AM - mebeim (Marco Bonelli): Nope, what gets to master is definitive (unless it's something extreme then one of the org owners can force-push to master). Don't worry about it. 10/31/2019, 7:45:30 AM - einverne (Ein Verne): OK, next time I will be more careful... 10/31/2019, 7:46:58 AM - mebeim (Marco Bonelli): Takes a couple of PRs to get used to haha 😛 10/31/2019, 8:33:32 PM - waldyrious (Waldir Pimenta): @mebeim small correction — where you wrote 10/31/2019, 8:33:40 PM - waldyrious (Waldir Pimenta): > There are exceptional cases in which it is useless to have something there like explanation of complicated/multiple changes or stuff like that, but it's rare. 10/31/2019, 8:34:11 PM - waldyrious (Waldir Pimenta): You should have written "...in which it is useful..." 😉 10/31/2019, 8:36:04 PM - mebeim (Marco Bonelli): Whooops, you're right, typo 😛 11/5/2019, 12:39:43 AM - agnivade (Agniva De Sarker): Welcome @einverne ! 11/5/2019, 12:40:01 AM - agnivade (Agniva De Sarker): Glad to have you as a member ! 11/5/2019, 7:11:04 AM - einverne (Ein Verne): Thank you @agnivade ~~ 1/14/2023, 3:34:08 PM - MarkoShiva (Marko Shiva Pavlovic) joined the room 11/5/2019, 6:25:02 PM - MarkoShiva (Marko Shiva Pavlovic): I just wanted to say that its interesting name of the project and actually nice play on the RTFM thing. :) 11/5/2019, 6:25:39 PM - MarkoShiva (Marko Shiva Pavlovic): Definitelly new way to read man pages even for linux oldtimers like me. :) 11/5/2019, 6:53:09 PM - sbrl (Starbeamrainbowlabs): Thanks, @in1t3r! We strive for tldr-pages to be useful for a broad a user base as possible :-) 1/14/2023, 3:34:10 PM - guoruibiao (guoruibiao) joined the room 11/6/2019, 3:05:59 PM - guoruibiao (guoruibiao): wow, i would be very happy if i known this repo one year ago. awesome tool. 11/6/2019, 4:47:53 PM - sbrl (Starbeamrainbowlabs): 😃 11/8/2019, 5:20:17 AM - sbrl (Starbeamrainbowlabs): Ooops. Looks like we've got a bit confused in #3517 11/8/2019, 5:20:34 AM - sbrl (Starbeamrainbowlabs): I've just noticed that there's already a page for `stern` in `common` 11/8/2019, 5:20:51 AM - sbrl (Starbeamrainbowlabs): ....perhaps tldr-bot could notify of this lol 11/8/2019, 5:20:59 AM - sbrl (Starbeamrainbowlabs): it's happened quite a bit recently 11/8/2019, 5:22:25 AM - mebeim (Marco Bonelli): god dammit this is starting to become really annoying... wtf 11/8/2019, 5:22:40 AM - mebeim (Marco Bonelli): what did GH even do when merging 11/8/2019, 5:23:29 AM - sbrl (Starbeamrainbowlabs): In this instance the existing page was in common 11/8/2019, 5:23:36 AM - sbrl (Starbeamrainbowlabs): ...and the PR was made against osx 11/8/2019, 5:23:48 AM - sbrl (Starbeamrainbowlabs): It's quickly becoming a real issue 11/8/2019, 5:24:20 AM - sbrl (Starbeamrainbowlabs): like I wouldn't have known if @agnivade hadn't commented and I hadn't been lazy enough to use the `t` file finder trick to edit & open a 2nd PR 11/8/2019, 5:24:22 AM - mebeim (Marco Bonelli): Ah damn I see... for a second I thought that was still the duplicate page issue, nevermind! 11/8/2019, 5:24:27 AM - sbrl (Starbeamrainbowlabs): close 11/8/2019, 5:24:39 AM - sbrl (Starbeamrainbowlabs): close enough to warrant an upgrade to tldr-bot I think 11/8/2019, 5:25:01 AM - sbrl (Starbeamrainbowlabs): It's code is here: https://github.com/tldr-pages/tldr-bot 11/8/2019, 5:25:05 AM - sbrl (Starbeamrainbowlabs): and hosted on my server 11/8/2019, 5:25:42 AM - mebeim (Marco Bonelli): TLDR bot should really be upgraded to use GH APIs and become a real bot though... wish I had time to do it 11/8/2019, 5:25:57 AM - sbrl (Starbeamrainbowlabs): Yeah, me too. 11/8/2019, 5:28:30 AM - mebeim (Marco Bonelli): so in this case the stern page did not need a special osx version? 11/8/2019, 5:29:10 AM - sbrl (Starbeamrainbowlabs): Yep 11/8/2019, 5:29:20 AM - sbrl (Starbeamrainbowlabs): ...but we reviewed and merged it anyway lol 11/8/2019, 5:29:43 AM - sbrl (Starbeamrainbowlabs): ....with 4 approvals too 11/8/2019, 5:31:35 AM - mebeim (Marco Bonelli): meh.. that is one thing that should always be looked into, when reviewing a page checking if it makes sense to stay in a certain folder should be the first thing to do 11/8/2019, 5:32:00 AM - mebeim (Marco Bonelli): adding a check in Travis would prevent just some of this kind of problems, not all of them :\ 11/8/2019, 5:33:22 AM - sbrl (Starbeamrainbowlabs): True, but at least having tldr-bot notify to say "there's already an NNNN page in tldr-pages under the `MMMMM` platform. Are you sure this isn't a duplicate" would be helpful 11/8/2019, 5:33:24 AM - mebeim (Marco Bonelli): by the way, it's not tldr-bot that should be upgraded 11/8/2019, 5:33:34 AM - mebeim (Marco Bonelli): it's just the build script 11/8/2019, 5:34:35 AM - mebeim (Marco Bonelli): it should also be kinda trivial to do, I could take a look at it next week 11/8/2019, 5:38:32 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I did take a look at tldr-bot and got confused 11/8/2019, 5:38:46 AM - sbrl (Starbeamrainbowlabs): Cool, thanks @mebeim :-) 11/8/2019, 5:38:53 AM - sbrl (Starbeamrainbowlabs): Shall I revert that PR for now? 11/8/2019, 5:39:09 AM - sbrl (Starbeamrainbowlabs): Or leave it with the /cc on it 11/8/2019, 5:40:59 AM - mebeim (Marco Bonelli): yeah just @ ping me here if I forget 😅 11/8/2019, 5:42:31 AM - mebeim (Marco Bonelli): Hmmm I think reverting the PR could be ok. What does that do? Just create another commit over the top of master? 11/8/2019, 5:42:47 AM - mebeim (Marco Bonelli): The important thing is that it does not force push. 11/8/2019, 5:43:59 AM - mebeim (Marco Bonelli): We should wait for others to reply first though. 11/8/2019, 4:28:51 PM - sbrl (Starbeamrainbowlabs): Yeah, revert creates a new commit that's the inverse of the previous commit(s) 11/8/2019, 4:28:54 PM - sbrl (Starbeamrainbowlabs): Yeah 11/8/2019, 8:11:30 PM - waldyrious (Waldir Pimenta): [![Screenshot 2019-11-08 at 14.39.33.png](https://files.gitter.im/tldr-pages/tldr/w5Js/thumb/Screenshot-2019-11-08-at-14.39.33.png)](https://files.gitter.im/tldr-pages/tldr/w5Js/Screenshot-2019-11-08-at-14.39.33.png) 11/8/2019, 8:11:47 PM - waldyrious (Waldir Pimenta): 😱 11/8/2019, 8:15:50 PM - agnivade (Agniva De Sarker): Yeah just do a git revert of that commit hash and send another PR. 11/8/2019, 8:17:07 PM - agnivade (Agniva De Sarker): @waldyrious - If I don't open GH for a week, I would probably reach that number too 😛 It's a constant battle. 11/8/2019, 8:17:24 PM - waldyrious (Waldir Pimenta): Yeah 😅 11/8/2019, 8:37:31 PM - agnivade (Agniva De Sarker): I have started to work on the duplicate commands issue here - https://github.com/tldr-pages/tldr/pull/3535 11/8/2019, 9:32:35 PM - sbrl (Starbeamrainbowlabs): Awesome @agnivade! So I'll revert #3517 11/8/2019, 9:36:38 PM - sbrl (Starbeamrainbowlabs): Commit reverted. 11/9/2019, 2:41:43 PM - agnivade (Agniva De Sarker): Hmm .. I just realized that it's not that simple to avoid false positives. For eg. someone might add a more specific example of a page in common, or someone might move a page from a platform dir to common. It might be better not to fail the build, but just comment on the PR saying that "we have detected another page with the same name in a different platform. Please check if this is expected". 11/9/2019, 2:42:04 PM - agnivade (Agniva De Sarker): That means we need to move this check from the build script to a webhook that tldr-bot can listen to 11/9/2019, 2:42:39 PM - agnivade (Agniva De Sarker): I don't have much time this weekend, @mebeim you wanted to work on it. Still interested ? 11/9/2019, 2:49:18 PM - mebeim (Marco Bonelli): Yeah but next week probably 11/9/2019, 2:58:04 PM - agnivade (Agniva De Sarker): sure 11/9/2019, 2:58:07 PM - agnivade (Agniva De Sarker): :+1: 11/9/2019, 3:01:01 PM - mebeim (Marco Bonelli): Failing the build was not what I meant. I just meant to check the `git diff master HEAD` for any "added file" and check if they already exist in common, if so comment saying something like "are you sure? if yes just ignore this comment". 11/9/2019, 5:01:20 PM - sbrl (Starbeamrainbowlabs): Hrm. I don't think we have to fail the whole build 11/9/2019, 5:01:31 PM - sbrl (Starbeamrainbowlabs): What about an "are you sure?" message? 11/9/2019, 5:01:42 PM - sbrl (Starbeamrainbowlabs): Like an informational comment 11/10/2019, 9:31:15 AM - agnivade (Agniva De Sarker): Yeah, let's do that. I just meant we have to use tldr-bot to comment on the PR. 11/10/2019, 9:31:44 AM - agnivade (Agniva De Sarker): Also note that the new added file might be added to common when a platform command already exists, that is also incorrect. So you would need to check that also. 11/10/2019, 6:06:16 PM - sbrl (Starbeamrainbowlabs): Yeah. I think a generic `A page for {{command}} already exists in platforms {{list_of_platforms}}. Are you sure that you want to add this page?` 11/10/2019, 6:06:22 PM - sbrl (Starbeamrainbowlabs): would work 11/10/2019, 6:10:14 PM - mebeim (Marco Bonelli): yeah something along the lines of that sounds good :) 11/13/2019, 6:56:24 AM - mebeim (Marco Bonelli): Guys @sbrl @waldyrious @agnivade @pxgamer I was thinking about the whole translation thing. I'm bootstrapping the process at https://github.com/mebeim/tldr/tree/po4a/l10n if you want to take a look or you want to help. In the mean time, what do you think about preparing a few lines to send over to Weblate to ask for free hosting? 11/13/2019, 6:59:14 AM - mebeim (Marco Bonelli): You can see the contact form at https://hosted.weblate.org/hosting/ (needs login, I simply logged in through GitHub) -- I see they require a path for the `.po` files to use, so I should first start generating them, but in the meantime we can agree on a message to add in the "Additional message" section. When we are ready I could submit a request and see what they answer. 11/13/2019, 9:59:27 AM - agnivade (Agniva De Sarker): Thanks for taking the initiative @mebeim ! @waldyrious can help with composing something. 11/13/2019, 4:15:28 PM - waldyrious (Waldir Pimenta): Nice! I should have some extra time for the rest of the week. Very happy to help however I can! 11/14/2019, 2:20:21 AM - mebeim (Marco Bonelli): Take a look at this helpful script I just made guys https://github.com/mebeim/tldr/blob/po4a/l10n/scripts/bootstrap-translation.sh 11/14/2019, 2:22:08 AM - mebeim (Marco Bonelli): It's an interactive script that will be useful to port existing translations to `.po` files. The process should be more or less effortless, but of course manual intervention will be needed (best if by someone who knows the language, of course). 11/14/2019, 2:48:51 AM - sbrl (Starbeamrainbowlabs): Nice one, @mebeim! 11/14/2019, 2:49:45 AM - sbrl (Starbeamrainbowlabs): I assume that eventually the aim will be to adjust it such that we have no errors and it can run automatically? 11/14/2019, 2:54:57 AM - mebeim (Marco Bonelli): @sbrl nope, it will only be needed at first to port existing translations to `.po` files. Once we have the `.po` files, it's all done through them, invoking `po4a` will read the `.po` files and generate all the translated pages. 11/14/2019, 2:55:55 AM - mebeim (Marco Bonelli): The fact that it runs with errors cannot be "adjusted", it's just the nature of the used tools... but still, again, it's only a one-time operation. 11/14/2019, 2:59:52 AM - sbrl (Starbeamrainbowlabs): Ah, I see now. Thanks for the clarification :-) 11/15/2019, 12:50:11 AM - mebeim (Marco Bonelli): I have the PR check script ready.. but I was wondering, how could it be possible to only check a PR once in Travis? If I output something like "hey this page already exists in common, are you sure?" then it will get commented *every single time* the user pushes commits to the PR, not just when it's opened 11/15/2019, 12:57:14 AM - sbrl (Starbeamrainbowlabs): You could potentially check using the GH API to see if tldr bot has commented already on the PR 11/15/2019, 12:59:06 AM - mebeim (Marco Bonelli): That... would be very annoying to do 11/15/2019, 1:05:13 AM - mebeim (Marco Bonelli): Dammit. Looks like a bot rework is needed... 11/15/2019, 1:05:20 AM - mebeim (Marco Bonelli): will have to work on that first 11/15/2019, 1:05:43 AM - sbrl (Starbeamrainbowlabs): One sec 11/15/2019, 1:05:49 AM - sbrl (Starbeamrainbowlabs): I'm writing a bash one-liner 11/15/2019, 1:08:12 AM - mebeim (Marco Bonelli): for what? 11/15/2019, 1:08:41 AM - mebeim (Marco Bonelli): Seriously no need to bother the bot needs a big update anyway 😅 11/15/2019, 1:09:51 AM - sbrl (Starbeamrainbowlabs): ``` curl https://api.github.com/repos/tldr-pages/tldr/issues/2795/comments | jq --raw-output '[ .[] | select(.user.login == "tldr-bot") | .user.login ] | length > 0' ``` 11/15/2019, 1:10:25 AM - sbrl (Starbeamrainbowlabs): Outputs `true` if tldr-bot has commented on a given PR or issue, and `false` otherwise. 11/15/2019, 1:10:44 AM - sbrl (Starbeamrainbowlabs): @mebeim 11/15/2019, 1:11:32 AM - mebeim (Marco Bonelli): Well... thanks for that but I would personally prefer upgrading the bot 11/15/2019, 1:17:03 AM - sbrl (Starbeamrainbowlabs): True 😛 11/15/2019, 1:17:08 AM - sbrl (Starbeamrainbowlabs): The above requires `jq` 11/15/2019, 1:17:27 AM - sbrl (Starbeamrainbowlabs): and is best read in a text editor that supports line wrapping 😛 11/15/2019, 1:17:49 AM - mebeim (Marco Bonelli): i'm working on a PR for tldr-bot 11/15/2019, 1:17:56 AM - mebeim (Marco Bonelli): also upgrading to python 3 11/15/2019, 1:18:18 AM - mebeim (Marco Bonelli): (should be painless, basically just changing `print x` to `print(x)`) 11/15/2019, 1:33:16 AM - sbrl (Starbeamrainbowlabs): cool 😃 11/15/2019, 1:33:33 AM - sbrl (Starbeamrainbowlabs): Also, isn't tldr bot running under python3 already? 11/15/2019, 1:33:50 AM - mebeim (Marco Bonelli): i see print statements with the python 2 syntax, so nope 11/15/2019, 1:33:55 AM - sbrl (Starbeamrainbowlabs): Ah, I see 11/15/2019, 1:34:26 AM - sbrl (Starbeamrainbowlabs): An upgrade there would be good, because I'm not sure how much longer my server will have python 2 installed 11/15/2019, 1:34:35 AM - sbrl (Starbeamrainbowlabs): My server being the place tldr-bot is hosted 11/15/2019, 1:35:05 AM - mebeim (Marco Bonelli): yep 11/15/2019, 2:00:50 AM - owenvoke (Owen Voke): Python 2 EOL is early next year right? 11/15/2019, 2:05:30 AM - mebeim (Marco Bonelli): ye 11/15/2019, 2:28:00 AM - sbrl (Starbeamrainbowlabs): yeah 11/15/2019, 4:21:30 AM - mebeim (Marco Bonelli): I've opened https://github.com/tldr-pages/tldr-bot/pull/6 guys, take a look when you have time. After that's merged I'll complete the PR-checking script for the main repo and open a new PR there. 11/15/2019, 4:22:02 AM - owenvoke (Owen Voke): Just off to sleep, but will take a look in the morning if it hasn't already been merged. :+1: 11/15/2019, 4:22:25 AM - mebeim (Marco Bonelli): Sure, good night :) 11/15/2019, 4:36:23 AM - sbrl (Starbeamrainbowlabs): The tldr-bot is now running @mebeim's `update` branch 11/15/2019, 5:24:08 AM - sbrl (Starbeamrainbowlabs): Added the tldr-bot to https://status.starbeamrainbowlabs.com/ 11/15/2019, 5:24:31 AM - mebeim (Marco Bonelli): Nice 11/15/2019, 5:24:35 AM - sbrl (Starbeamrainbowlabs): So if you think the tldr-bot is having a hiccup, you can now check to see if the bot running on my server is the problem 11/15/2019, 8:13:45 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/97fL/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/97fL/image.png) 11/15/2019, 8:14:16 PM - mebeim (Marco Bonelli): I'm having a really hard time trying to understand what the heck is going on with this `npm test` that doesn't want to fail. 11/15/2019, 8:20:15 PM - sbrl (Starbeamrainbowlabs): What exit code does the test script emit @mebeim 11/15/2019, 8:21:19 PM - mebeim (Marco Bonelli): `wtf.js` emits 1 11/15/2019, 8:21:31 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/wb9w/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/wb9w/image.png) 11/15/2019, 8:21:40 PM - mebeim (Marco Bonelli): here I also used `set -ex` just to make it clearer 11/15/2019, 8:24:27 PM - sbrl (Starbeamrainbowlabs): Strange 11/15/2019, 8:24:38 PM - sbrl (Starbeamrainbowlabs): what exit code does `npm test` generate 11/15/2019, 8:24:54 PM - mebeim (Marco Bonelli): `0` 11/15/2019, 8:25:27 PM - mebeim (Marco Bonelli): 😭😭😭 11/15/2019, 8:29:53 PM - mebeim (Marco Bonelli): You can `git clone git@github.com:mebeim/tldr --branch wtf --single-branch --depth 1 mebeim_tldr` if you want to test it. 11/15/2019, 8:31:02 PM - mebeim (Marco Bonelli): OK, I just re-cloned with the above command and... it... works.......... LOL 11/15/2019, 8:31:31 PM - sbrl (Starbeamrainbowlabs): Maybe a stray file or something? 11/15/2019, 8:31:41 PM - mebeim (Marco Bonelli): Could be some strange `git` interaction 11/15/2019, 8:31:44 PM - mebeim (Marco Bonelli): I'm puzzled 11/15/2019, 8:35:31 PM - mebeim (Marco Bonelli): Point is, that `npm test` seems to be failing to recognize errors on the main repo too (i.e. on Travis). 11/15/2019, 8:35:52 PM - mebeim (Marco Bonelli): Build should have failed badly for the PR containing all the Korean pages without trailing newlines. 11/15/2019, 8:36:20 PM - mebeim (Marco Bonelli): Instead, some absurd black magic happened on Travis-CI too.... 11/15/2019, 8:44:23 PM - sbrl (Starbeamrainbowlabs): Hrmmmmmmm 11/15/2019, 8:44:31 PM - sbrl (Starbeamrainbowlabs): /cc @agnivade 11/15/2019, 8:53:06 PM - mebeim (Marco Bonelli): I just looked at the process with `strace`, the program runs fine, executes markdownlint which reads both the config and the `.md` file correctly. 11/15/2019, 8:53:22 PM - mebeim (Marco Bonelli): It's definitely a bug in markdownlint-cli 11/15/2019, 8:53:32 PM - sbrl (Starbeamrainbowlabs): It's possible that it's a unicode bug 11/15/2019, 8:53:33 PM - mebeim (Marco Bonelli): Cannot really narrow it down more than that though 11/15/2019, 8:53:42 PM - mebeim (Marco Bonelli): Very possible, yes 11/15/2019, 8:53:50 PM - sbrl (Starbeamrainbowlabs): In that case we should open an issue against markdownlint-cli 11/15/2019, 8:54:00 PM - mebeim (Marco Bonelli): Oh, I just realized why this is happening maybe 11/15/2019, 8:54:06 PM - sbrl (Starbeamrainbowlabs): The developers of that project should be able to help 11/15/2019, 8:54:07 PM - sbrl (Starbeamrainbowlabs): Oh? 11/15/2019, 8:54:36 PM - mebeim (Marco Bonelli): I have a `node_modules` folder with a different version of markdownlint-cli I think 11/15/2019, 8:55:00 PM - mebeim (Marco Bonelli): It could be that on the repo that I just re-clonet the absence of a `node_modules` folder makes node use the system wide markdownlint-cli 11/15/2019, 8:55:18 PM - mebeim (Marco Bonelli): Let me check 11/15/2019, 8:55:23 PM - sbrl (Starbeamrainbowlabs): Ah 11/15/2019, 8:55:34 PM - sbrl (Starbeamrainbowlabs): Try deleting it and doing an `npm install` again 11/15/2019, 8:56:36 PM - mebeim (Marco Bonelli): Indeed... that's exactly the case. Let's see which one is broken. 11/15/2019, 8:57:47 PM - mebeim (Marco Bonelli): Ok.. latest version seems the one that is broken 11/15/2019, 8:58:25 PM - mebeim (Marco Bonelli): `npm install` installs the latest? 11/15/2019, 8:59:10 PM - mebeim (Marco Bonelli): Or the one in package.json? 11/15/2019, 9:04:07 PM - mebeim (Marco Bonelli): Oh wait, thank God! `0.15` is the one that is broken. Latest (`0.19`) seems to work. 11/15/2019, 9:05:33 PM - mebeim (Marco Bonelli): Will update that too in the next PR I open (probably later today) 11/15/2019, 9:08:31 PM - sbrl (Starbeamrainbowlabs): Cool - sounds great! Glad you've managed to fix it 😃 11/15/2019, 9:10:13 PM - mebeim (Marco Bonelli): I was seriously worrying a bit too much LOL, thinking about who-knows-what when it's just a old version of the npm package, silly me. 11/15/2019, 9:23:12 PM - sbrl (Starbeamrainbowlabs): Lol, check the simple things first 😛 11/15/2019, 9:25:16 PM - mebeim (Marco Bonelli): By the way, I can't open the new PR until https://github.com/tldr-pages/tldr/pull/3573 is merged since those pages would automagically make my PR build fail (since it fixes the error) 11/15/2019, 9:25:54 PM - mebeim (Marco Bonelli): (as can be seen here https://travis-ci.org/mebeim/tldr/builds/612449994) 11/15/2019, 9:29:17 PM - sbrl (Starbeamrainbowlabs): Merged! 11/15/2019, 9:29:33 PM - sbrl (Starbeamrainbowlabs): I haven't gotten around to PR reviewing yet today, but I've done that one for you 11/15/2019, 9:36:21 PM - mebeim (Marco Bonelli): Thank you very much! :) 11/15/2019, 9:44:31 PM - sbrl (Starbeamrainbowlabs): np :-) 11/15/2019, 9:44:49 PM - sbrl (Starbeamrainbowlabs): Happy to do a fast-review on select PRs if you need them merging quickly 11/15/2019, 10:17:51 PM - mebeim (Marco Bonelli): Oh wow really, now some of the ko pages have a double ending `\n` and the linter complains for that too. Damn 😂 😂 11/15/2019, 10:23:23 PM - sbrl (Starbeamrainbowlabs): oops 11/15/2019, 10:23:31 PM - sbrl (Starbeamrainbowlabs): Make another PR and I'll quick merge 11/15/2019, 10:26:15 PM - mebeim (Marco Bonelli): Yeah I am, this is insane 😆 11/15/2019, 10:30:13 PM - mebeim (Marco Bonelli): done lol 11/15/2019, 10:31:02 PM - sbrl (Starbeamrainbowlabs): Lol, yeah 11/15/2019, 10:32:00 PM - sbrl (Starbeamrainbowlabs): Merged 11/15/2019, 10:32:33 PM - mebeim (Marco Bonelli): ty 11/15/2019, 10:40:50 PM - sbrl (Starbeamrainbowlabs): np 11/15/2019, 11:08:29 PM - mebeim (Marco Bonelli): Done, I can finally rest (for now) 😅 11/15/2019, 11:12:47 PM - agnivade (Agniva De Sarker): Yep, I think I faced a similar issue sometime back. Wiped out node_modules and reinstall seemed to do the trick. 11/15/2019, 11:12:55 PM - agnivade (Agniva De Sarker): But it's good that you are bumping it now. 11/15/2019, 11:17:00 PM - mebeim (Marco Bonelli): Yeah just lost like 1 hour trying to figure it out 😆 silly me 11/15/2019, 11:18:29 PM - agnivade (Agniva De Sarker): Happens to all of us :) And thank you for diligently looking into travis logs and catching the error ! 11/15/2019, 11:18:48 PM - mebeim (Marco Bonelli): np 😉 11/17/2019, 6:19:51 AM - sbrl (Starbeamrainbowlabs): Wow, that's a lot of Korean PRs 11/17/2019, 6:36:33 AM - mebeim (Marco Bonelli): As much as I love seeing people contribute I cannot help but think how much of a pain this will be when transforming those into `.po` files... without knowing the language... D: 11/17/2019, 6:37:58 AM - mebeim (Marco Bonelli): I mean, the same applies to other languages too, but Korean and Chinese worry me the most. 11/17/2019, 4:35:27 PM - sbrl (Starbeamrainbowlabs): Indeed 11/18/2019, 2:23:50 AM - sbrl (Starbeamrainbowlabs): tldr-bot#6 was merged 11/18/2019, 11:22:13 AM - agnivade (Agniva De Sarker): Great stuff ! Somebody want to test it out ? 11/18/2019, 11:22:23 AM - agnivade (Agniva De Sarker): I am working on the lang support now 🎉 11/18/2019, 1:43:13 PM - agnivade (Agniva De Sarker): I just found an issue in the index.json format. For each page, we store the languages and platforms the page is available in an array of separate fields. 11/18/2019, 1:43:36 PM - agnivade (Agniva De Sarker): i.e. - for a page, there is a separate array for languages, and another for platforms. 11/18/2019, 1:44:04 PM - agnivade (Agniva De Sarker): This means there is no mapping between which lang-platform combo, the page is _actually_ available in. 11/18/2019, 1:44:24 PM - agnivade (Agniva De Sarker): Unless this is fixed, lang support cannot land. 11/18/2019, 1:45:02 PM - agnivade (Agniva De Sarker): I am sending a fix for this. I hope nobody is consuming the new index.json fields yet. 11/18/2019, 2:47:53 PM - mebeim (Marco Bonelli): @agnivade are you working on the lang support on the js client or the main repo with po4a? 11/18/2019, 2:50:06 PM - agnivade (Agniva De Sarker): The js client 11/18/2019, 2:50:22 PM - agnivade (Agniva De Sarker): po4a is your domain :) 11/18/2019, 2:51:23 PM - mebeim (Marco Bonelli): I never noticed that index.json issue btw, that's funny. IMHO that file serves little-to-no purpose for a good client. A good client should be able to work without it and just rely on the system to resolve pages (it'a also much, much faster). 11/18/2019, 2:52:10 PM - agnivade (Agniva De Sarker): Yes, a lot of clients already do that. 11/18/2019, 2:52:29 PM - agnivade (Agniva De Sarker): The node client has it's own shortIndex format which gets built from the index.json 11/18/2019, 2:53:24 PM - mebeim (Marco Bonelli): Yeah I mean, whatever index format you buold, that's gonna be slower than making two syscalls to try and open the file directly 11/18/2019, 2:53:34 PM - agnivade (Agniva De Sarker): Ok, so the PR is out. And my node client is also nearly ready. 11/18/2019, 2:53:54 PM - mebeim (Marco Bonelli): But it's strange that this wasn't noticed before 11/18/2019, 2:54:12 PM - mebeim (Marco Bonelli): Are people even really using that file? 🤔 11/18/2019, 2:54:28 PM - mebeim (Marco Bonelli): It seems to me that something like this should have been noticed long ago 11/18/2019, 2:54:56 PM - agnivade (Agniva De Sarker): It's hard to notice until you actually start to write code for lang support. The issue comes up while writing the page resolution logic. 11/18/2019, 2:55:16 PM - agnivade (Agniva De Sarker): I think there's only one client with lang support, and they don't use the index file 11/18/2019, 2:56:22 PM - mebeim (Marco Bonelli): Hmmm you're right. 11/18/2019, 2:56:40 PM - agnivade (Agniva De Sarker): I don't believe there'll be just 2 syscalls. If you don't have the index file, you don't know which language/platform directory a page is in, which means you have to do a lot of `stat` calls. 11/18/2019, 2:57:21 PM - mebeim (Marco Bonelli): So what? just `open` all of them in the right order of precedence 😉 the OS takes care of it 11/18/2019, 2:57:48 PM - mebeim (Marco Bonelli): if there's a file it opens, otherwise you get a `ENOENT` 11/18/2019, 2:57:54 PM - agnivade (Agniva De Sarker): So that means, in the worst case, you end up making a lot of wasteful syscalls. 11/18/2019, 2:58:13 PM - mebeim (Marco Bonelli): not really, 4 max 11/18/2019, 2:58:41 PM - mebeim (Marco Bonelli): and that's about 4 times faster than opening and parsing any kind of index (at least on my machine) 11/18/2019, 2:59:35 PM - agnivade (Agniva De Sarker): Yes, now _that_ is a fair argument. 11/18/2019, 2:59:37 PM - mebeim (Marco Bonelli): ah, 4 max is assuming you have only two languages sorry 11/18/2019, 2:59:45 PM - mebeim (Marco Bonelli): it's 2*num_langs max 11/18/2019, 3:00:04 PM - mebeim (Marco Bonelli): i doubt people uses more than two langs though 11/18/2019, 3:00:54 PM - mebeim (Marco Bonelli): (also, this is the way `man` works) 11/18/2019, 3:01:13 PM - agnivade (Agniva De Sarker): Well yeah, the point I guess you are making is making n no. of syscalls, is faster than reading and parsing json. Which may/may not be true depending on OS/language chosen. But I get your point. 11/18/2019, 3:01:34 PM - mebeim (Marco Bonelli): not only json, even a raw binary file 11/18/2019, 3:02:08 PM - mebeim (Marco Bonelli): just opening and reading the full content of a (rather large) file is way slower than just making a bunch of syscalls that fail 11/18/2019, 3:03:01 PM - mebeim (Marco Bonelli): But yeah it's not *that* much of a speedup. Only if you're really optimizing hard for performance that'a gonna be an issue. 11/18/2019, 3:03:36 PM - mebeim (Marco Bonelli): Also yes I'm basing this entirely on my own machines so I don't exclude there could be a case where this is not true (although I doubt it) 11/18/2019, 3:03:36 PM - agnivade (Agniva De Sarker): Sure, that makes theoretical sense (but hard to confirm without actually running the tests on a variety of platforms in a variety of languages) 11/18/2019, 3:05:24 PM - agnivade (Agniva De Sarker): It would be interesting to see what is the no. of syscalls beyond which the numbers even out. 11/18/2019, 3:05:40 PM - mebeim (Marco Bonelli): That's true. In the case of the JS client this argument is basically worth zero, even if what I say was true the time to boot up the node interpereter is already ~100x the time to resolve a page, so whatever haha 11/18/2019, 3:07:31 PM - mebeim (Marco Bonelli): I *could* try that, just adding unnecessary languages on my config hahaha, but I think it's going to be a significant number, Linux is faaast 11/18/2019, 3:08:15 PM - mebeim (Marco Bonelli): The node client probably already does 10s of thousands of syscalls and runs in 140ms 11/18/2019, 3:08:25 PM - agnivade (Agniva De Sarker): haha yes 11/18/2019, 3:08:47 PM - agnivade (Agniva De Sarker): If you are interested, also try comparing across Kernel versions. 11/18/2019, 3:10:10 PM - mebeim (Marco Bonelli): Ah I didn't think of that. For now I only tested on a 4.19 and a 5.1. 11/18/2019, 3:11:20 PM - agnivade (Agniva De Sarker): I guess that's a good start. I ask because there was a paper recently showing that in the light of recent vulnerabilities like spectre, meltdown; the fixes made to the kernel has only made it slower and slower 11/18/2019, 3:11:39 PM - mebeim (Marco Bonelli): So @agnivade now the index is `page: {platform: [os1, os2, ...]}` ? 11/18/2019, 3:12:39 PM - mebeim (Marco Bonelli): @agnivade Yeah that's true, but it's not for one shot syscalls that you're going to notice the problem, it's the internal kernel routines that run constantly, like scheduling etc 11/18/2019, 3:12:54 PM - agnivade (Agniva De Sarker): it is ` {name: page, targets: [{"os": os, "language": language}]}` 11/18/2019, 3:13:04 PM - mebeim (Marco Bonelli): Oh ok 11/18/2019, 3:13:34 PM - mebeim (Marco Bonelli): So the structure is totally changed 11/18/2019, 3:14:01 PM - agnivade (Agniva De Sarker): Not totally, only the platform and language keys are removed. 11/18/2019, 3:14:10 PM - mebeim (Marco Bonelli): I wonder if this requires another https://github.com/tldr-pages/tldr/issues/2865 11/18/2019, 3:14:20 PM - agnivade (Agniva De Sarker): Yes, technically it's a breaking change. I can keep the old keys, but I wonder how many clients use this. 11/18/2019, 3:14:28 PM - mebeim (Marco Bonelli): @agnivade well that's all that there is in that index.. so basically it changed the whole structure 11/18/2019, 3:15:41 PM - agnivade (Agniva De Sarker): It changes certain parts of the json structure. If that's what you mean, then yes. 11/18/2019, 3:16:14 PM - agnivade (Agniva De Sarker): Here's the link to the paper btw if you are interested: http://delivery.acm.org/10.1145/3360000/3359640/p554-ren.pdf?ip=185.125.168.91&id=3359640&acc=TRUSTED&key=4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35%2EE47D41B086F0CDA3&__acm__=1574070503_b67c08d530bb6891336b86546c50f272 11/18/2019, 3:16:16 PM - mebeim (Marco Bonelli): What I'm thinking about is that if anyone was using it for page resolution (even without language support) that's going to break the client 11/18/2019, 3:16:33 PM - agnivade (Agniva De Sarker): Yep, it'll break the client. 11/18/2019, 3:16:41 PM - mebeim (Marco Bonelli): thank you for the link will give it a read :) 11/18/2019, 3:16:58 PM - agnivade (Agniva De Sarker): That's why I said, I can keep the old keys if you are concerned about breakage. 11/18/2019, 3:17:42 PM - mebeim (Marco Bonelli): Well.. I don't remember how many clients use it. 11/18/2019, 3:18:47 PM - mebeim (Marco Bonelli): When I opened https://github.com/tldr-pages/tldr/issues/2865 I was only looking at the position of the file if it was used... I should go through that list again to be sure 11/18/2019, 3:19:14 PM - mebeim (Marco Bonelli): What we can say is only that this *could* break some client... 11/18/2019, 3:19:37 PM - agnivade (Agniva De Sarker): Hmm .. wait, older versions of node client will itself break. Gah .. we need to keep the old keys. 11/18/2019, 3:19:45 PM - agnivade (Agniva De Sarker): Okay, will update it. 11/18/2019, 3:19:51 PM - mebeim (Marco Bonelli): Oh LOL, that's... a good argument 11/18/2019, 3:20:16 PM - mebeim (Marco Bonelli): So just keep `language`, `platform` and add `targets`? 11/18/2019, 3:25:10 PM - mebeim (Marco Bonelli): Oh wow, those numbers on that paper are way worse than I thought D: unfortunately (or maybe fortunately) they don't talk specifically about `open` or `stat` haha 11/18/2019, 4:58:58 PM - sbrl (Starbeamrainbowlabs): That link 404s for me. What are we talking about here? 11/18/2019, 5:00:45 PM - sbrl (Starbeamrainbowlabs): Ah, the messages just came in for me 11/18/2019, 5:00:54 PM - sbrl (Starbeamrainbowlabs): Yeah, parsing JSON does actually take a while 11/18/2019, 5:01:21 PM - sbrl (Starbeamrainbowlabs): I found that it can upwards of ~300ms to ~500ms to parse a 1MiB JSON file 11/18/2019, 5:01:54 PM - sbrl (Starbeamrainbowlabs): Hence for my full-text search engine, I now use a key-value store in an SQLite Database which I then have smaller bites of JSON in 11/18/2019, 5:02:10 PM - sbrl (Starbeamrainbowlabs): Then this allows for partial deseerialisation, which is much faster 11/18/2019, 5:02:40 PM - sbrl (Starbeamrainbowlabs): I blogged about it here: https://starbeamrainbowlabs.com/blog/article.php?article=posts/372-next-gen-search-1-backend-storage.html 11/18/2019, 5:03:23 PM - sbrl (Starbeamrainbowlabs): and https://starbeamrainbowlabs.com/blog/article.php?article=posts/375-next-gen-search-2-test-data.html 11/18/2019, 5:32:35 PM - agnivade (Agniva De Sarker): @sbrl - Check this link if that one 404s for you. https://dl.acm.org/citation.cfm?id=3359640 11/18/2019, 5:33:51 PM - mebeim (Marco Bonelli): we were just talking about the speed of raw syscalls, off topic funny stuff 11/18/2019, 8:38:55 PM - sbrl (Starbeamrainbowlabs): Ah, I see 11/18/2019, 8:43:39 PM - sbrl (Starbeamrainbowlabs): Interesting 11/18/2019, 8:43:52 PM - sbrl (Starbeamrainbowlabs): The Linux kernel has seriously slowed down recently it looks like 11/18/2019, 8:47:18 PM - mebeim (Marco Bonelli): yeah right? all those security patches... 😟 well let's just say that if you take into account the performance increase of newer processors the speed is the same 😂 11/18/2019, 11:26:24 PM - sbrl (Starbeamrainbowlabs): Indeed! 11/18/2019, 11:36:28 PM - agnivade (Agniva De Sarker): Can anybody help me find an npm package for posix locale parsing ? 11/18/2019, 11:36:36 PM - agnivade (Agniva De Sarker): All I see are for BCP47 formats 11/18/2019, 11:39:00 PM - sbrl (Starbeamrainbowlabs): Check out the top result for the search query: 11/18/2019, 11:39:01 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/F3XR/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/F3XR/image.png) 11/18/2019, 11:39:25 PM - agnivade (Agniva De Sarker): lol 11/18/2019, 11:40:22 PM - sbrl (Starbeamrainbowlabs): What are the differences between the 2 formats? 11/18/2019, 11:40:59 PM - sbrl (Starbeamrainbowlabs): Could we translate between the two by doing `tr '-' '_'` 11/18/2019, 11:42:27 PM - agnivade (Agniva De Sarker): I think there are some differences. As @mebeim pointed out here https://github.com/tldr-pages/tldr-node-client/pull/270#discussion_r300885553. There can be encodings with a period at the end. Or even `@` signs. 11/18/2019, 11:44:02 PM - mebeim (Marco Bonelli): @agnivade you don't need anything special to parse posix locales 11/18/2019, 11:44:22 PM - mebeim (Marco Bonelli): they are in the form `ll[_CC[.encoding]]` 11/18/2019, 11:44:40 PM - mebeim (Marco Bonelli): so just take everything until a `.` or the end 11/18/2019, 11:45:09 PM - sbrl (Starbeamrainbowlabs): We do follow the POSIX spec now IIRC 11/18/2019, 11:45:13 PM - mebeim (Marco Bonelli): ye 11/18/2019, 11:46:51 PM - mebeim (Marco Bonelli): it's basically just a regex: `[a-z]{2,3}(_[A-Z]{2})?` 11/18/2019, 11:48:39 PM - agnivade (Agniva De Sarker): Ah I see. I should have looked at the spec closer. Ok, that takes away one more dependency. Thanks ! 11/18/2019, 11:49:28 PM - mebeim (Marco Bonelli): np 11/18/2019, 11:49:52 PM - mebeim (Marco Bonelli): by the way, I was looking here: https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#page-structure 11/18/2019, 11:50:00 PM - mebeim (Marco Bonelli): Specifically the phrase "Clients MUST NOT break if the page format is changed within the CommonMark specification." 11/18/2019, 11:50:35 PM - mebeim (Marco Bonelli): Seems like a fairly strong requirement, I doubt most of the clients would still function if the examples are not formatted the right way... 11/18/2019, 11:52:31 PM - sbrl (Starbeamrainbowlabs): Yeah. Basically that's for things such as adding the more information `` syntax 11/18/2019, 11:52:44 PM - sbrl (Starbeamrainbowlabs): It is a strong requirement, yeah 11/18/2019, 11:52:54 PM - mebeim (Marco Bonelli): It's stronger than that 11/18/2019, 11:53:06 PM - mebeim (Marco Bonelli): It basically says "as long as the page is markdown, it should work" 11/18/2019, 11:53:16 PM - mebeim (Marco Bonelli): I doubt that's the case with any client. 11/18/2019, 11:53:23 PM - sbrl (Starbeamrainbowlabs): True 11/18/2019, 11:53:34 PM - sbrl (Starbeamrainbowlabs): Above I'm only giving an example 11/18/2019, 11:53:37 PM - mebeim (Marco Bonelli): Should probably be rephrased.. but whatever 11/18/2019, 11:53:48 PM - sbrl (Starbeamrainbowlabs): it's specifically because we can't predict how we will need to update the page format in the future 11/18/2019, 11:54:41 PM - sbrl (Starbeamrainbowlabs): i.e. if you want to extract intelligence from our pages, you really should parse them properly rather than using regular expressions for example 11/18/2019, 11:54:51 PM - sbrl (Starbeamrainbowlabs): i.e. parse tree etc 11/18/2019, 11:56:12 PM - mebeim (Marco Bonelli): I doubt anyone does that 😆 I use a simple greedy parser, but I managed to support both the current and the proposed new syntax 11/18/2019, 11:59:18 PM - sbrl (Starbeamrainbowlabs): Yeah, I'm unsure as to whether that new syntax will ever be adopted at this rate 11/18/2019, 11:59:47 PM - mebeim (Marco Bonelli): Hope never dies I guess 11/19/2019, 12:00:38 AM - mebeim (Marco Bonelli): But yea, I don't see how that could be done easily... 11/19/2019, 3:58:06 AM - mebeim (Marco Bonelli): I was thinking that for the po4a support thing we will have to "lock down" the repo from accepting PRs momentarily 11/19/2019, 4:09:07 AM - owenvoke (Owen Voke): Anyone else having session issues with GitHub? 11/19/2019, 4:11:10 AM - mebeim (Marco Bonelli): What kind of issues? 11/19/2019, 4:19:31 AM - owenvoke (Owen Voke): https://i.imgur.com/Ippa5oo_d.jpg?maxwidth=800 11/19/2019, 4:20:23 AM - owenvoke (Owen Voke): Kept getting it randomly yesterday night, and now a few times this evening. 🤔 11/19/2019, 4:20:58 AM - mebeim (Marco Bonelli): Hmm, nope, it's been a while since the last time I saw that beautiful interrobang 11/19/2019, 4:26:06 AM - owenvoke (Owen Voke): No worries. I'll leave it until the morning. :+1: 11/19/2019, 11:07:38 AM - agnivade (Agniva De Sarker): Woops, no issues here. 11/19/2019, 11:09:42 AM - agnivade (Agniva De Sarker): @mebeim - Can you outline your plan on po4a support ? We can do a lock down, but I would like to know more on the specifics. 11/19/2019, 5:18:05 PM - sbrl (Starbeamrainbowlabs): Yeah. Ideally we'd want the lockdown to be as short as possible - potentially with a README message. 11/19/2019, 6:27:16 PM - mebeim (Marco Bonelli): Plan on support: 1. Finish the scripts to generate translations in my po4a branch and familiarize with them, then generate a first version of the .po files (just for Weblate to look into when considering our request) 2. Request hosting to Weblate 3. Figure out how Weblate would integrate and adapt the build system 4. Merge as much translation PRs as possible, then stop merging them to keep the .po files stable to not have any conflict (we can leave PRs open but just without merging, or we can even merge them but update the .po file manually each time one is merged) 5. Generate final version of .po files 6. Integrate the new build system and update README to point to the new translation platform 7. Unlock PRs, close all remaining translation PRs linking to the new platform (or manually transfer them to .po files) This will be quite hard to do and will require fast reciew and collaboration (not at the usual rythm we work) if we want to make the transition as short as possible. 11/19/2019, 6:29:18 PM - mebeim (Marco Bonelli): The build process will have to be subject to change for amy action: adding new pages, editin existing pages, updating translations from weblate 11/19/2019, 6:29:31 PM - mebeim (Marco Bonelli): (sorry for typos I'm on my phone) 11/19/2019, 6:33:54 PM - mebeim (Marco Bonelli): I don't quite get what @mquinson says here: https://github.com/tldr-pages/tldr/pull/2793#issuecomment-553128272 he says we are "quite close" but really to me it really seems the opposite 11/19/2019, 7:09:18 PM - sbrl (Starbeamrainbowlabs): If someone posts a link to an urgent PR or issue that they need me to look into here, I'm happy to do a fast review. I'd also suggest in step #1 that we write some additional documentation on how to contribute translations, so as to not confuse people 1/14/2023, 3:36:21 PM - mquinson (Martin Quinson) joined the room 11/19/2019, 7:47:35 PM - mquinson (Martin Quinson): Hello @mebeim , gitter brought me here :) 11/19/2019, 7:48:19 PM - mquinson (Martin Quinson): I may be somewhat optimistic by nature... But I think that the harder/longer part will not be to setup the infrastructure but instead to actually translate the content 11/19/2019, 7:48:59 PM - mquinson (Martin Quinson): Step 3 for example is very easy 11/19/2019, 7:51:47 PM - mquinson (Martin Quinson): to the opposite, step 4 does not sound like a cleaver idea to me: gettextize the existing translation (merging existing translated md files into the po file) is a non-trivial step. If the translators did something wrong like changing the structure of the doc, then you are in trouble. You have to either discard their translation (but that's hard if the PR is merged) or modify the document to fix the doc structure (but that's rather hard if you don't even recognize the words in the translation -- I've done that often for all european languages where I can at least recognze some words, but I could not do that for asian languages) 11/19/2019, 7:52:32 PM - mquinson (Martin Quinson): If the docs are shorts and if you recognize some words, that may be doable however 11/19/2019, 7:52:49 PM - sbrl (Starbeamrainbowlabs): The structure of translations should be the same as the document they are translating @mquinson 11/19/2019, 7:53:13 PM - mquinson (Martin Quinson): of course they should. But in practice, they rarely do 😉 Believe my experience here... 11/19/2019, 7:53:18 PM - sbrl (Starbeamrainbowlabs): I'd rather not discard existing translations, because we have literally hundreds of pre-existing translations already 11/19/2019, 7:53:51 PM - sbrl (Starbeamrainbowlabs): If po4a isn't capable of handling that, then I'm cautious about using it here 11/19/2019, 7:54:29 PM - mquinson (Martin Quinson): yes, that's for sure. I'm just saying that the more you wait, the more raw translation you'll get. And the more raw translations you have to integrate into po4a, the more manual work the transition is. 11/19/2019, 7:54:51 PM - sbrl (Starbeamrainbowlabs): I'm sure if there are discrepancies, then we can fix those manually 11/19/2019, 7:55:44 PM - mquinson (Martin Quinson): The strategy I'd advise would be to freeze the existing PR, move as fast as possible to po4a to ensure that future translation work will not increase the transition work, and then handle those translations 11/19/2019, 7:56:25 PM - mquinson (Martin Quinson): @sbrl I'm not saying otherwise. I'm just saying that if the structure changed (and it will in some case), then that's a manual operation. 11/19/2019, 7:57:19 PM - sbrl (Starbeamrainbowlabs): That's basically what @mebeim has said though. Or am I missing something? Well, yes 11/19/2019, 7:57:47 PM - mquinson (Martin Quinson): Again, I'm just discussing step 4 11/19/2019, 8:12:45 PM - mebeim (Marco Bonelli): I agree with @mquinson that step 4 just makes it harder to keep track of translations and generate po files. 11/19/2019, 8:13:25 PM - mebeim (Marco Bonelli): Freezing is probably better indeed... 11/19/2019, 8:18:39 PM - sbrl (Starbeamrainbowlabs): Yeah, but we should at least merge the ones that people have submitted 11/19/2019, 8:20:13 PM - mebeim (Marco Bonelli): I hope step 3 is as easy as you say. gettextize-ing existing translations seemed pretty straight forward to me when doing it for a language I know (like Italian). The only problem is what to do for pages written in languages we do not know. The best thing is to probably set the missing fields as empty (with the help of google translate just to understand which translated fields correspond to which english fields) and generate the po files. 11/19/2019, 8:20:43 PM - mebeim (Marco Bonelli): @sbrl well I would like to too yeah 11/19/2019, 8:21:37 PM - mebeim (Marco Bonelli): Point is, even if that makes it harder to bootstrap translations, it seems like it would be harder to integrate (or migrate) those PRs later 11/19/2019, 8:21:49 PM - sbrl (Starbeamrainbowlabs): If they don't match up, we can always discard if we need to 11/19/2019, 8:21:57 PM - sbrl (Starbeamrainbowlabs): True 11/19/2019, 8:24:12 PM - sbrl (Starbeamrainbowlabs): Is there a way we can identify which translated pages match up and which don't? We could always have something like ``` for each page { success, result = make_po_file(page); if(!success) continue; save(result); } ``` 11/19/2019, 8:24:34 PM - mebeim (Marco Bonelli): it's not at all that easy 11/19/2019, 8:27:21 PM - mebeim (Marco Bonelli): I'll explain it simply, gettextize works like this: 1. It reads the original document (English, e.g. `pages/common/ls.md`) and extracts the strings that need to be translated. 2. It looks at the corresponding translated document (e.g. `pages.ko/common/ls.md`) and *tries to match the strings*. 3. If they match (which basically just means they are the same number and in the same order), the translation is added to the `.po` file. 4. Otherwise a conflict happens and the translated document (i.e. `pages.ko/common/ls.md`) **has to be manually fixed to add the missing strings (even empty, just as a placeholder)**, then the tool can be re-run. 11/19/2019, 8:28:47 PM - mebeim (Marco Bonelli): With this said, I already created a script that does this interactively. It scans all pages and generates a `.po` file for each page, pausing and asking for user intervention if there is some problem. You can see it in the `po4a` branch on my fork: https://github.com/mebeim/tldr/blob/po4a/l10n/scripts/bootstrap-translation.sh 11/19/2019, 8:29:30 PM - mebeim (Marco Bonelli): The only missing thing is joining all the single `.po` files into a big `.po` file for the whole language, which should be easy. 11/19/2019, 8:30:07 PM - sbrl (Starbeamrainbowlabs): Ah, right - I see! 11/19/2019, 8:30:11 PM - mebeim (Marco Bonelli): The problem here is that step 4 has to be done for all languages with the existing pages. You can discard a PR, but you cannot discard an existing page. What do you do? Throw it away? Doesn't look right. 11/19/2019, 8:31:17 PM - sbrl (Starbeamrainbowlabs): Hrm. It sounds to me like we've got 2 options: - Discard all open PRs - Discard all pages that don't go through automatically 11/19/2019, 8:31:31 PM - mebeim (Marco Bonelli): So I, for example, can do this easily for Italian pages, and other folks can do it easily for languages they speak. The problem is for stuff like Korean where we do not have a collaborator of reference that could do it. 11/19/2019, 8:32:19 PM - mebeim (Marco Bonelli): @sbrl hmmm not quite 11/19/2019, 8:33:00 PM - mebeim (Marco Bonelli): Would we discard valid translations? We have to integrate them, not discard them. 11/19/2019, 8:34:04 PM - sbrl (Starbeamrainbowlabs): I think I'm getting confused here. 11/19/2019, 8:34:25 PM - mebeim (Marco Bonelli): I can explain in DM if you want 11/19/2019, 8:34:34 PM - mebeim (Marco Bonelli): If you have some particular question/doubt 11/19/2019, 8:34:35 PM - sbrl (Starbeamrainbowlabs): The only reason I can foresee it not going through is if the English page has been updated since the translation was made 11/19/2019, 8:34:51 PM - mebeim (Marco Bonelli): Yes, that's basically almost always the case 11/19/2019, 8:35:07 PM - mebeim (Marco Bonelli): But it's pretty frequent 11/19/2019, 8:35:18 PM - sbrl (Starbeamrainbowlabs): Hrm, that's not good 11/19/2019, 8:35:28 PM - sbrl (Starbeamrainbowlabs): A difficult problem, to be sure 11/19/2019, 8:35:36 PM - mebeim (Marco Bonelli): I mean, maybe I'm overstating it, just take a look for yourself 11/19/2019, 8:35:55 PM - sbrl (Starbeamrainbowlabs): I'd perhaps suggest handing it in 2 stages: 1. All the pages that can be automatically converted 2. All the pages that don't go through 11/19/2019, 8:36:37 PM - mebeim (Marco Bonelli): what do you mean by "converted" here? 11/19/2019, 8:36:46 PM - mebeim (Marco Bonelli): converted to po? 11/19/2019, 8:36:50 PM - sbrl (Starbeamrainbowlabs): yeah 11/19/2019, 8:36:55 PM - sbrl (Starbeamrainbowlabs): or I assume so 11/19/2019, 8:37:44 PM - mebeim (Marco Bonelli): well, the order isn't really important 11/19/2019, 8:38:57 PM - mebeim (Marco Bonelli): If by that you mean that stage 1 should be done before integrating weblate and stage 2 after, I wouldn't advise that 11/19/2019, 8:39:46 PM - sbrl (Starbeamrainbowlabs): ....I see 11/19/2019, 8:40:28 PM - sbrl (Starbeamrainbowlabs): The whole process seems to be terribly complicated lol 11/19/2019, 8:40:49 PM - mebeim (Marco Bonelli): That's for sure IMHO 11/19/2019, 8:41:37 PM - mebeim (Marco Bonelli): And I still have to see how Weblate integrates with the build process. 11/19/2019, 8:42:44 PM - mebeim (Marco Bonelli): So I would propose freezing translation PRs only accepting the important ones 11/19/2019, 8:46:36 PM - sbrl (Starbeamrainbowlabs): Right. From when should the freeze occur? 11/19/2019, 8:46:50 PM - sbrl (Starbeamrainbowlabs): (and how will be let people know about it?) 11/19/2019, 8:49:01 PM - mebeim (Marco Bonelli): we could update the readme/contirbuting documents as per the "when" I have no idea 11/19/2019, 8:49:47 PM - mebeim (Marco Bonelli): This change should be done fast, but I doubt I would find the needed time. 11/19/2019, 8:50:54 PM - mebeim (Marco Bonelli): I should write to Weblate and see what they respond. 11/19/2019, 8:51:58 PM - sbrl (Starbeamrainbowlabs): Good idea. Yeah, it should Let's do that first, to see if they are willing. When we can decide where to go from there. 11/19/2019, 9:44:45 PM - mebeim (Marco Bonelli): By the way, if you want to give https://github.com/tldr-pages/tldr/pull/3576 a read + review, the more people look at it the better. 11/19/2019, 9:57:09 PM - sbrl (Starbeamrainbowlabs): I've taken a full and proper look at that issue for you @mebeim - I skimmed it the last few times. 11/19/2019, 9:57:16 PM - sbrl (Starbeamrainbowlabs): I've made a bunch of comments. 11/19/2019, 9:58:00 PM - mebeim (Marco Bonelli): thank you very much :) 11/19/2019, 9:58:42 PM - sbrl (Starbeamrainbowlabs): np :-) 11/19/2019, 10:06:12 PM - mebeim (Marco Bonelli): Are we using indentation with two spaces for any particular reason? 11/19/2019, 10:06:44 PM - mebeim (Marco Bonelli): I would suggest changing to 4 (or a tab), 2 spaces really make it hard to read the code for me sometimes 11/19/2019, 10:08:24 PM - sbrl (Starbeamrainbowlabs): I would personally prefer a literal tab character. If you're talking about the bash script - I use a tab character in all of my scripts. 11/19/2019, 10:15:48 PM - mebeim (Marco Bonelli): I use tabs in all of my scripts too. I don't know why the two spaces are set up here in `.editorconfig` though, so that's why I am asking. Most of the times, spaces are used to keep indentation consistent everywhere for everyone. If this is the case, then I would suggest changing from 2 to 4 spaces since 2 spaces indentation is really not that much and I find it confusing (don't know if I'm the only one, but I find myself having to read chunks of code two or three times because I miss the matching starting statement). 11/19/2019, 10:19:08 PM - sbrl (Starbeamrainbowlabs): Ah, I see. I'd change that personally 11/19/2019, 10:19:38 PM - mebeim (Marco Bonelli): I'll open an Issue when I can 11/19/2019, 10:20:57 PM - sbrl (Starbeamrainbowlabs): cool. I'm just reviewing the tldr-node-client PR atm 11/19/2019, 10:23:38 PM - agnivade (Agniva De Sarker): Thanks for the update @mebeim. I have only skimmed the conversation here, as I probably need to go through the issue again to get full context. Are you blocked on composing the message for Weblate ? 11/19/2019, 10:25:31 PM - mebeim (Marco Bonelli): Nope, just haven't thought about what to write yet. 11/19/2019, 10:27:10 PM - agnivade (Agniva De Sarker): Cool. When you have a draft ready, @waldyrious can help fine tuning it. 11/19/2019, 10:30:43 PM - sbrl (Starbeamrainbowlabs): :+1: 11/19/2019, 10:49:33 PM - sbrl (Starbeamrainbowlabs): Wow, 75% of PRs in my notifications are translations 11/19/2019, 11:02:41 PM - mebeim (Marco Bonelli): I'd rather have someone else write to Weblate since I don't have much time and it would also require reading their doc and understanding how it would work 11/19/2019, 11:03:56 PM - mebeim (Marco Bonelli): I have too many university projects to handle starting from this week and until january/february, I don't know how consistently I can contribute in this period 11/19/2019, 11:05:45 PM - mebeim (Marco Bonelli): One thing to notice is that here https://weblate.org/en/hosting/ weblate says "25 translation components". So the definition of "component" seems to be important and needs to be looked into. 11/20/2019, 12:02:31 AM - sbrl (Starbeamrainbowlabs): Looks like a translation component is a like a GitHub repository 11/20/2019, 12:02:53 AM - sbrl (Starbeamrainbowlabs): I'm drafting something to send to Weblate now. I'll open an issue once done. 11/20/2019, 12:08:01 AM - sbrl (Starbeamrainbowlabs): Opened #3591 11/20/2019, 2:27:54 AM - mquinson (Martin Quinson): @mebeim to me, the best is to have one component per per software package if you can afford it on weblate. I mean, if there is say 3 ssh-related pages (ssh, ssh-keygen, scp) then you put them in the same component. If you do one component per page, the expertise it takes to contribute and translate decently is spread accross many pages. If you do one big huge component, you may have difficulties to have more than one translator at the same time 11/20/2019, 2:28:47 AM - mquinson (Martin Quinson): in both cases (one huge component or too many small components), someone wanting to collaborate to a given software package because s·he is expert of it will first need to collect all parts back 11/20/2019, 2:34:39 AM - sbrl (Starbeamrainbowlabs): @mquinson: 1 problem: we don't currently differentiate between which software package a page comes from in tldr-pages. 11/20/2019, 2:47:47 AM - mebeim (Marco Bonelli): @mquinson I don't think that grouping would be feasible. We do not track similar commands or packages of commands. It would be challenging to say the least, if not impossible. Doing one component === one page would be better at that point. Either way, if we want to ask for hosting both solutions are still impossible, since it's way above the 25 components limit that Weblate offers. The only real solution would be less, huge components. I'm not even sure how you would define a component though, I only took a quick look at the docs, not enough to fully understand how it would work and which meaning would a component have. 11/20/2019, 2:49:08 AM - sbrl (Starbeamrainbowlabs): I'd start with 1 huge component. It looks like weblate can be self-hosted - so perhaps someone could spin up a local instance to see what 1 big component would look like? 11/20/2019, 2:50:24 AM - mebeim (Marco Bonelli): Self hosting with one huge component doesn't make sense IMHO. If you self-host you can add as many components as you want, and there would be no advantage (only disadvantages) in having a huge single component instead of one component per page. 11/20/2019, 2:54:29 AM - sbrl (Starbeamrainbowlabs): Oops, looks like I wasn't clear. I'm suggesting that someone spins up a test instance and loads in 1 huge component, and takes a screenshot 11/20/2019, 2:54:49 AM - sbrl (Starbeamrainbowlabs): so that we can see what it looks like. 11/20/2019, 2:55:02 AM - sbrl (Starbeamrainbowlabs): Depending on resource usage, I may be able to self-host. 11/20/2019, 2:55:23 AM - sbrl (Starbeamrainbowlabs): but it would have to be fairly light and _not_ use a MySQL/MariaDB database 11/20/2019, 2:55:44 AM - sbrl (Starbeamrainbowlabs): (I don't and will not have a database server of any kind running) 11/20/2019, 2:57:07 AM - mebeim (Marco Bonelli): 1) The main issue of having one compinent is not that weblate cannot handle it or that the interface would be counter intuitive, it's as @mquinson said that multiple people working on it would have trouble. 2) The main problem is that nobody here knows how the whole thing would work and therefore we don't have a clear plan. The situation needs to be studied and the solutions need to be tested. 3) *Of course* you would need a database, if not several different databases LOL 11/20/2019, 2:59:46 AM - sbrl (Starbeamrainbowlabs): I see. ....SQLite DBs are ok, but I don't have the resources to run something like MySQL/MariaDB/PostgreSQL 😕 11/20/2019, 3:01:34 AM - mebeim (Marco Bonelli): Weblate uses a lot of different pieces of software, I don't know how resource intensive it is, but they provide Docker images so that would be easy to find out (of course, after understanding how to set it all up, which is already kind of a challenge). 11/20/2019, 3:11:08 AM - mebeim (Marco Bonelli): Okay, I think it's quite clear what a component is from this page in the docs: https://docs.weblate.org/en/latest/admin/projects.html#component-configuration 11/20/2019, 3:11:44 AM - mebeim (Marco Bonelli): So yeah, having huge components is not advisable :\ I think this already kills the idea of asking for free hosting. 11/20/2019, 3:23:13 AM - sbrl (Starbeamrainbowlabs): Hrm, it might do, yeah. I'd advise commenting on the issue I opened then 11/20/2019, 3:23:24 AM - sbrl (Starbeamrainbowlabs): We might be back to the drawing board...... 11/20/2019, 3:24:04 AM - mebeim (Marco Bonelli): yeah, most probably 11/20/2019, 9:26:39 AM - agnivade (Agniva De Sarker): What if we group the pages according to their frequency by their starting letters. For eg - a-h, i-k,l-t ... ? 11/20/2019, 5:15:09 PM - mebeim (Marco Bonelli): We have 1.6k pages. Any way we choose to split them into 25 groups, it's going to be around 64 per group, the problem persists. 11/20/2019, 5:17:45 PM - agnivade (Agniva De Sarker): Is there a limit to the no. of entries per group ? 11/20/2019, 5:18:11 PM - agnivade (Agniva De Sarker): Or you mean it will be problematic if there are too many entries in a group ? 11/20/2019, 5:18:28 PM - mebeim (Marco Bonelli): 2nd one 11/20/2019, 5:19:37 PM - agnivade (Agniva De Sarker): What do you think is the cutoff no. for the no. of entries in a group ? 11/20/2019, 5:22:49 PM - mebeim (Marco Bonelli): Well, surely way less than 64 :\ I would say 1 ideally, but just because having something like 2-3-10 per group wouldn't make much sense (based on what woukd you group at that point?). 11/20/2019, 5:23:22 PM - mebeim (Marco Bonelli): Someone has to spin up a test instance of Weblate and see what happens when two or more users contribute on the same group. 11/20/2019, 5:25:08 PM - agnivade (Agniva De Sarker): Right, I don't think there's much use speculating. It will be good to see practical results 11/20/2019, 5:38:16 PM - mebeim (Marco Bonelli): True. 11/21/2019, 5:35:16 PM - agnivade (Agniva De Sarker): tldr-node-client v3.3.1 with language support is now published ! 11/21/2019, 5:35:31 PM - agnivade (Agniva De Sarker): Please test it out and let me know if there are any issues. 11/21/2019, 5:36:49 PM - agnivade (Agniva De Sarker): Sorry there was a small bug in 3.3.0 which was to be the intended release, so I missed the nice round figure 😛 11/21/2019, 5:51:12 PM - sbrl (Starbeamrainbowlabs): Awesome, @agnivade 😃 11/21/2019, 5:51:30 PM - sbrl (Starbeamrainbowlabs): You could always put out 2 more patches and get v3.3.3 😛 11/22/2019, 1:53:12 PM - mebeim (Marco Bonelli): Has there ever been a discussion about the current rules for community role changes? If so can anyone link it? I would be interested in reading it just to see how the contribution goals described in`COMMUNITY-ROLES.md` doc were decided. 11/22/2019, 6:32:24 PM - agnivade (Agniva De Sarker): It should be in the associated PR. 11/22/2019, 6:36:03 PM - mebeim (Marco Bonelli): ah you're right i can just look at the git blame of the file 11/22/2019, 6:36:10 PM - mebeim (Marco Bonelli): nvm 11/27/2019, 4:00:43 AM - waldyrious (Waldir Pimenta): Any concerns in particular about the roles, @mebeim? Hopefully I can offer some context as IIRC I was involved in most if not all decisions related to that doc 11/27/2019, 4:01:17 AM - waldyrious (Waldir Pimenta): (also, phew, I finally managed to catch up with the Gitter chat backlog! Now if I could only do the same with the GH notifications... 😛) 11/27/2019, 4:02:29 AM - waldyrious (Waldir Pimenta): > Yeah, I'm unsure as to whether that new syntax will ever be adopted at this rate @sbrl I certainly haven't given up 😉 11/27/2019, 4:03:35 AM - sbrl (Starbeamrainbowlabs): @waldyrious: Congrats! Yeah, there's been quite a bit of chatter here. Lol, I'm sure we'll be able to organise the new syntax eventually 😛 11/27/2019, 4:23:28 AM - mebeim (Marco Bonelli): Not at all @waldyrious just curiosity 11/27/2019, 4:56:22 AM - waldyrious (Waldir Pimenta): :+1: 11/27/2019, 5:30:33 AM - waldyrious (Waldir Pimenta): I've commented in https://github.com/tldr-pages/tldr/pull/3543#issuecomment-558867787 with what may be a clearer argument towards linking to online manpages than I've been able to formulate before. Please take a look and let me know what you think! 11/27/2019, 5:36:18 AM - sbrl (Starbeamrainbowlabs): Ah, thanks so much! That's a great way of expressing it. 11/27/2019, 6:14:33 AM - principis (Arthur Bols): I think I'm blind 😛 is there an issue for the new syntax discussed here? (I haven't been following lately so this is the first thing I heard about it) 11/27/2019, 6:17:32 AM - mebeim (Marco Bonelli): Hmm no there hasn't been a discussion about that AFAIK 11/27/2019, 6:19:51 AM - principis (Arthur Bols): I just saw my email about unread messages and saw "Lol, I'm sure we'll be able to organise the new syntax eventually 😛" So I'm very confused 11/27/2019, 6:23:01 AM - mebeim (Marco Bonelli): I think someone mentioned it, don't remember the context, but it was just that. 11/27/2019, 6:23:22 AM - sbrl (Starbeamrainbowlabs): Yeah, there's a huge big issue on it. I'm having trouble tracking it down though 11/27/2019, 6:23:36 AM - mebeim (Marco Bonelli): I would love to see the new syntax adopted but it's not easy at all 11/27/2019, 6:24:28 AM - mebeim (Marco Bonelli): (just for client compatibility though, converting pages is easy) 11/27/2019, 6:24:49 AM - principis (Arthur Bols): Do you mean the translations? 11/27/2019, 6:25:18 AM - principis (Arthur Bols): I can't find any other issue about syntax 😕 11/27/2019, 6:27:19 AM - mebeim (Marco Bonelli): I mean the new pages structure/syntax 11/27/2019, 6:28:59 AM - mebeim (Marco Bonelli): If only I could find the discussion on GitHub 😅 11/27/2019, 6:29:00 AM - sbrl (Starbeamrainbowlabs): Hrm, I can't find it 11/27/2019, 6:29:29 AM - principis (Arthur Bols): > If only I could find the discussion on GitHub 😅 I just wanted to ask haha 11/27/2019, 6:29:39 AM - sbrl (Starbeamrainbowlabs): I think we might need @waldyrious' awesome powers of finding previous discussions here 11/27/2019, 6:32:22 AM - principis (Arthur Bols): I'm going to bed, feel free to mention me if you find it :) (I'll also try to follow here) 11/27/2019, 6:42:19 AM - mebeim (Marco Bonelli): The only thing I can remember is that the new proposed syntax was like this: ``` # command > Desc. > Desc. > Desc. Example 1 desc: example 1 code Example 2 desc: example 2 code``` 11/27/2019, 3:25:06 PM - waldyrious (Waldir Pimenta): The PR was closed by stale-bot due to lack of progress after a long time: https://github.com/tldr-pages/tldr/pull/958 11/27/2019, 3:25:47 PM - waldyrious (Waldir Pimenta): We never bothered to reopen it because we didn't have a roadmap for quick progress 11/27/2019, 3:26:47 PM - waldyrious (Waldir Pimenta): IIRC the main issue blocking progress was the linter, which needed the rewrite in a more familiar language/framework, so that it could be adapted to support the new syntax 11/27/2019, 4:16:07 PM - principis (Arthur Bols): Ow wow that's older than my client. 😅 Thanks 11/27/2019, 4:43:57 PM - mebeim (Marco Bonelli): Ah yes, the linter was the main problem... thanks for finding that @waldyrious 11/27/2019, 5:00:31 PM - sbrl (Starbeamrainbowlabs): Ah, that's the one @waldyrious. No wonder I couldn't find it - it was a PR 😛 11/27/2019, 5:00:57 PM - sbrl (Starbeamrainbowlabs): tbh the new syntax would certainly make translations easier 11/27/2019, 5:36:29 PM - waldyrious (Waldir Pimenta): Any news about the linter? I'd love to help if there was good documentation of how to convert the current code into the new one. Any resources you guys could share in that regard? 11/27/2019, 5:36:42 PM - waldyrious (Waldir Pimenta): That way we could make some progress towards the new syntax 11/27/2019, 5:40:38 PM - sbrl (Starbeamrainbowlabs): I think we've got a project spec on the wiki about it, where I suggested we use [Nearley](https://www.npmjs.com/package/nearley) + Node.js to rebuild the linter. 11/27/2019, 5:41:06 PM - sbrl (Starbeamrainbowlabs): @waldyrious 11/27/2019, 6:08:29 PM - waldyrious (Waldir Pimenta): My main issue is understanding the existing linter. Is there a good introductory overview of how Lex/Yacc work? 11/27/2019, 7:17:20 PM - sbrl (Starbeamrainbowlabs): Hrm - that's a tough one. I can basically understand what's going on because of the_Languages and Compilers_ module I've take at University, in which we built a compiler with flex and bison (the successors to lex and yacc). 11/27/2019, 7:17:26 PM - sbrl (Starbeamrainbowlabs): Let me see if can find anything 11/27/2019, 7:18:15 PM - sbrl (Starbeamrainbowlabs): Try this slide deck? https://www.capsl.udel.edu//courses/cpeg421/2012/slides/Tutorial-Flex_Bison.pdf 11/27/2019, 7:18:33 PM - sbrl (Starbeamrainbowlabs): If you have any specific questions, I'm happy to answer them. 11/27/2019, 7:18:54 PM - sbrl (Starbeamrainbowlabs): I haven't read the linter code in a while though 11/27/2019, 7:19:26 PM - sbrl (Starbeamrainbowlabs): There are 2 parts to writing the linter: 1. Building a parse tree that represents the page itself 2. Walking that parse tree to ensure everything is in order 11/27/2019, 7:31:44 PM - mebeim (Marco Bonelli): @waldyrious lex/yacc/bison are all super cool but also super difficult. It also doesn't make much sense to use such tools with JS IMHO, that stuff is meant to be compiled into C and then into a binary. 11/27/2019, 7:33:35 PM - mebeim (Marco Bonelli): I've had a working Nearley implementation of the linter for ages now, it's just basically impossible to understand how to generate meaningful error messages. The documentation says nothing, concrete examples are hard to find and almost always unrelated. I mean, it's basically black magic to me. 11/27/2019, 7:35:56 PM - waldyrious (Waldir Pimenta): So the hold up at the moment is to make the Nearley implementation print out good error messages? 11/27/2019, 7:36:31 PM - waldyrious (Waldir Pimenta): Thanks for the link @sbrl, I'll take a look as soon as I get the chance! 11/27/2019, 7:41:15 PM - mebeim (Marco Bonelli): Yes @waldyrious 11/27/2019, 7:41:39 PM - waldyrious (Waldir Pimenta): Gotcha. That's useful to know so we can focus our efforts 11/27/2019, 7:41:54 PM - mebeim (Marco Bonelli): at least AFAIK for the time I've spent investigating this 11/27/2019, 7:49:27 PM - sbrl (Starbeamrainbowlabs): np, @waldyrious! 11/27/2019, 7:49:40 PM - sbrl (Starbeamrainbowlabs): Ah, I see @mebeim. Is that open-source? I might be able to take a look. 11/27/2019, 7:50:09 PM - sbrl (Starbeamrainbowlabs): I've got a bunch of compiler / parsing experience, apparently, so I'm happy to take a look. 11/27/2019, 8:00:31 PM - mebeim (Marco Bonelli): No it isn't but it's fairly trivial. You just need a grammar and the nearlycc to parse it into a JS file that recognizes it. I linked the grammar here a long time ago 11/27/2019, 8:01:11 PM - mebeim (Marco Bonelli): I remember I tweaked it a bit but anyway that's a starting point 11/27/2019, 8:01:22 PM - sbrl (Starbeamrainbowlabs): I see. If you can open-source that (under the tldr-pages org?) I can take a look if you like 11/27/2019, 8:01:53 PM - mebeim (Marco Bonelli): There's no point to open source it since it was just me playing around with random broken scripts, that's what I mean 11/27/2019, 8:02:02 PM - mebeim (Marco Bonelli): Nothing that can't be done in 5 minutes 11/27/2019, 8:02:02 PM - sbrl (Starbeamrainbowlabs): Ah, I see. 11/27/2019, 8:02:19 PM - mebeim (Marco Bonelli): Let me see if I find the original grammar 11/27/2019, 8:07:46 PM - mebeim (Marco Bonelli): Oh ok it's more than 5 minutes, but still messy 11/27/2019, 8:09:22 PM - mebeim (Marco Bonelli): [tldr-nearley-grammars.tar.gz](https://files.gitter.im/tldr-pages/tldr/dqWG/tldr-nearley-grammars.tar.gz) 11/27/2019, 8:10:15 PM - mebeim (Marco Bonelli): Here it is @sbrl, to turn that into a working JS script that recognizes the grammar you just need to `nearleyc grammar.ne -o parser.js` 11/27/2019, 8:15:57 PM - sbrl (Starbeamrainbowlabs): ty! I'll look when get home 11/27/2019, 8:16:11 PM - sbrl (Starbeamrainbowlabs): ...if I don't message by tomorrow, send me a reminder message 11/27/2019, 8:43:08 PM - agnivade (Agniva De Sarker): @pepa65 already has a linter for the new syntax. I think this comment https://github.com/tldr-pages/tldr/pull/958#issuecomment-357434969 summarizes the latest status. 11/27/2019, 8:51:20 PM - mebeim (Marco Bonelli): That's a bash script, I don't really think something like that is advisable. 11/27/2019, 8:51:40 PM - mebeim (Marco Bonelli): (this one for reference https://github.com/pepa65/tldr-bash-client/blob/master/tldr-lint) 11/27/2019, 9:30:05 PM - sbrl (Starbeamrainbowlabs): Wow, that's pretty impressive @pepa65. Still, I think I do agree that it needs to be easy to understand. The problem is that linting is an inherently complicated process, so it's difficult to write it in a way that's easy to understand and maintainable. 12/9/2019, 11:44:01 PM - sbrl (Starbeamrainbowlabs): ...that's a lot of PRs that have just been marked stale. 12/10/2019, 12:06:11 AM - mebeim (Marco Bonelli): Seems like december is a busy month for everyone, not just me :\ 12/10/2019, 12:06:39 AM - sbrl (Starbeamrainbowlabs): Yeah 12/10/2019, 12:06:52 AM - sbrl (Starbeamrainbowlabs): I think the stale bot was broken for a while, and now it's started working again 12/15/2019, 1:01:01 PM - mebeim (Marco Bonelli): Really like the new GitHub notifications page 12/15/2019, 4:15:33 PM - owenvoke (Owen Voke): Is it available? 🤔 I couldn't see it in the list of previews. 12/15/2019, 5:36:05 PM - sbrl (Starbeamrainbowlabs): I'm not seeing any drastic changes? 12/15/2019, 5:36:10 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/2hsa/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/2hsa/image.png) 12/15/2019, 5:36:18 PM - sbrl (Starbeamrainbowlabs): What are you seeing @mebeim 12/15/2019, 6:58:06 PM - owenvoke (Owen Voke): I think there was a change for people with the iOS beta app? 12/15/2019, 7:45:11 PM - mebeim (Marco Bonelli): oh, maybe they are rolling it out gradually 12/15/2019, 7:48:29 PM - sbrl (Starbeamrainbowlabs): That sounds logical for a site their size 12/15/2019, 7:49:49 PM - mebeim (Marco Bonelli): I saw this 12/15/2019, 7:49:50 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/awvp/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/awvp/image.png) 12/15/2019, 7:50:26 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/E6FI/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/E6FI/image.png) 12/15/2019, 7:50:28 PM - mebeim (Marco Bonelli): and then this 12/15/2019, 7:51:36 PM - mebeim (Marco Bonelli): now when you open a notification it doesn't navigate to the PR but it loads it in the same page 12/15/2019, 7:51:38 PM - mebeim (Marco Bonelli): [![image.png](https://files.gitter.im/tldr-pages/tldr/ROGb/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/ROGb/image.png) 12/15/2019, 8:00:27 PM - owenvoke (Owen Voke): That's way nicer 12/15/2019, 8:00:57 PM - owenvoke (Owen Voke): Kinda like Octobox. 12/15/2019, 8:06:15 PM - mebeim (Marco Bonelli): yea it's pretty cool 12/16/2019, 4:04:27 PM - waldyrious (Waldir Pimenta): It was announced recently on GitHub Universe: - https://github.blog/2019-11-13-universe-day-one/#notifications - https://help.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications-beta - https://www.youtube.com/watch?v=afcqKcs1zMo&t=13m37s 12/16/2019, 4:04:37 PM - waldyrious (Waldir Pimenta): Looking forward to try it out! 12/16/2019, 4:57:59 PM - sbrl (Starbeamrainbowlabs): Ah, nice @waldyrious! 12/16/2019, 4:58:10 PM - sbrl (Starbeamrainbowlabs): I don't follow GH universe, so cool to learn about that 12/16/2019, 5:13:06 PM - waldyrious (Waldir Pimenta): I don't either, but their videos kept popping up in my youtube recommendations 😛 12/16/2019, 5:19:09 PM - sbrl (Starbeamrainbowlabs): lol 12/16/2019, 5:35:44 PM - owenvoke (Owen Voke): I follow GitHub Universe, but forgot about that. 😋 12/17/2019, 2:38:02 PM - agnivade (Agniva De Sarker): Wow, really looking forward to it. My notifications went off the roof after I joined my new company 😛 Now I am part of 3 huge orgs, and not 2. I seriously need this. 12/17/2019, 2:38:18 PM - agnivade (Agniva De Sarker): @mebeim - Good to see you here https://twitter.com/MeBeiM/status/1206725299108495366 :) 12/17/2019, 5:31:10 PM - mebeim (Marco Bonelli): @agnivade ahaha, that just made me realize that in Go every single function has a stack size check in the prologue with a call to a funcion `morestack` that remaps the stack if it's too small and updates every single pointer... insane LOL https://golang.org/src/runtime/stack.go insane 12/17/2019, 5:34:53 PM - sbrl (Starbeamrainbowlabs): Wow, Go really does that? I read it as C code and got confused 12/17/2019, 5:49:48 PM - mebeim (Marco Bonelli): Yes it does... 12/17/2019, 5:50:30 PM - mebeim (Marco Bonelli): It also always needs debugging information in the binary to be able to do this and other introspection stuff like reflections. A Go binary without debugging info basically doesn't run LOL 12/17/2019, 5:52:58 PM - sbrl (Starbeamrainbowlabs): That's.... wow. 12/17/2019, 5:53:06 PM - sbrl (Starbeamrainbowlabs): No stripping Go binaries here then 12/17/2019, 5:53:13 PM - sbrl (Starbeamrainbowlabs): I've been learning Rust myself 12/17/2019, 10:39:32 PM - agnivade (Agniva De Sarker): That is incorrect. You can build a Go binary without debugging info and it runs just fine. 12/17/2019, 10:40:29 PM - agnivade (Agniva De Sarker): The DWARF info is needed when you want to debug stack traces, or heap profiles. Which won't be there if you turn off debugging symbols. Otherwise, the binary can run just fine. 12/17/2019, 10:43:15 PM - agnivade (Agniva De Sarker): And just to circle back on the stack growth, Go does this because of mainly two reasons - 1. The intial stack size is much smaller than a thread stack. 2KB compared to 8KB, which makes them much lighter than threads. 2. The Go spec does not specify whether a variable will get allocated on stack or on heap. The compiler does something called "escape analysis" to determine whether the variable "escapes" the current call frame, and if it does, it allocates on the heap, otherwise it allocates on stack. Hence, the need to grow stacks when needed. 12/17/2019, 10:53:37 PM - mebeim (Marco Bonelli): @agnivade true about the DWARF & symbols 12/17/2019, 10:53:46 PM - mebeim (Marco Bonelli): nonetheless, go binaries still have hidden debug info 12/17/2019, 10:53:54 PM - mebeim (Marco Bonelli): in the RODATA section 12/17/2019, 10:53:59 PM - mebeim (Marco Bonelli): that cannot be stripped 12/17/2019, 10:54:58 PM - mebeim (Marco Bonelli): probably I shouldn't call it "debug info" because it is not intended as being used for debugging purposes, bit it's there nonetheless, you can still know the names of all functions, types, and other stuff used inside a program even if it's stripped 12/17/2019, 10:58:07 PM - mebeim (Marco Bonelli): @agnivade as per the escape analysis I know about that but aren't statically allocated variables still known at compile time? I don't see an obvious reason why you would need to move the stack around dynamically at runtime, if you have any link that talks about this that would be an intesting read 12/18/2019, 12:27:21 AM - agnivade (Agniva De Sarker): Yes, that info is there. You can trim some of it using `-trimpath` now. But the primary stuff will be there. 12/18/2019, 12:38:42 AM - agnivade (Agniva De Sarker): Re: escaping, I think you may be right. I guess this may be because it is just hard to analyse the code and insert the right stack allocation amount in the call frames. There might be weird edge cases around it. I am not 100% sure though. There are more knowledgable folks who have much more expertise on these matters. Feel free to join the #performance channel on Gophers slack if you want to ask such questions. 12/18/2019, 1:57:41 AM - mebeim (Marco Bonelli): it was just curiosity, I already know a couple of people I could ask 12/24/2019, 9:35:59 PM - waldyrious (Waldir Pimenta): Whoof! I **finally** cleared up all the notifications from the threads I was mentioned or had otherwise participated in 😃 12/24/2019, 9:36:26 PM - waldyrious (Waldir Pimenta): I need to take vacations more often 😛 in two days I cleared up so much old stuff! 12/24/2019, 9:36:53 PM - waldyrious (Waldir Pimenta): (Thanks to @zdroid for digging through old issues btw 😃) 12/24/2019, 10:32:36 PM - sbrl (Starbeamrainbowlabs): Congrats @waldyrious! 12/24/2019, 10:32:54 PM - sbrl (Starbeamrainbowlabs): Oh my, I need to clear mine out too 12/24/2019, 10:33:06 PM - sbrl (Starbeamrainbowlabs): Unread 48 lol 12/24/2019, 11:04:42 PM - agnivade (Agniva De Sarker): Awesome :) 12/24/2019, 11:48:26 PM - sbrl (Starbeamrainbowlabs): @zdroid is gaining on me in my notifications list lol 12/28/2019, 5:26:46 AM - sbrl (Starbeamrainbowlabs): I've renamed the `hacktoberfest` label back to `help wanted`, since we appear to have forgotten after all the business of October lol 😛 12/28/2019, 5:50:36 AM - owenvoke (Owen Voke): :+1: 12/28/2019, 6:39:29 AM - waldyrious (Waldir Pimenta): I actually think we should not rename the labels anymore 12/28/2019, 6:39:36 AM - waldyrious (Waldir Pimenta): We already have one for GCI 12/28/2019, 6:40:13 AM - waldyrious (Waldir Pimenta): and I tagged various PRs that I was involved that I know were created specifically in the context of Hacktoberfest 12/28/2019, 6:41:03 AM - waldyrious (Waldir Pimenta): So we might want to split the labeled issues and PRs into those that are hacktoberfest related (mostly those created during the month of october) and those that are generic "help wanted" issues 12/28/2019, 6:41:25 AM - waldyrious (Waldir Pimenta): Otherwise it's just going to become confusing over time 12/28/2019, 4:46:08 PM - sbrl (Starbeamrainbowlabs): Hrm, true 12/28/2019, 4:46:51 PM - sbrl (Starbeamrainbowlabs): At the same time, some of the existing issues with this label were created when it wasn't hacktoberfest, so it's already confused to an extent 12/28/2019, 9:06:08 PM - waldyrious (Waldir Pimenta): Exactly. We need to untangle it. 12/28/2019, 9:10:11 PM - sbrl (Starbeamrainbowlabs): lol , yeah 12/28/2019, 9:11:31 PM - waldyrious (Waldir Pimenta): Maybe we should create an issue to track doing that, because I won't be able to work on it immediately and I don't want that to be dropped, WDYT? 12/28/2019, 11:02:47 PM - sbrl (Starbeamrainbowlabs): Good idea! 12/29/2019, 2:20:34 AM - waldyrious (Waldir Pimenta): @sbrl https://github.com/tldr-pages/tldr/issues/3706 12/29/2019, 3:25:55 AM - sbrl (Starbeamrainbowlabs): :+1: 1/4/2020, 12:16:16 PM - agnivade (Agniva De Sarker): @zdroid - Great work on following up on old issues. Much appreciated ! I just wanted to mention that it may be worthwhile to slow down a bit, and not be too eager to close the issues :) Perhaps just gently nudge the issue asking for an update, rather than directly push for closing it. 1/14/2023, 3:38:06 PM - ivanhercaz (Iván Hernández Cazorla) joined the room 1/6/2020, 6:03:34 AM - ivanhercaz (Iván Hernández Cazorla): Hi everyone! 1/6/2020, 6:03:55 AM - ivanhercaz (Iván Hernández Cazorla): Nice to regard you here 😊 1/6/2020, 6:05:10 AM - ivanhercaz (Iván Hernández Cazorla): I usually don't use chats, but I will try to visit this one periodically. 1/6/2020, 6:07:40 AM - ivanhercaz (Iván Hernández Cazorla): Has this chat a matrix link to a Telegram group? I admit that it would be really useful (at least for me hehe). 1/6/2020, 6:19:02 AM - sbrl (Starbeamrainbowlabs): Hey there, @ivanhercaz! 1/6/2020, 6:19:16 AM - sbrl (Starbeamrainbowlabs): I don't think we have any links to other platforms yet. 1/6/2020, 6:19:31 AM - sbrl (Starbeamrainbowlabs): Personally I keep this open in a pinned tab in Firefox 1/6/2020, 6:19:47 AM - sbrl (Starbeamrainbowlabs): If you need to get a hold of me, this is actually the best way to do so 1/6/2020, 6:20:10 AM - sbrl (Starbeamrainbowlabs): Since I usually see things on here before I even check my GitHub notifications 1/6/2020, 8:44:06 PM - ivanhercaz (Iván Hernández Cazorla): Hi @sbrl! 1/6/2020, 8:44:07 PM - ivanhercaz (Iván Hernández Cazorla): Thank you for the information. 1/6/2020, 8:44:19 PM - sbrl (Starbeamrainbowlabs): np :-) 1/6/2020, 8:44:44 PM - ivanhercaz (Iván Hernández Cazorla): I allow to Gitter to send me notifications, so I hope to see them usually hehe. 1/6/2020, 8:45:09 PM - sbrl (Starbeamrainbowlabs): cool 1/6/2020, 8:49:50 PM - ivanhercaz (Iván Hernández Cazorla): Well, to avoid to forget notifications I have install Gitter Notifier in Brave. I am going to test it. 1/6/2020, 9:34:30 PM - sbrl (Starbeamrainbowlabs): @agnivade: I'm not sure that @zdroid is on Gitter. Might be worth reaching out via another method. 1/6/2020, 11:10:41 PM - agnivade (Agniva De Sarker): Hmm .. yea figured. 1/14/2023, 3:38:13 PM - kosmgco (ooops) joined the room 1/8/2020, 9:35:59 AM - kosmgco (ooops): hello, I make a tldr web client based on Golang and Vue.js, some proposals? 😊https://tldr.ooops.me 1/8/2020, 9:58:44 AM - mebeim (Marco Bonelli): @kosmgco that's pretty cool! We can add that to the list of clients in our repository if you want and plan to keep it up. If you're looking for suggestions I'd say right off the bat that the website probably needs to be more mobile friendly (the heading text seems to be overlapping on my phone: https://imgur.com/a/MROdFr7). 1/8/2020, 10:04:35 AM - kosmgco (ooops): @mebeim yeah. I will keep up and make a mobile version later. 1/8/2020, 1:44:50 PM - kosmgco (ooops): @mebeim The website has been updated. For mobile compatible. 1/8/2020, 5:11:52 PM - sbrl (Starbeamrainbowlabs): Nice one, @kosmgco! 1/8/2020, 5:12:05 PM - sbrl (Starbeamrainbowlabs): How about open a PR to add it to the list of clients in the README? 1/8/2020, 5:12:42 PM - sbrl (Starbeamrainbowlabs): Also, if you haven't checked out the client spec yet, it's designed to help implementers like yourself :-) 1/8/2020, 5:12:49 PM - sbrl (Starbeamrainbowlabs): https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md 1/8/2020, 6:03:10 PM - kosmgco (ooops): Yes, already made a PR at https://github.com/tldr-pages/tldr/pull/3740 1/9/2020, 2:11:34 AM - sbrl (Starbeamrainbowlabs): 😃 1/14/2023, 3:38:18 PM - debek (Daniel Debny) joined the room 1/10/2020, 4:44:03 PM - debek (Daniel Debny): Hi! I want to add to TLDR my private pages. Do you know how is it possible? 1/10/2020, 7:23:05 PM - sbrl (Starbeamrainbowlabs): Hey, @debek! That depends on support for such a feature from clients. 1/10/2020, 7:23:40 PM - sbrl (Starbeamrainbowlabs): The official tldr client specification doesn't specify anything about private pages, so it's up to individual clients to implement that feature. 1/10/2020, 7:24:13 PM - sbrl (Starbeamrainbowlabs): If you have any pages you're willing to contribute publicly, please do open a PR :-) 1/10/2020, 7:46:25 PM - debek (Daniel Debny): Ok 😟 So i will use eg or cheat 😕 1/10/2020, 7:47:52 PM - debek (Daniel Debny): I want to use it to private project for my coworkers. And do not public it. 1/10/2020, 7:50:09 PM - sbrl (Starbeamrainbowlabs): Ah, I see! You could always change the URL of the repo in the settings of the Node client IIRC 1/10/2020, 7:50:23 PM - sbrl (Starbeamrainbowlabs): then it would request pages from your private repo 1/10/2020, 7:50:30 PM - sbrl (Starbeamrainbowlabs): but not the actual official repo 1/10/2020, 7:50:34 PM - sbrl (Starbeamrainbowlabs): @debek 1/15/2020, 9:09:25 PM - mebeim (Marco Bonelli): I think #3755 might require some attention @waldyrious @sbrl @agnivade @pxgamer 1/15/2020, 10:13:52 PM - owenvoke (Owen Voke): Taking a look :+1: 1/16/2020, 12:52:16 AM - sbrl (Starbeamrainbowlabs): Ok, taking a look @mebeim 1/16/2020, 12:53:59 AM - sbrl (Starbeamrainbowlabs): Sees the beginning of the PR: Huh, this looks fine Gets 1/2 way down: Uh oh, this doesn't look good 1/16/2020, 12:54:13 AM - sbrl (Starbeamrainbowlabs): /cc @waldyrious on this one, though I'm going to continue reading 1/16/2020, 12:56:32 AM - sbrl (Starbeamrainbowlabs): Oof, it sounds like the OP there was pretty unfair 1/16/2020, 12:57:54 AM - sbrl (Starbeamrainbowlabs): That was a great response you gave there I think @mebeim 1/16/2020, 12:58:05 AM - sbrl (Starbeamrainbowlabs): Also, I think we should encourage @zdroid to join us here on Gitter 1/16/2020, 2:03:33 AM - mebeim (Marco Bonelli): Ah.. I thought that actually was a requirement to be a member, as the invitation message states: *"If you accept the invitation, we ask you to make your membership public, and (in case you don't already) start hanging out in our Gitter chat room. [...]"* (from the `COMMUNITY-ROLES.md` file). 1/16/2020, 2:06:14 AM - sbrl (Starbeamrainbowlabs): Huh, I completely forgot about that. 1/16/2020, 2:06:52 AM - sbrl (Starbeamrainbowlabs): Perhaps we could comment on their original issue that invited them to be an org member? 1/16/2020, 2:07:49 AM - mebeim (Marco Bonelli): Well it is unclear whether that is a strict requirement or not. Perhaps it should be made clearer... but sure, commenting on the issue makes sense. 1/16/2020, 2:09:57 AM - sbrl (Starbeamrainbowlabs): We can always ask them nicely to hang out here first 😛 1/16/2020, 2:10:32 AM - mebeim (Marco Bonelli): Of course, that's what I meant with "commenting on the issue" 1/16/2020, 2:10:59 AM - mebeim (Marco Bonelli): There's a good chance he didn't even acknowledge that 1/16/2020, 2:13:03 AM - sbrl (Starbeamrainbowlabs): Yeah 1/16/2020, 9:09:22 AM - ivanhercaz (Iván Hernández Cazorla): Hi everyone! I just created something in which I have been thinking since some time ago: a tldr-pages data repository to analyze some data. What I created it's very basic and it might be improved in different ways. But I hope to work bit by bit in this aside-project. https://github.com/ivanhercaz/tldr-pages-data/tree/master 1/16/2020, 9:10:11 AM - ivanhercaz (Iván Hernández Cazorla): If you consider this repository could be part of the organization repositories, for me it would be a pleasure. If not, I will continue working there. 1/16/2020, 11:49:48 PM - sbrl (Starbeamrainbowlabs): Nice! 1/16/2020, 11:50:27 PM - sbrl (Starbeamrainbowlabs): Do you have a screenshot or instructions on how to use a juptyer notebook? 1/16/2020, 11:50:41 PM - sbrl (Starbeamrainbowlabs): I've seen them before, but have no idea of how to use them 1/16/2020, 11:50:49 PM - sbrl (Starbeamrainbowlabs): @ivanhercaz 1/17/2020, 3:07:50 AM - ivanhercaz (Iván Hernández Cazorla): Hi @sbrl! 1/17/2020, 3:08:04 AM - sbrl (Starbeamrainbowlabs): Heya! 1/17/2020, 3:08:22 AM - ivanhercaz (Iván Hernández Cazorla): This might be useful for you: https://www.dataquest.io/blog/jupyter-notebook-tutorial/ 1/17/2020, 3:09:05 AM - ivanhercaz (Iván Hernández Cazorla): But for the case of the notebook in tldr-pages-data, you can test yourself with Binder. 1/17/2020, 3:09:16 AM - ivanhercaz (Iván Hernández Cazorla): Have you view the notebook on nbviewer? 1/17/2020, 3:09:36 AM - sbrl (Starbeamrainbowlabs): I'm not aware of what nbviewer is 1/17/2020, 3:09:47 AM - sbrl (Starbeamrainbowlabs): thanks for the link - I'll give it a read 1/17/2020, 3:10:32 AM - ivanhercaz (Iván Hernández Cazorla): In the section "Notebook" in the README, you have two links, one to see the notebook in GitHub (GitHub render the notebook from the .ipynb file). 1/17/2020, 3:11:34 AM - ivanhercaz (Iván Hernández Cazorla): And another link to see this notebook on nbviewer, a viewer for Jupyter notebooks, that already has links to another tools like Binder, in which you can test by yourself the notebooks. This is the link to what I refer: https://nbviewer.jupyter.org/github/ivanhercaz/tldr-pages-data/blob/master/tldr-pages_data.ipynb 1/17/2020, 3:12:56 AM - ivanhercaz (Iván Hernández Cazorla): nbviewer = non-interactive views of notebooks Binder = interactive notebooks (like edit them in the Jupyter interface) 1/17/2020, 3:18:32 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl, this is the Binder link: https://hub.gke.mybinder.org/user/ivanhercaz-tldr-pages-data-n9w0a4q6/notebooks/tldr-pages_data.ipynb 1/17/2020, 3:19:38 AM - ivanhercaz (Iván Hernández Cazorla): There you can test the cells, execute them and change what you want. Execute cell by cell might be an easy way to understand Jupyter notebooks. 1/17/2020, 3:20:20 AM - ivanhercaz (Iván Hernández Cazorla): If anyone has any recommendation or whatever, feel free to open an issue! 1/17/2020, 3:20:38 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I spotteed neither of those links lol 1/18/2020, 4:28:09 AM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/BDog/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/BDog/image.png) 1/18/2020, 4:28:27 AM - sbrl (Starbeamrainbowlabs): Looks like we recently exceeded 1K common pages! 1/18/2020, 5:27:58 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl :applause: :applause:! 1/18/2020, 5:29:59 AM - sbrl (Starbeamrainbowlabs): 😃 1/18/2020, 5:30:12 AM - sbrl (Starbeamrainbowlabs): Thanks to everyone who's contributed 1/18/2020, 5:31:48 AM - ivanhercaz (Iván Hernández Cazorla): Yeah! 1/18/2020, 5:31:51 AM - mebeim (Marco Bonelli): 🎉 🎉 🎉 1/18/2020, 5:32:51 AM - ivanhercaz (Iván Hernández Cazorla): Tonight I was resting a bit of the master course tasks and of working and I translated to Spanish a bunch of git pages 1/18/2020, 5:35:57 AM - ivanhercaz (Iván Hernández Cazorla): Thera are already 34 pages about git commands translated in #3727. I hope to finish tomorrow. 1/18/2020, 5:38:22 AM - mebeim (Marco Bonelli): Take your time, there's no rush. 1/18/2020, 5:39:09 AM - ivanhercaz (Iván Hernández Cazorla): No, of course. But I approach this to relax with a cup of coffee or tea between task and tasks hehe. 1/19/2020, 8:15:00 PM - sbrl (Starbeamrainbowlabs): Looks like there's a new GitHub Android app in beta! 1/19/2020, 8:15:04 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/tldr-pages/tldr/nx0R/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/nx0R/image.png) 1/19/2020, 8:15:11 PM - sbrl (Starbeamrainbowlabs): Sadly they are maxed out on testers atm 1/19/2020, 9:06:23 PM - mebeim (Marco Bonelli): Yeah I've been on the iOS app as beta tester for a while 1/19/2020, 9:06:51 PM - mebeim (Marco Bonelli): They're finally working on official apps. Still a lot of work to do, but they are getting there... 1/19/2020, 9:11:06 PM - owenvoke (Owen Voke): I'm using the Android beta at the moment. It's quite nice, but it seems that quite a few pages don't open in the app, they just open in a browser within the app. Seems good so far though. :+1: 1/19/2020, 9:23:00 PM - sbrl (Starbeamrainbowlabs): Cool! I wish I was fast enough to grab a closed beta test of the app lol 1/19/2020, 11:18:49 PM - owenvoke (Owen Voke): Could probably send the APK anyway. Hopefully the beta won't be too long, unlike the label descriptions API beta... 1/19/2020, 11:25:11 PM - sbrl (Starbeamrainbowlabs): That'd be cool, if you could! 1/19/2020, 11:55:46 PM - owenvoke (Owen Voke): I've got the APKs from my phone, but looks like they're split. Not sure how you install multiple APKs. 1/19/2020, 11:58:46 PM - sbrl (Starbeamrainbowlabs): Huh, that's odd 1/20/2020, 12:04:24 AM - owenvoke (Owen Voke): I think you can with ADB, but not sure. 1/20/2020, 12:05:43 AM - sbrl (Starbeamrainbowlabs): I'm somewhat baffled by the fact that it's distributed as multiple APKs in the first place 1/20/2020, 12:05:49 AM - sbrl (Starbeamrainbowlabs): that's a thing you can do? 1/20/2020, 12:07:15 AM - mebeim (Marco Bonelli): https://developer.android.com/google/play/publishing/multiple-apks 1/20/2020, 12:07:47 AM - mebeim (Marco Bonelli): That's probably just a question of picking the right one 1/20/2020, 12:21:18 AM - owenvoke (Owen Voke): Well, there is one called `base.apk`, so I'd assume that's the main one? 1/20/2020, 12:21:59 AM - owenvoke (Owen Voke): I can zip them and send them to you on Keybase if you want @sbrl? 1/20/2020, 1:19:22 AM - sbrl (Starbeamrainbowlabs): Can do, @pxgamer! I'll take a look. See also: send.firefox.com 1/20/2020, 2:22:05 AM - owenvoke (Owen Voke): Ah, always forget about FF Send 1/20/2020, 2:46:54 AM - sbrl (Starbeamrainbowlabs): Got it - thanks! 1/20/2020, 2:47:11 AM - sbrl (Starbeamrainbowlabs): Looks like 2 of them do config, and the other one is the app itself 1/20/2020, 2:49:33 AM - owenvoke (Owen Voke): :+1: Not sure what the config stuff is. But hopefully the app installs ok. 1/20/2020, 3:12:19 AM - sbrl (Starbeamrainbowlabs): yeah! 1/20/2020, 3:15:14 AM - sbrl (Starbeamrainbowlabs): "There was a problem while parsing the package" for the config ones 1/20/2020, 3:15:31 AM - sbrl (Starbeamrainbowlabs): and "app not installed" for the base 1/20/2020, 3:15:35 AM - sbrl (Starbeamrainbowlabs): worth a try at least 1/20/2020, 3:41:50 AM - owenvoke (Owen Voke): Eh; Sorry about that. Worth a try indeed. 1/20/2020, 4:21:19 AM - sbrl (Starbeamrainbowlabs): np! 1/21/2020, 1:32:05 PM - agnivade (Agniva De Sarker): Thanks for jumping in on #3755 @mebeim. I was on vacation and just got back. 1/21/2020, 1:37:30 PM - agnivade (Agniva De Sarker): I think your initial PR review was absolutely fine. It's just that our review process is indeed tiring to a lot of people. Mostly because it's just a bunch of text, and not code per-se. So folks don't take stuff that seriously. But IMO, things like "reordering" and "adding an example" are very important things, and what makes tldr pages stand out from the crowd. 1/21/2020, 2:49:25 PM - mebeim (Marco Bonelli): @agnivade 👍 1/21/2020, 5:46:00 PM - sbrl (Starbeamrainbowlabs): :+1: 1/22/2020, 2:23:00 AM - mebeim (Marco Bonelli): Guys please pay attention when reviewing. I'm noticing very poorly reviewed PRs lately: see https://github.com/tldr-pages/tldr/pull/3770 and https://github.com/tldr-pages/tldr/pull/3771 for example. 1/22/2020, 2:24:22 AM - mebeim (Marco Bonelli): Both add phrases that are barely correct English and have very awkward wording. On top of that, #3770 transforms on example into another, which shouldn't be done like that, and it doesn't seem to have been noticed... :\ 1/22/2020, 2:26:26 AM - mebeim (Marco Bonelli): Please pay more attention when reviewing. You should take your time, there's no hurry, and if you don't have time don't rush a review, you can look at it later. 1/22/2020, 2:27:18 AM - mebeim (Marco Bonelli): Also, @sbrl did you ping @zdroid on GitHub about getting here on Gitter? I don't remember. 1/22/2020, 3:09:18 AM - sbrl (Starbeamrainbowlabs): Hey, @mebeim! I don't think I've reviewed those PRs yet. 1/22/2020, 3:09:24 AM - sbrl (Starbeamrainbowlabs): No I didn't I'll do it now. 1/22/2020, 3:11:25 AM - mebeim (Marco Bonelli): #3771 is probaly ok as is, I did the last review. #3770 needs to be clarified though, we should make sure why was the example removed and also correct the english on the added examples 1/22/2020, 3:14:54 AM - sbrl (Starbeamrainbowlabs): Posted message. Link: https://github.com/tldr-pages/tldr/issues/3663#issuecomment-576896934 1/22/2020, 3:16:01 AM - mebeim (Marco Bonelli): :+1: 1/22/2020, 4:03:49 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): > @zdroid is gaining on me in my notifications list lol what did you mean by this? 1/22/2020, 4:03:52 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl 1/22/2020, 4:11:29 AM - mebeim (Marco Bonelli): Not much, just that @sbrl had a significant number of notifications from you on GH :) 1/22/2020, 4:19:31 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It's two-sided, @sbrl spams my notifications as well 😛 1/22/2020, 4:21:59 AM - mebeim (Marco Bonelli): By the way, haven't had a chance to say it, but thanks for all the PRs/Issues you took time to open/review/comment on lately. Nice job @zdroid :) 1/22/2020, 4:32:01 AM - schneiderl (Lucas Gabriel Schneider): @zdroid Hi, About #3773, I'm unsure I understood the problem here. As far as I understood, Serbian is a language used by Serbs, while Croatian is used in Croatia, Bosnia and Herzegovina, etc. Serbo-Croatian is the language that they derive from. Are Serbian and Croatian that different from Serbo-Croatian? and from each other? 1/22/2020, 4:33:15 AM - schneiderl (Lucas Gabriel Schneider): Also, ISO639-2 does not seem to include anything like Serbo-Croatian, which lead me to think we should label as Serbian and Croatian. 1/22/2020, 4:35:26 AM - sbrl (Starbeamrainbowlabs): Hey there, @zdroid! I just meant that I had a lot of GH notifications from you - and since I like to sit down and deal with all my notifications at once, when we are on GH at the same time I end up not getting to the end of the list 😛 1/22/2020, 4:42:34 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl Same problem here, whenever I refresh the page another one appears 😃 @mebeim thanks 1/22/2020, 4:42:53 AM - sbrl (Starbeamrainbowlabs): Lol 😛 1/22/2020, 4:42:55 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @schneiderl It's more of a political issue 1/22/2020, 4:43:39 AM - sbrl (Starbeamrainbowlabs): Also, just a quick note: Since I hang out in here regularly @zdroid I won't always have seen / reviewed PRs recently-ish 1/22/2020, 4:43:56 AM - sbrl (Starbeamrainbowlabs): If there's something urgent you're welcome to bring it to my attention here 1/22/2020, 4:44:09 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Standard varieties of Serbian/Croatian/Bosnian have been united throughout Yugoslavia's existence, but they were split in 90s and 00s 1/22/2020, 4:44:22 AM - sbrl (Starbeamrainbowlabs): But right now I've had a busy and I'm just chilling for a it - I'll prob. get to GH some time tomorrow 1/22/2020, 6:53:19 AM - ivanhercaz (Iván Hernández Cazorla): @mebeim Excuse me a lot! Fast reviews. I will be more cautious before to review and approve them. 1/22/2020, 6:54:26 AM - mebeim (Marco Bonelli): @ivanhercaz it's ok, it can happen :) and thank you 1/22/2020, 7:08:36 AM - ivanhercaz (Iván Hernández Cazorla): @mebeim Then I read the another reviews and note my fault of appreciation. I must think more before to review. I try to do it in my free time, but sometimes in the bus or waiting for something, I rush erroneously. 1/22/2020, 3:59:43 PM - mebeim (Marco Bonelli): Yeah there's no rush, you can always get back at it later :) 1/23/2020, 9:33:59 AM - agnivade (Agniva De Sarker): Hello @zdroid - regarding https://github.com/tldr-pages/tldr/issues/3782#issuecomment-577440868, we had decided not to immediately close issues by ourselves and let the contributor come back and close it by themselves. If they don't respond by a week or so, it is okay to close it by ourselves. 1/23/2020, 3:48:50 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I understood that, but it was a quite simple request after all 1/23/2020, 3:49:05 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): dpkg page already exists 1/24/2020, 12:22:24 AM - sbrl (Starbeamrainbowlabs): True, but it's about the contributor's experience I think is what @agnivade is trying to get at @zdroid - even if it's obvious to us at the time that it needs to be closed 1/24/2020, 12:32:07 AM - agnivade (Agniva De Sarker): Yes, correct. Even if it's dead simple and should absolutely be closed. For example client related bugs. Even then, we should let the author close it rather than closing it ourselves. This is just to be extra polite and be welcoming as a community. 1/24/2020, 12:32:21 AM - agnivade (Agniva De Sarker): FWIW, it was @waldyrious who came up with this idea. Not me :) 1/24/2020, 12:52:08 AM - sbrl (Starbeamrainbowlabs): :+1: 1/24/2020, 1:36:54 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Alright. Btw, @sbrl check https://github.com/tldr-pages/tldr/issues/3773 again 1/24/2020, 8:02:39 AM - schneiderl (Lucas Gabriel Schneider): [![image.png](https://files.gitter.im/tldr-pages/tldr/gAIC/thumb/image.png)](https://files.gitter.im/tldr-pages/tldr/gAIC/image.png) 1/24/2020, 8:03:51 AM - schneiderl (Lucas Gabriel Schneider): Hi, Any idea where all this unusual traffic is coming from? 1/24/2020, 10:13:51 AM - mebeim (Marco Bonelli): might be somebody writing an article about us or sharing a link? 1/24/2020, 12:02:08 PM - agnivade (Agniva De Sarker): Referrers say tldr.sh and github.com. I guess somebody linked to tldr.sh 1/24/2020, 11:17:34 PM - sbrl (Starbeamrainbowlabs): That's a pretty huge traffic spike. 1/24/2020, 11:18:16 PM - sbrl (Starbeamrainbowlabs): Do we have analytics on tldr.sh or something? 1/24/2020, 11:18:21 PM - sbrl (Starbeamrainbowlabs): I'm really curious now 1/14/2023, 3:39:12 PM - tgolightly (Mr_____T) joined the room 1/25/2020, 12:01:10 AM - tgolightly (Mr_____T): Hello new here just installed tldr snap and tldr-luk3yx. tldr page returns an nfs generatesystemkey error then updating cache message and w/o end sits cntrl c to exit. tldr-luk3yx works fine. Linux Mint 19.3. 1/25/2020, 12:31:36 AM - sbrl (Starbeamrainbowlabs): Hey, @tgolightly! The snap package is rather out of date. It's actually backed by the node client. Perhaps you could try uninstalling the snap package and installing the regular node client (`sudo npm install --global tldr` on Linux + macOS; drop the `sudo` on windows) 1/25/2020, 12:31:59 AM - sbrl (Starbeamrainbowlabs): @agnivade: Perhaps we should consider unpublishing the tldr snap package if it's outdated. 1/25/2020, 12:32:14 AM - sbrl (Starbeamrainbowlabs): I've seen a number of queries about it recently 1/25/2020, 3:22:47 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): We do have GA for tldr.github.io 1/25/2020, 3:22:56 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Someone should check it, as I don't know who has the access 1/25/2020, 3:23:15 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): > We do have GA for tldr.github.io (Google Analytics) @sbrl 1/25/2020, 3:24:56 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): There has also been a spike in recent stars, from ~24.3k to the current 25.4k 1/25/2020, 3:26:46 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): ![trending](https://i.imgur.com/Xc7tKsg.png) 1/25/2020, 3:52:56 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Okay this is where all of it is coming from 😃 https://news.ycombinator.com/item?id=22117237 1/25/2020, 3:55:20 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): This is recent too https://www.tecmint.com/tldr-easy-to-understand-linux-man-pages/ 1/25/2020, 3:55:27 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): and https://www.reddit.com/r/linux/comments/ese2dt/tldr_pages_simplified_communitydriven_man_pages/ 1/25/2020, 4:36:11 AM - sbrl (Starbeamrainbowlabs): Ah, nice! I wonder who has access to that then. Nice work, @zdroid! 1/25/2020, 4:37:05 AM - sbrl (Starbeamrainbowlabs): In the tecmint article: > you need to install one of the supported clients called Node.js * cringes at the wording * 1/25/2020, 4:37:29 AM - sbrl (Starbeamrainbowlabs): Also, that tecmint article may be where we're seeing those people trying the snap package and experiencing issues 1/25/2020, 4:38:21 AM - sbrl (Starbeamrainbowlabs): I'll try and reach out to tecmint about that 1/25/2020, 4:47:37 AM - sbrl (Starbeamrainbowlabs): Also, the top comment there on the ycombinator site appears to point to http://cht.sh, which appears to take pages from tldr-pages too 1/25/2020, 4:47:54 AM - sbrl (Starbeamrainbowlabs): Which is interesting 1/25/2020, 4:48:03 AM - sbrl (Starbeamrainbowlabs): Though it does credit us, which is nice 1/25/2020, 5:05:57 AM - tgolightly (Mr_____T): Wow all there responses. Great! However, I checked and just to run tldr I have to install all node.js packages. Not that I don't have the disk space. I do. What can be said for tldr-luk3yx. I ran is with lsof and it stopped at line 12/37 and no more. Just wanted to see if there was a quick way to check it out w/o adding alot more files that will otherwise not be used. tx 1/25/2020, 5:08:22 AM - sbrl (Starbeamrainbowlabs): Ah, I see @tgolightly. I'm pretty sure that the snap package will install all those things anyway (and if you're running low on disk space, you'll probably have a better time with apt instead as it's more disk space efficient) - but there are lots of other clients to try: https://github.com/tldr-pages/tldr#clients For example, you could try the Python client: `sudo pip3 install tldr` 1/25/2020, 5:09:53 AM - tgolightly (Mr_____T): @sbrl Yeah I'll pip3 it! 1/25/2020, 5:10:02 AM - sbrl (Starbeamrainbowlabs): 😃 1/25/2020, 5:10:30 AM - sbrl (Starbeamrainbowlabs): The great thing about having an open client ecosystem like we do is that if 1 client doesn't work, there are loads more you can try 😃 1/25/2020, 5:13:05 AM - tgolightly (Mr_____T): @sbrl Absitively, posilutely! 1/25/2020, 11:24:28 AM - agnivade (Agniva De Sarker): I wonder if unpublishing things would break more stuff. 1/25/2020, 11:24:42 AM - agnivade (Agniva De Sarker): I would just put the notice more prominently that it is broken and not to be used. 1/25/2020, 5:17:20 PM - sbrl (Starbeamrainbowlabs): Yeah, that's perhaps the best solution @agnivade 1/25/2020, 6:05:08 PM - ivanhercaz (Iván Hernández Cazorla): @agnivade totally agree. 1/25/2020, 8:46:00 PM - sbrl (Starbeamrainbowlabs): OpenRC pages are now a thing in #3800 😃 1/25/2020, 8:54:09 PM - ivanhercaz (Iván Hernández Cazorla): @sbrl Approved! 1/25/2020, 8:54:24 PM - sbrl (Starbeamrainbowlabs): Oh wow thanks @ivanhercaz! 1/25/2020, 8:54:46 PM - sbrl (Starbeamrainbowlabs): I wasn't expecting an approval with so many pages lol 1/26/2020, 9:06:18 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Look at this: https://isitmaintained.com/project/tldr-pages/tldr 1/26/2020, 9:06:44 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): As I've been saying, we could improve this by a lot 😛 1/26/2020, 9:28:16 PM - psibi (Sibi Prabakaran): New release of the Haskell client for tldr. Nothing major apart from the fact that you can download binaries now from now onwards: https://github.com/psibi/tldr-hs/releases 1/26/2020, 9:29:23 PM - mebeim (Marco Bonelli): @zdroid the problem is unsolvable, as it stands there are issues that are basically impossible to solve lol 1/26/2020, 9:29:44 PM - mebeim (Marco Bonelli): and others that are there just for discussion 1/26/2020, 9:30:01 PM - mebeim (Marco Bonelli): the "20d issue resolution date" is a pretty bad metric for a repo if issues are used like this, doesn't mean anything really 1/26/2020, 9:30:33 PM - mebeim (Marco Bonelli): it's not an indicator of how good/maintained the repo is 1/26/2020, 10:27:59 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): > New release of the Haskell client for tldr. Nothing major apart from the fact that you can download binaries now from now onwards: https://github.com/psibi/tldr-hs/releases Nice to see an active client, keep up the good work 😃 1/26/2020, 10:28:55 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @agnivade I agree with you a little bit, but if we don't implement a way to resolve them, over the years the project will be left with hundreds of never resolved issues 1/26/2020, 10:33:45 PM - mebeim (Marco Bonelli): if an issue is meant to represent a problem to resolve, then yeah, but right now it is not 1/26/2020, 10:34:13 PM - mebeim (Marco Bonelli): issues are not necessarely problems, they can also be discussion threads 1/26/2020, 11:24:33 PM - sbrl (Starbeamrainbowlabs): @psibi: Hey, awesome! That's the default client in my apt repo I think 1/26/2020, 11:25:23 PM - sbrl (Starbeamrainbowlabs): @zdroid: Indeed, but in tldr-pages issues are more of a todo list and long-standing tracking issues than issues from people with problems 1/26/2020, 11:25:33 PM - sbrl (Starbeamrainbowlabs): So such a metric doesn't make much sense in our context 1/27/2020, 1:23:00 PM - psibi (Sibi Prabakaran): @sbrl Yeah, that's right. It seems to be the default for Debian and Ubuntu distros. It's sad that they both ship a very old version of the client. 1/27/2020, 2:27:43 PM - mebeim (Marco Bonelli): @psibi I was wondering, why is that that your package is named `tldr` instead of being `tldr-hs` with `Provides: tldr`? 1/27/2020, 2:28:21 PM - mebeim (Marco Bonelli): Because I see other people wanting to publish to Debian/Ubuntu too and of course you can't have the same name 1/27/2020, 2:35:51 PM - psibi (Sibi Prabakaran): Well, I didn't package for Debian/Ubuntu so you have to take up with the maintainers there. 1/27/2020, 2:37:06 PM - mebeim (Marco Bonelli): @psibi Ah, got it, thank you 1/27/2020, 2:37:26 PM - psibi (Sibi Prabakaran): :thumbsup: 1/27/2020, 5:06:31 PM - sbrl (Starbeamrainbowlabs): Ah, I see. That's a shame - we should really poke the maintainers on that one 1/27/2020, 5:06:47 PM - sbrl (Starbeamrainbowlabs): There have been so many improvements in the tldr world recently - like multi-language support! 1/27/2020, 6:04:51 PM - agnivade (Agniva De Sarker): Yep, we don't create issues like a task list. It's more of ideas and discussions. Somebody might eventually get to it. But we cannot just close them outright. 1/27/2020, 6:21:51 PM - sbrl (Starbeamrainbowlabs): :+1: 1/27/2020, 6:23:29 PM - sbrl (Starbeamrainbowlabs): A better metric would perhaps be the GitHub pulse page: https://github.com/tldr-pages/tldr/pulse 1/27/2020, 6:44:23 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl Damn, I squashed your multi-page PR 1/27/2020, 6:44:56 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): should I maybe revert it? or it can stay with 1 commit only? 1/27/2020, 6:45:56 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): https://github.com/tldr-pages/tldr/pull/3800 1/27/2020, 11:43:25 PM - sbrl (Starbeamrainbowlabs): Ah, it can probably stay as-is. 1/27/2020, 11:43:41 PM - sbrl (Starbeamrainbowlabs): Nevermind, there's always next time 1/29/2020, 5:29:15 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Can someone take a look at https://github.com/tldr-pages/tldr/pull/3798 and review it? 1/29/2020, 5:29:31 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Once it is merged, I can continue translating the pages 1/29/2020, 5:33:32 PM - mebeim (Marco Bonelli): @zdroid What's `hbs`? I don't think that's a valid ISO 639 code 1/29/2020, 6:05:55 PM - owenvoke (Owen Voke): Serbo-Croatian. It's a valid ISO 639-3 code, but don't we use 2-character codes? 1/29/2020, 6:07:23 PM - owenvoke (Owen Voke): Actually, we just say "the shortest ISO 639 language code for the chosen language". So I guess it should be fine? 1/29/2020, 6:21:06 PM - mebeim (Marco Bonelli): Ah, I guess I was looking at the wrong Wikipedia page (ISO 639-2) 1/29/2020, 6:24:27 PM - mebeim (Marco Bonelli): Feels weird though, I'm not an expert at all to say if `hbs` is better than other tags, but I see the Issue that @zdroid opened, and makes sense... 1/29/2020, 6:43:39 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): sh used to be a code for it, but that's ISO 639-1 1/29/2020, 7:12:26 PM - mebeim (Marco Bonelli): @zdroid you're saying that `sh` is a valid ISO 639 code for Serbo-Croatian? 1/29/2020, 7:41:12 PM - principis (Arthur Bols): `hbs` seems to be preferred `sh` is deprecated https://en.wikipedia.org/wiki/Serbo-Croatian 1/29/2020, 7:44:21 PM - mebeim (Marco Bonelli): Ok, makes sense 1/29/2020, 8:22:55 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): ISO 639-1 yes 1/29/2020, 8:23:15 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But for 639-2 and 639-3, no 1/29/2020, 8:26:16 PM - mebeim (Marco Bonelli): yeah the one in 639-1 is deprecated so makes sense to use 639-3 1/29/2020, 8:28:03 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It's quite complicated anyway, since the language has several "standard" varieties 1/29/2020, 8:28:47 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But mutual intelligibility is almost 100%, especially in the tech field where all words stem from English 1/29/2020, 8:54:10 PM - principis (Arthur Bols): We can't support all varieties. It would be useless anyway. 1/29/2020, 8:55:09 PM - principis (Arthur Bols): Wow I didn't mean to send that already 😕 1/29/2020, 8:56:06 PM - principis (Arthur Bols): I don't know anything about languages in eastern-europe 1/29/2020, 8:57:40 PM - principis (Arthur Bols): Gitter is annoying on mobile 1/29/2020, 9:04:18 PM - principis (Arthur Bols): Ok so what I meant to say is: (I don't know anything about languages, except that it's a confusing mess...) If possible we should try to minimize the amount of varieties, for example en_US vs en_UK would be completely useless. And supporting dialects that few people speak seems useless to me except for it being "fun". Because they would understand the more common language anyway. 1/29/2020, 9:04:27 PM - principis (Arthur Bols): Gitter seems to send messages when I switch tabs 1/29/2020, 9:05:41 PM - mebeim (Marco Bonelli): Yeah that's what we try to do 1/30/2020, 2:11:01 AM - sbrl (Starbeamrainbowlabs): Yeah, it's a complicated situation. 1/30/2020, 2:11:19 AM - sbrl (Starbeamrainbowlabs): I suggested `hbs` since it's the banner for a bunch of related languages 2/3/2020, 6:20:04 PM - agnivade (Agniva De Sarker): @mebeim - Was this your doing ? https://github.com/tldr-pages/tldr/pull/3809#issuecomment-579203643. Great work :) 2/3/2020, 7:04:00 PM - mebeim (Marco Bonelli): @agnivade yep :) it's one of the checks I implemented 2/3/2020, 8:18:19 PM - owenvoke (Owen Voke): That's neat! 2/4/2020, 12:32:39 AM - sbrl (Starbeamrainbowlabs): ❤️ 2/5/2020, 9:34:48 PM - sbrl (Starbeamrainbowlabs): Hey! I've been ill with a nasty cold, but I should be back now. 2/5/2020, 10:55:15 PM - owenvoke (Owen Voke): Hope you're feeling better :) 2/5/2020, 11:44:11 PM - ivanhercaz (Iván Hernández Cazorla): Oh my good! 54 messages and a lot of notifications in tldr repository hehe...I have been very busy and, although I still very busy, I want to review the last notifications. A huge hug for everyone! 2/5/2020, 11:49:39 PM - ivanhercaz (Iván Hernández Cazorla): @agnivade Nice check and very pleasant message! Great work @mebeim. 2/5/2020, 11:51:12 PM - ivanhercaz (Iván Hernández Cazorla): @sbrl I hope you have a quick and good recuperation. 2/6/2020, 1:11:35 AM - sbrl (Starbeamrainbowlabs): Thanks! It's better now, but it's set off my asthma - so I'll just be coughing a lot for the next week 😛 2/6/2020, 8:13:35 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl oh, I understand you. I suffered a lot of asthma when I was younger, now less, but when there is calima (haze, in our case, sand in the air) I am very bad. Good luck! 2/6/2020, 8:47:47 AM - ivanhercaz (Iván Hernández Cazorla): I know this is offtopic, but this is specifically the phenomenon that affect us: https://en.wikipedia.org/wiki/Saharan_Air_Layer The article is bad in English and Spanish, I am going to add it to my pending tasks. @waldyrious, it hasn't a Portuguese translation! 😸 2/6/2020, 8:55:43 AM - ivanhercaz (Iván Hernández Cazorla): Could someone participate in tldr-pages/tldr#3802#issuecomment-582717570? I would like to know if it should be accepted a pun as an accepted form to add a command. I hope I responded appropriately. 2/6/2020, 4:47:22 PM - sbrl (Starbeamrainbowlabs): Ah, very interesting @ivanhercaz! Also, done. I thinkt he aim of that PR is to add a mnomic to make it easier to remember. While the author may call it a pun, I think it's better described as a mnomic - and a useful one too! It can be difficult with commands like `tar`, `rsync`, and `netstat` to remember the options you want. For example with `netstat` I use `sudo netstat -peanut` to remind me. 2/6/2020, 5:03:20 PM - ivanhercaz (Iván Hernández Cazorla): @sbrl I use pun because it was used by the author, but in Spanish we use a very similar word "mnemónico". And yes, I am agree there are some commands very difficult to remember, `tar` is one that I need to check every time I need it. However, I had doubts about if commands examples with mnemonics are accepted because it is the first time I see one in tldr reviewing PRs. 2/6/2020, 10:09:20 PM - sbrl (Starbeamrainbowlabs): Ah, I see! IMHO mneomics are cool. 2/6/2020, 10:10:13 PM - ivanhercaz (Iván Hernández Cazorla): Laura isn't happy with us 😟 #3802 2/6/2020, 10:10:39 PM - ivanhercaz (Iván Hernández Cazorla): I hope my message don't sound rude or something else... 2/6/2020, 10:11:12 PM - sbrl (Starbeamrainbowlabs): No, it's fine :-) 2/6/2020, 10:11:20 PM - sbrl (Starbeamrainbowlabs): I don't get the `-rauL` one though 2/6/2020, 10:11:36 PM - sbrl (Starbeamrainbowlabs): Perhaps we should plug it into a word unscrambler lol 2/6/2020, 10:12:16 PM - ivanhercaz (Iván Hernández Cazorla): @sbrl it's a Spanish name: https://www.wikidata.org/wiki/Q18218532 2/6/2020, 10:13:16 PM - ivanhercaz (Iván Hernández Cazorla): I think in English it is Ralph. 2/6/2020, 10:13:25 PM - sbrl (Starbeamrainbowlabs): Ah, I see! 2/6/2020, 10:13:27 PM - sbrl (Starbeamrainbowlabs): ty 2/6/2020, 10:14:07 PM - ivanhercaz (Iván Hernández Cazorla): enwiki for Ralph: https://en.wikipedia.org/wiki/Ralph 2/6/2020, 10:19:51 PM - mebeim (Marco Bonelli): In #3802 she probably got offended by the fact that the edit was done without asking. Which is exactly what I was trying to explain here (at the bottom of my comment): https://github.com/tldr-pages/tldr/pull/3755#issuecomment-574736396 2/6/2020, 10:20:10 PM - mebeim (Marco Bonelli): I don't see any problem with the comments made by any of you guys. 2/6/2020, 10:21:34 PM - sbrl (Starbeamrainbowlabs): Yeah. IIRC this may not be the @ notpeter has reacted like that either. 2/6/2020, 10:23:34 PM - mebeim (Marco Bonelli): It's impossible to please everyone. No matter how you operate, there's always going to be someone who doesn't like something :\ 2/6/2020, 10:23:56 PM - sbrl (Starbeamrainbowlabs): :+1: 2/6/2020, 11:20:54 PM - agnivade (Agniva De Sarker): Oh I think I get it now .. Her name is "Laura" .. and she intentionally made the option as `-Laura` .. 2/6/2020, 11:21:09 PM - agnivade (Agniva De Sarker): I probably offended by making the change myself 😟 2/6/2020, 11:21:16 PM - agnivade (Agniva De Sarker): Phew .. can't please everyone .. 2/7/2020, 12:00:27 AM - mebeim (Marco Bonelli): ¯\\_(ツ)_/¯ 2/7/2020, 3:59:00 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): > Oh I think I get it now .. Her name is "Laura" .. and she intentionally made the option as `-Laura` .. Yes, that's why she called it a pun 2/7/2020, 3:59:11 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I thought it was obvious ehh 2/7/2020, 4:00:06 AM - mebeim (Marco Bonelli): LOL 2/7/2020, 4:00:19 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But after all, the goal is to keep things as short as possible 2/7/2020, 4:00:34 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Raul is 1 letter shorter than Laura, so you did the job correctly 😃 2/7/2020, 9:12:28 AM - agnivade (Agniva De Sarker): Yes, looking back, it is obious now. Somehow my brain didn't register it. 2/7/2020, 9:13:20 AM - agnivade (Agniva De Sarker): She called it a pun, but she never explicitly mentioned of what. And I didn't carefully look at her username to make the connection. 2/7/2020, 6:57:28 PM - sbrl (Starbeamrainbowlabs): Neither did I 😛 2/8/2020, 12:42:28 AM - ivanhercaz (Iván Hernández Cazorla): @zdroid, #3840 remembers me that I have to update [tldr-pages-data](https://github.com/ivanhercaz/tldr-pages-data) to have Serbo-Croatian in the graphs ❤️ I hope to have time soon to make something deployed to be updated automatically. At this moment it is just a Jupyter Notebook. 2/8/2020, 12:58:37 AM - ivanhercaz (Iván Hernández Cazorla): When someone of you have a bit of time, could you review #3727? It is the PR I opened for the translation of all the `git` commands to Spanish. I think it is only necessary to update `git-add` page due #3778, but I maybe something is wrong. At least tldr-bot didn't warn about any issue. 2/8/2020, 1:04:02 AM - ivanhercaz (Iván Hernández Cazorla): And... excuse me for the 44 files translated 😇 2/8/2020, 1:04:27 AM - sbrl (Starbeamrainbowlabs): Ah, nice work @ivanhercaz! Shall I remove the WIP then? 2/8/2020, 1:05:07 AM - ivanhercaz (Iván Hernández Cazorla): Ups, give me a second and I will translate the addition of #3778 and then WIP can take its holiday hehe. 2/8/2020, 1:05:28 AM - sbrl (Starbeamrainbowlabs): 😃 2/8/2020, 1:10:48 AM - ivanhercaz (Iván Hernández Cazorla): Pushed! 2/8/2020, 1:10:58 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl thank you for faaaaast review. 2/8/2020, 1:11:05 AM - sbrl (Starbeamrainbowlabs): np 😛 2/8/2020, 1:11:16 AM - sbrl (Starbeamrainbowlabs): It would be much slower if I actually knew Spanish lol 2/8/2020, 1:11:40 AM - ivanhercaz (Iván Hernández Cazorla): Should I wait to @zdroid review due he approved it after the firsts commits? 2/8/2020, 1:12:44 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl we need more Spanish speakers in tldr to review, because I am sure someone could see things that I don't see or improve the translated text. 2/8/2020, 1:13:17 AM - sbrl (Starbeamrainbowlabs): We should wait a while for the Spanish speaker you @mentioned to reespond I think 2/8/2020, 1:13:21 AM - ivanhercaz (Iván Hernández Cazorla): I have to admit that... I really love to contribute to tldr-pages. 2/8/2020, 1:13:28 AM - sbrl (Starbeamrainbowlabs): Same! 2/8/2020, 1:13:46 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl yes! I am agree. I admit you that I forgot that I mentioned him hehe. 2/8/2020, 1:13:54 AM - sbrl (Starbeamrainbowlabs): This appears to be a consistent theme with tldr-pages - we need more contributors for every language we're translating to 😛 2/8/2020, 1:14:19 AM - ivanhercaz (Iván Hernández Cazorla): Yes, totally agree. 2/8/2020, 1:32:12 AM - ivanhercaz (Iván Hernández Cazorla): I wrote him privately about our interest in his review and with a subtle statement about our lack of Spanish reviewers... 😶 2/8/2020, 1:38:17 AM - sbrl (Starbeamrainbowlabs): 😃 2/8/2020, 1:47:06 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I reviewed pretty much every file you added there, I just didn't notify you of that 😛 2/8/2020, 1:47:21 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @ivanhercaz You have my blessing for merging 2/8/2020, 1:51:03 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): You could write some for-loop to check all pages.* directories and analyze them in the same way, for your project 2/8/2020, 2:55:47 AM - sbrl (Starbeamrainbowlabs): Doesn't the Travis check all files automatically already? 2/8/2020, 8:21:25 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): What do you mean @sbrl, perhaps the Spanish translations? Travis doesn't check for the mistakes in them 😃 2/8/2020, 9:03:14 PM - sbrl (Starbeamrainbowlabs): Ah, I see. But neither would a for loop 2/9/2020, 6:11:26 AM - ivanhercaz (Iván Hernández Cazorla): @zdroid niiiiice! 2/9/2020, 6:11:44 AM - ivanhercaz (Iván Hernández Cazorla): @zdroid Thank you very much! 2/9/2020, 6:13:15 AM - ivanhercaz (Iván Hernández Cazorla): @zdroid Yes, I have something similar. But what I have in mind is to create a Flask app powered with Plotly. I will notice everyone when I have updated it. 2/9/2020, 6:18:48 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl, I am going to merge the PR and if ChrisADR replied my email or with a comment in GitHub, I will review with him the translations. 2/9/2020, 7:20:54 AM - sbrl (Starbeamrainbowlabs): Oooh, a flask app? Is that for showing translation stats or something? Sure thing, @ivanhercaz 2/9/2020, 3:34:55 PM - ivanhercaz (Iván Hernández Cazorla): @sbrl, yes, to make stats of tldr-pages. Quantity of them in each language and quantity of them in each platform. 2/9/2020, 5:08:21 PM - sbrl (Starbeamrainbowlabs): Ah, cool! 2/9/2020, 5:08:53 PM - sbrl (Starbeamrainbowlabs): If you don't have anywhere to host that once it's done I may be able to sort something out and host it alongside tldr-bot 2/9/2020, 5:09:21 PM - sbrl (Starbeamrainbowlabs): Just so-long as it's fairly lightweight and doesn't require a MariaDB etc DB (SQLite is fine though) 2/9/2020, 10:27:06 PM - owenvoke (Owen Voke): Could do it with GitHub Actions? 2/9/2020, 10:28:46 PM - sbrl (Starbeamrainbowlabs): Ah, I haven't really been paying attention to GH actions. What are they for? 2/10/2020, 2:25:39 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl, I thought to deploy it on Heroku due it is a very basic app. We can talk about it. Even if tldr-pages team considere, the repository might be transfered to the tldr-pages. 2/10/2020, 2:26:18 AM - ivanhercaz (Iván Hernández Cazorla): Wow! Chris replied to #3727, although I don't know to what he is referring with "Spanish version sounds spanish enough to me". 2/10/2020, 2:33:50 AM - sbrl (Starbeamrainbowlabs): Ah, that's an option too. Though if / when we sort out the donation thing, we might be able to pay for a VPS to host our stuff on 😃 2/10/2020, 2:34:26 AM - sbrl (Starbeamrainbowlabs): I think there's an issue open about that. IIRC it's pretty much setup - we just need to add the FUNDING.yml file or whatever it is 2/10/2020, 2:37:39 AM - ivanhercaz (Iván Hernández Cazorla): That's would be awesome. I am going to work a bit in the web app. When I have something I will notice you to have opinions about it. 2/10/2020, 2:38:05 AM - sbrl (Starbeamrainbowlabs): sure thing! 2/10/2020, 2:38:17 AM - ivanhercaz (Iván Hernández Cazorla): Although I always thanks every idea or whatever opening an issue because in that way it is better documented. 2/10/2020, 2:38:38 AM - sbrl (Starbeamrainbowlabs): Speaking of (on a bit of a tangent), I'm finally starting to make a bit of progress on learning Rust by building a web app 2/10/2020, 2:38:41 AM - ivanhercaz (Iván Hernández Cazorla): As historian, I really like to document so... issues, issues, issues everywhere! 2/10/2020, 2:40:06 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl ufff, sometimes I play a bit with Rust, but I prefer to focus on Python and improve as much I can. Rust is very interesting and powerful, but its learning curve its bigger and now Python satisfy the most of my necessities. 2/10/2020, 2:42:47 AM - ivanhercaz (Iván Hernández Cazorla): What do you think about the possibility to transfer the repository (tldr-pages-data) to tldr-pages if you (the team) considered it is useful? 2/10/2020, 2:46:45 AM - sbrl (Starbeamrainbowlabs): Yeah. I'm going to write a blog post about Rust at some point, but you're right - the learning curve is _huge_! Definitely not for the faint of heart. Absolutely! I'm certain we can arrange that - and also ensure you retain admin rights over the repo. 2/10/2020, 2:47:29 AM - sbrl (Starbeamrainbowlabs): And yeah, I've become increasingly fond of documenting stuff over the last few years 2/10/2020, 2:47:39 AM - sbrl (Starbeamrainbowlabs): Perhaps open an issue about the transfer? 2/10/2020, 2:47:46 AM - sbrl (Starbeamrainbowlabs): Just for the record 😛 2/10/2020, 7:32:24 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Is Rust even worth learning? Especially compared to some more popular languages like Go 2/10/2020, 7:32:35 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Which have the similar purpose 2/10/2020, 7:35:23 PM - mebeim (Marco Bonelli): Go and Rust definitely don't have the same purpose, but well, depends on what you like. 2/10/2020, 7:36:44 PM - mebeim (Marco Bonelli): If you ask me, Rust is well worth learning, but has a very steep learning curve (as in: you'll struggle a lot in the beginning). Other than that, I think Rust is the most powerful language in existence at the moment (comparable to C). 2/10/2020, 7:39:20 PM - mebeim (Marco Bonelli): Go goal = effortless and efficient parallelism, simple semantics and C-like paradigm. Rust goal = guaranteed memory safety and C-like speed, more functional paradigm. 2/10/2020, 7:41:30 PM - mebeim (Marco Bonelli): Go is just more popular because it's easier to learn IMHO 2/10/2020, 7:43:39 PM - mebeim (Marco Bonelli): Ah forgot to mention: Go build/pkg/import system is a real circus, under that perspective Rust is way more mature. 2/10/2020, 8:16:47 PM - psibi (Sibi Prabakaran): Another difference is that Go still doesn't have generics. 2/10/2020, 8:17:28 PM - psibi (Sibi Prabakaran): Although it seems it might get it as there is a proposal now. 2/10/2020, 8:41:17 PM - sbrl (Starbeamrainbowlabs): What fascinates me about Rust is the ability to do so many checks at compile time. Since it has an unparalleled understanding of how memory is going to be used at compile time, it can actually generate more optimal code than even the most advanced C/C++ compiler in a number of circumstances. 2/11/2020, 11:22:42 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @mebeim Both are used for similar purpose, i.e. backend 2/11/2020, 11:22:54 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): And yes, Go's package management seems like a circus haha 2/11/2020, 11:23:14 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl Can you please review this PR https://github.com/tldr-pages/tldr/pull/3716 and save it from the evil hands of a terminator named tldr-bot? 2/11/2020, 11:24:59 PM - sbrl (Starbeamrainbowlabs): I haven't seen Go's package management (not a Go programmer). What's up with it? 2/11/2020, 11:25:08 PM - sbrl (Starbeamrainbowlabs): @zdroid: Haha lol sure 2/11/2020, 11:25:50 PM - sbrl (Starbeamrainbowlabs): Erm I'm not seeing tldr-bot on that PR. 2/11/2020, 11:26:03 PM - sbrl (Starbeamrainbowlabs): That's stale-bot, which will only close things if there isn't any acitivity 2/11/2020, 11:27:31 PM - sbrl (Starbeamrainbowlabs): I think we're still waiting for @ waldyrious' thoughts on that one 2/12/2020, 1:56:34 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Both of them are killers 2/12/2020, 1:56:53 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But right, this is stale-bot 2/12/2020, 2:13:40 AM - sbrl (Starbeamrainbowlabs): They have their uses. 2/12/2020, 2:13:56 AM - sbrl (Starbeamrainbowlabs): stale-bot in particular is great for PRs where the author doesn't respond 2/12/2020, 2:14:08 AM - sbrl (Starbeamrainbowlabs): it's a graceful way of closing old PRs from people who don't reply 2/12/2020, 2:14:17 AM - sbrl (Starbeamrainbowlabs): tldr-bot is great at telling people what's gone wrong 2/12/2020, 2:23:45 AM - sbrl (Starbeamrainbowlabs): because otherwise the linter fails and there's no obvious message to tell people what the problem is 2/12/2020, 2:23:50 AM - sbrl (Starbeamrainbowlabs): @zdroid 1/14/2023, 3:41:53 PM - noelzubin (noel zubin victor) joined the room 2/18/2020, 12:37:09 PM - noelzubin (noel zubin victor): I dont see why tldr should be a github repo. 2/18/2020, 12:37:30 PM - noelzubin (noel zubin victor): Can we add more features to the site. and store the commands in a db instead. 2/18/2020, 12:38:10 PM - noelzubin (noel zubin victor): allow users to vote, add and change commands from the webapp ? 2/18/2020, 12:38:35 PM - noelzubin (noel zubin victor): Store each example in the db instead ? 2/18/2020, 2:10:34 PM - owenvoke (Owen Voke): Interesting idea. I feel that tldr works well as a repository on GitHub. It can easily be discussed, edited, and voted on through the repository. And issues can be created for new page requests, etc. It is also decentralised through Git. The website however is a separate project, so it may be possible to use a database? I think currently it just downloads a zipped archive of the pages, but I'm not sure. 2/18/2020, 6:59:11 PM - mebeim (Marco Bonelli): The problem about creating a fully functional standalone website is that everything should be built from ground up. Github offers Issues/PRs, built-in history, and has its own users. 2/18/2020, 7:00:29 PM - mebeim (Marco Bonelli): What we would like to do is to have a website for translations, but that requires non-trivial work and none of us has any experience in the field unfortunately so that's going to be a real slow transition. 1/14/2023, 3:41:57 PM - StewAlexanderACC (Stew Alexander) joined the room 2/18/2020, 8:19:09 PM - StewAlexanderACC (Stew Alexander): Curious if anyone has thought of creating an ncurses tldr dictionary for the command line? Essentially a tldr that can be browsed? If not, any objections if I start a project? 2/18/2020, 8:34:28 PM - StewAlexanderACC (Stew Alexander): Started: https://github.com/StewAlexanderACC/nTLDR 2/19/2020, 12:08:34 AM - sbrl (Starbeamrainbowlabs): If it's not in the client list, then it probably doesn't yet exist. You're welcome to start such a project @StewAlexanderACC :-) 2/19/2020, 12:08:55 AM - sbrl (Starbeamrainbowlabs): For reference, check out our client spec here: https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md 2/20/2020, 9:27:31 PM - sbrl (Starbeamrainbowlabs): Are my notifications right? Have we not had any activity for 2 days? 2/20/2020, 9:27:50 PM - sbrl (Starbeamrainbowlabs): Been having some oddness with my notifications recently, so just want to check 2/20/2020, 10:34:27 PM - StewAlexanderACC (Stew Alexander): I'm getting updates 2/20/2020, 10:34:49 PM - StewAlexanderACC (Stew Alexander): Well, I got yours 2/21/2020, 12:19:09 AM - mebeim (Marco Bonelli): @sbrl I think they are right 🤔 2/21/2020, 2:42:23 AM - sbrl (Starbeamrainbowlabs): hrm, thanks 2/22/2020, 11:34:30 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): They are, some days are simply silent 2/22/2020, 11:35:09 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): There hasn't been much activity lately 2/22/2020, 11:36:28 PM - sbrl (Starbeamrainbowlabs): Indeed 2/22/2020, 11:36:34 PM - sbrl (Starbeamrainbowlabs): It does tend to be seasonal 2/22/2020, 11:36:47 PM - sbrl (Starbeamrainbowlabs): October is the busiest time I've noticed 2/22/2020, 11:36:57 PM - sbrl (Starbeamrainbowlabs): 'cause of hacktoberfest 2/28/2020, 6:23:58 AM - dbrgn (Danilo Bargen): Tealdeer 1.3.0 has been released! https://github.com/dbrgn/tealdeer/releases/tag/v1.3.0 2/28/2020, 6:24:37 AM - dbrgn (Danilo Bargen): (Holy moly, that thing was a quick hack on a train ride, and now the repo has almost 600 stars... 😳) 2/28/2020, 6:25:23 AM - sbrl (Starbeamrainbowlabs): Nice one! 2/28/2020, 6:26:22 AM - sbrl (Starbeamrainbowlabs): Does it support multiple languages, out of interest? 2/28/2020, 6:26:27 AM - dbrgn (Danilo Bargen): No, not yet 2/28/2020, 6:26:52 AM - dbrgn (Danilo Bargen): I personally wouldn't use that feature (even as a non-native English speaker), so someone would have to contribute it :) 2/28/2020, 6:27:24 AM - dbrgn (Danilo Bargen): https://github.com/dbrgn/tealdeer/issues/96 2/28/2020, 6:28:49 AM - sbrl (Starbeamrainbowlabs): Ah, I see. I don't speak more than 1 language myself, but as I've been reviewing PRs I've noticed a lot of people working really hard to translate tldr-pages into lots of different languages! 2/28/2020, 6:29:47 AM - dbrgn (Danilo Bargen): Ok. I personally think that keeping translations up to date / in sync requires a lot of effort, and I prefer up-to-date pages over translated pages. But if you're not *that* fluent in English, then translated pages would help a lot. 2/28/2020, 6:33:22 AM - dbrgn (Danilo Bargen): Actually it should be quite simple to add support for multiple languages, since the translated pages are already fetched anyways: https://github.com/dbrgn/tealdeer/issues/96#issuecomment-592256633 2/28/2020, 6:37:22 AM - sbrl (Starbeamrainbowlabs): Yeah, we're still trying to figure that one out about keeping translations in sync 2/28/2020, 6:38:40 AM - sbrl (Starbeamrainbowlabs): We've got the page resolution algorithm detailed here, if you're interested: https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#language 2/28/2020, 6:39:24 AM - dbrgn (Danilo Bargen): Ah, that's helpful! 2/28/2020, 6:40:15 AM - sbrl (Starbeamrainbowlabs): If you spot any issues with that spec, please do let us know by opening an issue 😃 2/28/2020, 6:41:00 AM - dbrgn (Danilo Bargen): Something I just noticed is that it's quite POSIX centric. Windows users probably won't know how to set a `LC_MESSAGES` env variable (and it doesn't make sense there at all). 2/28/2020, 6:41:31 AM - dbrgn (Danilo Bargen): Also, a web based client for example would not be able to access the env. 2/28/2020, 6:42:01 AM - sbrl (Starbeamrainbowlabs): Very true. Some parts of the spec are only applicable to certain platforms. 2/28/2020, 6:42:09 AM - dbrgn (Danilo Bargen): Since the wording uses `MUST` (RFC style), strictly speaking a client on Windows is not spec-compliant. Maybe the section could be reworded to only apply to POSIX platforms. 2/28/2020, 6:42:12 AM - sbrl (Starbeamrainbowlabs): How would one determine the language on Windows though? 2/28/2020, 6:42:14 AM - dbrgn (Danilo Bargen): Or generalized. 2/28/2020, 6:42:32 AM - sbrl (Starbeamrainbowlabs): We should factor that into the spec if possible. 2/28/2020, 6:42:37 AM - dbrgn (Danilo Bargen): > How would one determine the language on Windows though? I'm not sure (I very rarely use Windows), but I'm sure there's a way to query it. 2/28/2020, 6:42:59 AM - sbrl (Starbeamrainbowlabs): I always thought that Windows was POSIX-compliant with respect to languages. 2/28/2020, 6:43:27 AM - dbrgn (Danilo Bargen): There's a registry entry, but that's awkward :) https://stackoverflow.com/questions/1610337/how-can-i-find-the-current-windows-language-from-cmd/35704694 2/28/2020, 6:43:57 AM - dbrgn (Danilo Bargen): There's also a powershell command: https://docs.microsoft.com/en-us/powershell/module/international/get-winsystemlocale?view=win10-ps 2/28/2020, 6:44:32 AM - dbrgn (Danilo Bargen): So I'm sure there's a way to query it, although the spec probably should not specify how to do it. Wording like "use the system language" would probably be better. 2/28/2020, 6:45:17 AM - dbrgn (Danilo Bargen): Anyways, gotta go get some sleep. Maybe I'll open an issue about this tomorrow (although I don't really have time to do a proposal myself). 2/28/2020, 6:45:28 AM - sbrl (Starbeamrainbowlabs): Hrm. Might be worth refactoring that section and expanding to talk about different platforms as examples then. 2/28/2020, 6:46:21 AM - sbrl (Starbeamrainbowlabs): Ah, thanks! Even if you don't have the time to handle it, I'm sure the rest of us at tldr-pages will be happy to discuss the issue and come up with a solution. 2/28/2020, 6:46:59 AM - sbrl (Starbeamrainbowlabs): We use GitHub issues to track issues and discuss things, you see - and the issue you've raised sounds like it should be "on the record", so to speak 😛 2/28/2020, 10:28:16 AM - agnivade (Agniva De Sarker): I think we discussed the Windows thing when we were deciding on how to detect the language. @mebeim do you remember ? 2/28/2020, 1:29:48 PM - mebeim (Marco Bonelli): Yeah I vaguely remember, Windows was kind of a pain to understand really, and IIRC it was not POSIX 2/28/2020, 1:32:46 PM - mebeim (Marco Bonelli): (and not BCP47 either) 2/28/2020, 4:34:40 PM - dbrgn (Danilo Bargen): What if someone writes a TLDR client for the Commodore 64? :) No POSIX either. 2/28/2020, 4:35:11 PM - dbrgn (Danilo Bargen): I think the spec should just say "the client should detect the system language", with a subsection specifically for POSIX systems (that doesn't apply to others). 2/28/2020, 4:38:26 PM - mebeim (Marco Bonelli): @dbrgn agree, that section of the spec should have a subsection when it talks about env vars that are linux/unix/posix specific, of course it doesn't make sense to say "the client MUST use $XXX if present" for all systems 2/28/2020, 4:42:15 PM - dbrgn (Danilo Bargen): https://github.com/tldr-pages/tldr/issues/3886 2/28/2020, 5:06:13 PM - mebeim (Marco Bonelli): Thank you @dbrgn :) 1/14/2023, 3:42:18 PM - hetraeus (hetraeus) joined the room 3/1/2020, 3:50:10 AM - hetraeus (hetraeus): Hello, I issued "$ tldr copyq" and found "(Copy a file's contents into the clipboard) copyq copy < file.txt" . It's not working for me and the working command I found on their page is slightly different: "copyq copy - < file.txt" . Reference:https://github.com/hluk/CopyQ 3/1/2020, 3:53:45 AM - sbrl (Starbeamrainbowlabs): > It's not working for me Can you elaborate, @hetraeus? What OS are you on? What do you mean by "not working"? 3/1/2020, 4:04:34 AM - hetraeus (hetraeus): My bad, there was a typo never mind... 3/1/2020, 5:00:57 AM - sbrl (Starbeamrainbowlabs): Ah, I see! You're welcome to contribute a pull request to fix the typo in the page, @hetraeus :-) 1/14/2023, 3:42:21 PM - macintacos (Julian Torres) joined the room 3/3/2020, 9:41:41 PM - macintacos (Julian Torres): Wanted to ask this here before opening a feature request; is it possible to have tldr search all OS's for any viable entry, or you'd have to search them all individually? 3/3/2020, 9:51:04 PM - sbrl (Starbeamrainbowlabs): Hey there, @macintacos! Which client are you using? That's perfectly possible, but you'd need to open an issue against the client you're using, rather than tldr-pages itself. 3/3/2020, 9:51:26 PM - sbrl (Starbeamrainbowlabs): For example, the bash client I use by @ pepa65 does this automatically 3/3/2020, 9:51:36 PM - sbrl (Starbeamrainbowlabs): But the Node.js client doesn't IIRC 3/3/2020, 10:40:36 PM - macintacos (Julian Torres): I'm using whatever client is installed by homebrew, so looks like the C client 3/3/2020, 10:42:44 PM - sbrl (Starbeamrainbowlabs): Ah, I see. I think it's [here](https://github.com/tldr-pages/tldr-cpp-client) that you'll want to open an issue then 3/3/2020, 10:43:31 PM - sbrl (Starbeamrainbowlabs): Though that client hasn't been updated in a while, so it might be worth changing the client that's installed by homebrew, I'm not sure 3/3/2020, 10:43:50 PM - sbrl (Starbeamrainbowlabs): Don't have a mac and don't have homebrew, so I'm of limited help there 3/3/2020, 10:44:18 PM - macintacos (Julian Torres): all good; I might actually just look into using a different client instead of trying to get the current one I'm using modified 3/3/2020, 10:44:41 PM - macintacos (Julian Torres): does the bash client search everything out of the box or do you have to pass in an option? 3/3/2020, 10:45:56 PM - sbrl (Starbeamrainbowlabs): It does do everything out of the box, yeah 3/3/2020, 10:46:20 PM - macintacos (Julian Torres): cool I'll take a look, thanks! 3/3/2020, 10:46:36 PM - sbrl (Starbeamrainbowlabs): np 3/3/2020, 10:46:50 PM - sbrl (Starbeamrainbowlabs): don't forget the client list in the readme 😃 3/4/2020, 12:53:27 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It seems someone has awoken the CLA assistant from the deep hibernation 3/4/2020, 12:53:41 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): How come it comments all PRs like this? 3/4/2020, 12:57:19 AM - sbrl (Starbeamrainbowlabs): Ah, I haven't checked my notifications yet today 3/4/2020, 12:57:38 AM - sbrl (Starbeamrainbowlabs): It's probably just catching up 3/4/2020, 12:57:47 AM - sbrl (Starbeamrainbowlabs): Lol about the hibernation though 3/4/2020, 1:51:58 AM - mebeim (Marco Bonelli): @zdroid yeah that's strange, i too noticed that 3/4/2020, 1:52:27 AM - mebeim (Marco Bonelli): something funny going on with the CLA bot probably 3/4/2020, 1:52:38 AM - mebeim (Marco Bonelli): not under out control 3/4/2020, 2:56:54 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Probably its owner had to restart it due to some internal failure 3/4/2020, 2:57:43 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But I hope it's not gonna become a spambot instead 😃 3/9/2020, 6:02:54 PM - owenvoke (Owen Voke): @mebeim, I've just noticed that the `scripts/check-pr.sh` script doesn't run correctly on Travis. 🤔 3/9/2020, 6:03:05 PM - owenvoke (Owen Voke): It get's the following output: `scripts/check-pr.sh: line 62: readarray: -d: invalid option` 3/9/2020, 6:03:22 PM - sbrl (Starbeamrainbowlabs): Hrm, that's odd 3/9/2020, 6:03:44 PM - sbrl (Starbeamrainbowlabs): ``` $ help readarray readarray: readarray [-d delim] [-n count] [-O origin] [-s count] [-t] [-u fd] [-C callback] [-c quantum] [array] Read lines from a file into an array variable. A synonym for `mapfile'. ``` 3/9/2020, 6:03:50 PM - sbrl (Starbeamrainbowlabs): Ubuntu 19.10 3/9/2020, 6:04:07 PM - sbrl (Starbeamrainbowlabs): I wonder what container it runs inside of on Travis 3/9/2020, 6:04:30 PM - owenvoke (Owen Voke): Ubuntu Xenial 3/9/2020, 6:04:48 PM - owenvoke (Owen Voke): So we are currently using 16.04 3/9/2020, 6:06:19 PM - owenvoke (Owen Voke): I wonder if it's worth updating to use `dist: bionic` in the Travis config? 3/9/2020, 6:07:46 PM - mebeim (Marco Bonelli): @pxgamer oh... And I was sure I tested it, what the hell 3/9/2020, 6:08:07 PM - owenvoke (Owen Voke): https://travis-ci.org/tldr-pages/tldr/builds/660125219#L214 3/9/2020, 6:08:55 PM - sbrl (Starbeamrainbowlabs): The issue aside, we should def. update to bionic 3/9/2020, 6:09:16 PM - sbrl (Starbeamrainbowlabs): Perhaps it's because of an old version of bash 3/9/2020, 6:09:24 PM - sbrl (Starbeamrainbowlabs): updating to bionic should fix it I theorise 3/9/2020, 6:10:12 PM - owenvoke (Owen Voke): Yeah, just checked the man page for it in Bionic, and the `-d` flag does exist :+1: 3/9/2020, 6:14:14 PM - mebeim (Marco Bonelli): I could also just get rid of that readarray really 3/9/2020, 6:15:54 PM - sbrl (Starbeamrainbowlabs): @owenvoke: I thought so 😛 3/10/2020, 12:15:44 AM - agnivade (Agniva De Sarker): We should update the bionic nevertheless. 3/10/2020, 2:41:35 AM - owenvoke (Owen Voke): I've opened #3900 to test. :+1: 3/11/2020, 2:15:33 AM - mebeim (Marco Bonelli): Hey guys, what do you think about this? Looking for other opinions. https://github.com/tldr-pages/tldr/pull/3835#pullrequestreview-371083122 3/11/2020, 2:18:30 AM - sbrl (Starbeamrainbowlabs): Hrm, tough one @mebeim. I think a reference in the page description is the best approach there. 3/11/2020, 2:21:18 AM - mebeim (Marco Bonelli): Yeah I think so too.. 3/11/2020, 2:40:03 AM - sbrl (Starbeamrainbowlabs): Looks like someone got confused about token syntax in #3894 3/11/2020, 2:54:47 AM - mebeim (Marco Bonelli): A *lot* of confusion going on in that PR 3/11/2020, 2:56:30 AM - sbrl (Starbeamrainbowlabs): Yeah 3/11/2020, 3:05:59 AM - mebeim (Marco Bonelli): Do you think it makes sense to keep `file.ts`? 3/11/2020, 3:07:47 AM - mebeim (Marco Bonelli): OP did not get confused about the token syntax, what they're saying is that they prefer `file.ts`instead of `path/to/file.ts` 3/11/2020, 3:11:09 AM - mebeim (Marco Bonelli): And I agree with them since all programming-language related commands seem to use the `file.ext` form rather than `path/to/file.ext`. I don't know how strict it makes sense to be on that rule. 3/11/2020, 3:12:40 AM - sbrl (Starbeamrainbowlabs): I think `{{path/to/file.ts}}` would be better. That way we keep the extension and make it more consistent. 3/11/2020, 3:18:15 AM - mebeim (Marco Bonelli): Well, if anything that'd make it inconsistent since any other page regarding programming languages uses `file.ext`. See for example: `node`, `gcc`, `g++`, `go`, `rustc`, `ghc`... 3/11/2020, 3:26:43 AM - sbrl (Starbeamrainbowlabs): Huh, interesting. 3/11/2020, 3:27:07 AM - sbrl (Starbeamrainbowlabs): I'm sure I've used the pattern `{{path/to/file.customextension}}` as a hint before. 3/11/2020, 3:27:19 AM - mebeim (Marco Bonelli): We actually have it in the style guide. 3/11/2020, 3:28:27 AM - mebeim (Marco Bonelli): I'm making a comment, I think we should reword the style guide to say that `path/to/file.ext` is preferred if it doesn't impact readability. 3/11/2020, 3:28:59 AM - mebeim (Marco Bonelli): In the case of `deno {{file.ts}}` for example it makes sense to have `deno {{path/to/file.ts}}`, doesn't hurt. 3/11/2020, 3:29:05 AM - sbrl (Starbeamrainbowlabs): Huh, interesting - I wasn't aware 3/11/2020, 3:29:13 AM - sbrl (Starbeamrainbowlabs): ty 3/11/2020, 3:37:53 AM - mebeim (Marco Bonelli): np 3/12/2020, 10:47:56 PM - agnivade (Agniva De Sarker): Yeah .. I added the extension part in the style guide. But feel free to modify it. 3/14/2020, 9:53:13 PM - mebeim (Marco Bonelli): Hey guys, there's a security warning on the node client: https://github.com/tldr-pages/tldr-node-client/network/alert/package-lock.json/minimist/open 3/14/2020, 10:46:35 PM - sbrl (Starbeamrainbowlabs): Uh oh. I've clicked the "create automated security update" button 3/14/2020, 10:46:46 PM - sbrl (Starbeamrainbowlabs): We might need to do it manually with an `npm audit fix` 3/14/2020, 11:15:41 PM - mebeim (Marco Bonelli): I wouldn't do that automated thing honestly 3/14/2020, 11:16:16 PM - mebeim (Marco Bonelli): If it's fixable it can be easily done manually, but I don't know the client codebase and I don't know if that version can be updated or if it breaks something. 3/14/2020, 11:17:34 PM - mebeim (Marco Bonelli): In any case the fact that `tldr` is a simple cli utility already means that this is not an issue for us (it's not like it's a server app that allows someone to exploit the vuln remotely, you already need access to the machine to execute `tldr` **if** the bug affects the node client). 3/14/2020, 11:19:29 PM - sbrl (Starbeamrainbowlabs): I think that it opens a PR with an automated security update 3/14/2020, 11:20:03 PM - sbrl (Starbeamrainbowlabs): I haven't looked into the vuln in detail myself, but I guess it depends on what it is as to whether it can be exploited 3/14/2020, 11:24:08 PM - mebeim (Marco Bonelli): @sbrl what I'm saying is that even if it can be exploited the node client is just a simple offline local client. It is not exposed to external stuff. Even if the client was vulnerable, a potential attacker would have to already have control of the machine in order to run the client and trigger the vulnerability. 3/14/2020, 11:24:29 PM - mebeim (Marco Bonelli): (with that said of course it doesn't mean that we shouldn't fix the issue) 3/14/2020, 11:33:29 PM - sbrl (Starbeamrainbowlabs): true 3/28/2020, 2:37:29 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): to any org owner, you should edit the repo settings to display the funding button 3/28/2020, 2:38:59 AM - mebeim (Marco Bonelli): Done! 3/28/2020, 3:45:22 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Thanks @mebeim 3/28/2020, 3:45:36 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): May I ask are you alright, since you're in Milan? 3/28/2020, 3:50:51 AM - mebeim (Marco Bonelli): Oh yes I'm fine, staying safe and doing everything from home. Thanks for the concern :) 3/28/2020, 4:06:50 AM - sbrl (Starbeamrainbowlabs): Nice! I'm in Yorkshire, UK - doing ok here, though I'm apparently in an "at-risk" category 3/28/2020, 5:12:51 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): That's good, stay safe. Thanks to the chaotic response of my country, I probably already contracted the virus on a party a few weeks ago. I had symptoms for a week, but I'm healthy now anyway. 3/28/2020, 8:49:02 PM - mebeim (Marco Bonelli): If you have symptoms you should probably get tested. Anyway, hope you're all doing fine guys stay safe! 3/28/2020, 8:53:42 PM - sbrl (Starbeamrainbowlabs): Nope, no symptoms here! 3/29/2020, 5:37:05 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): What do you think about my website BTW? I revamped it a day ago. It's on https://zdroid.github.io/. 3/29/2020, 6:58:53 AM - sbrl (Starbeamrainbowlabs): Nice, @zdroid! 3/29/2020, 7:53:38 AM - mebeim (Marco Bonelli): @zdroid really like the minimalistic design. Though I would suggest making the background fixed and not scrolling along with the text and a little more transparent, as it is right now it kind of gets in the way while reading. 3/29/2020, 4:13:17 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It's a pattern, so it can hardly be fixed. But you're right about transparent background. I added it for text elements, so pattern doesn't get in their way. 3/29/2020, 5:16:30 PM - sbrl (Starbeamrainbowlabs): I think what @mebeim means @zdroid is to use css `position: fixed;` on a background element to fix the background in place. 3/29/2020, 5:16:42 PM - sbrl (Starbeamrainbowlabs): I'd personally disagree, but it's good stylistic choice 3/29/2020, 5:17:11 PM - sbrl (Starbeamrainbowlabs): perhaps a `background: rgba(255, 255, 255, 0.25);` or something on the text would make it slightly easier to read? 3/29/2020, 5:19:00 PM - sbrl (Starbeamrainbowlabs): I was also going to say before I saw the time last night (clock change) that I'd also suggest adding a new section / page for a portfolio as to the projects you've done? You mention them, but haven't gone into any detail. It looks like you're building a personal profile website (e.g. for a CV), so adding some detail on the projects you've done and the things you participate in can be valuable here. 3/29/2020, 6:38:00 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): There's `background-attachment: fixed;` so that works. I probably will add a projects page, I just need to reconsider which projects are worth noting. I had the page previously, too. 3/29/2020, 9:21:35 PM - mebeim (Marco Bonelli): it's `background-position`, not `position`, but yeah 3/29/2020, 9:22:08 PM - mebeim (Marco Bonelli): anyway it's a cool web page 3/29/2020, 10:49:54 PM - sbrl (Starbeamrainbowlabs): Oh, I wasn't aware of those 4/1/2020, 6:21:11 AM - sbrl (Starbeamrainbowlabs): Perhaps when reviewing a PR @zdroid you could insert a suggestion to let contributors know what you mean? When I've been reviewing PRs I've been confused by a few of your comments rececntly. 4/1/2020, 6:21:18 AM - sbrl (Starbeamrainbowlabs): Though it might just be me 4/1/2020, 6:48:06 AM - mebeim (Marco Bonelli): Me too (example: https://github.com/tldr-pages/tldr/pull/3902#discussion_r390665554). Rather than just saying "do X", try to explain why they should do X and why you think it's good idea. 4/1/2020, 3:32:19 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I agree, but the descriptions that contributors provide are not so clear as well. For most of those cases I couldn't come up with a suggestion that looks good enough. I just noted it so it doesn't get unnoticed by other maintainers that may have an idea how to fix it. 4/1/2020, 4:46:12 PM - sbrl (Starbeamrainbowlabs): Yeah, that can be an issue @zdroid. Generally what I've found to be effective in those situations is to ask for clarification on what they mean _first_, before suggested something afterwards. For example: > I'm somewhat confused about X here. Do you mean Y, or perhaps Z? Then, you can make a more informed ```suggestion 4/1/2020, 5:53:04 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Yup, I understood. I decided just to note it's confusing, instead of directly asking it to be changed. 1/14/2023, 3:43:04 PM - gradlexyz (gradlexyz) joined the room 4/3/2020, 5:07:47 PM - gradlexyz (gradlexyz): I want a db file that contain command name, desc, examples, what shoud I do? 4/3/2020, 10:30:38 PM - mebeim (Marco Bonelli): @gradlexyz there's a ZIP archive available at tldr.sh/assets/tldr.zip 4/3/2020, 10:32:25 PM - mebeim (Marco Bonelli): if you are specifically asking for something like a SQL database with name, description and examples then we don't have it unfortunately, but you can parse the files in the zip and create one if you want 4/4/2020, 10:26:40 PM - mebeim (Marco Bonelli): https://github.com/tldr-pages/tldr-node-client/network/alert/package-lock.json/minimist/open 4/4/2020, 10:26:57 PM - mebeim (Marco Bonelli): hmmm these security alerts are starting to pop up a bit too often, damn nodejs 4/4/2020, 11:47:00 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): What do you think about the new GitHub notifications? For me, those are way too complicated and noisy. 4/4/2020, 11:48:05 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): The past system was really simple, but they are dropping it out. 😟 4/5/2020, 12:05:29 AM - mebeim (Marco Bonelli): It has its ups and downs.. I don't really like the fact that it's almost impossible to "escape" the notification to follow the link... 4/5/2020, 12:06:03 AM - mebeim (Marco Bonelli): like if you click the link (or even open in a new page) it gets you to a new page which is still inside of the notification with a banner to go back... kind of annoying 4/5/2020, 4:24:01 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Oh yes, that's really annoying. And lack of clear view of still active vs already done notifications. 4/7/2020, 6:32:42 PM - sbrl (Starbeamrainbowlabs): Hey, Gitter signed me out randomly. How annoying! I don't like the new notifications. I'm sticking with the old one 4/7/2020, 6:33:12 PM - sbrl (Starbeamrainbowlabs): Also, GitHub Pages is down, so @pepa65's Bash client that I use isn't working 😕 4/7/2020, 6:34:12 PM - sbrl (Starbeamrainbowlabs): [![Selection_035.png](https://files.gitter.im/tldr-pages/tldr/sV3C/thumb/Selection_035.png)](https://files.gitter.im/tldr-pages/tldr/sV3C/Selection_035.png) 4/7/2020, 7:49:39 PM - agnivade (Agniva De Sarker): GitHub has been having issues since past couple of months now. 4/7/2020, 7:51:54 PM - sbrl (Starbeamrainbowlabs): I wonder if it's got something to do with the virus & increased load lol 4/8/2020, 2:16:16 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): You may be right, check https://www.githubstatus.com/uptime 4/8/2020, 2:17:15 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Comparing the same months past year, it seems like this one is way busier on GitHub 4/13/2020, 4:04:38 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl Can you re-check this? https://github.com/tldr-pages/tldr/pull/3716 4/13/2020, 4:04:51 PM - sbrl (Starbeamrainbowlabs): Sure 1/14/2023, 3:43:12 PM - SturmB (Chris McGee) joined the room 4/16/2020, 8:07:47 PM - SturmB (Chris McGee): Good morning. 4/16/2020, 8:09:21 PM - SturmB (Chris McGee): I figured doing a simple `yarn global add tldr` would do the same thing as `npm install -g tldr`, but after installation, when running the `tldr` command, I am getting a "zsh: command not found: tldr" error message. Can anyone please help me to diagnose what to do from here? 4/16/2020, 8:33:26 PM - SturmB (Chris McGee): It looks like it was downloaded fine, but it sits at `~/.config/yarn/global/node_modules/tldr/bin/tldr`. What's the best way to call it without using the whole path? 4/16/2020, 8:42:06 PM - SturmB (Chris McGee): Never mind. Yarn appears to be going through some major changes as of late and they are now discouraging global installations with it. So I just installed `tldr` using the `npm` command on the site and now it appears to work fine. 4/16/2020, 9:05:00 PM - mebeim (Marco Bonelli): @SturmB good to hear you solved that. If you still want to go with yarn you could just add an alias in your shell like `alias tldr='/path/to/bin/tldr'` to your shell. 4/16/2020, 9:05:37 PM - mebeim (Marco Bonelli): Though having it installed globally automatically by the package manager is of course smoother. 4/18/2020, 4:08:59 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Or just add path/to/tldr to your $PATH. Interestingly, pip adds programs to path even for local installations. 4/18/2020, 4:09:30 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl it looks like you missed #3716 somehow 4/18/2020, 4:12:10 PM - sbrl (Starbeamrainbowlabs): Sorry @zdroid - I've been very busy preparing for my PhD Panel 1, which is on Thursday. 4/18/2020, 5:13:26 PM - owenvoke (Owen Voke): Good luck @sbrl! 4/18/2020, 5:13:36 PM - sbrl (Starbeamrainbowlabs): Thanks 😃 4/18/2020, 5:17:20 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Oh alright. Good luck with that. :) 4/18/2020, 5:33:55 PM - sbrl (Starbeamrainbowlabs): Just taken a look for you, and I'm not sure what you're after me saying? I don't see anything else I can add there 4/19/2020, 4:45:20 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl You're the only one putting it on hold (i.e. you requested changes), while others approved. That's why I asked you to "re-review" it. 4/19/2020, 4:48:08 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I think this project really needs a tie-breaking mechanism for issues stuck on hold for years. I'm completely for open discussion, but there's pretty much nothing to add. All that's left to be done is to decide on all of them. 4/19/2020, 4:48:58 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I have issues like #190, #266, #1109 in mind. 4/19/2020, 4:50:09 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): The burden of those issues increases with the scale of the project. As the number of pages is constantly growing, it really needs to be solved. 4/19/2020, 6:13:28 AM - sbrl (Starbeamrainbowlabs): I am? I wasn't aware of that. I'll have to go change that? The issues you like to there (especially #190 and #266) are very long-term issues. They might look like they are not being touched, but in actuality there are a large number of complicated dependencies that are not obvious. In addition, trying to force the issue just makes everyone unhappy. 4/19/2020, 6:14:14 AM - sbrl (Starbeamrainbowlabs): Sure, some issues might be blocked for a long time, but the project is still growing and evolving in other ways. 4/19/2020, 6:14:36 AM - sbrl (Starbeamrainbowlabs): /cc @pxgamer, @agnivade, @waldyrious 4/19/2020, 3:46:37 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Of course, they are complex so they take time to resolve. But I've went through the discussions and I don't see much new input over the years. That's why I think we need some tie-breaking mechanism to definitely resolve such issues. 4/19/2020, 5:22:10 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): One more thing. Many such issues are really obsolete, but are kept for some specific point, e.g. #3111. It's very confusing and time-consuming, as you have to dozens of comments before reaching the point of the discussion. A way more efficient approach is to close obsolete issues and open the new ones to reflect the changes. 4/19/2020, 10:07:44 PM - mebeim (Marco Bonelli): I agree that some kind of tie-breaking mechanism would make sense 4/23/2020, 10:05:19 AM - agnivade (Agniva De Sarker): Hey @zdroid - thank you so much for spending your time and going through the old issues ! I personally haven't been able to give that much time as I used to a few years back. I do agree that we need a conclusion on the old issues, but as with big open source projects, we need a consensus from the parties involved before taking any action. Without that, it can _seem_ slightly offensive to people who have put significant effort in the issue, and may have got busy with other things in life. I wanted to bring attention to the 2nd point in our GOVERNANCE file which beautifully captures what I am trying to say: `All interactions must be respectful and cordial.` Of course, you don't mean to be intentionally disrespectful but, `Remember, it's very hard to convey meaning on a purely written medium, especially between people from different cultures, technical backgrounds, English proficiency levels, etc.` Keeping that in mind, going a little further to always be a bit more respectful than usual helps us a long ways. :) 4/23/2020, 4:05:35 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): That's right, that point is presumed to be respected. But we can still add a point about respectful ways to resolve dead-locked issues. That's what I had in mind. 4/23/2020, 7:31:44 PM - agnivade (Agniva De Sarker): I agree on theory. But if start writing down each and every thing then it starts to become a constitution rather than guidelines for an open source project :) We just follow what makes sense. But I totally agree that we need to decide on a policy on what to do about old issues. It's been neglected for too long. 4/26/2020, 3:25:17 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I suggest... we open a new issue to discuss this haha 4/26/2020, 3:25:46 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): What do you think @agnivade @sbrl @mebeim? 4/26/2020, 3:30:13 AM - mebeim (Marco Bonelli): @zdroid you want to open an issue to discuss whether we should close old issues? 4/26/2020, 3:32:32 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I don't think it's whether, it's more likely when and how do we close them 4/26/2020, 3:32:43 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I.e. what should be the tie-breaking mechanism 4/26/2020, 9:03:39 AM - agnivade (Agniva De Sarker): Agree. Let's do that. 4/26/2020, 5:01:33 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Done. 4/26/2020, 6:24:37 PM - owenvoke (Owen Voke): :+1: 1/14/2023, 3:43:38 PM - yiweili (Yiwei Li) joined the room 4/29/2020, 3:10:55 AM - yiweili (Yiwei Li): Hi there, the we page doesn't seem to work. https://tldr.ostera.io/ 4/29/2020, 3:23:01 AM - sbrl (Starbeamrainbowlabs): Hey there, @yiweili! It appears to function as expected for me. What error are you seeing? 4/29/2020, 6:29:56 AM - yiweili (Yiwei Li): @sbrl no matter what command I input, the webpage will just show "Oops! Command not found!" 4/29/2020, 6:30:23 AM - sbrl (Starbeamrainbowlabs): Ah, I see. What client are you using? Also, try `tldr --update` 4/29/2020, 6:30:59 AM - yiweili (Yiwei Li): I'm using the web server: https://tldr.ostera.io/ 4/29/2020, 6:34:17 AM - sbrl (Starbeamrainbowlabs): Oh, I see. Sorry, it's late where I am lol Does `tar` work? Is there anything in the browser developer tools (F12 → js console)? 4/29/2020, 6:37:43 AM - yiweili (Yiwei Li): tar doesn't work either. The js console shows: Failed to load resource: net::ERR_FAILED 4/29/2020, 6:38:11 AM - yiweili (Yiwei Li): Maybe it's a proxy issue as I'm using company's computer. It might has something to do with its firewall setting. 4/29/2020, 4:52:22 PM - sbrl (Starbeamrainbowlabs): That sounds likely, @yiweili. It's functioning as expected for me, so I think the issue may be with your company's firewall. If you have permission, you could always try a command-line client instead. 4/29/2020, 9:19:40 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): did you try https://tldr.ooops.me/ or https://distrowatch.com/dwres.php?resource=man-pages 4/29/2020, 9:20:29 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): GitHub shouldn't be behind any firewalls, so it's most likely up to the website or domain 4/29/2020, 9:52:35 PM - sbrl (Starbeamrainbowlabs): Great suggestion, @zdroid - though some corporate firewalls are known to block such things I might add 4/29/2020, 10:56:49 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Reading an issue from 2015 in tldr-python-client, I found out GitHub's SSL verification can be blocked 4/29/2020, 10:57:06 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): So maybe that's the issue, but I don't know much about that 4/30/2020, 12:19:24 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl @agnivade @mebeim Is there a way to add a collaborator for tldr-python-client? 4/30/2020, 12:19:57 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Some were very active recently in that repo, making valuable contribs 4/30/2020, 12:20:17 AM - sbrl (Starbeamrainbowlabs): Ah, I see. Yeah, there is a way, but I recommend opening an issue about it 4/30/2020, 12:20:24 AM - sbrl (Starbeamrainbowlabs): Just like we do to welcome regular contributions 4/30/2020, 12:22:38 AM - sbrl (Starbeamrainbowlabs): *contributors 4/30/2020, 12:26:39 AM - mebeim (Marco Bonelli): Agree :) 4/30/2020, 10:12:12 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl open in tldr-python-client or in tldr? 4/30/2020, 10:17:18 PM - sbrl (Starbeamrainbowlabs): Probably tldr-python-client 4/30/2020, 10:17:31 PM - sbrl (Starbeamrainbowlabs): Could you post a link here too please? I don't think I've been getting notifications from that repo 5/1/2020, 12:48:44 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): https://github.com/tldr-pages/tldr-python-client/issues/55 5/1/2020, 12:48:55 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I thought to add it here, since there's an old issue about it 5/1/2020, 12:56:19 AM - sbrl (Starbeamrainbowlabs): +1 5/1/2020, 12:56:41 AM - sbrl (Starbeamrainbowlabs): Actually, if they are new people then a new issue might be best 5/2/2020, 4:24:52 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl I opened a new one, https://github.com/tldr-pages/tldr-python-client/issues/102 5/2/2020, 4:49:33 AM - sbrl (Starbeamrainbowlabs): thanks 5/3/2020, 12:51:03 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrlo also re-check #4000, I changed the at example 5/4/2020, 5:21:41 AM - sbrl (Starbeamrainbowlabs): Gosh, activity seems a bit quiet. Only 4 open PRs? Madness! I don't remember it ever getting that low lol 5/4/2020, 6:15:36 AM - sbrl (Starbeamrainbowlabs): There, I've doubled the number of open PRs to 8 😛 5/4/2020, 6:15:40 AM - sbrl (Starbeamrainbowlabs): much better lol 5/4/2020, 6:41:23 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Don't worry, we still have almost 70 open issues 5/4/2020, 6:41:37 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): They are more fun than PRs 😃 5/14/2020, 1:09:27 AM - ivanhercaz (Iván Hernández Cazorla): Hi everyone! I am happy to announce everyone that after the conversation in #4032 I decided to transfer ExTldr to tldr-pages organization, so it is now part of the tldr-pages ecosystem. I promise to maintain and continue the development of this client, as well to accomplish with the client specification as soon as possible (I hope to have it before July, before it might complicated because I have to finish the master degree and another important works to do). 5/14/2020, 1:10:06 AM - ivanhercaz (Iván Hernández Cazorla): Thank you very much to @zdroid, @owenvoke and @sbrl for your awesome comments ❤️ 5/14/2020, 1:11:32 AM - sbrl (Starbeamrainbowlabs): You're most welcome @ivanhercaz! I've now also granted you admin rights over that repository. 5/14/2020, 1:11:51 AM - sbrl (Starbeamrainbowlabs): Since you're leading development on it lol 5/14/2020, 1:12:17 AM - sbrl (Starbeamrainbowlabs): No worries, we've all got other things we're doing at the same time :-) For me it's a PhD in Computer Science 5/14/2020, 1:17:38 AM - ivanhercaz (Iván Hernández Cazorla): Oh! Yes, I am now administrator. Thank you very much. 5/14/2020, 1:18:44 AM - ivanhercaz (Iván Hernández Cazorla): I opened tldr-pages/extldr#13 to fix references to the old repository. Thanks to @owenvoke comment now I see that Travis is working fine. 5/14/2020, 1:19:56 AM - ivanhercaz (Iván Hernández Cazorla): Wow, you're awesome @owenvoke, thank you for tldr-pages/extldr#14 ❤️ 5/14/2020, 1:24:11 AM - sbrl (Starbeamrainbowlabs): Just let us know what we need to do to authorise Coveralls & Codacy @ivanhercaz if anything 5/14/2020, 1:24:45 AM - ivanhercaz (Iván Hernández Cazorla): Awesome! I will let you know in the issue in which you commented. 5/14/2020, 1:25:00 AM - owenvoke (Owen Voke): 👌 great. 🎉 5/14/2020, 1:25:35 AM - ivanhercaz (Iván Hernández Cazorla): Hummm... I think I can grant the access to Codacy and Coveralls being just member of tldr-pages. 5/14/2020, 1:25:59 AM - ivanhercaz (Iván Hernández Cazorla): Should I do or do you prefer that some org owner do it? 5/14/2020, 1:26:44 AM - ivanhercaz (Iván Hernández Cazorla): It is possible to authorize just one project. 5/14/2020, 1:31:53 AM - owenvoke (Owen Voke): I'll grant Coveralls permissions for the repository :+1: It looks relatively easy to do. 5/14/2020, 1:33:16 AM - owenvoke (Owen Voke): Coveralls now has permission. :slight_smile: 5/14/2020, 1:33:42 AM - ivanhercaz (Iván Hernández Cazorla): Awesome! 😻 5/14/2020, 1:34:06 AM - ivanhercaz (Iván Hernández Cazorla): @sbrl, do you want to make Codacy integration? 😃 5/14/2020, 1:35:24 AM - ivanhercaz (Iván Hernández Cazorla): And, even before the transfer, I was thinking about to add the CLA Assistant, what do you think? 5/14/2020, 1:43:31 AM - owenvoke (Owen Voke): Travis build is passing now 🎉 5/14/2020, 1:44:09 AM - owenvoke (Owen Voke): Just need Coveralls and then that PR can be merged I think. :+1: 5/14/2020, 1:44:26 AM - ivanhercaz (Iván Hernández Cazorla): Awesome! Really awesome! 5/14/2020, 1:54:40 AM - ivanhercaz (Iván Hernández Cazorla): In the case I won't reply to next messages it is because I am going to dine. @owenvoke, I left you the review of the PR, I trust your decision, the one you will choose it will be the best one :+1: 5/14/2020, 2:17:05 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): You're welcome! Good work for this implementation. I still am not able to write a full client in my favorite language. 😃 5/14/2020, 2:17:19 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Also, what do you think about Elixir @ivanhercaz? 5/14/2020, 2:17:23 AM - sbrl (Starbeamrainbowlabs): Cool @owenvoke! How would I do the Codacy integration? 5/14/2020, 2:17:48 AM - sbrl (Starbeamrainbowlabs): Also, CLAAssistant is a great idea. Doing it early is a wise move. 5/14/2020, 2:18:46 AM - sbrl (Starbeamrainbowlabs): I see Codacy in the "integrations" tab of the repo there already 5/14/2020, 2:20:32 AM - sbrl (Starbeamrainbowlabs): Just looking into CLAAssistant - we've just passed over 1K signings of the CLA agreement! 🎆 We now have 1010 signs so far to be exact 5/14/2020, 2:22:20 AM - sbrl (Starbeamrainbowlabs): CLA Assistant is now setup on tldr-pages/extldr 5/14/2020, 2:54:35 AM - ivanhercaz (Iván Hernández Cazorla): > You're welcome! Good work for this implementation. I still am not able to write a full client in my favorite language. 😃 There is always a first time! I think to start the development of a project it is a good and awesome way to learn how to solve a specific situation. 1/14/2023, 3:44:07 PM - MasterOdin (Matthew Peveler) joined the room 5/14/2020, 2:55:00 AM - MasterOdin (Matthew Peveler): Can a organization owner disable tldr-python-client on https://travis-ci.org as we move to gh-actions there? 5/14/2020, 3:01:34 AM - ivanhercaz (Iván Hernández Cazorla): > Also, what do you think about Elixir @ivanhercaz? I began with Elixir some weeks ago thanks to a mate that introduce it to me. I really like how it works, it simple and elegant. Although it is very soon for me to give a structured opinion, I think its more powerful features are how it works with concurrency programming. It is a very new language compared to another ones, but it is based in Erlang and approach many features of this language. It is really interesting too how you can integrate another programming languages into Elixir; it has a native integration with Erlang functions. My idea is to learn sufficient to check if it could be able to develop a project that I have in mind for my future PhD or a big grant project, and in this project one part would be the development of a webapp in which, if Elixir works, I will need to integrate it with Python too. 5/14/2020, 3:09:35 AM - principis (Arthur Bols): Should someone look into cleaning up the clients list? For example the TLDR Elixir Client is 6 years old, archived and still says "(binaries not yet available)". There are probably more clients which aren't being updated and/or following the client spec. 5/14/2020, 3:09:41 AM - ivanhercaz (Iván Hernández Cazorla): > Cool @owenvoke! How would I do the Codacy integration? It seems Codacy is already integrated, I said it per your comment in tldr-pages/extldr#13 and the one by @owenvoke tldr-pages/extldr#14. I will review in some minutes. 5/14/2020, 3:11:33 AM - ivanhercaz (Iván Hernández Cazorla): > Should someone look into cleaning up the clients list? For example the TLDR Elixir Client is 6 years old, archived and still says "(binaries not yet available)". There are probably more clients which aren't being updated and/or following the client spec. Yes, this is something that I think we should do. The TLDR Elixir Client (not the same as ExTldr, another Elixir client) is a good example of this case. I think the archived projects should be considered inactive and removed from the list because these projects have not support. 5/14/2020, 3:11:54 AM - sbrl (Starbeamrainbowlabs): @principis Probably a good idea 5/14/2020, 3:12:27 AM - sbrl (Starbeamrainbowlabs): @MasterOdin: So you've already moved to GitHub actions, and you'd like Travis disabling? 5/14/2020, 3:12:53 AM - ivanhercaz (Iván Hernández Cazorla): > Also, CLAAssistant is a great idea. Doing it early is a wise move. > Just looking into CLAAssistant - we've just passed over 1K signings of the CLA agreement! 🎆 > We now have 1010 signs so far to be exact Wow! Really awesome. Applause for everyone ❤️ 5/14/2020, 3:13:25 AM - ivanhercaz (Iván Hernández Cazorla): > CLA Assistant is now setup on tldr-pages/extldr Thank you very much! 5/14/2020, 3:14:36 AM - ivanhercaz (Iván Hernández Cazorla): @principis @sbrl, if you are agree, probably it might a good idea to open an issue on tldr-pages/tldr to comment this topic. If you want, principis, you could open the issue, or I could do it later. 5/14/2020, 3:14:55 AM - sbrl (Starbeamrainbowlabs): Good idea @ivanhercaz 5/14/2020, 3:16:11 AM - ivanhercaz (Iván Hernández Cazorla): There is also a Python client that I think it is unmaintained, not the one in which @MasterOdin and @zdroid are working, if I don't remember bad. 5/14/2020, 3:16:41 AM - sbrl (Starbeamrainbowlabs): So we want to turn off Travis for tldr-python-client 5/14/2020, 3:16:45 AM - sbrl (Starbeamrainbowlabs): @MasterOdin 5/14/2020, 3:17:01 AM - principis (Arthur Bols): @ivanhercaz sure :) 5/14/2020, 3:17:14 AM - principis (Arthur Bols): I'm not sure if I should do it, I don't have much time 5/14/2020, 3:17:34 AM - ivanhercaz (Iván Hernández Cazorla): > @ivanhercaz sure :) Nice, nice 5/14/2020, 3:18:07 AM - ivanhercaz (Iván Hernández Cazorla): > I'm not sure if I should do it, I don't have much time Don't worry, I can open an issue and comment everything we talked here, and you can contribute to the issue when you have time available. 5/14/2020, 3:18:23 AM - principis (Arthur Bols): thanks! :) 5/14/2020, 3:18:48 AM - ivanhercaz (Iván Hernández Cazorla): So, if you are agree, I will open before to go sleep. 5/14/2020, 3:19:31 AM - principis (Arthur Bols): Yes that's fine, thank you. 5/14/2020, 3:20:46 AM - ivanhercaz (Iván Hernández Cazorla): > Yes that's fine, thank you. Thanks to you for talk about this topic, I really think it is very important. 5/14/2020, 3:21:25 AM - MasterOdin (Matthew Peveler): > @sbrl So we want to turn off Travis for tldr-python-client I talked to @zdroid about it and I'd like to move to github actions as the build pipeline over Travis. However, while doing that, I'd like to disable Travis for the project as otehrwise it will keep trying to build it as a ruby project after I delete the .travis.yml file. Additionally, need to make sure that there's no mandatory travis checks for PRs. 5/14/2020, 3:23:44 AM - MasterOdin (Matthew Peveler): Given Travis' acquisition by Idera and GH' growing ecosystem of tools, I do think Travis is going to lag behind GH over time (if not already) 5/14/2020, 3:27:26 AM - sbrl (Starbeamrainbowlabs): Travis has been acquired? I wasn't aware of that Is GitHub Actions free? Ok, that makes sense. 5/14/2020, 3:27:38 AM - sbrl (Starbeamrainbowlabs): I've turned off "build pushed branches" 5/14/2020, 3:27:49 AM - sbrl (Starbeamrainbowlabs): and "build pushed pull requests" 5/14/2020, 3:28:01 AM - sbrl (Starbeamrainbowlabs): for tldr-python-client 5/14/2020, 3:28:12 AM - MasterOdin (Matthew Peveler): Yeah, they got acquired by Idera https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc 5/14/2020, 3:28:48 AM - ivanhercaz (Iván Hernández Cazorla): > > @sbrl So we want to turn off Travis for tldr-python-client > > I talked to @zdroid about it and I'd like to move to github actions as the build pipeline over Travis. However, while doing that, I'd like to disable Travis for the project as otehrwise it will keep trying to build it as a ruby project after I delete the .travis.yml file. Additionally, need to make sure that there's no mandatory travis checks for PRs. When was Travis acquired?! 😲 5/14/2020, 3:28:54 AM - MasterOdin (Matthew Peveler): Who by all accounts are not a great OSS company. GH actions is free for public repos, yes. 5/14/2020, 3:29:07 AM - sbrl (Starbeamrainbowlabs): cool, that's probably the better solution then 5/14/2020, 3:29:17 AM - ivanhercaz (Iván Hernández Cazorla): > Yeah, they got acquired by Idera https://blog.travis-ci.com/2019-01-23-travis-ci-joins-idera-inc Wow, at the beginning of 2019... 5/14/2020, 3:29:53 AM - sbrl (Starbeamrainbowlabs): Gosh, I've been living under a rock! In that case, we might want to start thinking about moving to GitHub actions for the main tldr repository 5/14/2020, 3:30:10 AM - ivanhercaz (Iván Hernández Cazorla): > Gosh, I've been living under a rock! > In that case, we might want to start thinking about moving to GitHub actions for the main tldr repository I feel like you at this moment... I will think about it and depending of the decision for the main tldr repository, probably the best could be to standardize GitHub Actions for the rest of repositorios of tldr-pages. 5/14/2020, 3:34:32 AM - MasterOdin (Matthew Peveler): Yeah, you can also set-up workflows for a ton of things, like making a stock reply on new issues and stuff like that 5/14/2020, 3:35:58 AM - MasterOdin (Matthew Peveler): https://help.github.com/en/actions 5/14/2020, 3:36:23 AM - MasterOdin (Matthew Peveler): I'd be happy to help move any and all repos from Travis to GH actions 5/14/2020, 3:38:17 AM - ivanhercaz (Iván Hernández Cazorla): Nice! Thank you for the offer @MasterOdin. If in the future the ExTldr repository would be moved from Travis to GH Actions, I will open an issue for this task and mention you. Probably you could give very good advices to set-up it. 5/14/2020, 3:55:58 AM - sbrl (Starbeamrainbowlabs): That's interesting that you can comment on GH issues directly from an action: We currently use a bot for that 5/14/2020, 3:56:09 AM - sbrl (Starbeamrainbowlabs): Definitely worth opening an issue to discuss that one 5/14/2020, 3:56:21 AM - MasterOdin (Matthew Peveler): you can trigger a workflow on pretty much any action on GH 5/14/2020, 3:58:16 AM - ivanhercaz (Iván Hernández Cazorla): > That's interesting that you can comment on GH issues directly from an action: We currently use a bot for that This may reduce the effort in the maintenance of another tools, like the bot. It sound like a new issue... 🎉 5/14/2020, 4:00:44 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): GH actions are pretty interesting. For simple projects, porting is seamless, too. 5/14/2020, 4:01:25 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Most of the projects still use Travis or other solutions out of pure convenience. 5/14/2020, 7:34:32 AM - ivanhercaz (Iván Hernández Cazorla): @principis @sbrl, issue about the inactive and unmaintained clients opened (tldr-pages/tldr#4044). 5/15/2020, 2:43:00 AM - ivanhercaz (Iván Hernández Cazorla): Hi everyone! 5/15/2020, 2:46:51 AM - ivanhercaz (Iván Hernández Cazorla): As someone knows, I am learning Elixir and one of my first steps was to check the available examples for `mix`, the tool to manage the Elixir environment of a project (dependencies, compilations, etcetera). There is a page in `common` directory for this tool, but I was thinking about the possibility to create pages for its subcommands. The mix subcommands are in the style of: `mix deps` get the deps. `mix deps.{{subcommand}}`, where subcommand might be `get` to install all the the dependencies specified in the `mix.exs`, the configuration file. 5/15/2020, 2:49:30 AM - ivanhercaz (Iván Hernández Cazorla): There are another commands with their own subcommands, and there is some cases with interesting examples that sometimes one need to search to know, and I think tldr-pages may help with the task of documenting them in briefly way. One very interesting, for example, is `mix deps.clean --unlock --unused`, to clean the dependencies removed from `mix.exs` but that still installed in the environment. 5/15/2020, 2:50:25 AM - ivanhercaz (Iván Hernández Cazorla): It would be my first time creating pages for subcommands (not just translating) so, should I do for this case? If yes, any advice? 5/15/2020, 3:15:03 AM - sbrl (Starbeamrainbowlabs): Sounds good @ivanhercaz! 5/15/2020, 3:16:13 AM - sbrl (Starbeamrainbowlabs): We've got pages for a few other subcommands if you'd like some references. 5/15/2020, 3:16:16 AM - sbrl (Starbeamrainbowlabs): More info: https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md#subcommands 5/15/2020, 3:17:59 AM - ivanhercaz (Iván Hernández Cazorla): > Sounds good @ivanhercaz! Nice! 5/15/2020, 3:18:31 AM - ivanhercaz (Iván Hernández Cazorla): > We've got pages for a few other subcommands if you'd like some references. Yes... I remember fine my Spanish translation of `git` very well haha. 5/15/2020, 3:18:53 AM - ivanhercaz (Iván Hernández Cazorla): So when I have a bit of time I will begin with this project. 5/15/2020, 3:21:23 AM - ivanhercaz (Iván Hernández Cazorla): If anyone knows about coverage tests, may be you can help me a bit with tldr-pages/extldr#21. Although you do not know Elixir, may be someone could give me an idea of the approach I should consider to achieve the total coverage of both lines. 5/16/2020, 4:00:17 AM - ivanhercaz (Iván Hernández Cazorla): If anyone is interested in tldr-pages/extldr#21, I need opinions about how I should proceed with the current situation of the PR after knows more about how it may be possible to test the raised exceptions for the coverage tests. 5/16/2020, 5:05:44 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Isn't there some kind of a test mockup framework for Elixir (like there is for other languages)? 5/16/2020, 5:06:13 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Although, I'd focus not on testing, but on building the client more. Python client has only a basic render test, that's all about it. 😃 5/16/2020, 5:06:36 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): But the client's functionality is really good. 5/16/2020, 12:54:56 PM - ivanhercaz (Iván Hernández Cazorla): Yes, there are some packages for mockups, the one I am using is Mox. 5/16/2020, 1:20:37 PM - principis (Arthur Bols): Testing is important, but I think it's fine if you only have some basic tests. My client only has some tests if commands run with the correct exit code. But is awesome you're so invested into it! :) 1/14/2023, 3:44:32 PM - czwocvfvqyofpexzrsnoffmmf_gitlab (Doberden Bezopaznestie) joined the room 5/16/2020, 5:49:50 PM - czwocvfvqyofpexzrsnoffmmf_gitlab (Doberden Bezopaznestie): Hi there, what is the recommended workflow to add new commands to the tldr? I found that the `apk` (alpine package manager, often used in docker containers) has no tldr yet. Should I just fork and add it somewhere? 5/16/2020, 6:08:12 PM - sbrl (Starbeamrainbowlabs): [![Selection_047.png](https://files.gitter.im/tldr-pages/tldr/SZKj/thumb/Selection_047.png)](https://files.gitter.im/tldr-pages/tldr/SZKj/Selection_047.png) 5/16/2020, 6:08:15 PM - sbrl (Starbeamrainbowlabs): Hey there, @czwocvfvqyofpexzrsnoffmmf_gitlab! 5/16/2020, 6:08:30 PM - sbrl (Starbeamrainbowlabs): I see a tldr page for `apk`, which client are you using? 5/16/2020, 6:09:13 PM - sbrl (Starbeamrainbowlabs): Anyway, I would recommend checking out the [Contributing guide](https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md) for how to write a page. 5/16/2020, 6:10:15 PM - sbrl (Starbeamrainbowlabs): Then, when you've written a new page, I usually use the "create new file" button in the GitHub web interface, which does the forking for you. If you like using Git locallly on your machine, the workflow there is to fork and create a new branch. 5/16/2020, 6:10:27 PM - sbrl (Starbeamrainbowlabs): Then you can commit the new page, and open a pull request :-) 5/16/2020, 6:10:51 PM - sbrl (Starbeamrainbowlabs): Let us know if there's anything we can help out with! 5/17/2020, 12:46:43 AM - MasterOdin (Matthew Peveler): @here can someone with push rights to pypi help release 1.0.0 of tldr-python-client? 5/17/2020, 12:47:25 AM - MasterOdin (Matthew Peveler): welp, I guess gitter does not work like slack and doing that actually just pings a real person. Sorry person. 5/17/2020, 12:50:00 AM - MasterOdin (Matthew Peveler): alternatively, I'd be happy to work with someone to set-up an automatic release onto pypi through GH actions using a bot user of some sort (be it mine (https://pypi.org/user/Master_Odin_Bot/) or tldr's or whatever) 5/17/2020, 1:20:30 AM - sbrl (Starbeamrainbowlabs): I don't have access, but it would seem sensible perhaps to grant you it 5/17/2020, 1:21:21 AM - MasterOdin (Matthew Peveler): Who does have access? Just @felixonmars? 5/17/2020, 1:57:47 AM - sbrl (Starbeamrainbowlabs): I don't know. @agnivade? 5/17/2020, 8:10:42 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I closed #4052, but keep an eye on it. It may need to be locked as well. 5/17/2020, 8:11:21 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): The author opened several similar discussions that are supposed to make some heat, and almost all got instantly locked. 5/17/2020, 8:34:30 PM - MasterOdin (Matthew Peveler): He really likes to come in hot to discussions 5/17/2020, 8:47:20 PM - sbrl (Starbeamrainbowlabs): Hrm, that's a bizzare issue there @zdroid 5/17/2020, 8:47:37 PM - sbrl (Starbeamrainbowlabs): Have we had an issue opened by that person before? 5/17/2020, 10:01:52 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I hope not 😃 5/18/2020, 1:43:57 AM - MasterOdin (Matthew Peveler): what was the comment they made in #1192? 5/18/2020, 1:45:57 AM - sbrl (Starbeamrainbowlabs): I can't see one in #1192 @MasterOdin 5/18/2020, 1:46:05 AM - sbrl (Starbeamrainbowlabs): tbh I'm really confused by the whole thing 5/18/2020, 1:46:24 AM - MasterOdin (Matthew Peveler): "@tldr-pages tldr-pages deleted a comment from kolokd 1 hour ago" 5/18/2020, 1:46:45 AM - MasterOdin (Matthew Peveler): They made a comment, and it was deleted. I'm curious to know what it might have been. 5/18/2020, 1:47:01 AM - sbrl (Starbeamrainbowlabs): Ah, I see 5/18/2020, 1:47:11 AM - sbrl (Starbeamrainbowlabs): @zdroid? 5/18/2020, 1:47:31 AM - sbrl (Starbeamrainbowlabs): (I haven't yet checked by GH notifications today, 'cause I'm currently implementing the haversine formula in Bash for a thing) 5/18/2020, 2:46:50 AM - principis (Arthur Bols): lol in bash of all things.... good luck 5/18/2020, 2:53:37 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl use something handy like Julia, and just use Bash to execute it with julia -e "expression" 5/18/2020, 2:54:04 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): That comment was something insultive, but I am fairly disinclined to remember such things 5/18/2020, 2:54:10 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): so I already forgot what the original content was 5/18/2020, 2:54:29 AM - sbrl (Starbeamrainbowlabs): Ah, np @zdroid 5/18/2020, 2:54:33 AM - sbrl (Starbeamrainbowlabs): Also, too late lol 5/18/2020, 2:54:33 AM - sbrl (Starbeamrainbowlabs): https://ybin.me/p/b34ac0ad6d8c8165#lBKBUIlsO11jNwXo21StxYghZ1ScXCM8fUypC/S3jHQ= 5/18/2020, 2:55:11 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): poor you 5/18/2020, 2:56:26 AM - sbrl (Starbeamrainbowlabs): Eh, it wasn't so bad Off-topic, but I'm heading towards writing a bash client for the open street maps reverse geocoding API that caches locally and writes the result back to jpeg exif data 5/18/2020, 2:56:34 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): With Julia it is as simple as x=5; julia -E "(1 - cos($x))/2" 5/18/2020, 2:56:37 AM - sbrl (Starbeamrainbowlabs): just for fun 5/18/2020, 2:56:43 AM - sbrl (Starbeamrainbowlabs): Oh, cool 5/18/2020, 2:57:00 AM - sbrl (Starbeamrainbowlabs): I don't have Julia installed though, and I'd prefer something portable in this instance 5/18/2020, 2:57:06 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I recently started using that language as a replacement for both Python and C++ 5/18/2020, 2:57:12 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Since it has features of both 5/18/2020, 2:57:26 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): You are Ubuntu user right? 5/18/2020, 2:57:47 AM - sbrl (Starbeamrainbowlabs): Oh that's interesting Must be a weird language to have features of both Python & C++ Most oft he time yeah 5/18/2020, 2:57:47 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Debian team maintains the package, just sudo apt install julia 5/18/2020, 2:57:53 AM - sbrl (Starbeamrainbowlabs): ah, cool 5/18/2020, 2:58:18 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It's a dream of programmers who wanted it all, or so the authors said 5/18/2020, 2:58:22 AM - sbrl (Starbeamrainbowlabs): This script is going in my bin folder though, so I'm going for portable to lessen the setup hassle 5/18/2020, 2:58:27 AM - sbrl (Starbeamrainbowlabs): Hrm, interesting 5/18/2020, 2:58:33 AM - sbrl (Starbeamrainbowlabs): might be worth a look then 5/18/2020, 2:58:49 AM - sbrl (Starbeamrainbowlabs): Currently still learning Rust though, so it might hafta get in the queue 😛 5/18/2020, 2:59:14 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It has better REPL than Lisp, more straight-forward syntax than Python, but with the speed of ~1-10x of C 5/18/2020, 2:59:23 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): If you do research, it's just perfect 5/18/2020, 2:59:33 AM - sbrl (Starbeamrainbowlabs): O.O Faster than C is a very bold claim 5/18/2020, 2:59:47 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I meant 1-10x times slower 5/18/2020, 3:04:02 AM - sbrl (Starbeamrainbowlabs): Ah 5/18/2020, 10:50:14 AM - agnivade (Agniva De Sarker): I don't have access to pypi. 5/18/2020, 10:50:47 AM - agnivade (Agniva De Sarker): It was a similar case with the node-client too. Only Igor had push rights to npm, but I got a hold of his mail address and got the credentials. 5/18/2020, 10:51:06 AM - agnivade (Agniva De Sarker): If Felix is not active anymore, I think we might need a way to contact him and get the credentials. 5/18/2020, 11:17:53 AM - MasterOdin (Matthew Peveler): easy enough, listed right in his GH profile (https://github.com/felixonmars): felixonmars@archlinux.org 5/18/2020, 1:09:41 PM - czwocvfvqyofpexzrsnoffmmf_gitlab (Doberden Bezopaznestie): > I see a tldr page for `apk`, which client are you using? I was using tldr.io 5/18/2020, 2:34:25 PM - owenvoke (Owen Voke): Ah, tldr.ostera.io requires the OS for non-common pages. So it would be `linux/apk` (https://tldr.ostera.io/linux/apk) 5/18/2020, 5:47:52 PM - principis (Arthur Bols): Sorry, I had something in my clipboard lol 5/18/2020, 5:48:20 PM - principis (Arthur Bols): is kolokd spamming us? 5/18/2020, 6:17:03 PM - sbrl (Starbeamrainbowlabs): Hard to say @principis It could be a case of misunderstanding 5/18/2020, 6:21:30 PM - principis (Arthur Bols): Maybe 😕 I looked into some of his/her posts and he's in most of them very unrespectful and commanding towards others. For example https://github.com/sveltejs/site-kit/pull/19 5/18/2020, 7:39:00 PM - sbrl (Starbeamrainbowlabs): Hrm, that's good to know @principis 5/18/2020, 10:17:36 PM - sbrl (Starbeamrainbowlabs): Ah, I see you had to lock #4052 @zdroid 5/18/2020, 10:17:46 PM - sbrl (Starbeamrainbowlabs): It's a shame it had to come to that 5/18/2020, 10:17:53 PM - sbrl (Starbeamrainbowlabs): but thanks for taking action 5/18/2020, 10:18:05 PM - sbrl (Starbeamrainbowlabs): I'd have locked it as too heated, but spam works too 5/19/2020, 3:31:28 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Right, that would have been better. I think I clicked the first thing that came to my mind. 5/19/2020, 3:32:41 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Some of kolokd's comments are actually insightful (saw them in some repositories that I watch). It may just be the case kolokd is very young and impulsive. 5/19/2020, 3:36:09 AM - sbrl (Starbeamrainbowlabs): Yeah, it can be difficult in such situations - I've been there before. Perhaps, yeah. Perhaps some comments they make we can reason with, and only delete / lock later when it gets too heated 5/19/2020, 10:54:24 AM - MasterOdin (Matthew Peveler): @sbrl @agnivade were you folks going to reach out to @felixonmars or do you want me? 5/19/2020, 5:39:18 PM - sbrl (Starbeamrainbowlabs): I thought @agnivade was going to do it 5/19/2020, 7:46:45 PM - schneiderl (Lucas Gabriel Schneider): Hello, I've been out for a few weeks now as I was going through a lot of personal problems. I'm now getting back to contributing to tldr and hope everyone is doing alright on this dark times we are living. 5/19/2020, 8:50:22 PM - sbrl (Starbeamrainbowlabs): No problems @schneiderl - glad you're back 😃 5/19/2020, 8:50:29 PM - sbrl (Starbeamrainbowlabs): hope you're doing better now 5/20/2020, 10:33:33 PM - agnivade (Agniva De Sarker): Oh no sorry for the confusion. Please feel free to reach out to him. 5/28/2020, 1:28:31 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): https://github.com/tldr-pages/tldr-cpp-client 5/28/2020, 1:28:40 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Can somebody proceed to rename this to tldr-c-client as it should be named? 5/28/2020, 1:28:56 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): GitHub sets the redirects so it isn't a breaking change 5/28/2020, 1:36:26 AM - owenvoke (Owen Voke): I'm happy to do that if it's ok with everyone. :+1: 5/28/2020, 1:38:18 AM - owenvoke (Owen Voke): Does someone want to prepare a PR for the Brew repository change as well? 5/28/2020, 1:41:56 AM - sbrl (Starbeamrainbowlabs): Ah yeah, I remember that one. Sure, let's go ahead with that change. 5/28/2020, 1:42:04 AM - sbrl (Starbeamrainbowlabs): I can do it too if @owenvoke doesn't 5/28/2020, 1:42:18 AM - sbrl (Starbeamrainbowlabs): A PR to the Brew repo sounds good too 5/28/2020, 1:44:12 AM - owenvoke (Owen Voke): Also, have the font and icons changed on GitHub? 5/28/2020, 1:44:44 AM - owenvoke (Owen Voke): (I've renamed that repo now) :slight_smile: 5/28/2020, 1:57:28 AM - sbrl (Starbeamrainbowlabs): Yeah, I've noticed that too @owenvoke! 5/28/2020, 1:57:32 AM - sbrl (Starbeamrainbowlabs): They look better I think 5/28/2020, 1:59:11 AM - owenvoke (Owen Voke): Not entirely sure about the brew stuff, went to make a PR but it looks like the hash for the source download isn't right. I can update it I guess, but not sure that it ever worked (I guess most people wouldn't build from source). 5/28/2020, 2:03:44 AM - owenvoke (Owen Voke): Fixed the hash, and opened a PR :+1: https://github.com/Homebrew/homebrew-core/pull/55357 5/28/2020, 2:14:02 AM - sbrl (Starbeamrainbowlabs): Awesome! 5/28/2020, 2:14:09 AM - sbrl (Starbeamrainbowlabs): Looks like 3 of their checked failed though 5/28/2020, 2:14:16 AM - sbrl (Starbeamrainbowlabs): not sure what's up with that 5/28/2020, 2:24:29 AM - owenvoke (Owen Voke): > stable: sha256 changed without the version also changing; please create an issue upstream to rule out malicious circumstances and to find out why the file changed. 5/28/2020, 2:24:46 AM - owenvoke (Owen Voke): Ah, that's because I fixed the sha256 hash that wasn't working. 5/28/2020, 2:25:50 AM - sbrl (Starbeamrainbowlabs): Ah, I see 5/28/2020, 2:26:03 AM - sbrl (Starbeamrainbowlabs): So it looks like merging is going to be more complicated. 5/28/2020, 2:33:28 AM - sbrl (Starbeamrainbowlabs): First! I've opened https://github.com/tldr-pages/.github/pull/1 The very first PR on the .github repo 5/28/2020, 2:33:40 AM - sbrl (Starbeamrainbowlabs): Achievement get 😛 5/28/2020, 2:51:32 AM - sbrl (Starbeamrainbowlabs): Comment on that Homebrew issue: > If it isn't currently building, was the version retagged? And if so, why? 5/28/2020, 2:51:42 AM - sbrl (Starbeamrainbowlabs): Unfortunately I don't know enough to answer 5/28/2020, 2:58:13 AM - MasterOdin (Matthew Peveler): maybe easiest thing would be to cut a release with the stuff @zdroid merged today and change the hash + version at the same time, avoid the whole problem 5/28/2020, 3:22:41 AM - sbrl (Starbeamrainbowlabs): Yeah 5/28/2020, 3:22:47 AM - sbrl (Starbeamrainbowlabs): That sounds like a plan @MasterOdin 5/29/2020, 12:01:36 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): By the way, the C client is very far behind the other clients 5/29/2020, 12:01:53 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It hasn't been maintained for a long while 5/29/2020, 12:02:44 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): It even has some failed-to-rename-a-directory bugs 5/29/2020, 7:35:56 AM - MasterOdin (Matthew Peveler): assuming that Felix does not respond (I'll send a bump email in a few days), the next option I suppose would be https://www.python.org/dev/peps/pep-0541/ and attempt to reclaim tldr via PyPI support 5/29/2020, 7:37:28 AM - MasterOdin (Matthew Peveler): though that's another 6 week wait for them to attempt contact 5/29/2020, 8:34:43 PM - sbrl (Starbeamrainbowlabs): Right. Is there an issue open for this @MasterOdin? It's sounding like we might need one.... 5/29/2020, 9:51:46 PM - MasterOdin (Matthew Peveler): Not yet, was going to give @felixonmars some more time to respond. Will also open an issue first on the tldr-python-client repo as well as that might be a way to ping them 5/29/2020, 10:33:46 PM - sbrl (Starbeamrainbowlabs): Ok, sure thing 6/2/2020, 12:32:25 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Python client's v1.0 has just been published 🎉 6/2/2020, 12:50:56 AM - sbrl (Starbeamrainbowlabs): 🎉 🎊 6/3/2020, 3:13:56 PM - owenvoke (Owen Voke): Also, just a heads up. Homebrew/homebrew-core#55357 was merged, so now it's using the right links and can be built from source in Brew. 6/3/2020, 5:51:09 PM - sbrl (Starbeamrainbowlabs): 🎉 6/6/2020, 11:07:45 PM - psibi (Sibi Prabakaran): I'm planning to update my haskell client to support the language option and I'm going through the client specification: https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#language I'm not entirely sure about how it has to be handled. For example, this is my current system's environment variable: ``` $ echo $LANG en_US.utf8 ``` So how should should I check the pages directory ? How are other client developers checking it ? 6/6/2020, 11:11:17 PM - MasterOdin (Matthew Peveler): The python client takes `LANG` (or the list of languages in `LANGUAGES`) and splits on `_`, and taking the first item of the resulting array. If `C`, then use `en`. Then, when we go to look up the file (either local cache or web), in pseudo-python: ``` url = 'pages' if lang != 'en': url += lang ``` 6/6/2020, 11:11:50 PM - MasterOdin (Matthew Peveler): we're currently debating whether or not to always include English or not on look-up given the state of overall translation of tldr, where we currently do not, so if say `LANG=nl`, we just return a message saying no page could be found. 6/6/2020, 11:15:31 PM - psibi (Sibi Prabakaran): Thanks, that's helpful. But I'm concerned about the inefficiency: doing file system calls each time. 6/6/2020, 11:17:59 PM - MasterOdin (Matthew Peveler): Depending on how you do caching, or whatever, you could parse https://tldr.sh/assets/index.json for the supported languages / platforms for a command 6/6/2020, 11:18:10 PM - psibi (Sibi Prabakaran): Also, according to the standards, it seems the locale can be even `en-US` (`-` instead of `_`). So I'm not sure if it's right. 6/6/2020, 11:23:34 PM - MasterOdin (Matthew Peveler): what standard? I believe that except for a few exceptions (`C`, `POSIX`), the list of valid settings for `LANG` are all of `xx_YY` 6/6/2020, 11:36:48 PM - sbrl (Starbeamrainbowlabs): It should be a standard that we're following there. 6/6/2020, 11:37:03 PM - sbrl (Starbeamrainbowlabs): Doesn't haskell have a language code parsing library? 6/7/2020, 12:07:52 AM - agnivade (Agniva De Sarker): There are competing standards- BCP-47 and POSIX. We started with BCP-47 and then pivoted to POSIX. POSIX doesn't need a library really. It's basically `ll_CC.UTF8`. https://en.wikipedia.org/wiki/Locale_(computer_software)#POSIX_platforms 6/7/2020, 12:09:19 AM - agnivade (Agniva De Sarker): Feel free to check https://github.com/tldr-pages/tldr-node-client/blob/master/lib/index.js as an example implementation 6/7/2020, 1:41:21 PM - psibi (Sibi Prabakaran): @agnivade Thanks, that's helpful. One thing I observed in the nodejs client is that we aren't reading the `LANGUAGES` and `LC_MESSAGES` environment variable if `LANG` is empty ( Ref: https://github.com/tldr-pages/tldr-node-client/blob/4da9d7b4867e10d323c00fe1219b618b908157fb/lib/cache.js#L25 ) as opposed to how the client specification document specifies. Am I missing something or is that intended ? 6/8/2020, 2:19:38 PM - agnivade (Agniva De Sarker): It's just a lack of complete implementation of the spec. The `LANG` variable is present in almost all systems, so I did not yet implement that. PRs are welcome. 6/8/2020, 3:38:10 PM - psibi (Sibi Prabakaran): Cool. That's good to know! 6/9/2020, 3:45:31 PM - owenvoke (Owen Voke): Did we come to a decision about looking into GitHub Actions for CI? I remember it being mentioned at some point. 6/9/2020, 4:25:31 PM - mebeim (Marco Bonelli): I don't think so 6/9/2020, 4:27:49 PM - owenvoke (Owen Voke): Ah ok, I've just been having a look into it and there are some features that Travis has that aren't as clean/easy to do in GitHub Actions. 6/9/2020, 6:22:14 PM - sbrl (Starbeamrainbowlabs): Oh interesting Yeah, we didn't come to a decision on that 6/9/2020, 6:22:49 PM - sbrl (Starbeamrainbowlabs): IIRC there was an announcement about Travis that made us want to switch away, but I can't remember? My memory is all fuzzy 6/9/2020, 7:23:32 PM - MasterOdin (Matthew Peveler): probably https://techcrunch.com/2019/01/23/idera-acquires-travis-ci/ 6/9/2020, 7:33:09 PM - owenvoke (Owen Voke): Ah yep, that's the one. :+1: I've started a branch for it, looks like there are 2 env variables in Travis that I'm trying to work out how to do in GitHub Actions. - `TRAVIS_PULL_REQUEST` (the id of the pull request, can be extracted from `GITHUB_REF`) - `TRAVIS_COMMIT_RANGE` (the range of commits, used in the deploy script) 6/9/2020, 7:56:26 PM - owenvoke (Owen Voke): I've opened #4097 to allow for better discussion. :+1: 6/9/2020, 8:30:25 PM - sbrl (Starbeamrainbowlabs): :+1: 6/9/2020, 9:06:41 PM - MasterOdin (Matthew Peveler): PR opened on node client to convert it over as I forgot I had started that a few weeks ago. 6/9/2020, 10:47:34 PM - owenvoke (Owen Voke): Nice! 6/11/2020, 7:58:44 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Since the project's name and description were finally standardized, all tldr-pages org clients and web site should use the standard form now. 6/11/2020, 8:02:35 PM - sbrl (Starbeamrainbowlabs): What was the description we need to change the main tldr repo to @zdroid? 6/11/2020, 8:02:38 PM - sbrl (Starbeamrainbowlabs): I can't find it 6/11/2020, 9:07:26 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): see https://github.com/tldr-pages/tldr/pull/4084#issuecomment-642725838 for the discussion 6/11/2020, 9:09:59 PM - sbrl (Starbeamrainbowlabs): Looks like someone's already updated it 6/11/2020, 9:10:49 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): Yes but not to what @waldyrious and I had in mind 6/11/2020, 9:11:26 PM - sbrl (Starbeamrainbowlabs): There are multiple suggestions there - I'm confused as to which one was the right one 6/11/2020, 9:11:32 PM - sbrl (Starbeamrainbowlabs): evidently others were too 6/11/2020, 10:23:16 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I always understood it's just one description, that's what the PR was aimed at 😛 6/11/2020, 10:23:50 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): The text in readme was never a description in the first place. 6/11/2020, 10:24:05 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl Can you change the org's description to match the repository's? 6/11/2020, 10:24:25 PM - sbrl (Starbeamrainbowlabs): sure thing 6/11/2020, 10:25:41 PM - sbrl (Starbeamrainbowlabs): done 6/11/2020, 10:30:33 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): great 6/11/2020, 10:31:23 PM - sbrl (Starbeamrainbowlabs): np 6/11/2020, 10:31:32 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): although it's the wrong one 😆 6/11/2020, 10:31:55 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): agnivade fixed the repo's to be "Collaborative cheatsheets for console commands" 6/11/2020, 10:32:01 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): that's what org's should be too 6/11/2020, 10:32:15 PM - sbrl (Starbeamrainbowlabs): right 6/11/2020, 10:32:20 PM - sbrl (Starbeamrainbowlabs): I'll do that now 6/11/2020, 10:32:22 PM - sbrl (Starbeamrainbowlabs): for the org 6/11/2020, 10:32:44 PM - sbrl (Starbeamrainbowlabs): done 6/11/2020, 10:33:12 PM - sbrl (Starbeamrainbowlabs): [![Selection_058.png](https://files.gitter.im/tldr-pages/tldr/2XD1/thumb/Selection_058.png)](https://files.gitter.im/tldr-pages/tldr/2XD1/Selection_058.png) 6/11/2020, 10:33:13 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): now it's perfect 6/11/2020, 10:33:18 PM - sbrl (Starbeamrainbowlabs): 😃 6/12/2020, 10:22:04 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @waldyrious @sbrl One more thing... the image should be updated in Settings -> Social preview of the repository 6/12/2020, 10:22:19 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I.e. that image you will see on expanded link on Facebook, Twitter, forums 6/12/2020, 11:50:30 PM - sbrl (Starbeamrainbowlabs): Oh, I'd forgotten about the image 6/12/2020, 11:51:32 PM - sbrl (Starbeamrainbowlabs): I can't remember what we decided to change it to? 6/13/2020, 2:20:42 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl I assume the one in the readme, as it was similar to that before 6/13/2020, 2:20:53 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): I shared a link on FB and found it's like that 6/13/2020, 2:49:52 AM - owenvoke (Owen Voke): https://metatags.io is usually good for testing those previews. :+1: 6/13/2020, 3:06:27 AM - sbrl (Starbeamrainbowlabs): There's https://github.com/tldr-pages/tldr/blob/master/images/logo.png 6/13/2020, 3:06:30 AM - sbrl (Starbeamrainbowlabs): in the main repo 6/13/2020, 3:06:43 AM - sbrl (Starbeamrainbowlabs): but I'd assume we'd want a cropped version for the org avatar? 6/13/2020, 3:15:17 AM - principis (Arthur Bols): > see https://github.com/tldr-pages/tldr/pull/4084#issuecomment-642725838 for the discussion I'm actually a bit confused. According to [LANGUAGE](https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html) it may be preferred over LANG but we choose to prefer LANG over LANGUAGE, correct? 6/13/2020, 4:16:37 AM - MasterOdin (Matthew Peveler): node client only uses LANG, python client uses LANGUAGE, but sorts the value of `LANG` to the front of attempted languages 6/13/2020, 4:30:39 PM - principis (Arthur Bols): I do the same as the python client, thank you. I also think that's the best option 6/13/2020, 5:26:42 PM - sbrl (Starbeamrainbowlabs): @principis oh, oops! That sounds like a spec issue. We.ve got an open PR against the spec at the moment - could you comment on there about that please? 6/13/2020, 6:55:40 PM - principis (Arthur Bols): woops I've quoted the wrong pr 6/13/2020, 7:26:40 PM - principis (Arthur Bols): I commented on the PR 6/13/2020, 7:41:50 PM - sbrl (Starbeamrainbowlabs): ty 6/21/2020, 7:19:12 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @sbrl can you check https://github.com/tldr-pages/tldr/issues/4113 6/22/2020, 1:46:56 AM - sbrl (Starbeamrainbowlabs): Sure 6/22/2020, 1:47:06 AM - sbrl (Starbeamrainbowlabs): Haha well done for spotting that 6/22/2020, 1:47:57 AM - sbrl (Starbeamrainbowlabs): @owenvoke / @mebiem / @agnivade - is everyone in agreement on adding @zdroid as an owner? I can do it if everyone agrees. 6/22/2020, 12:28:08 PM - owenvoke (Owen Voke): I think that's a great idea. :+1: 6/22/2020, 6:23:39 PM - sbrl (Starbeamrainbowlabs): Yeah! I'll add @zdroid then 6/22/2020, 6:23:56 PM - sbrl (Starbeamrainbowlabs): just wanted more than just 1 owner to agree to add another owner 6/25/2020, 1:52:59 PM - principis (Arthur Bols): Which client do windows users typically use? 6/25/2020, 3:02:31 PM - owenvoke (Owen Voke): I've tended to use the Node one on all platforms. Seems to work well on Windows. 6/25/2020, 4:49:44 PM - mebeim (Marco Bonelli): That's an interesting question, I personally know 0 people who use tldr on windows (and just a few tho use windows at all) 6/25/2020, 4:53:48 PM - mebeim (Marco Bonelli): NB: I am not classifying WSL as windows 6/25/2020, 6:10:34 PM - sbrl (Starbeamrainbowlabs): I'm a linux user myself, not sure. Both the Python and Node.js clients should work well on Windows IIRC 6/26/2020, 1:41:25 PM - owenvoke (Owen Voke): I think #4125 is finally ready. :+1: Anyone mind having a look over it when they get the chance? :slight_smile: 6/26/2020, 2:33:27 PM - mebeim (Marco Bonelli): I'll check this evening 6/26/2020, 2:35:59 PM - mebeim (Marco Bonelli): Please don't merge before then 6/26/2020, 5:03:13 PM - owenvoke (Owen Voke): No problem @mebeim :+1: 6/27/2020, 3:46:51 PM - mebeim (Marco Bonelli): @owenvoke do you know if there is a way of passing stuff from one workflow to the other? I was thinking about the "splitting" that I suggested in #4125... that would require a way of passing the generated zip file from the "CI" workflow to another "Deploy" workflow, or re-building it from scratch (which seems annoying). 6/27/2020, 3:47:39 PM - mebeim (Marco Bonelli): I have a feeling that this file passing from a workflow to another cannot be done... that would make your suggestion of checking `github.ref == 'refs/heads/master'` the way to go. 6/27/2020, 5:20:36 PM - owenvoke (Owen Voke): I don't think it can be done as they are in separate runners. You can split the job in the same runner and have it depends on the first, but that doesn't really help us. 6/27/2020, 5:21:35 PM - mebeim (Marco Bonelli): @owenvoke yeah exactly what I was thinking. We'll use your suggestion then. 6/27/2020, 5:23:15 PM - mebeim (Marco Bonelli): I find it really strange that GitHub Actions don't provide such basic information like the branch name or the PR number in an easy way. 6/27/2020, 6:02:23 PM - mebeim (Marco Bonelli): Regarding https://github.com/tldr-pages/tldr/pull/4082 is there a way to check if a specific email has signed the CLA? 6/27/2020, 7:31:38 PM - mebeim (Marco Bonelli): Anyway give this a check+merge when you can folks https://github.com/tldr-pages/tldr/pull/4130 6/27/2020, 7:32:01 PM - mebeim (Marco Bonelli): We *should* have successfully migrated to GitHub Actions 6/27/2020, 7:32:30 PM - sbrl (Starbeamrainbowlabs): Approved 😃 6/27/2020, 10:59:26 PM - mebeim (Marco Bonelli): Nice it's merged now. FYI: existing PRs that were done before the transition to GH pages need to be merged using with admin power since the check cannot run on those (unless the author does a rebase of the branch). 6/27/2020, 11:01:15 PM - sbrl (Starbeamrainbowlabs): right. I haven't checked my GH notifications yet today (though I plan to) 6/27/2020, 11:11:33 PM - mebeim (Marco Bonelli): Whelp I said GH pages I meant GH actions of course 😅 6/28/2020, 10:05:17 PM - psibi (Sibi Prabakaran): New Haskell client release supporting the locale (-L) feature: https://github.com/psibi/tldr-hs/releases/tag/v0.7.0 Also, we are back to providing static binary for Linux platforms from this release. Thanks to the tldr team for answering my questions here! 6/29/2020, 4:02:35 AM - waldyrious (Waldir Pimenta): Pheww.... I just finished reading my backlog for this channel, from the past six months 🙈 6/29/2020, 4:02:47 AM - waldyrious (Waldir Pimenta): I apologize for not responding to a few mentions 6/29/2020, 4:16:40 AM - waldyrious (Waldir Pimenta): I just want to say that it really warms my heart to see all the kind and thoughtful comments and discussions that were had here and in issues linked from here, on delicate subjects such as the hastiness in closing old issues, the need for careful reviews of PRs rather than approving/merging asap, and the difficult balance of expediting reviews vs. overstepping contributors. I'm particularly proud to read @mebeim's response to notpeter in #3755, and @agnivade's response to Laura in #3802. Amidst all the harshness and gatekeeping that is unfortunately more common than it should in open source communities, I must say that tldr-pages sometimes feels like an oasis where we managed to keep a warm, forgiving, considerate and welcoming culture over the years, even when (especially when) we make mistakes and upset contributors. I'm really proud of being part of this group! ❤️ 6/29/2020, 4:25:51 AM - sbrl (Starbeamrainbowlabs): ❤️ 6/29/2020, 4:35:39 AM - waldyrious (Waldir Pimenta): @sbrl I'm writing something for you btw, in the title-case issue where I failed to show up. Sorry! 6/29/2020, 4:36:26 AM - sbrl (Starbeamrainbowlabs): Oh thanks! No problem :-) I don't remember which issue that was, but I'll be sure to check it out in my notifications :-) 6/29/2020, 4:40:17 AM - waldyrious (Waldir Pimenta): I'll post a link in a bit :) 6/29/2020, 4:40:56 AM - sbrl (Starbeamrainbowlabs): ty 6/29/2020, 4:47:14 AM - waldyrious (Waldir Pimenta): Here you go: https://github.com/tldr-pages/tldr/pull/3716#issuecomment-650835676 6/29/2020, 5:25:39 PM - mebeim (Marco Bonelli): Thanks Waldir ❤️ 6/29/2020, 6:38:30 PM - sbrl (Starbeamrainbowlabs): Thanks ♥ 1/14/2023, 3:46:00 PM - RH-sdavey (RH-sdavey) joined the room 7/1/2020, 5:47:35 PM - RH-sdavey (RH-sdavey): hello all, Im currently updating my PR for new page zgrep , https://github.com/tldr-pages/tldr/pull/4131 based on comments (thanks for them) , qq... I am putting braces around the variables there, and qq.. on line 23 I have this line `zgrep -e "pattern_1" -e "pattern_2" path/to/compressed/file` do the braces go outside or inside the " please ? 7/1/2020, 5:54:27 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): @RH-sdavey check https://github.com/tldr-pages/tldr/blob/master/pages/common/grep.md 7/1/2020, 5:55:24 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): and https://github.com/tldr-pages/tldr/pull/4096/files 7/1/2020, 5:55:51 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): it probably should be just zgrep -e {{pattern_1}} ... 7/1/2020, 5:56:06 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost): can somebody review https://github.com/tldr-pages/tldr/pull/4126? it's a simple change 7/1/2020, 6:01:53 PM - agnivade (Agniva De Sarker): Thanks for the thoughtful comment Waldir! I completely agree with your sentiment. I feel that somehow we are tremendously lucky to have preserved the warm and considerate culture over such a long time. 7/1/2020, 7:18:13 PM - waldyrious (Waldir Pimenta): I'm glad you feel the same! :) 7/1/2020, 7:20:13 PM - sbrl (Starbeamrainbowlabs): Oops @zdroid, I've commented there 7/1/2020, 7:20:28 PM - sbrl (Starbeamrainbowlabs): need to go through my GH notifications again 7/2/2020, 7:07:12 PM - owenvoke (Owen Voke): Looking into the additional GitHub Actions for maintenance. Anything that would be good to add? So far I'm planning on doing one for stale bot, and one for doing the maintenance (e.g. creating issues for new maintainers, etc.) 7/2/2020, 7:14:24 PM - sbrl (Starbeamrainbowlabs): Sounds good! One for maintenance of roles would be great to remind us when a contributor has 10 PRs etc 7/2/2020, 7:15:00 PM - sbrl (Starbeamrainbowlabs): I didn't know that you could use GH actions to clean up stale PRs, but that sounds like a good idea too 7/2/2020, 7:22:52 PM - owenvoke (Owen Voke): :+1: Yeah, we can't move over to the Stale one yet as it doesn't support posting a message on closure. But I might try and add support for that. 7/2/2020, 7:31:12 PM - sbrl (Starbeamrainbowlabs): Ah, I see! No problem. 7/2/2020, 9:35:44 PM - waldyrious (Waldir Pimenta): I'd love to see some automation in the role transitions! It's an area where many open source projects are lacking (onboarding and encouraging new contributors and maintainers) 7/2/2020, 9:36:41 PM - sbrl (Starbeamrainbowlabs): yeah 7/2/2020, 9:45:15 PM - owenvoke (Owen Voke): Just opened a PR for the Stale Action comment updates. actions/stale#99 7/2/2020, 9:47:51 PM - sbrl (Starbeamrainbowlabs): Oh wow nice - you opened the PR against the GH action itself! I went to label it, and found I didn't have permission lol 7/2/2020, 11:07:55 PM - owenvoke (Owen Voke): Yeah. :+1: 7/10/2020, 1:33:08 AM - sbrl (Starbeamrainbowlabs): Woah, #2835 was updated 7/10/2020, 1:33:41 AM - sbrl (Starbeamrainbowlabs): there's the possibly of an _enormous_ review job coming our way 7/10/2020, 3:32:46 AM - waldyrious (Waldir Pimenta): Commented there @sbrl. Sounds like a pretty interesting challenge :) and nice of them to contribute back upstream! 7/10/2020, 3:33:18 AM - sbrl (Starbeamrainbowlabs): Yeah! It's pretty exciting to have the possibility of a large contribution like that 😃 7/13/2020, 12:25:21 AM - MasterOdin (Matthew Peveler): Assuming people are fine with the table of how `LANGUAGE` and `LANG` shake out, could we maybe see https://github.com/tldr-pages/tldr/pull/4101 get merged with rewords happening in follow-up PRs (as simple rewords would not require a new specification version)? 7/13/2020, 12:30:11 AM - sbrl (Starbeamrainbowlabs): /cc @mebeim 7/13/2020, 2:13:30 AM - mebeim (Marco Bonelli): Sorry I was busy this week, I would really like to apply the change before it gets merged. I should be able to do it tomorrow (i.e. around 18:00-20:00 CEST). If I don't then feel free to merge and I'll do this in another PR. 7/15/2020, 1:17:57 PM - owenvoke (Owen Voke): Looks like the Stale Action ran successfully. :+1: Hasn't done anything yet as there aren't any issues to mark as stale/close, but the log output looks correct. 7/15/2020, 5:43:28 PM - sbrl (Starbeamrainbowlabs): Awesome! 7/15/2020, 9:52:58 PM - mebeim (Marco Bonelli): Nice 7/17/2020, 2:17:44 AM - sbrl (Starbeamrainbowlabs): dependabot has found a security issue in tldr-node and opened a PR: https://github.com/tldr-pages/tldr-node-client/pull/309?notification_referrer_id=MDE4Ok5vdGlmaWNhdGlvblRocmVhZDk5NjI5ODE3MDo5OTI5NzM3¬ifications_query=repo%3Atldr-pages%2Ftldr-node-client 7/17/2020, 2:55:54 AM - sbrl (Starbeamrainbowlabs): Hrm, I think GH's times on comments has gone weird again. 7/17/2020, 3:41:14 AM - owenvoke (Owen Voke): :+1: Yeah, I was looking at that earlier. But the CI failed. 7/17/2020, 3:41:51 AM - owenvoke (Owen Voke): Also, going to try and look into a GitHub Action for maintainer promotion, etc. soon. 7/17/2020, 3:43:31 AM - sbrl (Starbeamrainbowlabs): Ah, np Oh that would be cool! 7/17/2020, 3:43:44 AM - sbrl (Starbeamrainbowlabs): That would definitely help 7/17/2020, 3:44:04 AM - sbrl (Starbeamrainbowlabs): as it's difficult to keep track of who's made how many PRs 7/18/2020, 1:35:27 PM - agnivade (Agniva De Sarker): Did the CI of that dependabot PR run correctly? When I saw it, there were some failures. That's why I didn't merge it at that time. 7/18/2020, 3:24:33 PM - owenvoke (Owen Voke): No it was failing which is why I left it as well. Looks like it failed when it was merged as well. 🤔 7/18/2020, 3:25:45 PM - owenvoke (Owen Voke): Just triggered a re-run of the CI to check if it was a temporary issue. 7/18/2020, 3:27:39 PM - owenvoke (Owen Voke): Looks like it was. :+1: https://github.com/tldr-pages/tldr-node-client/runs/884676292 7/21/2020, 8:40:08 AM - morrme (morrme): i haven't been on this in years, just saying hi to everyone! great to see so much work and so many of the same 'faces' from before! if i can help, i'm happy to pitch in! 7/21/2020, 6:11:57 PM - sbrl (Starbeamrainbowlabs): Hi @morrme! Great to hear from you. We'd love it if you'd like to pitch in 😃 7/22/2020, 2:05:43 AM - sbrl (Starbeamrainbowlabs): If you're stuck for inspiration, we've got a number of open issues about requested pages. I've also implemented a script for Linux systems that detects pages that haven't been written based on your shell history: https://github.com/tldr-pages/tldr/wiki/Useful-scripts-and-programs#find-pages-that-dont-exist 7/22/2020, 2:06:13 AM - sbrl (Starbeamrainbowlabs): _(@zdroid, you might want to check #3648 - I've left a present 😛)_ 1/14/2023, 3:46:15 PM - roeniss (Roeniss Moon) joined the room 7/23/2020, 9:04:12 PM - roeniss (Roeniss Moon): Hello everyone! Today, Some idea that can improve our `tl;dr` just came to me. Can I make it as a issue on github or should I post it to here first? It's not obvious which way should I take when I looked at contribution guide! 7/23/2020, 9:05:15 PM - mebeim (Marco Bonelli): What's it about? 7/23/2020, 9:05:47 PM - mebeim (Marco Bonelli): It's fine either way I think. If it's just a minod doubt/question then you can just ask here. 7/23/2020, 9:06:06 PM - mebeim (Marco Bonelli): *minor 7/23/2020, 9:06:25 PM - mebeim (Marco Bonelli): Otherwise feel free to open an Issue 7/23/2020, 9:13:24 PM - roeniss (Roeniss Moon): well, then I'll choose you Marco! :) shortly, how about this feature : **personal note**! I think that `tldr''s mighty power came from 'common', 'useful', 'carefully chosen' commands. But as a user, some commands are not on the chosen commands list even though I used them alot. Of course each time I searched because it's not that... worth to memory (a little contradictory, yeah) So, If each person can make a note with command and args for themselves to a specific commands, it would be useful. Every time they typed `tldr xxx`, their commands will be on there with commands which was suggested by tldr community. 7/23/2020, 9:15:47 PM - roeniss (Roeniss Moon): It could be a little/more not what tldr is for, but I think this feature may be appropriate for `tl;dr` in that both are for useful for themselves. if such a discussion was there before, please reference it! 7/23/2020, 10:13:46 PM - psibi (Sibi Prabakaran): I do like this idea. 7/23/2020, 10:14:48 PM - psibi (Sibi Prabakaran): Probably each command could optionally have an extra page associated with it `ls-extra.md` and have optional flags for viewing it. Eg: `tldr ls --extra`. 7/23/2020, 10:25:19 PM - sbrl (Starbeamrainbowlabs): This sounds like a client-specific feature to me, since the main tldr-pages/tldr repo is just for the official pages themselves 7/23/2020, 10:27:58 PM - sbrl (Starbeamrainbowlabs): So perhaps it would be worth looking at implementing the feature in a client first I believe similar suggestions have been made in the past - see #3269 for an example 7/23/2020, 10:42:16 PM - roeniss (Roeniss Moon): @psibi Thank you for feedback! everything you mentioned is great! @sbrl You are right! the word "client-specific" is perfect for what I said. And, #3269 is just what I try to illustrate! But looks like `tldr-node-client` does not fit in well because it's actually 'change' but not 'add' repository(command list). I'd better go there then dig in for insight. Thank you for referencing! 7/23/2020, 10:46:51 PM - sbrl (Starbeamrainbowlabs): Yeah. The problem is that such a private repository might have duplicate pages. In this case, how does one know which page to pick? Does the private one take precedence? Or perhaps the official one? 7/24/2020, 5:50:21 AM - roeniss (Roeniss Moon): @sbrl I'm currently not sure but let me explain. I imagined two kinds of solution for that. One is recommendation/ranking, the other is randomize. 7/24/2020, 5:51:12 AM - sbrl (Starbeamrainbowlabs): Yeah, I think some kind of ranking system is required, but I'm unsure as to whether that should be a core spec thing, or a client-specific feature 7/24/2020, 5:51:19 AM - sbrl (Starbeamrainbowlabs): I'm currently inclined to think the latter 7/24/2020, 5:51:50 AM - roeniss (Roeniss Moon): - recommendation/ranking : if people share or make public their own pages, we might be able to measure which one is more frequent, and of course, useful these days. 7/24/2020, 5:52:53 AM - roeniss (Roeniss Moon): ah ha. I got it.Ok then I'll check that tldr-node-client side first. One day I think this is not enough (lol) I'll find you then! 7/24/2020, 5:53:23 AM - roeniss (Roeniss Moon): but for now, as you said, it doesn't look like core-thing. 7/24/2020, 6:31:25 AM - sbrl (Starbeamrainbowlabs): sure thing! It's just a case of finding a way that works for everyone. Good luck! 7/25/2020, 12:49:32 AM - sbrl (Starbeamrainbowlabs): Looks like the GitHub Actions is working @owenvoke: https://github.com/tldr-pages/tldr/pull/4096#issuecomment-662167184 7/25/2020, 12:49:47 AM - sbrl (Starbeamrainbowlabs): 😃 7/25/2020, 2:03:54 AM - owenvoke (Owen Voke): Great! I'm glad it worked. :+1: 7/25/2020, 2:05:22 AM - owenvoke (Owen Voke): Hmm. Wonder if we can make it post the comment as tldr-bot. Or if I can make a PR to allow that in `actions/stale`. 7/25/2020, 2:11:40 AM - owenvoke (Owen Voke): Looks like you can, but we'd need to add a PAT token from the `tldr-bot` account. https://github.com/actions/stale/issues/61#issuecomment-625653899 7/25/2020, 2:48:46 AM - sbrl (Starbeamrainbowlabs): That'd be awesome! Just what I was about to suggest lol 😛 Ah, I see. Getting such a token shouldn't be too hard - we just need to find who's responsible for that account. Perhaps @agnivade will know. 7/25/2020, 9:19:45 AM - agnivade (Agniva De Sarker): I can help with the token. Although I do like the `BOT` label on the sender. 😃 Something which tldr-bot doesn't have. 7/25/2020, 12:08:51 PM - owenvoke (Owen Voke): That's true. Hmm. 7/25/2020, 4:48:43 PM - sbrl (Starbeamrainbowlabs): I wonder if there's a way to do it such that you get the bot label? Or maybe that's a per-account thing we need to fill in some special form for? 7/26/2020, 3:16:40 PM - agnivade (Agniva De Sarker): You need to create an app, and post comments via that. Not via a user. 7/27/2020, 12:39:59 AM - owenvoke (Owen Voke): Ah, perhaps we could do that? If it's quick. If not, I guess it's probably fine to keep it as is? 7/27/2020, 1:46:33 PM - agnivade (Agniva De Sarker): Don't think it's quick. But I haven't really checked. I have no strong opinions either ways. Happy to send you the token if we decide to use the bot. 7/31/2020, 5:57:00 AM - sbrl (Starbeamrainbowlabs): Wow, I was going to go through the rest of the GH notifications, but I'm all reviewed out for now after #4225 7/31/2020, 5:57:07 AM - sbrl (Starbeamrainbowlabs): 57(!) comments O.O 7/31/2020, 5:57:38 AM - sbrl (Starbeamrainbowlabs): 13 pages, average of ~4.4 comments per page 8/4/2020, 8:29:00 AM - MasterOdin (Matthew Peveler): While looking at https://tldr.sh/assets/index.json and looking at other clients, what is the historical context of the format of: ```json { "commands": [ { "name": "", // other command details } ] } ``` versus having something like a map: ```json { "commands": { "": { // other command details } ] } ``` 8/6/2020, 5:08:31 PM - agnivade (Agniva De Sarker): No idea tbh. This was decided a long time ago. Frankly speaking, I don't think we actually need the index.json anymore. The page resolution algorithm is sufficient to let a client find out a page from the local cache. A while back myself and @mebeim had an interesting conversation on the tradeoffs between parsing a big chunk of JSON upfront versus doing multiple Stat syscalls. 8/6/2020, 6:21:44 PM - sbrl (Starbeamrainbowlabs): I guess as time goes on it's only going to become more of a performance hit to parse a big lump of JSON. 8/6/2020, 6:22:11 PM - sbrl (Starbeamrainbowlabs): In a separate project of mine, I refactored specifically to avoid parsing too much JSON, as it's slow 8/6/2020, 9:32:09 PM - MasterOdin (Matthew Peveler): On my local laptop, it took ~5-7ms to parse the JSON file using Node 14. The tldr-node-client also looks to be building a version of that index.json file with it being a map instead (from iterating through the filesystem). The https://github.com/lord63/tldr.py client reads it in and recasts it to a map. 8/6/2020, 9:34:18 PM - MasterOdin (Matthew Peveler): For the tldr-python-client, I thought to use this file, but then decided not to due to performance concern of reading in the JSON file, and then having to loop through it to find the right command, versus if it was a dict. The performance concern I'd have would be in the cost of loading it into memory completely, but on the other hand, if all clients are doing it anyway, the question to me becomes "does any client benefit from it being in this format, versus say a map?" 8/7/2020, 12:22:14 AM - agnivade (Agniva De Sarker): Are you suggesting to change the format of the file? Or publish a new file in a map format? I'd say both of them are complicated solutions compared to just looking up the right file in the directory. 8/7/2020, 6:20:50 AM - MasterOdin (Matthew Peveler): Given that there's a number of clients using that file as is, I think changing the format would be problematic, but I think making a new file (`commands.json`?) with a new format would be best. > I'd say both of them are complicated solutions compared to just looking up the right file in the directory. Except that even for who might minimally use it, the node client is basically constructing this proposed file right now, so having it would be an immediate use to an official client, not to mention the tldr.py one (and potentially others, like python-tldr-client). 8/7/2020, 10:02:57 AM - agnivade (Agniva De Sarker): It would still have to read the new file. All we would save is the conversion step. I was suggesting that we don't actually need such an index. The proposed change would require changes in the Node client, and if we are making changes, I don't see a reason not to just look up the file in the directory. 8/10/2020, 1:13:15 PM - mebeim (Marco Bonelli): To add my two cents: I never understood the need of that index file in the first place. Whatever client you are using, it's both faster and simpler to just try and open the file you are looking for directly. If the open fails fallback to the next one and so on until you either find a file or you are left with no options according to the user language/platform preferences and you report a "not found". 8/10/2020, 9:07:16 PM - MasterOdin (Matthew Peveler): not every client downloads the entire zip of files, and so they use the index.json as a lookup on pages 8/11/2020, 1:43:48 AM - mebeim (Marco Bonelli): @MasterOdin hmm good point, that only applies to command line clients (or in any case any client which does caching) 8/13/2020, 11:24:25 PM - MasterOdin (Matthew Peveler): You could argue that said behavior should not be supported via the client specification on caching (https://github.com/tldr-pages/tldr/blob/master/CLIENT-SPECIFICATION.md#caching), but it's also a file that adds ~20kb to the final zip and ~200kb on disk, which could be equaled out by finally removing ./pages/index.json as was proposed a while back. At this point, I figure I'll just open a PR and let people decide via that mechanism as getting the file generated requires very minimal changes to the repo itself 8/13/2020, 11:54:05 PM - sbrl (Starbeamrainbowlabs): :+1: 8/16/2020, 9:14:10 PM - sbrl (Starbeamrainbowlabs): The massive #4225 is ready for a 2nd review - I've already approved 8/17/2020, 5:23:26 AM - owenvoke (Owen Voke): Nice. :+1: I will have a look tomorrow if I get time. :slight_smile: 8/19/2020, 4:58:16 PM - sbrl (Starbeamrainbowlabs): What do people think of #4271? In short it's a page about an alias, rather than a command 8/19/2020, 5:24:30 PM - waldyrious (Waldir Pimenta): You guys are fast! I decided to write directly in the PR to avoid duplicating arguments (and the temptation to shorten the justification actually given there, if we had discussed in more length here), but I was late to the party :) anyway, I've added my thoughts to @einverne and @owenvoke's 😉 8/19/2020, 5:28:51 PM - sbrl (Starbeamrainbowlabs): Thanks everyone for that :-) I'm currently reviewing #4279, but have got distracted with a new version of my favourite vector graphics program 😃 8/19/2020, 5:29:34 PM - waldyrious (Waldir Pimenta): (as a side note, regarding short answers — just the other day I came across an issue in another project where the maintainer's response was a bit too curt and blunt, which impacted the contributor: https://github.com/Homebrew/homebrew-core/issues/57795. Unfortunately, even after civil exposure of the problem of immediate closure by the contributor, the maintainers doubled down on the initial action 😕 ) 8/19/2020, 5:33:11 PM - waldyrious (Waldir Pimenta): Nice one @sbrl, it's my favorite too! Btw, whoever merges #4279, please include the description in the opening comment of the PR in the body of the squash-merge commit :) 8/19/2020, 9:40:35 PM - MasterOdin (Matthew Peveler): The intended usage of the Homebrew issue tracker and disorganized nature of their discourse (three categories of "Homebrew on Linux", "Homebrew", and "Advanced Usage") seems to actively reject people requesting stuff that someone else with time and desire to help will pick up 8/19/2020, 9:41:19 PM - MasterOdin (Matthew Peveler): Definitely simplifies the life of maintainers though 8/19/2020, 10:34:21 PM - waldyrious (Waldir Pimenta): Yeah, I can certainly appreciate that their strategy of aggressively protecting maintainers' time and attention has benefits for the project's scalability and long-term resilience (especially such a popular one), but I keep wondering if there couldn't be a gentler way to implement such a policy... 8/19/2020, 11:00:18 PM - sbrl (Starbeamrainbowlabs): Indeed! Perhaps something along the lines of encouraging people to help out? 8/19/2020, 11:00:53 PM - sbrl (Starbeamrainbowlabs): e.g. pointing them at some contributing / pr docs 8/19/2020, 11:01:06 PM - sbrl (Starbeamrainbowlabs): that way the community grows 😃 1/14/2023, 3:46:39 PM - anthonyfelts (Anthony Felts) joined the room 8/20/2020, 11:33:19 AM - anthonyfelts (Anthony Felts): Hi! Just wanted to ask a question before making an issue or pull request. I've noticed for some commands such as htop they show up on linux and not osx due to being in pages/linux and not pages/osx. Is there currently a way to have commands show up for multiple operating systems without duplicating the markdown file across directories without globally having them on all systems? Sorry if this is already documented somewhere. 8/20/2020, 11:43:02 AM - agnivade (Agniva De Sarker): The spec dictates that if a page is not found in the host platform, the client should automatically search in other platforms. So it really depends on which client you are using. Some clients also support the `--os` flag which you can use to specify a particular OS. 8/20/2020, 11:54:55 AM - anthonyfelts (Anthony Felts): Okay that makes sense due to the default homebrew client being the c client. The `--platform` flag works. Thank you! 8/20/2020, 4:33:02 PM - sbrl (Starbeamrainbowlabs): If it's not searching in other platforms, that's a bug that should be reported to said client 8/20/2020, 10:00:29 PM - anthonyfelts (Anthony Felts): Okay. I'll verify it's not a homebrew issue tonight then summit an issue to the c-client repo. 8/20/2020, 10:25:07 PM - sbrl (Starbeamrainbowlabs): :-) 1/14/2023, 3:46:42 PM - snan (snan) joined the room 8/21/2020, 4:13:24 AM - snan (snan): Hi it's pretty easy to install the tldr pages as normal man pages https://idiomdrottning.org/tldr-to-man 8/21/2020, 4:14:36 AM - snan (snan): Someone just today told me about tldr pages, I didn't know about them. Thank you for making them♥ 8/21/2020, 4:25:28 AM - snan (snan): Oh, there were already a couple of other people who had similar ideas: https://github.com/joelekstrom/tldr-man for example 8/21/2020, 4:25:30 AM - snan (snan): Huh... 8/21/2020, 4:25:33 AM - * snan (snan) = late to the party 8/21/2020, 2:21:31 PM - waldyrious (Waldir Pimenta): @snan you're one of today's lucky 10,000! https://xkcd.com/1053 8/21/2020, 2:58:27 PM - snan (snan): @waldyrious a classic♥ 8/23/2020, 11:50:05 AM - snan (snan): part doesn't work. irc 8/25/2020, 2:43:38 AM - sbrl (Starbeamrainbowlabs): Another invite for a new collaborator in #4291 :-) 8/25/2020, 2:44:12 AM - sbrl (Starbeamrainbowlabs): @navarroaxel has already accepted - if everyone else agrees then we can go ahead with the invitation 1/14/2023, 3:46:47 PM - navarroaxel (Axel Navarro) joined the room 9/5/2020, 9:01:48 AM - navarroaxel (Axel Navarro): Hi 9/5/2020, 4:21:50 PM - sbrl (Starbeamrainbowlabs): Hi there! I haven't seen thsi thread thingy beofre 8/25/2020, 2:48:42 AM - mebeim (Marco Bonelli): 👍 8/31/2020, 5:12:10 AM - sbrl (Starbeamrainbowlabs): Are we good to merge #4246? 8/31/2020, 8:32:09 PM - waldyrious (Waldir Pimenta): @sbrl yeah, looks good. I've just merged it, thanks for the heads-up! 8/31/2020, 8:34:26 PM - sbrl (Starbeamrainbowlabs): Thanks! Now we can do something about the monstrous #4290 8/31/2020, 8:34:53 PM - sbrl (Starbeamrainbowlabs): I've started a branch already, but the task ahead is pretty overwhelming sorting through everything that's been said already 9/2/2020, 5:32:30 PM - sbrl (Starbeamrainbowlabs): [![Selection_075.png](https://files.gitter.im/542e7b12163965c9bc208722/Tntd/thumb/Selection_075.png)](https://files.gitter.im/542e7b12163965c9bc208722/Tntd/Selection_075.png) 9/2/2020, 5:32:43 PM - sbrl (Starbeamrainbowlabs): Looks like tldr-pages/tldr is now in the GH artic code vault thingy 9/2/2020, 6:47:20 PM - owenvoke (Owen Voke): Nice! 9/3/2020, 11:53:22 AM - principis (Arthur Bols): lol we went from talking about client spec 1.3 to suddenly client spec 1.4 merged... I've missed quite a lot 😛 9/3/2020, 4:33:56 PM - sbrl (Starbeamrainbowlabs): no worries @principis Things seem to be really moving around the client spec atm 9/3/2020, 4:34:10 PM - sbrl (Starbeamrainbowlabs): There's also #4290 you might be interested in 9/5/2020, 5:39:28 PM - dbrgn (Danilo Bargen): Tealdeer 1.4 and 1.4.1 released! https://github.com/dbrgn/tealdeer/releases Main new features are automatic cache updates (opt-in) and improved color detection (conforming to https://no-color.org/). 9/5/2020, 5:45:09 PM - owenvoke (Owen Voke): Nice work @dbrgn! 9/5/2020, 5:46:03 PM - owenvoke (Owen Voke): And thanks for sharing that `NO_COLOR` page. :+1: 9/5/2020, 5:47:32 PM - dbrgn (Danilo Bargen): This channel isn't bridged to Matrix, is it? 9/5/2020, 6:14:21 PM - sbrl (Starbeamrainbowlabs): Nice @dbrgn! Oh, that env var looks very interesting. I should add support for `NO_COLOR` to my personal libraries Wait , tldr-pages has a matrix channel @dbrgn? 9/5/2020, 7:57:43 PM - matrixbot (matrixbot): `sahilister` Yes, matrix bridge is available here. 9/5/2020, 7:57:53 PM - matrixbot (matrixbot): `sahilister` not sure officially supported or not. 9/6/2020, 3:12:13 AM - principis (Arthur Bols): @sbrl thanks, will take look :) 9/6/2020, 3:13:08 AM - sbrl (Starbeamrainbowlabs): ty @principis, it's an enourmous issue and I haven't yet had time to return to it 9/6/2020, 3:13:33 AM - sbrl (Starbeamrainbowlabs): I've started a new branch in the tldr-pages repo for it, but it's very unfinished 1/14/2023, 3:46:56 PM - Penguinlay (Shein Lin Phyo) joined the room 9/11/2020, 6:00:59 PM - Penguinlay (Shein Lin Phyo): *Homebrew Cask* `Warning: Calling brew cask list is deprecated! Use brew list --cask instead.` Not sure how to contribute in the repo as it's a change to existing pages. 9/11/2020, 6:19:35 PM - sbrl (Starbeamrainbowlabs): Hey there, @Penguinlay! Is that a warning you're seeing in the client published via Homebrew? 9/11/2020, 6:20:37 PM - sbrl (Starbeamrainbowlabs): That's the c client, IIRC. I'd recommend opening an issue here: https://github.com/tldr-pages/tldr-c-client/issues/new 9/11/2020, 7:28:00 PM - owenvoke (Owen Voke): I just assumed they were meaning the Brew Cask page. 9/11/2020, 7:28:02 PM - owenvoke (Owen Voke): https://github.com/tldr-pages/tldr/blob/master/pages/osx/brew-cask.md 9/11/2020, 7:34:19 PM - sbrl (Starbeamrainbowlabs): Oh I see! Lol, I misinterpreted that one 😛 In that case @Penguinlay you can click the pencil icon in the top right of the page that @owenvoke has linked to open up the web editor and create a fork + PR :-) 9/22/2020, 10:35:16 PM - sbrl (Starbeamrainbowlabs): University induction is around now, so have been busy & unable to review as frequently 9/22/2020, 11:47:17 PM - owenvoke (Owen Voke): No worries @sbrl, sorry for the spam. 😬 Hope it's going well. 9/22/2020, 11:47:45 PM - sbrl (Starbeamrainbowlabs): No worries, with the new notification system it's pretty easy to deal with :-) 10/1/2020, 11:26:23 PM - navarroaxel (Axel Navarro): https://twitter.com/shitoberfest/status/1311646233128181760 OMG All October is crazy like these last 2 days? 10/1/2020, 11:45:19 PM - sbrl (Starbeamrainbowlabs): Yep, October gets pretty nuts around here @navarroaxel It's easily the busiest time of the year for tldr pages 10/1/2020, 11:45:43 PM - sbrl (Starbeamrainbowlabs): That reminds me, I need to process my GH notifications again 10/2/2020, 12:02:20 AM - sbrl (Starbeamrainbowlabs): Oh my, that's a lot of tldr-pages activity today 10/2/2020, 12:03:58 AM - sbrl (Starbeamrainbowlabs): Looks like PRs this year don't have to be attached to issues labelled `hacktoberfest`: https://hacktoberfest.digitalocean.com/ 10/2/2020, 12:04:37 AM - sbrl (Starbeamrainbowlabs): Although if we have a specific project or set of pages we'd like writing or issues we want closing, we should label them as such to channel the hacktoberfest energy a bit 10/2/2020, 1:56:34 AM - sbrl (Starbeamrainbowlabs): And thus Hactoberfest begins 1/14/2023, 3:47:02 PM - kschurter (kschurter) joined the room 10/2/2020, 2:07:14 AM - kschurter (kschurter): Has there been discussion of providing integration with fzf? Along the same lines as completion scripts in https://github.com/cheat/cheat/tree/master/scripts? I made a quick command palette with tldr pages + fzf that I find handy as a noob that previously had to google for the right terms to search before landing on the right tldr/man page. 10/2/2020, 2:14:25 AM - kschurter (kschurter): ``` cd ~/.local/share/tldr/pages/common grep "^-\|^\`" ./{common,linux}/* | awk 'BEGIN {FS=":[`-]"; OFS="\0"}; /md:-/ {gsub(".*/","",$1); desc=$2; f=$1; next} {gsub("`$","",$2); printf "%s%s\033[35m%s%s %s\033[0m\n", $2, OFS, desc, OFS, f;}' > ~/.tldrpalette __fzf_command_palette__() { local output output=$(fzf --ansi --no-hscroll --query "$READLINE_LINE" --delimiter "\0" --preview 'cat $(fd ^{3}$ ~/.local/share/tldr/pages/{common,linux})' --preview-window=hidden:wrap < ~/.tldrpalette | cut -f 1 -d "") || return e | cut -f 1 -d "") || return READLINE_LINE=${output#*$'\t'} if [ -z "$READLINE_POINT" ]; then echo "$READLINE_LINE" else READLINE_POINT=0x7fffffff fi } bind -m emacs-standard -x '"\ep": __fzf_command_palette__' bind -m vi-command -x '"\ep": __fzf_command_palette__' bind -m vi-insert -x '"\ep": __fzf_command_palette__' ``` 10/2/2020, 2:14:37 AM - sbrl (Starbeamrainbowlabs): No, I don't think so @kschurter. Why don't you open an issue about it? 10/2/2020, 2:14:49 AM - sbrl (Starbeamrainbowlabs): That sounds useful 10/2/2020, 2:15:01 AM - sbrl (Starbeamrainbowlabs): Although I suspect it's a client-specific feature 10/2/2020, 2:15:39 AM - sbrl (Starbeamrainbowlabs): The Node.js client is the reference client, so it might be worth opening an issue over there: https://github.com/tldr-pages/tldr-node-client 10/2/2020, 2:16:03 AM - kschurter (kschurter): Yes, I am not sure how portable my approach is. Ok, thanks for the suggestion. 10/2/2020, 2:18:18 AM - sbrl (Starbeamrainbowlabs): No problem! It sounds useful either way :+1: 10/2/2020, 2:18:26 AM - sbrl (Starbeamrainbowlabs): Definitely worth discussing 10/2/2020, 4:24:03 AM - waldyrious (Waldir Pimenta): @sbrl are we going to finally create a proper label for hacktoberfest this year, instead of renaming the "help wanted" label? 10/2/2020, 4:24:12 AM - waldyrious (Waldir Pimenta): It's made things confusing in the past 10/2/2020, 4:24:19 AM - sbrl (Starbeamrainbowlabs): Lol, that would be a good idea 😛 10/2/2020, 4:24:31 AM - waldyrious (Waldir Pimenta): Let's do it 🙏 10/2/2020, 4:24:58 AM - waldyrious (Waldir Pimenta): It's very hard to search for stuff when the label changes name for a month every year 😂 10/2/2020, 4:25:45 AM - sbrl (Starbeamrainbowlabs): Label created! 10/2/2020, 4:25:57 AM - sbrl (Starbeamrainbowlabs): Do you have perms to change labels on issues @waldyrious? 10/2/2020, 4:26:07 AM - sbrl (Starbeamrainbowlabs): I think as collaborator you should 10/2/2020, 4:27:47 AM - waldyrious (Waldir Pimenta): I believe so, but it's bed time here 😇 10/2/2020, 4:28:08 AM - sbrl (Starbeamrainbowlabs): Right. Night night! 👋 10/2/2020, 4:28:19 AM - waldyrious (Waldir Pimenta): I will definitely go over some existing issues though tomorrow or in the weekend, it's a pet peeve of mine. 10/2/2020, 4:28:41 AM - sbrl (Starbeamrainbowlabs): Sounds great! Thanks so much for that ❤️ 10/2/2020, 4:28:57 AM - waldyrious (Waldir Pimenta): Don't thank me before I do it 😛 10/2/2020, 4:29:01 AM - sbrl (Starbeamrainbowlabs): I've spent a lot of time today reviewing PRs, and need to relax before bed now 10/2/2020, 4:29:04 AM - sbrl (Starbeamrainbowlabs): lol, true 10/2/2020, 4:29:15 AM - waldyrious (Waldir Pimenta): :+1: enjoy a rest too, then! 10/2/2020, 4:29:17 AM - waldyrious (Waldir Pimenta): See ya! 10/2/2020, 4:29:39 AM - sbrl (Starbeamrainbowlabs): Ty 👋 10/2/2020, 5:49:43 PM - owenvoke (Owen Voke): I was thinking about finalising https://github.com/tldr-pages/tldr-lint/issues/13 today. I've opened https://github.com/tldr-pages/tldr-lint/pull/18, which prepares the package for release. And then we should be able to tag and push a new version. :thumbsup: I've also done some other PRs that can be merged after this `v0.0.8` release, which update dependencies, etc. :) 10/2/2020, 5:51:30 PM - owenvoke (Owen Voke): Then once `v0.0.8` is released, we should finally be able to merge #4161 😋 10/2/2020, 7:05:09 PM - sbrl (Starbeamrainbowlabs): 😃 10/2/2020, 7:16:40 PM - owenvoke (Owen Voke): Ah... looks like someone tagged v0.0.8 😬 https://github.com/tldr-pages/tldr-lint/releases/tag/v0.0.8 10/2/2020, 7:16:55 PM - sbrl (Starbeamrainbowlabs): Oops, that might have been my fault 10/2/2020, 7:17:03 PM - sbrl (Starbeamrainbowlabs): Give me a sec, I'll delete the tag 10/2/2020, 7:17:28 PM - owenvoke (Owen Voke): Ah, ok. Is that ok to do? Or should I just bump straight to v0.0.9 instead? 10/2/2020, 7:18:33 PM - sbrl (Starbeamrainbowlabs): Deleted 10/2/2020, 7:18:39 PM - sbrl (Starbeamrainbowlabs): Yeah, it should be fine 10/2/2020, 7:18:43 PM - sbrl (Starbeamrainbowlabs): it wasn't published anyway 10/2/2020, 7:20:18 PM - owenvoke (Owen Voke): :thumbsup: 10/2/2020, 7:25:14 PM - owenvoke (Owen Voke): Well, that worked 😀 https://www.npmjs.com/package/tldr-lint 10/2/2020, 7:26:11 PM - sbrl (Starbeamrainbowlabs): Nice one! We might want to update the README though, as I'm sure we have a check somewhere about the .md file extension? 10/2/2020, 7:29:38 PM - owenvoke (Owen Voke): https://github.com/tldr-pages/tldr-lint/blob/master/lib/tldr-lint-cli.js#L63 Looks like it, but it won't really throw an error if someone opens a PR that doesn't have a `.md` extension 🤔 10/2/2020, 7:31:34 PM - sbrl (Starbeamrainbowlabs): Ah, I see. I thought for sure I've seen a PR recently where tldr-bot made an auto comment asking about it though 10/2/2020, 7:31:55 PM - sbrl (Starbeamrainbowlabs): Something along the lines of "I've noticed something odd" 10/2/2020, 7:35:00 PM - owenvoke (Owen Voke): Oh, hmm. I thought I'd seen that somewhere too. 10/2/2020, 11:14:51 PM - agnivade (Agniva De Sarker): Oh hey, here it is. I came from here https://github.com/tldr-pages/tldr-node-client/issues/312#issuecomment-702630249 @sbrl - I'm afraid I'm not very familiar with fzf or what does a command palette even mean. Can you outline what is expected of the node client here? Is it like one of those bash/zsh completion files which we already have and just need to add another for fzf ? 10/2/2020, 11:46:37 PM - sbrl (Starbeamrainbowlabs): I'm not actually familiar with fzf much beyond that it's a command myself. I don't really know what the OP means by command palette - perhaps further clarification is required 10/2/2020, 11:47:16 PM - sbrl (Starbeamrainbowlabs): as far as I was aware `fzf` was like `fzy`, in that it provides a text-based ui to search & select a single line from stdin 10/3/2020, 10:23:33 AM - agnivade (Agniva De Sarker): Yes I think that's right. But I am not sure what is expected from node client here. 10/3/2020, 10:23:50 AM - agnivade (Agniva De Sarker): @kschurter - can you clarify a bit? 10/3/2020, 3:20:56 PM - kschurter (kschurter): Hi, yes. I think I can clarify easily because I found something that is pretty much exactly what I had in mind: https://github.com/pindexis/marker. It seems like it ships with an outdated list of tldr usage examples. Apart from that, the demo looks quite nice. I have not installed it yet to see how well it works. 10/3/2020, 4:22:55 PM - owenvoke (Owen Voke): So, is now opt-in. Do we want to add the `hacktoberfest` topic? https://hacktoberfest.digitalocean.com/hacktoberfest-update 10/3/2020, 4:23:11 PM - owenvoke (Owen Voke): *Hacktoberfest is now opt-in. 10/3/2020, 4:23:24 PM - owenvoke (Owen Voke): No idea why it removed that word from the sentence... 10/3/2020, 5:54:06 PM - sbrl (Starbeamrainbowlabs): @owenvoke Oh, interesting. I guess it might be worth doing? Apparently we need to tag issues & prs with `hacktoberfest` too 10/3/2020, 5:54:51 PM - sbrl (Starbeamrainbowlabs): Let's wait and see what others say 10/3/2020, 6:40:18 PM - agnivade (Agniva De Sarker): Yeah sure I don't see a reason not to do now, since we have been doing every year. And also we have some more maintainers which gives me a bit more confidence because I won't be able to spend as much time as I used to earlier. 10/3/2020, 6:48:45 PM - sbrl (Starbeamrainbowlabs): Added the `hacktoberfest` topic to our repo 10/3/2020, 6:49:07 PM - sbrl (Starbeamrainbowlabs): now we just need to tag issues & PRs, which I think @waldyrious was going to help with? 10/3/2020, 7:04:38 PM - owenvoke (Owen Voke): Ah, we have to label PRs/issues too? 🤔 10/3/2020, 7:15:03 PM - sbrl (Starbeamrainbowlabs): apparently so 10/3/2020, 7:15:20 PM - sbrl (Starbeamrainbowlabs): according to the page you linked to 10/3/2020, 10:14:13 PM - waldyrious (Waldir Pimenta): I don't think the labeling part is required, @sbrl. From the piece of pseudocode they shared, the only mention of labels is if maintainers can't handle a PR during October, and mark it with the "hactoberfest-accepted" label to signal that it's not spam, until they have the availability to properly review and merge it 10/3/2020, 10:14:28 PM - sbrl (Starbeamrainbowlabs): Ah, I see 10/3/2020, 10:15:27 PM - waldyrious (Waldir Pimenta): Otherwise the PR would need to be either merged or receive an approval review for it to count, neither of which should be rushed. 10/3/2020, 10:16:04 PM - sbrl (Starbeamrainbowlabs): Ah, right. That makes sense! 10/5/2020, 7:04:04 PM - sbrl (Starbeamrainbowlabs): 109 notifications O.O 10/5/2020, 7:20:09 PM - mebeim (Marco Bonelli): gee that's a lot 😮 10/5/2020, 7:25:39 PM - sbrl (Starbeamrainbowlabs): Yeah, and only in a few days O.o 10/5/2020, 8:10:40 PM - owenvoke (Owen Voke): Yeah, this year seems to have a lot more PRs. But at least they all seem good so far. :+1: 10/5/2020, 8:21:26 PM - sbrl (Starbeamrainbowlabs): Yeah! 10/5/2020, 8:21:40 PM - sbrl (Starbeamrainbowlabs): I think it's all the translations being 1 PR per page 10/5/2020, 8:21:48 PM - sbrl (Starbeamrainbowlabs): I need to write a saved reply for that one 10/5/2020, 8:22:52 PM - sbrl (Starbeamrainbowlabs): I should be doing PhD work, but I'm trying to clear out this GH notifications first lol 10/5/2020, 9:16:20 PM - waldyrious (Waldir Pimenta): PhDs are the prime procrastination trap 😅 10/5/2020, 9:31:13 PM - navarroaxel (Axel Navarro): https://github.com/tldr-pages/tldr/pull/4476 `dep` command is a dependency management tool for golang but also the `dep` command could be `deployer`, a deployment tool for PHP. I think the page should be `deployer.md`. But, should we add a mention in the golang `dep.md` page like: `If you are looking for PHP deployer use tldr deployer`? 10/5/2020, 9:33:58 PM - sbrl (Starbeamrainbowlabs): @waldyrious haha yeah @navarroaxel I meant to say, wow thanks so much for all the reviewing you've been doing! It's really been helping out. 10/5/2020, 9:34:08 PM - sbrl (Starbeamrainbowlabs): And uh oh! I was wondering when that was happen lol 10/5/2020, 9:34:19 PM - sbrl (Starbeamrainbowlabs): I think that's our first instance of a name conflict 10/5/2020, 9:35:23 PM - sbrl (Starbeamrainbowlabs): I don't actually know what we should do there 10/5/2020, 9:35:32 PM - sbrl (Starbeamrainbowlabs): @agnivade / @owenvoke? 10/5/2020, 9:39:51 PM - navarroaxel (Axel Navarro): https://github.com/golang/dep go `dep`: Dep was an official experiment to implement a package manager for Go. As of 2020, Dep is deprecated and archived in favor of Go modules. 13.2k stars in GH https://github.com/deployphp/deployer 8k stars 10/5/2020, 9:41:55 PM - sbrl (Starbeamrainbowlabs): Oh, great point. In that case, we should replace the existing page on Go dep if it's archived 10/5/2020, 9:42:08 PM - sbrl (Starbeamrainbowlabs): There's a much stronger case there for the PHP deployer. 10/5/2020, 9:42:35 PM - navarroaxel (Axel Navarro): and we can add in the go-dep that is now deprecated. 10/5/2020, 9:43:47 PM - sbrl (Starbeamrainbowlabs): Good idea, in the 2nd description line 10/5/2020, 9:43:49 PM - sbrl (Starbeamrainbowlabs): Let's do that 10/5/2020, 9:43:53 PM - sbrl (Starbeamrainbowlabs): :+1: 10/5/2020, 9:44:29 PM - sbrl (Starbeamrainbowlabs): Also, how many PRs have you merged @navarroaxel? You may be eligible to become an org member if it's over 10 10/5/2020, 9:44:53 PM - sbrl (Starbeamrainbowlabs): I know you've definitely submitted 5+ non-trivial reviews 10/5/2020, 9:59:18 PM - navarroaxel (Axel Navarro): Should I review how many reviews I have done? 😫 this never ends 10/5/2020, 10:10:40 PM - sbrl (Starbeamrainbowlabs): No no haha, @navarroaxel 10/5/2020, 10:11:03 PM - sbrl (Starbeamrainbowlabs): I think given your activity here, I can definitely say you've merged over 10 PRs. 10/5/2020, 10:12:48 PM - sbrl (Starbeamrainbowlabs): Opened #4504 @navorroaxel 😃 10/6/2020, 12:21:27 AM - navarroaxel (Axel Navarro): awesome! 10/6/2020, 12:25:38 AM - sbrl (Starbeamrainbowlabs): Invite sent 😃 10/6/2020, 12:40:48 AM - sbrl (Starbeamrainbowlabs): Could you make your membership of the tldr-pages org public please, @navarroaxel? 10/6/2020, 1:35:39 AM - owenvoke (Owen Voke): Welcome @navarroaxel! 10/6/2020, 1:37:55 AM - navarroaxel (Axel Navarro): Thx! I didn't know about that visibility setting 10/6/2020, 1:40:56 AM - mebeim (Marco Bonelli): Welcome! :) 10/6/2020, 1:56:20 AM - sbrl (Starbeamrainbowlabs): Np! Yeah, it's in our community roles document that everyone has to have their membership public 10/6/2020, 1:56:29 AM - sbrl (Starbeamrainbowlabs): Also, well done for having 2FA enabled 😃 10/6/2020, 2:21:27 AM - waldyrious (Waldir Pimenta): > it's in our community roles document that everyone has to have their membership public Actually, it's in the very message you wrote in #4504, @sbrl 😉 10/6/2020, 2:24:37 AM - sbrl (Starbeamrainbowlabs): Oh yeah! lol 😛 10/6/2020, 10:33:23 PM - sbrl (Starbeamrainbowlabs): Sorry to cause a scene in #4459, but felt that there was a number of issues whereby the meaning of the examples were not clear with the changed wording. I reverted it in #4532, and have opened #4533 to move forwards. 10/6/2020, 10:33:48 PM - sbrl (Starbeamrainbowlabs): Sorry in particular to @owenvoke who merged it 10/6/2020, 10:40:45 PM - mebeim (Marco Bonelli): @sbrl Oh dammit, I thought you were ok with the changes. I was waiting for your review though. In any case, you make a good point that simply changing "master" to "main" in those pages just confuses things, and something like "branch_name" should be used instead. 10/6/2020, 10:41:45 PM - sbrl (Starbeamrainbowlabs): Sorry for confusing, @mebeim! I was in a rush yesterday when I left a comment - I was clearing out 109 GH notifications and didn't actually check the changes properly. I'll try to communicate better in future haha 10/7/2020, 12:11:59 AM - owenvoke (Owen Voke): No problem. :+1: Simple mistake from me, and we can continue the conversation in a clearer way. 10/7/2020, 11:16:19 AM - agnivade (Agniva De Sarker): Nice work there @sbrl. Appreciate the time and effort you are giving to this project (inspite of your PhD work) ! 10/7/2020, 5:30:40 PM - sbrl (Starbeamrainbowlabs): Thanks @agnivade 😃 As I've been contributing, I've really come to care about tldr-pages a lot ❤️ 1/14/2023, 3:47:50 PM - seenukarthi (Karthikeyan Vaithilingam) joined the room 10/7/2020, 5:44:27 PM - seenukarthi (Karthikeyan Vaithilingam): Hi All, how to add a command where the options differ from platform to platform? 10/7/2020, 5:48:22 PM - sbrl (Starbeamrainbowlabs): Hey there, @seenukarthi! To do that, you should create a copy of the command page with the altered arguments in the directory for the platform where ti works slightly differently. For example, if I have a command `foo` that works the same on Windows and Linux, but differently on macOS, I would create a copy in `common` for Windows and Linux, and a copy in `osx` for mac - which will override the `common` copy. 10/7/2020, 5:48:56 PM - sbrl (Starbeamrainbowlabs): Another example: If I have a command `bar` that functions differently on Windows, macOS, and Linux, then I would create 3 copies in each of the 3 different platform directories. 10/7/2020, 5:50:26 PM - mebeim (Marco Bonelli): One exception is: if the command has different options on different platforms, but the examples in the page you write for it do not show any of the platform-specific options, you can just create it under `common`. 10/7/2020, 5:57:11 PM - sbrl (Starbeamrainbowlabs): :+1: 10/7/2020, 5:59:02 PM - seenukarthi (Karthikeyan Vaithilingam): :+1: 1/14/2023, 3:47:53 PM - OiYouYeahYou (Jason Allan) joined the room 10/9/2020, 1:22:31 AM - OiYouYeahYou (Jason Allan): Is a PR per new command expected, or do you prefer one PR for a bunch? 10/9/2020, 1:24:05 AM - mebeim (Marco Bonelli): @OiYouYeahYou if the commands are related then you can do more than one per PR, but in general we prefer one PR per command as it's easier for both the author and the maintainers to review. 10/9/2020, 1:29:48 AM - OiYouYeahYou (Jason Allan): great 😃 10/9/2020, 1:46:35 AM - sbrl (Starbeamrainbowlabs): If it's a translation of existing commands, then as many as you like per PR are preferred 10/9/2020, 10:31:48 AM - seenukarthi (Karthikeyan Vaithilingam): Is there any problem with Liberapay? 10/9/2020, 10:37:30 AM - seenukarthi (Karthikeyan Vaithilingam): http://imgur.com/gallery/vaX7XPC 10/9/2020, 12:15:16 PM - owenvoke (Owen Voke): This was mentioned recently (#4428). I think @ostera might not have set up a payment provider yet. 🤔 10/9/2020, 4:35:01 PM - mebeim (Marco Bonelli): Yes @seenukarthi, unfortunately there's some misconfiguration issue on our end. We are waiting for all the members to update the payment providers, hopefully that'll be enough. 10/12/2020, 2:40:10 PM - seenukarthi (Karthikeyan Vaithilingam): Hi all I'm planning to do Tamil translations for git commands there are 72 commands in English shall i create a single PR for all 72 commands or do it in batches? 10/12/2020, 3:22:29 PM - mebeim (Marco Bonelli): @seenukarthi I would suggest batches if that helps speed up the process for you, but it's fine either way. Even if we do not have Tamil speaking members those would still need to be "checked" at least with something like google translate just to make sure the phrases make sense overall 1/14/2023, 3:47:59 PM - eshack94 (Elijah Shackelford) joined the room 10/12/2020, 3:57:04 PM - eshack94 (Elijah Shackelford): Just opened a couple PRs :) A review when convenient would be much appreciated 10/12/2020, 3:58:51 PM - mebeim (Marco Bonelli): @eshack94 thank you very much Elijah, bear with us as we currently have a lot of PRs open. We will get to those, I swear! :) 10/12/2020, 4:06:23 PM - eshack94 (Elijah Shackelford): No rush or worries! Just giving a friendly heads-up. It’s not urgent at all 10/13/2020, 3:55:42 AM - sbrl (Starbeamrainbowlabs): It's not usually this busy, it's the Hacktoberfest rush 😛 10/16/2020, 2:12:03 AM - navarroaxel (Axel Navarro): This PR is awaiting opinions for more reviewers before merge it: https://github.com/tldr-pages/tldr/pull/4513 1/14/2023, 3:48:02 PM - ivorysoap (Ivor Benderavage) joined the room 10/17/2020, 3:19:50 AM - ivorysoap (Ivor Benderavage): Allo, pour les traductions en français est-ce qu'on utilise l'infinitif ou non dans le "header" de la page? 10/17/2020, 3:21:54 AM - ivorysoap (Ivor Benderavage): If anyone English-speaking knows the answer, that would also be great. In the headers of the French translated pages, I noticed that some pages have the first form, and others have the second form: * **Afficher** tous les systèmes de fichiers et leur utilisation d'espace disque : * **Liste** les fichiers, un par ligne : 10/17/2020, 3:22:18 AM - ivorysoap (Ivor Benderavage): And I was wondering if one of them was preferred over the other. (The style guide doesn't mention anything) 10/17/2020, 3:32:31 AM - sbrl (Starbeamrainbowlabs): Hey there, @ivorysoap! I don't speak French myself, but I suggest that you open a new issue and @ mention some of the people who have contributed to the French pages. 10/17/2020, 3:14:12 PM - navarroaxel (Axel Navarro): Hi! Someone knows how to fix this? https://github.com/tldr-pages/tldr/pull/4702#discussion_r506349703 10/17/2020, 4:30:13 PM - owenvoke (Owen Voke): I don't think we support escaping in most clients. I'd say it's best to just put a PID placeholder. 10/17/2020, 4:30:48 PM - owenvoke (Owen Voke): So something like `pid == 1234` 10/18/2020, 4:39:37 AM - MasterOdin (Matthew Peveler): someone here willing to add a GH secret to https://github.com/tldr-pages/tldr-python-client ? 10/18/2020, 4:43:07 AM - mebeim (Marco Bonelli): @MasterOdin sure, what's that for? 10/18/2020, 4:46:56 AM - MasterOdin (Matthew Peveler): want to add my pypi api token for publishing through gh actions 10/18/2020, 4:52:57 AM - mebeim (Marco Bonelli): @MasterOdin send me a pm and I'll add it 10/18/2020, 12:01:00 PM - seenukarthi (Karthikeyan Vaithilingam): Hi All, I Have created a Java client for tldr-pages. https://github.com/seenukarthi/tldr-java-client this is still WIP. Will appreciate feedback. 10/18/2020, 5:18:08 PM - sbrl (Starbeamrainbowlabs): Nice one, @seenukarthi! 10/18/2020, 5:18:24 PM - sbrl (Starbeamrainbowlabs): You're welcome to open a PR against the README to add it to the list if you like :-) 10/19/2020, 9:05:43 PM - sbrl (Starbeamrainbowlabs): eek, 96 GH notifications better get started on them then 10/23/2020, 7:36:37 PM - navarroaxel (Axel Navarro): we have a PR conflict here https://github.com/tldr-pages/tldr/pull/4764 and https://github.com/tldr-pages/tldr/pull/4815. both with different perspective about Lynx a CLI Web Browser 10/23/2020, 10:58:43 PM - navarroaxel (Axel Navarro): https://github.com/tldr-pages/tldr/pull/4815#issuecomment-715472051 I think we should merge 4764 and work an improved version in 4815 10/24/2020, 4:13:03 AM - sbrl (Starbeamrainbowlabs): Been setting up a new laptop, so haven't had time to review today 10/24/2020, 1:32:37 PM - owenvoke (Owen Voke): Oh, 2 of the same page. That's odd. I agree with merging #4764 as it's older, however I feel like the syntax seems wrong for the interactive usage. 10/24/2020, 1:40:43 PM - owenvoke (Owen Voke): Looking at some of the other interactive pages (`vim`/`nvim`), I think it will need quite a few changes. 10/24/2020, 4:46:13 PM - sbrl (Starbeamrainbowlabs): Oh, great point @owenvoke 10/24/2020, 4:46:24 PM - sbrl (Starbeamrainbowlabs): I never know what to do with the interactive syntax on pages 10/24/2020, 4:46:45 PM - sbrl (Starbeamrainbowlabs): so I appreciate any assistance there :-) 10/25/2020, 2:42:57 PM - agnivade (Agniva De Sarker): We've had quite a few pages with a REPL like syntax. Even apart from vim, there are a few GUI tools. So given that there is precedent, I am fine with it. 10/25/2020, 2:44:34 PM - agnivade (Agniva De Sarker): On a different note, I am really amazed at how many different languages we support now. 🎉 Never would I have imagined the community would come up and organically build such a huge translation base. 10/25/2020, 5:31:14 PM - sbrl (Starbeamrainbowlabs): Right - it's just that uncommon that I always forget what we do there every time 😛 Yeah, it's pretty amazing! We've got a pretty significant percentage of PRs at the moment are translating pages, and I've noticed that many of them translate more than 1 page too! 10/25/2020, 6:11:34 PM - owenvoke (Owen Voke): Yeah, we could probably do with some notes on how to handle them. :+1: 10/25/2020, 6:39:09 PM - sbrl (Starbeamrainbowlabs): Yeah 10/27/2020, 4:12:47 PM - navarroaxel (Axel Navarro): https://github.com/tldr-pages/tldr/pull/4833#issuecomment-716922626 The end of the Hacktoberfest is coming and the people need a label applied to their PRs to be counted in the fest 10/27/2020, 4:20:57 PM - sbrl (Starbeamrainbowlabs): Hrm. On the one hand we could create it, but on the other it might result in an enormous rush of people creating lots of PRs. What do other people think? 10/28/2020, 8:43:22 PM - waldyrious (Waldir Pimenta): Well, there are only 3 days left in October, so IMO we could add the `hacktoberfest-accepted` label to the existing PRs and if we start getting too many PRs afterwards, we can simply not tag them, and they won't count for Hacktoberfest. Then we can get through them at our own pace. WDYT @sbrl ? 10/28/2020, 8:54:26 PM - sbrl (Starbeamrainbowlabs): Sounds good, @waldyrious! 10/28/2020, 8:54:30 PM - sbrl (Starbeamrainbowlabs): Let's do that. 10/28/2020, 9:43:14 PM - sbrl (Starbeamrainbowlabs): New label created & applied 10/28/2020, 9:43:33 PM - sbrl (Starbeamrainbowlabs): Feel free t o apply the label to other PRs, I might have missed some since I did a mass change 10/29/2020, 12:00:48 AM - sbrl (Starbeamrainbowlabs): Looks like #4608 slipped through the net 10/29/2020, 12:00:59 AM - sbrl (Starbeamrainbowlabs): I think it's ready to go, just needs merging 10/30/2020, 10:35:55 AM - agnivade (Agniva De Sarker): If someone with expertise with promises can take a look at https://github.com/tldr-pages/tldr-node-client/pull/316, it will be very appreciated. 10/30/2020, 4:07:42 PM - navarroaxel (Axel Navarro): @agnivade `async`/`await` is supported since node v7.6+ and this app supports v10+ (LTS active until 2021-04-30) Can we improve the code replacing promises by `async`/`await`? 10/30/2020, 5:56:10 PM - sbrl (Starbeamrainbowlabs): Yep, that could be improved with async / await 10/31/2020, 1:44:29 AM - agnivade (Agniva De Sarker): Sure, I would like to hand off maintainership of the codebase to someone. So if you are interested, I am okay with the changes. 10/31/2020, 2:40:35 AM - sbrl (Starbeamrainbowlabs): I've got too much to do at the moment, so I'm not a good candidate for taking over maintainership for tldr-node-client 10/31/2020, 9:00:53 AM - agnivade (Agniva De Sarker): Oh I meant that towards Axel, not you sbrl. 😛 10/31/2020, 6:36:31 PM - sbrl (Starbeamrainbowlabs): ah ok, np 11/4/2020, 3:11:25 PM - owenvoke (Owen Voke): Just looking at #4750, it seems that #4782 has already been merged so the PR kind of becomes redundant, should I close it? 🤔 11/4/2020, 3:16:10 PM - navarroaxel (Axel Navarro): The author explicitly refuses to sign the CLA 🤷‍ https://github.com/tldr-pages/tldr/pull/4750#issuecomment-711281519 I was expecting the bot to close it 11/4/2020, 3:17:03 PM - waldyrious (Waldir Pimenta): Why would the bot close it? Due to inactivity? 11/4/2020, 3:17:49 PM - navarroaxel (Axel Navarro): yep 11/4/2020, 3:18:06 PM - waldyrious (Waldir Pimenta): I would say it's fair for us to close the PR manually given that the author refuses the CLA's terms 11/4/2020, 3:18:19 PM - waldyrious (Waldir Pimenta): Just waiting around for the bot to close it may feel a little passive-aggressive 11/4/2020, 3:18:48 PM - waldyrious (Waldir Pimenta): I can do that. 11/4/2020, 3:19:53 PM - navarroaxel (Axel Navarro): Why the CLA is not inside the tldr-pages repo? or in the tldr org? 11/4/2020, 3:20:07 PM - owenvoke (Owen Voke): It's a 3rd-party service. 11/4/2020, 3:20:59 PM - owenvoke (Owen Voke): I'll leave it for you @waldyrious, as I'm sure you can write something a lot better. :thumbsup: 11/4/2020, 3:21:44 PM - owenvoke (Owen Voke): @navarroaxel, here is the service: https://cla-assistant.io 11/4/2020, 3:22:51 PM - navarroaxel (Axel Navarro): I mean why is in a gist http://tldr.sh/CLA.xhtml 11/4/2020, 3:30:19 PM - waldyrious (Waldir Pimenta): That's the only way CLA-assistant can be set up so that the content and history of the agreement is public. At least it was the only way when we set up the service. 11/4/2020, 3:30:42 PM - waldyrious (Waldir Pimenta): At the time I tried to create the gist under the tldr-pages organization, but that wasn't possible. I'm not sure if it is now. 11/4/2020, 3:30:58 PM - waldyrious (Waldir Pimenta): (Or if a file in the repo can be used, for that matter.) 11/4/2020, 3:31:16 PM - waldyrious (Waldir Pimenta): I'd be happy to change to a better system if there's one now :) 11/4/2020, 3:33:09 PM - navarroaxel (Axel Navarro): good to know 11/4/2020, 3:34:30 PM - navarroaxel (Axel Navarro): I wonder if we should talk about change the default branch to `main` before someone external comes with that request. Maybe we can't, maybe we need a migration plan 11/4/2020, 3:35:51 PM - waldyrious (Waldir Pimenta): AFAIK GitHub is working on enabling that transition to happen more smoothly 11/4/2020, 3:36:00 PM - waldyrious (Waldir Pimenta): I'd say we should wait until that is in place 11/4/2020, 3:40:24 PM - navarroaxel (Axel Navarro): I thought the last github transition was change the default branch to `main` for new repos, Is there more coming? 11/4/2020, 3:56:31 PM - waldyrious (Waldir Pimenta): Yeah: https://github.com/github/renaming/#later-this-year-seamless-move-for-existing-repositories- 11/4/2020, 4:32:01 PM - navarroaxel (Axel Navarro): cool 1/14/2023, 3:48:41 PM - LukBukkit (Lukas) joined the room 11/5/2020, 4:41:12 PM - LukBukkit (Lukas): Hello guys, in the last few day I tinkered a little bit and built a tool which shows the progress of translating every page. Maybe this is useful for contributors to find pages which are not yet translated into their language. You can view the deployed website: https://lukwebsforge.github.io/tldri18n/ and take a look at the source code: https://github.com/LukWebsForge/TldrProgress Let me know, if this is helpful for you. :) 11/5/2020, 4:42:57 PM - owenvoke (Owen Voke): Wow, that's great! 11/5/2020, 4:46:28 PM - LukBukkit (Lukas): side note: It's updated every day at around 2 am CET, so I'll take a while until the `commom` category is removed from the site 11/5/2020, 5:20:16 PM - waldyrious (Waldir Pimenta): That's amazing @LukBukkit! 11/5/2020, 6:23:27 PM - sbrl (Starbeamrainbowlabs): Wow, that's awesome @LukBukkit! We should definitely link to that at least on the wiki. 11/6/2020, 11:02:07 PM - sbrl (Starbeamrainbowlabs): Would you be open to editing the wiki there? 11/8/2020, 9:51:42 PM - LukBukkit (Lukas): Yeah I could do that in the next few days. 11/8/2020, 11:32:00 PM - sbrl (Starbeamrainbowlabs): 😃 11/10/2020, 2:39:56 AM - LukBukkit (Lukas): Or I guess I can't. The write access of the wiki is restricted to owners of the repository. I could write a few sentences for the page https://github.com/tldr-pages/tldr/wiki/Useful-scripts-and-programs. And does this qualify as a web client of tldr? 11/10/2020, 2:45:16 AM - sbrl (Starbeamrainbowlabs): Oh, that's annoying. Is there any way that we can open the wiki to pull requests? 11/10/2020, 2:47:23 AM - LukBukkit (Lukas): As far as I know, there no way to do this. 11/10/2020, 3:03:36 AM - LukBukkit (Lukas): I put a short entry for the wiki into a Gist, feel free to improve it. https://gist.github.com/LukBukkit/d57676aab1c34b6afb8f5e1d37c852b9 11/10/2020, 3:14:44 PM - waldyrious (Waldir Pimenta): I don't see any spam in the revision history of the wiki pages. Was there a particular reason we decided to close it for contributions, or was that something GitHub did automatically? I'd be in favor of reopening the wiki 11/10/2020, 6:41:36 PM - owenvoke (Owen Voke): :thumbsup: 11/10/2020, 8:57:00 PM - sbrl (Starbeamrainbowlabs): I don't remember closing it, so I think it was before my time 11/17/2020, 12:04:02 AM - navarroaxel (Axel Navarro): Hi, could someone please add an extra check to this? https://github.com/tldr-pages/tldr/pull/4705#pullrequestreview-518953471 11/17/2020, 12:37:55 AM - waldyrious (Waldir Pimenta): @navarroaxel I've added some comments. Thanks for the heads-up. 11/17/2020, 9:19:21 AM - agnivade (Agniva De Sarker): Hey guys, just to let you know, I have unsubscribed myself from the firehose of notifications from tldr, and will not be doing much PR reviews as frequently as before. The load was becoming too much for me to handle. Just `@mention` me if you want my attention. 1/14/2023, 3:48:48 PM - manuelhaussmann (Manuel Haussmann) joined the room 11/17/2020, 5:44:50 PM - manuelhaussmann (Manuel Haussmann): Hi, since pull requests to the wiki don't seem possible, what is your preferred policy for reporting errors there? Opening a regular issue, or a quick message here? Specifically, the list of console clients [1] has the archlinux install instructions with the cpp-client, while pacman actually relies on the python-client [2] [1]https://github.com/tldr-pages/tldr/wiki/tldr-pages-clients#other-console-clients [2]https://www.archlinux.org/packages/community/any/tldr/ (Thanks for a great project!) 11/17/2020, 5:48:58 PM - waldyrious (Waldir Pimenta): @agnivade are you able to reopen the wiki? Both @manuelhaussmann and @LukBukkit are chatting here about wanting to make changes to the wiki, but it seems to be closed for public editing (even though as far as I can see there's no history of spam or any other type of abuse) 11/17/2020, 5:50:06 PM - waldyrious (Waldir Pimenta): (also, good call on unsubscribing from the notifications — the last thing we want is for the experienced hands that help manage the project to burn out :)) 11/17/2020, 6:35:31 PM - sbrl (Starbeamrainbowlabs): Found the setting! 11/17/2020, 6:35:35 PM - sbrl (Starbeamrainbowlabs): [![image.png](https://files.gitter.im/542e7b12163965c9bc208722/gg8M/thumb/image.png)](https://files.gitter.im/542e7b12163965c9bc208722/gg8M/image.png) 11/17/2020, 6:35:45 PM - sbrl (Starbeamrainbowlabs): I've now enabled public edits to the wiki. 11/17/2020, 6:36:00 PM - sbrl (Starbeamrainbowlabs): /cc @manuelhaussmann and @LukBukkit 11/17/2020, 6:38:30 PM - manuelhaussmann (Manuel Haussmann): Thanks @sbrl . I updated it 11/17/2020, 6:40:07 PM - navarroaxel (Axel Navarro): Why you can't turn it ON outside the Hacktoberfest season? @agnivade 11/17/2020, 6:41:19 PM - sbrl (Starbeamrainbowlabs): @navarroaxel Even outside hacktoberfest, tldr-pages does get a few notifications. Particularly around now, I think it's common for people to take a bit of a break :-) 11/17/2020, 6:41:24 PM - sbrl (Starbeamrainbowlabs): @manuelhaussmann: Thanks 😃 11/17/2020, 11:04:41 PM - agnivade (Agniva De Sarker): @navarroaxel - It's not due to Hacktoberfest. I am part of several high traffic repositories, and I get around 100-200 notifications daily. It was turning out to be a cat and mouse game. If I leave my notifications unattended for a single day, it would easily climb to 500. Things were getting out of hand. And I have only so much of free time :) So now that this project has a lot of new maintainers, I decided to take a more hands-off approach. 11/18/2020, 1:54:26 AM - navarroaxel (Axel Navarro): :thumbsup: 11/18/2020, 3:24:09 PM - matrixbot (matrixbot): `sahilister` tldr's CI checks are failing due to changes with GitHub actions. I have raised an issue documenting the same - https://github.com/tldr-pages/tldr/issues/4963 11/18/2020, 5:17:11 PM - navarroaxel (Axel Navarro): Error: Unable to process command '::set-env name=PULL_REQUEST_ID::4958' successfully. Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ 11/18/2020, 5:17:46 PM - navarroaxel (Axel Navarro): Oh I didn't notice the warning in the tldr-pages pipelines. I knew about this deprecation months ago 11/18/2020, 7:03:24 PM - sbrl (Starbeamrainbowlabs): /cc @owenvoke 11/18/2020, 7:04:24 PM - navarroaxel (Axel Navarro): @einverne fixed that ! from the shadows 11/18/2020, 7:09:56 PM - sbrl (Starbeamrainbowlabs): Nice one 😃 11/18/2020, 8:49:40 PM - owenvoke (Owen Voke): I'm surprised I hadn't seen that in the repo, as I did a search of all repos I have access to which were using the old `set-env` syntax. 11/18/2020, 8:51:14 PM - owenvoke (Owen Voke): But yes, I force-merged #4964 which resolved the issue. Any PRs that are still experiencing the issue should either be rebased or I guess manually checked without the CI passing? 1/14/2023, 3:48:57 PM - SmithJohnTaylor (JT Smith) joined the room 11/20/2020, 1:11:02 AM - SmithJohnTaylor (JT Smith): Hi all. Maybe I'm missing it but the "https://github.com/tldr-pages/tldr/wiki/tldr-pages-clients" entry does not exists, but is linked to on both the website and README. Should an issue be raised for this? 11/20/2020, 1:12:24 AM - mebeim (Marco Bonelli): Hmm that's odd let me see (and yes you can open an issue for that) 11/20/2020, 1:13:46 AM - SmithJohnTaylor (JT Smith): I can do that for both tldr-pages/tldr and tldr-pages.github.io 11/20/2020, 1:15:54 AM - mebeim (Marco Bonelli): Tep that's fine 11/20/2020, 1:16:25 AM - mebeim (Marco Bonelli): The only thing I can see that resembles that page is this: http://web-old.archive.org/web/20200213042357/https://github.com/tldr-pages/tldr/wiki/TLDR-clients 11/20/2020, 1:17:00 AM - mebeim (Marco Bonelli): I wonder if somebody deleted it for some strange reason 11/20/2020, 1:17:07 AM - mebeim (Marco Bonelli): I might be missing something 11/20/2020, 1:18:06 AM - SmithJohnTaylor (JT Smith): I was thinking something along those lines. Just seemed odd which is why I wanted to ask here first. 11/20/2020, 1:19:42 AM - sbrl (Starbeamrainbowlabs): Oh, I think we merged that into the list in the README 11/20/2020, 1:19:46 AM - sbrl (Starbeamrainbowlabs): that link should be updated 11/20/2020, 1:19:47 AM - sbrl (Starbeamrainbowlabs): oops! 11/20/2020, 1:22:54 AM - mebeim (Marco Bonelli): Oh ok, that's what I was thinking, I'm from mobile so I was struggling to find the PR for that 11/20/2020, 1:23:12 AM - SmithJohnTaylor (JT Smith): haha feel free to close #4973 11/20/2020, 1:24:12 AM - mebeim (Marco Bonelli): We'll fix that and close it, thanks for letting us know! 11/20/2020, 1:25:26 AM - sbrl (Starbeamrainbowlabs): Updating the wiki now 11/20/2020, 1:27:03 AM - sbrl (Starbeamrainbowlabs): Done 😃 11/20/2020, 1:31:19 AM - SmithJohnTaylor (JT Smith): also made one for the site, not sure how you wanted to update the verbiage. #50 I assume just link to the readme? I can make a PR if needed 11/20/2020, 4:44:46 AM - waldyrious (Waldir Pimenta): > Oh, I think we merged that into the list in the README 11/20/2020, 4:45:03 AM - waldyrious (Waldir Pimenta): Did we? I don't recall that 🤔 11/20/2020, 4:45:23 AM - waldyrious (Waldir Pimenta): I can't find any PR making any mention of that, either... 11/20/2020, 6:03:30 AM - mebeim (Marco Bonelli): @waldyrious ok so I wasn't the only one confused haha 11/20/2020, 6:53:34 AM - sbrl (Starbeamrainbowlabs): I thought we did at one point? Maybe I'm misremebering 11/20/2020, 7:40:49 AM - waldyrious (Waldir Pimenta): We certainly have talked about it, but it was pending an actual merge of the content 11/20/2020, 7:40:58 AM - waldyrious (Waldir Pimenta): It looks like the wiki page was simply deleted 11/20/2020, 7:50:10 AM - mebeim (Marco Bonelli): I wonder if that has something to do with the fact that anyone is allowed to edit, which doesn't seem like a good idea to me 11/20/2020, 7:50:44 AM - mebeim (Marco Bonelli): It's also annoying that there isn't a decent way to track wiki changes 11/20/2020, 7:53:33 AM - waldyrious (Waldir Pimenta): it's technically a wiki, but yeah, the remote url is a little obscure 11/20/2020, 7:53:50 AM - waldyrious (Waldir Pimenta): I wonder if anyone being able to edit also allows anyone to delete pages 🤔 11/20/2020, 7:54:10 AM - waldyrious (Waldir Pimenta): in any case, page deletions may be visible in the tldr org's audit log 11/20/2020, 8:11:13 AM - mebeim (Marco Bonelli): I looked into it but AFAICT there does not seem to be any kind of entry related to Wikis: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#repo-category-actions 11/20/2020, 8:28:38 AM - waldyrious (Waldir Pimenta): In that case we will have to check out the wiki's repository. 11/20/2020, 8:29:04 AM - waldyrious (Waldir Pimenta): the url should be https://github.com/tldr-pages/tldr.wiki.git 11/20/2020, 8:31:36 AM - waldyrious (Waldir Pimenta): Ah, I figured out what happened 11/20/2020, 8:31:43 AM - waldyrious (Waldir Pimenta): the page was just renamed 😄 11/20/2020, 8:36:00 AM - waldyrious (Waldir Pimenta): @manuelhaussmann made an edit and seems to have written the edit summary in the title box, which renamed the page 11/20/2020, 8:36:06 AM - waldyrious (Waldir Pimenta): It's now back in place :) 11/20/2020, 9:09:53 AM - mebeim (Marco Bonelli): @waldyrious wait a sec, that git repo *exists*? How did you know? Where is it documented? 11/20/2020, 9:11:42 AM - mebeim (Marco Bonelli): I had no idea, amazing 11/20/2020, 2:25:11 PM - waldyrious (Waldir Pimenta): Yeah, it's not made very explicit by github, perhaps because it's a parallel repo to the main one (rather than, say, a branch like gh-pages). But it's in their docs :) 11/20/2020, 2:25:38 PM - waldyrious (Waldir Pimenta): https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/adding-or-editing-wiki-pages#adding-or-editing-wiki-pages-locally 11/20/2020, 2:25:45 PM - mebeim (Marco Bonelli): That's good to know for the future 11/20/2020, 2:26:24 PM - waldyrious (Waldir Pimenta): Yeah :) I always forget the repo URL but I know it's somewhere to be found, a google search away 😛 11/27/2020, 6:24:56 AM - sbrl (Starbeamrainbowlabs): Heya! Gotten distracted when reviewing and ended up tackling #4970 instead - which resulted in #4993 11/27/2020, 6:31:34 AM - sbrl (Starbeamrainbowlabs): Also, if someone with better vim knowledge than I could look at #4968 I'd be very grateful 😛 1/14/2023, 3:49:15 PM - ronan696 (Ronan D'Souza) joined the room 11/30/2020, 6:02:03 PM - ronan696 (Ronan D'Souza): Hey everyone! I have made a tldr pages integration for [Keypirinha](https://keypirinha.com/). Check it out here https://github.com/ronan696/keypirinha-tldr Would love to hear any feedback. Thanks! 1/14/2023, 3:49:20 PM - gitter-badger (The Gitter Badger) upgraded this room. 1/18/2023, 10:32:14 PM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) removed their profile picture 1/19/2023, 1:02:38 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) set a profile picture 1/19/2023, 12:56:42 PM - @wybgitlab:matrix.org joined the room 1/19/2023, 12:56:46 PM - @wybgitlab:matrix.org left the room 2/2/2023, 12:24:24 AM - gitter-badger (The Gitter Badger) changed the power level of waldyrious (Waldir Pimenta) from Default to Custom (90). 2/2/2023, 12:24:26 AM - gitter-badger (The Gitter Badger) changed the power level of agnivade (Agniva De Sarker) from Default to Custom (90). 2/2/2023, 12:24:27 AM - gitter-badger (The Gitter Badger) changed the power level of jeeftor (Jeef) from Default to Custom (90). 2/2/2023, 12:24:28 AM - gitter-badger (The Gitter Badger) changed the power level of sbrl (Starbeamrainbowlabs) from Default to Custom (90). 2/2/2023, 12:24:29 AM - gitter-badger (The Gitter Badger) changed the power level of jsonbruce (Max Xu) from Default to Custom (90). 2/2/2023, 12:24:30 AM - gitter-badger (The Gitter Badger) changed the power level of owenvoke (Owen Voke) from Default to Custom (90). 2/2/2023, 12:24:31 AM - gitter-badger (The Gitter Badger) changed the power level of mfrw (Muhammad Falak R Wani) from Default to Custom (90). 2/2/2023, 12:24:32 AM - gitter-badger (The Gitter Badger) changed the power level of mebeim (Marco Bonelli) from Default to Custom (90). 2/2/2023, 12:24:34 AM - gitter-badger (The Gitter Badger) changed the power level of andrik (Andrik Albuquerque) from Default to Custom (90). 2/2/2023, 12:24:35 AM - gitter-badger (The Gitter Badger) changed the power level of ivanhercaz (Iván Hernández Cazorla) from Default to Custom (90). 2/2/2023, 12:24:36 AM - gitter-badger (The Gitter Badger) changed the power level of MasterOdin (Matthew Peveler) from Default to Custom (90). 2/2/2023, 12:24:37 AM - gitter-badger (The Gitter Badger) changed the power level of navarroaxel (Axel Navarro) from Default to Custom (90). 2/2/2023, 12:24:39 AM - gitter-badger (The Gitter Badger) changed the power level of @yutyo-5ea6e62fd73408ce4fe1d7e5:gitter.im from Default to Custom (90). 2/2/2023, 12:24:39 AM - gitter-badger (The Gitter Badger) changed the power level of @aherst-603690126da03739846310de:gitter.im from Default to Custom (90). 2/2/2023, 12:24:40 AM - gitter-badger (The Gitter Badger) changed the power level of @marchersimon-6048a8806da0373984674b01:gitter.im from Default to Custom (90). 2/2/2023, 12:24:41 AM - gitter-badger (The Gitter Badger) changed the power level of @waples-5b923e2cd73408ce4fa73a2c:gitter.im from Default to Custom (90). 2/2/2023, 12:24:42 AM - gitter-badger (The Gitter Badger) changed the power level of @cleanmachine1-609af5956da03739847c6588:gitter.im from Default to Custom (90). 2/2/2023, 12:24:43 AM - gitter-badger (The Gitter Badger) changed the power level of @258204-60c8653d6da03739847ee928:gitter.im from Default to Custom (90). 2/2/2023, 12:24:44 AM - gitter-badger (The Gitter Badger) changed the power level of @blueskyson-6114a87a6da037398482fdd0:gitter.im from Default to Custom (90). 2/2/2023, 12:24:45 AM - gitter-badger (The Gitter Badger) changed the power level of @nico385412-62d6423b6da03739849a3cd9:gitter.im from Default to Custom (90). 2/2/2023, 12:24:46 AM - gitter-badger (The Gitter Badger) changed the power level of @kbdharun-62e60cef6da03739849abcc6:gitter.im from Default to Custom (90). 2/2/2023, 12:24:46 AM - gitter-badger (The Gitter Badger) changed the power level of @adrienthebo-5866e7a8d73408ce4f404843:gitter.im from Default to Custom (90). 2/3/2023, 2:28:32 AM - @amosbird-54e48ded15522ed4b3dc26b7:gitter.im left the room 2/3/2023, 2:28:33 AM - @andrewhavens-53c59994107e137846ba6bc9:gitter.im left the room 2/3/2023, 2:28:34 AM - @aydwi-59ba6bb1d73408ce4f75bce5:gitter.im left the room 2/3/2023, 2:28:35 AM - @crease29-59d5dbadd73408ce4f78ac62:gitter.im left the room 2/3/2023, 2:28:36 AM - @darless1-58c0c2c9d73408ce4f4f59f0:gitter.im left the room 2/3/2023, 2:28:37 AM - dgadelha (Douglas Gadêlha) left the room 2/3/2023, 2:28:38 AM - Erwyn (Martin Goyot) left the room 2/3/2023, 2:28:39 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) left the room 2/3/2023, 2:28:42 AM - ghost~57bf5afe40f3a6eec0615ad5 (Ghost) left the room 2/3/2023, 2:28:43 AM - guilhermeleobas (Guilherme Leobas) left the room 2/3/2023, 2:28:44 AM - hhirsch (Henry Hirsch) left the room 2/3/2023, 2:28:45 AM - idleberg (Jan T. Sott) left the room 2/3/2023, 2:28:46 AM - Jahhein (Jacob Hein) left the room 2/3/2023, 2:28:47 AM - jayvdb (John Vandenberg) left the room 2/3/2023, 2:28:49 AM - jeanlucaslima (Jean Lucas) left the room 2/3/2023, 2:28:50 AM - kosmgco (ooops) left the room 2/3/2023, 2:28:51 AM - Krutonium (Krutonium) left the room 2/3/2023, 2:28:52 AM - kschurter (kschurter) left the room 2/3/2023, 2:28:56 AM - marksylee (Mark Lee) left the room 2/3/2023, 2:28:58 AM - Mixih (mixih) left the room 2/3/2023, 2:28:59 AM - mstruebing (Max Strübing) left the room 2/3/2023, 2:29:01 AM - pfista (mikey) left the room 2/3/2023, 2:29:03 AM - rubenvereecken (Ruben Vereecken) left the room 2/3/2023, 2:29:04 AM - selfagency (Daniel Sieradski) left the room 2/3/2023, 2:29:06 AM - ShivamSinghania (Shivam Singhania) left the room