| 29 Mar 2024 |
 okinea | Please consider this PR - https://github.com/tldr-pages/tldr/pull/12571 | 08:24:57 |
| 2 Apr 2024 |
|  fazlearefin joined the room. | 02:28:11 |
| fazlearefin | Hi, I am @fazlearefin, the newest maintainer of tldr-pages. I am glad to be part of something which I personally use every single day.
My interest lies in Offensive Security and Web Penetration Testing. I look forward to adding more pages and improving existing ones related to OffSec | 02:40:02 |
| fazlearefin | * Hi, I am @fazlearefin, the newest maintainer of tldr-pages. I am glad to be part of something which I personally use every single day | 05:50:11 |
 Seth | In reply to @kbdk:matrix.org
Hi, I got a follow up mail from them a few hours ago, anything I should reply?
Hi Dharun,
Hope all is well! Following up regarding the above. Happy to announce Warp is now on Linux! Would you have interest in partnering with us for a github sponsorship?
Let us know and we can find some time to discuss further.
Best,
Tess
Seems everyone is too busy to keep up with the topic. ^-^'
In my opinion, a sensible response would probably be to ask if the placement of the ad is negotiable, and that we'd consider their proposal only if:
- We can place the sponsor near the bottom of the README.
- The ad is clearly marked as an ad, for example through a Markdown heading or through appending
#Ad at the end of their copy/text.
If we can agree on that with Warp, then we can have a more in-depth discussion and share what metrics we can with them.
Would anyone else like to chime in?
| 15:25:09 |
| Seth | In reply to @kbdk:matrix.org
Hi, I got a follow up mail from them a few hours ago, anything I should reply?
Hi Dharun,
Hope all is well! Following up regarding the above. Happy to announce Warp is now on Linux! Would you have interest in partnering with us for a github sponsorship?
Let us know and we can find some time to discuss further.
Best,
Tess
* Seems everyone is too busy to keep up with the topic. ^-^'
In my opinion, a sensible response would probably be to ask if the placement of the ad is negotiable, and that we'd consider their proposal only if:
- We can place the sponsor near the bottom of the README.
- The ad is clearly marked as an ad, for example through a Markdown heading or through appending
#Ad at the end of their copy/text.
If we can agree on that with Warp, then we can have a more in-depth discussion and share what metrics we can with them.
Would anyone else like to chime in?
| 15:25:51 |
| Seth | In reply to @kbdk:matrix.org
Hi, I got a follow up mail from them a few hours ago, anything I should reply?
Hi Dharun,
Hope all is well! Following up regarding the above. Happy to announce Warp is now on Linux! Would you have interest in partnering with us for a github sponsorship?
Let us know and we can find some time to discuss further.
Best,
Tess
* Seems everyone is too busy to keep up with the topic. ^-^'
In my opinion, a sensible response would probably be to ask if the placement of the ad is negotiable, and that we'd consider their proposal only if:
- We can place the sponsor near the bottom of the README.
- The ad is clearly marked as an ad, for example through a Markdown heading or through prefixing
#Ad to the start of their copy.
If we can agree on that with Warp, then we can have a more in-depth discussion and share what metrics we can with them.
Would anyone else like to chime in?
| 15:27:02 |
| 4 Apr 2024 |
|  @0323pin:converser.eu left the room. | 11:42:27 |
| 5 Apr 2024 |
 sbrl (Starbeamrainbowlabs) | Welcome, fazlearefin! | 21:47:09 |
| sbrl (Starbeamrainbowlabs) | This all seems sensible to me.
I would agree I would be most comfortable with any placement like that at the bottom of the readme if we were to accept sponsorships. | 23:55:45 |
| 13 Apr 2024 |
 Managor | Uhhh... what? https://github.com/tldr-pages/tldr/pull/12638 | 08:48:13 |
| Seth | In reply to @managor:matrix.org
Uhhh... what? https://github.com/tldr-pages/tldr/pull/12638 Could you explain your comment and what you think is wrong with the PR? š¤ļø | 09:53:10 |
| Managor | He opened an external PR for his own fork and then closed it after merging into his branch into his main | 09:56:33 |
| Managor | He already has one open PR for yt-dlp | 09:58:01 |
| Managor | The guy needs someone to guide him through the process. His contributions are a mess | 09:59:01 |
| Seth | Understood, in future it'd be more respectful to run through those details in the comment. It also ensures other collaborates have the context.
The contributor looks like they may just not have much experience with Git, and I don't think your comment on GitHub is the kind of guidance that's going to make their contributions less messy.
Even paired with your comment here, it's not very constructive, and the contributor that needs the message didn't get it.
| 10:04:39 |
| Seth | In reply to @sbrl-57247531659847a7aff542b6:gitter.im
This all seems sensible to me.
I would agree I would be most comfortable with any placement like that at the bottom of the readme if we were to accept sponsorships. It seems everyone is too busy, so getting the consensus from everyone will be challenging in the Matrix chat.
Perhaps a GitHub discussion thread is a more appropriate place for this? Then we can finalize whatever actions we want to take.
| 10:12:25 |
|  Milo Moisson set a profile picture. | 11:39:09 |
 K.B.Dharun Krishna | In reply to @sethi:one.ems.host
It seems everyone is too busy, so getting the consensus from everyone will be challenging in the Matrix chat.
Perhaps a GitHub discussion thread is a more appropriate place for this? Then we can finalize whatever actions we want to take.
Yeah, that would work the best. | 12:43:43 |
| Managor | See here https://github.com/tldr-pages/tldr/pull/12580 | 13:34:28 |
| sbrl (Starbeamrainbowlabs) | In reply to @sethi:one.ems.host
Understood, in future it'd be more respectful to run through those details in the comment. It also ensures other collaborates have the context.
The contributor looks like they may just not have much experience with Git, and I don't think your comment on GitHub is the kind of guidance that's going to make their contributions less messy.
Even paired with your comment here, it's not very constructive, and the contributor that needs the message didn't get it.
To add context, we often see contributors to tldr-pages who haven't used git before, or are just starting out in open-source. It's up to us to give them a warm welcome!
If in doubt, always assume good faith :D | 19:07:12 |
| sbrl (Starbeamrainbowlabs) | In reply to @sethi:one.ems.host
It seems everyone is too busy, so getting the consensus from everyone will be challenging in the Matrix chat.
Perhaps a GitHub discussion thread is a more appropriate place for this? Then we can finalize whatever actions we want to take.
sounds good. Perhaps post a link here when the issue/thread is opened to allow people to follow it? | 19:08:08 |
| 14 Apr 2024 |
 waldyrious | Just to add to this: even when good faith seems unlikely, it's still a good idea to respond as if it can be assumed, because (1) that sets the tone for the community's communication style, and (2) it can actually clarify similar questions by others who come across the discussion and, due to lack of context, might recognize the action as something that they themselves might have done. | 19:10:58 |
| waldyrious | It's worth remembering that the tldr-pages project operates entirely in public: both comments in issues and PRs on GitHubs, and messages in this chat room, are public and recorded for all of posterity. That's quite a responsibility if you think about it :) And it's very hard to be kind and patient all the time, so we need to be constantly reinforcing each other to pay attention to all those micro interactions that may be interpreted as a dry, curt, or otherwise non-welcoming. | 19:14:00 |
| waldyrious | * It's worth remembering that the tldr-pages project operates entirely in public: both comments in issues and PRs on GitHubs, and messages in this chat room, are public and recorded for all of posterity. That's quite a responsibility if you think about it :) And it's very hard to be kind and patient all the time, so we need to be constantly reinforcing each other to pay attention to all those micro interactions that may be interpreted as dry, curt, or otherwise non-welcoming. | 19:28:14 |
| 18 Apr 2024 |
|  @witchcraftery:private.coffee joined the room. | 08:56:18 |
| 19 Apr 2024 |
| @witchcraftery:private.coffee removed their profile picture. | 10:36:50 |
| @witchcraftery:private.coffee removed their display name zā·. | 10:36:59 |
| @witchcraftery:private.coffee left the room. | 10:37:33 |
| 23 Apr 2024 |
|  Sluffer set a profile picture. | 01:28:42 |
