Comments (5)
bean5
commented on May 31, 2024
I still think it is ambiguous, actually. To be fully unambiguous, perhaps:
Please don't give other users legal advice. Legal advice tends to confuse users.
OR
Please don't give advice because it tends to confuse them.
OR
To avoid confusing users, please don't give legal advice.
What do you think? In any case, mind making a small PR for your proposal for a speedier acceptance and application (if approved)?
from site-policy.
sf-mrichter
commented on May 31, 2024
I don’t see the sit-policy branch. Where should I create the PR?
From: Bean [mailto:[email protected]]
Sent: Monday, July 17, 2017 06:24
To: github/site-policy <[email protected]>
Cc: Mark Richter <[email protected]>; Author <[email protected]>
Subject: Re: [github/site-policy] README wording suggestion (#27)
I still think it is ambiguous, actually. To be fully unambiguous, perhaps:
Please don't give other users legal advice. Legal advice tends to confuse users.
OR
Please don't give advice because it tends to confuse them.
OR
To avoid confusing users, please don't give legal advice.
What do you think? In any case, mind making a small PR for your proposal for a speedier acceptance and application (if approved)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_github_site-2Dpolicy_issues_27-23issuecomment-2D315754255&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=Ba6UtYrUHlYN5K8RsM0CIDyGxOYiHWJT7AJ4pgtxGSs&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AbSDW1K8C54e-5FfdiPDzEFt03KZqS3OHrks5sO2B1gaJpZM4OTVj7&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=2xzi2b3TWhh6s5z80G7UCP5mV6xHcNgXvNmWmRP_cCE&e=>.
The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.
from site-policy.
sf-mrichter
commented on May 31, 2024
Scratch that (I gotta read the pages more carefully…).
Which branch of site-policy should I use?
From: Mark Richter
Sent: Monday, July 17, 2017 10:23
To: 'github/site-policy' <[email protected]>; github/site-policy <[email protected]>
Cc: Author <[email protected]>
Subject: RE: [github/site-policy] README wording suggestion (#27)
I don’t see the sit-policy branch. Where should I create the PR?
From: Bean [mailto:[email protected]]
Sent: Monday, July 17, 2017 06:24
To: github/site-policy <[email protected]<mailto:[email protected]>>
Cc: Mark Richter <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>>
Subject: Re: [github/site-policy] README wording suggestion (#27)
I still think it is ambiguous, actually. To be fully unambiguous, perhaps:
Please don't give other users legal advice. Legal advice tends to confuse users.
OR
Please don't give advice because it tends to confuse them.
OR
To avoid confusing users, please don't give legal advice.
What do you think? In any case, mind making a small PR for your proposal for a speedier acceptance and application (if approved)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_github_site-2Dpolicy_issues_27-23issuecomment-2D315754255&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=Ba6UtYrUHlYN5K8RsM0CIDyGxOYiHWJT7AJ4pgtxGSs&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AbSDW1K8C54e-5FfdiPDzEFt03KZqS3OHrks5sO2B1gaJpZM4OTVj7&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=2xzi2b3TWhh6s5z80G7UCP5mV6xHcNgXvNmWmRP_cCE&e=>.
The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.
from site-policy.
bean5
commented on May 31, 2024
I do but know either.
…On Mon, Jul 17, 2017, 10:24 AM Mark Richter ***@***.***> wrote:
Scratch that (I gotta read the pages more carefully…).
Which branch of site-policy should I use?
From: Mark Richter
Sent: Monday, July 17, 2017 10:23
To: 'github/site-policy' ***@***.***>; github/site-policy <
***@***.***>
Cc: Author ***@***.***>
Subject: RE: [github/site-policy] README wording suggestion (#27)
I don’t see the sit-policy branch. Where should I create the PR?
From: Bean ***@***.***
Sent: Monday, July 17, 2017 06:24
To: github/site-policy ***@***.***<mailto:
***@***.***>>
Cc: Mark Richter ***@***.******@***.***>>;
Author ***@***.******@***.***>>
Subject: Re: [github/site-policy] README wording suggestion (#27)
I still think it is ambiguous, actually. To be fully unambiguous, perhaps:
Please don't give other users legal advice. Legal advice tends to confuse
users.
OR
Please don't give advice because it tends to confuse them.
OR
To avoid confusing users, please don't give legal advice.
What do you think? In any case, mind making a small PR for your proposal
for a speedier acceptance and application (if approved)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_github_site-2Dpolicy_issues_27-23issuecomment-2D315754255&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=Ba6UtYrUHlYN5K8RsM0CIDyGxOYiHWJT7AJ4pgtxGSs&e=>,
or mute the thread<
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AbSDW1K8C54e-5FfdiPDzEFt03KZqS3OHrks5sO2B1gaJpZM4OTVj7&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=524okDh5adlYIDB-3DGPNV66wpWvvI-6Uyp96Y4GLbA&m=wqnVMD0i-6E6lyKWb5gpcCMT_BnveCUr8mJhPhp9W0U&s=2xzi2b3TWhh6s5z80G7UCP5mV6xHcNgXvNmWmRP_cCE&e=>.
The information contained in this message is confidential and is intended
for the addressee(s) only. If you have received this message in error,
please notify the sender immediately and delete the message. Unless you are
an addressee (or authorized to receive for an addressee), you may not use,
copy or disclose to anyone this message or any information contained in
this message. The unauthorized use, disclosure, copying or alteration of
this message is strictly prohibited.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB9SJrhdFd0PSQc41t9f-Efn-Vsdm5VHks5sO5i0gaJpZM4OTVj7>
.
from site-policy.
nsqe
commented on May 31, 2024
Thanks, @sf-mrichter and @bean5.
We took another look at the language, but ultimately, we think we're pretty clear that users shouldn't be giving legal advice in this repository. There are many reasons why users should not be giving legal advice here, and we don't think most people will be confused by our wording.
from site-policy.
Related Issues (20)
- Hello world HOT 1
- Bhdrmms HOT 2
- Some one hack this polli y please block the Lunix window site HOT 3
- Outdated how to update all HOT 1
- Recuperando
- My payment back
- Typo in site-policy/CONTRIBUTING.md HOT 1
- Policy
- 油猴
- gearky forsk
- My neighbor was cloning my phone
- Contribute
- Reporting typos in doc: "Building a CLI with a GitHub App" HOT 3
- Yo
- Manager
- We want to thank everyone for their review and feedback on the Privacy Statement Update. We appreciate and share your passion for developer privacy. GitHub remains committed to having the highest privacy standards and will continue to center the needs of developers in all of our platform decisions. We intend for this to be a minimally invasive change that will enable us to provide the best tools to our users. In response to your comments, we are providing the following changes and points of clarification: HOT 1
- ###？？？
- services.google.com/corporate/publickey.txt
- Manager
- Content Taxonomies/Content Taxonomy 3.0.tsv
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from site-policy.